Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

BSOD in windows XP

rshaffer61

Posted 15 October 2012 - 10:07 AM

OK what other steps have you done before this so I don't duplicate any?I would like to check the drivers to see if that is what is causing this.

Download WhoCrashed from the link in my signature belowThis program checks for any drivers which may have been causing your computer to crash....

Click on the file you just downloaded and run it.

Put a tick in Accept then click on NextPut a tick in the Don't create a start menu folder then click NextPut a tick in Create a Desktop Icon then click on Install and make sure there is a tick in Launch Whocrashed before clicking FinishClick AnalyzeIt will want to download the Debugger and install it Say YesWhoCrashed will create report but you have to scroll down to see itCopy and paste it into your next reply

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.

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:

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.

rshaffer61

Posted 15 October 2012 - 02:57 PM

OK I think I got it now. It is a nvidia driver but not your video card. It seems to be one of the chipsets on the motherboard so I want to take a step to see if the drivers are out of date now.

Download DriverMax and have it scan your system. It will open their website with all the out of date drivers you can update. With the free version you can update only 2 drivers per day so if you have a lot of them it will take a few days to get everything updated. I have been using it for about 4 months now and like it better then any other utility out there for keeping my drivers up to date.If you want you can post screenshots of all the drivers in the list that need to be updated and I will suggest in what order to get them.