积极答复者
求助 windows server 2008 tdtcp.sys 蓝屏

问题
-
服务器是CITRIX服务器
以下是dump分析报告
..................................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************Use !analyze -v to get detailed debugging information.
BugCheck 7E, {c0000005, a399e716, b32dc1ac, b32dbea8}
Page 47bd2b not present in the dump file. Type ".hh dbgerr004" for details
Page 275de4 not present in the dump file. Type ".hh dbgerr004" for details
*** ERROR: Module load completed but symbols could not be loaded for pdrframe.sys
*** ERROR: Module load completed but symbols could not be loaded for pdcrypt1.sys
*** ERROR: Module load completed but symbols could not be loaded for wdica.sys
Page 47ba24 not present in the dump file. Type ".hh dbgerr004" for details
Page 2775ac not present in the dump file. Type ".hh dbgerr004" for details
*** ERROR: Module load completed but symbols could not be loaded for vdtw30.dll
Page 40d68b not present in the dump file. Type ".hh dbgerr004" for details
Page 40d68b not present in the dump file. Type ".hh dbgerr004" for details
Page 40d68b not present in the dump file. Type ".hh dbgerr004" for details
Page 40d68b not present in the dump file. Type ".hh dbgerr004" for details
Page 40d68b not present in the dump file. Type ".hh dbgerr004" for details
Page 40d68b not present in the dump file. Type ".hh dbgerr004" for details
Page 40d68b not present in the dump file. Type ".hh dbgerr004" for details
Page 40d68b not present in the dump file. Type ".hh dbgerr004" for details
Page 40d68b not present in the dump file. Type ".hh dbgerr004" for details
Page 40d68b not present in the dump file. Type ".hh dbgerr004" for details
Page 40d68b not present in the dump file. Type ".hh dbgerr004" for details
Page 40d68b not present in the dump file. Type ".hh dbgerr004" for details
Page 40d68b not present in the dump file. Type ".hh dbgerr004" for details
Page 40d68b not present in the dump file. Type ".hh dbgerr004" for details
Page 40d68b not present in the dump file. Type ".hh dbgerr004" for details
Page 40d68b not present in the dump file. Type ".hh dbgerr004" for details
Page 40d68b not present in the dump file. Type ".hh dbgerr004" for details
Page 40d68b not present in the dump file. Type ".hh dbgerr004" for detailsProbably caused by : tdtcp.sys ( tdtcp!DeviceInitializeWrite+92 )
Followup: MachineOwner
4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: a399e716, The address that the exception occurred at
Arg3: b32dc1ac, Exception Record Address
Arg4: b32dbea8, Context Record AddressDebugging Details:
------------------Page 47bd2b not present in the dump file. Type ".hh dbgerr004" for details
Page 275de4 not present in the dump file. Type ".hh dbgerr004" for details
Page 40d68b not present in the dump file. Type ".hh dbgerr004" for details
Page 40d68b not present in the dump file. Type ".hh dbgerr004" for details
Page 40d68b not present in the dump file. Type ".hh dbgerr004" for details
Page 40d68b not present in the dump file. Type ".hh dbgerr004" for details
Page 40d68b not present in the dump file. Type ".hh dbgerr004" for details
Page 40d68b not present in the dump file. Type ".hh dbgerr004" for details
Page 40d68b not present in the dump file. Type ".hh dbgerr004" for details
Page 40d68b not present in the dump file. Type ".hh dbgerr004" for details
Page 40d68b not present in the dump file. Type ".hh dbgerr004" for details
Page 40d68b not present in the dump file. Type ".hh dbgerr004" for details
Page 40d68b not present in the dump file. Type ".hh dbgerr004" for details
Page 40d68b not present in the dump file. Type ".hh dbgerr004" for details
Page 40d68b not present in the dump file. Type ".hh dbgerr004" for details
Page 40d68b not present in the dump file. Type ".hh dbgerr004" for details
Page 40d68b not present in the dump file. Type ".hh dbgerr004" for details
Page 40d68b not present in the dump file. Type ".hh dbgerr004" for details
Page 40d68b not present in the dump file. Type ".hh dbgerr004" for details
Page 40d68b not present in the dump file. Type ".hh dbgerr004" for detailsEXCEPTION_CODE: (NTSTATUS) 0xc0000005 - 0x%08lx
FAULTING_IP:
tdtcp!DeviceInitializeWrite+92
a399e716 8b4008 mov eax,dword ptr [eax+8]EXCEPTION_RECORD: b32dc1ac -- (.exr 0xffffffffb32dc1ac)
ExceptionAddress: a399e716 (tdtcp!DeviceInitializeWrite+0x00000092)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 00000008
Attempt to read from address 00000008CONTEXT: b32dbea8 -- (.cxr 0xffffffffb32dbea8)
eax=00000000 ebx=8f4b9ba4 ecx=00000019 edx=8f4b9cac esi=8f4b9b64 edi=8f4b9c80
eip=a399e716 esp=b32dc274 ebp=b32dc280 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
tdtcp!DeviceInitializeWrite+0x92:
a399e716 8b4008 mov eax,dword ptr [eax+8] ds:0023:00000008=????????
Resetting default scopePROCESS_NAME: csrss.exe
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - 0x%08lx
EXCEPTION_PARAMETER1: 00000000
EXCEPTION_PARAMETER2: 00000008
READ_ADDRESS: 00000008
FOLLOWUP_IP:
tdtcp!DeviceInitializeWrite+92
a399e716 8b4008 mov eax,dword ptr [eax+8]BUGCHECK_STR: 0x7E
DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
LAST_CONTROL_TRANSFER: from a399d40d to a399e716
STACK_TEXT:
b32dc280 a399d40d 00000000 8f4b9b64 8eecb938 tdtcp!DeviceInitializeWrite+0x92
b32dc2a0 97bed837 8f4b98f0 00000000 b32dc3f0 tdtcp!TdRawWrite+0x49
b32dc2bc 97bed918 8eecb928 00000002 b32dc3f0 termdd!_IcaCallSd+0x37
b32dc2d8 a89cd325 9e1ab68c 00000002 b32dc3f0 termdd!IcaCallNextDriver+0x4a
WARNING: Stack unwind information not available. Following frames may be wrong.
b32dc2f4 a89ce33d 8f3815f8 b32dc3f0 9e1ab678 pdrframe+0x1325
b32dc308 97bed837 8f3815f8 b32dc3f0 b32dc3f0 pdrframe+0x233d
b32dc324 97bed918 9e1ab678 00000002 b32dc3f0 termdd!_IcaCallSd+0x37
b32dc340 a89d663c 909552c4 00000002 b32dc3f0 termdd!IcaCallNextDriver+0x4a
b32dc360 a89d80fd 8f4bf758 b32dc3f0 909552b0 pdcrypt1+0x163c
b32dc374 97bed837 8f4bf758 b32dc3f0 b32dc3f0 pdcrypt1+0x30fd
b32dc390 97bed918 909552b0 00000002 b32dc3f0 termdd!_IcaCallSd+0x37
b32dc3ac a1b51ebd 8f69636c 00000002 b32dc3f0 termdd!IcaCallNextDriver+0x4a
b32dc3fc a1b4f462 ac4a0000 8f4b9b64 8f4b0000 wdica+0x2bebd
b32dc434 a1b5060b ac4a0000 00000000 00000001 wdica+0x29462
b32dc46c a1b4dcc9 ac4a0000 b32dc48c 00000001 wdica+0x2a60b
b32dc49c a1b316cb ac4a0000 00000009 00000002 wdica+0x27cc9
b32dc6e4 97bed837 ac4a0000 b32dc76c 8dc89678 wdica+0xb6cb
b32dc700 97bedced 8f696358 00000003 b32dc76c termdd!_IcaCallSd+0x37
b32dc720 97bee598 8dc89670 00000003 b32dc76c termdd!_IcaCallStack+0x57
b32dc748 97be9d18 9e0d1e98 00000003 b32dc76c termdd!IcaCallDriver+0x11e
b32dc7a4 97bebaf8 9e0d1e98 912363d0 91236440 termdd!IcaWriteChannel+0x126
b32dc7c0 97bec0e0 912363d0 91236440 a0e67d40 termdd!IcaWrite+0x40
b32dc7d8 8185a976 8b4be920 912363d0 912363d0 termdd!IcaDispatch+0xce
b32dc7f0 9de92201 00000008 fe08f028 00000008 nt!IofCallDriver+0x63
b32dc80c 9de9230e 00000004 a0e67d40 9dcb5560 win32k!_CtxDoFileIo+0xa3
b32dc830 9de59b99 a0e67d40 9dcb5560 00000008 win32k!CtxWriteFile+0x1e
b32dc854 9dc414c5 a0e67d40 9dcb5560 00000008 win32k!EngFileWrite+0x1b
b32dc878 9dc363d3 ffa761e8 00000001 00000002 vdtw30+0x414c5
b32dcd04 9dc370fa 9dcb51fc 00000000 9857d927 vdtw30+0x363d3
b32dcd7c 819ebf7a 00000000 d9c6ae14 00000000 vdtw30+0x370fa
b32dcdc0 81854efe 9dc36510 00000000 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
SYMBOL_STACK_INDEX: 0SYMBOL_NAME: tdtcp!DeviceInitializeWrite+92
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: tdtcp
IMAGE_NAME: tdtcp.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 47919224
STACK_COMMAND: .cxr 0xffffffffb32dbea8 ; kb
FAILURE_BUCKET_ID: 0x7E_tdtcp!DeviceInitializeWrite+92
BUCKET_ID: 0x7E_tdtcp!DeviceInitializeWrite+92
Followup: MachineOwner
---------
答案
-
你好,
关于Bug Check 0x7E,请参考下面的文章并检查是否能帮助你。(需要提醒的是,这是个英文文档。)
Bug Check 0x7E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
与此同时,能否让我确认下这个BSOD问题是突然出现?还是在这Windows Server 2008上做了某些改变 (比如:安装某些updates,更改某些settings)?
在现在的情况下,请允许sfc /scannow命令去扫描所有受保护的系统文件,安装所有必要的Windows Updates,并检查是否能帮助解决这BSOD问题。此外,可以执行Clean Boot,检查是否这BSOD问题仍然存在。
顺便说一句,在论坛上对dump file分析不是很有效率的。如果这个问题对你来说比较紧急,请通过电话联系 Microsoft 客户服务和支持 (CSS)以便专用的支持专业人员可以帮助您。
关于如何获得特定的技术支持的电话号码,请参阅下面列出的 web 站点:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607
希望这对你有帮助。
Best regards,
Justin Gu
- 已标记为答案 Justin GuModerator 2014年9月4日 15:51