BSOD - driver power state failure

[onyxquark]

Hi,

I'm new to this forum but i hope you can help with BSOD issues on my windows 7 Laptop.

I have a HP HDX18 Laptop that is about 8months old. I bought it with Vista home premium and upgraded to windows 7 home premium when it was released. As soon as i upgraded i started having blue screen of death problems (BSOD) problems. The laptop became unusable as it would crash intermittantly. It turned out to be my anti-virus software, Zone Alarm and so i swapped to Kaspersky.

About two months ago the machine started running slowly, locking up and crashing. I wasn't able to complete any tasks, there didn't seem to be any system restore points and it was completely unusable and so i decided i would recover to factory condition (Vista) and start again. I have done this and reloaded Windows 7 update and normal windows software. I also upgraded again to windows 7 ultimate so i would have networking capability as my other computers are XP pro and a Mac and the networking function in Win 7 home premium is worse than useless.

This all completed successfully last week and within a few days i am again having problems. I cannot shutdown my laptop, it will hang (saying 'shutting down') for about five minutes and then BSOD. I have attached the minidumps files using the SF Diagnostic Tool from this forum.

I also cannot use any usb ports, backup and have trouble with some proprietory HP software.

First things first, i need to find out why i cannot shut down so hopefully someone can read these mini dump files and see what the problem might be.

Many thanks.

 

[zigzag3143]

Hi,

I'm new to this forum but i hope you can help with BSOD issues on my windows 7 Laptop.

I have a HP HDX18 Laptop that is about 8months old. I bought it with Vista home premium and upgraded to windows 7 home premium when it was released. As soon as i upgraded i started having blue screen of death problems (BSOD) problems. The laptop became unusable as it would crash intermittantly. It turned out to be my anti-virus software, Zone Alarm and so i swapped to Kaspersky.

About two months ago the machine started running slowly, locking up and crashing. I wasn't able to complete any tasks, there didn't seem to be any system restore points and it was completely unusable and so i decided i would recover to factory condition (Vista) and start again. I have done this and reloaded Windows 7 update and normal windows software. I also upgraded again to windows 7 ultimate so i would have networking capability as my other computers are XP pro and a Mac and the networking function in Win 7 home premium is worse than useless.

This all completed successfully last week and within a few days i am again having problems. I cannot shutdown my laptop, it will hang (saying 'shutting down') for about five minutes and then BSOD. I have attached the minidumps files using the SF Diagnostic Tool from this forum.

I also cannot use any usb ports, backup and have trouble with some proprietory HP software.

First things first, i need to find out why i cannot shut down so hopefully someone can read these mini dump files and see what the problem might be.

Many thanks.

Hi and welcome


Farily straight forward Memory_corruption. To test y our memory I would download a 3rd party app called memtestx886, burn it to cd, and run it for at least 7 passes.

BugCheck 1000009F, {4, 258, fffffa8003d02680, fffff80000b9c4d0}
Probably caused by : memory_corruption
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 1000009F, {4, 258, fffffa8003d01680, fffff80000b9c4d0}
Probably caused by : memory_corruption
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 1000009F, {4, 258, fffffa8003cf6680, fffff80000b9c4d0}
Probably caused by : memory_corruption
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 1000009F, {4, 258, fffffa8003ce7b60, fffff800043ff4d0}
Probably caused by : memory_corruption
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 1000009F, {4, 258, fffffa8003d00040, fffff800043ff4d0}
Probably caused by : memory_corruption
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 1000009F, {4, 258, fffffa8003ce5040, fffff80000b9c4d0}
Probably caused by : memory_corruption

 

[onyxquark]

Thanks for your reply... i found a 'pay for' application from www.memtest86.com is this what you mean?

 

[Tews]

There is the free version which is what we recommend... download the ISO and burn it as an image file, then boot your computer from it... let it run for at least 7 passes... let us know...

 

[onyxquark]

I was unable to find the application 'memtestx886' however i found one labelled 'memtest 86+' hopefully this does the same job.

I booted from 'memtest 86+' and left it running over night which ended up being 10 passes. There were 0 errors reported or found according to the log.

So far today i have not had any problems at all. I can shut down and restart without it hanging, all the USB ports work normally and everything seems reasonably 'crisp' and not sluggish.

If this was the solution, can someone explain to me what the memtest application actually does? I was under the impression that it was a diagnostic tool not a repair tool??

The only problem i have at the moment is that i cannot seem to back up to my NAS drive. It always says that 'the creation of a shadow copy timed out' and gives the error code '0x81000101'

Regardless i am happy to be able to use this machine again!

 

[onyxquark]

BSOD again!

After my backup did not complete, the back up program 'hung up' so i decided to restart and the shut down process once again hung up for more than five minutes and then BSOD.

I am attaching the mini dump files once again.

 

[usasma]

Well, that test most likely rules out problems with the memory (MemTest 86+ is a good memory test program also).

7 memory dumps from 8 to 13 June 2010 (6 days).
1 STOP error cited 7 times, with 1 cause blamed (memory corruption).
This is most likely a driver error (based on the type of STOP error and the consistency of the STOP error messages).

hpdskflt.sys is present in the stack text of several of the dump files (5 of 7). I've seen this driver causing BSOD errors several times before - so I suspect this program to be at fault.

It's a part of the HP Mobile Data Protection System Disk Filter

Please do the following:
- Visit the HP support website and download the latest available version of the HP Mobile Data Protection for your model and OS
- Uninstall the current version from your system
- Install the freshly downloaded version and watch for further BSOD's.

Summary of the BSOD's:

[FONT=lucida console]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 [COLOR=Red]hpdskflt.sys[/COLOR]
*** 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 [COLOR=Red]hpdskflt.sys[/COLOR]
*** 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 [COLOR=Red]hpdskflt.sys[/COLOR]
*** 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 [COLOR=Red]hpdskflt.sys[/COLOR]
*** 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 [COLOR=Red]hpdskflt.sys[/COLOR]
*** 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[/FONT]

 

[onyxquark]

Thanks...

I have looked for the HP Mobile Data Protection software but cannot spot it. Could it be that this is the HP 3D Drive Protection?

I am attaching a screenshot to show what HP software i have available to un/install.

 

[usasma]

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.

 

[onyxquark]

I have been struggling with this but currently to no avail....

If i change the hpdskflt.sys to hpdskflt.bak then re-install the sp45501.exe file (BTW this is the HP 3D Drive Guard), it will ask for a restart to finish the installation. The restart then fails to complete and asks to start 'launch startup repair', this then asks to do a system restore. This is the only path that will restart the system.

Once it has restarted, i cannot shut down again. In fact i cannot shut down anytime i have tried another process such as 'back up', or 'un/install'... starting these processes will mean that a shutdown will result in BSOD.

The only way to get the system to shut down properly is if i boot from the memtest 86+ disk (although this does not always go first time) and then restart again. This seems to reset the hang up error.

If i uninstall the 3D Drive Protection, restart, then change the hpdskflt.sys to .bak and then install 3D Protection (sp45501) it will ask for a restart.
A restart will fail and i will have to do a system restore to carry on.

If i look for hpdskflt.sys in the drivers file before i restart, it does not exist. The only file is the .bak that i changed.

I am attaching the minidump folder again incase there is anything new.

Any more suggestions? Thanks

 

[usasma]

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

 

[onyxquark]

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.

 

[usasma]

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

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

 

[usasma]

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:

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:

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

[FONT=lucida console]
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
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
  
  
 
[/FONT]

 

[onyxquark]

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.

 

[zigzag3143]

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

 

[zigzag3143]

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

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

 

[onyxquark]

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

 

[onyxquark]

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

 

[usasma]

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.