F5F Stay Refreshed Hardware Desktop Is my custom computer restarting on its own?

Is my custom computer restarting on its own?

Is my custom computer restarting on its own?

Pages (2): Previous 1 2
C
CheezBurgerzz
Member
202
09-23-2026, 02:24 PM
#11
If you can get your computer running in safe mode, you might want to look at the reliability history or monitor it, along with event viewer.
C
CheezBurgerzz
09-23-2026, 02:24 PM #11

If you can get your computer running in safe mode, you might want to look at the reliability history or monitor it, along with event viewer.

N
nc432
Member
186
09-23-2026, 08:47 PM
#12
Turning things down - probably because it's getting too hot, so check your CPU temps. Or maybe the power supply is being triggered by its own safety checks. A bad high-power GPU might do that to you, or the PSU itself could just be broken. Try swapping out the GPU; try swapping out the PSU.
N
nc432
09-23-2026, 08:47 PM #12

Turning things down - probably because it's getting too hot, so check your CPU temps. Or maybe the power supply is being triggered by its own safety checks. A bad high-power GPU might do that to you, or the PSU itself could just be broken. Try swapping out the GPU; try swapping out the PSU.

B
Bulldog1245
Junior Member
15
09-24-2026, 02:32 PM
#13
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
B
Bulldog1245
09-24-2026, 02:32 PM #13

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

H
HermanZ07
Member
194
09-26-2026, 03:04 AM
#14
Here is what I found in my reliability monitor. A problem with your hardware made Windows not work right. 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.
H
HermanZ07
09-26-2026, 03:04 AM #14

Here is what I found in my reliability monitor. A problem with your hardware made Windows not work right. 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.

J
Jacoby_23
Junior Member
48
09-26-2026, 04:25 AM
#15
I used CoreTemp to check my idle speed, which was around 45 to 48 percent. Then I ran a PerformanceTest, but the program kept crashing instead of running well. My temperature stayed high, usually hitting 56 to 61 degrees Celsius.
J
Jacoby_23
09-26-2026, 04:25 AM #15

I used CoreTemp to check my idle speed, which was around 45 to 48 percent. Then I ran a PerformanceTest, but the program kept crashing instead of running well. My temperature stayed high, usually hitting 56 to 61 degrees Celsius.

T
the5harkman
Senior Member
542
09-26-2026, 08:37 AM
#16
I can't start up properly and I have to ask my third-party IT team for my BitLocker password to fix it.
T
the5harkman
09-26-2026, 08:37 AM #16

I can't start up properly and I have to ask my third-party IT team for my BitLocker password to fix it.

G
Geocentric
Senior Member
250
09-29-2026, 04:47 AM
#17
I checked MSI Afterburner to see if my 4090 showed up, but it didn't. Instead, only an AMD integrated card appeared on the screen. I went into Device Manager and turned off that AMD card so the Nvidia could take over. Now everything is running perfectly fine. My guess was that the AMD card was taking the lead as the default choice and making my CPU too hot. Does that sound wild?
G
Geocentric
09-29-2026, 04:47 AM #17

I checked MSI Afterburner to see if my 4090 showed up, but it didn't. Instead, only an AMD integrated card appeared on the screen. I went into Device Manager and turned off that AMD card so the Nvidia could take over. Now everything is running perfectly fine. My guess was that the AMD card was taking the lead as the default choice and making my CPU too hot. Does that sound wild?

D
DeiFilium
Member
110
09-29-2026, 06:43 AM
#18
If you don't have a really cool computer, then try turning off your graphics card. It's easier to do this in your BIOS settings so that your picture screen stops working completely.
D
DeiFilium
09-29-2026, 06:43 AM #18

If you don't have a really cool computer, then try turning off your graphics card. It's easier to do this in your BIOS settings so that your picture screen stops working completely.

T
TitoEnri_69
Junior Member
1
Today, 07:32 AM
#19
It might work with my Noctua NH-U12S.
T
TitoEnri_69
Today, 07:32 AM #19

It might work with my Noctua NH-U12S.

Pages (2): Previous 1 2