Windows 10: PC suddenly keeps crashing with this as the dump

Microsoft R Windows Debugger Version 10.0.19528.1000 AMD64Copyright c Microsoft Corporation. All rights reserved.Loading Dump File [C:\Windows\MEMORY.DMP]Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.Symbol search path is: srv*Executable search path is: Windows 10 Kernel Version 18362 MP 12 procs Free x64Product: WinNt, suite: TerminalServer SingleUserTS18362.1.amd64fre.19h1_release.190318-1202Machine Name:Kernel base = 0xfffff802`7d600000 PsLoadedModuleList = 0xfffff802`7da48170Debug session time: Fri Jun 19 00:02:34.701 2020 UTC + 4:00System Uptime: 0 days 6:10:31.368Loading Kernel Symbols.................................................................Page 12fbb3 not present in the dump file. Type ".hh dbgerr004" for details....................................................................................................................Loading User SymbolsLoading unloaded module list............For analysis of this file, run !analyze -vnt!KeBugCheckEx:fffff802`7d7c2390 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff10f`ea3b8590=000000000000000a5: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************IRQL_NOT_LESS_OR_EQUAL aAn attempt was made to access a pageable or completely invalid address at aninterrupt request level IRQL that is too high. This is usuallycaused by drivers using improper addresses.If a kernel debugger is available get the stack backtrace.Arguments:Arg1: 0000000000000186, memory referencedArg2: 0000000000000002, IRQLArg3: 0000000000000000, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation only on chips which support this level of statusArg4: fffff8027d714ffd, address which referenced memoryDebugging Details:------------------KEY_VALUES_STRING: 1 Key : Analysis.CPU.Sec Value: 2 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on DESKTOP-O4TDE7G Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.Sec Value: 30 Key : Analysis.Memory.CommitPeak.Mb Value: 64 Key : Analysis.System Value: CreateObjectADDITIONAL_XML: 1BUGCHECK_CODE: aBUGCHECK_P1: 186BUGCHECK_P2: 2BUGCHECK_P3: 0BUGCHECK_P4: fffff8027d714ffdREAD_ADDRESS: 0000000000000186 BLACKBOXBSD: 1 !blackboxbsdBLACKBOXNTFS: 1 !blackboxntfsBLACKBOXWINLOGON: 1PROCESS_NAME: SystemTRAP_FRAME: fffff10fea3b86d0 -- .trap 0xfffff10fea3b86d0NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=0000000000000002 rbx=0000000000000000 rcx=ffffb7006c280180rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000rip=fffff8027d714ffd rsp=fffff10fea3b8860 rbp=0000000000000000 r8=0000000000000000 r9=0000000000000000 r10=0000000000000000r11=fffff780000003b0 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0 nv up ei pl zr na po ncnt!KiSwapThread+0xb7d:fffff802`7d714ffd 410fb6b686010000 movzx esi,byte ptr [r14+186h] ds:00000000`00000186=??Resetting default scopeBAD_STACK_POINTER: fffff10fea3b8588STACK_TEXT: fffff10f`ea3b8588 fffff802`7d7d41e9 : 00000000`0000000a 00000000`00000186 00000000`00000002 00000000`00000000 : nt!KeBugCheckExfffff10f`ea3b8590 fffff802`7d7d0529 : ffffb700`6c280180 fffff802`7d7c955f 00000067`b4bbbdff 00000000`00000001 : nt!KiBugCheckDispatch+0x69fffff10f`ea3b86d0 fffff802`7d714ffd : ffffb700`6c280180 00000000`fffffffe ffffb700`ffffffff 00000000`00000001 : nt!KiPageFault+0x469fffff10f`ea3b8860 fffff802`7d713f04 : 00000000`00000000 fffff802`00000000 00000000`00000000 ffffc701`00000000 : nt!KiSwapThread+0xb7dfffff10f`ea3b8900 fffff802`7d7136a5 : 00000000`00000010 ffffc701`00000000 ffffc701`a36e5100 00000000`00000000 : nt!KiCommitThreadWait+0x144fffff10f`ea3b89a0 fffff802`7dcbd78b : ffffc701`b44633e0 fffff10f`00000006 00000000`00000001 ffffa5d9`21ebc001 : nt!KeWaitForSingleObject+0x255fffff10f`ea3b8a80 fffff802`7d7d4151 : ffffc701`b88e9080 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtWaitForSingleObject+0x10bfffff10f`ea3b8b00 00007ffd`e2fdc0f4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExitPico+0x2bc0000003a`4c1ffb68 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`e2fdc0f4SYMBOL_NAME: nt!KiSwapThread+b7dMODULE_NAME: ntIMAGE_NAME: ntkrnlmp.exeSTACK_COMMAND: .thread ; .cxr ; kbBUCKET_ID_FUNC_OFFSET: b7dFAILURE_BUCKET_ID: AV_STACKPTR_ERROR_nt!KiSwapThreadOS_VERSION: 10.0.18362.1BUILDLAB_STR: 19h1_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {f711f20c-346e-2775-2486-4da10b7f0622}Followup: MachineOwner---------5: kd> lmvm ntBrowse full module liststart end module namefffff802`7d600000 fffff802`7e0b7000 nt pdb symbols C:\ProgramData\Dbg\sym\ntkrnlmp.pdb\DCA4AD4BEEB4746D48F84C0125019E431\ntkrnlmp.pdb Loaded symbol image file: ntkrnlmp.exe Image path: ntkrnlmp.exe Image name: ntkrnlmp.exe Browse all global symbols functions data Image was built with /Brepro flag. Timestamp: B785E389 This is a reproducible build file hash, not a timestamp CheckSum: 0097940F ImageSize: 00AB7000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4 Information from resource tables:

:)

 

Windows 10 keeps crashing

Hi,

There are many possible reasons why the computer will keeps on crashing. One of which is missing or corrupted system files. For us to further isolate the issue, we suggest answering the following questions:

• What exactly are you accessing/doing when the computer crashes?
• Were you still able to login to the computer after it happens?
• Can you send us a screenshot of the error messages or mini dump that you've received?

In the meantime, if you're seeing a blue screen when the computer crashes, we suggest following the steps on this article:
Troubleshoot blue screen errors. Kindly choose the appropriate answer to the category
"When did you get the error?".

We'll wait for your response on this matter.

 

IE 11 11.0.14393.1715 after recent update crashes. I have a crash dump.

I have taken the steps you listed previously along with any other "fix" I could find. The browser still fails.

Can I upload the crash dump somewhere so someone with Windows expertise can take a look?

 

WinDBG - The Basics for Debugging Crash Dumps in Windows 10  


Please note that the tutorial is meant for system crash dumps, game crash dumps contain different information and thus not all the steps in the tutorial work for a game crash dump.