Four sticks RAM and XMP result in BSOD.

Mar 18, 2018
43
0
30
0
Hello! I get BSOD at random when I run all four memory sticks, but if run just two sticks it runs fine. All four sticks run like they should,I tested all four sticks mixed match in all four slots. I ran a memory test and it did not find anything wrong. It could BSOD with in minutes of starting my PC or after a couple of hours of it running or at anytime in between. I can run XMP with only two sticks as well but if i have all four sticks installed it BSOD before i get two windows. The voltage of my CPU SA is at .808v I bumped it up to 1.1v and it BSOD before windows. I'm not sure what else to check or do to make this stop happening. Does anyone have anymore ideas?

PC
OS: Windows 10
Motherboard: MSI Z97S SLI Krait Edition LGA 1150 Intel Z97 HDMI SATA 6Gb/s USB 3.0 ATX Intel
GPU: NVIDIA GeForce GTX 970
CPU: Intel Core i7-4790K Devil's Canyon Quad-Core 4.0 GHz LGA 1150
RAM: G.SKILL Ripjaws X Series 16GB (4 x 8GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800) Desktop Memory Model F3-1600C9D-16GXM
PSU: Corsair RMx Series, RM850x, 850W, Fully Modular Power Supply, 80+ Gold Certified
HDD: 931GB Seagate ST1000DM003-1ER162 & 3726GB Seagate ST4000DM000-1F2168
 

Vic 40

Titan
Ambassador
Sticks didn't come as one set so this probably has to do with that.Mixing ram even when using the same sticks (=specs) from the same maker can give problems.Read the next,
http://www.tomshardware.com/reviews/ddr-dram-myths,4155.html#p4
look at "Just Adding More Dram".

What you can try is setting the Dram voltage to 1.65V,make sure that the "Command Rate" is set to 2T,see if that helps with stability. Make these changes with XMP enabled.Can also try and set rated settings manually if you're comfortable with that.
 
Mar 18, 2018
43
0
30
0

I tried what you suggested but I never made it pass the, "all settings were reset to default" error screen.
I also forgot to mention that I can't run 2133MHz with two stick sets either with XMP enable.
 

Vic 40

Titan
Ambassador

It's 1600mhz ram so don't even get why you would try 2133mhz. If knowing how to overclock ram would it maybe possible,but timings would need to be loosened.

With four sticks would i first try and settle for their tested speed,get that working.
 
Mar 18, 2018
43
0
30
0


I have a two other sticks that run at 2133MHz and they didn't work after i change the settings to fit with them, Also i am not a 100% confident on messing around in BIOS regarding the DRAM to make it stable. I ran the settings you suggested and i couldn't get it to work it just reset my BIOS settings everytime.
 
Mar 18, 2018
43
0
30
0
This was probably caused by the following module: ntkrnlmp.exe (nt!setjmpex+0x94B9)
Bugcheck code: 0x3B (0xC0000005, 0xFFFF8E0EC0291C5D, 0xFFFF800DAA5D3D50, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



The following dump files were found but could not be read. These files may be corrupt:
C:\WINDOWS\Minidump\040518-30062-01.dmp
 
add one clock tick to the command rate in the bios. then boot and run memtest86 to confirm the memory timings. IE commands rate set to 2N or 2T depending on what your bios uses to indicate clock rates.
http://www.gskill.com/en/product/f3-1600c9d-16gxm
Tested Latency 9-9-9-24-2N (the last number is the command rate, it is the number of clock cycles required for the memory address lines to become stable in the electronics)

often when you have one set of banks populated it will work at 1 clock tick but when you add a second set the circuit will require 2 clock ticks to allow the electronic signals to become stable.

here is the memory address in binary:
1111111111111111100011100000111011000000001010010001110001011101
when the circuit is sampled too early some of the bits will be read while they are changing from a 0 to 1 or 1 to 0 if that happens the wrong memory address will be decoded and the function will get a return code of 0xC0000005 (parameter one of the bugcheck code)

often bios vendors do not put in the correct bios defaults for 2n memory modules until after the motherboard ships. This is one of the reasons you would do a bios update to get better default timings.

 
Mar 18, 2018
43
0
30
0


The timings are correct. I did the MemTest86 with the settings you said, it did not find any errors, also I took pictures of the memory speed test. They're not the best quality but should work because I used the free version of MemTest86.

https://imgur.com/gallery/vBnW3

https://imgur.com/gallery/a1trl

https://imgur.com/gallery/HXxP9
 
Mar 18, 2018
43
0
30
0
It crashed twice before I got to start-up my PC this morning.

On Sun 4/8/2018 7:20:23 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\040818-27484-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x175510)
Bugcheck code: 0x50 (0xFFFFB08742CCDD12, 0x0, 0xFFFFF80081EE7F1D, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 4/8/2018 7:20:23 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: fltmgr.sys (FLTMGR!FltRemoveOpenReparseEntry+0x267)
Bugcheck code: 0x50 (0xFFFFB08742CCDD12, 0x0, 0xFFFFF80081EE7F1D, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\WINDOWS\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.
 
Mar 18, 2018
43
0
30
0


Should I change IO compensation ch1/ch2 and RTL in It value ch1/ch2 and ODT Fine tune ch1/ch2?

[Update] I can now boot my PC with OC Genie and XMP enabled. I'm going to run my pc without it enable to see if it will still BSOD
 
Mar 18, 2018
43
0
30
0
After running OC Genie and XMP for two days my PC failed to boot and then I had to turn off OC Genie and XMP now it boots up. After booting it up my PC looked as if it was the first time I ever booted it up. All my settings were changed and all of my files were gone and desktop was bare. I then restarted my PC and everything is back to normal except every time there is a sound it stutters and makes a brr sound.

It still hasn't BSOD since changing the Channel Interleaving but it still will not run OC Genie and XMP and I also have this brr sound when anything with sound is played and also skips .



I fixed the stuttering and burrp noise it was a Window update that needed a reboot
 
Mar 18, 2018
43
0
30
0
Windows made a growling sound as there was sound playing in the background and then my PC restarted. That is the first time that it did that and whoCrashed did not pick anything up when it did this.
 
Mar 18, 2018
43
0
30
0
On Thu 4/19/2018 3:54:08 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\041918-30062-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x175930)
Bugcheck code: 0xD1 (0xFFFF9742C0C49FF8, 0x2, 0x0, 0xFFFFF804580012C0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
 
Mar 18, 2018
43
0
30
0
Crashes at least once a day not at the same time of day. The last WhoCrashed summary is the same i keep getting over and over. The latest suggestion seemed to help but it did not last long as my PC said that the overclocking failed and it reset everything to default.
 
Mar 18, 2018
43
0
30
0
Wed 5/16/2018 2:24:52 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!setjmpex+0x87F9)
Bugcheck code: 0x7F (0x8, 0xFFFFCF813EA83050, 0xFFFFFA0090C2ACF0, 0xFFFFF802090E09AC)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.Double Fault, indicates that an exception occurs during a call to the handler for a prior exception. Most often this is caused by a software problem (kernel stack overflow) but this can also be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

This is a different one.
 

ASK THE COMMUNITY

TRENDING THREADS