BSOD - random - always Driver Power State Failure

[curtisrb15]

I've got randomly occouring BSODs on my Dell XPS 9000. The BSOD is always a driver power state failure. Log files attached.

My system is ~3 years old. Running a 2 year old Win 7 Ultimate x64 image.

Please help.

Thanks!

 

[zigzag3143]

Might have something to do with the fact that your uptime (time since last reboot) was almost 6 days.

The slightest memory leak, etc will magnify over that time.

 

[curtisrb15]

uptime not 6 days

I had a BSOD yesterday evening. No way my uptime is 6 days.

 

[zigzag3143]

I had a BSOD yesterday evening. No way my uptime is 6 days.

While your machine may have BSOD'ed yesterday but the only DMP you uploaded was from Feb 27, and the uptime is highlighted in the snip.

 

[curtisrb15]

newer log file?

I thought I followed the instructions for posting BSOD log files. Help me out. How do I find/get/output a newer DMP file?

 

[zigzag3143]

I thought I followed the instructions for posting BSOD log files. Help me out. How do I find/get/output a newer DMP file?

We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

If you are overclocking STOP

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

 

[curtisrb15]

Good info. I had to update the settings for writing the debugging info. I'll reboot and post the minidump folder contents next time it BOSDs. I guess it could be a few days given that it doesn't BSOD every day.

Thanks for the help.

 

[zigzag3143]

Good info. I had to update the settings for writing the debugging info. I'll reboot and post the minidump folder contents next time it BOSDs. I guess it could be a few days given that it doesn't BSOD every day.

Thanks for the help.

Sounds like a plan.

 

[curtisrb15]

sooner than I thought

just had a BSOD. Happened sooner that I thought it would. DMP file attached.

Not overclocking by the way.

 

[zigzag3143]

just had a BSOD. Happened sooner that I thought it would. DMP file attached.

Not overclocking by the way.

Related to Your HD or controller. Please run chkdsk.


A- CHKDSK /R /F:

Run CHKDSK /R /F from an elevated (Run as administrator) Command Prompt.

Do this for each hard drive on your system.

When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter.

Then reboot and let the test run.

It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors.

See "CHKDSK LogFile" below in order to check the results of the test.

B- Elevated Command Prompt:

Go to Start and type in "cmd.exe" (without the quotes)

At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"

C-CHKDSK LogFile:

Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter

Expand the Windows logs heading, then select the Application log file entry.

Double click on the Source column header.

Scroll down the list until you find the Chkdsk entry (wininit for Win7) (winlogon for XP).

Copy/paste the results into your next post.

 

[curtisrb15]

Thanks. I'll do the checking and report back. One question though.... From the command prompt how do know which disk it is checking and how do I tell it to run CHKDSK on a certain drive?

 

[zigzag3143]

Thanks. I'll do the checking and report back. One question though.... From the command prompt how do know which disk it is checking and how do I tell it to run CHKDSK on a certain drive?

From cmd you can just type (for example) C: enter and that will leave you at a "C:\" prompt. If you run chkdsk from there you will be checking "C"

Same for all the others.

 

[curtisrb15]

another BSOD

I haven't had time to run the CHKDSK yet. But when I got up this morning I had another BSOD. DMP is attached. Can you check this one and let me know if it is the same thing (HDD controller) or something new?

Thanks.

 

[zigzag3143]

I haven't had time to run the CHKDSK yet. But when I got up this morning I had another BSOD. DMP is attached. Can you check this one and let me know if it is the same thing (HDD controller) or something new?

Thanks.

Probably caused by : disk.sys