First of all this isn't happening on my current pc, rather on my old pc that I gave to my Dad which the specs are as follows:- Q6600 (can be OC'd to 3.51GHz but currently set to 3GHz) Gigabyte X38-DS5 (latest bios installed) 8GB RAM 1066MHz R9 285 (set to legacy bios via switch rather than UEFI) Samsung 256GB 850 Evo 680W PSU (It's an old Hiper Type-R mkII however it's still running perfectly) Windows 10 Professional (Creators Fall) (I know this is a relatively old pc now but it's by no means incapable) Whenever the pc restarts, it will come to a black screen, that is, it fails to boot up as such, it wont load the bios and will just be stuck in a pre-post state. The pc runs perfectly fine, shuts down normally, turns on normally. The issue only occurs when attempting to restart, such as when restarting after installing software or if there has been a windows update that requires a restart, in which I have to shutdown instead or force the machine off and then turn it on to resume the update - this behaviour never occurred while it was under Windows 7 nor prior to Windows 10 Creators update. This is a really weird issue that I just can't seem to solve - fast startup is disabled, bios for motherboard and gpu is up to date, firmware is latest on the ssd. Thanks
Could be bad ram training or even PSU. I had a first gen TX750 that would not reboot but was otherwise fine under stress tests; sometimes after a few days of sitting it would not post at all until sitting there for 5 mins. It was like it needed to 'warm' up.. Really weird.
I've tested with my EVGA PSU, same thing still occurs which as you suggest, it could mean memory issues sure but again this didn't happen until after Win 10 Creators, prior to creators it behaved normally (I thought that the Fall update might have addressed it but it didn't), I'm inclined to believe it might be something to do with handover from OS to BIOS (maybe Win10 doesn't realise it's a legacy bios sytem not UEFI) I will toy around with the memory, try all manner of configurations (such as 1 module vs 4 etc) see if that has any impact. Turning on and shutting down all works fine, it is just restarting.
Once you restart it and it 'cycles' power the OS has nothing do with the POST afterwards. If it's freezing on post It's some other issue to address.
The problem could of occurred during the time of your windows installation or something. Why don't you put Windows 7 on a flash disk and run that for a week to see if it has anything to do with the os at all. I think the issue probably doesn't have anything to do with which os you have installed. So put a windows 7 os on a flash drive and use that os to run the whole system instead of hard drives inside the case to confirm if it has anything to do with the os. Sounds reasonable?
Hi you already try make use of Dism to search some corruption? if not try this two commands: remember to use cmd @ admin ok Dism.exe /online /cleanup-image /scanhealth -->type enter (if OS warn some issue) Dism.exe /online /cleanup-image /restorehealth -->type enter I hope that help you
Yeah, that's what I mean with the handover, I don't think Windows is actually power cycling, when it gets to the point were it would "turn off" or "cycle" (when you'd see the power light ordinarily flash or lights on other devices flash), it just does nothing leaving it in limbo so to speak, everything just remains on. I've tested out different ram configurations and it still exhibits the same behaviour so I'm thinking it might be a motherboard issue (it is old now so would make sense and the creators update could have been coincidental) or still an OS issue. I'll try out the cleanup and try out a separate install of windows on another drive to see if those shed light on this issue.
To make sure windows is actually doing a real reboot and not that 'fake' reboot, make sure to disable hibernation. You could try this in cmd. shutdown.exe /r /t 0 Latest out of the box windows behavior does not do an actual reboot, it pages everything to disk and loads it into RAM when 'restarting'. Above cmd forces an actual reboot.
Google says you might try disabling "Fast Startup", and/or disable all non-Microsoft startup services and re-enable one at a time to see what's causing the issue. Good luck!
How do you know the PC is in pre-POST? Can you RDP into it when this happens? What does event viewer say? Check that Base video isn’t ticked – start, run: msconfig. See boot tab. Check Reliability history: start, run: perfmon /rel
I have a similar issue with one of my hdd's, it seems that the OS storage driver does not exit cleanly and the drive needs to re- spin up after restart, which in an msi motherboard would hang, in my current asrock board it takes 20 seconds to continue booting- and no such issue after shutdown or cold boot, only when restarting. I did not find a solution yet. Also, it seems related to intel RST driver exit mechanism.