Windows 10: BSOD Win10 tdx.sys - after update

PC restarted to install latest updates and now it just restarts with the error SYSTEM_THREAD_EXCEPTION_NOT_HANDLED with reference to the file tdx.sys.

I was hoping someone could have a look at the extract below from the dmp file and let me know your thoughts.


Thanks


Microsoft (R) Windows Debugger Version 10.0.17134.12 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [E:\Data Backups\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.


************* Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 10 Kernel Version 16299 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 16299.15.amd64fre.rs3_release.170928-1534
Machine Name:
Kernel base = 0xfffff803`a3400000 PsLoadedModuleList = 0xfffff803`a3767130
Debug session time: Fri Aug 10 09:04:10.879 2018 (UTC + 1:00)
System Uptime: 0 days 0:01:00.657
Loading Kernel Symbols
...............................................................
................................................................
..........................................................
Loading User Symbols

Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7E, {ffffffffc0000005, fffff8047e4614ed, ffff8d8d694f4608, ffff8d8d694f3e50}

*** ERROR: Module load completed but symbols could not be loaded for siserial.sys
Probably caused by : tdx.sys ( tdx!TdxTdiDispatchInternalDeviceControl+3d )

Followup: MachineOwner
---------

3: 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: fffff8047e4614ed, The address that the exception occurred at
Arg3: ffff8d8d694f4608, Exception Record Address
Arg4: ffff8d8d694f3e50, Context Record Address

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


KEY_VALUES_STRING: 1


TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING: 16299.15.amd64fre.rs3_release.170928-1534

SYSTEM_MANUFACTURER: Hewlett-Packard

SYSTEM_PRODUCT_NAME: HP ENVY Notebook

SYSTEM_SKU: M5L32EA#ABU

SYSTEM_VERSION: Type1ProductConfigId

BIOS_VENDOR: Insyde

BIOS_VERSION: F.35

BIOS_DATE: 03/03/2016

BASEBOARD_MANUFACTURER: Hewlett-Packard

BASEBOARD_PRODUCT: 80DE

BASEBOARD_VERSION: 64.36

DUMP_TYPE: 1

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8047e4614ed

BUGCHECK_P3: ffff8d8d694f4608

BUGCHECK_P4: ffff8d8d694f3e50

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

FAULTING_IP:
tdx!TdxTdiDispatchInternalDeviceControl+3d
fffff804`7e4614ed 488b4820 mov rcx,qword ptr [rax+20h]

EXCEPTION_RECORD: ffff8d8d694f4608 -- (.exr 0xffff8d8d694f4608)
ExceptionAddress: fffff8047e4614ed (tdx!TdxTdiDispatchInternalDeviceControl+0x000000000000003d)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000020
Attempt to read from address 0000000000000020

CONTEXT: ffff8d8d694f3e50 -- (.cxr 0xffff8d8d694f3e50)
rax=0000000000000000 rbx=ffffb58580f43db0 rcx=ffffb5857cc81e40
rdx=ffffb58580f43db0 rsi=0000000000000000 rdi=ffffb58580f43e80
rip=fffff8047e4614ed rsp=ffff8d8d694f4840 rbp=0000000000000080
r8=000000000000000f r9=ffffb5857cc81e40 r10=ffff940113947800
r11=0000000000000000 r12=0000000000000648 r13=0000000000000001
r14=ffffb58577cc9040 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202
tdx!TdxTdiDispatchInternalDeviceControl+0x3d:
fffff804`7e4614ed 488b4820 mov rcx,qword ptr [rax+20h] ds:002b:00000000`00000020=????????????????
Resetting default scope

CPU_COUNT: 4

CPU_MHZ: 95a

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3d

CPU_STEPPING: 4

CPU_MICROCODE: 6,3d,4,0 (F,M,S,R) SIG: 22'00000000 (cache) 22'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXPNP: 1 (!blackboxpnp)


PROCESS_NAME: System

CURRENT_IRQL: 0

FOLLOWUP_IP:
tdx!TdxTdiDispatchInternalDeviceControl+3d
fffff804`7e4614ed 488b4820 mov rcx,qword ptr [rax+20h]

BUGCHECK_STR: AV

READ_ADDRESS: 0000000000000020

DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE

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: 0000000000000020

ANALYSIS_SESSION_HOST: DESKTOP-K218O24

ANALYSIS_SESSION_TIME: 08-10-2018 13:43:22.0396

ANALYSIS_VERSION: 10.0.17134.12 x86fre

LAST_CONTROL_TRANSFER: from fffff803a3434669 to fffff8047e4614ed

STACK_TEXT:
ffff8d8d`694f4840 fffff803`a3434669 : fffff804`00000000 ffffb585`812690d8 00000000`00000080 00000000`00000004 : tdx!TdxTdiDispatchInternalDeviceControl+0x3d
ffff8d8d`694f48b0 fffff804`7f8f4a78 : fffff804`7f96883f fffff804`7f968770 ffffb585`8126d4d8 ffffb585`80f43228 : nt!IofCallDriver+0x59
ffff8d8d`694f48f0 fffff804`7fa2198a : fffff804`7f9686bf fffff804`7f8f3013 ffffb585`8126d4d8 fffff803`a36ae11f : siserial+0x4a78
ffff8d8d`694f4930 fffff804`7f9380d7 : fffff804`7fa35080 ffff8d8d`694f4a68 00000000`00000011 ffff8d8d`694f4a68 : siserial+0x13198a
ffff8d8d`694f4970 fffff804`7f93f75e : ffffb585`812690c8 ffff8d8d`694f4a68 00000000`00000011 00000000`00000001 : siserial+0x480d7
ffff8d8d`694f4a40 fffff804`7f95b9ad : ffffb585`81269000 ffffb585`80f40958 ffffb585`80f43290 ffffb585`80f435f8 : siserial+0x4f75e
ffff8d8d`694f4ae0 fffff804`7f95a1a3 : ffffb585`80f431b0 ffffb585`80f43228 00000000`00000000 00000000`00000000 : siserial+0x6b9ad
ffff8d8d`694f4b40 fffff804`7f959d4a : ffffb585`80f431b0 fffff804`7f959d20 00000000`00000010 00000000`00000246 : siserial+0x6a1a3
ffff8d8d`694f4bd0 fffff803`a3516c07 : ffffb585`80f43228 fffff804`7f959d20 ffff9401`13946180 00000425`b59bbfff : siserial+0x69d4a
ffff8d8d`694f4c10 fffff803`a357ccc6 : ffff9401`13946180 ffffb585`80ee4040 fffff803`a3516bc0 00000000`00000000 : nt!PspSystemThreadStartup+0x47
ffff8d8d`694f4c60 00000000`00000000 : ffff8d8d`694f5000 ffff8d8d`694ef000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


THREAD_SHA1_HASH_MOD_FUNC: bc664042d9e5ac003a47bcc69c83f7e32945de3b

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: d9d914f74eda1a8cd184ecc416099a4fd0272724

THREAD_SHA1_HASH_MOD: 745ad636fc84faea4a79f53b8294cbf80a5f2c34

FAULT_INSTR_CODE: 20488b48

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: tdx!TdxTdiDispatchInternalDeviceControl+3d

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: tdx

IMAGE_NAME: tdx.sys

DEBUG_FLR_IMAGE_TIMESTAMP: cbc8cf3

STACK_COMMAND: .cxr 0xffff8d8d694f3e50 ; kb

BUCKET_ID_FUNC_OFFSET: 3d

FAILURE_BUCKET_ID: AV_tdx!TdxTdiDispatchInternalDeviceControl

BUCKET_ID: AV_tdx!TdxTdiDispatchInternalDeviceControl

PRIMARY_PROBLEM_CLASS: AV_tdx!TdxTdiDispatchInternalDeviceControl

TARGET_TIME: 2018-08-10T08:04:10.000Z

OSBUILD: 16299

OSSERVICEPACK: 0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 784

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2018-03-01 05:36:55

BUILDDATESTAMP_STR: 170928-1534

BUILDLAB_STR: rs3_release

BUILDOSVER_STR: 10.0.16299.15.amd64fre.rs3_release.170928-1534

ANALYSIS_SESSION_ELAPSED_TIME: 1989

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:av_tdx!tdxtdidispatchinternaldevicecontrol

FAILURE_ID_HASH: {78e8b4c1-007b-6ff1-2a23-47e3c9917b14}

Followup: MachineOwner
---------

:)

 

Win10: windows update stuck at never ending loop ?

When in win10:

• Update&security -> Windows update -> Finding update... .... .... ....

Planning to download the latest Win10.ISO (vers.1803) and manually update:
- Then wait that my ordered new SSD arrives and clone the old HDD to it.

 

wdf01000.sys and ntoskrnl.exe BSOD

I'm on Windows 10, 64bit

Basically, whenever I try to update my LPC controller through Device Manager, BSOD with WDF_VIOLATION occurs (culprit being wdf01000.sys)

So I try to use the driver verifier to see which driver is causing the BSOD, but then it causes BSOD (cultprit being ntoskrnl.exe)

Have no idea which driver is causing them

Please help!

Here are my list of drivers and system info: Documents

 

BSOD - driver_irql_not_less_or_equal (l1c63x64.sys)

Hi Seung,

Sorry for the inconvenience caused by BSOD - driver_irql_not_less_or_equal (l1c63x64.sys).

Please let us know the make/model of your computer.

The L1C63x64.sys is the Atheros LAN driver and I would suggest to uninstall and reinstall the Atheros LAN driver but install the latest Atheros LAN driver by visiting the manufacture's website and avoid using any LAN driver available though Windows Update.

However the problem could also be with any VPN software and other software so make sure you have the latest version of each of these software.

If the errors continue uninstall the VPN software and check if the issue persist.

Hope this helps. Get back to us for further queries for BSOD - driver_irql_not_less_or_equal (l1c63x64.sys). We are happy to help!