Windows 10: BSOD, because of XMP?

Hello,


I've been having some difficulties trying to diagnose why my new PC keeps bluescreening. I've only build this PC two days ago it's my first build so I haven't had enough time to properly say exactly what the problem is. I believe it's problem comes down to the memory correct me if I'm wrong, since whenever I enable my XMP profile it comes up. I ran a full memtest and windows memory diagnostic test with my RAM on base 2133MHz speed and it passed both of those. I haven't tried either with XMP enabled, since I'm not sure if I'd make a difference, would it/should I look to do that? Another thing I haven't done is a BIOS update, is that something that could potentially fix the problem? Then a follow-up question to that, if I were to fail either one of those with XMP enabled would that suggest a RAM hardware issue, or a motherboard issue, or potentially both? Alternatively, should I just try to manually OC the ram? A lot of this is new to me, but I'd appreciate any help I can get!


Many of my questions here are things I think MIGHT work but many of you helpful guys know a thing or two more about computers


Motherboard: Gigabyte Z390 Aorus Master

RAM: Corsair Vengeance RGB PRO 3200MHz


NOTE: This crash happened almost immediately after setting up my XMP profile I previously had disabled, if that makes a difference. I'd also like to note that the computer seems stable without XMP, although I haven't had a proper stress test or constant load.


Minidump: https://1drv.ms/u/s!AivAyba4cdJXqnRuqDV_VfgV-dKG?e=ixk2Pd


Assuming I got the minidump correctly, here it is:


IRQL_NOT_LESS_OR_EQUAL a

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 a kernel debugger is available get the stack backtrace.

Arguments:

Arg1: ffffcd17e1086ac0, memory referenced

Arg2: 0000000000000002, IRQL

Arg3: 0000000000000001, bitfield :

bit 0 : value 0 = read operation, 1 = write operation

bit 3 : value 0 = not an execute operation, 1 = execute operation only on chips which support this level of status

Arg4: fffff8033973ec05, address which referenced memory



Debugging Details:

------------------





KEY_VALUES_STRING: 1



Key : Analysis.CPU.Sec

Value: 1



Key : Analysis.DebugAnalysisProvider.CPP

Value: Create: 8007007e on DESKTOP-M1A6E4I



Key : Analysis.DebugData

Value: CreateObject



Key : Analysis.DebugModel

Value: CreateObject



Key : Analysis.Elapsed.Sec

Value: 3



Key : Analysis.Memory.CommitPeak.Mb

Value: 79



Key : Analysis.System

Value: CreateObject





DUMP_FILE_ATTRIBUTES: 0x8

Kernel Generated Triage Dump



BUGCHECK_CODE: a



BUGCHECK_P1: ffffcd17e1086ac0



BUGCHECK_P2: 2



BUGCHECK_P3: 1



BUGCHECK_P4: fffff8033973ec05



WRITE_ADDRESS: fffff8033a0fb390: Unable to get MiVisibleState

Unable to get NonPagedPoolStart

Unable to get NonPagedPoolEnd

Unable to get PagedPoolStart

Unable to get PagedPoolEnd

fffff8033a00f340: Unable to get Flags value from nt!KdVersionBlock

fffff8033a00f340: Unable to get Flags value from nt!KdVersionBlock

unable to get nt!MmSpecialPagesInUse

ffffcd17e1086ac0



BLACKBOXBSD: 1 !blackboxbsd





BLACKBOXNTFS: 1 !blackboxntfs





BLACKBOXWINLOGON: 1



CUSTOMER_CRASH_COUNT: 1



PROCESS_NAME: System



TRAP_FRAME: ffffd104bdd572a0 -- .trap 0xffffd104bdd572a0

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=ffffe68bf0843560 rbx=0000000000000000 rcx=ffffab000ce6f0d0

rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000

rip=fffff8033973ec05 rsp=ffffd104bdd57430 rbp=000000000044cfaf

r8=0000000000000003 r9=8004000000458734 r10=0000000000000008

r11=0000000000000000 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up ei pl nz na po cy

nt!MiInsertPageInList+0x555:

fffff803`3973ec05 4c895c2430 mov qword ptr [rsp+30h],r11 ss:ffffd104`bdd57460=0000000000000000

Resetting default scope



STACK_TEXT:

ffffd104`bdd57158 fffff803`39807169 : 00000000`0000000a ffffcd17`e1086ac0 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx

ffffd104`bdd57160 fffff803`39803469 : ffffd104`bdd58000 fffff803`3c8442fb 00000000`00000000 ffffe68b`fefa7c40 : nt!KiBugCheckDispatch+0x69

ffffd104`bdd572a0 fffff803`3973ec05 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x469

ffffd104`bdd57430 fffff803`3973d1cd : 00000000`00000003 00000000`00000008 00000000`00000000 00000000`00000000 : nt!MiInsertPageInList+0x555

ffffd104`bdd574d0 fffff803`3973cdba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiPfnReferenceCountIsZero+0x6d

ffffd104`bdd57510 fffff803`3960cad9 : 00000000`00000000 00000000`00000000 ffffe68b`fef77470 00000000`00000001 : nt!MiWriteCompletePfn+0x9a

ffffd104`bdd57540 fffff803`3960a598 : ffffe68b`fbb1cc01 00000000`c0000054 00000000`00000001 00000000`00001000 : nt!MiWriteComplete+0x1b9

ffffd104`bdd575f0 fffff803`397b239b : fffff803`3a050c00 00000000`00000001 ffffe68b`fc624a30 00000000`00000000 : nt!MiGatherMappedPages+0x32c

ffffd104`bdd576b0 fffff803`396a29a5 : ffffe68b`f7265080 ffffe68b`f7265080 00000000`00000080 000fa4ef`bd9bbfff : nt!MiMappedPageWriter+0x18b

ffffd104`bdd57b10 fffff803`397fc868 : fffff803`3555e180 ffffe68b`f7265080 fffff803`396a2950 00000000`00000000 : nt!PspSystemThreadStartup+0x55

ffffd104`bdd57b60 00000000`00000000 : ffffd104`bdd58000 ffffd104`bdd51000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28





SYMBOL_NAME: nt!MiInsertPageInList+555



MODULE_NAME: nt



IMAGE_VERSION: 10.0.19041.630



STACK_COMMAND: .thread ; .cxr ; kb



IMAGE_NAME: memory_corruption



BUCKET_ID_FUNC_OFFSET: 555



FAILURE_BUCKET_ID: AV_nt!MiInsertPageInList



OSPLATFORM_TYPE: x64



OSNAME: Windows 10



FAILURE_ID_HASH: {a90f9f23-588e-d5a6-a0a3-950e9fb27bf8}



Followup: MachineOwner

:)

 

BSOD when XMP Is Enabled

Then you have a different interpretation...

Thank you.

Cute.

At any rate, I'm not here to compete. I'm just adding what I know. Anyway It does the OP no good for us to argue over semantics.

Peace

 

BSOD when XMP Is Enabled

I can rule Intel out of the debate, most of what I wrote in the part you quoted is on Intel's site apparently.

Considering my view on overclocking and from what I read swarfega is looking to overclock, swarfega wrote in post BSOD when XMP Is Enabled that he wanted to overclock, that's my interpretation at least.

(meanwhile swarfega posted)

As Sygnus suggested a few times, it's probably better if you went to overclock.net for assistance with the XMP problems. That is if nobody who knows his/her stuff about XMP jumps in.

 

BSOD when XMP Is Enabled

Here are the HDTune screenshots:











OS drive is the bottom one.