Yukon Miniport driver incompatibility
-
2009年1月14日 下午 04:40
Apparently I have a driver problem with my Marvell Yukon Miniport. I was getting bluescreens. I disabled the adapter and it seems fine now. I have looked for new drivers but I am running the most current.
Unable to load image \SystemRoot\system32\DRIVERS\tdx.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for tdx.sys
*** ERROR: Module load completed but symbols could not be loaded for tdx.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************Use !analyze -v to get detailed debugging information.
BugCheck D1, {60, 2, 0, 89f0fb93}
*** WARNING: Unable to verify timestamp for tcpip.sys
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
*** WARNING: Unable to verify timestamp for ndis.sys
*** ERROR: Module load completed but symbols could not be loaded for ndis.sys
*** WARNING: Unable to verify timestamp for yk60x86.sys
*** ERROR: Module load completed but symbols could not be loaded for yk60x86.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
Operating System System Model Windows 7 Ultimate (build 7000) 32bit No details available Processor a Main Circuit Board b 3.40 gigahertz Intel Pentium 4
16 kilobyte primary memory cache
2048 kilobyte secondary memory cacheBoard: ASUSTeK Computer INC. P5WD2-Premium Rev 1.xx
Bus Clock: 200 megahertz
BIOS: American Megatrends Inc. 0709 03/31/2006Drives Memory Modules c,d 1050.23 Gigabytes Usable Hard Drive Capacity
825.97 Gigabytes Hard Drive Free Space
LITE-ON DVDRW SHW-160P6S ATA Device [CD-ROM drive]
3.5" format removeable media [Floppy drive]
LEXAR JD LIGHTNING II USB Device [Hard drive] (4.01 GB) -- drive 3
Volume0 [Hard drive] (750.16 GB) -- drive 0
WDC WD15 00ADFD-00NLR5 SCSI Disk Device (150.04 GB) -- drive 2
WDC WD15 00ADFD-00NLR5 SCSI Disk Device (150.04 GB) -- drive 12048 Megabytes Installed Memory
Slot 'DIMM0' has 512 MB
Slot 'DIMM1' has 512 MB
Slot 'DIMM2' has 512 MB
Slot 'DIMM3' has 512 MBLocal Drive Volumes c: (NTFS on drive 1) 150.04 GB 122.81 GB free d: (NTFS on drive 0) 750.16 GB 595.51 GB free f: (NTFS on drive 2) 150.03 GB 107.65 GB free Network Drives None detected Users Printers local user accounts last logon Rich 1/14/2009 8:51:21 AM (admin) local system accounts Administrator 1/12/2009 4:58:49 PM (admin) Guest never
Marks a disabled account; Marks a locked account Microsoft Shared Fax Driver on SHRFAX: Microsoft XPS Document Writer on XPSPort: Controllers Display Standard floppy disk controller
ATA Channel 0 [Controller]
ATA Channel 1 [Controller]
Intel(R) 82801G (ICH7 Family) Ultra ATA Storage Controllers - 27DFNVIDIA GeForce 6600 [Display adapter]
LGE W2252 [Monitor] (23.0"vis, January 2008)
PNR PX171M [Monitor] (17.3"vis, s/n 417A0121K0038, April 2004)Bus Adapters Multimedia Intel(R) ICH7R/DH SATA RAID Controller
ITE IT8211 ATA/ATAPI Controller
Silicon Image SiI 3132 SATALink Controller
Intel(R) 82801G (ICH7 Family) USB Universal Host Controller - 27C8
Intel(R) 82801G (ICH7 Family) USB Universal Host Controller - 27C9
Intel(R) 82801G (ICH7 Family) USB Universal Host Controller - 27CA
Intel(R) 82801G (ICH7 Family) USB Universal Host Controller - 27CB
Intel(R) 82801G (ICH7 Family) USB2 Enhanced Host Controller - 27CCLogitech Mic (Orbit/Sphere)
Realtek High Definition AudioCommunications Other Devices Intel(R) PRO/1000 PM Network Connection primary Auto IP Address: 192.168.0.190 / 24 Gateway: 192.168.0.1 Dhcp Server: 192.168.0.1 Physical Address: Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller Microsoft ISATAP Adapter Microsoft ISATAP Adapter Microsoft ISATAP Adapter #2 Teredo Tunneling Pseudo-Interface Networking Dns Server: 192.168.0.1 Texas Instruments 1394 OHCI Compliant Host Controller
HID UPS Battery
Microsoft Composite Battery
Microsoft USB Trackball Explorer
USB Human Interface Device
Logitech QuickCam Orbit/Sphere
Standard PS/2 Keyboard
Microsoft USB Trackball Explorer [Mouse]
Generic USB Hub
Logitech USB Camera (Orbit/Sphere)
USB Mass Storage Device
USB Root Hub (5x)
Generic volume shadow copy
Rich Toyser- 已編輯 Rich Toyser 2009年1月15日 下午 06:38
- 已變更類型 Mark L. FergusonModerator 2009年2月18日 下午 03:33
所有回覆
-
2009年1月15日 下午 06:22OK I thought I fixed it by disabling the Marvel Miniport. Apparently not.
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-22125-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are availableSymbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
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 = 0x82c56000 PsLoadedModuleList = 0x82da34d0
Debug session time: Thu Jan 15 11:12:38.518 2009 (GMT-7)
System Uptime: 0 days 1:59:28.002
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
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
*** ERROR: Module load completed but symbols could not be loaded for tdx.sys
Unable to load image tcpip.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for tcpip.sys
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************Use !analyze -v to get detailed debugging information.
BugCheck 100000D1, {60, 2, 0, 89bedb93}
*** WARNING: Unable to verify timestamp for ndis.sys
*** ERROR: Module load completed but symbols could not be loaded for ndis.sys
*** WARNING: Unable to verify timestamp for e1e6032.sys
*** ERROR: Module load completed but symbols could not be loaded 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 ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Probably caused by : tdx.sys ( tdx+7b93 )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 ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************MODULE_NAME: tdx
FAULTING_MODULE: 82c56000 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+7b93
89bedb93 ff7060 push dword ptr [eax+60h]CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WRONG_SYMBOLS
BUGCHECK_STR: 0xD1
LAST_CONTROL_TRANSFER: from 89c7d58e to 89bedb93
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
8069c7c4 89c7d58e 852b3008 8069c830 8069c924 tdx+0x7b93
8069c854 89c7c42b 87027094 0000ecc4 8069c924 tcpip+0x7358e
8069c8e8 89c7c87e 85a88008 85a88100 8069c924 tcpip+0x7242b
8069c93c 89c7a06d 85a88008 85a88100 8729cef8 tcpip+0x7287e
8069c96c 89c79c3b d69a0fb8 8069c990 8069c9c0 tcpip+0x7006d
8069c9c8 89c7a33f 86a2ef40 85a88008 0069ca3c tcpip+0x6fc3b
8069ca30 89c7aabc 86a037b0 86a2c00c 00000000 tcpip+0x7033f
8069ca80 89c7aea6 86a2ef40 86a2c00c 0000bd01 tcpip+0x70abc
8069ca94 89c75b66 8069cab0 00000001 00000001 tcpip+0x70ea6
8069cab8 89c74fb0 8069cac4 00000000 00000001 tcpip+0x6bb66
8069cb54 89cf3028 86ffa320 00000000 a5237390 tcpip+0x6afb0
8069cb7c 82cc9f28 00000000 b89ed6c1 86a20c48 tcpip+0xe9028
8069cbe4 89c928fe 89cf2f2d 8069cc0c 00000000 nt+0x73f28
8069cc20 89ac2170 87022a02 8729ce00 00000000 tcpip+0x888fe
8069cc58 89ab07f6 87024008 8729cef8 00000000 ndis+0x67170
8069cc80 89ab076d 00000000 00000001 86cf20e0 ndis+0x557f6
8069cdfc 89a5c585 86cf20e0 00000000 00000000 ndis+0x5576d
8069ce18 89ab09a2 86cf20e0 8729cef8 00000000 ndis+0x1585
8069ce3c 89a5c5e0 86cf20e0 8729cef8 00000000 ndis+0x559a2
8069ce64 903caff2 86cf20e0 8729cef8 00000000 ndis+0x15e0
8069ceac 903c580d 01fa6000 00000000 00000000 e1e6032+0x6ff2
8069cee0 903c5aaf 00fa6000 86cf20e0 8069cf08 e1e6032+0x180d
8069cef0 903c5b4a 86fa6000 00000000 8069cf38 e1e6032+0x1aaf
8069cf08 89ab0220 86fa6000 00000000 00000000 e1e6032+0x1b4a
8069cf48 89a5c4a4 86fa7b6c 00fa7a58 00000000 ndis+0x55220
8069cf70 82cbd870 86fa7b6c 86fa7a58 00000000 ndis+0x14a4
8069cff4 82ca049c a229dce0 00000000 00000000 nt+0x67870
8069cff8 a229dce0 00000000 00000000 00000000 nt+0x4a49c
82ca049c 00000000 00000000 00000000 00000000 0xa229dce0
STACK_COMMAND: kbFOLLOWUP_IP:
tdx+7b93
89bedb93 ff7060 push dword ptr [eax+60h]SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: tdx+7b93
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: tdx.sys
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
Rich Toyser -
2009年1月15日 下午 06:24not sure if this will be of any use to you as i believe its aimed at vista, but it might give some clues
Bug Check Codes
-
2009年1月15日 下午 06:26I'm running Windows 7? Not Vista? This is a Windows 7 forum?
Rich Toyser -
2009年1月15日 下午 06:28ahh I see. I used Belarc to grab all the facts. Belarc Advisor called is Vista. Windows Vista Ultimate (build 7000) 32bit. Build 7000 of Vista. Kind of funny if you think about it. No I am running 7
Rich Toyser -
2009年1月15日 下午 06:31I got more than a little confused there, Then even more confused when i noticed Belarc labelling it Vista Ultimate (7000) i havent yet found a list of codes for Win 7 i think that would make everyones life a lot easier, but my reckoning was that even though those bug check codes were for vista, if the codes reported , linked to specific hardware that you might have in your machine it might give us a point of reference as to why your having these problems.
-
2009年1月15日 下午 06:37Well what I am reading in these dump files are indicating that I have a network adapter driver failure.
Most appear to be in "tdx.sys" which is a networking driver. However I have disabled the Marvel network adapter. I am still using the Intel(R) PRO/1000 PM Network Connection.
Rich Toyser -
2009年1月15日 下午 06:42im trawling these forums just now because im almost positive ive seen mention of tdx.sys before somewhere, i havent found that yet, but i have found this.
http://social.technet.microsoft.com/Forums/en/w7itprohardware/thread/3fa12a26-88ae-4d2b-8195-874afe4c5292
-
2009年1月15日 下午 06:43another one
http://social.technet.microsoft.com/Forums/en/w7itprohardware/thread/63201d4a-02cb-433a-9a5f-a8c0af4e58c2
-
2009年1月15日 下午 06:45well not sure how it is going to help. I have the Marvel miniport adapter disabled. I changed the flow control to manual anyways just to try.
Rich Toyser -
2009年1月15日 下午 06:47is it possible the problem is in the intel network driver? if the Marvell is disabled, then there shouldnt be anything calling its drivers.
-
2009年1月15日 下午 06:47I didnt think that I may have a problem with the remaining adapter since I was thinking driver. Maybe I should change the flow contorl on the remaining Intel pro/1000 adapter to 1.0 Gbps Full Duplex
?
Rich Toyser -
2009年1月15日 下午 06:48lol....trying it. Will let you know. It may not be a persay direct driver problem but a auto negotiation problem. Maybe...
Rich Toyser -
2009年1月15日 下午 06:48Thats the point of a beta test open it up to a far greater range of hardware and make note of what problems arise. Yes its certainly worth trying it
-
2009年1月15日 下午 06:50Sorry im being a little slow, i had missed you saying the Marvell was disabled. been on these boards for about 17 hours again chasing problems... ;)
-
2009年1月16日 上午 02:04
5 more blue screens since last post
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: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
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
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
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
*** ERROR: Module load completed but symbols could not be loaded for tdx.sys
Unable to load image tcpip.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for tcpip.sys
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************Use !analyze -v to get detailed debugging information.
BugCheck 100000D1, {60, 2, 0, 89bedb93}
*** WARNING: Unable to verify timestamp for ndis.sys
*** ERROR: Module load completed but symbols could not be loaded for ndis.sys
*** WARNING: Unable to verify timestamp for e1e6032.sys
*** ERROR: Module load completed but symbols could not be loaded 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 ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Probably caused by : tdx.sys ( tdx+7b93 )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 ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************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+7b93
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:
WARNING: Stack unwind information not available. Following frames may be wrong.
8069c7c4 89c7658e a7cf6008 8069c830 8069c924 tdx+0x7b93
8069c854 89c7542b 86a3807c 000092c0 8069c924 tcpip+0x7358e
8069c8e8 89c7587e 884f0e00 884f0ef8 8069c924 tcpip+0x7242b
8069c93c 89c7306d 884f0e00 884f0ef8 8722fe98 tcpip+0x7287e
8069c96c 89c72c3b 4bb2e0c5 8069c990 8069c9c0 tcpip+0x7006d
8069c9c8 89c7333f 86a2eb50 884f0e00 0069ca3c tcpip+0x6fc3b
8069ca30 89c73abc 86a03990 86a2c00c 00000000 tcpip+0x7033f
8069ca80 89c73ea6 86a2eb50 86a2c00c 0000bd01 tcpip+0x70abc
8069ca94 89c6eb66 8069cab0 00000001 00000001 tcpip+0x70ea6
8069cab8 89c6dfb0 8069cac4 00000000 00000001 tcpip+0x6bb66
8069cb54 89cec028 87282648 00000000 88790030 tcpip+0x6afb0
8069cb7c 82c88f28 00000000 b968f99b 86a20e58 tcpip+0xe9028
8069cbe4 89c8b8fe 89cebf2d 8069cc0c 00000000 nt+0x73f28
8069cc20 89ac2170 87280802 8722fe00 00000000 tcpip+0x888fe
8069cc58 89ab07f6 87282008 8722fe98 00000000 ndis+0x67170
8069cc80 89ab076d 00000000 00000001 86db70e0 ndis+0x557f6
8069cdfc 89a5c585 86db70e0 00000000 00000000 ndis+0x5576d
8069ce18 89ab09a2 86db70e0 8722fe98 00000000 ndis+0x1585
8069ce3c 89a5c5e0 86db70e0 8722fe98 00000000 ndis+0x559a2
8069ce64 8fe2bff2 86db70e0 8722fe98 00000000 ndis+0x15e0
8069ceac 8fe2680d 01f48000 00000000 00000000 e1e6032+0x6ff2
8069cee0 8fe26aaf 00f48000 86db70e0 8069cf08 e1e6032+0x180d
8069cef0 8fe26b4a 86f48000 00000000 8069cf38 e1e6032+0x1aaf
8069cf08 89ab0220 86f48000 00000000 00000000 e1e6032+0x1b4a
8069cf48 89a5c4a4 86f826e4 00f825d0 00000000 ndis+0x55220
8069cf70 82c7c870 86f826e4 86f825d0 00000000 ndis+0x14a4
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+7b93
89bedb93 ff7060 push dword ptr [eax+60h]SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: tdx+7b93
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: tdx.sys
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
Rich Toyser -
2009年1月16日 上午 05:48four more blue screens since last post
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 -
2009年1月29日 上午 03:07版主Hello,
The common thing i am seeing in all yoru BSOD Minidump reads is that your Symbols are not correct. So the information that you have posted might not be correct as well. If you wish to upload the minidumps then we might be able to help.
As for the Marvel Yukon there is a thread in the forums on this matter here. Check that out and see if it is of use for you as well.
Also you could check out the Sticky Thread for other tips on things to try. There maybe something in there that you have not done yet.
Regards,
~Alex T.~
~Windows Desktop Experience MVP~
.png)
