BleepingComputer.com: BSOD...int15.sys,tdx.sys,irql_not_less_or_equal

Here's my problem, guys.
Here's my system:
OS Name Microsoft® Windows Vista™ Home Premium
Version 6.0.6001 Service Pack 1 Build 6001
System Manufacturer ACER
System Model Aspire M1640
Processor Intel® Pentium® Dual CPU E2160 @ 1.80GHz, 1803 Mhz, 2 Core(s), 2 Logical Processor(s)
BIOS Version/Date American Megatrends Inc. R01-A3, 1/29/2008
SMBIOS Version 2.5
Installed Physical Memory (RAM) 2.00 GB
Video: nVidia 7050/nForce 620i 256 MB

I haven't changed any hardware on this since I bought it (though I know I need a better video card).
So I only have two really new, current, push-the-system-to-its-limits kinda games, Spore and Fallout 3. I've played them both quite a bit. Until the other day. To preface, I haven't played either in a month or so, and moved from Arkansas to Oklahoma in that time. And I've had NO PROBLEMS WHATSOEVER with either, or with any other application.
So I go to load Spore, and I get a BSOD saying IRQL_NOT_LESS_OR_EQUAL. I checked the CPU temp, and it's fine. I haven't run a ram check yet (don't have any blank CDs to make a boot disc with), but I've run other applications that are ram hogs and I've never gotten this message randomly, I ONLY GET IT WHEN LOADING SPORE! The minidump seems to point to TDX.SYS. If I go into VERIFIER.EXE and flag all things non-Microsoft, it BSOD's on bootup on INT15.sys, which I know to be part of Acer's eRecovery utility.
Now, here's the weird part.
Since the only other high end, current game I have is Fallout 3 (which, admittedly, my system chokes on a bit with my video card as it is), I decided to see if I'd get the error on starting it as well. Actually, what I got was a message saying the renderer failed and that my video card didn't support the current settings. No settings had been changed, I'd played the game fine until then. I'd logged around 80 hours on it, actually. So, just on a whim, I go into the settings on the game's launcher, hit the "low quality" button (which it was already on), and start the game. It takes awhile, and it pauses on a black screen for awhile, but it loads...in a display that has been vertically compressed. A letterbox on my widescreen monitor. But it ran. So I played for two or three minutes, it seemed stable, so I exited out and loaded again, and it crashed on load. No BSOD, it just said the "program has stopped working." Did this again, same result.
Since this only seems to happen on video-intensive software, I'm wondering, is my video card going bad? Could it be that these programs are pushing the video ram too hard and making it run hot? Or what?
Argh.
Thanks guys,
Colin

At the very least it's the driver, if not the card
http://www.microsoft.com/technet/prodtechn...7.mspx?mfr=true

Disable the Acer e stuff from loading an boot and see if it fixes it. If not, please post the contents of the minidump analysis here for us to have a look at.

Alright, sorry it took so long to get back on here.
The video card drivers are up to date. I ran a RAM check, three times, it's fine. Been getting something new...the screen will flash black sometimes. Just momentarily, and it seems to be mostly when the computer's thinking about something...like when I plug in a jump drive, hook something up via a USB cable (like my phone), when you load something...yeah. So I'm increasingly starting to think that it's the video card. Anyway, here's what I got off the last minidump. I disable the Acer stuff, tried to load Spore, and it still crashed.

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


Loading Dump File [C:\Windows\Minidump\Mini021809-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows Server 2008/Windows Vista SP1 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18145.x86fre.vistasp1_gdr.080917-1612
Machine Name:
Kernel base = 0x8200a000 PsLoadedModuleList = 0x82121c70
Debug session time: Wed Feb 18 17:51:54.230 2009 (GMT-6)
System Uptime: 0 days 0:04:10.947
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {54, 1b, 1, 823c6fe9}

Probably caused by : tdx.sys ( tdx!TdxSendConnectionTlRequestComplete+bc )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000054, memory referenced
Arg2: 0000001b, IRQL
Arg3: 00000001, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 823c6fe9, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82141868
Unable to read MiSystemVaType memory at 82121420
 00000054 

CURRENT_IRQL:  1b

FAULTING_IP: 
hal!KeAcquireInStackQueuedSpinLockRaiseToSynch+19
823c6fe9 8711            xchg    edx,dword ptr [ecx]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  8816fa40 -- (.trap 0xffffffff8816fa40)
ErrCode = 00000002
eax=8816fac4 ebx=00000000 ecx=00000054 edx=8816fac4 esi=815f7ba0 edi=00000000
eip=823c6fe9 esp=8816fab4 ebp=8816fad0 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
hal!KeAcquireInStackQueuedSpinLockRaiseToSynch+0x19:
823c6fe9 8711            xchg    edx,dword ptr [ecx]  ds:0023:00000054=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 823c6fe9 to 82064d24

STACK_TEXT:  
8816fa40 823c6fe9 badb0d00 8816fac4 00000000 nt!KiTrap0E+0x2ac
8816fab0 8204c500 815f7ba0 815f7b60 00000000 hal!KeAcquireInStackQueuedSpinLockRaiseToSynch+0x19
8816fad0 8204442b 815f7ba0 00000000 00000000 nt!KeInsertQueueApc+0x21
8816fb08 8b1aa5c0 00000000 815f8020 0000000a nt!IopfCompleteRequest+0x438
8816fb20 8c13bd84 025f7ba0 00000000 0000000a tdx!TdxSendConnectionTlRequestComplete+0xbc
8816fb40 8c1395a7 815f8020 86f50b90 8c1c8850 tcpip!TcpCompleteTcbSend+0x2e
8816fb98 8c138f1b 86f50b10 00336008 8816fbfc tcpip!TcpTcbReceive+0x287
8816fbf0 8c138d14 86f50b10 00000000 00000000 tcpip!TcpMatchReceive+0x1ec
8816fc38 8c139310 86f50b10 815f5640 815f5610 tcpip!TcpPreValidatedReceive+0x2b0
8816fc54 8c139913 86f50b10 815f5640 8816fc90 tcpip!TcpReceive+0x32
8816fc64 8c163fef 8816fc78 c000023e 00000000 tcpip!TcpNlClientReceiveDatagrams+0x12
8816fc90 8c163db2 8c1bae50 8816fce4 c000023e tcpip!IppDeliverListToProtocol+0x49
8816fcb0 8c163cd9 8c1bac68 00000006 8816fce4 tcpip!IppProcessDeliverList+0x2a
8816fd08 8c15b147 8c1bac68 00000006 8210c13c tcpip!IppReceiveHeaderBatch+0x1eb
8816fd30 8222633b 86e64448 001bac68 83cba2d8 tcpip!IppLoopbackTransmit+0x52
8816fd44 82042445 865f5d08 00000000 83cba2d8 nt!IopProcessWorkItem+0x23
8816fd7c 821dfb18 865f5d08 e1bd0086 00000000 nt!ExpWorkerThread+0xfd
8816fdc0 82038a2e 82042348 00000001 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
tdx!TdxSendConnectionTlRequestComplete+bc
8b1aa5c0 5f              pop     edi

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  tdx!TdxSendConnectionTlRequestComplete+bc

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: tdx

IMAGE_NAME:  tdx.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  479190ee

FAILURE_BUCKET_ID:  0xA_tdx!TdxSendConnectionTlRequestComplete+bc

BUCKET_ID:  0xA_tdx!TdxSendConnectionTlRequestComplete+bc

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

Here's the last one before that, it's from before I disabled the Acer stuff, otherwise all is the same on the system...updated drivers, etc.

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


Loading Dump File [C:\Windows\Minidump\Mini012809-09.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows Server 2008/Windows Vista SP1 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18145.x86fre.vistasp1_gdr.080917-1612
Machine Name:
Kernel base = 0x81e16000 PsLoadedModuleList = 0x81f2dc70
Debug session time: Wed Jan 28 20:38:30.899 2009 (GMT-6)
System Uptime: 0 days 0:01:00.586
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D5, {a98dcf80, 0, 9ce4e7f5, 0}

Unable to load image \??\C:\Acer\Empowering Technology\eRecovery\int15.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for int15.sys
*** ERROR: Module load completed but symbols could not be loaded for int15.sys

Could not read faulting driver name
Probably caused by : int15.sys ( int15+17f5 )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL (d5)
Memory was referenced after it was freed.
This cannot be protected by try-except.
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: a98dcf80, memory referenced
Arg2: 00000000, value 0 = read operation, 1 = write operation
Arg3: 9ce4e7f5, if non-zero, the address which referenced memory.
Arg4: 00000000, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from 81f4d868
Unable to read MiSystemVaType memory at 81f2d420
 a98dcf80 

FAULTING_IP: 
int15+17f5
9ce4e7f5 ??              ???

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  9

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0xD5

PROCESS_NAME:  eRecoveryServic

CURRENT_IRQL:  0

TRAP_FRAME:  a0c7ab6c -- (.trap 0xffffffffa0c7ab6c)
ErrCode = 00000000
eax=a98dcf68 ebx=9e6768b8 ecx=37a9696e edx=00047824 esi=9e688fff edi=98a3afff
eip=9ce4e7f5 esp=a0c7abe0 ebp=a0c7ac0c iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
int15+0x17f5:
9ce4e7f5 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from 81e70b54 to 81ebb0f5

STACK_TEXT:  
a0c7ab54 81e70b54 00000000 a98dcf80 00000000 nt!MmAccessFault+0x10a
a0c7ab54 9ce4e7f5 00000000 a98dcf80 00000000 nt!KiTrap0E+0xdc
WARNING: Stack unwind information not available. Following frames may be wrong.
a0c7abdc 8c5ab368 a98dcf68 00223e84 00000000 int15+0x17f5
a0c7ac0c 820f86be 9e6768b8 a98dcf68 9e653e20 0x8c5ab368
a0c7ac30 81ed1f8a a98dcfd8 a98dcf68 9e6768b8 nt!IovCallDriver+0x23f
a0c7ac44 82062615 9e653e20 a98dcf68 a98dcfd8 nt!IofCallDriver+0x1b
a0c7ac64 82062dba 9e6768b8 9e653e20 04330b00 nt!IopSynchronousServiceTail+0x1d9
a0c7ad00 8204ca8d 9e6768b8 a98dcf68 00000000 nt!IopXxxControlFile+0x6b7
a0c7ad34 81e6da1a 00000284 00000000 00000000 nt!NtDeviceIoControlFile+0x2a
a0c7ad34 776f9a94 00000284 00000000 00000000 nt!KiFastCallEntry+0x12a
0413f824 00000000 00000000 00000000 00000000 0x776f9a94


STACK_COMMAND:  kb

FOLLOWUP_IP: 
int15+17f5
9ce4e7f5 ??              ???

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  int15+17f5

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: int15

IMAGE_NAME:  int15.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4689ae6c

FAILURE_BUCKET_ID:  0xD5_VRF_int15+17f5

BUCKET_ID:  0xD5_VRF_int15+17f5

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

And one more for kicks.

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


Loading Dump File [C:\Windows\Minidump\Mini012809-08.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows Server 2008/Windows Vista SP1 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18145.x86fre.vistasp1_gdr.080917-1612
Machine Name:
Kernel base = 0x81e0c000 PsLoadedModuleList = 0x81f23c70
Debug session time: Wed Jan 28 18:57:43.583 2009 (GMT-6)
System Uptime: 0 days 0:03:52.300
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 8a99ca08, a11d77b4, 0}

*** WARNING: Unable to verify timestamp for Mpfp.sys
*** ERROR: Module load completed but symbols could not be loaded for Mpfp.sys
*** WARNING: Unable to verify timestamp for bckd.sys
*** ERROR: Module load completed but symbols could not be loaded for bckd.sys
Probably caused by : tdx.sys ( tdx!TdxCreateControlChannel+70 )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 8a99ca08, The address that the exception occurred at
Arg3: a11d77b4, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
tdx!TdxCreateControlChannel+70
8a99ca08 89700c          mov     dword ptr [eax+0Ch],esi

TRAP_FRAME:  a11d77b4 -- (.trap 0xffffffffa11d77b4)
ErrCode = 00000002
eax=00000580 ebx=00000000 ecx=00000002 edx=00000000 esi=9e555088 edi=00000003
eip=8a99ca08 esp=a11d7828 ebp=a11d7830 iopl=0         nv up ei pl nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010206
tdx!TdxCreateControlChannel+0x70:
8a99ca08 89700c          mov     dword ptr [eax+0Ch],esi ds:0023:0000058c=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  8

DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  SporeApp.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 8a9a3e23 to 8a99ca08

STACK_TEXT:  
a11d7830 8a9a3e23 86cae338 00000580 00000000 tdx!TdxCreateControlChannel+0x70
a11d7868 81ec7fd3 86cae200 841ce470 841ce568 tdx!TdxTdiDispatchCreate+0x5f
a11d7880 8a979f50 a11d78ec 8a98ae80 8ccb8600 nt!IofCallDriver+0x63
WARNING: Stack unwind information not available. Following frames may be wrong.
a11d78b4 8a97217c 86cee700 841ce470 8ca000d0 Mpfp+0x8f50
a11d78f0 81ec7fd3 86cee700 841ce470 a09c6c40 Mpfp+0x117c
a11d7908 8a9dc851 98db35b8 a09c6c40 00000002 nt!IofCallDriver+0x63
a11d791c 8a9d880a 8ca000d0 a09c6c40 98db35b8 bckd+0x8851
a11d7954 8a9dd986 98db35b8 98db3694 98db35b8 bckd+0x480a
a11d7968 8a9e10a6 98db35b8 a09c6c40 98db35b8 bckd+0x9986
a11d7980 8a9dea93 00000000 98db35b8 8ca000d0 bckd+0xd0a6
a11d799c 8a9dc85e 0fa000d0 a09c6c40 00000000 bckd+0xaa93
a11d79b8 8a9dccb4 8ca000d0 a09c6c40 841ce470 bckd+0x885e
a11d7a04 8a9dd328 a09c6c40 0000000a 00000001 bckd+0x8cb4
a11d7a18 8a9d8e0c a09c6c40 841ce528 8ca000d0 bckd+0x9328
a11d7a44 8a9dd986 841ce580 00000104 841ce470 bckd+0x4e0c
a11d7a58 8a9e10a6 841ce470 83e94830 8ca00018 bckd+0x9986
a11d7a70 81ec7fd3 00000000 841ce470 841ce600 bckd+0xd0a6
a11d7a88 8716e405 2608bb8e a11d7b54 00000001 nt!IofCallDriver+0x63
a11d7ae0 8715e52b 9e599400 00000000 8715e52b afd!AfdFastConnectionSend+0x28c
a11d7c58 820589be 9e46fb01 00000001 1335fdbc afd!AfdFastIoDeviceControl+0x512
a11d7d00 82042a8d 86cb09f0 000005a8 00000000 nt!IopXxxControlFile+0x2cf
a11d7d34 81e63a1a 000005a0 000005a8 00000000 nt!NtDeviceIoControlFile+0x2a
a11d7d34 76ee9a94 000005a0 000005a8 00000000 nt!KiFastCallEntry+0x12a
1335fe10 00000000 00000000 00000000 00000000 0x76ee9a94


STACK_COMMAND:  kb

FOLLOWUP_IP: 
tdx!TdxCreateControlChannel+70
8a99ca08 89700c          mov     dword ptr [eax+0Ch],esi

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  tdx!TdxCreateControlChannel+70

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: tdx

IMAGE_NAME:  tdx.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  479190ee

FAILURE_BUCKET_ID:  0x8E_tdx!TdxCreateControlChannel+70

BUCKET_ID:  0x8E_tdx!TdxCreateControlChannel+70

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 8a99ca08, The address that the exception occurred at
Arg3: a11d77b4, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
tdx!TdxCreateControlChannel+70
8a99ca08 89700c          mov     dword ptr [eax+0Ch],esi

TRAP_FRAME:  a11d77b4 -- (.trap 0xffffffffa11d77b4)
ErrCode = 00000002
eax=00000580 ebx=00000000 ecx=00000002 edx=00000000 esi=9e555088 edi=00000003
eip=8a99ca08 esp=a11d7828 ebp=a11d7830 iopl=0         nv up ei pl nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010206
tdx!TdxCreateControlChannel+0x70:
8a99ca08 89700c          mov     dword ptr [eax+0Ch],esi ds:0023:0000058c=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  8

DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  SporeApp.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 8a9a3e23 to 8a99ca08

STACK_TEXT:  
a11d7830 8a9a3e23 86cae338 00000580 00000000 tdx!TdxCreateControlChannel+0x70
a11d7868 81ec7fd3 86cae200 841ce470 841ce568 tdx!TdxTdiDispatchCreate+0x5f
a11d7880 8a979f50 a11d78ec 8a98ae80 8ccb8600 nt!IofCallDriver+0x63
WARNING: Stack unwind information not available. Following frames may be wrong.
a11d78b4 8a97217c 86cee700 841ce470 8ca000d0 Mpfp+0x8f50
a11d78f0 81ec7fd3 86cee700 841ce470 a09c6c40 Mpfp+0x117c
a11d7908 8a9dc851 98db35b8 a09c6c40 00000002 nt!IofCallDriver+0x63
a11d791c 8a9d880a 8ca000d0 a09c6c40 98db35b8 bckd+0x8851
a11d7954 8a9dd986 98db35b8 98db3694 98db35b8 bckd+0x480a
a11d7968 8a9e10a6 98db35b8 a09c6c40 98db35b8 bckd+0x9986
a11d7980 8a9dea93 00000000 98db35b8 8ca000d0 bckd+0xd0a6
a11d799c 8a9dc85e 0fa000d0 a09c6c40 00000000 bckd+0xaa93
a11d79b8 8a9dccb4 8ca000d0 a09c6c40 841ce470 bckd+0x885e
a11d7a04 8a9dd328 a09c6c40 0000000a 00000001 bckd+0x8cb4
a11d7a18 8a9d8e0c a09c6c40 841ce528 8ca000d0 bckd+0x9328
a11d7a44 8a9dd986 841ce580 00000104 841ce470 bckd+0x4e0c
a11d7a58 8a9e10a6 841ce470 83e94830 8ca00018 bckd+0x9986
a11d7a70 81ec7fd3 00000000 841ce470 841ce600 bckd+0xd0a6
a11d7a88 8716e405 2608bb8e a11d7b54 00000001 nt!IofCallDriver+0x63
a11d7ae0 8715e52b 9e599400 00000000 8715e52b afd!AfdFastConnectionSend+0x28c
a11d7c58 820589be 9e46fb01 00000001 1335fdbc afd!AfdFastIoDeviceControl+0x512
a11d7d00 82042a8d 86cb09f0 000005a8 00000000 nt!IopXxxControlFile+0x2cf
a11d7d34 81e63a1a 000005a0 000005a8 00000000 nt!NtDeviceIoControlFile+0x2a
a11d7d34 76ee9a94 000005a0 000005a8 00000000 nt!KiFastCallEntry+0x12a
1335fe10 00000000 00000000 00000000 00000000 0x76ee9a94


STACK_COMMAND:  kb

FOLLOWUP_IP: 
tdx!TdxCreateControlChannel+70
8a99ca08 89700c          mov     dword ptr [eax+0Ch],esi

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  tdx!TdxCreateControlChannel+70

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: tdx

IMAGE_NAME:  tdx.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  479190ee

FAILURE_BUCKET_ID:  0x8E_tdx!TdxCreateControlChannel+70

BUCKET_ID:  0x8E_tdx!TdxCreateControlChannel+70

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

The common theme seems to be tdx.sys. I've looked it up online, haven't found anything that's helped. But maybe someone on here can.
Thanks,
Colin

It's not unusual for one fix to generate another issue - that's due to the problem occurring a significant amount of time before the crash.

I'm not familiar with Spore - but does it have an autoupdate feature that may be accessing the internet?

In this case, it's been about 2 weeks since the Acer crashes stopped - so we can assume that the Acer fix is done.
Now, the issue is in tdx.sys - which is associated with your networking components.
The stack trace cites the error when it calls "TdxSendConnectionTlRequestComplete+bc" - which seems to indicate your connection.
This doesn't tell us if it's your Windows installation or the networking drivers causing it - but it's easier to fix the drivers than it is to fix Windows.


To do this, download a copy of the latest drivers for your network card from the website of the manufacturer of your network card/chipset. Then uninstall the networking software from the Programs applet in Control Panel. Reboot and install the new network drivers and see if it works.

Tried that, same result. Still referencing tdx.sys. Maybe the most recent pack of drivers for my computer's ethernet card are bad? Seems like a longshot but I've had it happen before.
Here's the crash dump.

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


Loading Dump File [C:\Windows\Minidump\Mini022109-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows Server 2008/Windows Vista SP1 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18145.x86fre.vistasp1_gdr.080917-1612
Machine Name:
Kernel base = 0x82033000 PsLoadedModuleList = 0x8214ac70
Debug session time: Sat Feb 21 17:57:24.195 2009 (GMT-6)
System Uptime: 0 days 0:08:33.786
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 8b1a3a08, a03bb7b4, 0}

*** WARNING: Unable to verify timestamp for Mpfp.sys
*** ERROR: Module load completed but symbols could not be loaded for Mpfp.sys
*** WARNING: Unable to verify timestamp for bckd.sys
*** ERROR: Module load completed but symbols could not be loaded for bckd.sys
Probably caused by : tdx.sys ( tdx!TdxCreateControlChannel+70 )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 8b1a3a08, The address that the exception occurred at
Arg3: a03bb7b4, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
tdx!TdxCreateControlChannel+70
8b1a3a08 89700c          mov     dword ptr [eax+0Ch],esi

TRAP_FRAME:  a03bb7b4 -- (.trap 0xffffffffa03bb7b4)
ErrCode = 00000002
eax=00000040 ebx=00000000 ecx=00000002 edx=00000000 esi=8453f530 edi=00000003
eip=8b1a3a08 esp=a03bb828 ebp=a03bb830 iopl=0         nv up ei pl nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010206
tdx!TdxCreateControlChannel+0x70:
8b1a3a08 89700c          mov     dword ptr [eax+0Ch],esi ds:0023:0000004c=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  SporeApp.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 8b1aae23 to 8b1a3a08

STACK_TEXT:  
a03bb830 8b1aae23 87082d90 00000040 00000000 tdx!TdxCreateControlChannel+0x70
a03bb868 820eefd3 86e3a440 8ed410c0 8ed411b8 tdx!TdxTdiDispatchCreate+0x5f
a03bb880 8b180f50 a03bb8ec 8b191e80 8c38f100 nt!IofCallDriver+0x63
WARNING: Stack unwind information not available. Following frames may be wrong.
a03bb8b4 8b17917c 87045020 8ed410c0 8c2000d0 Mpfp+0x8f50
a03bb8f0 820eefd3 87045020 8ed410c0 844b6870 Mpfp+0x117c
a03bb908 8b1e3851 80d41bf8 844b6870 00000002 nt!IofCallDriver+0x63
a03bb91c 8b1df80a 8c2000d0 844b6870 80d41bf8 bckd+0x8851
a03bb954 8b1e4986 80d41bf8 80d41cd4 80d41bf8 bckd+0x480a
a03bb968 8b1e80a6 80d41bf8 844b6870 80d41bf8 bckd+0x9986
a03bb980 8b1e5a93 00000000 80d41bf8 8c2000d0 bckd+0xd0a6
a03bb99c 8b1e385e 0f2000d0 844b6870 00000000 bckd+0xaa93
a03bb9b8 8b1e3cb4 8c2000d0 844b6870 8ed410c0 bckd+0x885e
a03bba04 8b1e4328 844b6870 0000000a 00000001 bckd+0x8cb4
a03bba18 8b1dfe0c 844b6870 8ed41178 8c2000d0 bckd+0x9328
a03bba44 8b1e4986 8ed41040 00000104 8ed410c0 bckd+0x4e0c
a03bba58 8b1e80a6 8ed410c0 84432440 8c200018 bckd+0x9986
a03bba70 820eefd3 00000000 8ed410c0 8ed41008 bckd+0xd0a6
a03bba88 8736c405 270e1d86 a03bbb54 00000001 nt!IofCallDriver+0x63
a03bbae0 8735c52b a06d67d0 00000000 8735c52b afd!AfdFastConnectionSend+0x28c
a03bbc58 8227f9be 8431e801 00000001 082efdbc afd!AfdFastIoDeviceControl+0x512
a03bbd00 82269a8d 86fca998 00000378 00000000 nt!IopXxxControlFile+0x2cf
a03bbd34 8208aa1a 00000308 00000378 00000000 nt!NtDeviceIoControlFile+0x2a
a03bbd34 77159a94 00000308 00000378 00000000 nt!KiFastCallEntry+0x12a
082efe10 00000000 00000000 00000000 00000000 0x77159a94


STACK_COMMAND:  kb

FOLLOWUP_IP: 
tdx!TdxCreateControlChannel+70
8b1a3a08 89700c          mov     dword ptr [eax+0Ch],esi

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  tdx!TdxCreateControlChannel+70

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: tdx

IMAGE_NAME:  tdx.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  479190ee

FAILURE_BUCKET_ID:  0x8E_tdx!TdxCreateControlChannel+70

BUCKET_ID:  0x8E_tdx!TdxCreateControlChannel+70

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

Oh, and yes, Spore does use internet connectivity.

Yep, and Spore uses tdx.sys as indicated in your analysis (Process name is SporeApp.exe)

I'd suspect a corruption of the Spore program and would first check for updates. If there are none available, then I'd suggest uninstalling Spore and then reinstalling a fresh copy.