[SOLVED] BSOD while gaming with my newly built pc

Jan 24, 2020
15
0
10
0
I recently build a new pc and overclocked it and I ran into a crash while playing a game, I am no expert on overclocking so I'm not sure where I went wrong here any help is appreciated.
my specs are...

CPU: Intel Core i9 9900KF (with Dark rock pro 4 cooler)
MB: MSI MPG Z390 gaming edge AC
RAM: G.SKILL Ripjaws V 16gb (2x8 GB) ddr4 3600
GPU: EVGA Geforce RTX 2070 SUPER BLACK GAMING 8GB
PSU: Corsair RM850x
Storage: Intel 660p 1TB m.2

I overclocked the i9 to 5ghz all cores @1.31v adaptive and enabled xmp mode. My BIOS is up to date (A.60) and so is my graphics drivers, I've ran system file checker and Memtest86 and there were no errors. I did a stress test with cinebench and cpu-z as well as prime95 small ffts and blend but no crashes or problems.

here's my crash dump below

Microsoft (R) Windows Debugger Version 10.0.19528.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\grego\Desktop\012320-6531-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


Path validation summary *
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff80669400000 PsLoadedModuleList = 0xfffff80669848150
Debug session time: Thu Jan 23 19:52:17.611 2020 (UTC - 8:00)
System Uptime: 4 days 3:07:00.997
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.....
Loading User Symbols
Loading unloaded module list
..................................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff806695c14e0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffa180592e1710=000000000000000a
7: kd> !analyze -v
***
  • *
  • Bugcheck Analysis *
  • *
***

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: ffffd029f11f4b13, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: ffffd029f11f4b13, address which referenced memory

Debugging Details:
------------------


KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 1

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on GREGPC1

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 1

Key : Analysis.Memory.CommitPeak.Mb
Value: 70

Key : Analysis.System
Value: CreateObject


ADDITIONAL_XML: 1

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

BUGCHECK_CODE: d1

BUGCHECK_P1: ffffd029f11f4b13

BUGCHECK_P2: 2

BUGCHECK_P3: 8

BUGCHECK_P4: ffffd029f11f4b13

READ_ADDRESS: fffff806699733b8: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff8066982a3c8: Unable to get Flags value from nt!KdVersionBlock
fffff8066982a3c8: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
ffffd029f11f4b13

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: dwm.exe

TRAP_FRAME: ffffa180592e1850 -- (.trap 0xffffa180592e1850)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff80669eb90b0 rbx=0000000000000000 rcx=ffffa180592e1b50
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=ffffd029f11f4b13 rsp=ffffa180592e19e8 rbp=0000000000000001
r8=0000000000000008 r9=0000000000000000 r10=fffff80669eb9070
r11=ffff800199fb9180 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
ffffd029f11f4b13 ?? ???
Resetting default scope

FAILED_INSTRUCTION_ADDRESS:
+0
ffffd029f11f4b13 ?? ???

STACK_TEXT:
ffffa180592e1708 fffff806695d32e9 : 000000000000000a ffffd029f11f4b13 0000000000000002 0000000000000008 : nt!KeBugCheckEx
ffffa180592e1710 fffff806695cf62b : 0000000000000000 ffffc0832e6147e0 ffffc08330ac9630 ffffc08330ac9570 : nt!KiBugCheckDispatch+0x69
ffffa180592e1850 ffffd029f11f4b13 : 0000000000000001 0000000000000000 0000000000000096 00003f7cd19eb818 : nt!KiPageFault+0x46b
ffffa180592e19e8 0000000000000001 : 0000000000000000 0000000000000096 00003f7cd19eb818 fffff8066c7a95fa : 0xffffd029f11f4b13
ffffa180592e19f0 0000000000000000 : 0000000000000096 00003f7cd19eb818 fffff8066c7a95fa 00000000`00000000 : 0x1


SYMBOL_NAME: nt!KiPageFault+46b

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.18362.592

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 46b

FAILURE_BUCKET_ID: AV_CODE_AV_BAD_IP_nt!KiPageFault

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {73cd60cc-83fa-6b76-df08-1961c31d7403}

Followup: MachineOwner
---------
 
Last edited:

Colif

Win 10 Master
Moderator
Driver irq errors could be caused by overclocking I guess, but name seems to suggest its a driver.
Dump text doesn't tell me a lot. the driver that crashed here is part of windows kernel so its the victim, not the cause.
Its odd your MSI motherboard doesn't have Live update 6 as a utility, means we have to look at dumps to compare drivers
Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

copy that file to documents
upload the copy from documents to a file sharing web site, and share the link in your thread so we can help fix the problem
 
Jan 24, 2020
15
0
10
0
Driver irq errors could be caused by overclocking I guess, but name seems to suggest its a driver.
Dump text doesn't tell me a lot. the driver that crashed here is part of windows kernel so its the victim, not the cause.
Its odd your MSI motherboard doesn't have Live update 6 as a utility, means we have to look at dumps to compare drivers
Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

copy that file to documents
upload the copy from documents to a file sharing web site, and share the link in your thread so we can help fix the problem
I also tried updating my drivers in device manager but everything was up to date :/
 

gardenman

Admirable
Herald
Hi, I ran the dump file through the debugger and got the following information: https://tabulatemouse.htmlpasta.com/

File information:012320-6531-01.dmp (Jan 23 2020 - 22:52:17)
Bugcheck:DRIVER_IRQL_NOT_LESS_OR_EQUAL (D1)
Probably caused by:ntkrnlmp.exe (Process: dwm.exe)
Uptime:4 Day(s), 3 Hour(s), 07 Min(s), and 00 Sec(s)

Comments:
  • The overclocking driver "RTCore64.sys" was found on your system. (MSI Afterburner)
  • The overclocking driver "IOCBios2.sys" was found on your system. (Intel Extreme Tuning Utility)
  • BIOS info was not included in the dump file which sometimes mean an outdated BIOS is being used.
This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.
 

Colif

Win 10 Master
Moderator
Jan 24, 2020
15
0
10
0
Ok so I ran DDU and reinstalled my drivers but what older drivers should I be using? also I tried using g hub but it's not made for my older hardware since I use a logitech G700s mouse and G710+ keyboard so I got the latest version of LGS and it says I have the latest firmware version (45.7).
 

gardenman

Admirable
Herald
I ran the dump file through the debugger and got the following information: https://tweedierstill.htmlpasta.com/

File information:012720-6281-01.dmp (Jan 27 2020 - 18:12:09)
Bugcheck:KERNEL_SECURITY_CHECK_FAILURE (139)
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 3 Hour(s), 15 Min(s), and 57 Sec(s)

This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.
 

Zizo007

Notable
Feb 23, 2019
1,372
170
940
33
I can try with no OC and as for being compatible for the memory G.SKILL F4-3600C16D-16GVK (16-16-16-36) is on the list but mine are the G.SKILL F4-3600C16D-16GVKC (16-19-19-39)
If issue still persists with no OC change the RAM as those RAMs are different, I have the GVK and its Samsung B-die, the GVKC is not.
 

Colif

Win 10 Master
Moderator
Ok so I ran DDU and reinstalled my drivers but what older drivers should I be using?
I should have been more specific. Run ddu and instead of going to Nvidia, run windows update and let it find drivers. They aren't as new as the December drivers (as all you did was install same drivers you already had) but they might be more stable.
 
Jan 24, 2020
15
0
10
0
I wonder if it has anything to do with the intel m.2 ssd? I never downloaded any kind of driver for it was I supposed to? I also tried running my ram to stock speeds with no xmp (2133) and I didn't get a crash in the 20 min I was playing I wonder if the ram is unable to do 3600mhz as advertised?
 

Zizo007

Notable
Feb 23, 2019
1,372
170
940
33
I wonder if it has anything to do with the intel m.2 ssd? I never downloaded any kind of driver for it was I supposed to? I also tried running my ram to stock speeds with no xmp (2133) and I didn't get a crash in the 20 min I was playing I wonder if the ram is unable to do 3600mhz as advertised?
Its more like a compatibility problem with the RAM.
 
Jan 24, 2020
15
0
10
0
oh man so it looks like the old Nvidia driver won't be an option because now my game is crashing and saying my drivers are out of date, also I gotta thank you guys for helping me with this because I honestly don't know what to do at this point I'm clueless on what drivers causing the problem or if my ram is faulty.
 

Zizo007

Notable
Feb 23, 2019
1,372
170
940
33
oh man so it looks like the old Nvidia driver won't be an option because now my game is crashing and saying my drivers are out of date, also I gotta thank you guys for helping me with this because I honestly don't know what to do at this point I'm clueless on what drivers causing the problem or if my ram is faulty.
Its the RAM then.
 

ASK THE COMMUNITY

TRENDING THREADS