Also before the formating of my computer a lot of BSOD that other people had there were same as mine were linked to XP and Nvidia drives not playing nice.
System Information (local)
--------------------------------------------------------------------------------
computer name: CHRIS-8F370AB9F
windows version: Windows XP Service Pack 3, 5.1, build: 2600
windows dir: C:\WINDOWS
CPU: GenuineIntel Pentium® Dual-Core CPU E5400 @ 2.70GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 2146611200 total
VM: 2147352576, free: 2047414272
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Mon 10/15/2012 2:58:12 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini101512-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x2EBD1)
Bugcheck code: 0x10000050 (0xFFFFFFFFE31E001C, 0x0, 0xFFFFFFFFBF82EBD1, 0x1)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 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 Fri 10/12/2012 4:36:45 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini101212-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x2EBD1)
Bugcheck code: 0x10000050 (0xFFFFFFFFE53A401C, 0x0, 0xFFFFFFFFBF82EBD1, 0x1)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 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 10/11/2012 9:16:08 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini101112-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x1568C8)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFBF9568C8, 0xFFFFFFFFB28A8C00, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
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 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 10/10/2012 7:37:27 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini101012-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x2EBD1)
Bugcheck code: 0x10000050 (0xFFFFFFFFE3A5201C, 0x0, 0xFFFFFFFFBF82EBD1, 0x1)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 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 10/3/2012 1:49:57 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini100212-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x12501)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFBF812501, 0xFFFFFFFFB28F805C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
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 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 9/13/2012 6:34:11 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini091312-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x4C67E)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFBF84C67E, 0xFFFFFFFF9F9DBAE4, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
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 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 9/6/2012 11:09:58 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini090612-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x1568C8)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFBF9568C8, 0xFFFFFFFFA918AC00, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
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 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 Fri 8/31/2012 1:44:04 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini083012-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x12501)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFBF812501, 0xFFFFFFFFB1F0F33C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
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 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 7/18/2012 3:48:17 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini071712-01.dmp
This was probably caused by the following module: nv4_mini.sys (nv4_mini+0x3955)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFB69D7955, 0xFFFFFFFF8E3648E4, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\nv4_mini.sys
product: NVIDIA Windows XP Miniport Driver, Version 306.23
company: NVIDIA Corporation
description: NVIDIA Windows XP Miniport Driver, Version 306.23
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: nv4_mini.sys (NVIDIA Windows XP Miniport Driver, Version 306.23 , NVIDIA Corporation).
Google query: nv4_mini.sys NVIDIA Corporation KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Thu 7/12/2012 6:51:42 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini071212-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x12511)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFBF812511, 0xFFFFFFFFB31DAD1C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
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 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 Sat 7/7/2012 6:27:12 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini070712-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x155D8D)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFBF955D8D, 0xFFFFFFFFB2D17C00, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
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 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 6/27/2012 12:58:56 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini062612-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x155D8D)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFBF955D8D, 0xFFFFFFFFB2AD4C00, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
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 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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
12 crash dumps have been found and analyzed. A third party driver has 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:
nv4_mini.sys (NVIDIA Windows XP Miniport Driver, Version 306.23 , NVIDIA Corporation)
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.
Sign In
Create Account
