Ken Turner,

The MSDN bug check code page for DRIVER_POWER_STATE_FAILURE is a good place to start troubleshooting. The Driver Verifier tool can help you find the responsible driver.

Thanks for the suggestion, The_Namek.

I'm not sure I understand what I'm reading on the MSDN bug check code page, nor do I yet understand how to use the Driver Verifier tool. However I will persevere: the first step will be to record the values for parameters 1 to 4 which appear on my BSOD.

I will post again when there's some progress.

The_Namek

OK, here's the stuff from the BSOD:

STOP: 0x0000009F (0x00000500 0x00000002 0x893B76A0 0x891FF998)

So parameter 1 is 0x500, which corresponds to cause "The device object completed the IRP for the system power state request, but it failed to call PoStartNextPowerIrp."  So far so good.  Now it says parameters 3 and four tell me the device object.  What does that mean, and can I translate it into something which will tell me which driver is failing?

There's a link near the bottom of the article I referred you to in my first post in this thread that explains how to use Driver Verifier. You may find the information here and here more user friendly though. 

I had this problem once.

I have this fix:

http://us.f13.yahoofs.com/bc/4640ac66m197c479f/bc/BSOD+Fixes/Fix+Driver_Power_State_Failure.reg?bfUb1JIBar7u_NKd

The hyperlink might not work, but I hope it does. It's because it's on my Yahoo Briefcase thing so the hyperlink might time out.

What it does is it changes the registry so the problem will be fixed. Once you make the change, restart (You might see the problem now but it will be the last time) so that the registry can be re-read on start-up. Then the problem should be fixed.:robotvery-happy:

If the hyperlink does work I could e-mail it to you if you give your e-mail address.

WARNING you must be careful though. The registry is very dangerous, so I would advice creating a sytem restore point just incase it doesn't work and you machine plays up.

Frommerchicken:

As you suggested, the hyperlink does not work.

My email address is ken at kbturner dot co dot uk. 

Frommerchicken:

I still haven't managed to get rid of this problem.

Please either post a valid link or email it to me at ken at kbturner dot co dot uk.

Thanks

Ken,

You really would be better off using the Driver Verifier tool. There's no way to know whether Frommerchicken's BSOD was caused by the same driver as yours unless all the parameters are exactly identical. If they're not then the solution that worked for him or her may not work for you. The second link in my previous post in this thread explains in pretty good laymen's terms how to use the tool & what the outcome will be, which logically will be to identify the driver responsible for causing the blue screen so you can remove it & reinstall a good copy. Driver Verifier's results are also in more easily understood language than the programming code shown on the blue screen itself.