Question Constant BSODs! Please help :(

[mrsoup1]

Hi there. For some reason unbeknownst to me, my PC has suddenly started getting frequent BSODs, seemingly out the blue. It's not always the same one either; sometimes IRQL_NOT_LESS_OR_EQUAL and other times SYSTEM_SERVICE_EXCEPTION. I have tried different GPU drivers and some seem to cause less crashes than others but I'm not entirely convinced of the correlation. I have tried running MemTest three times. My PC froze during two of those tests, once with 365 errors and the other with a whopping 36,500!

Strangely enough, memory stress tests on OCCT seem to cause no problems but crashes occur when running the CPU stress test. The BSODs most commonly occur while gaming, at completely random times. I am honestly at a logical impasse and have no idea how to further diagnose the problem.

It might be worth mentioning that these crashes started occurring after resetting windows about a week ago.

Things I have tried:
-Resetting Windows
-Completely wiping drives and reinstalling Windows
-SFC /scannow
-Rolling back drivers
-Swapping out and re-seating RAM in different DIMM slots
-Enabling and disabling XMP
-Increasing DRAM voltages
-Updating BIOS

System specs:
G.Skill F5-6000U3636E16GX2-TZ5K Trident Z5 32GB (2x16GB) DDR5
Intel i9 12900k
Super Flower SF-1000F14MP Leadex Platinum 1000W 80 Plus Platinum
Asus GeForce RTX 3080 Ti TUF
Asus ROG STRIX Z690-F
Corsair H150i Elite
Mushkin MKNSSDHL1TB-D8 Helix-L 1TB M.2 (2280) PCIe NVMe Solid State Drive


I have attached a photo of the MemTest results and the dump file contents below.

https://imgur.com/a/rmCNzYm

Dump file results:

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

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1827

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 15997

Key : Analysis.Init.CPU.mSec
Value: 202

Key : Analysis.Init.Elapsed.mSec
Value: 4370

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

Key : Bugcheck.Code.DumpHeader
Value: 0x3b

Key : Bugcheck.Code.Register
Value: 0x3b

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key : WER.OS.Version
Value: 10.0.19041.1


FILE_IN_CAB: 092322-7203-01.dmp

BUGCHECK_CODE: 3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff8022ee879d0

BUGCHECK_P3: ffffaa8cd2626dd0

BUGCHECK_P4: 0

CONTEXT: ffffaa8cd2626dd0 -- (.cxr 0xffffaa8cd2626dd0)
rax=00000007df5f6230 rbx=0000000000000001 rcx=df4f6110ffffb788
rdx=00000000df5f6230 rsi=ffffb78b14d708a4 rdi=00000007df5f8231
rip=fffff8022ee879d0 rsp=ffffaa8cd26277d0 rbp=ffffaa8cd2627ac0
r8=00007df5f8231000 r9=0000000000000000 r10=ffffffffffffffff
r11=ffff9a0a111dd040 r12=000000b79bdfec10 r13=0000000000000030
r14=0000000000000000 r15=ffffb78b173b60c0
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050286
nt!MmQueryVirtualMemory+0xc70:
fffff8022ee879d0 483931 cmp qword ptr [rcx],rsi ds:002b:df4f6110ffffb788=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: chrome.exe

STACK_TEXT:
ffffaa8cd26277d0 fffff8022ee86d45 : ffffaed75f6f8008 ffffaed76bafb7c0 ffffaed76bb5d7d8 ffffb78b15d4e700 : nt!MmQueryVirtualMemory+0xc70
ffffaa8cd2627980 fffff8022ec0a9b5 : 0000000000000000 0000000000000000 0000000000000000 000000b79bdfe828 : nt!NtQueryVirtualMemory+0x25
ffffaa8cd26279d0 00007ffb7936d464 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x25
000000b79bdfea28 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffb`7936d464


SYMBOL_NAME: nt!MmQueryVirtualMemory+c70

MODULE_NAME: nt

IMAGE_VERSION: 10.0.19041.2006

STACK_COMMAND: .cxr 0xffffaa8cd2626dd0 ; kb

IMAGE_NAME: ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET: c70

FAILURE_BUCKET_ID: AV_nt!MmQueryVirtualMemory

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {daf5f12e-d641-44b4-72a6-40bb2e50ece7}

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

 

[Colif]

Did you take ram out as max error count you want is 0, not 36k

remove/replace ram sticks with errors

rma ram and get sticks that produce no errors, then if you still bsod, I will look at dumps/ No point looking at dumps if ram is causing errors in memtest.

is that 1 stick or both? helps to run memtest on 1 stick at a time so you know which one is the cause.

 

[mrsoup1]

Did you take ram out as max error count you want is 0, not 36k

remove/replace ram sticks with errors

rma ram and get sticks that produce no errors, then if you still bsod, I will look at dumps/ No point looking at dumps if ram is causing errors in memtest.

is that 1 stick or both? helps to run memtest on 1 stick at a time so you know which one is the cause.

No idea tbh. I've ran tests on 1 stick but not the other because running MemTest on every slot for every module is a pain in the ass. At this point it would be easier to just order some new RAM, to see if it solves the problem.

 

[mrsoup1]

Which leads me to ask; what on Earth could've caused one or both sticks of RAM to just suddenly fail? It was fine a mere week ago.

 

[Colif]

You only need to test 1 stick in all slots if you know stick is fine and are testing the slots.

RMA the pair and show the makers a copy of that screen shot and they should replace it.
No need to buy new if you have proof of purchase

ram can just go bad, I don't know why but I have seen it before. Could be a power spike, I don't know.