[SOLVED] BSOD's and crashes after RAM upgrade.

Sep 28, 2019
3
0
10
PC Specs: Ryzen 5 2600, 32GB DDR4 3200MHz Corsair Vengeange RGB, Aorus B450 PRO, EVGA SC2 GTX 1080 Ti.
I had a HyperX 2x4 kit that ran at 2133MHz and decided to upgrade since I couldn't stream or edit in AE so I decided to go with a Corsair Vengeange RGB 3200MHz kit 32GB. Since then most of my games keep crashing and sometimes I get BSOD's with the most common error code being IRQL NOT LESS OR EQUAL. I have tried multiple video tutorials on YouTube and none of them have helped me. I have ran memtest and got 2 errors within 10 minutes. I have also tried putting the speed of my RAM to 2933MHz and the voltage to 1.25V but no luck. I still get errors in memtest. When I turn on XMP I also get memory management BSOD's; sometimes I get a BSOD straight after logging in and after I restart everything works fine. I have been trying all sorts of YouTube video solutions but no luck for 4 weeks now.

Module 0:
DDR4, 8192 MB, 64-bit, 2933 MHz
DIMM 0 P0 CHANNEL A Unknown CMW32GX4M4C3200C16
Module 1:
DDR4, 8192 MB, 64-bit, 2933 MHz
DIMM 1 P0 CHANNEL A Unknown CMW32GX4M4C3200C16
Module 2:
DDR4, 8192 MB, 64-bit, 2933 MHz
DIMM 0 P0 CHANNEL B Unknown CMW32GX4M4C3200C16
Module 3:
DDR4, 8192 MB, 64-bit, 2933 MHz
DIMM 1 P0 CHANNEL B Unknown CMW32GX4M4C3200C16

0.000: Detecting usable memory (32718 MB theoretical max)...
32.312: 25344 MB Test starting on 12 CPUs...
32.312: Allocating memory...
52.031: Starting loop 1
52.031: Stuck Address Test...
57.437: Random Data Test...
64.984: Move Data Test...
67.250: Bitpattern Test...
219.718: Starting loop 2
219.718: Stuck Address Test...
225.062: Random Data Test...
229.625: Error at 30621CB
231.031: Move Data Test...
233.250: Bitpattern Test...
385.234: Starting loop 3
385.234: Stuck Address Test...
390.531: Random Data Test...
393.375: Error at FC47A55
398.140: Move Data Test...
400.359: Bitpattern Test...
420.328: Test finished with 2 errors

Errors: Error at 30621CB, Error at FC47A55
 
Solution
Start by running your RAM at default 2133 and see if your problems go away. If so, then check for a BIOS upgrade for your motherboard and update before trying faster RAM speeds.
Sep 28, 2019
3
0
10
Start by running your RAM at default 2133 and see if your problems go away. If so, then check for a BIOS upgrade for your motherboard and update before trying faster RAM speeds.
Hi! I have updated the BIOS the the newest version available. After I done that I turned on XMP and at first it all seemed fine until I booted into Windows and got a Memory Management BSOD right after I logged in so I went into the BIOS and set the voltage to 1.35V. After I did that everything worked fine, started memtest and got a blue screen within 2 minutes of starting the test.
 

kanewolf

Titan
Moderator
Hi! I have updated the BIOS the the newest version available. After I done that I turned on XMP and at first it all seemed fine until I booted into Windows and got a Memory Management BSOD right after I logged in so I went into the BIOS and set the voltage to 1.35V. After I did that everything worked fine, started memtest and got a blue screen within 2 minutes of starting the test.
With four DIMMs you may not be able to run faster than 2133. Check the memory support list for that motherboard. Not many DIMMs supported for four DIMMs.
 
Sep 28, 2019
3
0
10
With four DIMMs you may not be able to run faster than 2133. Check the memory support list for that motherboard. Not many DIMMs supported for four DIMMs.
I have done some more tweaking. Currently, I have been running memtest x86 for about 30 minutes and got no errors at 3200MHz. I have turned XMP off and manually set the voltage to 1.25V and the frequency to 3200MHz and it seems to work fine in memtest. I have not tried any games yet so after I do, Ill let you know. If they dont work I will also try some lower frequencies but just wondering, will upgrading the CPU and Motherboard help with this because I am considering a Ryzen 9 3900X and Asrock X570 motherboard.
UPDATE: One day later everything works fine. I think it was all because of how old my BIOS version was (over a year old). I went from BIOS version F2 to F42C so yeah, my BIOS was very outdated.
 
Last edited: