Question Constant BSOD after adding 2 more sticks of identical RAM

monz87

Distinguished
Apr 14, 2011
42
0
18,530
0
Hi guys,

For years I've had a pair of 4GB G Skill Ripjaw X 2133Mhz DDR3 RAM with XMP profile 1 at 2133Mhz running without issue.

I've just bought another 2 identical 4GB sticks from ebay to take it to 16GB.

However now I keep getting BSOD and the main culprit is ntoskrnl.exe.

I have gone through memtest and there are no errors.

Memory 16356M (22973 MB/s)
DIMM Slot #0 4GB DDR3 XMP PC3-17000
G Skill Intl / F3-17000CL11-4GBXL
11-11-11-30 / 2134 MHz / 1.600V
DIMM Slot #1 4GB DDR3 XMP PC3-17000
G Skill Intl / F3-17000CL11-4GBXL
11-11-11-30 / 2134 MHz / 1.600V
DIMM Slot #2 4GB DDR3 XMP PC3-17000
G Skill Intl / F3-17000CL11-4GBXL
11-11-11-30 / 2134 MHz / 1.600V
DIMM Slot #3 4GB DDR3 XMP PC3-17000
G Skill Intl / F3-17000CL11-4GBXL
11-11-11-30 / 2134 MHz / 1.600V


Test 0 [Address test, walking ones, 1 CPU] 4/4 (100%) 0
Test 1 [Address test, own address, 1 CPU] 4/4 (100%) 0
Test 2 [Address test, own address] 4/4 (100%) 0
Test 3 [Moving inversions, ones & zeroes] 4/4 (100%) 0
Test 4 [Moving inversions, 8-bit pattern] 4/4 (100%) 0
Test 5 [Moving inversions, random pattern] 4/4 (100%) 0
Test 6 [Block move, 64-byte blocks] 4/4 (100%) 0
Test 7 [Moving inversions, 32-bit pattern] 4/4 (100%) 0
Test 8 [Random number sequence] 4/4 (100%) 0
Test 9 [Modulo 20, ones & zeros] 4/4 (100%) 0
Test 10 [Bit fade test, 2 patterns, 1 CPU] 4/4 (100%) 0
Test 13 [Hammer test] 4/4 (100%) 0


Any thoughts?

Windows 10 Home - i7 4770k Stock - CM Hyper 212 Evo - Samsung 840 250GB SSD - WD 1TB Blue HDD - G-Skill 16GB Ripjaws X DDR3 2133Mhz - Gigabyte z87x-UD4H Bios Version F9 - Corsair TX750M - Sapphire 7950 Vapor-X 3GB - CM 690 II Advanced B&W - Dell U2715H - LG 49UH770V
 
Last edited:

Lutfij

Titan
Moderator
When posting a thread f troubleshooting nature, it's customary to include the specs to your build. Please list them like so:
CPU:
Motherboard:
Ram:
SSD/HDD:
GPU:
PSU:
Chassis:
OS:

If your specs are that which are listed in your sig space, it's suggested that you include them in the body of your thread. Reasoning behind that is due to the fact that sig space specs can and will change over time, meaning that this thread and it's relevant suggestions will be moot to an end user in the same boat as you(once were).

That out of the way, check and report what BIOS version you're currently on. See if manually setting voltage in BIOS to 1.65v helps.
 

monz87

Distinguished
Apr 14, 2011
42
0
18,530
0
When posting a thread f troubleshooting nature, it's customary to include the specs to your build. Please list them like so:
CPU:
Motherboard:
Ram:
SSD/HDD:
GPU:
PSU:
Chassis:
OS:

If your specs are that which are listed in your sig space, it's suggested that you include them in the body of your thread. Reasoning behind that is due to the fact that sig space specs can and will change over time, meaning that this thread and it's relevant suggestions will be moot to an end user in the same boat as you(once were).

That out of the way, check and report what BIOS version you're currently on. See if manually setting voltage in BIOS to 1.65v helps.
Ok so I have done this, and I noticed that I was on an older BIOS version F3 and have updated it to the latest non beta F9 version. I didn't find any change log for the updates though.

I will monitor and report back.
 

monz87

Distinguished
Apr 14, 2011
42
0
18,530
0
So far since updating the BIOS I have still not had any BSOD and it's been a few days. When it was happening it was frequent. I will still monitor for any infrequent crashes.
 

monz87

Distinguished
Apr 14, 2011
42
0
18,530
0
So I was just watching a Youtube video and all of a sudden got a BSOD. This is the log:

On Tue 10/03/2020 10:06:54 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\031020-52140-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C1510)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF8026C0626F8)
Error: 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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
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.


On Tue 10/03/2020 10:06:54 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl!TraceDxgkDevice+0xFE48)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF8026C0626F8)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
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 a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.


Any ideas?
 

monz87

Distinguished
Apr 14, 2011
42
0
18,530
0
The RAM is already running at 1.6v for the 2133Mhz speed. Its only rated for 1.5-1.6. Won't increasing it to 1.65v create further issues or crashes etc?
 

monz87

Distinguished
Apr 14, 2011
42
0
18,530
0
Ok so it hasn't crashed anymore since then. If it does I will try and increase the volts. What if I dial it down to 1600Mhz with no XMP applied, would that be better?
 
Dropping it down to 1600 will also decrease voltage to 1.5 volt.
Give it a shot if you are totally afraid of raising the ram voltage slightly above 1.6. odd that your bios only has .5v adjustments.
Although you may need to raise voltage slightly above 1.5 to get 4 sticks stable.
 

monz87

Distinguished
Apr 14, 2011
42
0
18,530
0
So I've taken it to 1600Mhz at 1.5v after a crash today and will monitor. If it still happens I will up the voltage on 1600Mhz to say 1.55v or 1.6v as the sticks are rated for up to 1.6v anyway and that way it will be the same logic as 2133Mhz at 1.65 volts.
 

ASK THE COMMUNITY

TRENDING THREADS