BSOD only when idle

[elkon3]

This has been with me for a long time (can't remember how long) must have been about 2 years now. Just decided to try to solve it.

When I'm using the computer, everything is fine. My video card is pretty old. When playing some games, sometimes the game crashes (and I get a notification about how my graphics sucks), but no BSOD. I haven't really exhaustively tested, but I think I've used it for 10 hours straight without any problems. The problem comes when I leave it alone (10-30 minutes.. I haven't seen it alive beyond 30 minutes of idle), even if its downloading something or running an antivirus scan. I have been able to run a full scan at startup (before windows loads), which took about an hour, with no problems.

I used windows update to install all the latest updates (from windows).

I have hibernate disabled and no screensavers, no standby after x minutes/hours. I do sometimes put it to sleep from time to time and there are usually no problems.

I took a look at the files and the event viewer and decided it must be a problem with the hdd, tried to do the hard drive self test from the bios, it got stuck at 90% and stayed there for over 12 hours then I killed it. chkdsk seems to think the harddrive is fine although I haven't tried running it with the -f option. A memory diagnostics test (through windows) was happy with the memory

I tried leaving it on on safe mode, and it has been on for about 4 hours now (I'll leave it overnight). That is what made me think there must be *some* driver that is problematic, and that it is not directly the hdd or memory that are the culprits here as the event viewer / files attached seem to show

Laptop is HP Pavilion dv1660ca
Is Windows 7 . . .
- x86 (32-bit)
- Original OS was Windows XP.
- Full retail (kinda).. got it from university

- Bought it on October 2006
- OS installation was in july 2009

the perfmon report is in the zip file.

Some useful information from the event viewer:
After the BSOD, there is a "critical" event that is created in the event viewer (after the restart)
Event 41, Kernel Power
BugcheckCode 122
BugcheckParameter1 0xc0450218
BugcheckParameter2 0xc000009d
BugcheckParameter3 0x97608c0
BugcheckParameter4 0x81043000
SleepInProgress false
PowerButtonTimeStamp 0

Sometimes BugcheckParameter2 is 0xc000000e

there are literally hundreds of these that I've collected

 

[zigzag3143]

You have old drivers from as far back as 2004 and they are contributing.
These crashes were caused by memory corruption/exception (c0000005) probably a driver.
Please run these two tests to verify your memory and find which driver is causing the problem.

* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have raid update its Driver.



Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



Driver verifier

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Old drivers needing updating.

mdmxsdk.sys    3/17/2004 3:04:10 PM       
HSF_CNXT.sys    8/22/2005 7:06:09 PM        
HSFHWAZL.sys    8/22/2005 7:06:13 PM      
HSF_DPV.sys    8/22/2005 7:06:56 PM        
CHDAud.sys    4/18/2006 2:29:04 PM       
rixdptsk.sys    11/14/2006 9:35:19 PM       
rimsptsk.sys    11/14/2006 11:42:45 PM        
rimmptsk.sys    11/15/2006 4:16:23 AM       
HpqKbFiltr.sys    6/18/2007 6:12:03 PM       
SynTP.sys    9/14/2007 10:10:35 PM        
e100b325.sys    11/16/2007 2:53:32 PM        
hamachi.sys    2/19/2009 6:36:27 AM        
netw5v32.sys    3/26/2009 12:10:37 PM

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads



Finally and important

Please remove any CD visualization programs such as Daemon Tools and Alcohol 120%.

They use a driver, found in your dmp, called sptd.sys, that is notorious for causing BSODs.

Use this SPTD uninstaller DuplexSecure - Downloads DuplexSecure - FAQ

when you're done you can use this Freeware:

MagicISO Virtual CD/DVD-ROM (MagicDisc) in its place

Using MagicISO to create ISO image files

 

[elkon3]

Thanks for the useful info. By the way, how do you extract that driver information from the zip file? I installed windows debugger and I'm able to check dump files...

Some of the drivers are not available from the part manufacturer and I can only get them from hp. hp made only vista drivers. OK anyway?

In the mean time, I think I'll give that verifier a try

 

[zigzag3143]

Thanks for the useful info. By the way, how do you extract that driver information from the zip file? I installed windows debugger and I'm able to check dump files...

They are extracted from the DMP file in WIN DBG by running the relevant modules,

Some of the drivers are not available from the part manufacturer and I can only get them from hp. hp made only vista drivers. OK anyway?

If Vista driver install in compatibility mode.

In the mean time, I think I'll give that verifier a try

Let us know if you need help.

 

[elkon3]

dumpfiles after using verifier and bsod

 

[elkon3]

oh. i got timed out .. last msg went through but no attachment.. here it is this time

(and i cant add an attachment when editing a post..?)

 

[zigzag3143]

oh. i got timed out .. last msg went through but no attachment.. here it is this time

(and i cant add an attachment when editing a post..?)

Related to memory corruption. Did you run memtest? what were the results?

None of these were driver verified.

The is a problem with the HD. Please run chkdsk

http://www.sevenforums.com/tutorials/433-disk-check.html


many many old drivers needing update.

mdmxsdk.sys    3/17/2004 3:04:10 PM        0xc3bf8000    0xc3bfae40    0x00002e40    0x4058a12a                        
HSF_CNXT.sys    8/22/2005 7:06:09 PM        0xc3b3b000    0xc3bea680    0x000af680    0x430a5a61                        
HSFHWAZL.sys    8/22/2005 7:06:13 PM        0xb0f3c000    0xb0f6d380    0x00031380    0x430a5a65                        
HSF_DPV.sys    8/22/2005 7:06:56 PM        0xc3a3e000    0xc3b3ab00    0x000fcb00    0x430a5a90                        
rixdptsk.sys    11/14/2006 9:35:19 PM        0x92332000    0x92383000    0x00051000    0x455a6ed7                        
rimsptsk.sys    11/14/2006 11:42:45 PM        0x9231e000    0x92332000    0x00014000    0x455a8cb5                        
rimmptsk.sys    11/15/2006 4:16:23 AM        0x92310000    0x9231e000    0x0000e000    0x455accd7                        
HpqKbFiltr.sys    6/18/2007 6:12:03 PM        0x9239b000    0x9239f180    0x00004180    0x46770333                        
SynTP.sys    9/14/2007 10:10:35 PM        0x923ad000    0x923da180    0x0002d180    0x46eb3f1b                        
e100b325.sys    11/16/2007 2:53:32 PM        0x922a3000    0x922c9c00    0x00026c00    0x473de72c                        
hamachi.sys    2/19/2009 6:36:27 AM        0x923f7000    0x923fbc00    0x00004c00    0x499d362b                        
netw5v32.sys    3/26/2009 12:10:37 PM        0x91e2b000    0x9223e000    0x00413000    0x49cba8fd

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

 

[elkon3]

Memtest didnt find any errors.
I ran chkdsk with all the options, it didn't find anything to fix.
For some of these drivers (example hamachi).. they are part of a program. I uninstalled the program but the driver is still lurking around. I know there are programs there that deal with such issues but they mainly work with graphics drivers... Anyone know a more general solution?

 

[writhziden]

Which drivers are you having trouble removing?

 

[elkon3]

With all the tools telling me nothing is wrong with the hdd/memory, I got fed up trying to update all these drivers and get rid of unwanted ones, so I just installed a new windows 7... not really a "clean" install, I shrunk a partition to make a new one and installed it on the new partition, that way I don't need to worry about backing up data (unless I run out of space, I'd then want to git rid of the extra junk)

So far, working fine. I'll try to "test" it for the next couple of days, if no more bsod I'll mark this solved.

By the way, I thought of trying out Windows 8 (an a yet another partition), worked fine except it didn't like the Conexant audio drivers (its actually a vista driver which works fine on Windows 7)

 

[writhziden]

I understand your frustration. Post back in a few days whether the system is responding well, and best wishes it is resolved.

 

[elkon3]

nope. bsod again :S

 

[elkon3]

I'm currently installing windows xp. if it works then I know theres some compatibility issues for some drivers vs windows 7. if it doesnt then ill probably go get a new hdd

 

[writhziden]

Sounds like a good step.

May I ask why a new hard drive?

Let us know if you need any further help. Best of luck!