Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD - driver power state failure

17 Jun 2010   #21
Jonathan_King

Windows 7 Professional x64
 
 

If I may insert something before usasma's advice, please remove Kaspersky: http://support.kaspersky.com/downloa...vremover10.zip

Replace with MSE: http://www.microsoft.com/security_essentials

Kaspersky causes its fair share of BSODs. Might be quicker than reinstalling. Follow usasma's advice if it doesn't work.


My System SpecsSystem Spec
.
20 Jun 2010   #22
onyxquark

Windows 7
 
 

Quote   Quote: Originally Posted by Jonathan_King View Post
If I may insert something before usasma's advice, please remove Kaspersky: http://support.kaspersky.com/downloa...vremover10.zip

Replace with MSE: http://www.microsoft.com/security_essentials

Kaspersky causes its fair share of BSODs. Might be quicker than reinstalling. Follow usasma's advice if it doesn't work.
Thanks for this tip. I was about to reformat and start again when i got your post.

So far i have done the following.
1. Removed Kaspersky
2. Installed MSE
3. Managed to run the propriatory 'Seatools for Windows' Hard drive diagnostic tool
4. Run all of the SeaTools tests and all tests have been error free.
5. I also ran HD Tune and all tests were error free

Everything seems alot more stable and i have had not as many BSOD's but the following problems remain.

1. I cannot 'back up'. Everytime i try it fails and a message says that it has failed while trying to create a system image. Any suggestions?
2. I still have had a few BSOD's. I am attaching them again to see if they are the same as before. If they are, would you still recommend erasing everything and reloading everything (bearing in mind i still cannot back up).

Thanks.
My System SpecsSystem Spec
20 Jun 2010   #23
usasma
Microsoft MVP

 
 

Well, it's still spitting out memory corruption/hpdskflt.sys errors - so it's most likely a hardware problem (although a Windows issue is also possible).

I'd first suggest running these free, diagnostics:
Quote:
H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link) - If you've run this already, please feel free to skip it this time.
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)

Then, if the above tests pass, I'd try these free stress tests:
Quote:
FurMark download site: FurMark: Graphics Card Stability and Stress Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit
Quote:
Prime95 download site: Free Software - GIMPS
Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead.
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
This won't necessarily crash the system - but check the output in the test window for errors.
The Test selection box and the stress.txt file describes what components that the program stresses.
If all of that passes, then I'd try a fresh install of Windows (can't recall if you've done this already or not).
If the error recurs after reinstalling Windows - then I'd have to suspect that it's either an issue with the motherboard or the hard drive.

The hard drive is cheaper to replace but (IMO) is less likely to be at fault. The motherboard replacement will cost enough (when time and labor installing it is figured in) that a replacement (new) laptop will be a very tempting thing.

BSOD BUGCHECK SUMMARY
Code:

Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jun 19 20:00:29.649 2010 (UTC - 4:00)
System Uptime: 0 days 6:14:32.444
BugCheck 1000009F, {4, 258, fffffa8003cf5680, fffff80000b9c4d0}
*** WARNING: Unable to verify timestamp for hpdskflt.sys
*** ERROR: Module load completed but symbols could not be loaded for hpdskflt.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jun 19 13:44:56.984 2010 (UTC - 4:00)
System Uptime: 0 days 5:05:22.919
BugCheck 1000009F, {4, 258, fffffa8003cf3b60, fffff800043f74d0}
*** WARNING: Unable to verify timestamp for hpdskflt.sys
*** ERROR: Module load completed but symbols could not be loaded for hpdskflt.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jun 19 08:38:34.952 2010 (UTC - 4:00)
System Uptime: 0 days 0:57:08.888
BugCheck 1000009F, {4, 258, fffffa8003ce4b60, fffff80000b9c4d0}
*** WARNING: Unable to verify timestamp for hpdskflt.sys
*** ERROR: Module load completed but symbols could not be loaded for hpdskflt.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Jun 17 16:06:51.464 2010 (UTC - 4:00)
System Uptime: 0 days 0:35:31.399
BugCheck 1000009F, {4, 258, fffffa8003cf3b60, fffff800044054d0}
*** WARNING: Unable to verify timestamp for hpdskflt.sys
*** ERROR: Module load completed but symbols could not be loaded for hpdskflt.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Jun 17 15:30:11.561 2010 (UTC - 4:00)
System Uptime: 0 days 2:00:42.496
BugCheck 1000009F, {4, 258, fffffa8003ce5680, fffff80000b9c4d0}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Jun 17 09:30:33.220 2010 (UTC - 4:00)
System Uptime: 0 days 0:48:43.155
BugCheck 1000009F, {4, 258, fffffa8003ce6040, fffff80000b9c4d0}
*** WARNING: Unable to verify timestamp for hpdskflt.sys
*** ERROR: Module load completed but symbols could not be loaded for hpdskflt.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Jun 16 07:26:17.079 2010 (UTC - 4:00)
System Uptime: 0 days 0:35:30.874
BugCheck 1000009F, {4, 258, fffffa8003cf4b60, fffff80000b9c4d0}
*** WARNING: Unable to verify timestamp for hpdskflt.sys
*** ERROR: Module load completed but symbols could not be loaded for hpdskflt.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Jun 16 06:49:46.032 2010 (UTC - 4:00)
System Uptime: 0 days 0:35:30.968
BugCheck 1000009F, {4, 258, fffffa8003cf4680, fffff80000b9c4d0}
*** WARNING: Unable to verify timestamp for hpdskflt.sys
*** ERROR: Module load completed but symbols could not be loaded for hpdskflt.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Jun 16 06:13:13.922 2010 (UTC - 4:00)
System Uptime: 0 days 0:35:30.857
BugCheck 1000009F, {4, 258, fffffa8003cf4b60, fffff80000b9c4d0}
*** WARNING: Unable to verify timestamp for hpdskflt.sys
*** ERROR: Module load completed but symbols could not be loaded for hpdskflt.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Jun 16 05:36:43.240 2010 (UTC - 4:00)
System Uptime: 0 days 0:35:32.035
BugCheck 1000009F, {4, 258, fffffa8003cf4680, fffff80000b9c4d0}
*** WARNING: Unable to verify timestamp for hpdskflt.sys
*** ERROR: Module load completed but symbols could not be loaded for hpdskflt.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Jun 16 05:00:03.966 2010 (UTC - 4:00)
System Uptime: 0 days 0:45:42.901
BugCheck 1000009F, {4, 258, fffffa8003d01680, fffff800044054d0}
*** WARNING: Unable to verify timestamp for hpdskflt.sys
*** ERROR: Module load completed but symbols could not be loaded for hpdskflt.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jun 15 17:17:46.264 2010 (UTC - 4:00)
System Uptime: 0 days 0:35:30.199
BugCheck 1000009F, {4, 258, fffffa8003cf5040, fffff80000b9c4d0}
*** WARNING: Unable to verify timestamp for hpdskflt.sys
*** ERROR: Module load completed but symbols could not be loaded for hpdskflt.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jun 15 13:22:58.418 2010 (UTC - 4:00)
System Uptime: 0 days 2:24:26.353
BugCheck 1000009F, {4, 258, fffffa8003ce5040, fffff80000b9c4d0}
*** WARNING: Unable to verify timestamp for hpdskflt.sys
*** ERROR: Module load completed but symbols could not be loaded for hpdskflt.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jun 15 05:15:17.764 2010 (UTC - 4:00)
System Uptime: 0 days 1:00:43.699
BugCheck 1000009F, {4, 258, fffffa8003ce6040, fffff80000b9c4d0}
*** WARNING: Unable to verify timestamp for hpdskflt.sys
*** ERROR: Module load completed but symbols could not be loaded for hpdskflt.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
  
  
 
My System SpecsSystem Spec
.

29 Jun 2010   #24
onyxquark

Windows 7
 
 

I ran all of the tests that were suggested and everything came back with no errors.

I recovered to factory settings (Vista) and then did a clean install of windows 7 (not upgrade). Apart from some of the audio control drivers not working correctly (still don't) everything else seemed to load fine.

I have been running the system for nearly a week now and had no problems until today when Microsoft Outlook 2007 fails on opening each time. I'm not sure why these things happen and not sure if it is related to anything else. The microsoft help files that i can find on this matter just say to restart the system, unfortunately this does not change anything nor does 'repairing' from the un/install page.

If this Outlook problem is unrelated, i would say that my original issues were down to two things.
1. Kaspersky's (and Zone Alarm previously)
2. Upgrading to Windows 7 and not doing a clean install (although this looses drivers)

Currently i have not had a BSOD for 1 week.

Any suggestions on Outlook? the message that appears after the Outlook windows launches for a spilt second and then dissappears is 'Cannot start Microsoft Office Outlook. Cannot open the Outlook window'
My System SpecsSystem Spec
30 Jun 2010   #25
usasma
Microsoft MVP

 
 

Check Device Manager to make sure that you have all your devices properly detected and installed.

Then uninstall Outlook, reinstall it, then get all the Windows/Microsoft Updates that apply to it.
My System SpecsSystem Spec
28 Jul 2010   #26
onyxquark

Windows 7
 
 

Just a quick update.

Everything seems to be working well now... so for others, the solutions seem to be

Don't upgrade, fresh install windows 7
Don't use any other anti virus apart from MSE

Thanks for the help on this forum.
My System SpecsSystem Spec
28 Jul 2010   #27
Jonathan_King

Windows 7 Professional x64
 
 

Thanks for the report. Glad it's all sorted out.
My System SpecsSystem Spec
28 Jul 2010   #28
CarlTR6

Windows 7 Ultimate 32 bit
 
 

Good report. I am glad you are up and running smoothly.
My System SpecsSystem Spec
28 Jul 2010   #29
Tews

64-bit Windows 8.1 Pro
 
 

Glad its all sorted!
My System SpecsSystem Spec
Reply

 BSOD - driver power state failure




Thread Tools




Similar help and support threads
Thread Forum
BSOD Driver power state failure
Hi, My laptop has been having the following issue: Sometimes when I put my laptop into hibernate it experiences a blue screen of death and states that the problem is due to a driver power failure. I have a: Dell 1745 500GB HDD
BSOD Help and Support
BSOD Driver power State Failure
Hi my Dell Inspiron N5110 laptop has been having the BSOD issues, these days if I shut the lid down, the laptop does not hibernate, even though the power settings are such. I have got the blue screen a number of times, I have also restored the laptop to an earlier restore point, but it has not...
BSOD Help and Support
BSOD Driver State Power Failure
Intermittently I get this blue screen. The latest crash occurred as I was typing so i don't think it has anything to do with sleep mode as someone suggested. I have not installed anything lately other than adobe photoshop and lightroom updates. Any help would be appreciated.
BSOD Help and Support
BSOD Driver power state failure
I am having this BSOD since 14 days , my laptop HP dv6 6165 tx is new and a month old and i play games on it for almost 2-3 hours daily it has OEM windows 7 64 bit installed on it. I have attched the mini dump report files and the perform/report files in the attched file zip folder ,please help...
BSOD Help and Support
BSOD Driver Power State Failure...Please Help
Hello, this is my first time posting, so I hope I have met all the requirements. I have ran into the ole' BSOD caused by a driver power state failure. Just to bring you up to speed with what I have done thus far...I started with a system recovery after making a second copy of discs, thanks to...
BSOD Help and Support
Driver power state failure BSOD
I updated my HP Pavilion from Vista to Win 7 and since then have experienced a Driver Power State failure crash on a regular basis. System Specs are: 3 GB Ram, 32 OS, Intel Quad Core 2.3 ghz I have hopefully attached the dump files that will help in diagnosing the problem. Any help...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

й Designer Media Ltd

All times are GMT -5. The time now is 07:30.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App