R
RobertRamza
I've got a brand new HP Envy that can't share my desktop while running in MS Teams, which I need for work.
I've run all the updates, even took it back to the Microsoft store and they did a factory reboot. A month later, and I am still crashing. I need help looking at minidump files. The most recent minidump info is below:
Microsoft (R) Windows Debugger Version 10.0.19528.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Owner\OneDrive\Documents\Minidump files\032420-8906-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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff801`81400000 PsLoadedModuleList = 0xfffff801`81848150
Debug session time: Tue Mar 24 17:05:14.737 2020 (UTC - 5:00)
System Uptime: 0 days 20:56:01.453
Loading Kernel Symbols
...............................................................
................................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
..................................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff801`815c2380 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff504`b28f1f20=000000000000007e
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffff80000003, The exception code that was not handled
Arg2: fffff8018145a1c8, The address that the exception occurred at
Arg3: fffff504b28f2f38, Exception Record Address
Arg4: fffff504b28f2780, Context Record Address
Debugging Details:
------------------
*** WARNING: Unable to verify checksum for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 6
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-AVRL4AI
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 34
Key : Analysis.Memory.CommitPeak.Mb
Value: 70
Key : Analysis.System
Value: CreateObject
ADDITIONAL_XML: 1
BUGCHECK_CODE: 7e
BUGCHECK_P1: ffffffff80000003
BUGCHECK_P2: fffff8018145a1c8
BUGCHECK_P3: fffff504b28f2f38
BUGCHECK_P4: fffff504b28f2780
EXCEPTION_RECORD: fffff504b28f2f38 -- (.exr 0xfffff504b28f2f38)
ExceptionAddress: fffff8018145a1c8 (nt!KeCheckStackAndTargetAddress+0x0000000000000048)
ExceptionCode: 80000003 (Break instruction exception)
ExceptionFlags: 00000010
NumberParameters: 1
Parameter[0]: 0000000000000000
CONTEXT: fffff504b28f2780 -- (.cxr 0xfffff504b28f2780)
rax=fffff504b28f3198 rbx=fffff504b28f43b8 rcx=0000000000000000
rdx=fffff504b28f43b8 rsi=fffff504b28f39c0 rdi=0000000000000000
rip=fffff8018145a1c8 rsp=fffff504b28f3170 rbp=fffff504b28f3780
r8=fffff504b28f39c0 r9=fffff504b28f3800 r10=0000fffff8018159
r11=fffff504b28f3208 r12=fffff504b28f4c10 r13=fffff504b28f4178
r14=fffff504b28f3800 r15=fffff80181916d84
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00040246
nt!KeCheckStackAndTargetAddress+0x48:
fffff801`8145a1c8 cc int 3
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION} Breakpoint A breakpoint has been reached.
EXCEPTION_CODE_STR: 80000003
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_STR: 0x80000003
TRAP_FRAME: fffff80181361e70 -- (.trap 0xfffff80181361e70)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=cccccccccccccccc rsp=ccccccc310423101 rbp=cccccccccccccccc
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=1 vif nv up ei pl zr na po nc
418b:cccccccc`cccccccc ?? ???
Resetting default scope
BAD_STACK_POINTER: ccccccc310423101
UNALIGNED_STACK_POINTER: ccccccc310423101
STACK_TEXT:
fffff504`b28f3170 fffff801`8159d305 : 00000000`00000000 fffff504`b28f4c10 fffff801`931c3efc fffff504`b28f3790 : nt!KeCheckStackAndTargetAddress+0x48
fffff504`b28f31a0 fffff801`815cb1b2 : fffff504`b28f4c10 fffff504`b28f3780 00000000`00000000 00000000`0010001f : nt!_C_specific_handler+0x45
fffff504`b28f3210 fffff801`814fa2d5 : 00000000`000000ca 00000000`00000000 fffff504`b28f3780 00007fff`ffff0000 : nt!RtlpExecuteHandlerForException+0x12
fffff504`b28f3240 fffff801`814fe86e : fffff504`b28f4178 fffff504`b28f3ec0 fffff504`b28f4178 ffffcd0e`c1d5d600 : nt!RtlDispatchException+0x4a5
fffff504`b28f3990 fffff801`815d431d : fffffe7f`3f9fc000 fffff504`b28f4220 ffff8000`00000000 00000000`00000000 : nt!KiDispatchException+0x16e
fffff504`b28f4040 fffff801`815d0505 : ffffcd0e`00000000 00000000`00000001 fffff504`b28f4a10 ffffcd0e`b963c000 : nt!KiExceptionDispatch+0x11d
fffff504`b28f4220 00000000`00000000 : fffff801`95cb53a8 ffffcd0e`c1c15cc0 fffff801`95ca315f 00000000`00000001 : nt!KiPageFault+0x445
SYMBOL_NAME: nt!KeCheckStackAndTargetAddress+48
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.18362.720
STACK_COMMAND: .cxr 0xfffff504b28f2780 ; kb
BUCKET_ID_FUNC_OFFSET: 48
FAILURE_BUCKET_ID: AV_STACKPTR_ERROR_nt!KeCheckStackAndTargetAddress
OS_VERSION: 10.0.18362.1
BUILDLAB_STR: 19h1_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {a7fbb798-1fbb-fe00-60e7-70b4789edf37}
Followup: MachineOwner
---------
Any pointers? What do I do next?
Continue reading...
I've run all the updates, even took it back to the Microsoft store and they did a factory reboot. A month later, and I am still crashing. I need help looking at minidump files. The most recent minidump info is below:
Microsoft (R) Windows Debugger Version 10.0.19528.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Owner\OneDrive\Documents\Minidump files\032420-8906-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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff801`81400000 PsLoadedModuleList = 0xfffff801`81848150
Debug session time: Tue Mar 24 17:05:14.737 2020 (UTC - 5:00)
System Uptime: 0 days 20:56:01.453
Loading Kernel Symbols
...............................................................
................................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
..................................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff801`815c2380 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff504`b28f1f20=000000000000007e
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffff80000003, The exception code that was not handled
Arg2: fffff8018145a1c8, The address that the exception occurred at
Arg3: fffff504b28f2f38, Exception Record Address
Arg4: fffff504b28f2780, Context Record Address
Debugging Details:
------------------
*** WARNING: Unable to verify checksum for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 6
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-AVRL4AI
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 34
Key : Analysis.Memory.CommitPeak.Mb
Value: 70
Key : Analysis.System
Value: CreateObject
ADDITIONAL_XML: 1
BUGCHECK_CODE: 7e
BUGCHECK_P1: ffffffff80000003
BUGCHECK_P2: fffff8018145a1c8
BUGCHECK_P3: fffff504b28f2f38
BUGCHECK_P4: fffff504b28f2780
EXCEPTION_RECORD: fffff504b28f2f38 -- (.exr 0xfffff504b28f2f38)
ExceptionAddress: fffff8018145a1c8 (nt!KeCheckStackAndTargetAddress+0x0000000000000048)
ExceptionCode: 80000003 (Break instruction exception)
ExceptionFlags: 00000010
NumberParameters: 1
Parameter[0]: 0000000000000000
CONTEXT: fffff504b28f2780 -- (.cxr 0xfffff504b28f2780)
rax=fffff504b28f3198 rbx=fffff504b28f43b8 rcx=0000000000000000
rdx=fffff504b28f43b8 rsi=fffff504b28f39c0 rdi=0000000000000000
rip=fffff8018145a1c8 rsp=fffff504b28f3170 rbp=fffff504b28f3780
r8=fffff504b28f39c0 r9=fffff504b28f3800 r10=0000fffff8018159
r11=fffff504b28f3208 r12=fffff504b28f4c10 r13=fffff504b28f4178
r14=fffff504b28f3800 r15=fffff80181916d84
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00040246
nt!KeCheckStackAndTargetAddress+0x48:
fffff801`8145a1c8 cc int 3
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION} Breakpoint A breakpoint has been reached.
EXCEPTION_CODE_STR: 80000003
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_STR: 0x80000003
TRAP_FRAME: fffff80181361e70 -- (.trap 0xfffff80181361e70)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=cccccccccccccccc rsp=ccccccc310423101 rbp=cccccccccccccccc
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=1 vif nv up ei pl zr na po nc
418b:cccccccc`cccccccc ?? ???
Resetting default scope
BAD_STACK_POINTER: ccccccc310423101
UNALIGNED_STACK_POINTER: ccccccc310423101
STACK_TEXT:
fffff504`b28f3170 fffff801`8159d305 : 00000000`00000000 fffff504`b28f4c10 fffff801`931c3efc fffff504`b28f3790 : nt!KeCheckStackAndTargetAddress+0x48
fffff504`b28f31a0 fffff801`815cb1b2 : fffff504`b28f4c10 fffff504`b28f3780 00000000`00000000 00000000`0010001f : nt!_C_specific_handler+0x45
fffff504`b28f3210 fffff801`814fa2d5 : 00000000`000000ca 00000000`00000000 fffff504`b28f3780 00007fff`ffff0000 : nt!RtlpExecuteHandlerForException+0x12
fffff504`b28f3240 fffff801`814fe86e : fffff504`b28f4178 fffff504`b28f3ec0 fffff504`b28f4178 ffffcd0e`c1d5d600 : nt!RtlDispatchException+0x4a5
fffff504`b28f3990 fffff801`815d431d : fffffe7f`3f9fc000 fffff504`b28f4220 ffff8000`00000000 00000000`00000000 : nt!KiDispatchException+0x16e
fffff504`b28f4040 fffff801`815d0505 : ffffcd0e`00000000 00000000`00000001 fffff504`b28f4a10 ffffcd0e`b963c000 : nt!KiExceptionDispatch+0x11d
fffff504`b28f4220 00000000`00000000 : fffff801`95cb53a8 ffffcd0e`c1c15cc0 fffff801`95ca315f 00000000`00000001 : nt!KiPageFault+0x445
SYMBOL_NAME: nt!KeCheckStackAndTargetAddress+48
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.18362.720
STACK_COMMAND: .cxr 0xfffff504b28f2780 ; kb
BUCKET_ID_FUNC_OFFSET: 48
FAILURE_BUCKET_ID: AV_STACKPTR_ERROR_nt!KeCheckStackAndTargetAddress
OS_VERSION: 10.0.18362.1
BUILDLAB_STR: 19h1_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {a7fbb798-1fbb-fe00-60e7-70b4789edf37}
Followup: MachineOwner
---------
Any pointers? What do I do next?
Continue reading...