Answered by:
tdx.sys Blue Screen?
Question
-
Microsoft (R) Windows Debugger Version 6.10.0003.233 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Richard Toyser\Desktop\011509-27046-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are availableSymbol search path is: D:\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x82c15000 PsLoadedModuleList = 0x82d624d0
Debug session time: Thu Jan 15 18:43:02.539 2009 (GMT-7)
System Uptime: 0 days 0:37:52.007
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
.......
Unable to load image tdx.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for tdx.sys
Unable to load image tcpip.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for tcpip.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************Use !analyze -v to get detailed debugging information.
BugCheck 100000D1, {60, 2, 0, 89bedb93}
Unable to load image ndis.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ndis.sys
Unable to load image e1e6032.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for e1e6032.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command 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: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command 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: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command 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: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command 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: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command 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: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command 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: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command 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: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command 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: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : tdx.sys ( tdx!TdxEventReceiveConnection+2d3 )Followup: MachineOwner
---------0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000060, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 89bedb93, address which referenced memoryDebugging Details:
------------------***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command 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: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command 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: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command 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: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command 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: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command 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: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command 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: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command 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: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command 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: nt!_KPRCB ***
*** ***
*************************************************************************MODULE_NAME: tdx
FAULTING_MODULE: 82c15000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4943153f
READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
00000060CURRENT_IRQL: 0
FAULTING_IP:
tdx!TdxEventReceiveConnection+2d3
89bedb93 ff7060 push dword ptr [eax+60h]CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WRONG_SYMBOLS
BUGCHECK_STR: 0xD1
LAST_CONTROL_TRANSFER: from 89c7658e to 89bedb93
STACK_TEXT:
8069c7c4 89c7658e a7cf6008 8069c830 8069c924 tdx!TdxEventReceiveConnection+0x2d3
8069c854 89c7542b 86a3807c 000092c0 8069c924 tcpip!TcpIndicateData+0x203
8069c8e8 89c7587e 884f0e00 884f0ef8 8069c924 tcpip!TcpDeliverDataToClient+0x2fa
8069c93c 89c7306d 884f0e00 884f0ef8 8722fe98 tcpip!TcpDeliverReceive+0x96
8069c96c 89c72c3b 4bb2e0c5 8069c990 8069c9c0 tcpip!TcpTcbFastDatagram+0x27a
8069c9c8 89c7333f 86a2eb50 884f0e00 0069ca3c tcpip!TcpTcbReceive+0x108
8069ca30 89c73abc 86a03990 86a2c00c 00000000 tcpip!TcpMatchReceive+0x1fe
8069ca80 89c73ea6 86a2eb50 86a2c00c 0000bd01 tcpip!TcpPreValidatedReceive+0x293
8069ca94 89c6eb66 8069cab0 00000001 00000001 tcpip!TcpNlClientReceivePreValidatedDatagrams+0x15
8069cab8 89c6dfb0 8069cac4 00000000 00000001 tcpip!IppDeliverPreValidatedListToProtocol+0x33
8069cb54 89cec028 87282648 00000000 88790030 tcpip!IpFlcReceivePreValidatedPackets+0x437
8069cb7c 82c88f28 00000000 b968f99b 86a20e58 tcpip!FlReceiveNetBufferListChainCalloutRoutine+0xfb
WARNING: Stack unwind information not available. Following frames may be wrong.
8069cbe4 89c8b8fe 89cebf2d 8069cc0c 00000000 nt+0x73f28
8069cc20 89ac2170 87280802 8722fe00 00000000 tcpip!FlReceiveNetBufferListChain+0x7c
8069cc58 89ab07f6 87282008 8722fe98 00000000 ndis!ndisMIndicateNetBufferListsToOpen+0x16b
8069cc80 89ab076d 00000000 00000001 86db70e0 ndis!ndisIndicateSortedNetBufferLists+0x4a
8069cdfc 89a5c585 86db70e0 00000000 00000000 ndis!ndisMDispatchReceiveNetBufferLists+0x129
8069ce18 89ab09a2 86db70e0 8722fe98 00000000 ndis!ndisMTopReceiveNetBufferLists+0x2d
8069ce3c 89a5c5e0 86db70e0 8722fe98 00000000 ndis!ndisMIndicateReceiveNetBufferListsInternal+0x3b
8069ce64 8fe2bff2 86db70e0 8722fe98 00000000 ndis!NdisMIndicateReceiveNetBufferLists+0x52
8069ceac 8fe2680d 01f48000 00000000 00000000 e1e6032!RxProcessReceiveArray+0x162
8069cee0 8fe26aaf 00f48000 86db70e0 8069cf08 e1e6032!E1000HandleInterrupt+0x13d
8069cef0 8fe26b4a 86f48000 00000000 8069cf38 e1e6032!E1000HandleInterruptEx+0xf
8069cf08 89ab0220 86f48000 00000000 00000000 e1e6032!E1000MessageInterruptDPC+0x1a
8069cf48 89a5c4a4 86f826e4 00f825d0 00000000 ndis!ndisMiniportDpc+0xda
8069cf70 82c7c870 86f826e4 86f825d0 00000000 ndis!ndisInterruptDpc+0xaf
8069cff4 82c5f49c 9c9fdce0 00000000 00000000 nt+0x67870
8069cff8 9c9fdce0 00000000 00000000 00000000 nt+0x4a49c
82c5f49c 00000000 00000000 00000000 00000000 0x9c9fdce0
STACK_COMMAND: kbFOLLOWUP_IP:
tdx!TdxEventReceiveConnection+2d3
89bedb93 ff7060 push dword ptr [eax+60h]SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: tdx!TdxEventReceiveConnection+2d3
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: tdx.sys
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
Rich Toyser
Answers
-
Try asking in this forumhttp://social.technet.microsoft.com/Forums/en-US/whatforum/threads/where you should post this question to.The present forum isn't the place as it is only for Bug reports *on the forum software*
- Marked as answer by Ed Price - MSFTMicrosoft employee Thursday, May 24, 2012 11:11 PM
