none
What caused the BSOD, would you help me to analyze it ? RRS feed

  • Question

  • Loading User Symbols
    Loading unloaded module list
    ..................................................
    For analysis of this file, run !analyze -v
    nt!KeBugCheckEx:
    fffff806`0adf5e40 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffffb00`2176ddf0=000000000000001a
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    MEMORY_MANAGEMENT (1a)
        # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 0000000000041792, A corrupt PTE has been detected. Parameter 2 contains the address of
    	the PTE. Parameters 3/4 contain the low/high parts of the PTE.
    Arg2: fffff97b04400ec8
    Arg3: 000000100c100000
    Arg4: 0000000000000000
    
    Debugging Details:
    ------------------
    
    
    KEY_VALUES_STRING: 1
    
        Key  : Analysis.CPU.mSec
        Value: 3608
    
        Key  : Analysis.DebugAnalysisManager
        Value: Create
    
        Key  : Analysis.Elapsed.mSec
        Value: 27099
    
        Key  : Analysis.Init.CPU.mSec
        Value: 389
    
        Key  : Analysis.Init.Elapsed.mSec
        Value: 31313
    
        Key  : Analysis.Memory.CommitPeak.Mb
        Value: 75
    
        Key  : MemoryManagement.PFN
        Value: 100c100
    
    
    DUMP_FILE_ATTRIBUTES: 0x8
      Kernel Generated Triage Dump
    
    BUGCHECK_CODE:  1a
    
    BUGCHECK_P1: 41792
    
    BUGCHECK_P2: fffff97b04400ec8
    
    BUGCHECK_P3: 100c100000
    
    BUGCHECK_P4: 0
    
    BLACKBOXBSD: 1 (!blackboxbsd)
    
    
    BLACKBOXNTFS: 1 (!blackboxntfs)
    
    
    BLACKBOXPNP: 1 (!blackboxpnp)
    
    
    BLACKBOXWINLOGON: 1
    
    CUSTOMER_CRASH_COUNT:  1
    
    PROCESS_NAME:  SpatialAudioLi
    
    STACK_TEXT:  
    fffffb00`2176dde8 fffff806`0ac9d0fa     : 00000000`0000001a 00000000`00041792 fffff97b`04400ec8 00000010`0c100000 : nt!KeBugCheckEx
    fffffb00`2176ddf0 fffff806`0ac0b9e6     : 00000000`00000000 00000000`00000000 00000000`0000000a fffff97b`04400ec8 : nt!MiDeleteVa+0x153a
    fffffb00`2176def0 fffff806`0ac0bafb     : fffff97c`bd822000 ffff8985`0b187740 fffffb00`00000000 fffffb00`2176e360 : nt!MiWalkPageTablesRecursively+0x776
    fffffb00`2176df90 fffff806`0ac0bafb     : fffff97c`be5ec110 ffff8985`0b187740 fffffb00`00000001 fffffb00`2176e370 : nt!MiWalkPageTablesRecursively+0x88b
    fffffb00`2176e030 fffff806`0ac0bafb     : fffff97c`be5ec000 ffff8985`0b187740 fffffb00`00000002 fffffb00`2176e380 : nt!MiWalkPageTablesRecursively+0x88b
    fffffb00`2176e0d0 fffff806`0ac5de6b     : 00000000`00000000 ffff8985`0b187740 00000000`00000003 fffffb00`2176e390 : nt!MiWalkPageTablesRecursively+0x88b
    fffffb00`2176e170 fffff806`0ac9b991     : fffffb00`2176e310 ffff8985`00000001 00000000`00000002 fffff806`00000000 : nt!MiWalkPageTables+0x36b
    fffffb00`2176e270 fffff806`0b062b84     : 00000000`00040282 fffff806`0aca8b0e ffff998e`00000000 ffff8984`f98d5080 : nt!MiDeletePagablePteRange+0x4f1
    fffffb00`2176e580 fffff806`0acd5094     : ffff8985`0b1870c0 00000000`054f22e0 00000000`00000002 fffff806`00000000 : nt!MiDeleteVadBitmap+0x8c
    fffffb00`2176e610 fffff806`0b062a00     : ffff8985`0b1870c0 ffff8985`0b187800 ffff8985`0b187740 ffff8985`0e8a6080 : nt!MiDeleteFinalPageTables+0xc8
    fffffb00`2176e6d0 fffff806`0b05fe6f     : ffff8985`0b1870c0 fffffb00`2176e790 ffff8985`0e8a6080 ffff8985`0b187508 : nt!MmDeleteProcessAddressSpace+0x64
    fffffb00`2176e720 fffff806`0affb300     : ffff8985`0b187090 ffff8985`0b187090 00000000`00000000 ffff8984`f98f7900 : nt!PspProcessDelete+0x13f
    fffffb00`2176e7b0 fffff806`0ac61277     : 00000000`00000000 00000000`00000000 fffffb00`2176e939 ffff8985`0b1870c0 : nt!ObpRemoveObjectRoutine+0x80
    fffffb00`2176e810 fffff806`0b028d6e     : ffff8984`f98f7900 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ObfDereferenceObjectWithTag+0xc7
    fffffb00`2176e850 fffff806`0b02c9ec     : 00000000`00001240 ffff8985`0e8a6080 00000000`00000000 000000a8`5b95d480 : nt!ObCloseHandleTableEntry+0x29e
    fffffb00`2176e990 fffff806`0ae077b5     : ffff8985`00000000 00000000`00000001 fffffb00`2176ea80 fffffb00`2176ea80 : nt!NtClose+0xec
    fffffb00`2176ea00 00007ffd`9640cf04     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
    000000a8`5b95d1b8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`9640cf04
    
    
    SYMBOL_NAME:  nt!MiDeleteVa+153a
    
    MODULE_NAME: nt
    
    IMAGE_VERSION:  10.0.19041.928
    
    STACK_COMMAND:  .thread ; .cxr ; kb
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    BUCKET_ID_FUNC_OFFSET:  153a
    
    FAILURE_BUCKET_ID:  0x1a_41792_nt!MiDeleteVa
    
    OSPLATFORM_TYPE:  x64
    
    OSNAME:  Windows 10
    
    FAILURE_ID_HASH:  {ad6dfca3-101b-35a8-d6e1-12de9ecbc1f5}
    
    Followup:     MachineOwner
    ---------

    Wednesday, May 12, 2021 2:35 AM

All replies

  • Cause this

    Arg1: 0000000000041792, A corrupt PTE has been detected. Parameter 2 contains the address of
    	the PTE. Parameters 3/4 contain the low/high parts of the PTE.

    IMAGE_NAME: ntkrnlmp.exe


    Also you can need trace that 0000000000041792


    • Edited by Peter2222 Thursday, May 20, 2021 7:58 AM
    Thursday, May 20, 2021 7:56 AM
  • reset your BSOD
    Tuesday, May 25, 2021 7:59 AM
  • Hi,

    Check the error log files and see what happened before the BSOD. This can help you figure out what caused the BSOD, whether it was a driver problem or a problem with a Windows update/piece of software. You can also Google search for the code/error that is showing on the bluescreen. But without your system specs, I can't be more specific than that.

    Thank you

    Friday, May 28, 2021 1:45 PM
  • The BSOD error can cause the system to crash suddenly after a shutdown error. It even becomes difficult to note the error code. 
    It indicates a possible corruption of the disk file system and is most likely caused by bad sectors on your hard disk. This problem is related to the NTFS file system. In order not to kill your PC, the automatic mechanism shuts down your computer.
    The problem is located 
    in the-- NTFS.SYS file. This is a driver file that allows to read and write to the NTFS-system. 
    Solution
    >You can use Windows Defender and Security Essentials to recheck your PC for viruses/malware and clean them.
    >Check the hard drive for corruption using the CHKDSK /F command mentioned above, responding to the warning messages.
    >Check for outdated drivers using a driver update tool. These tools check all the drivers on your system & automatically update them with the latest ones.
    >Run a disk defragmentation tool available in Windows. You can also try to repair individual locations on your hard drive using this software.
    Wednesday, June 2, 2021 12:04 PM
  • Try to reset BSOD
    Saturday, June 26, 2021 6:19 AM

  • MEMORY_MANAGEMENT bsod errors indicate faulty RAM. You can download a free tool called MemTest86+ to check the integrity of your RAM.

    https://www.tenforums.com/tutorials/14201-memtest86-test-ram.html

    I suggest leaving it overnight to scan thoroughly. If any errors are found, I suggest removing or replacing the faulty RAM stick.

    Thanks,
    Chris.



    • Edited by Chris Humm Sunday, June 27, 2021 2:59 AM
    • Proposed as answer by orderingstack Friday, September 17, 2021 2:32 PM
    Sunday, June 27, 2021 2:58 AM
  • Is resetting the BSOD useful?
    • Proposed as answer by orderingstack Friday, September 17, 2021 2:32 PM
    • Unproposed as answer by orderingstack Friday, September 17, 2021 2:32 PM
    Monday, June 28, 2021 3:09 AM
  • These kinds of reviews are really only useful if you're interested in the casual side of the game -- campaign and skirmishes -- and if we're being honest here (as opposed to pre-order evangelists) then the PC Gamer and the PC Invasion (in particular) pieces are the fairest so far. Read them all the way through instead of basing your decision on the score like an illiterate pleb or you'll deserve whatever you get. The other reviews I read (only read English ones) the journalists didn't even properly research the game and they're talking out their asses.

    On the other hand if you're interested in the competitive/multiplayer side of the game then these reviews are pretty useless. Go look through the Steam reviews to find someone who's reviewing from this perspective, or better yet watch some pro streams and VODs and make up your own mind. AoA deserves that much from you at least. Also realize that it's early days and there's no telling how the MP will mature over time, though in my worthless opinion the current indicators augur well.

    Wait and see... i'll try to update with the most serious sites www.best-minecraft-servers.co  i know about. please do the same with your best and respected sites.
    Thursday, July 1, 2021 6:26 AM
  • wow thanks for sharing, that's what i was looking for!
    Thursday, July 1, 2021 1:29 PM
  • it usually comes with QR code you can scan and post for reference
    Thursday, August 26, 2021 9:36 AM
  •  I actually wonder what BSOD will be like in the upcoming Windows 11 :)
    Friday, September 17, 2021 2:35 PM
  • The Verge understands Microsoft will be switching to a Black Screen of Death forcwindow 11, matching the new black logon and shutdown screens.
    Friday, September 24, 2021 1:47 PM
  • Thank you!
    8 hours 10 minutes ago