System Information (local)
--------------------------------------------------------------------------------
computer name: NIEK-PC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: AuthenticAMD AMD Phenom(tm) II X6 1035T Processor AMD586, level: 16
6 logical processors, active mask: 63
RAM: 4294164480 total
VM: 2147352576, free: 1981243392
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Thu 2-6-2011 11:36:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060211-18220-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7E24A)
Bugcheck code: 0x4E (0x7, 0xB4903, 0xFF000000000000, 0x0)
Error: PFN_LIST_CORRUPT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Thu 2-6-2011 8:53:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060211-16676-01.dmp
This was probably caused by the following module: unknown_module_00000000`00000001.sys (Unloaded_Unknown_Module_00000000`00000001+0x3FF76CD9)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002A76C3D, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A 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: unknown_module_00000000`00000001.sys .
Google query: unknown_module_00000000`00000001.sys KMODE_EXCEPTION_NOT_HANDLED
On Sun 29-5-2011 10:18:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052911-19780-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x42A5)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8800122C2A5, 0xFFFFF88002FA79B8, 0xFFFFF88002FA7220)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\ntfs.sys
product: Besturingssysteem Microsoft® Windows®
company: Microsoft Corporation
description: NT-bestandssysteemstuurprogramma
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The 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.
On Sun 29-5-2011 7:33:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052911-16536-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0xD5DD)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88000DA75DD, 0xFFFFF88009686EF0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Besturingssysteem Microsoft® Windows®
company: Microsoft Corporation
description: Microsoft Bestandssysteemfilterbeheer
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The 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.
On Sun 29-5-2011 7:31:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052911-17378-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x2DE4E)
Bugcheck code: 0xFE (0x5, 0xFFFFFA80044781A0, 0x10DE077C, 0xFFFFFA8004F99C50)
Error: BUGCODE_USB_DRIVER
file path: C:\Windows\system32\drivers\usbport.sys
product: Besturingssysteem Microsoft® Windows®
company: Microsoft Corporation
description: Poortstuurprogramma voor USB 1.1 en 2.0
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
The 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.
On Wed 25-5-2011 10:10:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052711-17175-01.dmp
This was probably caused by the following module: Unknown (0xFFFFF880068E06E4)
Bugcheck code: 0xA0000001 (0x5, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A 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: Unknown .
Google query: Unknown CUSTOM_ERROR
On Wed 25-5-2011 10:05:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052511-15974-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x706D0)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Wed 25-5-2011 8:57:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052511-18080-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70700)
Bugcheck code: 0xC4 (0x91, 0x0, 0xFFFFFA8003A03040, 0x0)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
The driver switched stacks using a method that is not supported by the operating system. The only supported way to extend a kernel mode stack is by using KeExpandKernelStackAndCallout. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Wed 25-5-2011 8:20:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052511-17269-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x2DE4E)
Bugcheck code: 0xFE (0x5, 0xFFFFFA80041731A0, 0x10DE077E, 0xFFFFFA800403BC50)
Error: BUGCODE_USB_DRIVER
file path: C:\Windows\system32\drivers\usbport.sys
product: Besturingssysteem Microsoft® Windows®
company: Microsoft Corporation
description: Poortstuurprogramma voor USB 1.1 en 2.0
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
The 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.
On Wed 25-5-2011 7:02:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052511-17035-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70700)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80003B5C50, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sun 22-5-2011 9:35:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052211-18704-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70700)
Bugcheck code: 0x19 (0x22, 0xFB000000000000, 0x0, 0x0)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sun 15-5-2011 12:10:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051511-48609-01.dmp
This was probably caused by the following module: g? (nt+0x769A)
Bugcheck code: 0xFE (0x5, 0xFFFFFA80043F41A0, 0x10DE077C, 0xFFFFFA8004DA1C50)
Error: BUGCODE_USB_DRIVER
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
A 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: g? .
Google query: g? BUGCODE_USB_DRIVER
On Sun 15-5-2011 10:41:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051511-21559-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x2DE4E)
Bugcheck code: 0xFE (0x5, 0xFFFFFA80043FF1A0, 0x10DE077C, 0xFFFFFA8004DBFC50)
Error: BUGCODE_USB_DRIVER
file path: C:\Windows\system32\drivers\usbport.sys
product: Besturingssysteem Microsoft® Windows®
company: Microsoft Corporation
description: Poortstuurprogramma voor USB 1.1 en 2.0
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
The 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.
On Sun 15-5-2011 9:55:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051511-13572-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x2DE4E)
Bugcheck code: 0xFE (0x5, 0xFFFFFA8004D891A0, 0x10DE077E, 0xFFFFFA8006F88C50)
Error: BUGCODE_USB_DRIVER
file path: C:\Windows\system32\drivers\usbport.sys
product: Besturingssysteem Microsoft® Windows®
company: Microsoft Corporation
description: Poortstuurprogramma voor USB 1.1 en 2.0
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
The 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.
On Thu 7-1-2010 12:50:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010710-16863-01.dmp
This was probably caused by the following module: unknown_module_fffff880`0181e0f0.sys (Unloaded_Unknown_Module_fffff880`0181e0f0+0x5225D5E)
Bugcheck code: 0xFE (0x5, 0xFFFFFA800442A1A0, 0x10DE077C, 0xFFFFFA8004F42C50)
Error: BUGCODE_USB_DRIVER
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
A 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: unknown_module_fffff880`0181e0f0.sys .
Google query: unknown_module_fffff880`0181e0f0.sys BUGCODE_USB_DRIVER
The following dump files were found but could not be read. These files may be corrupt:
C:\Windows\Minidump\060211-19718-01.dmp
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
On your computer a total of 17 crash dumps have been found. Only 16 could be analyzed. Only 15 are included in this report. 4 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
unknown_module_00000000`00000001.sys
unknown_module_fffff880`0181e0f0.sys
unknown
g?
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
