Question Custom build reboots randomly ?

[works_arc]

Build Specs
Mobo: ASUS X670E-PRO-WIFI
CPU: AMD RYZEN 9 7950X3D
GPU: NVIDIA GEFORCE RTX 4090 24GB
OS: Windows 11


Over the past week, a strange phenomenon has been cropping up. Randomly, even when not using a program, the build goes through a reboot but the power button is always illuminated. The machine is not OC'd and had been performing super well. We ran a drivers update right before the issues begin and I thought that this may be an explanation, but I am not finding this happening to anyone else online.

Also probably unrelated, when I try to adjust my background I get a message saying this:
"No product key for Windows can be found"

Where do I begin, Flash the BIOS ?

 

[ohio_buckeye]

What psu are you using? If I recall the 4090 can have large power spikes.

 

[Ralston18]

Look in Reliability History/Monitor and Event Viewer.

Either one or both tools may be capturing some error code, warning, or even an informational event just before or at the time of the reboots.

 

[works_arc]

What psu are you using? If I recall the 4090 can have large power spikes.

I knew that I left something critical out - I am using EVGA SUPERNOVA 1600P

 

[works_arc]

Look in Reliability History/Monitor and Event Viewer.

Either one or both tools may be capturing some error code, warning, or even an informational event just before or at the time of the reboots.

At the moment, it won't stay on long enough to do much of anything.

 

[works_arc]

OK - its definitely shutting off, the user was mistaken. The power button just stays illuminated.

 

[williamjeremiah]

We ran a drivers update right before the issues begin

If the chipset driver was included within the updates, while not having the latest BIOS, I'd say update the BIOS.

 

[works_arc]

If the chipset driver was included within the updates, while not having the latest BIOS, I'd say update the BIOS.

We ran nvidia GPU drivers. On me for not being more specific.

 

[williamjeremiah]

We ran nvidia GPU drivers. On me for not being more specific.

Boot into safe mode and use Display Driver Uninstaller (www.wagnardsoft.com) to remove the graphics drivers. Then reinstall the driver and see if the issue persists.

 

[works_arc]

Boot into safe mode and use Display Driver Uninstaller (www.wagnardsoft.com) to remove the graphics drivers. Then reinstall the driver and see if the issue persists.

Got it - I’ll report back tomorrow. Friday evening calls.

 

[Ralston18]

And if you are able to boot into Safe Mode then you should be able to check Reliability History/Monitor and Event Viewer.

 

[SkyNetRising]

OK - its definitely shutting off, the user was mistaken. The power button just stays illuminated.

Shutting off - means either overheating - check cpu temperatures;
or PSU protections are getting triggered.

Faulty high power GPU can trip PSU protections or PSU itself could be faulty.
Try with a different GPU;
Try with a different PSU.

 

[works_arc]

And if you are able to boot into Safe Mode then you should be able to check Reliability History/Monitor and Event Viewer.

The machine seems stable, suddenly, after attempting a start in safe mode. I was able to access troubleshoot but I clicked restart, it went to the bitlocker screen and rebooted windows to the desktop. It has been stable now for ~15 minutes and I was able to access the event viewer. Here are some of the most recent administrative events:

Windows Hello for Business provisioning will not be launched.

Device is Microsoft Entra joined (or hybrid joined): Not Tested

User has logged on with Microsoft Entra credentials: No

Windows Hello for Business policy is enabled: Not Tested

Windows Hello for Business post-logon provisioning is enabled: Not Tested

Local computer meets Windows hello for business hardware requirements: Not Tested

User is not connected to the machine via Remote Desktop: Yes

User certificate for on premise auth policy is enabled: Not Tested

Machine is governed by none policy.

Cloud trust for on premise auth policy is enabled: Not Tested

User account has Cloud to OnPrem TGT: Not Tested

See https://go.microsoft.com/fwlink/?linkid=832647 for more details.





The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID

{F87B28F1-DA9A-4F35-8EC0-800EFCF26B83}

and APPID

{0868DC9B-D9A2-4F64-9362-133CEA201299}

to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.



Function: CNetEnvironment::logProbeFailure

File: C:\temp\build\thehoff\Raccoon_MR50.78933656813\Raccoon_MR5\vpn\Agent\NetEnvironment.cpp

Line: 1751

Invoked Function: CHttpProbeAsync::SendProbe

Return Code: -27000818 (0xFE64000E)

Description: HTTP_PROBE_ASYNC_ERROR_CANNOT_CONNECT

HTTP (host: 72.163.1.80)



Function: PreferenceMgr::invokePreferenceUpdateCBs

File: C:\temp\build\thehoff\Raccoon_MR50.78933656813\Raccoon_MR5\vpn\Api\PreferenceMgr.cpp

Line: 1756

Callback interface address set is empty.









License Activation (slui.exe) failed with the following error code:

hr=0x80004005

Command-line arguments:

RuleId=31e71c49-8da7-4a2f-ad92-45d98a1c79ba;Action=AutoActivate;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=221a02da-e2a1-4b75-864c-0a4410a33fdf;NotificationInterval=1440;Trigger=UserLogon;SessionId=1







Function: CThread::invokeRun

File: C:\temp\build\thehoff\Raccoon_MR50.78933656813\Raccoon_MR5\vpn\Common\Utility\Thread.cpp

Line: 500

Invoked Function: IRunnable::Run

Return Code: -32112629 (0xFE16000B)

Description: BROWSERPROXY_ERROR_NO_PROXY_FILE





Function: CNetEnvironment::testNetwork

File: C:\temp\build\thehoff\Raccoon_MR50.78933656813\Raccoon_MR5\vpn\Agent\NetEnvironment.cpp

Line: 1029

Invoked Function: CNetEnvironment::IsSGAccessible

Return Code: -28901363 (0xFE47000D)

Description: NETENVIRONMENT_ERROR_PROBE_INCOMPLETE:Network Probe could not contact target



Function: CNetEnvironment::TestAccessToSG

File: C:\temp\build\thehoff\Raccoon_MR50.78933656813\Raccoon_MR5\vpn\Agent\NetEnvironment.cpp

Line: 1678

Invoked Function: CNetEnvironment::analyzeHttpResponse

Return Code: -28901363 (0xFE47000D)

Description: NETENVIRONMENT_ERROR_PROBE_INCOMPLETE:Network Probe could not contact target

 

[works_arc]

And if you are able to boot into Safe Mode then you should be able to check Reliability History/Monitor and Event Viewer.

And here is what I could find in the reliability monitor.


Description

A problem with your hardware caused Windows to stop working correctly.



Problem signature

Problem Event Name:     LiveKernelEvent

Code: 141

Parameter 1:      ffffe78f2572b010

Parameter 2:      fffff80254b46740

Parameter 3:      0

Parameter 4:      ffffe78f233e8080

OS version: 10_0_26100

Service Pack:     0_0

Product:    256_1

OS Version: 10.0.26100.2.0.0.256.48

Locale ID:  1033



Files that help describe the problem

WATCHDOG-20250531-1119.dmp

sysdata.xml

WERInternalMetadata.xml

memory.csv

sysinfo.txt

WERInternalRequest.xml



View a temporary copy of these files

Warning: If a virus or other security threat caused the problem, opening a copy of the files could harm your computer.





Description

A problem with your hardware caused Windows to stop working correctly.



Problem signature

Problem Event Name:     LiveKernelEvent

Code: 1b8

Parameter 1:      a

Parameter 2:      0

Parameter 3:      0

Parameter 4:      0

OS version: 10_0_26100

Service Pack:     0_0

Product:    256_1

OS Version: 10.0.26100.2.0.0.256.48

Locale ID:  1033



Files that help describe the problem

WATCHDOG4400-20250531-1119.dmp

sysdata.xml

WERInternalMetadata.xml

memory.csv

sysinfo.txt

WERInternalRequest.xml



View a temporary copy of these files

Warning: If a virus or other security threat caused the problem, opening a copy of the files could harm your computer.







Description

A problem with your hardware caused Windows to stop working correctly.



Problem signature

Problem Event Name:     LiveKernelEvent

Code: 1b8

Parameter 1:      a

Parameter 2:      0

Parameter 3:      0

Parameter 4:      0

OS version: 10_0_26100

Service Pack:     0_0

Product:    256_1

OS Version: 10.0.26100.2.0.0.256.48

Locale ID:  1033



Files that help describe the problem

WATCHDOG4401-20250531-1119.dmp

sysdata.xml

WERInternalMetadata.xml

memory.csv

sysinfo.txt

WERInternalRequest.xml



View a temporary copy of these files

Warning: If a virus or other security threat caused the problem, opening a copy of the files could harm your computer.

 

[works_arc]

Shutting off - means either overheating - check cpu temperatures;
or PSU protections are getting triggered.

Faulty high power GPU can trip PSU protections or PSU itself could be faulty.
Try with a different GPU;
Try with a different PSU.

Using CoreTemp. My Idle is 45-48. I launched PerformanceTest and it operated well until it didn't and crashed. Temp range though was routinely between 56-61.

 

[works_arc]

Boot into safe mode and use Display Driver Uninstaller (www.wagnardsoft.com) to remove the graphics drivers. Then reinstall the driver and see if the issue persists.

Unable to boot into safe mode, I need our third party IT group to provide the Bitlocker key.

 

[works_arc]

SOLUTION - I navigated over to MSI Afterburner just for the heck of it and I was unable to find the 4090 GPU, only the AMD integrated card was listed. I then opened device manager and disabled the AMD integrated card and now everything is working great. My supposition is that the AMD card was overriding the Nvidia as the default/go-to and the CPU was overheating. Sound crazy?

 

[Teknoman2]

SOLUTION - I navigated over to MSI Afterburner just for the heck of it and I was unable to find the 4090 GPU, only the AMD integrated card was listed. I then opened device manager and disabled the AMD integrated card and now everything is working great. My supposition is that the AMD card was overriding the Nvidia as the default/go-to and the CPU was overheating. Sound crazy?

Probable if you dont' have a good enough cooler. Best to disable the iGPU from the bios to completely turn it off.

 

[works_arc]

Probable if you dont' have a good enough cooler. Best to disable the iGPU from the bios to completely turn it off.

Could be - I am using the Noctua NH-U12S.

 

[Teknoman2]

Way too little cooling for that CPU. That cooler is barely good enough for a 7700X