Question Random Reboots

[KLHill]

I started getting random reboots without warning. Sometimes I'll get several reboots in a row and sometimes I can go hours or days without a reboot. The reboots can occur from an idle state as well as a gaming state. Temps never exceed 40 to 50c on CPU or GPU. VRM runs around 60c. I did a complete reinstall of Win 11 and that seemed to fix it, but now I'm getting reboots again. The only utilities that I am running are GPU Tweak 3. XMP enabled in bios. Fan control via bios. Event Viewer Error 12/11/2023 12:02:02 PM BugCheck 1001 None

AMI Bios ver 2.21.1278 2022

All components were purchased and assembled July 2022
Asus ROG Strix Z590-E Gaming Wifi MB
Intel Core i9-11900k 5.3 GHz CPU (liquid cooled)
Corsair Vengeance RGB 64GB DDR3600
Samsung 980 Pro 500GB SSD (OS and Utilities)
Asus Strix RTX 3060 GPU
EVGA Supernova 1300w G+ 80+ PSU

 

[Lutfij]

Please post the specs to your afflicted system in the thread's body. Sig space specs can and will change over time and eventually render this thread and it's solution/suggestions moot to the person in the same boat as you're in now.

Random reboots can happen due to two things, often;
1| You have an overheating issue
2| Your PSU is incapable of powering all your components in your build.

Where did you source the installer for your OS? BIOS version for your OS? Age for your PSU? How are you cooling your processor?

 

[KLHill]

Asus ROG Strix Z590-E Gaming Wifi MB
Intel Core i9-11900k 5.3 GHz CPU (liquid cooled)
Corsair Vengeance RGB 64GB DDR3600
Samsung 980 Pro 500GB SSD (OS and Utilities)
Asus Strix RTX 3060 GPU
EVGA Supernova 1300w G+ 80+ PSU

Please post the specs to your afflicted system in the thread's body. Sig space specs can and will change over time and eventually render this thread and it's solution/suggestions moot to the person in the same boat as you're in now.

Random reboots can happen due to two things, often;
1| You have an overheating issue
2| Your PSU is incapable of powering all your components in your build.

Where did you source the installer for your OS? BIOS version for your OS? Age for your PSU? How are you cooling your processor?

Updated

 

[MrN1ce9uy]

Boot to BIOS and share what you see for +12V +5V and +3.3V readings.

 

[KLHill]

Boot to BIOS and share what you see for +12V +5V and +3.3V readings.

12.192, 5.080, 3.392, DRAM 1.361

 

[MrN1ce9uy]

12.192, 5.080, 3.392, DRAM 1.361

Looks good.

 

[ubuysa]

Are there any minidumps with relevant timestamps in the folder C:\Windows\Minidump? Upload any that you find.

Are there any dump files in any of the sub-folders under the folder C:\Windows\LiveKenrelReports? Upload any with relevant timestamps.

Please also export and upload your System and Application logs...

1. Enter the command eventvwr into the Run command box. The Event Viewer will open.
2. Locate the Windows Logs folder in the left hand pane and expand it by clicking on the arrow (>) to the left of it.
3. Right-click on the Application entry and select 'Save all events as...'. Choose a folder anywhere that suits you and a filename of 'Application' (an .evtx suffix will be added automatically).
4. Right-click on the System entry and select 'Save all events as...'. Choose a folder anywhere that suits you and a filename of 'System' (an .evtx suffix will be added automatically).
5. Upload Application.evtx and System.evtx to a cloud service with a link to them here.

Please be sure to make all uploaded files public (so that we don;t have to login to download them).

 

[KLHill]

Are there any minidumps with relevant timestamps in the folder C:\Windows\Minidump? Upload any that you find.

Are there any dump files in any of the sub-folders under the folder C:\Windows\LiveKenrelReports? Upload any with relevant timestamps.

Please also export and upload your System and Application logs...

1. Enter the command eventvwr into the Run command box. The Event Viewer will open.
2. Locate the Windows Logs folder in the left hand pane and expand it by clicking on the arrow (>) to the left of it.
3. Right-click on the Application entry and select 'Save all events as...'. Choose a folder anywhere that suits you and a filename of 'Application' (an .evtx suffix will be added automatically).
4. Right-click on the System entry and select 'Save all events as...'. Choose a folder anywhere that suits you and a filename of 'System' (an .evtx suffix will be added automatically).
5. Upload Application.evtx and System.evtx to a cloud service with a link to them here.

Please be sure to make all uploaded files public (so that we don;t have to login to download them).

Microsoft OneDrive

1drv.ms

 

[ubuysa]

All your reboots are related to either the graphics card or the graphics driver. The minidumps are different, some are VIDEO_TDR_FAILURE bugchecks, indicating a graphics hang that the Windows Timeout Detection and Recovery feature (TDR) was not able to recover, and some are SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M bugchecks caused by the graphics driver (nvlddmkm.sys) fouling up a memory pointer. This error can be clearly seen in the context record in dumps...

CONTEXT:  fffffa0b5eefd1e0 -- (.cxr 0xfffffa0b5eefd1e0)
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa0b5eefdb00
rdx=00000000000000e6 rsi=ffffaa8f67ad1000 rdi=0000000000000000
rip=fffff8057e854afa rsp=fffffa0b5eefdc00 rbp=fffffa0b5eefdd00
 r8=ffffe603977de1aa  r9=0000000000000022 r10=00000000ffffffff
r11=0000000000010490 r12=fffffa0b5eefde78 r13=fffffa0b5eefded0
r14=0000000004000000 r15=0000000000001100
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050246
nvlddmkm+0x1044afa:
fffff805`7e854afa 4c89b7b8000000  mov     qword ptr [rdi+0B8h],r14 ds:002b:00000000`000000b8=????????????????
Resetting default scope

At the bottom there you can see the nvlddmkm.sys driver referencing memory via the RDI register that doesn't exist (note the ????????????????) because the RDI register is all zeros. This is either an error in the driver code or a problem with the graphics card itself.

For all but one of your dumps (including the live kernel dumps) your graphics driver was dated 9th Nov 2023, but I can see in one of the later live kernel dumps that it' was updated to the 6th Dec 2023 version. If you're getting BSOD on two different driver versions then you should probably suspect the graphics card. I would initiall pop the RTX3060 out and reset it properly, also check any external power cable - at both ends.

You could also remove the RTX3060 and run on the Intel iGPU for a while - just to check whether or not it BSODs without the RTX3060.

 

[KLHill]

Microsoft OneDrive

1drv.ms

All your reboots are related to either the graphics card or the graphics driver. The minidumps are different, some are VIDEO_TDR_FAILURE bugchecks, indicating a graphics hang that the Windows Timeout Detection and Recovery feature (TDR) was not able to recover, and some are SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M bugchecks caused by the graphics driver (nvlddmkm.sys) fouling up a memory pointer. This error can be clearly seen in the context record in dumps...

CONTEXT:  fffffa0b5eefd1e0 -- (.cxr 0xfffffa0b5eefd1e0)
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa0b5eefdb00
rdx=00000000000000e6 rsi=ffffaa8f67ad1000 rdi=0000000000000000
rip=fffff8057e854afa rsp=fffffa0b5eefdc00 rbp=fffffa0b5eefdd00
 r8=ffffe603977de1aa  r9=0000000000000022 r10=00000000ffffffff
r11=0000000000010490 r12=fffffa0b5eefde78 r13=fffffa0b5eefded0
r14=0000000004000000 r15=0000000000001100
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050246
nvlddmkm+0x1044afa:
fffff805`7e854afa 4c89b7b8000000  mov     qword ptr [rdi+0B8h],r14 ds:002b:00000000`000000b8=????????????????
Resetting default scope

At the bottom there you can see the nvlddmkm.sys driver referencing memory via the RDI register that doesn't exist (note the ????????????????) because the RDI register is all zeros. This is either an error in the driver code or a problem with the graphics card itself.

For all but one of your dumps (including the live kernel dumps) your graphics driver was dated 9th Nov 2023, but I can see in one of the later live kernel dumps that it' was updated to the 6th Dec 2023 version. If you're getting BSOD on two different driver versions then you should probably suspect the graphics card. I would initiall pop the RTX3060 out and reset it properly, also check any external power cable - at both ends.

You could also remove the RTX3060 and run on the Intel iGPU for a while - just to check whether or not it BSODs without the RTX3060.

I kinda suspected it may have been a graphics issue. I reseated the card and cable. Crossing fingers that will do the trick. If it continues with the driver update that came out today, then I'll know its the card. If so, I'll see if I can't get a repair cheaper than a new one. At least now I know what the issue is. Thank you for sharing your expertise and time! Merry Christmas!