Windows 10: BSOD - Unsure of what to make of minidump analysis

Discus and support BSOD - Unsure of what to make of minidump analysis in Windows 10 BSOD Crashes and Debugging to solve the problem; Hi! My PC BSOD about once a day and it occurs at random. wathcing youtube, playing games, idle with nothing opened. Every .dmp file I've opened says... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by phopo, Jan 5, 2020.

  1. PHOPO
    phopo Win User

    BSOD - Unsure of what to make of minidump analysis


    Hi!


    My PC BSOD about once a day and it occurs at random. wathcing youtube, playing games, idle with nothing opened.

    Every .dmp file I've opened says memory corruption. However, I have replaced my ram with ram from my other PC which works fine, and BSOD still occurs. Memtest86 was also performed on both for 4 runs and 0 errors came up.


    Any help would be appreciated!


    System specs:

    ryzen7 3700x

    2 x 8gb corsair ram running on xmp 3600mhz still BSOD if i turn off XMP

    asus x570 strix - bios, chipset drivers all up to date

    amd 5700xt - drivers all up to date non beta versions


    1xssd

    1x m.2 ssd


    Here is what .dmp file says



    Loading Dump File [C:\Windows\minidump\010520-8421-01.dmp]

    Mini Kernel Dump File: Only registers and stack trace are available



    Symbol search path is: srv*

    Executable search path is:

    Windows 10 Kernel Version 18362 MP 16 procs Free x64

    Product: WinNt, suite: TerminalServer SingleUserTS

    Built by: 18362.1.amd64fre.19h1_release.190318-1202

    Machine Name:

    Kernel base = 0xfffff806`0da00000 PsLoadedModuleList = 0xfffff806`0de48210

    Debug session time: Sun Jan 5 16:35:14.613 2020 UTC + 11:00

    System Uptime: 0 days 1:45:37.287

    Loading Kernel Symbols

    ...............................................................

    ................................................................

    ..........................................................

    Loading User Symbols

    Loading unloaded module list

    ...........

    For analysis of this file, run !analyze -v

    9: kd> !analyze -v

    *******************************************************************************

    * *

    * Bugcheck Analysis *

    * *

    *******************************************************************************



    PAGE_FAULT_IN_NONPAGED_AREA 50

    Invalid system memory was referenced. This cannot be protected by try-except.

    Typically the address is just plain bad or it is pointing at freed memory.

    Arguments:

    Arg1: ffffffff88118412, memory referenced.

    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.

    Arg3: fffff8060e1000df, If non-zero, the instruction address which referenced the bad memory

    address.

    Arg4: 0000000000000002, reserved



    Debugging Details:

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





    Could not read faulting driver name

    *** WARNING: Unable to verify timestamp for win32k.sys



    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: 18362.1.amd64fre.19h1_release.190318-1202



    SYSTEM_MANUFACTURER: System manufacturer



    SYSTEM_PRODUCT_NAME: System Product Name



    SYSTEM_SKU: SKU



    SYSTEM_VERSION: System Version



    BIOS_VENDOR: American Megatrends Inc.



    BIOS_VERSION: 0604



    BIOS_DATE: 07/02/2019



    BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.



    BASEBOARD_PRODUCT: ROG STRIX X570-F GAMING



    BASEBOARD_VERSION: Rev X.0x



    DUMP_TYPE: 2



    BUGCHECK_P1: ffffffff88118412



    BUGCHECK_P2: 0



    BUGCHECK_P3: fffff8060e1000df



    BUGCHECK_P4: 2



    READ_ADDRESS: fffff8060df733b8: Unable to get MiVisibleState

    Unable to get NonPagedPoolStart

    Unable to get NonPagedPoolEnd

    Unable to get PagedPoolStart

    Unable to get PagedPoolEnd

    ffffffff88118412



    FAULTING_IP:

    nt!PiLookupInDDB+11b

    fffff806`0e1000df 8b9012841188 mov edx,dword ptr [rax-77EE7BEEh]



    MM_INTERNAL_CODE: 2



    CPU_COUNT: 10



    CPU_MHZ: e09



    CPU_VENDOR: AuthenticAMD



    CPU_FAMILY: 17



    CPU_MODEL: 71



    CPU_STEPPING: 0



    BLACKBOXBSD: 1 !blackboxbsd





    BLACKBOXNTFS: 1 !blackboxntfs





    BLACKBOXPNP: 1 !blackboxpnp





    BLACKBOXWINLOGON: 1



    CUSTOMER_CRASH_COUNT: 1



    DEFAULT_BUCKET_ID: CODE_CORRUPTION



    BUGCHECK_STR: AV



    PROCESS_NAME: System



    CURRENT_IRQL: 0



    ANALYSIS_SESSION_HOST: DESKTOP-IEQNHH7



    ANALYSIS_SESSION_TIME: 01-05-2020 19:55:07.0155



    ANALYSIS_VERSION: 10.0.18362.1 amd64fre



    TRAP_FRAME: fffffb0d4dd415f0 -- .trap 0xfffffb0d4dd415f0

    NOTE: The trap frame does not contain all registers.

    Some register values may be zeroed or incorrect.

    rax=0000000000000000 rbx=0000000000000000 rcx=ffff8883e2524050

    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000

    rip=fffff8060e1000df rsp=fffffb0d4dd41780 rbp=fffffb0d4dd41809

    r8=ffff8883e06d8af0 r9=ffffad0c1ca4e7a8 r10=ffff8883cdaf4600

    r11=ffff8883e31e9040 r12=0000000000000000 r13=0000000000000000

    r14=0000000000000000 r15=0000000000000000

    iopl=0 nv up ei pl zr na po nc

    nt!PiLookupInDDB+0x11b:

    fffff806`0e1000df 8b9012841188 mov edx,dword ptr [rax-77EE7BEEh] ds:ffffffff`88118412=????????

    Resetting default scope



    LOCK_ADDRESS: fffff8060de62a20 -- !locks fffff8060de62a20

    Cannot get _ERESOURCE type



    Resource @ nt!PiEngineLock 0xfffff8060de62a20 Available

    1 total locks



    PNP_TRIAGE_DATA:

    Lock address : 0xfffff8060de62a20

    Thread Count : 0

    Thread address: 0x0000000000000000

    Thread wait : 0x0



    LAST_CONTROL_TRANSFER: from fffff8060dbe33d6 to fffff8060dbc1220



    STACK_TEXT:

    fffffb0d`4dd41348 fffff806`0dbe33d6 : 00000000`00000050 ffffffff`88118412 00000000`00000000 fffffb0d`4dd415f0 : nt!KeBugCheckEx

    fffffb0d`4dd41350 fffff806`0da72edf : 00000000`00000000 00000000`00000000 00000000`00000000 ffffffff`88118412 : nt!MiSystemFault+0x1d66a6

    fffffb0d`4dd41450 fffff806`0dbcf320 : 00000000`00000030 00000000`00000001 00000000`00000000 ffffad0c`251ed000 : nt!MmAccessFault+0x34f

    fffffb0d`4dd415f0 fffff806`0e1000df : ffffad0c`141af450 fffffb0d`4dd41800 fffff806`0e3affb0 01000000`00100000 : nt!KiPageFault+0x360

    fffffb0d`4dd41780 fffff806`0e100287 : 00000000`c0000001 fffff806`0ad00000 fffffb0d`4dd419e8 ffffffff`800049b4 : nt!PiLookupInDDB+0x11b

    fffffb0d`4dd41870 fffff806`0e1008de : fffff806`0ad00000 00000000`00000000 00000000`00000002 ffffffff`800049b4 : nt!PpCheckInDriverDatabase+0x93

    fffffb0d`4dd418d0 fffff806`0e10ef99 : fffffb0d`4dd41a50 fffff806`0ad000e8 00000000`00000000 00000000`00000000 : nt!PnpPrepareDriverLoading+0x6a

    fffffb0d`4dd41950 fffff806`0e10ec2e : 00000000`00000000 00000000`00000000 00000000`00000000 fffff806`0de65aa0 : nt!IopLoadDriver+0x265

    fffffb0d`4dd4****`00000080 ffff8883`cda7a300 0067006f`00000001 : nt!ExpWorkerThread+0x105

    fffffb0d`4dd41c10 fffff806`0dbc886a : fffff806`0aa85180 ffff8883`e31e9040 fffff806`0db2a6d0 00690057`005c0025 : nt!PspSystemThreadStartup+0x55

    fffffb0d`4dd41c60 00000000`00000000 : fffffb0d`4dd42000 fffffb0d`4dd3c000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x2a





    CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt

    fffff8060e1000e0-fffff8060e1000e3 4 bytes - nt!PiLookupInDDB+11c

    [ d8 85 c0 0f:90 12 84 11 ]

    4 errors : !nt fffff8060e1000e0-fffff8060e1000e3



    MODULE_NAME: memory_corruption



    IMAGE_NAME: memory_corruption



    FOLLOWUP_NAME: memory_corruption



    DEBUG_FLR_IMAGE_TIMESTAMP: 0



    MEMORY_CORRUPTOR: LARGE



    STACK_COMMAND: .thread ; .cxr ; kb



    FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE



    BUCKET_ID: MEMORY_CORRUPTION_LARGE



    PRIMARY_PROBLEM_CLASS: MEMORY_CORRUPTION_LARGE



    TARGET_TIME: 2020-01-05T05:35:14.000Z



    OSBUILD: 18362



    OSSERVICEPACK: 418



    SERVICEPACK_NUMBER: 0



    OS_REVISION: 0



    SUITE_MASK: 272



    PRODUCT_TYPE: 1



    OSPLATFORM_TYPE: x64



    OSNAME: Windows 10



    OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS



    OS_LOCALE:



    USER_LCID: 0



    OSBUILD_TIMESTAMP: unknown_date



    BUILDDATESTAMP_STR: 190318-1202



    BUILDLAB_STR: 19h1_release



    BUILDOSVER_STR: 10.0.18362.1.amd64fre.19h1_release.190318-1202



    ANALYSIS_SESSION_ELAPSED_TIME: 2952



    ANALYSIS_SOURCE: KM



    FAILURE_ID_HASH_STRING: km:memory_corruption_large



    FAILURE_ID_HASH: {e29154ac-69a4-0eb8-172a-a860f73c0a3c}



    Followup: memory_corruption

    ---------

    :)
     
    phopo, Jan 5, 2020
    #1
  2. EL.FAKIR
    el.Fakir Win User

    Windows 10 Pro x64 minidumps analysis request

    Hi there,

    Still experiencing BSOD, here you are another minidump : http://1drv.ms/1PlFKzp Any analysis would be greatly appreciated. Thanks!

    el' ~
     
    el.Fakir, Jan 5, 2020
    #2
  3. RVAJEFF1
    rvajeff1 Win User
    Need help with BSOD / Minidump file analysis

    Hi everyone,

    My PC has been having intermittent BSODs for a few months now, and it has been more frequent as of late. I posted a thread about it before, please see
    here    . The very helpful gentleman in that thread found my smart card reader to potentially be at fault. I have since removed that device and uninstalled its drivers. But yesterday and today, I encountered 2 more BSODs.

    I have some new minidump files, found here: Dropbox - Minidump-new.zip - Simplify your life

    Also, here is my system info: Dropbox - MSinfo.nfo - Simplify your life

    Any help would be greatly appreciated. This is my work PC, I use it for video editing and other similar multimedia work, and I am afraid of the pain that it might cause if these BSODs keep increasing in frequency, and if hardware ends up damaged or similar.
    Thanks in advance!!
     
    rvajeff1, Jan 5, 2020
    #3
  4. FORCEFLOW
    Forceflow Win User

    BSOD - Unsure of what to make of minidump analysis

    2.9.0 causing BSOD (minidump analysis attached)

    I've been doing the reboot + immediately launch game dance all day (like ... 20+ times), and the only way I can get it to reliably crash is when I launch GPU-Z first.

    Here's a Dropbox folder with a bunch of minidumps to analyse: Dropbox - Link not found

    Note that it doesn't always lists GPU-Z as active process when it crashes, but it's always the nvidia driver sys, though.

    I've mailed all of this to L: driverfeedback at nvidia.com, and reported it in the Driver Feedback Thread on the Geforce forums too.
     
    Forceflow, Jan 5, 2020
    #4
Thema:

BSOD - Unsure of what to make of minidump analysis

Loading...

  1. BSOD - Unsure of what to make of minidump analysis - Similar Threads - BSOD Unsure minidump

  2. BSOD Minidump Analysis Help

    in Windows 10 Gaming
    BSOD Minidump Analysis Help: I've been getting pretty frequent BSODs and until recently Windows was not generating any Minidumps it only has for the two most recent, which I've uploaded. Would somebody be willing to analyze these and help point me towards what's going wrong?Minidump...

  3. BSOD and crashing minidump analysis

    in Windows 10 Software and Apps
    BSOD and crashing minidump analysis: https://1drv.ms/u/s!Ah-FekajzWrQif0-SxwDzMnwZkca6g?e=wtT7sWMy computer keeps crashing when I play some games such as League of Overwatch, however, all my drivers say they are healthy as well as my computer graphics being of good quality. I only have issues on certain games...

  4. BSOD and crashing minidump analysis

    in Windows 10 Gaming
    BSOD and crashing minidump analysis: https://1drv.ms/u/s!Ah-FekajzWrQif0-SxwDzMnwZkca6g?e=wtT7sWMy computer keeps crashing when I play some games such as League of Overwatch, however, all my drivers say they are healthy as well as my computer graphics being of good quality. I only have issues on certain games...

  5. BSOD minidump analysis is needed

    in Windows 10 Software and Apps
    BSOD minidump analysis is needed: MINIDUMP : https://drive.google.com/file/d/1tnOuMsuHm0pX-jvjXMhCvxVvieqJ0crf/view?usp=sharing https://answers.microsoft.com/en-us/windows/forum/all/bsod-minidump-analysis-is-needed/9f39ab75-d98a-481d-b41d-2e151ac4172d

  6. BSOD minidump analysis is needed

    in Windows 10 Software and Apps
    BSOD minidump analysis is needed: Hi,My PC crashes intermittently with the BSOD with the WHEA error Minidump folder contains several crash dumps.https://drive.google.com/drive/folders/1Bzui4686935ehrm1PN33eh8hF7N7AvWK?usp=sharingCan you please help me to identify the problem causing these...

  7. Analysis of BSOD minidump file

    in Windows 10 BSOD Crashes and Debugging
    Analysis of BSOD minidump file: My PC crashed again recently thus making it the second time it has happened for no reason. I built it just a few months ago and all the components are new except for my GTX 1060 which I kept from my old build. So what I'm asking for is help with analyzing the crash dump...

  8. Analysis of BSOD minidump file

    in Windows 10 Gaming
    Analysis of BSOD minidump file: My PC crashed again recently thus making it the second time it has happened for no reason. I built it just a few months ago and all the components are new except for my GTX 1060 which I kept from my old build. So what I'm asking for is help with analyzing the crash dump...

  9. Analysis of BSOD minidump file

    in Windows 10 Software and Apps
    Analysis of BSOD minidump file: My PC crashed again recently thus making it the second time it has happened for no reason. I built it just a few months ago and all the components are new except for my GTX 1060 which I kept from my old build. So what I'm asking for is help with analyzing the crash dump...

  10. BSOD - Minidump file analysis

    in Windows 10 Drivers and Hardware
    BSOD - Minidump file analysis: Hello my Dell Latitude E6320 crashes BSOD - system service crashexception anytime a usb drive is inserted. This has started after a recent windows update. I used verifier, and the laptop started crashing on startup, with following message: Driver verifier detected...