Windows Server 2008 BSOD tdx.sys

StangMan04 · 24 Dec 2012

I had this issue back in April, and I updated my Intel NIC drivers and I haven't had this issue since. Today, it happened again and I updated the drivers again with Windows Updates. When it rebooted to the desktop, it BSOD again a few minutes later. Not sure what is causing this. I looked at the minidump and couldn't find anything. But, was wondering if you guys could take a look incase I wasn't seeing enough information on the dumps.

I am using this machine to present iSCSI targets to another machine.

Arc · 24 Dec 2012

Hello StrongMan.

It is caused by Symantec/ Norton Network Dispatch Driver.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {6, 2, 0, fffffa6002fce545}

*** WARNING: Unable to verify timestamp for SYMTDIV.SYS
*** ERROR: Module load completed but symbols could not be loaded for SYMTDIV.SYS
Probably caused by : tdx.sys ( tdx!TdxSendDatagramTransportAddress+1d5 )

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

Description here: Driver Reference Table - SYMTDIV.SYS

I'd suggest you to uninstall Norton and all Symentec products using Norton Removal tool. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner. (I hope MSE can be used with your windows version.)

Download and install those, and then run full system scans with both of them, one by one.

Let us know the results.

StangMan04 · 24 Dec 2012

Issue with uninstalling it, is that our company uses Symantec End Point Protection for Anti-Virus. I will check and see what we can do. Glad you saw that, because my tool did not show that. So that is causing my issue all along? I have a similar machine that has the Symantec End Point Protection and that hasn't had this issue. Strange.

Arc · 24 Dec 2012

The dumps you uploaded, I checked the last three and got the same thing. That symentec driver is causing some problems with some other drivers, including the network driver, too.

And, it is not a must that a problem must to occur in all the computer in a similar manner.

If you cannot uninstall norton, you may contract norton community and they may assist you how to get rid of it by altering SEP.