Verschillende BSOD win 7

[Anoniem2]

hallo, al enige tijd krijg ik regelmatig BSOD\'s en word er gek van. De ene keer vaker dan de andere keer, gebeurd het vaakst als ik grafisch bezig ben.\r\n\r\nHieronder de crash dump en ik hoop dat iemand me op weg kan helpen!\r\n\r\n[CODE]System Information (local)\r\n--------------------------------------------------------------------------------\r\n\r\ncomputer name: BOXY-HP\r\nwindows version: Windows 7 Service Pack 1, 6.1, build: 7601\r\nwindows dir: C:\\Windows\r\nCPU: AuthenticAMD AMD Phenom(tm) II X6 1045T Processor AMD586, level: 16\r\n6 logical processors, active mask: 63\r\nRAM: 4294217728 total\r\nVM: 2147352576, free: 1977032704\r\n\r\n\r\n\r\n--------------------------------------------------------------------------------\r\nCrash Dump Analysis\r\n--------------------------------------------------------------------------------\r\n\r\nCrash dump directory: C:\\Windows\\Minidump\r\n\r\nCrash dumps are enabled on your computer.\r\n\r\n\r\nOn Sun 23-9-2012 20:12:11 GMT your computer crashed\r\ncrash dump file: C:\\Windows\\Minidump\\092312-16473-01.dmp\r\nThis was probably caused by the following module: usbport.sys (USBPORT+0x2D27D) \r\nBugcheck code: 0xFE (0x6, 0xFFFFFA80062A2C20, 0x43787254, 0x0)\r\nError: BUGCODE_USB_DRIVER\r\nfile path: C:\\Windows\\system32\\drivers\\usbport.sys\r\nproduct: Besturingssysteem Microsoft® Windows®\r\ncompany: Microsoft Corporation\r\ndescription: Poortstuurprogramma voor USB 1.1 en 2.0\r\nBug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.\r\nThe crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time. \r\n\r\n\r\nOn Sun 23-9-2012 20:00:53 GMT your computer crashed\r\ncrash dump file: C:\\Windows\\Minidump\\092312-16848-01.dmp\r\nThis was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) \r\nBugcheck code: 0x50 (0xFFFFF80000000000, 0x0, 0xFFFFF80002FA8F39, 0x0)\r\nError: PAGE_FAULT_IN_NONPAGED_AREA\r\nfile path: C:\\Windows\\system32\\ntoskrnl.exe\r\nproduct: Microsoft® Windows® Operating System\r\ncompany: Microsoft Corporation\r\ndescription: NT Kernel & System\r\nBug check description: This indicates that invalid system memory has been referenced.\r\nThis appears to be a typical software driver bug and is not likely to be caused by a hardware problem. \r\nThe crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. \r\n\r\n\r\nOn Sun 23-9-2012 19:58:30 GMT your computer crashed\r\ncrash dump file: C:\\Windows\\Minidump\\092312-16286-01.dmp\r\nThis was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) \r\nBugcheck code: 0x50 (0xFFFFFA7FF0BEECB0, 0x0, 0xFFFFF8800659D06B, 0x7)\r\nError: PAGE_FAULT_IN_NONPAGED_AREA\r\nfile path: C:\\Windows\\system32\\ntoskrnl.exe\r\nproduct: Microsoft® Windows® Operating System\r\ncompany: Microsoft Corporation\r\ndescription: NT Kernel & System\r\nBug check description: This indicates that invalid system memory has been referenced.\r\nThis appears to be a typical software driver bug and is not likely to be caused by a hardware problem. \r\nThe crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. \r\n\r\n\r\nOn Sun 23-9-2012 19:54:12 GMT your computer crashed\r\ncrash dump file: C:\\Windows\\Minidump\\092312-19312-01.dmp\r\nThis was probably caused by the following module: sptd.sys (sptd+0x44CF4) \r\nBugcheck code: 0xBE (0xFFFFF880010B0CF4, 0x3545121, 0xFFFFF880030B0A20, 0xA)\r\nError: ATTEMPTED_WRITE_TO_READONLY_MEMORY\r\nfile path: C:\\Windows\\system32\\drivers\\sptd.sys\r\nBug check description: This is issued if a driver attempts to write to a read-only memory segment.\r\nThis appears to be a typical software driver bug and is not likely to be caused by a hardware problem. \r\nA third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: sptd.sys . \r\nGoogle query: sptd.sys ATTEMPTED_WRITE_TO_READONLY_MEMORY\r\n\r\n\r\n\r\n\r\nOn Sat 22-9-2012 15:53:16 GMT your computer crashed\r\ncrash dump file: C:\\Windows\\Minidump\\092312-27705-01.dmp\r\nThis was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) \r\nBugcheck code: 0x9F (0x3, 0xFFFFFA8006042060, 0xFFFFF80000B9C518, 0xFFFFFA8005C41410)\r\nError: DRIVER_POWER_STATE_FAILURE\r\nfile path: C:\\Windows\\system32\\ntoskrnl.exe\r\nproduct: Microsoft® Windows® Operating System\r\ncompany: Microsoft Corporation\r\ndescription: NT Kernel & System\r\nBug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.\r\nThis appears to be a typical software driver bug and is not likely to be caused by a hardware problem. \r\nThe crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. \r\n\r\n\r\nOn Wed 19-9-2012 18:17:00 GMT your computer crashed\r\ncrash dump file: C:\\Windows\\Minidump\\091912-19999-01.dmp\r\nThis was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) \r\nBugcheck code: 0x3D (0xFFFFF8800298F830, 0x0, 0x0, 0xFFFFFA800630513B)\r\nError: INTERRUPT_EXCEPTION_NOT_HANDLED\r\nfile path: C:\\Windows\\system32\\ntoskrnl.exe\r\nproduct: Microsoft® Windows® Operating System\r\ncompany: Microsoft Corporation\r\ndescription: NT Kernel & System\r\nBug check description: This bug check appears very infrequently. \r\nThe crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. \r\n\r\n\r\nOn Wed 19-9-2012 17:19:22 GMT your computer crashed\r\ncrash dump file: C:\\Windows\\Minidump\\091912-30888-01.dmp\r\nThis was probably caused by the following module: fltmgr.sys (fltmgr+0x7189) \r\nBugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF88000D74189, 0x1, 0x730010)\r\nError: KMODE_EXCEPTION_NOT_HANDLED\r\nfile path: C:\\Windows\\system32\\drivers\\fltmgr.sys\r\nproduct: Besturingssysteem Microsoft® Windows®\r\ncompany: Microsoft Corporation\r\ndescription: Microsoft Bestandssysteemfilterbeheer\r\nBug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.\r\nThis appears to be a typical software driver bug and is not likely to be caused by a hardware problem. \r\nThe crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time. \r\n\r\n\r\nOn Wed 19-9-2012 12:46:35 GMT your computer crashed\r\ncrash dump file: C:\\Windows\\Minidump\\091912-20030-01.dmp\r\nThis was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) \r\nBugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002CF84E5, 0x0, 0xFFFFFFFFFFFFFFFF)\r\nError: KMODE_EXCEPTION_NOT_HANDLED\r\nfile path: C:\\Windows\\system32\\ntoskrnl.exe\r\nproduct: Microsoft® Windows® Operating System\r\ncompany: Microsoft Corporation\r\ndescription: NT Kernel & System\r\nBug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.\r\nThis appears to be a typical software driver bug and is not likely to be caused by a hardware problem. \r\nThe crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. \r\n\r\n\r\nOn Wed 19-9-2012 7:29:56 GMT your computer crashed\r\ncrash dump file: C:\\Windows\\Minidump\\091912-24663-01.dmp\r\nThis was probably caused by the following module: fltmgr.sys (fltmgr+0x22751) \r\nBugcheck code: 0x1A (0x41201, 0xFFFFF68000095808, 0xFDB000011E418667, 0xFFFFFA8007613F70)\r\nError: MEMORY_MANAGEMENT\r\nfile path: C:\\Windows\\system32\\drivers\\fltmgr.sys\r\nproduct: Besturingssysteem Microsoft® Windows®\r\ncompany: Microsoft Corporation\r\ndescription: Microsoft Bestandssysteemfilterbeheer\r\nBug check description: This indicates that a severe memory management error occurred.\r\nThis might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. \r\nThe crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time. \r\n\r\n\r\nOn Mon 17-9-2012 19:54:30 GMT your computer crashed\r\ncrash dump file: C:\\Windows\\Minidump\\091712-19936-01.dmp\r\nThis was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) \r\nBugcheck code: 0xA (0x400707, 0x2, 0x0, 0xFFFFF80002CE1915)\r\nError: IRQL_NOT_LESS_OR_EQUAL\r\nfile path: C:\\Windows\\system32\\ntoskrnl.exe\r\nproduct: Microsoft® Windows® Operating System\r\ncompany: Microsoft Corporation\r\ndescription: NT Kernel & System\r\nBug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.\r\nThis appears to be a typical software driver bug and is not likely to be caused by a hardware problem. \r\nThe crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. \r\n\r\n\r\nOn Tue 4-9-2012 18:59:09 GMT your computer crashed\r\ncrash dump file: C:\\Windows\\Minidump\\090412-16083-01.dmp\r\nThis was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) \r\nBugcheck code: 0xA (0xFFFFF88003284510, 0x2, 0x1, 0xFFFFF80002C83A2F)\r\nError: IRQL_NOT_LESS_OR_EQUAL\r\nfile path: C:\\Windows\\system32\\ntoskrnl.exe\r\nproduct: Microsoft® Windows® Operating System\r\ncompany: Microsoft Corporation\r\ndescription: NT Kernel & System\r\nBug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.\r\nThis appears to be a typical software driver bug and is not likely to be caused by a hardware problem. \r\nThe crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. \r\n\r\n\r\nOn Sun 29-7-2012 8:08:38 GMT your computer crashed\r\ncrash dump file: C:\\Windows\\Minidump\\072912-21668-01.dmp\r\nThis was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) \r\nBugcheck code: 0xA (0x1BEFFFFC2, 0x2, 0x0, 0xFFFFF80002CA8332)\r\nError: IRQL_NOT_LESS_OR_EQUAL\r\nfile path: C:\\Windows\\system32\\ntoskrnl.exe\r\nproduct: Microsoft® Windows® Operating System\r\ncompany: Microsoft Corporation\r\ndescription: NT Kernel & System\r\nBug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.\r\nThis appears to be a typical software driver bug and is not likely to be caused by a hardware problem. \r\nThe crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. \r\n\r\n\r\nOn Fri 27-7-2012 10:30:08 GMT your computer crashed\r\ncrash dump file: C:\\Windows\\Minidump\\072912-21652-01.dmp\r\nThis was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) \r\nBugcheck code: 0xD1 (0xFFFFF80002B99AC0, 0x2, 0x8, 0xFFFFF80002B99AC0)\r\nError: DRIVER_IRQL_NOT_LESS_OR_EQUAL\r\nfile path: C:\\Windows\\system32\\ntoskrnl.exe\r\nproduct: Microsoft® Windows® Operating System\r\ncompany: Microsoft Corporation\r\ndescription: NT Kernel & System\r\nBug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.\r\nThis appears to be a typical software driver bug and is not likely to be caused by a hardware problem. \r\nThe crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. \r\n\r\n\r\nOn Wed 25-7-2012 20:32:12 GMT your computer crashed\r\ncrash dump file: C:\\Windows\\Minidump\\072712-20092-01.dmp\r\nThis was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) \r\nBugcheck code: 0x1A (0x41287, 0x30, 0x0, 0x0)\r\nError: MEMORY_MANAGEMENT\r\nfile path: C:\\Windows\\system32\\ntoskrnl.exe\r\nproduct: Microsoft® Windows® Operating System\r\ncompany: Microsoft Corporation\r\ndescription: NT Kernel & System\r\nBug check description: This indicates that a severe memory management error occurred.\r\nThis might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. \r\nThe crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. \r\n\r\n\r\nOn Tue 24-7-2012 17:37:14 GMT your computer crashed\r\ncrash dump file: C:\\Windows\\Minidump\\072412-17066-01.dmp\r\nThis was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) \r\nBugcheck code: 0x50 (0xFFFFF8A00B5F4788, 0x1, 0xFFFFF80002F5FC64, 0x2)\r\nError: PAGE_FAULT_IN_NONPAGED_AREA\r\nfile path: C:\\Windows\\system32\\ntoskrnl.exe\r\nproduct: Microsoft® Windows® Operating System\r\ncompany: Microsoft Corporation\r\ndescription: NT Kernel & System\r\nBug check description: This indicates that invalid system memory has been referenced.\r\nThis appears to be a typical software driver bug and is not likely to be caused by a hardware problem. \r\nThe crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. \r\n[/CODE]

[Anoniem2]

[B]Bug Check 0xFE: BUGCODE_USB_DRIVER[/B] : The BUGCODE_USB_DRIVER bug check has a value of 0x000000FE. This indicates that an error has occurred in a universal serial bus (USB) driver - [url]http://msdn.microsoft.com/en-us/library/windows/hardware/ff560407(v=vs.85).aspx[/url]\n\nVerwijder eerst all USB-randapparatuur.\nSchakel in [B]Apparaatbeheer[/B] eens alle USB-poorten uit en start de PC opnieuw in.\n\nKijk ook evtl. eens hier : [B]Welkom bij het Fix it support center [/B] - [url]http://support.microsoft.com/fixit/[/url]

[Anoniem2]

Graag zie ik de bestanden in de volgende folders:\nC:\\Windows\\Minidump\nC:\\Windows\\LiveKernelReports\\WATCHDOG\n\nGebruik nog even niet \"Disk Cleanup\' van Windows zelf, dat gooit ze namelijk weg.\nDoe alle bestanden even in een zip of rar.

[Anoniem2]

Zo veel verschillende BSOD\'s duiden meestal op kapot geheugen of een kapotte harde schijf.\nOpen command prompt als Administrator en typ het volgende:\nsfc scannow\n\nNu worden alle Windows bestanden gecontroleerd op fouten. Als hij fouten vind, sluit het venster dan niet maar zeg het dan even, dan kan ik uitleggen hoe de log op te slaan.\n\nRun ook even Disk Check van Windows zelf. Als je weet hoe Memtest werkt draai die dan ook, zo niet kan er iemand anders precies uitleggen wat te doen.

[Anoniem2]

Hoi jeroen,\r\n\r\nbedankt dat je er even naar wilt kijken. Zoals je wilde heb ik ze in een rar gedaan. zie [URL=\"http://www.boxworx.nl/Desktop.rar\"]link[/URL] want hij is groter dan dat ik hier als bijlagen kan uploaden.

[Anoniem2]

op dit moment ben ik de sfc scannow aan het uitvoeren...

[Anoniem2]

Hoi Jeroen,\r\n\r\nDisk check uitgevoerd en er zijn beschadigde bestanden gevonden maar kunnen niet allemaal worden hersteld.\r\n\r\nIk heb de CBS.log file beschikbaar onder deze [URL=\"http://www.boxworx.nl/CBS.log\"]link[/URL]\r\n\r\nMvg

[Anoniem2]

[QUOTE=mboxy;622624]Hoi Jeroen,\r\n\r\nDisk check uitgevoerd en er zijn beschadigde bestanden gevonden maar kunnen niet allemaal worden hersteld.\r\n\r\nIk heb de CBS.log file beschikbaar onder deze [URL=\"http://www.boxworx.nl/CBS.log\"]link[/URL]\r\n\r\nMvg[/QUOTE]\r\n\r\nDit wilde ik voorkomen eigenlijk. Voor het log open command prompt en typ het volgende letterlijk over:\r\nfindstr /c:\"[SR]\" %windir%\\Logs\\CBS\\CBS.log >\"%userprofile%\\Desktop\\sfcdetails.txt\"\r\n\r\nPost dat tekstbestand.

[Anoniem2]

Heel veel fouten uit de minidump geven ntoskrnl.exe. Als je verder kijkt naar de WATCHDOG crashdumps kun je zien dat in iedere foutmelding wel atikmpag.sys voorkomt. Dit zijn de drivers van je ATI/AMD videokaart. Deïnstalleer deze volgens [URL=\"http://www.overclock.net/t/988215/how-to-properly-uninstall-ati-amd-software-drivers-for-graphics-cards\"]deze[/URL] handleiding. Installeer ze hierna opnieuw, na een herstart. Laat ook Disk Cleaner van Windows draaien. Al je minidumps heb je (ik) nu.\nAangezien er zo veel verschillende fouten zijn is het goed mogelijk dat je geheugen kapot is. Gebruik [URL=\"http://www.memtest.org/\"]dit[/URL] programma om je geheugen te testen en [URL=\"http://majorgeeks.com/Video_Memory_Stress_Test__d5896.html\"]dit[/URL] programma om je videokaart geheugen te testen op fouten.

[Anoniem2]

[QUOTE=Jeroentje94;622628]Dit wilde ik voorkomen eigenlijk. Voor het log open command prompt en typ het volgende letterlijk over:\r\nfindstr /c:\"[SR]\" %windir%\\Logs\\CBS\\CBS.log >\"%userprofile%\\Desktop\\sfcdetails.txt\"\r\n\r\nPost dat tekstbestand.[/QUOTE]\r\n\r\ndat moet ik invoeren als ik de command prompt heb geopent doormiddel van CMD toch? maar helaas werkte dit niet?

[Anoniem2]

ik heb de videokaart geheugen getest en er is nix bijzonders gevonden, zie hieronder\n[QUOTE]WARNING: Your card can be not compatible with this test! If multiple errors will found, try test with onscreen buffer usage or wthout of ignoring colors bit mask.\nChanging video mode to 640x480x16...OK\n[9/25/2012 12:51:15 PM] Test started for \"Primair beeldschermstuurprogramma (ATI Radeon HD 5450)\"...\nTrying 16bpp RGB:565 mode...OK\nTrying 16bpp RGB:555 mode...OK\nTrying 16bpp BGR:565 mode...NOT SUPPORTED (Code: 80004001)\nTrying 32bpp RGB:888 mode...OK\nTrying 32bpp BGR:888 mode...NOT SUPPORTED (Code: 80004001)\n[9/25/2012 2:05:45 PM] Pass completed (0 errors found).[/QUOTE]

[Anoniem2]

[QUOTE=mboxy;622646]dat moet ik invoeren als ik de command prompt heb geopent doormiddel van CMD toch? maar helaas werkte dit niet?[/QUOTE]\r\n\r\nCMD is de command prompt. Nadat je sfc scannow hebt laten draaien dit meteen intypen.

[Anoniem2]

Oke ga ik nogmaals doen, memtest staat momenteel te draaien, kan ik hier ook een logbestand van vinden? Of moet ik ergens zelf opletten?

[Anoniem2]

[QUOTE=mboxy;622658]Oke ga ik nogmaals doen, memtest staat momenteel te draaien, kan ik hier ook een logbestand van vinden? Of moet ik ergens zelf opletten?[/QUOTE]\n\nEhm, geen idee of die een log maakt. Kijk gewoon als hij klaar is of hij fouten heeft gegeven.\nBTW: het is sfc /scannow. Foutje van mij.

[Anoniem2]

Ik heb de memtest 10x laten rond gaan en hij geeft aan: pass complete, no errors... Dus mijn geheugen is in orde?

[Anoniem2]

Kun je hier eens een[B] Overzicht[/B] van [B]Speccy[/B] plaatsen ?\r\nSpeccy : [url]http://www.filehippo.com/download_speccy/[/url]

[Anoniem2]

[QUOTE=mboxy;622688]Ik heb de memtest 10x laten rond gaan en hij geeft aan: pass complete, no errors... Dus mijn geheugen is in orde?[/QUOTE]\r\n\r\nDat lijkt me wel ja.

[Anoniem2]

[B]AMD Support & Drivers[/B] - [url]http://support.amd.com/us/Pages/AMDSupportHub.aspx[/url]\r\nKijk op deze pagina eens hier :[B] Automatically Detect and Install[/B]

[Anoniem2]

[QUOTE=ricky1;622690]Kun je hier eens een[B] Overzicht[/B] van [B]Speccy[/B] plaatsen ?\r\nSpeccy : [url]http://www.filehippo.com/download_speccy/[/url][/QUOTE]\r\n\r\nzie [URL=\"http://www.boxworx.nl/BOXY-HP.txt\"]bijlage[/URL]

[Anoniem2]

Beter je licentie code even verwijderen uit de bijlage. ;)\r\nVoordat iemand ermee aan de haal gaat.