Windows 10: BSOD after locking the PC. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)

Hello,


One of my users has a consistent BSOD shortly after the PC is locked. Only 1 of 10 PCs with identical OS/ UEFI version and build exhibits the issue. The PC is part of the same GPO that the other 10 are part of. Hibernation and Quick Start are disabled. SFC and DISM show no OS corruption. The PC is on the High Performance power plan with the the option Turn Off Screen disabled. All power saving options in the Advanced Settings of the power plan and USB Power Saving in the Device Manager are off. The PC was re-imaged twice with a clean install of Windows 10 1809 following which the required third party software was installed one-by-one to attempt to identify possible software conflicts. None found (the BSOD was happening even with the bare OS install). The user account was tested on another PC for possible GPO related issues (the user was given another workstation identical in HW/SW/UEFI version and settings). The issue did not occur on the swap PC. No problems were encountered when enrolling the PC to the AD. The PC is running the latest available drivers and UEFI with the Safe Defaults loaded.


The memory was tested with MemTest86 and cleared of any errors. Subsequently, it was swapped with a memory kit from a known good PC. No effect on the problem and the donor PC is stable with the original memory kit.

The PC is stable when tested with Prime 95 for 12 consecutive hours (the test was manually terminated).


The BugCheck information is bellow. Any and all assistance will be very appreciated.


****** BugCheck ******


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: fffff80506acbb70, The address that the exception occurred at
Arg3: fffff6047beeaa78, Exception Record Address
Arg4: fffff6047beea2c0, Context Record Address

Debugging Details:
------------------


KEY_VALUES_STRING: 1


STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING: 17763.1.amd64fre.rs5_release.180914-1434

SYSTEM_MANUFACTURER: System manufacturer

SYSTEM_PRODUCT_NAME: System Product Name

SYSTEM_SKU: SKU

SYSTEM_VERSION: System Version

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 3602

BIOS_DATE: 10/31/2012

BASEBOARD_MANUFACTURER: ASUSTeK Computer INC.

BASEBOARD_PRODUCT: P8P67 DELUXE

BASEBOARD_VERSION: Rev 1.xx

DUMP_TYPE: 1

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff80506acbb70

BUGCHECK_P3: fffff6047beeaa78

BUGCHECK_P4: fffff6047beea2c0

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

FAULTING_IP:
nt!MiDemoteCombinedPte+40
fffff805`06acbb70 498378f001 cmp qword ptr [r8-10h],1

EXCEPTION_RECORD: fffff6047beeaa78 -- (.exr 0xfffff6047beeaa78)
ExceptionAddress: fffff80506acbb70 (nt!MiDemoteCombinedPte+0x0000000000000040)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT: fffff6047beea2c0 -- (.cxr 0xfffff6047beea2c0)
rax=ffffd9ecf67b3000 rbx=860008021457a843 rcx=fffff80506e57320
rdx=ffffd9cf4612ac80 rsi=ffffd9cf4612ac80 rdi=ffff9918063d06e0
rip=fffff80506acbb70 rsp=fffff6047beeacb0 rbp=0000000000000000
r8=8000000000000000 r9=0000000000000000 r10=ffffd9ecf67b3000
r11=ffffd98000000000 r12=fffff80506e56630 r13=fffff6047beeb450
r14=8000000000000000 r15=fffff80506e57320
iopl=0 nv up ei ng nz na pe cy
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010283
nt!MiDemoteCombinedPte+0x40:
fffff805`06acbb70 498378f001 cmp qword ptr [r8-10h],1 ds:002b:7fffffff`fffffff0=????????????????
Resetting default scope

CPU_COUNT: 8

CPU_MHZ: d53

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 2a

CPU_STEPPING: 7

CPU_MICROCODE: 6,2a,7,0 (F,M,S,R) SIG: 2D'00000000 (cache) 2D'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXPNP: 1 (!blackboxpnp)


DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 2

FOLLOWUP_IP:
nt!MiDemoteCombinedPte+40
fffff805`06acbb70 498378f001 cmp qword ptr [r8-10h],1

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: MEC-DW32YV1

ANALYSIS_SESSION_TIME: 05-09-2019 10:10:01.0220

ANALYSIS_VERSION: 10.0.17763.132 amd64fre

LAST_CONTROL_TRANSFER: from fffff80506acaa99 to fffff80506acbb70

STACK_TEXT:
fffff604`7beeacb0 fffff805`06acaa99 : fffff805`06e56630 fffff805`06e57320 fffff604`7beeb350 fffff604`7beeb450 : nt!MiDemoteCombinedPte+0x40
fffff604`7beead80 fffff805`06ac3677 : fffff604`7beeae99 00000000`00000000 00000000`00000003 00000000`00000000 : nt!MiAgePte+0x3b9
fffff604`7beeae10 fffff805`06ac3a6a : fffff604`7beeb450 fffff604`00000000 ffffd9ec`00000000 fffff805`00000000 : nt!MiWalkPageTablesRecursively+0x2c7
fffff604`7beeaf00 fffff805`06ac3a6a : fffff604`7beeb450 00000000`00000000 ffffd9ec`00000001 00000000`00000000 : nt!MiWalkPageTablesRecursively+0x6ba
fffff604`7beeaff0 fffff805`06ac3a6a : fffff604`7beeb450 00000000`00000000 ffffd9ec`00000002 ffffc589`00000000 : nt!MiWalkPageTablesRecursively+0x6ba
fffff604`7beeb0e0 fffff805`06ac2f2a : fffff604`7beeb450 00000000`00000000 fffff604`00000003 00000000`00000000 : nt!MiWalkPageTablesRecursively+0x6ba
fffff604`7beeb1d0 fffff805`06ac25de : fffff604`7beeb450 ffffc589`00000002 fffff805`00000000 00000000`00000000 : nt!MiWalkPageTables+0x1ea
fffff604`7beeb2c0 fffff805`06ac214d : fffff805`06e56c98 fffff805`06e56c98 1524f4df`d7368728 b77c1e86`f2d207cc : nt!MiAgeWorkingSet+0x38e
fffff604`7beeb7d0 fffff805`06b40675 : 00000000`00000000 fffff604`7beeba80 fffff604`7beeb9b0 00000000`00000000 : nt!MiTrimOrAgeWorkingSet+0x7cd
fffff604`7beeb8b0 fffff805`06b3f056 : fffff805`00000003 00000000`00000000 fffff805`06e58980 ffffc589`6b6430f0 : nt!MiProcessWorkingSets+0x255
fffff604`7beeba60 fffff805`06b99c17 : 00000000`00000005 00000000`00000005 00000000`ffffffff 00000000`00000001 : nt!MiWorkingSetManager+0xaa
fffff604`7beebb20 fffff805`06a58a45 : ffffc589`6b76a080 00000000`00000080 fffff805`06b99ad0 e28a44f0`b70f45e8 : nt!KeBalanceSetManager+0x147
fffff604`7beebc10 fffff805`06bd5c3c : ffff8780`67348180 ffffc589`6b76a080 fffff805`06a589f0 880ff685`45660000 : nt!PspSystemThreadStartup+0x55
fffff604`7beebc60 00000000`00000000 : fffff604`7beec000 fffff604`7bee6000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x1c


THREAD_SHA1_HASH_MOD_FUNC: e3a8964b8ac9f4183e9b225b40d450ed3989dd86

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 6207867028f14c037c2add566856f63918a36a8c

THREAD_SHA1_HASH_MOD: 7f608ac2fbce9034a3386b1d51652e4911d30234

FAULT_INSTR_CODE: f0788349

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!MiDemoteCombinedPte+40

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: .cxr 0xfffff6047beea2c0 ; kb

IMAGE_NAME: memory_corruption

BUCKET_ID_FUNC_OFFSET: 40

FAILURE_BUCKET_ID: AV_nt!MiDemoteCombinedPte

BUCKET_ID: AV_nt!MiDemoteCombinedPte

PRIMARY_PROBLEM_CLASS: AV_nt!MiDemoteCombinedPte

TARGET_TIME: 2019-05-08T12:53:52.000Z

OSBUILD: 17763

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: 180914-1434

BUILDLAB_STR: rs5_release

BUILDOSVER_STR: 10.0.17763.1.amd64fre.rs5_release.180914-1434

ANALYSIS_SESSION_ELAPSED_TIME: 1380

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:av_nt!midemotecombinedpte

FAILURE_ID_HASH: {c577c73b-79a7-0c44-6c62-58e1d697b6d8}

Followup: MachineOwner

:)

 

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.

 

Windows 10 BSOD: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

When I start my laptop. It's always restart and show BSOD : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

(Cl.dll). Please give me your suggestion.

 

Windows 10 does not boot, fails with BSOD 0x7E SYSTEM_THREAD_EXCEPTION_NOT_HANDLED in ntfs.sys

I have been using Windows 10 for about three months now on my Lenovo T450s and all of a sudden out of nowhere I cannot boot my PC anymore. I recieve the following BSOD message:

I have looked around the internet for any solutions to this problem but I have not been able to find anything. Unless Windows 10 did once of it's infamous background updates, I have not done any updates to the computer.

I have tried booting into safe mode under a number of different conditions with no luck. All I get is this message. Windows 10 Automatic Repair was, as usual, unable to fix anything.

I do have Ubuntu dual booted with the system however because Windows locks the hard drives I cannot access the Windows partitions.

Any suggestions?