• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Bluescreen at XP shutdown/restart

C

Cabana

Senior member
I get a bluescreen everytime I shutdown or restart my computer. I installed XP Professional about a month ago and about 2 or 3 weeks ago it began doing this. Here are my computer specs:

ABIT KT7-RAID
AMD 1ghz Thunderbird
768mb pc100
Voodoo5 AGP
2 IBM HDs
TDK 16x Burner
Pioneer 16x DVD
Linksys LNE100TX
SBLive MP3
Microtech ZIO Smartmedia Reader

Here is the error:



<< A problem has been detected and Windows has been shut down to prevent damage
to your computer.

DRIVER_POWER_STATE_FAILURE

If this is the first time you've seen this Stop error screen,
restart your computer. If this screen appears again, follow these
steps:

Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use Safe Mode to remove or disable components, restart your
computer, press F8 to selected Advanced Startup Options, and then
select Safe Mode.

Technical Information:

*** STOP: 0x00000009F (0x00000002, 0x82F6EE10, 0x82FEBA38, 0x82FA8A08) >>



That last part probably isn't any help, but I figured I'd post it anyway.

The only thing I could think of is that I have the Voodoo5 and there are no drivers for XP, so I had to use some hacked 2k drivers. It worked fine for a while, but maybe I installed a different set that messed everything up. I have tried resorting to the XP default drivers and also some other ones, but I can't get rid of the blue screen. I also took out the Voodoo5 and put in a junky AGP card, but that didn't help either. Anyone know? This is driving me crazy.
 
It sounds like your computer isn't able to turn off a hardware device for some reason. First, make sure you have all the Windows Updates, then I'd start pulling pieces of hardware bit by bit and restarting a few times. Is there any especially old/weird hardware in the machine besides the Voodoo5 (the smartmedia reader?).
 
Had the same thing about two months ago when I first installed XP pro. The Blue Screen did tell me the culprit . . . a Lexar combo media reader. Apparently it is not happy with XP Pro and vice versa.

I read your blue screen and am inclined to suspect your media reader. A simple test would be to remove it and see if the blue screen goes away.



 
I took out both the network and sound cards, unplugged the USB media reader, and switched the Voodoo5 for a Trident card. I ran Sigverif.exe to check for unsigned drivers and it pointed to two 3dfx files, so I deleted those. I still got the blue screen after all this. I'm going to reinstall XP over the current installation and hopefully that will cure it. If not, then I guess I have to start over. *Sigh*
 
I believe it's definitely a driver issue, and I wouldn't go reinstalling just yet. Instead, make note of all your running programs when you go to shutdown. Here's a utility that can help you determine that...it's called "EndItAll" from Zdlabs...freeware. It does a better job of describing what driver belongs to what program:

Read about it here, and you can download it from the table of contents on the right side of the web page. I'd read about it first, though...

EndItAll from PC Magazine

You've definitely got an incompatible driver or a program that's running that won't shutdown properly. However, "signed" drivers are nice, but just because a driver isn't "signed", I wouldn't necessarily suspect it. I have tons of unsigned (yet new) drivers on my XP system.

Here's a few pages from Microsoft's Knowledge Base that will show you that it's not just hardware, but could be a program itself that's causing this issue. You might see something in here that applies to your system, but just because you don't, keep investigating. Use EndItAll to shutdown a program before attempting a shutdown to see if it affects your blue screen. Tedious? Sure, but that's what troubleshooting is all about. Here's the list of sites from MS about this problem:

Google list of Knowledge Base articles about this issue
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top