[SOLVED] PC randomly restarts but there is no BSOD ?

[Khojo]

My pc will just randomly restart while playing a game and there will be no BSOD. Took it to a shop and they weren't able to replicate it. Looking for any help in identifying and fixing the issue. Thanks.

System Logs: https://1drv.ms/u/s!Agx8r3104AXbizmL_J5Nve5UIHyM?e=PGoc3K

 

[Darkbreeze]

Nobody can access your logs without your OneDrive login info, which you should not share. Please post your full system specs HERE, as follows. Please provide EXACT model numbers for everything possible, not just, "8gb ram". Model numbers are sometimes very important.

CPU
Motherboard
RAM
Power supply (Exact model is 100% necessary)
Storage devices
Cooling devices
Case
Windows version
EXACT BIOS version

 

[bicy]

So, system log usually do not contain all error reports.

 

[ubuysa]

Thanks for uploading the System log, it is a useful source of error and warning messages and does often help in diagnosing problems.

In your log I can see the many error 41 messages indicating that Windows wasn't shutdown properly, these will be the result of the restarts of which you complain. Whilst I do see several other error or warning messages that are of concern I don't see any error messages that can convincingly be said to be the cause of these restarts.

How does it restart? Does it power off and you have to restart it manually? Does it do an auto-restart on it's own? Does it do something else?

Have you checked temperatures yet? If not please download HWMonitor (free) and run that. Expand the CPU temperatures section so we can see every CPU core. Then post a screenshot of those temperatures when the PC has been completely idle for five minutes. Then post a second screenshot of those temperatures when you are working the CPU as hard as you possibly can.

It will be handy to see more troubleshooting data, so can you please download the SysnativeBSODCollectionApp and save it to the Desktop. Then run it and upload the resulting zip file to a cloud service with a link to it here. The SysnativeBSODCollectionApp collects all the troubleshooting data we're likely to need. It DOES NOT collect any personally identifying data. It's used by several highly respected Windows help forums (including this one). I'm a senior BSOD analyst on the Sysnative forum where this tool came from, so I know it to be safe.

You can of course look at what's in the zip file before you upload it, most of the files are txt files. Please don't change or delete anything though. If you want a description of what each file contains you'll find that here.

In addition, look in the folder C:\Windows\LiveKernelReports. You may see several sub-folders, look in each sub-folder for dump files (.dmp) and upload all those that have a timestamp within the last month.

 

[Darkbreeze]

Sigh. More is better, but honestly, if we can just get the basic information, as we asked for it, we can usually figure out wtf is going on. When we can't, it's usually because we never got that information. Period.

 

[Khojo]

Nobody can access your logs without your OneDrive login info, which you should not share. Please post your full system specs HERE, as follows. Please provide EXACT model numbers for everything possible, not just, "8gb ram". Model numbers are sometimes very important.

CPU
Motherboard
RAM
Power supply (Exact model is 100% necessary)
Storage devices
Cooling devices
Case
Windows version
EXACT BIOS version

Intel Core i7-8700K ‎(BX80684I78700K)
ROG Strix Z370-E GAMING Motherboard
G.SKILL Trident Z RGB 4x8GB (F4-3200C16D-16GTZR)
EVGA Supernova 850W G3 (220-G3-0850)
ROG-STRIX-GTX1080TI-11G-GAMING
Thermaltake View 71 Tempered Glass RGB Edition (CA-1I7-00F1WN-01)
Thermaltake Floe Ring RGB 360
Windows 10 Home 64bit (22H2)
American Megatrends Inc. 1002, 7/2/2018

 

[Khojo]

Thanks for uploading the System log, it is a useful source of error and warning messages and does often help in diagnosing problems.

In your log I can see the many error 41 messages indicating that Windows wasn't shutdown properly, these will be the result of the restarts of which you complain. Whilst I do see several other error or warning messages that are of concern I don't see any error messages that can convincingly be said to be the cause of these restarts.

How does it restart? Does it power off and you have to restart it manually? Does it do an auto-restart on it's own? Does it do something else?

Have you checked temperatures yet? If not please download HWMonitor (free) and run that. Expand the CPU temperatures section so we can see every CPU core. Then post a screenshot of those temperatures when the PC has been completely idle for five minutes. Then post a second screenshot of those temperatures when you are working the CPU as hard as you possibly can.

It will be handy to see more troubleshooting data, so can you please download the SysnativeBSODCollectionApp and save it to the Desktop. Then run it and upload the resulting zip file to a cloud service with a link to it here. The SysnativeBSODCollectionApp collects all the troubleshooting data we're likely to need. It DOES NOT collect any personally identifying data. It's used by several highly respected Windows help forums (including this one). I'm a senior BSOD analyst on the Sysnative forum where this tool came from, so I know it to be safe.

You can of course look at what's in the zip file before you upload it, most of the files are txt files. Please don't change or delete anything though. If you want a description of what each file contains you'll find that here.

In addition, look in the folder C:\Windows\LiveKernelReports. You may see several sub-folders, look in each sub-folder for dump files (.dmp) and upload all those that have a timestamp within the last month.

When it restarts it just auto restarts on its own.

Idle Temps - CPU Temps Idle.jpg
Temps with OCCT CPU test running - CPU Temps OCCT Test.jpg

SysnativeFileCollectionApp.zip

There was nothing in the LiveKernelReports folder

 

[ubuysa]

It's not overheating then.

Your system drive (C) does not have a huge amount of free space. 43GB free on a 512GB drive isn't a lot. Things are likely OK now and I don't think this is a cause, but moving user data off that drive would be good.

I don't see anything else obvious in the uploaded data except that you're running a very old BIOS version. There have been 14 BIOS updates since your 1002 (2018) version. Whilst I'm not a fan of rushing to flash the BIOS I think that in your case that's a sensible place to start. See https://rog.asus.com/motherboards/rog-strix/rog-strix-z370-e-gaming-model/helpdesk_bios/

 

[Khojo]

It's not overheating then.

Your system drive (C) does not have a huge amount of free space. 43GB free on a 512GB drive isn't a lot. Things are likely OK now and I don't think this is a cause, but moving user data off that drive would be good.

I don't see anything else obvious in the uploaded data except that you're running a very old BIOS version. There have been 14 BIOS updates since your 1002 (2018) version. Whilst I'm not a fan of rushing to flash the BIOS I think that in your case that's a sensible place to start. See https://rog.asus.com/motherboards/rog-strix/rog-strix-z370-e-gaming-model/helpdesk_bios/

Went ahead and updated the BIOS and still ran into the same issue. The game I'm playing when the restarts occur is World of Warcraft. I've noticed that when I lower the graphic quality of the game all the way down to a 1, I don't seem to get the restarts. or at the very least they occur much less frequently.

 

[Darkbreeze]

The EVGA G3 PSU was terrible. I would suspect this is the problem. The G2 was very good. The G3, G4 and G5 were not. The G6 was better and the G7 was excellent, but things went south after the G2 because EVGA moved from Super Flower to a crappier builder. But, that's an assumption. Still, I'd start there. Besides which, a G3 has to be more than five years old now which is plenty old enough to be failing.

Obviously, testing is an option as well. Or, can do the HWinfo thing and see what the 12v, 5v and 3v readings are showing. It won't be as accurate as using a PSU tester or multimeter, but, can give at least an indication.

 

[Khojo]

The G3 was terrible. I would suspect this is the problem. The G2 was very good. The G3, G4 and G5 were not. The G6 was better and the G7 was excellent, but things went south after the G2 because EVGA moved from Super Flower to a crappier builder. But, that's an assumption. Still, I'd start there. Besides which, a G3 has to be more than five years old now which is plenty old enough to be failing.

Obviously, testing is an option as well. Or, can do the HWinfo thing and see what the 12v, 5v and 3v readings are showing. It won't be as accurate as using a PSU tester or multimeter, but, can give at least an indication.

Went ahead and replaced the PSU yesterday and it seems to have fixed the issue. Thank you

 

[Darkbreeze]

Nice.