Question "IRQL_NOT_LESS_OR_EQUAL" only with certain programs

[nzuzz]

Last spring i bought a new pc. I built it myself. Everything works fine except of some bsods while gaming. It happens every 1-2 hours. I recently replaced the ram sticks but that didnt seem to be the source of the problem.

specs:

Intel Core i9-9900K (LGA 1151, 3.60GHz, 8-Core)
MSI MPG Z390 Gaming Edge AC (LGA 1151, Intel Z390, ATX)
MSI GeForce RTX 2070 ARMOR
Samsung 970 EVO Plus (500GB, M.2 2280)
Corsair Hydro Series H100x
Corsair RM750x (750W)
Corsair Vengeance RGB Pro (2x, 16GB, DDR4-3200, DIMM 288)
Windows 10 Home

Minidumpfiles: https://we.tl/t-SFR1egHJMK

A - With Corsair Vengeance LPX (2x, 8GB, DDR4-3000, DIMM 288)
B - With Corsair Vengeance RGB Pro (2x, 16GB, DDR4-3200, DIMM 288)

thankful for any help

 

[Ketchup79]

Was Windows a fresh install for this build? Have you installed drivers from the MSI website for this build? What settings are you using for your RAM (standard, optimized, XMP, etc)?

 

[Calvin7]

Based on your description of the memory your using, It appears you may be buying memory modules sold as single modules and combining them in multiple configurations. Such combinations have no guarantee to be compatible together.

I suggest posting memory with a part number and/or link to it.

 

[nzuzz]

Was Windows a fresh install for this build? Have you installed drivers from the MSI website for this build? What settings are you using for your RAM (standard, optimized, XMP, etc)?

Yes. Yes. XMP is enabled in bios (I have to say i dont really know how to handle these settings, what they do and how they infect the performance etc.)

 

[nzuzz]

Based on your description of the memory your using, It appears you may be buying memory modules sold as single modules and combining them in multiple configurations. Such combinations have no guarantee to be compatible together.

I suggest posting memory with a part number and/or link to it.

The memory sticks where bought in pairs

once Corsair Vengeance LPX (2x, 8GB, DDR4-3000, DIMM 288)
and once Corsair Vengeance RGB Pro (2x, 16GB, DDR4-3200, DIMM 288)

 

[Ketchup79]

XMP CAN improve performance, however since you have two different sets of sticks, running at two different speeds, most likely with different timings, XMP is probably what is giving you issues here. You can try turning off XMP and see if they will run together that way, or try to return the slower set for one that matched the 3200 in speed and timings.

 

[nzuzz]

XMP CAN improve performance, however since you have two different sets of sticks, running at two different speeds, most likely with different timings, XMP is probably what is giving you issues here. You can try turning off XMP and see if they will run together that way, or try to return the slower set for one that matched the 3200 in speed and timings.

I tried to disable xmp, but still got the bsod. I dont know if it is worth to mension, but the bsod error codes ar not always the same. "IRQL_NOT_LESS_OR_EQUAL" is just the most common one.

 

[Ketchup79]

What speed is your motherboard set to run your RAM at now?

 

[nzuzz]

What speed is your motherboard set to run your RAM at now?

3200 with xmp enabled

 

[Ketchup79]

3200 with xmp enabled

That's the problem. You should be running 3000 max, as that I'd the max speed of your LPX set.

 

[nzuzz]

That's the problem. You should be running 3000 max, as that I'd the max speed of your LPX set.

i upgraded from the lpx set. im now using Corsair Vengeance RGB Pro (2x, 16GB, DDR4-3200, DIMM 288). so 3200 should fit.

 

[Ketchup79]

Ok. So the two sets are at different times. That wasn't clear to me. What voltage are you giving them?

 

[nzuzz]

Ok. So the two sets are at different times. That wasn't clear to me. What voltage are you giving them?

1.360V

 

[Ketchup79]

Good voltage. What timings? Corsairs recommends 16-18-18-36 at that speed.

 

[nzuzz]

Good voltage. What timings? Corsairs recommends 16-18-18-36 at that speed.

Yes they are indeed 16-18-18-36

 

[Ketchup79]

If you try 3000, do they work? If so, you may need to swap them out for a new set that works properly. Do all testing with XMP disabled for now, just to rule that part out.

 

[nzuzz]

are the ram sticks even the problem?

* Path validation summary **
Response Time (ms) Location
Deferred srvC:\Temp

Symbol information

WARNING: Whitespace at start of path element

Microsoft (R) Windows Debugger Version 10.0.18362.1 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\122619-8125-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at start of path element

* Path validation summary **
Response Time (ms) Location
Deferred srvC:\Temp

Symbol information

WARNING: Whitespace at start of path element
Symbol search path is: SRVC:\Temp

http://msdl.microsoft.com/download/...RL]http://msdl.microsoft.com/download/symbols

[/URL]
Executable search path is:
Windows 10 Kernel Version 18362 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff80672600000 PsLoadedModuleList = 0xfffff80672a48130
Debug session time: Thu Dec 26 16:50:56.767 2019 (UTC + 1:00)
System Uptime: 0 days 3:54:10.449
Loading Kernel Symbols
..

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

.............................................................
................................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
.........
For analysis of this file, run !analyze -v
15: kd> !analyze -v
***

• *
• Bugcheck Analysis *
• *

***

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80672bd6a5a, Address of the instruction which caused the bugcheck
Arg3: ffff888d76edea80, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10.0.18362.535 (WinBuild.160101.0800)

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

DUMP_TYPE: 2

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff80672bd6a5a

BUGCHECK_P3: ffff888d76edea80

BUGCHECK_P4: 0

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%p verwies auf Arbeitsspeicher bei 0x%p. Der Vorgang %s konnte im Arbeitsspeicher nicht durchgef hrt werden.

FAULTING_IP:
nt!EtwpWriteUserEvent+d0a
fffff80672bd6a5a 488b4578 mov rax,qword ptr [rbp+78h] CONTEXT: ffff888d76edea80 -- (.cxr 0xffff888d76edea80) rax=0000000040000000 rbx=0000000000000006 rcx=ffff888d76edf990 rdx=000000000000001e rsi=0000000000000000 rdi=0000000000000006 rip=fffff80672bd6a5a rsp=ffff888d76edf470 rbp=ffff888d76edf4c0 r8=0000000000000068 r9=0000000000000000 r10=ffffe7039e2e69e4 r11=ffffe7039e2e69e4 r12=ffffe7039e2e6980 r13=0000000000000000 r14=0000000000000068 r15=0000004a947fded0 iopl=0 nv up ei pl nz na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050206 nt!EtwpWriteUserEvent+0xd0a: fffff80672bd6a5a 488b4578 mov rax,qword ptr [rbp+78h] ss:0018:ffff888d76edf538=00000020b6cf5820 Resetting default scope BUGCHECK_STR: 0x3B_c0000005 CPU_COUNT: 10 CPU_MHZ: e10 CPU_VENDOR: GenuineIntel CPU_FAMILY: 6 CPU_MODEL: 9e CPU_STEPPING: c CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT PROCESS_NAME: chrome.exe CURRENT_IRQL: 0 ANALYSIS_SESSION_HOST: DESKTOP-7BRTSPA ANALYSIS_SESSION_TIME: 12-26-2019 20:24:38.0297 ANALYSIS_VERSION: 10.0.18362.1 x86fre LAST_CONTROL_TRANSFER: from fffff80672624fb8 to fffff80672bd6a5a STACK_TEXT: ffff888d76edf470 fffff80672624fb8 : ffff888d76edf920 fffff80678f75517 0000004a947fdc98 fffff8067263a5a7 : nt!EtwpWriteUserEvent+0xd0a ffff888d76edf840 fffff806727d2d15 : ffffe70300000000 0000021600000001 0000000000000000 ffff888d76edfa80 : nt!NtTraceEvent+0x248 ffff888d76edfa00 00007ffb25bfcc74 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x25 0000004a947fdc28 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffb25bfcc74


THREAD_SHA1_HASH_MOD_FUNC: f8d38820688d47b00c7baf415d5b102971b86af3

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: ba7a1d957ef6294e495f4ddfb4e5c7b37f47f92f

THREAD_SHA1_HASH_MOD: 2a7ca9d3ab5386d53fea7498e1d81b9c4a4c036b

FOLLOWUP_IP:
nt!EtwpWriteUserEvent+d0a
fffff806`72bd6a5a 488b4578 mov rax,qword ptr [rbp+78h]

FAULT_INSTR_CODE: 78458b48

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!EtwpWriteUserEvent+d0a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 12dcb470

IMAGE_VERSION: 10.0.18362.535

STACK_COMMAND: .cxr 0xffff888d76edea80 ; kb

BUCKET_ID_FUNC_OFFSET: d0a

FAILURE_BUCKET_ID: 0x3B_c0000005_nt!EtwpWriteUserEvent

BUCKET_ID: 0x3B_c0000005_nt!EtwpWriteUserEvent

PRIMARY_PROBLEM_CLASS: 0x3B_c0000005_nt!EtwpWriteUserEvent

TARGET_TIME: 2019-12-26T15:50:56.000Z

OSBUILD: 18362

OSSERVICEPACK: 535

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 784

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 1980-01-11 16:53:20

BUILDDATESTAMP_STR: 160101.0800

BUILDLAB_STR: WinBuild

BUILDOSVER_STR: 10.0.18362.535

ANALYSIS_SESSION_ELAPSED_TIME: 130d

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x3b_c0000005_nt!etwpwriteuserevent

FAILURE_ID_HASH: {f4ba4e04-c347-1683-5519-b57989a066f1}

Followup: MachineOwner
---------


This is a dmp from today. Can you see whats causing it?

 

[Flayed]

Looks to me like chrome was writing some data from a register to memory when the exception occurred. It points to memory instability as the issue I think