Good afternoon, I can’t decipher the windbg minidump, please help. Here's windbg's analysis. Thanks to everyone who responded.
KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: ffffffffc0000096, The exception code that was not handled
Arg2: ffffab06b5017f73, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
Debugging Details:
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: ExceptionRecord ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: ContextRecord ***
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1453
Key : Analysis.Elapsed.mSec
Value: 8972
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 1
Key : Analysis.IO.Write.Mb
Value: 23
Key : Analysis.Init.CPU.mSec
Value: 750
Key : Analysis.Init.Elapsed.mSec
Value: 77823
Key : Analysis.Memory.CommitPeak.Mb
Value: 99
Key : Analysis.Version.DbgEng
Value: 10.0.27725.1000
Key : Analysis.Version.Description
Value: 10.2408.27.01 amd64fre
Key : Analysis.Version.Ext
Value: 1.2408.27.1
Key : Bugcheck.Code.LegacyAPI
Value: 0x1e
Key : Bugcheck.Code.TargetModel
Value: 0x1e
Key : Failure.Bucket
Value: 0x1E_C0000096_nt!KiDispatchException
Key : Failure.Hash
Value: {505cfaff-0bdc-8a96-0650-5a81952f0ba1}
Key : Stack.Pointer
Value: PRCBException
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Version
Value: 10.0.19041.1
BUGCHECK_CODE: 1e
BUGCHECK_P1: ffffffffc0000096
BUGCHECK_P2: ffffab06b5017f73
BUGCHECK_P3: 0
BUGCHECK_P4: 0
FILE_IN_CAB: 021825-9750-01.dmp
FAULTING_THREAD: ffffab06b2d2f040
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000000
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffff80801012c8e8 fffff8043407e721 : 000000000000001e ffffffffc0000096 ffffab06b5017f73 0000000000000000 : nt!KeBugCheckEx
ffff80801012c8f0 fffff80433fff882 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiDispatchException+0x1447b1
ffff80801012cfb0 fffff80433fff850 : fffff804340130e5 0000000000000042 fffff80433e71b3a ffffab06b2c99aa0 : nt!KxExceptionDispatchOnExceptionStack+0x12
ffffa98dbbf5e9f8 fffff804340130e5 : 0000000000000042 fffff80433e71b3a ffffab06b2c99aa0 ffffa98dbbf5ea89 : nt!KiExceptionDispatchOnExceptionStackContinue
ffffa98dbbf5ea00 fffff8043400e4ef : 7010008004002001 0000000002740000 ffffab0600008000 ffffd40ca44280a0 : nt!KiExceptionDispatch+0x125
ffffa98dbbf5ebe0 ffffab06b5017f73 : ffffffffb8797400 0000000000000001 ffffab06b5002102 ffffffffb8797400 : nt!KiGeneralProtectionFault+0x32f
ffffa98dbbf5ed70 ffffffffb8797400 : 0000000000000001 ffffab06b5002102 ffffffffb8797400 0000000000000000 : 0xffffab06b5017f73 ffffa98dbbf5ed78 0000000000000001 : ffffab06b5002102 ffffffffb8797400 0000000000000000 fffff8043484f800 : 0xffffffffb8797400
ffffa98dbbf5ed80 ffffab06b5002102 : ffffffffb8797400 0000000000000000 fffff8043484f800 0000000000000000 : 0x1
ffffa98dbbf5ed88 ffffffffb8797400 : 0000000000000000 fffff8043484f800 0000000000000000 fffff80433e3f40c : 0xffffab06b5002102 ffffa98dbbf5ed90 0000000000000000 : fffff8043484f800 0000000000000000 fffff80433e3f40c 1a0000037c7e9863 : 0xffffffffb8797400
SYMBOL_NAME: nt!KiDispatchException+1447b1
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.19041.5486
STACK_COMMAND: .process /r /p 0xffffab0698702080; .thread 0xffffab06b2d2f040 ; kb
BUCKET_ID_FUNC_OFFSET: 1447b1
FAILURE_BUCKET_ID: 0x1E_C0000096_nt!KiDispatchException
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {505cfaff-0bdc-8a96-0650-5a81952f0ba1}
Followup: MachineOwner