F5F Stay Refreshed Hardware Desktop System experiences unexpected shutdowns with an unrecoverable error message.

System experiences unexpected shutdowns with an unrecoverable error message.

System experiences unexpected shutdowns with an unrecoverable error message.

Pages (2): Previous 1 2
J
jdclay
Member
154
04-26-2022, 12:32 AM
#11
Visit C:\Windows\Minidump to see if any minidump files exist. If present, return to the Windows directory and transfer the Minidump folder to the Downloads folder (use your desktop if needed). Compress the copied folder and include it in a post. Please adhere strictly to instructions since Windows doesn't allow file changes there.
J
jdclay
04-26-2022, 12:32 AM #11

Visit C:\Windows\Minidump to see if any minidump files exist. If present, return to the Windows directory and transfer the Minidump folder to the Downloads folder (use your desktop if needed). Compress the copied folder and include it in a post. Please adhere strictly to instructions since Windows doesn't allow file changes there.

C
55
04-27-2022, 03:42 AM
#12
It looks like you're missing a Minidump directory.
C
carebearisboss
04-27-2022, 03:42 AM #12

It looks like you're missing a Minidump directory.

N
NinjagobobMC
Member
69
05-05-2022, 02:35 AM
#13
I'm leaning toward the CPU again. That quote about a bad CPU not booting seems accurate. A faulty CPU might start working fine but eventually lead to crashes or unexpected restarts. Have you attempted static overclocking yet?
N
NinjagobobMC
05-05-2022, 02:35 AM #13

I'm leaning toward the CPU again. That quote about a bad CPU not booting seems accurate. A faulty CPU might start working fine but eventually lead to crashes or unexpected restarts. Have you attempted static overclocking yet?

D
204
05-05-2022, 05:23 AM
#14
I didn't attempt static OC; I'll try it for the 3.8 to 4.0 range—are you referring to frequency in GHz? Edit: I just adjusted the CPU voltage to 1.2V and it appears to fail to boot (everything looks active but no display, not even BIOS). Edit 2: I managed to restart the PC by clearing the default settings via CMOS, then tested 1.2v voltage and 3.8GHz base clock, but it still doesn’t boot. Another point: I haven’t overclocked my machine, so I’m not very experienced with the risks involved. If you have a helpful guide to suggest, I’d appreciate it.
D
DoctorThaddeus
05-05-2022, 05:23 AM #14

I didn't attempt static OC; I'll try it for the 3.8 to 4.0 range—are you referring to frequency in GHz? Edit: I just adjusted the CPU voltage to 1.2V and it appears to fail to boot (everything looks active but no display, not even BIOS). Edit 2: I managed to restart the PC by clearing the default settings via CMOS, then tested 1.2v voltage and 3.8GHz base clock, but it still doesn’t boot. Another point: I haven’t overclocked my machine, so I’m not very experienced with the risks involved. If you have a helpful guide to suggest, I’d appreciate it.

J
jaefrh
Member
180
05-05-2022, 06:48 AM
#15
You can customize the BSOD display by adding information to the registry. If you're unsure about editing it yourself, skip that step. Go to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\CrashControl, click on the empty space, choose New → DWORD value and name it "DisplayParameters". Set its value to 1 in either hex or decimal format. After saving, reboot to see the extra details appear on the screen. For more guidance, refer to the instructions on changing dump type and the tips for adjusting the restart behavior. If you need a visual reference, let me know.
J
jaefrh
05-05-2022, 06:48 AM #15

You can customize the BSOD display by adding information to the registry. If you're unsure about editing it yourself, skip that step. Go to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\CrashControl, click on the empty space, choose New → DWORD value and name it "DisplayParameters". Set its value to 1 in either hex or decimal format. After saving, reboot to see the extra details appear on the screen. For more guidance, refer to the instructions on changing dump type and the tips for adjusting the restart behavior. If you need a visual reference, let me know.

B
buckeree3
Member
81
05-05-2022, 10:46 AM
#16
I'm working on this now. Enabling "DisplayParameter" didn't trigger the crash, possibly due to an update after reboot. I'll keep you posted.
B
buckeree3
05-05-2022, 10:46 AM #16

I'm working on this now. Enabling "DisplayParameter" didn't trigger the crash, possibly due to an update after reboot. I'll keep you posted.

Pages (2): Previous 1 2