Vista - driver power state failure

It seems this is a pretty common occurance lately. 2 Days ago I updated my Vista Home Premium with SP2 and since then it has been crash after crash.. Right now I am lucky if I can go an hour before a crash. It started 5 minutes after installing sp2 with the error message Bugcode_USB_Driver and a bunch of numbers, I got online direct with microsoft and allowed them access to my computer and they deleted all drivers and reinstalled and updated..etc.etc.
After that I was good for about 6 hours then I started crashing with the Driver_Power_State failure. I have not installed any other new hardware or software.
My Specs are: HP Pavillion TX1000US 2GB ram...not sure what else u need.
This is making me crazy....This is the 3rd time I tried to post but my system freezes up.. Everytime it is going to crash my mouse and keyboard lock up, both are wireless devices.
I have tried to zip my 21 minidump files but no matter what I do it is always empty.

Please help... this is the first time I have ever posted anything and I hope I am in the right place...

mch

do you have a backup to restore from ?

If not can you un-install SP2?

dump files. Are they there but you cant zip them? If you drag them to your desktop and zip them?


ken

There is apparently some running process that spreads garbage into your drivers. The difficulty will be to find the culprit. For starters I would disable all startup programs and see whether the culprit is amongst those. If that is not it, keep a manual log of all the programs, webpages, folders, etc. that you open. And when you encounter the problem, see whether there is a pattern of openings just before the crash. You will have to observe several crashes to see what's going on.

I dragged and dropped my minidump files to the desktop and tried to zip but to no avail..it keeps saying encountered errors and the file is empty when I try to extract it back out to check contents.
I do not have an OS backup it came preinstalled and I never got around to creating one...imagine that!
How do you open a .dmp file? I would like to view it and see the similarities between the 22 crashes in 2 days.
Thanks for the help

mch

the only way to make sense of a dump file is with an app that "decodes" it. the one that most ppl who do BSOD analyzing use the windbuger from microsoft. there is a friendlier app called blue screen viewer if you are just curious.

Let me know if I can help

ken

Have a look at this How to open Windows DUMP .DMP files.

I downloaded the BlueScreen Viewer...and after decoding every crash has this in common as caused by driver ntkrnlpa.exe. Any ideas? mchris

mch

Blue screen view is a neat app to do a quick read. problem is sometimes it doesn't go far enough. ntkrnpa.exe is a sytem file. without the thing that cuased it to fault the only thing I can suggest it to run a system file check. if you are interested let me know and I will get you links for the debugger.

start>search>type cmd>right click and click run as admin>type sfc /scannow. let us know the results

instructions for run as admin are here Run as Administrator - Windows 7 Forums

hope this helps

Ken

I ran the scan now and it shows corrupt files. Looked at the cbs.log and everything shows 100% except these 2.. 000001b2 verify 2% comp and 000001b6 0%comp. No idea what these mean...any clues?? thanks mchris

driver power state failiure is usually caused when drivers get screwy when your OS is switching power modes (ie going into or coming out of hibernation)

as you have wireless devices im wondering if you have them set to be system manged ie "allow windows to turn this device off to save power" and in being "turned off" thats when the specific driver is causing the BSOD

goto device manager and right click your wireless devices and your network adapters right click and select properties open the power management" tab and if its not greyed out make sure "allow windows to turn this device off to save power" is unchecked

also goto power options in control panel and set your profile to high performance (you can change it back later)