[SOLVED] How to read DMP files ?

[aamgr]

TLDR; I have random BSODs. They usually occur during mundane tasks, not during gaming or any other intensive tasks. I used WinDbg to analyze DMP files but I do not know what the results mean because it's a lot of technical stuff I do not know. Can anyone help me figure this out? Been having this issue for a while now. I just ran memtest and it passed the 13 tests 4 times with no problem, updated drivers, chkdsk. I can upload the DMP file or show the results of WinDbg. Any feedback is welcomed!

 

[aamgr]

Update: The pc is a lot more stable, it only crashed 1 time in 2 days. The codes of the BSOD were new, I never encountered them before. Here's the new dump files: https://www.dropbox.com/sh/5ad8cy5hsyq0a9j/AADC83kRj2xtDCEbBfKCcHwJa?dl=0

There was only 1 actual BSOD, but there are 2 new DMP files, so one of the DMP files was created even though it did not crash.

I believe the CreativeSoundBlaster was one of the malfunctioning drivers but it wasn't the only one I guess.

 

[gardenman]

I ran the dump file through the debugger and got the following information: https://jsfiddle.net/gycrhpow/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.

File information:	090121-10390-01.dmp (Aug 31 2021 - 12:37:23)
Bugcheck:	PFN_LIST_CORRUPT (4E)
Probably caused by:	memory_corruption (Process: System)
Uptime:	0 Day(s), 11 Hour(s), 19 Min(s), and 27 Sec(s)

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

 

[aamgr]

BSODs are further apart and it's not during zoom calls anymore. Latest dump file https://www.dropbox.com/sh/wyuwqjahzkb9wpo/AAB4UVA4HnkqgWWwA7QdH-I8a?dl=0

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

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 10083

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

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

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

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


BUGCHECK_CODE: 3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff8003de8981c

BUGCHECK_P3: fffff508e1fcc420

BUGCHECK_P4: 0

CONTEXT: fffff508e1fcc420 -- (.cxr 0xfffff508e1fcc420)
rax=0000000000000000 rbx=ffffc58ecccf7080 rcx=0000000000000016
rdx=0000000000000000 rsi=0000000000000000 rdi=a2e64eada2e64ead
rip=fffff8003de8981c rsp=fffff508e1fcce20 rbp=fffff508e1fcd070
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=ffff917ccfc00000 r12=0000000000000000 r13=ffffc58ecccf7080
r14=ffffc58ecbc71ba0 r15=fffff508e1fcdb00
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!ExFreeHeapPool+0x76c:
fffff8003de8981c 488b18 mov rbx,qword ptr [rax] ds:002b:0000000000000000=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: chrome.exe

IRP_ADDRESS: ffffffffffffff88

STACK_TEXT:
fffff508e1fcce20 fffff8003e5b2149 : 0000000000000010 0000000000000000 0000000000000000 0000000000000018 : nt!ExFreeHeapPool+0x76c
fffff508e1fccf00 fffff8003de860e6 : ffffc58e00000000 fffff508e1fcd070 ffffc58ed5ae5080 fffff508e1fccf00 : nt!ExFreePool+0x9
fffff508e1fccf30 fffff8003de0ee00 : 0000000000000000 0000000000000000 ffffc58ecbc71ba0 ffffc58ecccf7080 : nt!IopCompleteRequest+0x106
fffff508e1fccff0 fffff8003de0cc97 : 0000000000000000 0000000000000000 0000000000000000 ffffc58ed4a2e158 : nt!KiDeliverApc+0x1b0
fffff508e1fcd0a0 fffff8003de0be9f : eb77ffff00000004 fffff80000000009 fffff508e1fcd290 fffff50800000000 : nt!KiSwapThread+0x827
fffff508e1fcd150 fffff8003de805be : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiCommitThreadWait+0x14f
fffff508e1fcd1f0 fffff8003e26f7b0 : fffff508e1fcd5b0 0000000000000001 ffffc58ecc01b4b0 00000000000000ff : nt!KeWaitForMultipleObjects+0x2be
fffff508e1fcd300 fffff8003e26f489 : ffffc58ecbc71b90 0000000000000000 0000000000000000 0000000000000000 : nt!ObWaitForMultipleObjects+0x2f0
fffff508e1fcd800 fffff8003e008bb8 : 0000006b425ff950 0000000000000684 ffffc58ecccf7080 0000006b425ff950 : nt!NtWaitForMultipleObjects+0x119
fffff508e1fcda90 00007ffae900d974 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x28
0000006b425ff5b8 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffa`e900d974


SYMBOL_NAME: nt!ExFreePool+9

IMAGE_NAME: Pool_Corruption

IMAGE_VERSION: 10.0.19041.1165

MODULE_NAME: Pool_Corruption

STACK_COMMAND: .cxr 0xfffff508e1fcc420 ; kb

BUCKET_ID_FUNC_OFFSET: 9

FAILURE_BUCKET_ID: 0x3B_c0000005_nt!ExFreePool

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {c9913766-80de-cdf5-a1a8-15c856d3f064}

Followup: Pool_corruption
---------

 

[Colif]

PFN corrupt - pfn = Page Frame Number

A block of RAM, typically 4KB in size, used for virtual memory. A page frame is a physical entity with its own page frame number (PFN), whereas a "page" is content that floats between memory page frames and storage (disk or SSD).

https://www.pcmag.com/encyclopedia/term/page-frame

have you tested the ram? I am surprised I didn't mention it yet

Try running memtest86 on each of your ram sticks, one stick at a time, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors. Memtest is created as a bootable USB so that you don’t need windows to run it

 

[aamgr]

I already ran memtest, I actually mentioned it before. The test came back with no errors in all 13 tests, 4 times. Although I tested it with both ram sticks installed, I haven't tried it with only one installed.

 

[Colif]

it wouldn't make a difference, we only test 1 stick at a time so you know that stick is the cause of any errors, with 2 you wouldn't know.

well, its not ram.

run driver verifer until it stops showing driver names I guess.

 

[Colif]

well, chrome was last victim so could be lan drivers. You have January ones, the ones below might be newer
Download Win10 Auto Installation Program from under windows header here - https://www.realtek.com/en/componen...0-1000m-gigabit-ethernet-pci-express-software (you can't imagine how many times I typed that sentence out, getting sick of it)

 

[aamgr]

That was actually one of the first things you recommended when I started this thread, (exact same sentence haha). I'm gonna run it again just to be sure and run memtest multiple times using 1 stick at a time. I've seen some people only figuring out the error on their 6th pass of memtest.

 

[Colif]

i figured i probably had at some stage in thread. Sentence only changes if Realtek change their description.

 

[aamgr]

The first stick booted fine and I was able to run memtest, it passed the13 tests 4 times with no errors. When I changed out the first stick for the other one the pc would not post. The debugger led was just stuck on "CPU". It does look like the second one is faulty? But the pc boots fine with both of them on and detects the full 16gb.

MB: B450 tomahawk - If only using 1 stick manual says to put on the second DIMM slot and that's where I tested each stick.
Does ram slot matter? I've searched videos where they tried every combination of ram placement and it worked the same as running it on the 2nd and 4th slot.
Ram: T-force delta tuf gaming rgb 2x8gb 3200mhz

Right now I'm just using the one that works and passed memtest. I'm just going to use the pc normally and test if it still BSODs.

 

[Colif]

I wonder if the time you tested both sticks you had the good one in the right slot? its way too late to know for sure.

I won't jinx us but it looked like ram, errors kept moving and that is common with ram errors.

i had mistakenly thought you had run Memtest 13 times, I forgot it had that many tests. We used to suggest 8 runs but they restrict to to 4 for the free version and its not worth paying difference.
If PC won't even start with ram in, its a pretty good sign. Windows is pretty sensitive so it must have worked enough that win 10 didn't just reject it and set it as hardware reserved

 

[aamgr]

I'm just gonna have to see if it doesn't BSOD anymore to know for sure that the ram was the problem. If it's stable for at least the next week, then I can say that the ram was indeed the problem.