|
Problem description: Ever since I upgraded my PC to WIndows 10 a few months ago I've been having some issues trying to wake the computer from sleep. 25-50% of the time the computer will spin it's fans as if it is waking from sleep, stop, try again, the finally stop and just restart. This seems to be happening more and more this last week. This was not happening on Windows 7 as far as I can recall. I also overclocked a little while before the Windows 10 upgrade following a guide online, but I do not recall which sleep settings I may have changed. Attempted fixes: I have played around with some sleep settings but nothing seems to have fixed it yet. Googling the problem gives me a lot of threads with fixes based on changing the power button settings, but this happens whether I use the power button to wake the computer or the mouse/keyboard. Many people also point to driver issues but my my display driver is kept up to date and my motherboard chipset drivers are as up to date as they can be (no Windows 10 version available). BIOS are up to date as well. Checking Event Viewer shows me that there was a critical Kernel-Power error and states "The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly." This makes me think that it is less of a Windows issue and maybe something else messing with sleep. I'm not sure what else to look for in there. Recent changes: Windows 10 in-place upgrade. Overclock. -- Operating system: Windows 10 Home 64-bit System specs: Home-built PC: code:
I have Googled and read the FAQ: Yes Radioactive Toy fucked around with this message at 16:34 on Feb 8, 2016 |
# ? Feb 8, 2016 02:00 |
|
|
# ? Apr 19, 2024 10:03 |
|
Update to the latest motherboard BIOS, that's what controls sleep/wake transitions and stuff like that.
|
# ? Feb 8, 2016 16:21 |
|
Whoops sorry, I meant to mention that I'm on the most current BIOS version for my motherboard, 3602. I will edit that in to the original post.
|
# ? Feb 8, 2016 16:34 |
|
In case this happens to come up for anyone in the future, I solved this by disabling the Internal PLL Voltage in BIOS. The solution came from here and here.
|
# ? Feb 15, 2016 17:48 |