Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

BSoD error message help


  • Please log in to reply
1 reply to this topic

#1 psycopuppy

psycopuppy

  • Members
  • 16 posts
  • OFFLINE
  •  
  • Local time:05:26 PM

Posted 23 April 2011 - 08:55 AM

So it seems like I get the bsod when either I'm playing a game or when my wife is watching streaming video. The problem is that it dosent happen all the time, maybe a couple of times a week. I havent installed anything new or updated anything (at least as far as I know) here is the log, any suggestions?


Microsoft ® Windows Debugger Version 6.12.0002.633 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18327.x86fre.vistasp2_gdr.101014-0432
Machine Name:
Kernel base = 0x8281c000 PsLoadedModuleList = 0x82933c70
Debug session time: Thu Apr 21 23:22:17.300 2011 (UTC - 6:00)
System Uptime: 0 days 5:28:56.713
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols

Loading unloaded module list
.......................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {4, 2, 1, 8c7e77df}

Probably caused by : tdx.sys ( tdx!TdxCloseConnectionEndpointTlRequestComplete+75 )

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: 00000004, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 8c7e77df, address which referenced memory

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


WRITE_ADDRESS: 00000004

CURRENT_IRQL: 2

FAULTING_IP:
tdx!TdxCloseConnectionEndpointTlRequestComplete+75
8c7e77df 895104 mov dword ptr [ecx+4],edx

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: System

TRAP_FRAME: 88d5fa70 -- (.trap 0xffffffff88d5fa70)
ErrCode = 00000002
eax=84f3cb38 ebx=00000001 ecx=00000000 edx=88d5faf0 esi=84f3caf8 edi=00000000
eip=8c7e77df esp=88d5fae4 ebp=88d5fb08 iopl=0 nv up ei pl nz ac po cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010213
tdx!TdxCloseConnectionEndpointTlRequestComplete+0x75:
8c7e77df 895104 mov dword ptr [ecx+4],edx ds:0023:00000004=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 8c7e77df to 82869fd9

STACK_TEXT:
88d5fa70 8c7e77df badb0d00 88d5faf0 00000002 nt!KiTrap0E+0x2e1
88d5fb08 8804f860 84f3caf8 00000000 84bbc8c8 tdx!TdxCloseConnectionEndpointTlRequestComplete+0x75
88d5fb20 8804fe25 84bbc9f4 00000000 88d5fb40 tcpip!TcpCleanupTcbWorkQueueRoutine+0xbd
88d5fb30 8807020f 84bbc8c8 84bbc8c8 88d5fb98 tcpip!TcpCleanupTcb+0x3b
88d5fb40 880682d6 84bbc8c8 854d7f78 880e3af0 tcpip!TcpDereferenceTcb+0x1c
88d5fb98 88066558 854d7ef8 00bbc8c8 88d5fbfc tcpip!TcpTcbReceive+0x2af
88d5fbf0 88067f3b 854d7ef8 84f80100 84f80100 tcpip!TcpMatchReceive+0x1ec
88d5fc38 88067fd1 854d7ef8 84f808e0 84f8da14 tcpip!TcpPreValidatedReceive+0x1fd
88d5fc54 88066972 854d7ef8 84f808e0 88d5fc90 tcpip!TcpReceive+0x2d
88d5fc64 8807ea8b 88d5fc78 c000023e 00000000 tcpip!TcpNlClientReceiveDatagrams+0x12
88d5fc90 8807e4b8 880d5ebc 88d5fce4 c000023e tcpip!IppDeliverListToProtocol+0x49
88d5fcb0 8807e908 880d5cd0 00000006 88d5fce4 tcpip!IppProcessDeliverList+0x2a
88d5fd08 88063095 880d5cd0 00000006 8291e13c tcpip!IppReceiveHeaderBatch+0x1eb
88d5fd30 82a29c49 8543bf08 000d5cd0 84605d78 tcpip!IppLoopbackTransmit+0x52
88d5fd44 828c1e22 854d88d8 00000000 84605d78 nt!IopProcessWorkItem+0x23
88d5fd7c 829f1f7a 854d88d8 23cf6644 00000000 nt!ExpWorkerThread+0xfd
88d5fdc0 8285aefe 828c1d25 00000001 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
tdx!TdxCloseConnectionEndpointTlRequestComplete+75
8c7e77df 895104 mov dword ptr [ecx+4],edx

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: tdx!TdxCloseConnectionEndpointTlRequestComplete+75

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: tdx

IMAGE_NAME: tdx.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 49e02084

FAILURE_BUCKET_ID: 0xD1_tdx!TdxCloseConnectionEndpointTlRequestComplete+75

BUCKET_ID: 0xD1_tdx!TdxCloseConnectionEndpointTlRequestComplete+75

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

BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 55,405 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:07:26 PM

Posted 23 April 2011 - 02:35 PM

I would try uninstalling the network drivers...then reinstalling same.

Louis




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users