xerxesix Loc: Portland, OR

I have noticed that are a few hoggers that are very knowledgeable about computers. I am having a little problem and hope that someone can offer some suggestions for a possible fix.
I have a PC, ASUS motherboard, OS Win 10 latest update.
When I shut down one of two things happen:
1. Nothing, in which case I do a hard shutdown
2. Normal shutdown
When I do a hard shutdown the PC starts up normally on restart.

When the shutdown was normal the following happens on startup:
1. When I press the start button nothing happens until I press the reset button
2. If I let the computer go through the whole cycle then:
a. I get the blue screen of death with a message of a Driver Power State Failure
b. The OS collects "information" for the recovery and when this complete I have to press the reset button
c. Normal startup from this point on
3. If I let the startup cycle progress for about 5 seconds or so and then press the reset button
a. Normal startup.

I recently replaced my CD drive (SSD to SSD). I have run a diagnostic and it shows no errors or problems with the replacement drive.
Any pointers to a possible fix will be much appreciated

letmedance Loc: Walnut, Ca.

Did you replace the DVD drive, or both hard drives? You may have a corrupt or wrong driver for one of your devices.

xerxesix Loc: Portland, OR

I just replaced the C-Drive. Was an 500MB SSD and I replaced it with a 1 GB SSD

nospambob Loc: Edmond, Oklahoma

check the wire connections to the motherboard. You might have accidentally pulled a button-wire when you pulled the ssd.

xerxesix Loc: Portland, OR

The strange behavior started before I replaced the hard drive. Some research suggested that my c-drive may be failing and that is why I replaced it.

letmedance Loc: Walnut, Ca.

Search Google using that error message and you will find many answers, most suggest a driver issue.

jerryc41 Loc: Catskill Mts of NY

Yes, the driver is usually responsible for crashes.

xerxesix Loc: Portland, OR

😃 At least I am not getting the typical "user error" that I used to get from the IT folks, although the photo could be showing a user error. 😃

SalvageDiver Loc: Huntington Beach CA

The problems you described could have a large number of causes. To help isolate the cause, I would go to your Event Viewer and look for significant errors recorded in the logs. Your problems should have been recorded here. I would search for major errors (red icon to left of error). A Google search of the error description usually describes the cause and in many cases how to fix. Here is a video describing how to use the Event Viewer in Win10.

https://www.youtube.com/watch?v=_6fP8bV5Pb4

If none of these help, I would open the case and look for any loose connections. Failing that, I would then suspect a failing power supply and have it diagnosed by a local technician.

Hope this helps

11bravo

I'll 2nd the advice of looking at the event viewer logs.

When you say "normal shutdown" is that a software (windows icon) shutdown command, or pressing the start button on the computer?

I'd have Task Manager running (ctrl-alt-del) and see what's going on when you say nothing is happening when you do a normal shutdown. Are processes being terminated? Likewise, when you say nothing is happening, do you have HDD/SDD access lights on the computer that are flashing, as in the computer is trying to write/close your drives. I'd be VERY cautious of doing hard shutdowns as I've had several experiences of drive MFT (master file tables) being corrupted before windows had a chance to update. Data can be recovered, but a long process. It sounds like something is being told to shutdown but is hanging...

This MIGHT help with BSOD analysis, especially in determining which driver is at fault. WhoCrashed is freeware.
https://www.resplendence.com/whocrashed_help.htm

You might also enable boot logging to see which driver is failing, especially if you can compare a successful boot log with a failed to boot log.
https://www.windowscentral.com/how-enable-boot-log-windows-10

Does your mobo have an lcd readout of states during post? Or beep codes?

Baffling is why the start button doesn't work after a normal shutdown. What happens if you turn off power supply (either with power supply on/off) or unplugging, the turning back on? Does start button then work?

Sorry, just a lot of spitballing....

Starman441 Loc: Iguana Land, Fl.

You may try this as a solution.When you're ready to 'shut down'; close all open files, folders, & programs. Then open the "task manager" (right click on task bar). Then go to "Details". left click on "User name". This will populate according to users alphabetically. Then 'right click' on any third party program tasks running under 'your' user name end select 'end task'; if there are several tasks under the same program, select "end process tree" instead, to stop all processes from that program. I would leave system files listed under your user name "(blue dot icon) alone. In the 'task manager, you can also click on 'processes' for a list of running processes and stop the user program related items. I hope this helps in some way.

stonecherub Loc: Tucson, AZ

Recently, I had a bunch of seemingly unrelated problems - no sound, the video card went walkabout, new ram chips were hostile, etc. One of the responders on the video card forum suggested that I clear my BIOS by removing the battery and shorting the terminals to drain the capacitors. After I did this and replaced the battery, the BIOS started at "zero" and reset itself, going into setup on the next boot.

ALL of my problems disappeared, "Poof!" It might work for you. This was a common fix-all in the 80s and 90s.

xerxesix Loc: Portland, OR

Thanks to all for your suggestions. After following through on most of the suggestions and a lot of references on "driver power state failure" I removed on of my CD drives, it has been sporadically misbehaving, and the multi card reader, it had a constantly flashing LED.
Here is the current situation:
On shutdown everything is normal, great improvement there and shutdown is really fast compared to what it used to be.
On start-up the C-drive LED flashes a few time and then goes dark. I then have to press reset and then startup continues a lot faster and without the BSoD showing up - another improvement.
Any suggestions on this last glitch would be appreciated. On the other hand, compared to my gyrations to get to full startup, this is a breeze.

11bravo

Could it be a problem with fast startup (guessing)? You might try these to turn off fast startup (as in maybe the computer is not really shutting down, though if you've disabled hybernate this is a moot point):
https://www.windowscentral.com/how-disable-windows-10-fast-startup

https://www.techrepublic.com/article/how-to-fix-slow-boot-times-in-windows-10-when-other-tips-have-failed/

https://www.howtogeek.com/243901/the-pros-and-cons-of-windows-10s-fast-startup-mode/

Also with fast startup turned off, you should be able to see the boot process better displayed on the screen.

You might also check your bios settings to check on boot order. Could it be the computer is waiting on something to timeout before booting to the C: drive?

Also you might want to turn off Quick Boot in the BIOS settings so you have more detail of what's going on.

xerxesix Loc: Portland, OR

I did turn off fast startup and it did not seem to make a difference. Where would I look in the BIOS to see the startup processes and who waits on what?