Need help analyzing this dmp file

Brayden Thornton

New member
Jul 12, 2022
1
0
0
Visit site
So I've recently had a few Green Screen of Deaths on my PC

My most recent change was using a different DRAM profile for my CPU in the BIOS (It was capped at 2400MHz and I bumped it up to 3200MHz). I changed it back and so far, no more crashes

But I'm still concerned, so I searched through the .dmp files and oddly enough, Microsoft Edge is labelled in these files. So I'm curious if the DRAM profile wasn't entirely the issue but just Microsoft Edge causing some issues. I have the Crash Report here, I hope someone else can look over it and get back to me with an answer:
..........................................................

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the BugCheck
Arg2: fffff8031d826f67, Address of the instruction which caused the BugCheck
Arg3: ffffb78dbd5dad10, 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: 1936

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 2097

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

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

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

Key : Bugcheck.Code.DumpHeader
Value: 0x3b

Key : Bugcheck.Code.Register
Value: 0x3b

Key : Dump.Attributes.AsUlong
Value: 808

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

ORIGINAL_CAB_PATH: C:\Windows\Minidump\071222-14468-01.zip

FILE_IN_CAB: 071222-14468-01.dmp

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b

DUMP_FILE_ATTRIBUTES: 0x808
Kernel Generated Triage Dump

BUGCHECK_CODE: 3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff8031d826f67

BUGCHECK_P3: ffffb78dbd5dad10

BUGCHECK_P4: 0

CONTEXT: ffffb78dbd5dad10 -- (.cxr 0xffffb78dbd5dad10)
rax=0000000352740001 rbx=0000000000000000 rcx=ffffa38133b76e50
rdx=ff7fa38162fd1510 rsi=ffffe00110ea2180 rdi=0000000000000002
rip=fffff8031d826f67 rsp=ffffb78dbd5db730 rbp=00000000000003e8
r8=ff7fa38162fd1510 r9=0000000000000000 r10=ffffa38133b76e50
r11=ffffb78dbd5db830 r12=ffffa38133b76e50 r13=0000000000000000
r14=0000000000000160 r15=0000000000000001
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050282
nt!ExpInterlockedPopEntrySListFault:
fffff803`1d826f67 498b08 mov rcx,qword ptr [r8] ds:002b:ff7fa381`62fd1510=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: msedge.exe

STACK_TEXT:
ffffb78d`bd5db730 fffff803`1d6922a4 : ffffa381`4d3757c0 ffffffff`00000000 ffffa381`4d3757d0 ffffa381`4d3757f0 : nt!ExpInterlockedPopEntrySListFault
ffffb78d`bd5db740 fffff803`1d692157 : 00000000`00000002 00000000`00000004 00000000`00000000 00000000`00000010 : nt!IopAllocateIrpPrivate+0x134
ffffb78d`bd5db7b0 fffff803`1d61180d : 00000000`00000000 ffffa381`4fd5e7e0 00000000`00000000 00000000`00000000 : nt!IopAllocateIrpExReturn+0x17
ffffb78d`bd5db7e0 fffff803`1dab296f : ffffb78d`00000000 ffffb78d`bd5db990 ffffa381`77aadb80 00000000`00000000 : nt!IopAllocateAndPopulateWriteIrp+0x16d
ffffb78d`bd5db860 fffff803`1dab25c3 : ffffa381`77aadb80 00000000`0012019f 00000000`00000000 00000000`00000000 : nt!IopWriteFile+0x24f
ffffb78d`bd5db980 fffff803`1d831168 : 00000000`00000001 00000000`00000000 00000000`00000000 0000657a`00c6e098 : nt!NtWriteFile+0x263
ffffb78d`bd5dba70 00007ffc`1cfaedc4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000027`c3bfe6f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`1cfaedc4

SYMBOL_NAME: nt!IopAllocateIrpPrivate+134

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.22621.290

STACK_COMMAND: .cxr 0xffffb78dbd5dad10 ; kb

BUCKET_ID_FUNC_OFFSET: 134

FAILURE_BUCKET_ID: AV_nt!IopAllocateIrpPrivate

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {88edd08e-8bce-6db4-4bf1-59a7ad5d7993}

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

Thank you all
 

Members online

Forum statistics

Threads
323,173
Messages
2,243,380
Members
428,035
Latest member
powerupgo