Windows 10: Blue Screen SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

Pls Help.




Microsoft R Windows Debugger Version 10.0.18362.1 AMD64

Copyright 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 4 procs Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

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

Machine Name:

Kernel base = 0xfffff806`41c00000 PsLoadedModuleList = 0xfffff806`42048150

Debug session time: Fri Apr 17 15:28:43.297 2020 UTC + 3:00

System Uptime: 0 days 21:15:55.113

Loading Kernel Symbols

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

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

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

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

Loading User Symbols



Loading unloaded module list

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

For analysis of this file, run !analyze -v

2: kd> !analyze -v

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

* *

* Bugcheck Analysis *

* *

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



SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 7e

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: ffffffffc0000005, The exception code that was not handled

Arg2: fffff80651b31ed6, The address that the exception occurred at

Arg3: ffffe70d368af658, Exception Record Address

Arg4: ffff830059266930, Context Record Address



Debugging Details:

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





KEY_VALUES_STRING: 1



Key : AV.Fault

Value: Read





PROCESSES_ANALYSIS: 1



SERVICE_ANALYSIS: 1



STACKHASH_ANALYSIS: 1



TIMELINE_ANALYSIS: 1





DUMP_CLASS: 1



DUMP_QUALIFIER: 401



BUILD_VERSION_STRING: 18362.1.amd64fre.19h1_release.190318-1202



SYSTEM_MANUFACTURER: Dell Inc.



SYSTEM_PRODUCT_NAME: Latitude 7480



SYSTEM_SKU: 07A0



BIOS_VENDOR: Dell Inc.



BIOS_VERSION: 1.9.3



BIOS_DATE: 03/09/2018



BASEBOARD_MANUFACTURER: Dell Inc.



BASEBOARD_PRODUCT: 00F6D3



BASEBOARD_VERSION: A00



DUMP_TYPE: 1



BUGCHECK_P1: ffffffffc0000005



BUGCHECK_P2: fffff80651b31ed6



BUGCHECK_P3: ffffe70d368af658



BUGCHECK_P4: ffff830059266930



EXCEPTION_CODE: NTSTATUS 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.



FAULTING_IP:

immunetprotect+1ed6

fffff806`51b31ed6 48394a18 cmp qword ptr [rdx+18h],rcx



EXCEPTION_RECORD: ffffe70d368af658 -- .exr 0xffffe70d368af658

ExceptionAddress: fffff80651b31ed6 immunetprotect+0x0000000000001ed6

ExceptionCode: c0000005 Access violation

ExceptionFlags: 00000000

NumberParameters: 2

Parameter[0]: 0000000000000000

Parameter[1]: ffffffffffffffff

Attempt to read from address ffffffffffffffff



CONTEXT: ffff830059266930 -- .cxr 0xffff830059266930

rax=0000000000000000 rbx=ffffe70d368af930 rcx=ffff980cdef53c00

rdx=0041006500700079 rsi=0000000000000008 rdi=ffff980cdef53c00

rip=fffff80651b31ed6 rsp=ffffe70d368af890 rbp=ffffe70d368af939

r8=ffff980cdee693a0 r9=006900460020006d r10=ffff980cb1261700

r11=fffff80651b50c40 r12=0000000000000030 r13=0000000000000000

r14=ffff980cb1f64c00 r15=ffff980ce06de010

iopl=0 nv up ei ng nz na po cy

cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050287

immunetprotect+0x1ed6:

fffff806`51b31ed6 48394a18 cmp qword ptr [rdx+18h],rcx ds:002b:00410065`00700091=????????????????

Resetting default scope



CPU_COUNT: 4



CPU_MHZ: a98



CPU_VENDOR: GenuineIntel



CPU_FAMILY: 6



CPU_MODEL: 8e



CPU_STEPPING: 9



CPU_MICROCODE: 6,8e,9,0 F,M,S,R SIG: 8E'00000000 cache 8E'00000000 init



BLACKBOXBSD: 1 !blackboxbsd





BLACKBOXNTFS: 1 !blackboxntfs





BLACKBOXPNP: 1 !blackboxpnp





BLACKBOXWINLOGON: 1



DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT



PROCESS_NAME: System



CURRENT_IRQL: 2



FOLLOWUP_IP:

immunetprotect+1ed6

fffff806`51b31ed6 48394a18 cmp qword ptr [rdx+18h],rcx



BUGCHECK_STR: AV



READ_ADDRESS: ffffffffffffffff



ERROR_CODE: NTSTATUS 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.



EXCEPTION_CODE_STR: c0000005



EXCEPTION_PARAMETER1: 0000000000000000



EXCEPTION_PARAMETER2: ffffffffffffffff



ANALYSIS_SESSION_HOST: UA1-ISACCI



ANALYSIS_SESSION_TIME: 04-17-2020 18:06:20.0025



ANALYSIS_VERSION: 10.0.18362.1 amd64fre



BAD_STACK_POINTER: ffff8300592660c8



LAST_CONTROL_TRANSFER: from fffff80642ef872f to fffff80651b31ed6



STACK_TEXT:

ffffe70d`368af890 fffff806`42ef872f : 000000b2`426b4f43 00000000`00989680 ffff980c`def53c00 ffff980c`b1f64c00 : immunetprotect+0x1ed6

ffffe70d`368af8d0 fffff806`42ef69f3 : 00000000`00000000 ffff980c`def53c10 00000000`00000000 00000000`00000000 : FLTMGR!FltpFreeInstance+0x32f

ffffe70d`368af9a0 fffff806`42ef67d3 : ffff980c`dfa779c0 00000000`00000008 ffff980c`dfa77870 ffff980c`df26d180 : FLTMGR!FltpFreeVolume+0x1df

ffffe70d`368af9e0 fffff806`42ef6435 : ffff980c`e12ae090 fffff806`42ef6420 ffff980c`b128fcc0 fffff806`42ef87a0 : FLTMGR!FltpCleanupDeviceObject+0x6b

ffffe70d`368afa40 fffff806`41cf43c5 : ffff980c`b128fcc0 ffff980c`df26d000 fffff806`42ef8700 ffff980c`b128fcc0 : FLTMGR!FltpFastIoDetachDeviceWorker+0x15

ffffe70d`368afa70 fffff806`41c6bce5 : ffff980c`df26d040 00000000`00000080 ffff980c`b1289340 ffff82e6`00000001 : nt!ExpWorkerThread+0x105

ffffe70d`368afb10 fffff806`41dc99ca : ffff8300`5933a180 ffff980c`df26d040 fffff806`41c6bc90 ffff82e6`c0be39da : nt!PspSystemThreadStartup+0x55

ffffe70d`368afb60 00000000`00000000 : ffffe70d`368b0000 ffffe70d`368a9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x2a





THREAD_SHA1_HASH_MOD_FUNC: 60ab1afa242af7d31bd5c5e638b81196b2e825bd



THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 4c08d8c8ac72d5a2cf4dcae1ac7ee8905ccdd78f



THREAD_SHA1_HASH_MOD: 62fc48cbefe951e793a6558c513448c41b454d19



FAULT_INSTR_CODE: 184a3948



SYMBOL_STACK_INDEX: 0



SYMBOL_NAME: immunetprotect+1ed6



FOLLOWUP_NAME: MachineOwner



MODULE_NAME: immunetprotect



IMAGE_NAME: immunetprotect.sys



DEBUG_FLR_IMAGE_TIMESTAMP: 5e3d51c8



STACK_COMMAND: .cxr 0xffff830059266930 ; kb



BUCKET_ID_FUNC_OFFSET: 1ed6



FAILURE_BUCKET_ID: AV_STACKPTR_ERROR_immunetprotect!unknown_function



BUCKET_ID: AV_STACKPTR_ERROR_immunetprotect!unknown_function



PRIMARY_PROBLEM_CLASS: AV_STACKPTR_ERROR_immunetprotect!unknown_function



TARGET_TIME: 2020-04-17T12:28:43.000Z



OSBUILD: 18362



OSSERVICEPACK: 0



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: 3ae8



ANALYSIS_SOURCE: KM



FAILURE_ID_HASH_STRING: km:av_stackptr_error_immunetprotect!unknown_function



FAILURE_ID_HASH: {de736265-4e66-8aeb-37dd-e5f394043a58}



Followup: MachineOwner

---------

:)

 

BSOD: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED + stornvme.sys

Steps provided here should fix the error:
https://pc-mac-help.com/blog/fix-system_thread_exception_not_handled-blue-screen-error-windows-10

 

BSOD: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

Hello Ethan,

We realize the inconvenience you are experiencing with BSOD SYSTEM_THREAD_EXCEPTION_NOT_HANDLED on your system. We will certainly help you.

Blue screens (BSOD) is mostly occur due to hardware and sometimes due to incompatible software. In a lot of cases it is a corrupted driver or a driver conflict. The most common causes of blue screens are overheating, faulty RAM, video card problem
and BIOS.

The SYSTEM_THREAD_EXCEPTION_NOT_HANDLED bug check has a value of 0x0000007E. This bug check indicates that a system thread generated an exception that the error handler did not catch.

We suggest you to kindly follow the steps from the below article and check if it helps:

Troubleshoot blue screen errors

Let us know the status of the issue and the result of troubleshooting. We will be happy to assist you further.

Thank you.

 

Blue Screen

Hi,





Blue screens could be caused by problems with your computer’s hardware or with its driver. Still, we
would like to know more about the issue. Please clarify the following:

• Did you get a STOP code?
• Did you install any hardware or driver recently?

For basic troubleshooting steps to resolve blue screen errors, we suggest checking out this
article and simply follow the steps.



Feel free to contact us if you need further help.