Windows 10: BSOD "tdx.sys" error

Discus and support BSOD "tdx.sys" error in Windows 10 Customization to solve the problem; BSOD occurs when accessing a specific web page. MEMORY.DMP analysis results are as follows. Windows 10 Kernel Version 19041 MP 4 procsFree x64... Discussion in 'Windows 10 Customization' started by Windows Category - All, Mar 1, 2021.

  1. WINDOWS CATEGORY - ALL
    Windows Category - All Win User

    BSOD "tdx.sys" error


    BSOD occurs when accessing a specific web page.

    MEMORY.DMP analysis results are as follows.



    Windows 10 Kernel Version 19041 MP 4 procsFree x64

    Product: WinNt, suite: TerminalServerSingleUserTS

    Built by:19041.1.amd64fre.vb_release.191206-1406

    Machine Name:

    Kernel base = 0xfffff801`6c400000PsLoadedModuleList = 0xfffff801`6d02a2f0

    Debug session time: TueFeb 2 15:49:11.617 2021 UTC + 9:00

    System Uptime: 0 days 1:21:31.359


    For analysis of this file, run !analyze -v

    0: kd> !analyze -v

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

    * *

    * Bugcheck Analysis *

    * *

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


    DPC_WATCHDOG_VIOLATION133

    The DPC watchdog detected a prolonged runtime at an IRQL of DISPATCH_LEVEL

    or above.

    Arguments:

    Arg1: 0000000000000000, A single DPC or ISRexceeded its time allotment. The offending

    componentcan usually be identified with a stack trace.

    Arg2: 0000000000000501, The DPC time countin ticks.

    Arg3: 0000000000000500, The DPC timeallotment in ticks.

    Arg4: fffff8016d0fa320, cast tont!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains

    additionalinformation regarding this single DPC timeout


    Debugging Details:

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


    BUGCHECK_CODE: 133


    BUGCHECK_P1: 0


    BUGCHECK_P2: 501


    BUGCHECK_P3: 500


    BUGCHECK_P4: fffff8016d0fa320


    DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED


    PROCESS_NAME: Registry


    SYMBOL_NAME: tdx!TdxShutdownEndpointConnection+e1


    MODULE_NAME: tdx


    IMAGE_NAME: tdx.sys <<<================ It appears that a problem has occurred in the OS module.


    STACK_COMMAND: .thread ; .cxr ; kb


    BUCKET_ID_FUNC_OFFSET: e1


    FAILURE_BUCKET_ID: 0x133_DPC_tdx!TdxShutdownEndpointConnection


    OS_VERSION: 10.0.19041.1


    BUILDLAB_STR: vb_release


    OSPLATFORM_TYPE: x64


    OSNAME: Windows 10


    FAILURE_ID_HASH: {30f682b0-0895-94a4-871d-12af715555f4}


    Followup: MachineOwner

    ---------


    0: kd> !running -it


    System Processors: 000000000000000f

    Idle Processors: 000000000000000e


    Prcbs Current pri Next pri Idle

    0 fffff8016858c180 ffffbf81c7acd080 11 ffffbf81c7a7a040 13fffff8016d126600 ................


    #Child-SP RetAddr Call Site

    00 fffff801`716afc88 fffff801`6c83a988nt!KeBugCheckEx

    01 fffff801`716afc90 fffff801`6c67541dnt!KeAccumulateTicks+0x1c8788

    02 fffff801`716afcf0 fffff801`6c6759c1nt!KiUpdateRunTime+0x5d

    03 fffff801`716afd40 fffff801`6c66f833nt!KiUpdateTime+0x4a1

    04 fffff801`716afe80 fffff801`6c6781f2nt!KeClockInterruptNotify+0x2e3

    05 fffff801`716aff30 fffff801`6c727ef5nt!HalpTimerClockInterrupt+0xe2

    06 fffff801`716aff60 fffff801`6c7f722ant!KiCallInterruptServiceRoutine+0xa5

    07 fffff801`716affb0 fffff801`6c7f7797nt!KiInterruptSubDispatchNoLockNoEtw+0xfa

    08 fffff60c`0ed67c00 fffff801`6c6e47fcnt!KiInterruptDispatchNoLockNoEtw+0x37

    09 fffff60c`0ed67d90 fffff801`6c6e47c8nt!KxWaitForSpinLockAndAcquire+0x2c

    0a fffff60c`0ed67dc0 fffff801`709ee304nt!KeAcquireSpinLockRaiseToDpc+0x88

    0b fffff60c`0ed67df0 fffff801`709ee2a5tcpip!TcpCloseTcb+0x44

    0c fffff60c`0ed67f50 fffff801`6c7f905etcpip!TcpTlConnectionCloseEndpointCalloutRoutine+0x15

    0d fffff60c`0ed67f80 fffff801`6c7f901cnt!KxSwitchKernelStackCallout+0x2e

    0e fffff801`716a5cd0 fffff801`6c7547ednt!KiSwitchKernelStackContinue

    0f fffff801`716a5cf0 fffff801`6c7545e2nt!KiExpandKernelStackAndCalloutOnStackSegment+0x19d

    10 fffff801`716a5d90 fffff801`6c754443nt!KiExpandKernelStackAndCalloutSwitchStack+0xf2

    11 fffff801`716a5e00 fffff801`6c7543fdnt!KeExpandKernelStackAndCalloutInternal+0x33

    12 fffff801`716a5e70 fffff801`70a05b1ant!KeExpandKernelStackAndCalloutEx+0x1d

    13 fffff801`716a5eb0 fffff801`7b5db871tcpip!TcpTlConnectionCloseEndpoint+0x6a

    14 fffff801`716a5f20 fffff801`7b5d4d25tdx!TdxShutdownEndpointConnection+0xe1

    15 fffff801`716a5f70 fffff801`7b5d9649tdx!TdxDecrementTlEndpointReference+0x35

    16 fffff801`716a5fa0 fffff801`70a80cddtdx!TdxDisconnectConnectionTlRequestComplete+0x189

    17 fffff801`716a5ff0 fffff801`708e8ea4tcpip!InetInspectDisconnectComplete+0x1d

    18 fffff801`716a6020 fffff801`708b5e08NETIO!StreamRequestNetBufferListCompletionFn+0x1ceb4

    19 fffff801`716a6060 fffff801`70c9448cNETIO!NetioDereferenceNetBufferList+0x88

    1a fffff801`716a60b0 fffff801`70c955cbfwpkclnt!FwppDereferenceNetioNetBufferList+0x98

    1b fffff801`716a6100 fffff801`70c95816fwpkclnt!FwpsDereferenceNetBufferList0+0x2b

    1c fffff801`716a6130 fffff801`70c9561bfwpkclnt!FwpsFreeCloneNetBufferList0+0x1d6

    1d fffff801`716a6170 fffff801`7cd7bcf2fwpkclnt!FwpsDiscardClonedStreamData0+0x1b

    1e fffff801`716a61a0 fffff801`7cd7751aAMonCDW8!NirpMgrPendingNirpComplete+0x15a

    1f fffff801`716a61f0 fffff801`7cd81054AMonCDW8!IAnfdTDCompleteRequest+0x102

    20 fffff801`716a6240 fffff801`7cd73d91AMonCDW8!SessionMgrTeObjDestroy+0x3b0

    21 fffff801`716a62d0 fffff801`7cd7239aAMonCDW8!ClassifyEndpointClosure+0x2cd

    22 fffff801`716a6330 fffff801`708bca51AMonCDW8!DispatcherClassify+0xa92

    23 fffff801`716a63b0 fffff801`708b86cbNETIO!ProcessCallout+0x5d1

    24 fffff801`716a6530 fffff801`70a5e31f NETIO!KfdClassify+0x8bb

    25 fffff801`716a6920 fffff801`709efeb2tcpip!AleNotifyEndpointDeactivate+0x6d677

    26 fffff801`716a6ec0 fffff801`709a340etcpip!TcpShutdownTcb+0x1232

    27 fffff801`716a7340 fffff801`709a28d9 tcpip!TcpLeaveTcbDelivery+0x15e

    28 fffff801`716a7370 fffff801`709a1f25tcpip!TcpDeliverDataToClient+0x7c9

    29 fffff801`716a74f0 fffff801`709a64bbtcpip!TcpDeliverReceive+0xb5

    2a fffff801`716a75e0 fffff801`709a536ftcpip!TcpTcbFastDatagram+0xebb

    2b fffff801`716a77b0 fffff801`709a470ftcpip!TcpTcbReceive+0x18f

    2c fffff801`716a7a00 fffff801`709a3798tcpip!TcpMatchReceive+0x51f

    2d fffff801`716a7cb0 fffff801`709a1e5etcpip!TcpReceive+0x358

    2e fffff801`716a7da0 fffff801`709b40aatcpip!TcpNlClientReceivePreValidatedDatagrams+0x2e

    2f fffff801`716a7de0 fffff801`70a0ed1ftcpip!IpFlcReceivePreValidatedPackets+0x6ba

    30 fffff801`716a8070 fffff801`6c754488tcpip!FlReceiveNetBufferListChainCalloutRoutine+0x12f

    31 fffff801`716a81c0 fffff801`6c7543fdnt!KeExpandKernelStackAndCalloutInternal+0x78

    32 fffff801`716a8230 fffff801`70a01cddnt!KeExpandKernelStackAndCalloutEx+0x1d

    33 fffff801`716a8270 fffff801`70a013bdtcpip!NetioExpandKernelStackAndCallout+0x8d

    34 fffff801`716a82d0 fffff801`70741eb1tcpip!FlReceiveNetBufferListChain+0x46d

    35 fffff801`716a8580 fffff801`70741ccbndis!ndisMIndicateNetBufferListsToOpen+0x141

    36 fffff801`716a8660 fffff801`70747ef1ndis!ndisMTopReceiveNetBufferLists+0x22b

    37 fffff801`716a86e0 fffff801`7077dee3ndis!ndisCallReceiveHandler+0x61

    38 fffff801`716a8730 fffff801`70744a94ndis!ndisInvokeNextReceiveHandler+0x1df

    39 fffff801`716a8800 fffff801`7d626a28ndis!NdisMIndicateReceiveNetBufferLists+0x104

    3a fffff801`716a8890 fffff801`7d625cbdrt640x64+0x26a28

    3b fffff801`716a89f0 fffff801`7d60636crt640x64+0x25cbd

    3c fffff801`716a8a40 fffff801`7d602a23rt640x64+0x636c

    3d fffff801`716a8aa0 fffff801`70747887rt640x64+0x2a23

    3e fffff801`716a8ad0 fffff801`6c60781endis!ndisInterruptDpc+0x197

    3f fffff801`716a8bb0 fffff801`6c606b04nt!KiExecuteAllDpcs+0x30e

    40 fffff801`716a8d20 fffff801`6c7fc7c5nt!KiRetireDpcList+0x1f4

    41 fffff801`716a8fb0 fffff801`6c7fc5b0nt!KxRetireDpcList+0x5

    42 fffff60c`153af150 fffff801`6c7fbe65nt!KiDispatchInterruptContinue

    43 fffff60c`153af180 fffff801`6c7f72f1nt!KiDpcInterruptBypass+0x25

    44 fffff60c`153af190 fffff801`6c650078nt!KiInterruptDispatch+0xb1

    45 fffff60c`153af320 fffff801`6cdb1094nt!ExAllocateHeapPool+0x168

    46 fffff60c`153af460 fffff801`6c65c5c9nt!ExAllocatePoolWithTag+0x64

    47 fffff60c`153af4b0 fffff801`6ca1dcb1nt!CmpAllocatePoolWithTag+0x9

    48 fffff60c`153af4e0 fffff801`6ca1db3ent!CmpConstructNameFromKeyNodes+0xb1

    49 fffff60c`153af560 fffff801`6ca1da3cnt!CmpConstructNameWithStatus+0xee

    4a fffff60c`153af5c0 fffff801`6c65bfffnt!CmpConstructName+0x14

    4b fffff60c`153af5f0 fffff801`6ca1acd3nt!CmpDoQueryKeyName+0x1af

    4c fffff60c`153af730 fffff801`6c9d9a03nt!CmpQueryKeyName+0x13

    4d fffff60c`153af780 fffff801`6c9d941ent!ObQueryNameStringMode+0xd3

    4e fffff60c`153af8a0 fffff801`6890371fnt!ObQueryNameString+0xe

    4f fffff60c`153af8e0 fffff801`68902bd2TKRgFtXp64+0x371f

    50 fffff60c`153af950 fffff801`689029d9TKRgFtXp64+0x2bd2

    51 fffff60c`153af9c0 fffff801`6ca26808TKRgFtXp64+0x29d9

    52 fffff60c`153afa00 fffff801`6ca225acnt!CmpCallCallBacksEx+0x1c8

    53 fffff60c`153afb10 fffff801`6ca22767nt!CmpCallCallBacks+0x28

    54 fffff60c`153afb60 fffff801`6c9faef0nt!CmpDeleteKeyObject+0xa7

    55 fffff60c`153afbf0 fffff801`6c661277nt!ObpRemoveObjectRoutine+0x80

    56 fffff60c`153afc50 fffff801`6ca2887ent!ObfDereferenceObjectWithTag+0xc7

    57 fffff60c`153afc90 fffff801`6ca2c4fcnt!ObCloseHandleTableEntry+0x29e

    58 fffff60c`153afdd0 fffff801`6c8071b5nt!NtClose+0xec

    59 fffff60c`153afe40 00000000`77ad1cfcnt!KiSystemServiceCopyEnd+0x25

    5a 00000000`0629d938 00000000`000000000x77ad1cfc


    1 ffffe40022e4e180 ffffe40022e59140 0 ffffe40022e59140 ................


    #Child-SP RetAddr Call Site

    00 fffff60c`0ea2f5b8 fffff801`7d941424intelppm!MWaitIdle+0x1f

    01 fffff60c`0ea2f5c0 fffff801`6c671396intelppm!AcpiCStateIdleExecute+0x24

    02 fffff60c`0ea2f5f0 fffff801`6c670154nt!PpmIdleExecuteTransition+0x10c6

    03 fffff60c`0ea2f9f0 fffff801`6c7f92a4nt!PoIdle+0x374

    04 fffff60c`0ea2fb60 00000000`00000000nt!KiIdleLoop+0x54


    2 ffffe40023040180 ffffe4002304b140 0 ffffe4002304b140 ................


    #Child-SP RetAddr Call Site

    00 fffff60c`0ea3f5b8 fffff801`7d941424 intelppm!MWaitIdle+0x1f

    01 fffff60c`0ea3f5c0 fffff801`6c671396intelppm!AcpiCStateIdleExecute+0x24

    02 fffff60c`0ea3f5f0 fffff801`6c670154nt!PpmIdleExecuteTransition+0x10c6

    03 fffff60c`0ea3f9f0 fffff801`6c7f92a4nt!PoIdle+0x374

    04 fffff60c`0ea3fb60 00000000`00000000nt!KiIdleLoop+0x54


    3 ffffe40023100180 ffffe4002310b140 0 ffffe4002310b140 ................


    #Child-SP RetAddr Call Site

    00 fffff60c`0ea4f5b8 fffff801`7d941424intelppm!MWaitIdle+0x1f

    01 fffff60c`0ea4f5c0 fffff801`6c671396intelppm!AcpiCStateIdleExecute+0x24

    02 fffff60c`0ea4f5f0 fffff801`6c670154nt!PpmIdleExecuteTransition+0x10c6

    03 fffff60c`0ea4f9f0 fffff801`6c7f92a4nt!PoIdle+0x374

    04 fffff60c`0ea4fb60 00000000`00000000nt!KiIdleLoop+0x54


    0: kd> lmvm tdx

    Browse full module list

    start end module name

    fffff801`7b5d0000 fffff801`7b5f2000 tdx

    Loaded symbol image file: tdx.sys

    Image path: \SystemRoot\system32\DRIVERS\tdx.sys

    Image name: tdx.sys

    Browse all global symbols functions data

    Image was built with /Brepro flag.

    Timestamp: 28EC0E80 Thisis a reproducible build file hash, not a timestamp

    CheckSum: 000273F3

    ImageSize: 00022000

    Translations: 0000.04b00000.04e4 0409.04b0 0409.04e4

    Information from resource tables:

    :)
     
    Windows Category - All, Mar 1, 2021
    #1
  2. AXE0
    axe0 Win User

    BSOD while using the internet. error (L1C63x64.sys)


    Hi trainman81,

    Welcome to the 10forums.

    Daemon tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known cause for BSOD's.
    Please remove Daemon Tools and run the SPTD pass through remover.
    1. Uninstall Daemon Tools
    2. Download the SPTD standalone installer and follow these steps:
      • Double click the executable to open it
      • Click on the button shown below

    BSOD "tdx.sys" error [​IMG]


    If the button is grayed out, like in the image, there is no more SPTD installation on your system, and you can close the window


    AVG is trying to request data from the internet, which is why the network driver is marked as the cause.
    Code:
    Code:
    *** WARNING: Unable to verify timestamp for L1C63x64.sys *** ERROR: Module load completed but symbols could not be loaded for L1C63x64.sys 0: kd> lmvm L1C63x64 start             end                 module name fffff801`89700000 fffff801`89722000   L1C63x64 T (no symbols)                Loaded symbol image file: L1C63x64.sys     Image path: \SystemRoot\System32\drivers\L1C63x64.sys     Image name: L1C63x64.sys     Timestamp:        Mon Apr 01 05:15:17 2013 (5158FBC5)     CheckSum:         000245C4     ImageSize:        00022000     Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    AVG drivers that have been flagged
    Code:
    Code:
    *** WARNING: Unable to verify timestamp for avgwfpa.sys *** ERROR: Module load completed but symbols could not be loaded for avgwfpa.sys *** WARNING: Unable to verify timestamp for avgfwd6a.sys *** ERROR: Module load completed but symbols could not be loaded for avgfwd6a.sys
    Please uninstall AVG and see if it helps
    Uninstall AVG | AVG
    It is further recommended to check your Qualcomm network driver for updates, its driver is not supported for Windows 10.
    Driver Reference Table - L1C63x64.sys
     
    axe0, Mar 1, 2021
    #2
  3. CPLPRO
    cplpro Win User
    7 different BSoD

    Hey guys,

    I have a serious problem. I make it as short as possible:

    • system runs 100 % fine with the 10.12
    • updatet to Catalyst 11.1 -> BSoD
    • updatet to 11.1 Hotfix -> BSoD
    • rollback to 10.12 -> BSoD
    • removed ALL AMD files manually, installed 10.12 -> BSoD
    • Temps are fine
    • no sfc /scannow errors
    • no chkdsk errors
    • Prime, Furmark all fine
    • regardless what driver I install -> BSoD
    • I did no hw changes, no OC
    Here are my BSoDs I receive:
    • 0x0000010e
    • 0x1000007e
    • 0x0000007e
    • 0x0000004e
    • 0x0000003b
    • dxgmms1.sys
    • PFN_LIST_CORRUPT
    They all refer to the GPU of course ...

    From now on I receive a BSoD every time I try to play a game (especially BC2 and SC II) even if I completely remove the old driver and make a clean install.
    Apparently the 11.1 damaged my system irreparable.

    Any advice or info would be very much appreciated *Smile BSOD "tdx.sys" error :)
     
    cplpro, Mar 1, 2021
    #3
  4. KURSAH
    Kursah Win User

    BSOD "tdx.sys" error

    BSOD - Registry Error

    Your BSOD code is 0X000000051

    Here's the Google search I did for it: https://www.google.com/search?q=0x0...j5.399j0j7&sourceid=chrome&es_sm=122&ie=UTF-8

    There is a hotfix available that might help, https://support.microsoft.com/en-us/kb/810558

    This thread makes a few good suggestions too: http://www.sevenforums.com/bsod-hel...dows-7-pro-sp1-registry-error-0x00000051.html

    +1 to listing your full system specs, OS version, etc. I did only look at your BSOD log file.

    Run a Diskchk /R (I know you already ran one, so you can skip this)

    Run SFC /SCANNOW

    Report back.
     
    Kursah, Mar 1, 2021
    #4
Thema:

BSOD "tdx.sys" error

Loading...

  1. BSOD "tdx.sys" error - Similar Threads - BSOD tdx sys

  2. BSOD - qcwlan64.sys error

    in Windows 10 Gaming
    BSOD - qcwlan64.sys error: Dear Community,After reinstalling and fully updating windows 11 on a lenovo thinkpad laptop I get repeated and very frequent bsod errors with no stop number but reference to file qcwlan64.sys. I checked qualcom drivers via Windows Decice Manager but windows indicates most...

  3. BSOD - qcwlan64.sys error

    in Windows 10 Software and Apps
    BSOD - qcwlan64.sys error: Dear Community,After reinstalling and fully updating windows 11 on a lenovo thinkpad laptop I get repeated and very frequent bsod errors with no stop number but reference to file qcwlan64.sys. I checked qualcom drivers via Windows Decice Manager but windows indicates most...

  4. rtwlane02.sys BSOD error

    in Windows 10 Drivers and Hardware
    rtwlane02.sys BSOD error: Hi. I was playing a game on my computer. However after a while my computer crashed. It was a bsod rtwlane02.sys failed. It also had PAGE_FAULT_IN_NONPAGED_AREA error message too. I cant access my desktop to try and update my drivers. I have access to the cmd though. My...

  5. Fix dxgmms2.sys BSOD error on Windows computer

    in Windows 10 News
    Fix dxgmms2.sys BSOD error on Windows computer: [ATTACH] [ATTACH]The dxgmms2.sys file is a Windows system driver file that is associated with the Graphics Rendering capabilities of a computer. This file is known to cause a Blue Screen error. But the main reasons include conflicts like RAM or Hard [...] This post Fix...

  6. BSODs Due to Qcamain10x65.sys Error

    in Windows 10 BSOD Crashes and Debugging
    BSODs Due to Qcamain10x65.sys Error: Hi, A week ago I posted a question regarding a similar problem. For a while, I was getting the driver_irql_not_less_or_equal error. After looking at the minidump files, I was told to update my Qualcomm Atheros Network card device driver. I tried this solution, but I started...

  7. BSOD playing Overwatch, error L1C63x64.sys

    in Windows 10 BSOD Crashes and Debugging
    BSOD playing Overwatch, error L1C63x64.sys: Hi all, I have been experiencing this BSOD: Driver IRQL Not Less or Equal, L1C63x64.sys for a few months now. When it happens, it is only when I am in the middle of gaming (Overwatch). After some research, I see that there are many of the same problems with my ethernet...

  8. BSOD While Streaming, L1C63x64.sys Error

    in Windows 10 BSOD Crashes and Debugging
    BSOD While Streaming, L1C63x64.sys Error: Lately whenever I stream I end up getting a Blue Screen am an hour or so in. I've narrowed it down to my qualcomm atheros ar8151 pci-e gigabit ethernet controller (ndis 6.30) Network Driver. I've updated it when Windows said I had the current drivers (of course) to ver....

  9. BSOD error igdkmd64.sys (5109aeb3)

    in Windows 10 BSOD Crashes and Debugging
    BSOD error igdkmd64.sys (5109aeb3): Hello, please help me to solve this problem. DM Log Collector below 74093

  10. BSOD while using the internet. error (L1C63x64.sys)

    in Windows 10 BSOD Crashes and Debugging
    BSOD while using the internet. error (L1C63x64.sys): Hello When using my vpn I get the BSOD. Driver_IRQL_NOT_LESS_OR_EQUAL(L1C63x64.sys) My cpu says it is the Qualcomm Atheros Network driver, I made sure it was updated still happens. I would appreciate if someone can look at the log posted below I am lost at the moment...