Different BSODs after reclocking RAM at normal speed. (Win 10)

segarobot

Commendable
Feb 27, 2016
10
0
1,510
After about a year I realized that I have been running my 2133Mhz RAM (2x4gb) at 1333Mhz, so I changed the clock speed to 2133Mhz and set it to XMP. Ever since then I've been getting different blue screens usually when running a game. I ran WhoCrashed and got these:

On Mon 2/29/2016 4:13:14 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x41792, 0xFFFFF680002C0CE0, 0x400000000, 0x0)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 2/28/2016 2:35:05 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\022716-7859-01.dmp
This was probably caused by the following module: win32kfull.sys (win32kfull!fnHkINLPMSG+0x4C)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF961DDCDF81C, 0xFFFFD00152FB0B10, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32kfull.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Full/Desktop Win32k Kernel Driver
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 a standard 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.


On Sat 2/27/2016 11:38:45 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\022716-8031-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x139 (0x3, 0xFFFFD0002A6643B0, 0xFFFFD0002A664308, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


Motherboard: F2A85-v Pro
Video Card: R7 260x 2gb
RAM: Patriot Xtreme 2x4gb
CPU-Z Specs: Specs

Is there a way to fix this that doesn't involve clocking the RAM back down to 1333mhz?
note: I ran memtest and received no errors
 

segarobot

Commendable
Feb 27, 2016
10
0
1,510


I'm not sure what you meant by CPU/NB as I do not have an option for "CPU/NB" so I just rose the VDDNB to 1.3v because my CPU was already at 1.3v (and it's listed right with the cpu). I received a MEMORY_MANAGEMENT BSOD about an hour after running Counter-Strike. Sorry if I'm screwing this up I don't know a lot about this stuff. I took a screenshot of my bios so it'd be easier to tell me what to raise and such.
4dHhFTH.png

I did notice NB VREF but I don't know if that's what you wanted me to raise.
Thank you for your help, Tradesman.
 

segarobot

Commendable
Feb 27, 2016
10
0
1,510


I'm getting the same MEMORY_MANAGEMENT BSOD after changing the VDDNB... Hmm...
 

segarobot

Commendable
Feb 27, 2016
10
0
1,510


goOV6G9.jpg


Yessir, although I don't know what tRC and Command Rate are supposed to be at. I did have XMP enabled so it set all those for me but it seems to be right.