Diagnose PC Restart Issues
Diagnose PC Restart Issues
I have A clean OS, twice now deleted partitions and reinstalled windows first was 22H2 updated to 23H2 then 24h2 and for that install
since my rebuild and new GPU upgrade the pc had been running 11 days 24/7 without issue idle and with max load, no issues! before this ( how is this possible?)
, anyway thanks for the support. let's see:
Same Reliability History Monitor: Windows was not properly shutdown. As before the rebuild and GPU upgrade, case swapped and such (eleven days without any issue after that the issue just appeared again (the previous GPU RX vega64 was dead) and nothing I have done since has solved this so far.
In the Event same events keep popping up at time of restart:
https://imgur.com/nbQd4ML
View: https://imgur.com/nbQd4ML
Same issues occurring?
Error codes, explanations, application names, etc... ?
Launch Disk Management. Increase the display size so everything is visible and readable.
Capture a screenshot and share it here via imgur (www.imgur.com).
Also access Reliability History/Monitor (day view) and take a screenshot to post.
Once you've completed working and/or gaming, what shutdown process are you using?
See previous post for some of that I have uploaded some imgur link.
When finished with working and/or gaming what shutdown procedure is being used? The pc runs 24/7.
there only one day listed now, because I clear the data when there is a fault (hope to get back to months of blue balls and never any red balls, hahah one day.
https://imgur.com/vgXoSj7
View: https://imgur.com/vgXoSj7
https://imgur.com/FJldfqT
View: https://imgur.com/FJldfqT
https://imgur.com/pVw2O6x
View: https://imgur.com/pVw2O6x
https://imgur.com/zfR1I0s
View: https://imgur.com/zfR1I0s
https://imgur.com/fTyrdv5
View: https://imgur.com/fTyrdv5
I tried with hyper-threading disabled, and no luck so I turned it back on.
why is this even listed I don't have hypervisor installed?
https://imgur.com/7ZKVLKv
View: https://imgur.com/7ZKVLKv
My suggestions:
Disk 0 (Drive B:
) Drive letters A and B were created for the wayback days of floppy disks that preceded the use of hard drives lettered C:, D:, etc. Historically then, A; and B: are "reserved" and should not be used to designate hard drives. Actually, I am not sure about the consequences of assigning A and B to system drives with respect to current builds. Overall though, the practice has been "do not use A and B" for hard drives or optical drives. Simple enough for you to change "B" to some other unused letter.
Reliability History/Event Viewer
. Stop clearing the logs. Logs can be and should be cleared from time to time but you are giving up the historical entries that could reveal patterns and/or trends.
Shut down.
Running a build 24/7 is understood. However, sooner or later updates will require restarts to fully implement the updated code. Loss of power is not a restart and often corrupts files and data.
Windows needs proper shutdowns in order to finish up working processes and prepare for the next boot. Use the
Windows Power icon to shutdown the system
and allow Windows the opportunity to do what needs to be done. No hard power offs - meaning that in one way or another power is cut to the system. Switch, unplugging, breaker trip, loose wire.....
It is not uncommon for the OS and some apps to make changes to the system. Either by design or maybe some bug in the software. There are many dependencies in Windows and and anything that is not as "expected" by Windows is likely to cause problems. If Windows is reporting something amiss (e.g., hyperthreading) then that is a clue.
Task Manager > Startup and Task Scheduler
both provide information about what Windows may be doing or trying to do when first booted.
Corrupted files:
Also very likely that overtime files and data of all sorts have been corrupted or even lost. Run "dism" and "sfc /scannow" to find and fix such problems.
Another tool that can help is
Process Explorer
(Microsoft, free). Process Eplorer provides a great deal of information about what all is running on the system. You may find unexpected or unknown processes running. Other others that are grabbing more resources that expected or otherwise not as expected.
https://learn.microsoft.com/en-us/sysint...s-explorer
= = = =
Backups:
Do you have all important data backed up at least 2 X to locations away from the build in question? If not, then do some immediately. Verify that all backups are recoverable and readable.
Thanks, Ralston18, I’ll keep your ideas in mind and try to apply them effectively.
In the meantime, I’ve been working on downloading some EA games that increased CPU usage when the PC would restart unexpectedly. I found a suggestion to adjust the auto-restart settings and set up a memory dump, which I followed. I also configured the system-managed page file, as it seemed necessary with the new GPU. This change might be important now, though I’m still unsure.
I’ll share more updates if I discover anything new or collect additional information.
Today’s gameplay felt stable; the only issue remains the idle restart problem, which should resolve once it reappears.
Hey there,
The age of the ANTEC seems to be around 2018, right? Correct?
Random restarts often occur during high load but not always, which might indicate a PSU issue. Do you have another option you could try, or would a friend be able to lend it temporarily?
Your PSU appears to be in decent condition and comes with a 10-year warranty, though it may be showing signs of failure.
What is your current BIOS version? Have you made any recent updates?
The PSU is from 2019, and I checked the system with a 2021 PSU too; before that, the previous GPU was failing, now the main problem is the PC restarting Windows when idle... where should I find memory dump files? I'm trying this approach now but don't know where else to look to fix this.
Remember, the PC had been working under heavy load and at idle for 11 days before this issue started, aside from the new one since it was rebuilt, upgraded, and reinstalled. If I leave the PC off for just a short time, the repeated restarts stop.