Question About Unusual Crash/Reboot Occurring Only When System Is Left Unattended
Question About Unusual Crash/Reboot Occurring Only When System Is Left Unattended
These were functioning as regular monitors before my first mention of the issue in post #1.
When reviewing the details, it simply says: The previous system shutdown at 10:08:56 PM on 3/1/2024 was unexpected.
Is there a more effective way than checking Administrative Events in Event Viewer? Is there a better method to share this information?
I checked the scheduler and only items I noticed were disabled.
Downloaded Process Explorer but it’s beyond my usual comfort zone now. I’m unsure how to use it effectively.
I have turned off updates and tried the update troubleshooter, so the outcome is still uncertain.
Event Viewer still shows a WHEA-Logger Hardware failure event.
Also, I realized I didn’t specify that this is Windows 11 Pro, and based on the issues, I think that might not matter.
Search for the phrase and examine several results. Adjust the search terms based on what you find, considering the issues with the system. The goal is to focus and pinpoint possible causes. Be ready to spend considerable time reading. You should quickly discard some options, especially those offering software fixes, as they often appear regardless of the issue. Avoid solutions that require registry edits. You requested tools like PowerShell and simple Get cmdlets for diagnostics. So far, no obvious "Get" commands stand out as useful. Revisit the information and see what diagnostic value it might offer. And you have progressed further in understanding the situation. It’s likely the number of possible causes is decreasing—hardware may be more questionable now.
I’m starting to wonder if leaving my BIOS unchanged was the right choice. I’ve been running a FurMark stress test on both GPU and CPU for about 15 minutes, aiming to simulate a failure. So far, there’s no visible issue—GPU is at or below 80°C and CPU stays under 74°C.
I’m not a beginner, but I haven’t faced something like this before. While it’s usually advised not to tweak BIOS settings, I’m curious if downgrading could help. The latest release was meant to fix a possible exploit, though I don’t have secure boot activated.
Well, this whole discussion feels quite similar… particularly the post you referenced:
https://www.reddit.com/r/Amd/s/kcu0mkyFbH
I had to look into it, found the setting in my BIOS, and made the adjustment. The system is now idle and should respond within about an hour.
So I adjusted my monitors to sleep after five minutes and let the system rest. It still crashed with dark screens and didn’t recover from a reboot. I had to keep the power on to shut it down before turning it back on. Positive news though! No WHEA-Logger event was recorded this time. Still facing the WindowsPackageManagerServer.exe crash issue.
I found a thread that suggests I’m not alone with this problem, and it’s recently appeared:
https://answers.microsoft.com/en-us/...r...98e2a2bc37
The symptoms match some users too; the system crashes without video, requiring power to shut down and then restarting. But now it seems less likely to be connected to these crashes since I saw a log entry after a restart.
I’m considering that Event ID 56 might be responsible for the crashes. I’ve opened a discussion on Microsoft Answers about it.
It’s worth noting that I sometimes dislike Google’s search algorithm... I’ve searched those WHEA events many times and never found the thread I just checked today.
I plan to leave my system unchanged so I can monitor for WHEA-logger events, and I’ve added my $.02 to the Microsoft forums thread. I really hope this signals progress...
So, there was no assistance from the Microsoft answers threads. The local shop where I brought my PC suggested I update my BIOS, which they said is a known issue for the ASRock board I have. They emphasized I should look up the part number of my board more carefully. I might try getting it back and see if downgrading the BIOS brings stability. If that fails, I’ll switch to an ASUS or Gigabyte model.