Hello,

Some information for those who are suffering of this. It usually happened when transfering large amount of data from SAMBA. I use HP Mediavault

It's not only Norton 360 v3 Beta problem. I also had same issue with avast antivirus. So this is most likely Microsoft tdx.sys driver issue.

I can also upload minidump files.

Norton 360 v3 Beta. Version: 3.0.0.110

Windows 7 Beta 64 bit build 7000

Info from minibump file.

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: 00000000000000b8, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880008b2fc0, address which referenced memory

Debugging Details:
------------------

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ac70e0
 00000000000000b8
CURRENT_IRQL:  2

FAULTING_IP:
tdx!TdxEventReceiveConnection+300
fffff880`008b2fc0 4c8b82b8000000  mov     r8,qword ptr [rdx+0B8h]
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System 

Call stack of last minibump file:

nt!KeBugCheckEx
nt!KiBugCheckDispatch+0x69
nt!KiPageFault+0x25d
tdx!TdxEventReceiveConnection+0x300
tcpip!TcpIndicateData+0xfe
tcpip!TcpDeliverDataToClient+0x370
tcpip!TcpDeliverReceive+0xa5
tcpip!TcpInspectReceive+0xaf
tcpip! ?? ::FNODOBFM::`string'+0x438da
tcpip!TcpTcbReceive+0x275
tcpip!TcpMatchReceive+0x1e9
tcpip!TcpPreValidatedReceive+0x31c
tcpip!IppDeliverListToProtocol+0x4d
tcpip!IppProcessDeliverList+0x59
tcpip!IppReceiveHeaderBatch+0x231
tcpip!IpFlcReceivePackets+0x664

FOLLOWUP_IP:
tdx!TdxEventReceiveConnection+300
fffff880`008b2fc0 4c8b82b8000000  mov     r8,qword ptr [rdx+0B8h]

- Juha

I can confirm the same error

intermittent BSODs with TDX.sys as the issue

im running Window 7 Beta 32 Build 7000

Norton 360 v3.0 Beta

Latest Intel Gigabit ethernet and WiFi Link 5300AGN Drivers

My problems started happening after I mounted a network drive in windows (specifically our NAS LinkStation Network hard drive), I then began copying files back and forth and about 5 minutes later the computer Blue screens.  After that point it would blue screen aywhere from 1-15 minutes after start up.

I uninstalled Norton and have not had a BSOD since.

hope this helps

MORE INFO

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: 8fe66b93, address which referenced memory

Debugging Details:
------------------

READ_ADDRESS: GetPointerFromAddress: unable to read from 82bcc984
Unable to read MiSystemVaType memory at 82bab180
 00000060

CURRENT_IRQL:  2

FAULTING_IP:
tdx!TdxEventReceiveConnection+2d3
8fe66b93 ff7060          push    dword ptr [eax+60h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  aa4e0400 -- (.trap 0xffffffffaa4e0400)
ErrCode = 00000000
eax=00000000 ebx=c0000016 ecx=854807b8 edx=aa4e0402 esi=854807b0 edi=aa4e059c
eip=8fe66b93 esp=aa4e0474 ebp=aa4e0530 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
tdx!TdxEventReceiveConnection+0x2d3:
8fe66b93 ff7060          push    dword ptr [eax+60h]  ds:0023:00000060=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 8fe66b93 to 82aae9eb

STACK_TEXT: 
aa4e0400 8fe66b93 badb0d00 aa4e0402 aa4e0450 nt!KiTrap0E+0x2cf
aa4e0530 89e7458e 854807b0 aa4e059c aa4e0690 tdx!TdxEventReceiveConnection+0x2d3
aa4e05c0 89e7342b 879a70ac 000075c1 aa4e0690 tcpip!TcpIndicateData+0x203
aa4e0654 89e7387e 855acbd0 855accc8 aa4e0690 tcpip!TcpDeliverDataToClient+0x2fa
aa4e06a8 89ea87fa 855acbd0 855accc8 854e1268 tcpip!TcpDeliverReceive+0x96
aa4e06d8 89e71066 855acbd0 855accc8 854e1268 tcpip!TcpInspectReceive+0x77
aa4e0708 89e70c3b 5652a6ae aa4e072c aa4e075c tcpip!TcpTcbFastDatagram+0x273
aa4e0764 89e7133f 865048b0 855acbd0 004e07d8 tcpip!TcpTcbReceive+0x108
aa4e07cc 89e71abc 85b50fa0 86501000 00000000 tcpip!TcpMatchReceive+0x1fe
aa4e081c 89e57bc9 865048b0 86501000 0000bd01 tcpip!TcpPreValidatedReceive+0x293
aa4e0838 89e57def 865048b0 86501000 aa4e0874 tcpip!TcpReceive+0x2d
aa4e0848 89e8ecae aa4e085c c000023e 00000000 tcpip!TcpNlClientReceiveDatagrams+0x12
aa4e0874 89e8ee57 89ef8f58 aa4e08c8 c000023e tcpip!IppDeliverListToProtocol+0x49
aa4e0894 89e8f284 89ef8d68 00000006 aa4e08c8 tcpip!IppProcessDeliverList+0x2a
aa4e08ec 89e8e1a5 89ef8d68 00000006 00000000 tcpip!IppReceiveHeaderBatch+0x1f2
aa4e097c 89e6c0b2 87978db8 00000000 00000001 tcpip!IpFlcReceivePackets+0xb98
aa4e0a08 89eea028 87978db8 876f7bf8 aacea030 tcpip!IpFlcReceivePreValidatedPackets+0x539
aa4e0a30 82b0c587 00000000 8143a95d 8650f460 tcpip!FlReceiveNetBufferListChainCalloutRoutine+0xfb
aa4e0a98 89e898fe 89ee9f2d aa4e0ac0 00000000 nt!KeExpandKernelStackAndCalloutEx+0x132
aa4e0ad4 89c71170 879a3d02 876f7b00 00000000 tcpip!FlReceiveNetBufferListChain+0x7c
aa4e0b0c 89c5f7f6 879a37b8 876f7bf8 00000000 ndis!ndisMIndicateNetBufferListsToOpen+0x16b
aa4e0b34 89c5f76d 00000000 8693b0e0 8693b0e0 ndis!ndisIndicateSortedNetBufferLists+0x4a
aa4e0cb0 89c13846 8693b0e0 00000000 00000000 ndis!ndisMDispatchReceiveNetBufferLists+0x129
aa4e0ce4 89c13918 00000001 876f7bf8 8693bd6c ndis!ndisDoPeriodicReceivesIndication+0x125
aa4e0d0c 89c13456 860103e0 00000000 aacea030 ndis!ndisPeriodicReceivesWorker+0x5b
aa4e0d4c 82c53aad 00000000 8143ae55 00000000 ndis!ndisReceiveWorkerThread+0xeb
aa4e0d90 82a9c535 89c1336b 00000000 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19

STACK_COMMAND:  kb

FOLLOWUP_IP:
tdx!TdxEventReceiveConnection+2d3
8fe66b93 ff7060          push    dword ptr [eax+60h]

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  tdx!TdxEventReceiveConnection+2d3

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: tdx

IMAGE_NAME:  tdx.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4943153f

FAILURE_BUCKET_ID:  0xD1_tdx!TdxEventReceiveConnection+2d3

BUCKET_ID:  0xD1_tdx!TdxEventReceiveConnection+2d3

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

I will always get a BSOD error after several minutes when I'm using the network.  I have a mapped drive (Z:) to a Mac Mini.  Uninstalling Norton Beta fixed the problem.  I also have this problem with Avast so I uninstalled that and I have had no issues.  So for me the situation looks like follows:  If using network and an antivirus, I will get the TPX.SYS BSOD after an undetermined time period. 

Andy

Just jumping in on something that caught my eye in your message:

<< Uninstalling Norton Beta fixed the problem.  I also have this problem with Avast so I uninstalled that and I have had no issues.  >>

You did not have both installed at the same time did you? That's usually a recipe for trouble.

Well you are using a beta operating system and, I assume, the beta N360V3 .........

"Beta squared" plus 64 bit OS .......

I hope this is not your primary machine <g>

Your lucky to be able to download anything with WIN 7 64 bit --- I can install it but it "can't find a wireless network adapter" which is the good news since I don't have one in the desktop and nothing that I've tried and that worked under WIN 7 32 bit works under 64 ...... It can't find and install a driver for my network adapter which is on the mobo.

I am getting BSOD from TDX.SYS on WINDOWS 7 x64 build 7000 with Norton 360 v3 Beta Version 3.0.0.114.

This error stops when Norton 360 Beta is uninstalled. The identical error also occurred with the most recent build of NIS 2009 and the previous beta build of Norton 360.

It's not Norton 360 and not just x64.  I am seeing the same on Windows 7 32-bit.  I did have the N360 3.0 beta installed, and seeing some other posts suggesting that was the problem, uninstalled it and installed AVG Free 8, which some said was "fine".  Not.

Like others here, the error is more likely to appear with heavy network traffic, such as backing up or copying to a NAS disk.  From what I can tell from my Googling, "solutions" are really just voodoo and there is no real solution out there.  I have also seen suggestions that installing newer Ethernet adapter drivers helps - doesn't for me.

It appears that the only "surefire" solution is to remove any and all AV products!  Yuck.

This is putting a big crimp in my use of Windows 7.