Question Troubleshoot Restarting PC

[iTRiP]

Antec NX220 RGB LED Gamer Case.
Intel i5 10600K 4.8GHz Hex Core Processor with Hyper-Treading (CPU)
Intel Stock LGA1200 Cooler.
Gigabyte B460M D3H Motherboard.
24GB 2133 MHz Dual-Channel (8GB+4GB Corsair DDR4 & 8GB+4GB Corsair DDR4) (RAM)
ASUS AMD TUF Radeon RX 7900 XT OC 20GB. (GPU)
Antec HCG EXTREME 1000 Watt Gold Power Supply. (PSU)
Samsung 500GB EVO 860 Solid State Drive, Installed Games. (SSD)
Samsung 980 PRO 1TB Solid State Drive, Operating System, Installed Games. (NVMe)
Samsung 980 PRO 2TB Solid State Drive, Installed Games. (NVMe)
Western Digital Blue 2TB SN550 Solid State Drive, Installed Games. (NVMe)
Seagate 2TB ST2000DM008. 7200rpm Hard Drive, Games backup. (HDD)
Seagate 2TB ST2000DM008. 7200rpm Hard Drive, Games backup. (HDD)
Seagate 10TB ST10000VE0008. 7200rpm Hard Drive, Movies. (HDD)
Microsoft VHD Blue Ray Image Drive.
Intel 1000Mbps Ethernet.
D-Link 300Mbps Usb WiFi.
Genius GX Scorpion K220 Wired Usb RGB Gaming Keyboard.
XGR Wired Usb LED Gaming Mouse.
Logitech Stereo Speakers.
LG 24inch 1080p 144Hz Monitor. (Capable of 2160p [4K] @ 120Hz)
Microsoft Windows 11 Home 64bit Usb Install media and activation.

On either windows 11 23H2 or windows 11 24h2 installed, PC restarts seemingly randomly when idle.
Reliability monitor displays error with the pc did not shut down properly, or previous shutdown was unexpected.
Before this error started the pc had been running without issue for 11 days, since it had been totally rebuilt, completely formatted and completely reset, and reinstalled. (to test the pc had been formatted and reinstalled again, with no resolve)

Thank you.

 

[helpstar]

Bios up to date?
anything OC? reset bios by jumper
all devices firmware is up to date?
check with memtest
check windows with dism commands
check all drives with manufacturer tools and eventually update firmware with it
try different psu
check cpu socket for bent or discolored pins
check if cpu cooler is tightened too much on the cpu

try minimum setup
windows drive, one ram, cpu with cooler, keyboard mouse, motherboard, monitor in motherboard

 

[iTRiP]

Bios up to date?
anything OC? reset bios by jumper
all devices firmware is up to date?
check with memtest
check windows with dism commands
check all drives with manufacturer tools and eventually update firmware with it
try different psu
check cpu socket for bent or discolored pins
check if cpu cooler is tightened too much on the cpu

try minimum setup
windows drive, one ram, cpu with cooler, keyboard mouse, motherboard, monitor in motherboard

None of that resolves the issue!

One thing noted thus far: If the PC had been shut down for 30mins or more the next random restart doesn't occur until 24 hours had passed, and if the PC is not shutdown the random restart repeat indefinitely.

 

[helpstar]

did you try a new psu with new cables ?
eventually replace other parts like motherboard and cpu

 

[iTRiP]

did you try a new psu with new cables ?
eventually replace other parts like motherboard and cpu

Yes, I have done that another time, but I think I might have found the solution in my bios, under power settings, something called dummy load (power loading), seems the setting was disabled. (and clearly states that one ought to enable it if such a restart occurs if the system was idle to resolve it)

This setting states that when the system is under low load it would restart the pc as if it were a power failure that occurred, thus the kernel 41 power event error, and pc did not properly shut down in reliability monitor.

Going on and looking forward if this was it, if not more help could be useful.

 

[iTRiP]

No have not found the solution to my pc randomly restarting issue yet, what I posted previously did not solve it.

Any real help would be greatly appreciated.

 

[iTRiP]

You all know this troubleshooting is not all that much fun, I'd rather play games that I paid for on an OS I paid for on hardware I paid for to properly run without any issue.

 

[iTRiP]

I ran Malwarebytes, You know with my practices, something like that ought to not be required, but looks like a great software and seems that if you really get your pc into trouble that can help, too bad they ask lots of money for such, but probably everybody has got to put food on their tables, besides that I have now enabled kernel memory dump to be created if there comes another restart to my pc, read that sort of thing can pinpoint the issue.

Another thing noted is that my pc somehow doesn't like a system managed page file anymore, and auto page file is anyway required to write a dump file, so I have set the page file to that.

Why did my pc function normally for the first 11 days since I rebuilt it, everything had been running great then this restart issue appears with the same windows reliability report as what I had seen on this pc when the previous GPU failed, I know that because it failed in my other pc too eventually and I have thrown it in the trash now, isn't my pc supposed to be running properly now since I have done everything up to this point that can be done?

 

[Ralston18]

Look in Reliability History/Monitor and Event Viewer for any error codes, warnings, or even informational events being logged before the restarts.

Also look in Task Manager > Startup and Task Scheduler.

There may be something running in the background or later being triggered via Task Scheduler.

 

[iTRiP]

Look in Reliability History/Monitor and Event Viewer for any error codes, warnings, or even informational events being logged before the restarts.

Also look in Task Manager > Startup and Task Scheduler.

There may be something running in the background or later being triggered via Task Scheduler.

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

 

[Ralston18]

What same events?

Error codes, descriptions, app names, etc... ?

Open Disk Management. Expand the screen so all can be seen and read.

Take a screenshot and post the screenshot here via imgur (www.imgur.com).

Also open Reliability History/Monitor (Day view) and take a screenshot to post.

When finished with working and/or gaming what shutdown procedure is being used?

 

[iTRiP]

What same events?

Error codes, descriptions, app names, etc... ?

Open Disk Management. Expand the screen so all can be seen and read.

Take a screenshot and post the screenshot here via imgur (www.imgur.com).

Also open Reliability History/Monitor (Day view) and take a screenshot to post.

When finished with working and/or gaming what shutdown procedure is being used?

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

 

[Ralston18]

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/sysinternals/downloads/process-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.

 

[iTRiP]

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/sysinternals/downloads/process-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 be sure to keep your suggestions in close consideration and actually utilizable.

In the meantime, I have been busy downloading some EA games which took the CPU usage up a bit from being idle, which was when the pc had these random restarts, saw somewhere that changing the setting for auto restart too unchecked could be a resolve, so I have done that, and set a memory dump to be created...also set the system managed page file which I always used to, automatic managed page file, seems with the new GPU it won't work right without this change, but that's just speculation at this point.

I'll post here If I learn something new or have more data to share.

I played some games again today and the system seems stable, just the idle restart issue to resolve at this point if it shows again.

 

[Roland Of Gilead]

Antec HCG EXTREME 1000 Watt Gold Power Supply. (PSU)

Hey there,

How old is the ANTEC? Prob about 2018? Correct?

Random restarts, typically at load but not always, can point to the PSU. Have you another you can try, or perhaps a friend can lend you temporarily?

Whilst your PSU is pretty decent, and also has a 10 year warranty, it could be failing.

What is your current bios? Have you updated the bios recently?

 

[iTRiP]

Hey there,

How old is the ANTEC? Prob about 2018? Correct?

Random restarts, typically at load but not always, can point to the PSU. Have you another you can try, or perhaps a friend can lend you temporarily?

Whilst your PSU is pretty decent, and also has a 10 year warranty, it could be failing.

What is your current bios? Have you updated the bios recently?

The PSU is 2019, and I tested the system with a 2021 PSU as well, before all this the previous GPU was dying, now the only issue remains is that the pc restarts windows when idle... where am I supposed to look for memory dump files being created, trying this method now, don't know where else to turn to resolve this.

Keep in mind the pc had been running (with heavy load and at idle) for 11 days prior to this issue without issue besides this new issue since being rebuilt and upgraded and reinstalled.

If I keep the pc off for just a few mins the consecutive restarts end.

 

[Roland Of Gilead]

The PSU is 2019, and I tested the system with a 2021 PSU as well, before all this the previous GPU was dying, now the only issue remains is that the pc restarts windows when idle... where am I supposed to look for memory dump files being created, trying this method now, don't know where else to turn to resolve this.

Keep in mind the pc had been running 11 days prior to this issue without issue besides this new issue since being rebuilt and upgraded and reinstalled.

If I keep the pc off for just a few mins the consecutive restarts end.

Okay.

Bios revisoin?

 

[Roland Of Gilead]

Have you tested your ram with memtest86+? Try that and see if it clears with no errors.

 

[iTRiP]

Have you tested your ram with memtest86+? Try that and see if it clears with no errors.

Yes ram tested, all four sticks pass the memory test. thanks for asking, but I have done that.

 

[iTRiP]

Okay.

Bios revisoin?

Gigabyte B460M D3H rev 1.0 bios version: F7

Where do I find the created memory dumps, I have set it to kernel memory dump, is that right?

At this point I can't find any memory dump being created, is the system not having a fault then?

Is this an intentional restart being triggered by what or who?

 

[Roland Of Gilead]

Gigabyte B460M D3H rev 1.0 bios version: F7

Where do I find the created memory dumps, I have set it to kernel memory dump, is that right?

At this point I can't find any memory dump being created, is the system not having a fault then?

Is this an intentional restart being triggered by what or who?

When did you update to F7? Do recall clearing CMOS when you did that? If not, I'd try that anyway, as it could be a bios issue.

 

[iTRiP]

When did you update to F7? Do recall clearing CMOS when you did that? If not, I'd try that anyway, as it could be a bios issue.

Had the default bios version for some years, then updated to the next, and later the next which was this one F7, somethings in the bios never looked correct on all versions, but it worked every time for the longest time without issue.

I think you might be right, because just now and in recent bios visits, there seems to be odd things happening like some settings that don't apply or when applied don't seem to have affect when altered and saved.
I'm looking into this. posting when something changes!

 

[iTRiP]

When did you update to F7? Do recall clearing CMOS when you did that? If not, I'd try that anyway, as it could be a bios issue.

Do recall that I had never needed to resort to clearing the CMOS, anyway I have done that now as well, but in the process lost my expansion slot for my additional NVMe, besides being with one drive less and having to sort out everything related to that change, somethings have changed since clearing the CMOS, for instance the power loading setting that I observed earlier changed to allow auto setting!

Lets see how it goes from now...