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

14 Jun 2010   #11
usasma
Microsoft MVP

 
 

How about changing the hpdskflt.sys to .bak, then reboot.
Then try to install SP45501 (this will ensure that the driver isn't loaded when trying to install the new one)?


My System SpecsSystem Spec
.
15 Jun 2010   #12
onyxquark

Windows 7
 
 

Quote   Quote: Originally Posted by usasma View Post
I dunno if that's it, but I've found the direct link to what you need to download: ftp://ftp.hp.com/pub/softpaq/sp45501/sp45501.exe (as with any direct link, scan it with your antivirus BEFORE opening).

Here's the web page for it: HP ProtectSmart Hard Drive Protection HP HDX X18-1320EA Premium Notebook PC - HP technical support (United Kingdom - English)
**********************************
Try this:
- go to C:\Windows\System32\drivers. Locate hpdskflt.sys and rename it to hpdskflt.BAK
- then install the file that was downloaded above.
- then check to see if it's created a new hpdskflt.sys file in the C:\Windows\System32\drivers directory.
If so, run the system and see if it gives any further BSOD's.
I don't think that the HP 3D drive protection (HP sp45501) is the problem program. I uninstalled it yesterday and have left this computer running for the most of the last 24hrs without using it. Randomly i have still had BSOD shut downs (mini dump files attached).
Also if the hpdskflt.sys file was part of this program, i would assume that it should be missing from the 'drivers' folder. It isn't.

When i rename hpdskflt.sys to .bak, i cannot restart the computer. It says that a system file is missing. The only way to restart is with a system restore.
My System SpecsSystem Spec
15 Jun 2010   #13
usasma
Microsoft MVP

 
 

The hpdskflt.sys program belongs to the ProtectSmart Hard Drive Protection program that I linked to earlier.
The presence in the stack text is significant. It is preceded by (presumably) user level information that isn't available to the debugger, and it is followed by the ntoskrnl.exe stuff relating to the crash.

But, the stack info isn't as clear as it usually is (IMO). Have you performed a hard drive diagnostic? If not, please follow the directions at this link on my website: HD Diagnostic (read the details at the link)

Here's the stack text from the latest crash (it's read from the bottom up):
Code:
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffff880`02fe7190 fffff800`02ed0752 : fffffa80`03cf5680 fffffa80`03cf5680 00000000`00000000 00000000`00000000 : nt!KiSwapContext+0x7a
fffff880`02fe72d0 fffff800`02ed28af : fffffa80`03d497d0 fffffa80`05542770 00000000`00000000 00000000`0000000c : nt!KiCommitThreadWait+0x1d2
fffff880`02fe7360 fffff880`01931b9b : 00000000`02fe7500 fffffa80`00000000 fffff880`02fe7400 00000000`00000700 : nt!KeWaitForSingleObject+0x19f
fffff880`02fe7400 00000000`02fe7500 : fffffa80`00000000 fffff880`02fe7400 00000000`00000700 fffff880`009ea180 : hpdskflt+0x2b9b
fffff880`02fe7408 fffffa80`00000000 : fffff880`02fe7400 00000000`00000700 fffff880`009ea180 fffff800`00000008 : 0x2fe7500
fffff880`02fe7410 fffff880`02fe7400 : 00000000`00000700 fffff880`009ea180 fffff800`00000008 00000000`00000000 : 0xfffffa80`00000000
fffff880`02fe7418 00000000`00000700 : fffff880`009ea180 fffff800`00000008 00000000`00000000 fffffa80`07692090 : 0xfffff880`02fe7400
fffff880`02fe7420 fffff880`009ea180 : fffff800`00000008 00000000`00000000 fffffa80`07692090 fffff880`02fe7460 : 0x700
fffff880`02fe7428 fffff800`00000008 : 00000000`00000000 fffffa80`07692090 fffff880`02fe7460 00000000`c0000000 : 0xfffff880`009ea180
fffff880`02fe7430 00000000`00000000 : fffffa80`07692090 fffff880`02fe7460 00000000`c0000000 fffff880`02fe7518 : 0xfffff800`00000008
My System SpecsSystem Spec
.

15 Jun 2010   #14
usasma
Microsoft MVP

 
 

Attached is a zipped copy of the hpdskflt.sys for 64 bit systems.
Please extract it to a location of your choosing (don't forget to scan for viruses!)
Then try renaming the one in C:\Windows\System32\drivers to hpdskflt.BAK(DON'T REBOOT)
Then put this one in there (Then reboot).

Also, please remove or update these older drivers that were loaded at the time of the crash. Don't use Windows Update or the Update drivers function of Device Manager.
Please use the following instructions to locate the most currently available drivers to replace the one's that you uninstall OR remove:
Quote:
How To Find Drivers:
- I have listed links to most of the drivers in the code box below. Please use the links there to see what info I've found about those 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: http://www.carrona.org/dvrref.html
- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html

Here's the older drivers. Please pay particular attention to any dated 2008 or earlier:
Code:
000.fcl      Fri Sep 26 09:11:22 2008 - CyberLink FCL Driver - http://www.carrona.org/dvrref.html#000.fcl
btwaudio.sys Tue May 13 00:10:36 2008 - Broadcom Bluetooth Audio Device - http://www.carrona.org/dvrref.html#btwaudio.sys
btwavdt.sys  Tue May 13 00:09:36 2008 - Broadcom Bluetooth AVDT Service - http://www.carrona.org/dvrref.html#btwavdt.sys
btwrchid.sys Tue May 13 00:10:53 2008 - Broadcom Bluetooth Remote Control HID Minidriver - http://www.carrona.org/dvrref.html#btwrchid.sys
enecir.sys   Thu Sep 04 05:47:58 2008 - ENE Consumer IR Driver for eHome - http://www.carrona.org/dvrref.html#enecir.sys
jmcr.sys     Mon Oct 20 05:31:04 2008 - JMicron JMB38X Memory Card Reader Driver - http://www.carrona.org/dvrref.html#jmcr.sys
nvhda64v.sys Wed Sep 24 20:09:38 2008 - nVidia HDMI Audio Device (nForce chipset driver) - http://www.carrona.org/dvrref.html#nvhda64v.sys
SynTP.sys    Thu Jul 17 20:28:21 2008 - Synaptic Touch Pad Driver - http://www.carrona.org/dvrref.html#SynTP.sys
BSOD BUGCHECK SUMMARY
Code:

Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jun 15 07:04:54.367 2010 (UTC - 4:00)
System Uptime: 0 days 0:35:31.302
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: Tue Jun 15 06:28:22.107 2010 (UTC - 4:00)
System Uptime: 0 days 0:35:32.042
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 05:51:49.466 2010 (UTC - 4:00)
System Uptime: 0 days 0:35:30.402
BugCheck 1000009F, {4, 258, fffffa8003cf6680, 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
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Jun 14 18:01:47.710 2010 (UTC - 4:00)
System Uptime: 0 days 0:38:00.645
BugCheck 1000009F, {4, 258, fffffa8003ce6680, fffff800043ff4d0}
*** 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: Mon Jun 14 16:58:54.428 2010 (UTC - 4:00)
System Uptime: 0 days 0:35:33.363
BugCheck 1000009F, {4, 258, fffffa8003cf4040, fffff800043ff4d0}
*** 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: Mon Jun 14 16:22:20.925 2010 (UTC - 4:00)
System Uptime: 0 days 0:35:31.860
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: Mon Jun 14 15:45:45.402 2010 (UTC - 4:00)
System Uptime: 0 days 1:20:18.337
BugCheck 1000009F, {4, 258, fffffa8003ce5680, 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: Mon Jun 14 14:08:17.618 2010 (UTC - 4:00)
System Uptime: 0 days 6:06:55.553
BugCheck 1000009F, {4, 258, fffffa8003ce6680, 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: Mon Jun 14 07:21:40.195 2010 (UTC - 4:00)
System Uptime: 0 days 0:45:32.130
BugCheck 1000009F, {4, 258, fffffa8003d00680, 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: Mon Jun 14 06:35:33.769 2010 (UTC - 4:00)
System Uptime: 0 days 0:39:25.704
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: Sun Jun 13 10:08:42.941 2010 (UTC - 4:00)
System Uptime: 0 days 1:07:38.819
BugCheck 1000009F, {4, 258, fffffa8003ce5680, 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 12 09:19:06.617 2010 (UTC - 4:00)
System Uptime: 0 days 0:46:53.552
BugCheck 1000009F, {4, 258, fffffa8003d02680, 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 10 18:51:47.215 2010 (UTC - 4:00)
System Uptime: 0 days 1:01:43.151
BugCheck 1000009F, {4, 258, fffffa8003d01680, 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 10 05:47:25.162 2010 (UTC - 4:00)
System Uptime: 0 days 0:20:29.097
BugCheck 1000009F, {4, 258, fffffa8003cf6680, 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 10 05:25:53.963 2010 (UTC - 4:00)
System Uptime: 0 days 0:20:27.898
BugCheck 1000009F, {4, 258, fffffa8003ce7b60, fffff800043ff4d0}
*** 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  8 19:12:17.250 2010 (UTC - 4:00)
System Uptime: 0 days 0:25:51.185
BugCheck 1000009F, {4, 258, fffffa8003d00040, fffff800043ff4d0}
*** 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  8 18:45:45.571 2010 (UTC - 4:00)
System Uptime: 0 days 2:50:44.506
BugCheck 1000009F, {4, 258, fffffa8003ce5040, 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
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
  
  
 
My System SpecsSystem Spec
17 Jun 2010   #15
onyxquark

Windows 7
 
 

Unfortunately i have not managed to achieve any of the tasks that you have specified except for installing the hpdskflt.sys file that you attached which has not made any difference.

When i download and burn a bootable disk from Seatools (SeaToolsDOS220ALL.576 is the DOS download file), i do not manage to get any more than a flashing '_' when i boot from the disk. I have tried it as many ways as i can think and still it does not launch any Hard Drive diagnostic program.

I still have this major problem that whenever a system function starts, i am not able to restart the computer. It always hangs up on the shutdown. The only way to manage a restart is to boot from the 'memtest 86+' disk and then restart.

I have attempted to download the drivers from the manufacturers websites but i cannot associate the driver name with what is in the manufacturers website lists. One that i downloaded was for the Broadcom Wireless Technology however i have twice tried to uninstall the existing driver and both times it has sat 'Uninstalling' indefinately (+ 15mins). Then i am not able to cancel the process and the only way to stop it is to crash the system. I have tried running this application without uninstalling and the process always stops and says that it cannot find bluetooth hardware.

Why does Microsoft include all of the functionality such as 'update driver', 'windows will check for a solution', etc and i have 'Never' seen that they will locate a solution or that the functionality will work?? I find it very misleading and pointless but every new OS gets more of this and more administrator rights hurdles to navigate around???

I know this doesn't help you to suggest any solutions but hopefully you might have something to suggest based on the fact that i have not been able to get things to run?

Windows 7 seems to be more inherently unstable than previous versions because it BSOD's whenever there is something that it doesn't like. I honestly thought that it would be a bit more robust but the OS gets more involved and you have to be as skilled as someone like yourself just to use it for everyday applications. As you can guess i am very frustrated with Windows 7 ever since i upgraded and i just want a working computer... My XP Pro isn't perfect but at least i can use it...!

I'm attaching the latest minidump files again.
My System SpecsSystem Spec
17 Jun 2010   #16
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by onyxquark View Post
Unfortunately i have not managed to achieve any of the tasks that you have specified except for installing the hpdskflt.sys file that you attached which has not made any difference.

When i download and burn a bootable disk from Seatools (SeaToolsDOS220ALL.576 is the DOS download file), i do not manage to get any more than a flashing '_' when i boot from the disk. I have tried it as many ways as i can think and still it does not launch any Hard Drive diagnostic program.

I still have this major problem that whenever a system function starts, i am not able to restart the computer. It always hangs up on the shutdown. The only way to manage a restart is to boot from the 'memtest 86+' disk and then restart.

I have attempted to download the drivers from the manufacturers websites but i cannot associate the driver name with what is in the manufacturers website lists. One that i downloaded was for the Broadcom Wireless Technology however i have twice tried to uninstall the existing driver and both times it has sat 'Uninstalling' indefinately (+ 15mins). Then i am not able to cancel the process and the only way to stop it is to crash the system. I have tried running this application without uninstalling and the process always stops and says that it cannot find bluetooth hardware.

Why does Microsoft include all of the functionality such as 'update driver', 'windows will check for a solution', etc and i have 'Never' seen that they will locate a solution or that the functionality will work?? I find it very misleading and pointless but every new OS gets more of this and more administrator rights hurdles to navigate around???

I know this doesn't help you to suggest any solutions but hopefully you might have something to suggest based on the fact that i have not been able to get things to run?

Windows 7 seems to be more inherently unstable than previous versions because it BSOD's whenever there is something that it doesn't like. I honestly thought that it would be a bit more robust but the OS gets more involved and you have to be as skilled as someone like yourself just to use it for everyday applications. As you can guess i am very frustrated with Windows 7 ever since i upgraded and i just want a working computer... My XP Pro isn't perfect but at least i can use it...!

I'm attaching the latest minidump files again.

Twenty seven DMP's will take quite a while. Running them now
My System SpecsSystem Spec
17 Jun 2010   #17
zigzag3143

Win 8 Release candidate 8400
 
 

Well these were almost all caused by memory corruption. They are virtually identical

I would download a 3rd party app called memtestx86, burn it to cd, and run it for at least 7 passes to test your memory.


Let us know if you need help

Ken

Code:
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Jun 17 09:30:33.220 2010 (GMT-4)
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 (GMT-4)
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 (GMT-4)
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 (GMT-4)
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 (GMT-4)
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 (GMT-4)
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
My System SpecsSystem Spec
17 Jun 2010   #18
onyxquark

Windows 7
 
 

Thanks...

BTW, i have a disk of updated drivers that HP issued with the Windows 7 upgrade. I have also tried to run this again... it seems to say that my drivers are all uptodate as far as the disk is concerned but once again when it asks to restart, the system hangs up.

If i try to back up, the back up fails and the system hangs up on a restart....

If i try to to uninstall drivers then it hangs up on a restart...
My System SpecsSystem Spec
17 Jun 2010   #19
onyxquark

Windows 7
 
 

Just got your message about the memory corruption.

If you see at the begining of the post, i downloaded memtest86+ (i couldn't find memtes886 on google) and i ran it over night which turned out to be 10 passes. I had 0 errors listed....
My System SpecsSystem Spec
17 Jun 2010   #20
usasma
Microsoft MVP

 
 

There is something major wrong with your system.
I would suggest that you backup your data, wipe your hard drive with a free program such as DBAN or KillDisk, and then reinstall Windows Vista from the HP recovery DVD's

If that runs fine without any problems - then try the upgrade to Win7 by wiping the hard drive again and installing the Win7 disk "clean".

This will help to rule out any Windows corruptions - either with the Vista install or the Win7 install
If the problems still occur, then this will point to a hardware problem.

Since you've fixed the hpdskflt.sys file and are still getting BSOD's, this is most likely a hardware issue.
The hard drive is the most likely culprit IMO - but the hard disk controller on the motherboard is very much in the running also.

I can't recall if you're run any sort of hard drive diagnostic (even HDTune is better than nothing) - but that is recommended to rule out the hard drive (which would then implicate the controller).

If you can't get any hard drive test to run, then the next thing would be to try another hard drive. They're about $60 US and are very easy to install:
- remove battery
- remove AC adapter plug
- open hard drive bay
- pull on plastic tab to remove drive
- unscrew 4 screws holding hard drive to housing
- remove hard drive.

Reverse the procedure to put the new HDD in.
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 10:51.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App