F5F Stay Refreshed Hardware Desktop They're messing with my DRAM configurations!

They're messing with my DRAM configurations!

They're messing with my DRAM configurations!

F
ferus02
Junior Member
38
06-02-2016, 10:50 AM
#1
Hello, I've been experiencing strange BSODs possibly linked to the WHEA_UNCORRECTABLE postcode. Occasionally, I also saw IRQL errors. The issues began after I altered my RAM manually a year ago, staying within safe limits like 1.45v. I reset the BIOS defaults and even cleared CMOS at one point. Since then, I haven't had any crashes or reboots except when using a NVME SSD that showed many bad sectors, which I returned. Recently, after adjusting some IRQ settings using tools like Win Aero Tweaker or Ultimate Windows Tweaker, I faced repeated BSODs and reboots. I tried restoring my system but it didn't resolve the problem. I resolved it temporarily by turning on my IGPU and installing its drivers. A few days ago, the problems reappeared. I fixed it again after a fresh Windows install by changing the RAM voltage to 1.2v. Interestingly, when I disabled XMP (which should set it to 1.35 according to HWINFO), the voltage remained at 1.35 even though it was supposed to auto-adjust. I'm starting to suspect other settings or changes in my MOBO might be contributing to the instability.
F
ferus02
06-02-2016, 10:50 AM #1

Hello, I've been experiencing strange BSODs possibly linked to the WHEA_UNCORRECTABLE postcode. Occasionally, I also saw IRQL errors. The issues began after I altered my RAM manually a year ago, staying within safe limits like 1.45v. I reset the BIOS defaults and even cleared CMOS at one point. Since then, I haven't had any crashes or reboots except when using a NVME SSD that showed many bad sectors, which I returned. Recently, after adjusting some IRQ settings using tools like Win Aero Tweaker or Ultimate Windows Tweaker, I faced repeated BSODs and reboots. I tried restoring my system but it didn't resolve the problem. I resolved it temporarily by turning on my IGPU and installing its drivers. A few days ago, the problems reappeared. I fixed it again after a fresh Windows install by changing the RAM voltage to 1.2v. Interestingly, when I disabled XMP (which should set it to 1.35 according to HWINFO), the voltage remained at 1.35 even though it was supposed to auto-adjust. I'm starting to suspect other settings or changes in my MOBO might be contributing to the instability.

D
Dennis_ur
Junior Member
12
06-07-2016, 02:53 PM
#2
You've accomplished quite a lot, but it's tough to keep up. It seems you've used the same RAM sticks throughout? (Manipulating RAM without proper knowledge is risky—it usually leads to instability. Even using Ryzen's calculator is just an estimate.) Changing the voltage won't likely make a big difference. Instead, it might reset the motherboard's memory timings, which would vary each time. If I were dealing with this problem, I'd tackle it from the ground up. GPU drivers and a fresh install would help. Windows can cause odd behavior that affects performance, but it rarely triggers bluescreen issues—usually it's other processes crashing by accident, not critical system functions.
D
Dennis_ur
06-07-2016, 02:53 PM #2

You've accomplished quite a lot, but it's tough to keep up. It seems you've used the same RAM sticks throughout? (Manipulating RAM without proper knowledge is risky—it usually leads to instability. Even using Ryzen's calculator is just an estimate.) Changing the voltage won't likely make a big difference. Instead, it might reset the motherboard's memory timings, which would vary each time. If I were dealing with this problem, I'd tackle it from the ground up. GPU drivers and a fresh install would help. Windows can cause odd behavior that affects performance, but it rarely triggers bluescreen issues—usually it's other processes crashing by accident, not critical system functions.

P
164
06-07-2016, 10:10 PM
#3
I completely reinstalled Windows and updated all the drivers, including the newest manufacturer and MOBO updates. My approach so far has been to enable 1.2v for RAM while keeping XMP disabled, which now sets the frequency to its default of 15/15/15/36 at 1066mhz (2133mhz). XMP is set to 15/15/15/35 at 1600mhz (3200mhz) with a voltage of 3.15v. I also forgot to re-seat the RAM, moving it from slots A2 and B2 to A1 and B1—likely during some cleaning. I’m still unsure why my MOBO is reporting incorrect voltages when AUTO is enabled, which makes me worried about other potential issues.
P
PandaBearMan23
06-07-2016, 10:10 PM #3

I completely reinstalled Windows and updated all the drivers, including the newest manufacturer and MOBO updates. My approach so far has been to enable 1.2v for RAM while keeping XMP disabled, which now sets the frequency to its default of 15/15/15/36 at 1066mhz (2133mhz). XMP is set to 15/15/15/35 at 1600mhz (3200mhz) with a voltage of 3.15v. I also forgot to re-seat the RAM, moving it from slots A2 and B2 to A1 and B1—likely during some cleaning. I’m still unsure why my MOBO is reporting incorrect voltages when AUTO is enabled, which makes me worried about other potential issues.