Jump to content

Welcome to Geeks to Go - Register now for FREE

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.

Create Account How it Works
Photo

BSOD in windows XP


  • Please log in to reply

#16
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
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 below
This 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 Next
Put a tick in the Don't create a start menu folder then click Next
Put a tick in Create a Desktop Icon then click on Install and make sure there is a tick in Launch Whocrashed before clicking Finish
Click Analyze
It will want to download the Debugger and install it Say Yes
WhoCrashed will create report but you have to scroll down to see it
Copy and paste it into your next reply

http://www.resplendence.com/downloads
  • 0

Advertisements


#17
cmislin

cmislin

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 384 posts
Had another blue screen when I got home . For some reason there isn't 2 different BSOD events when I look in the program to get the BSOD.txt files but uploaded another one that is updated.



Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.
Cleaning up minor inconsistencies on the drive.
Cleaning up 121 unused index entries from index $SII of file 0x9.
Cleaning up 121 unused index entries from index $SDH of file 0x9.
Cleaning up 121 unused security descriptors.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
Free space verification is complete.

312560608 KB total disk space.
157015264 KB in 177022 files.
69100 KB in 23678 indexes.
0 KB in bad sectors.
289308 KB in use by the system.
65536 KB occupied by the log file.
155186936 KB available on disk.

4096 bytes in each allocation unit.
78140152 total allocation units on disk.
38796734 allocation units available on disk.

Internal Info:
a0 18 03 00 08 10 03 00 50 ec 04 00 00 00 00 00 ........P.......
7c 60 00 00 04 00 00 00 6a 07 00 00 00 00 00 00 |`......j.......
0e 70 86 0f 00 00 00 00 d6 10 f9 6f 00 00 00 00 .p.........o....
62 3b a7 15 00 00 00 00 28 c8 47 47 08 00 00 00 b;......(.GG....
5a 4a 03 98 06 00 00 00 10 d7 14 7c 0f 00 00 00 ZJ.........|....
20 09 ef a0 00 00 00 00 e0 3b 07 00 7e b3 02 00 ........;..~...
00 00 00 00 00 80 73 6f 25 00 00 00 7e 5c 00 00 ......so%...~\..

Windows has finished checking your disk.
Please wait while your computer restarts.


For more information, see Help and Support Center at
  • 0

#18
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
WhoCrashed log from post 16?
  • 0

#19
cmislin

cmislin

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 384 posts
Not sure what your asking me?
  • 0

#20
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
In post 16 I requested you download, run and post a WhoCrashed report.
  • 0

#21
cmislin

cmislin

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 384 posts
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.
  • 0

#22
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
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.
  • 0

#23
cmislin

cmislin

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 384 posts
http://www.mediafire...xz57unvi2w7c77a

http://www.mediafire...tmngiuz8tk2t7wo
  • 0

#24
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
OK first two I need you to get in this order.

Intel N10/ICH7 Family Smbus Controller
Intel 4 Series Chipset Processor to I/O Controller


Download and install these two in the order above. Then tomorrow we will move on. Let me know between after installation and rebooting if there are any BSOD's between then and tomorrow.
  • 0

#25
cmislin

cmislin

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 384 posts
Installed those 2 as per your request in the order your stated. I was about to post this reply and another BSOD win32.sys error. Added the BSOD.txt for this recently BSOD.

Attached Files

  • Attached File  bsod.txt   2.03KB   25 downloads

  • 0

Advertisements


#26
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
OK we will get another two tomorrow. Let me ask is the OS disk original or is it a downloaded version?
  • 0

#27
cmislin

cmislin

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 384 posts

OK we will get another two tomorrow. Let me ask is the OS disk original or is it a downloaded version?

Original OS disc.
  • 0

#28
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
OK that is good to know as we may need it later. If all else fails we may try a repair on the OS but I'm thinking it is the drivers or something to do with the motherboard at this point.
  • 0

#29
cmislin

cmislin

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 384 posts
What will be the next 2 drivers to for tomorrow (I'm typically up late and can probably do it before bed)
  • 0

#30
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Get the first two on the same page as the last two.
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP