Patrick Grimson

Thanks for the reply! I will have to try your command because I only tried shutdown /f t 0. I will let you know if it works. As I said before, I did disable fast startup from power options because I heard it was a common problem. I then disabled the hibernation file using the command powercfg -h off. Still not much change. However, if I Shift-Shutdown from the start menu, the system shuts down like normal. No hanging with no disk usage. From my knowledge Shift-Shutdown just bypasses the hybrid boot of Windows 10 and completes a full shutdown which is why the system uptime resets when you shutdown this way? But if I disabled the hybrid shutdown from power options and then disabled the hibernation file, why would it still be causing issues? Shouldn't it be fully disabled or am I missing something here? There was no change to the computer names on any of the machines. Still User-PC I believe. I verified the health of all drives and they all registered as healthy and operate properly when swapped into other known good machines. I will enable verbosestatus when I get the chance and see if anything holds up the shutdown process once it gets to the blue spinning orb phase.

I have 3 machines from a lot of 24 which are experiencing some odd issues. When I shutdown the machine, whether it is from Run, CMD, Alt-F4, or start menu, the system will not do anything for a good minute. It almost appears that the button does not function at all. I should also mention that pressing the physical power button on the case does not prompt a shutdown either, despite the power options being set to do so. I can still open all programs on the machine after clicking shutdown and they will open, with the exception of Optimise Drives which takes 30 seconds - 1 minute to open, which is another odd behaviour all 3 are exhibiting. After a minute passes, the machines will start shutting down, but they will take a long time to do so, with little to no drive activity. Once the display eventually turns off, the machines will run for a while longer, again with no drive activity, before eventually powering off. I've read that this black screen issue is common among the 1803 update, but nothing about Windows refusing to shutdown. On some occasions, I have had a couple of the 3 flaky machines post (CPU Fan ramps up and down which usually immediately precedes Windows loading), but the display will not receive a signal for roughly a minute. Once the video shows, the Gigabyte BIOS logo will hang for 1-2 minutes and eventually to proceed to boot Windows normally. All of the machines have an identical image of Windows 10, as it was cloned from the same drive for each machine. All BIOS revisions are the same, and all systems are as up to date as possible as of 16/07/2018. I have tried reinstalling all drivers, swapping PSU's and SSD's with known good parts, removed GPU's and used IGPU's with no luck. I tried different SATA ports and versions (3.0 & 2.0). I have also tried disabling fast startup in Windows because I read that this is another common cause. The specs of the machines are: Intel Core i5 4460 Gigabyte B85M-D3H Antec VSK3000B Black Micro ATX Case with stock 500W PSU 8GB of generic DDR3 1600MHz Ram (2x4GB sticks) Kingston SSDNow V300 120GB SSD Gigabyte GTX 750 2GB Generic USB 2.0 Internal Card Reader I am lost as to why only 3 of the 24 machines are experiencing these issues. Each computer has been stress tested using Asus RealBench and the drive health checked by Crystal Disk Info. Any advice as to why these machines would be acting up is much appreciated!

Thanks all for your help. I went to install the 620 but found out that the x8 PCIE slot actually has a backing at the end of the slot, and isn't open so I can't install the GPU afterall.

I'll give it a shot when I get my computer back together

Hmmmmm. OK. I was able to get it to output from GPU and onboard graphics at the same time, but it was VGA from the mobo and had weird lines all over the screen.

So I have an R9 270X 4GB from Gigabyte, and one of the DVI connectors mysteriously broke after lending it away.... I did have three monitors connected to it, but now I am unable to connect my third monitor to it because of the broken DVI port. My question is, I have a GT 620 laying around. If I was to install that alongside my 270X, would I be able to use the 620 as a display output only, while still rendering games and such on the 270X?