Precision 3630 won't boot after shutdown Windows

How are you shutting down the computer? Are you using the Start Button and selecting Shutdown? Or right clicking on the Start button and selecting Shutdown from the menu?  If you are doing anything else, change to one of these methods.

More shutdown info-- How To Properly Shut Down A Windows 10 PC (lifehacker.com.au)

Check Event Viewer for any errors about shutdown.

Try :

Control panel > Power Options > System Settings
and uncheck  Turn on fast startup ( if on and greyed, click first on Change settings that are currently unavailable)

Windows is shut down as it should - Windows Start menu > Shutdown

When the machine is subsequently started (by pressing the power button on the case), it doesn't find a boot device. Opening the BIOS, the drive isn't there. When the power cord is pulled and then reseated, the machine starts without problems.

We have a bunch of 3630 machines and only one of them is having this problem.

Like I said - depends on how the machine is started. If it's on stand-by, and then switched on, the drive isn't there. BIOS nor diagnostics. When the power cord is pulled and reseated, the drive reappears.

What about going F12 diagnostics ? would still not see the boot drive ?

Well, that's why I suggested turning off Quick Boot ( to remove the partial hibernation from the equation ).

I assume the drive stays if doing reboots.

Ah ok. mmm and I assume that this specific machine has not received a driver update by error ( compared to the others )

The point with the previous questions is because I had something slightly similar happening but it impacted a randomly connected drive ( not the nvme ) and it was caused by a bug of the RSTe driver in conjunction with recovering from sleep/hibernate. But this seems definitely different.

Weird question maybe, but ... what about putting a new cmos battery ? ( in case the one onboard is low and causing quirks )

Hibernation / Quick Boot is turned off on all our machines (powercfg.exe /hibernate off). When I say the machine is in stand-by, I mean the power cord is connected to the machine, so the motherboard receives power.

Well yes, my system is working fine.

---

@Simon Weel wrote:
Hi there, We want to make sure your system is working fine and hence following up. Having said that, we do not want to disturb you with numerous messages. We will wait to hear from you to continue the conversation.

---

Weird - I didn't post this?

I felt it was strange...

Old topic - but it seems resolved. I tried all different suggestions, but they didn't solve the problem. Then I remembered I had put in a couple of extra 16 GB memory modules, so it had 64 GB in total. Although the modules were same spec as the ones already in the machine, Lansweeper reported a different speed for them? Not so with Powershell. A bit awkward - which is reporting the right values? Anyway, decided to remove those extra modules and.... problem seems solved!