Help needed with computer crashing randomly, instability issues

[gantugsmk]

My computer has been crashing for a while now with the error WHEA_UNCORRECTABLE_ERROR, and I'm sick of it!

It crashes when I try to do any resource intensive tasks like AI training, even gaming sometimes (crashes when I enter CS2 and Euro Truck Simulator 2).

It's a pretty janky computer, so is it any problem that's related to my PSU? (it's a cheap 600w PSU)

 

Below is the errors right when the computer crashed:

Error 1, 2, 4 - The inpoutx64 service could not be started due to the following error: "The requested service cannot be completed due to lack of system resources. The requested service cannot be completed due to lack of system resources.

inpoutx64 サービスを、次のエラーが原因で開始できませんでした: システム リソースが不足しているため、要求されたサービスを完了できません。

Error 3 - Secure boot update failed. Secure boot is not enabled on this computer. The Secure Boot variable could not be updated at for more information, see https://go.microsoft.com/fwlink/?linkid=2169931 

セキュア ブートの更新はエラー このコンピューターでセキュア ブートが有効になっていません。 でセキュア ブート変数を更新できませんでした。詳細については、https://go.microsoft.com/fwlink/?linkid=2169931  を参照してください

Error 5 - Creation of dump file failed due to an error during dump creation.

ダンプ作成中のエラーのため、ダンプ ファイルの作成が失敗しました。

Error 6 - Previous system shutdown ( 7/15/2024 3:54:42 PM) was not expected.

以前のシステム シャットダウン ( ‎7/‎15/‎2024 3:54:42 PM) は予期されていませんでした。

I believe this is insufficient, so how can I dump more errors to a log file or something? 

 

Also, after crashing, the SSD did not get recognized until I did a power cycle. 

SysnativeFileCollectionApp.zip

 

• OS - Windows 10
• Ryzen 7 1700 2.9GHz
• What OS was originaly installed on the system? - Windows 11
• Not an OEM system
• Probably 5-7 years (hardware)
• I do reset my PC every 4 months or so.
• RX5600XT XFX (it was a mining card)
• ROG B350F motherboard
• 600w sketchy PSU with no legible writing (it was all in chinese)
• Prebuilt, bought most components second-hand
• Desktop

[gantugsmk]

Also, i'll dump a sysnative bsod tool log down below within an hour or something.

 

[podkall]

What PSU exactly?

[gantugsmk]

1 hour ago, podkall said:

What PSU exactly?

No name chinese PSU. I couldnt even search it.

[gantugsmk]

I included the dump file below.

 

SysnativeFileCollectionApp.zip

[Bjoolz]

7 hours ago, gantugsmk said:

I included the dump file below.

 

SysnativeFileCollectionApp.zip 1.86 MB · 2 downloads

This did not include any dump files. Could you check for them manually? Go to C:\Windows\Minidump and check if you have any minidump files. If you do, go back to the Windows folder and copy the Minidump folder itself to the Downloads folder (You can use the desktop if you don't have OneDrive syncing files). Zip the copied folder and attach it to a post. Please follow the instructions to the letter as Windows doesn't like you messing with files in this location.

 

WHEA means a hardware issue with the CPU or a PCIe device. Or at least it did until Microsoft duct taped NVMe storage onto WHEA (Yes, I know NVMe is on PCIe, but PCIe has a separate error code from NVMe). No dump file + WHEA is usually a faulty NVMe SSD.

 

We need to see the arguments of the BSOD crash (Think of them as sub-errors). If it already hangs on the BSOD screen (As you can't get dump files) then this step is not necessary, but if it reboots normally after a few seconds then go to this guide and on this screen remove the check for automatically restart. To restart manually, just use the power button.

 

To make the BSOD screen display the additional info on the BSOD screen we need to add a field to the registry. If you are not comfortable editing the registry then do not do this step. Navigate to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\CrashControl, right click on the empty area on the right section and select New → DWORD value with the name "DisplayParameters". Right click on it, modify and set the value data to 1 (Does not matter if you use Hexadecimal or Decimal). It should look like this once done. Reboot to apply the registry change.

 

The next time you BSOD, you should have these extra numbers in the top left corner. I want a picture of this, but if Arg 1 is 0x0000000000000010 then it's blaming the NVMe SSD. Because NVMe errors are driver reported and not hardware reported it could be the SSD, the M.2 slot, the motherboard or even a corrupted storage driver. 

 

Note that this is only applicable to WHEA_Uncorrectable_Error BSODs.