Can someone analyze my minidump file? Not a bsod.

[Chaoz]

My computer keeps freezing after coming out of sleep. I'm pretty sure it has something to do with the sound manager.

Thanks.

 

[MvdB]

This was a driver power state failure:

Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Sep 29 01:59:35.429 2011 (UTC + 2:00)
System Uptime: 0 days 0:35:40.427
Probably caused by : ntkrnlmp.exe ( nt!KiSwapContext+7a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x9F_4_nt!KiSwapContext+7a
Bugcheck code 1000009F
Arguments 00000000`00000004 00000000`00000258 fffffa80`045f0680 fffff800`00b9c510
BiosVersion = 1.0.18
BiosReleaseDate = 02/24/2009
SystemManufacturer = Dell Inc.
SystemProductName = Inspiron 530
MaxSpeed:     2400
CurrentSpeed: 2992

But, strangely, you are also "underclocking". Any ideas on that?

I'd start by checking your powerplan and advanced settings for problems or inconsistency in your energy settings. For more help, please follow the complete upload instructions http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

 

[zigzag3143]

Chaoz


The power transition timed out waiting to synchronize with the Pnp subsystem. It waited for 258 seconds hence your computer freeze.

To find out which driver I would run driver verifier

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).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

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 "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 (an estimate on my part).

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.

 

[Chaoz]

So if I get bsod before windows loads, should I just check each driver one at a time till a find out which one is causing it?

 

[Chaoz]

I narrowed it down to what's causing the bsod. Something called nltdi.sys. It's listed as unknown.

Turns out to be netlimiter. I've never had a problem with it before so that's weird. I uninstalled it so I'll see if that'll fix the problem.

 

[zigzag3143]

So if I get bsod before windows loads, should I just check each driver one at a time till a find out which one is causing it?

No you run driver verifier and leave it running. If a driver misbehaves it will trap it.