Unusual mobo actions following a Windows update. Need assistance.
Unusual mobo actions following a Windows update. Need assistance.
Last night while shutting down my system, I noticed an upcoming Windows update and selected it, then powered off. About 20 minutes later, I returned and found the computer still on but with a black screen—completely unresponsive. I had to force shut it by pressing the power button. When I tried to restart, it wouldn’t turn on at all. I’ve had no stability problems since setting up this system roughly six months ago with Windows 10. Apart from enabling DOCP for RAM in the BIOS, I haven’t overclocked anything. After a few restarts, the error code changed from 0d to 64, sometimes showing 98. Eventually, I gave up and went to sleep. This morning, when I worked on it, I saw code 22 and got stuck in a boot loop for about 20 seconds before it rebooted with codes 64 or 98. After one final attempt, I pressed the power button repeatedly, then it booted into Windows showing code A0—seems to indicate a sleep-mode recovery. I can recreate this method by rapidly pressing the power button each time. If I reboot from Windows or just press it once after a cold start, I still see codes 64 or 98. When I boot normally, all hardware works fine. I’ve tried clearing CMOS, resetting BIOS, reinserting RAM, checking for faulty RAM, reseating the GPU, using a Windows flash drive, and even reformatting the drive, but nothing resolves the issue. Anyone know what might be causing this?
an update... so it turns out its related to my monitor and/or GPU I am running a 3080ti and just recently bought the samsung odyssey G9 (not the neo). I didnt notice the issue before but if i try to turn on the system while the G9 powered on first and connected with displayport it doesnt want to post. If i use my old monitor connected to displayport everything boots perfectly fine, no problems at all. If I power on the G9 AFTER I hit the power button on the system it also boots fine. I dont remember that happening before this last windows update, but I have only had the G9 for 2-3 days and maybe I had just been turning that on after the system and never ran into the issue until now. Im gonna see if theres a bios update of some kind that will address the issue. Ill keep this thread updated with my results for anyone else that may be having an issue. EDIT: vbios update to the GPU seems to have totally solved the issue.