F5F Stay Refreshed Hardware Desktop Your new PC is showing a blue screen and running very slowly.

Your new PC is showing a blue screen and running very slowly.

Your new PC is showing a blue screen and running very slowly.

Pages (3): Previous 1 2 3 Next
E
encoder92
Member
66
12-09-2022, 04:36 PM
#11
In theory it should work, but as @Mark Kaine mentioned, on Ryzen setups with DDR5, RAM might actually trigger a WHEA error.
E
encoder92
12-09-2022, 04:36 PM #11

In theory it should work, but as @Mark Kaine mentioned, on Ryzen setups with DDR5, RAM might actually trigger a WHEA error.

M
Minetoblend
Member
110
12-13-2022, 09:29 AM
#12
I believe relocating the NVMe SSD resolved the issue, though I'll find out more soon.
M
Minetoblend
12-13-2022, 09:29 AM #12

I believe relocating the NVMe SSD resolved the issue, though I'll find out more soon.

P
pepper52
Member
66
12-30-2022, 08:04 AM
#13
I've included it in this message. File reference: event files.evtx
P
pepper52
12-30-2022, 08:04 AM #13

I've included it in this message. File reference: event files.evtx

R
RedBoy002
Junior Member
31
01-05-2023, 03:37 PM
#14
It seems the fix worked because the NVME drive was placed in the second slot instead of the first.
R
RedBoy002
01-05-2023, 03:37 PM #14

It seems the fix worked because the NVME drive was placed in the second slot instead of the first.

T
TheAction1224
Junior Member
26
01-06-2023, 12:16 AM
#15
High EXPO speeds causing instability aren't valid since they overclock memory controllers, not RAM. RAM alone can't trigger this issue. He mentioned he disabled EXPO, but that doesn't explain it. Some EXPO profiles might have caused problems, while RAM errors won't produce WHEA messages. Refer to AMD's programming manual (volume 2) for details. The problem likely stems from registry changes or save failures. We should adjust the registry to investigate further.
T
TheAction1224
01-06-2023, 12:16 AM #15

High EXPO speeds causing instability aren't valid since they overclock memory controllers, not RAM. RAM alone can't trigger this issue. He mentioned he disabled EXPO, but that doesn't explain it. Some EXPO profiles might have caused problems, while RAM errors won't produce WHEA messages. Refer to AMD's programming manual (volume 2) for details. The problem likely stems from registry changes or save failures. We should adjust the registry to investigate further.

F
Foreverkim
Member
103
01-27-2023, 06:36 AM
#16
I assume you haven't used an MSI board or vengeance ram before. In any case, ram can cause these errors—it’s usually an incompatibility problem, not just a CPU or RAM issue. This kind of problem has been common since the AM4 era. Expo is simply XMP, and it's okay to refer to it that way.
F
Foreverkim
01-27-2023, 06:36 AM #16

I assume you haven't used an MSI board or vengeance ram before. In any case, ram can cause these errors—it’s usually an incompatibility problem, not just a CPU or RAM issue. This kind of problem has been common since the AM4 era. Expo is simply XMP, and it's okay to refer to it that way.

D
DarkTitanPT
Member
162
01-27-2023, 10:47 AM
#17
I repeatedly encountered WHEA (years back on AM4*) and it consistently pointed to "Nvidia GPU" as the issue... Initially, I thought that was unusual. However, upon checking, it turned out to be quite typical—some users attributed it to Wi-Fi problems, etc. At normal speeds my RAM errors vanished, though occasional random crashes remained. In short, that was just the start. Eventually, I decided to give up and purchased Gskill B-dies... No WHEA or crashes have occurred since then. It only crashed once after I overclocked it, but it worked afterward with the same settings. Still using the same machine even though everything changed or got updated. The original Windows 10 install from 2017 remains intact.
D
DarkTitanPT
01-27-2023, 10:47 AM #17

I repeatedly encountered WHEA (years back on AM4*) and it consistently pointed to "Nvidia GPU" as the issue... Initially, I thought that was unusual. However, upon checking, it turned out to be quite typical—some users attributed it to Wi-Fi problems, etc. At normal speeds my RAM errors vanished, though occasional random crashes remained. In short, that was just the start. Eventually, I decided to give up and purchased Gskill B-dies... No WHEA or crashes have occurred since then. It only crashed once after I overclocked it, but it worked afterward with the same settings. Still using the same machine even though everything changed or got updated. The original Windows 10 install from 2017 remains intact.

D
DeathRtH
Junior Member
15
01-31-2023, 09:51 PM
#18
D
DeathRtH
01-31-2023, 09:51 PM #18

I
IAmMelon
Junior Member
2
01-31-2023, 11:06 PM
#19
I've done more debugging than most. If you check my profile, I have a link to my reddit account which is almost exclusively on the tech support subreddit doing BSOD debugging. I also moderate their Discord. I am intimately familiar with BSODs and WHEA. AM4 had tons of memory controller issues related to voltages so I'm more inclined to think that's what you were seeing (Well, 5000 series did. 3000 series to some extent as well, but not as prevalent and it would more often give memory errors than CPU errors). I agree, but users get confused easily (Also EXPO technically has support for higher granularity for voltage settings, but it's a nitpick).
I
IAmMelon
01-31-2023, 11:06 PM #19

I've done more debugging than most. If you check my profile, I have a link to my reddit account which is almost exclusively on the tech support subreddit doing BSOD debugging. I also moderate their Discord. I am intimately familiar with BSODs and WHEA. AM4 had tons of memory controller issues related to voltages so I'm more inclined to think that's what you were seeing (Well, 5000 series did. 3000 series to some extent as well, but not as prevalent and it would more often give memory errors than CPU errors). I agree, but users get confused easily (Also EXPO technically has support for higher granularity for voltage settings, but it's a nitpick).

T
Thifleno
Member
206
02-01-2023, 03:12 AM
#20
I've reviewed the MCE documentation extensively, and I understand how WHEA functions. The CPER from the CPU plays a key role, along with internal components like BERT and the Boot Error Record Table. If Windows suspects an error in memory, it verifies the CPU's CPER first. When that fails, you typically encounter a 0x9C Machine_Check_Exception, except for specific cases after Windows XP where this exception is no longer active.
T
Thifleno
02-01-2023, 03:12 AM #20

I've reviewed the MCE documentation extensively, and I understand how WHEA functions. The CPER from the CPU plays a key role, along with internal components like BERT and the Boot Error Record Table. If Windows suspects an error in memory, it verifies the CPU's CPER first. When that fails, you typically encounter a 0x9C Machine_Check_Exception, except for specific cases after Windows XP where this exception is no longer active.

Pages (3): Previous 1 2 3 Next