BSOD, perplexed...

Converge

Converge

Converge

Soldato
Joined
26 Jan 2005
Posts
7,898
Hey guys,

I keep getting the BSOD (Blue screen of death) ramdomly lately. It comes up and says its dumping physical memory then basically restarts itself. Comes out of nowhere. Had Vista installed for over a month now, only started happening in the last week, any idea's?

Sorry i don't have much info about it, as its just started happening so unexpectedly, i don't really know what'd be the cause :confused: :eek:

It's happened a few times when the computer's been "locked" if that helps, but also a few times when i've been using iTunes and a few times just when its idle without being locked or anything.

Help me! :)
 
When I first installed Vista I had numerous problems, BSODs, freezing etc. Then my PSU blew and I bought a 620w Corsair, since doing that Vista has been fine.

Not sure if this is the case with you, just a possibility.
 
Last edited:
I'd be checking my hardware.

Ram, PSU and HDD's could all be a cause of this. (As could a software problem obviously)
 
That link wouldn't load for me for some reason... :(

This is the info that comes when the computer gets back to the desktop after restarting...

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6000.2.0.0.768.3
Locale ID: 2057

Additional information about the problem:
BCCode: 1000007e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF9800A0BA8EF
BCP3: FFFFF98002EB7868
BCP4: FFFFF98002EB7240
OS Version: 6_0_6000
Service Pack: 0_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\Mini122807-01.dmp
C:\Users\Mark\AppData\Local\Temp\WER-110074-0.sysdata.xml
C:\Users\Mark\AppData\Local\Temp\WERFEC8.tmp.version.txt


Any idea's what this means?

Thanks. :)
 
Just going to run the memory test and i will get back to you guys about it, also, Swinnie i've tried locating the file, but its not anywhere to be found :(
 
I've done the memtest, it's not showing any errors for 150% test duration. I thought it was the memory too, but this may prove otherwise then?

I've tried the link, which is now working, i'll get back to you guys when and if the error comes up again, so i will then use the guide, as at the moment there was no files produced from the previous one, as i need it to happen again, as some bits from the link posted, i've implemented, so there will be logs in future :)
 
I've tried the guide fully now, problem is, it's not working due to this error...

*** WARNING: Unable to verify timestamp for epfwtdi.sys
*** ERROR: Module load completed but symbols could not be loaded for epfwtdi.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

Yep i've rechecked the symbol path, copied and pasted it too to make doubley sure that i didn't input it wrong, so any idea's on what the new path is?

Thanks for your help so far guys :)


EDIT : just trying the guide to how to do the symbols via the MS website, i'll let you know if i get stuck :)
 
Ok, this is what was displayed (Sorry, but its rather large!)

:eek:

BugCheck 1000007E, {ffffffffc0000005, fffff9800a0ba8ef, fffff98002eb7868, fffff98002eb7240}

*** WARNING: Unable to verify timestamp for epfwtdi.sys
*** ERROR: Module load completed but symbols could not be loaded for epfwtdi.sys


Probably caused by : tdx.sys ( tdx!TdxIssueQueryAddressRequest+207 )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff9800a0ba8ef, The address that the exception occurred at
Arg3: fffff98002eb7868, Exception Record Address
Arg4: fffff98002eb7240, Context Record Address

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!TdxIssueQueryAddressRequest+207
fffff980`0a0ba8ef ff5008 call qword ptr [rax+8]

EXCEPTION_RECORD: fffff98002eb7868 -- (.exr 0xfffff98002eb7868)
ExceptionAddress: fffff9800a0ba8ef (tdx!TdxIssueQueryAddressRequest+0x0000000000000207)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000008
Attempt to read from address 0000000000000008

CONTEXT: fffff98002eb7240 -- (.cxr 0xfffff98002eb7240)
rax=0000000000000000 rbx=fffffa8005479d80 rcx=0000000000000000
rdx=fffff98002eb7ad0 rsi=fffffa8005c93c88 rdi=fffffa8005479d80
rip=fffff9800a0ba8ef rsp=fffff98002eb7aa0 rbp=fffffa8005c93c10
r8=0000000000000000 r9=0000000000000000 r10=fffffa8005479d80
r11=fffff9800a0ba2b0 r12=fffffa8005479d88 r13=fffffa8008b8b701
r14=fffffa80050dc3b0 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202
tdx!TdxIssueQueryAddressRequest+0x207:
fffff980`0a0ba8ef ff5008 call qword ptr [rax+8] ds:002b:00000000`00000008=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

CURRENT_IRQL: 0

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

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80001dfa0b0
0000000000000008

BUGCHECK_STR: 0x7E

DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER: from fffff9800a0b4030 to fffff9800a0ba8ef

STACK_TEXT:
fffff980`02eb7aa0 fffff980`0a0b4030 : 00000000`00000002 fffffa80`05479d80 fffffa80`0691e720 fffffa80`05c93cb8 : tdx!TdxIssueQueryAddressRequest+0x207
fffff980`02eb7b60 fffff980`0a0bb520 : fffffa80`08528760 fffff800`01d68980 fffffa80`09480ea0 fffffa80`05c93c10 : tdx!TdxQueryInformationConnection+0x80
fffff980`02eb7b90 fffff980`0a09dd27 : fffffa80`08528760 fffff800`01d68900 00000000`00000000 fffffa80`09480e11 : tdx!TdxTdiDispatchInternalDeviceControl+0x1ac
fffff980`02eb7bc0 fffffa80`08528760 : fffff800`01d68900 00000000`00000000 fffffa80`09480e11 00000000`00000000 : epfwtdi+0x5d27
fffff980`02eb7bc8 fffff800`01d68900 : 00000000`00000000 fffffa80`09480e11 00000000`00000000 fffff800`00000000 : 0xfffffa80`08528760
fffff980`02eb7bd0 00000000`00000000 : fffffa80`09480e11 00000000`00000000 fffff800`00000000 fffffa80`0691e701 : nt!ExpWorkerThreadBalanceManagerPtr
fffff980`02eb7bd8 fffffa80`09480e11 : 00000000`00000000 fffff800`00000000 fffffa80`0691e701 00000000`00000000 : 0x0
fffff980`02eb7be0 00000000`00000000 : fffff800`00000000 fffffa80`0691e701 00000000`00000000 00000000`00000000 : 0xfffffa80`09480e11
fffff980`02eb7be8 fffff800`00000000 : fffffa80`0691e701 00000000`00000000 00000000`00000000 fffffa80`06c65300 : 0x0
fffff980`02eb7bf0 fffffa80`0691e701 : 00000000`00000000 00000000`00000000 fffffa80`06c65300 fffffa80`0691e818 : 0xfffff800`00000000
fffff980`02eb7bf8 00000000`00000000 : 00000000`00000000 fffffa80`06c65300 fffffa80`0691e818 fffffa80`05c93c10 : 0xfffffa80`0691e701
fffff980`02eb7c00 00000000`00000000 : fffffa80`06c65300 fffffa80`0691e818 fffffa80`05c93c10 fffffa80`05371f40 : 0x0
fffff980`02eb7c08 fffffa80`06c65300 : fffffa80`0691e818 fffffa80`05c93c10 fffffa80`05371f40 fffffa80`09480ea0 : 0x0
fffff980`02eb7c10 fffffa80`0691e818 : fffffa80`05c93c10 fffffa80`05371f40 fffffa80`09480ea0 fffff980`02eb7d58 : 0xfffffa80`06c65300
fffff980`02eb7c18 fffffa80`05c93c10 : fffffa80`05371f40 fffffa80`09480ea0 fffff980`02eb7d58 fffff800`01d68980 : 0xfffffa80`0691e818
fffff980`02eb7c20 fffffa80`05371f40 : fffffa80`09480ea0 fffff980`02eb7d58 fffff800`01d68980 00000000`30060001 : 0xfffffa80`05c93c10
fffff980`02eb7c28 fffffa80`09480ea0 : fffff980`02eb7d58 fffff800`01d68980 00000000`30060001 fffff980`02eb7c48 : 0xfffffa80`05371f40
fffff980`02eb7c30 fffff980`02eb7d58 : fffff800`01d68980 00000000`30060001 fffff980`02eb7c48 fffff980`02eb7c48 : 0xfffffa80`09480ea0
fffff980`02eb7c38 fffff800`01d68980 : 00000000`30060001 fffff980`02eb7c48 fffff980`02eb7c48 fffffa80`0b3102b0 : 0xfffff980`02eb7d58
fffff980`02eb7c40 00000000`30060001 : fffff980`02eb7c48 fffff980`02eb7c48 fffffa80`0b3102b0 00000000`00000000 : nt!ExWorkerQueue
fffff980`02eb7c48 fffff980`02eb7c48 : fffff980`02eb7c48 fffffa80`0b3102b0 00000000`00000000 fffff980`02eb7d58 : 0x30060001
fffff980`02eb7c50 fffff980`02eb7c48 : fffffa80`0b3102b0 00000000`00000000 fffff980`02eb7d58 00000000`00000001 : 0xfffff980`02eb7c48
fffff980`02eb7c58 fffffa80`0b3102b0 : 00000000`00000000 fffff980`02eb7d58 00000000`00000001 fffffa80`08b74ae0 : 0xfffff980`02eb7c48
fffff980`02eb7c60 00000000`00000000 : fffff980`02eb7d58 00000000`00000001 fffffa80`08b74ae0 fffff980`0a09dde4 : 0xfffffa80`0b3102b0
fffff980`02eb7c68 fffff980`02eb7d58 : 00000000`00000001 fffffa80`08b74ae0 fffff980`0a09dde4 fffffa80`0691e720 : 0x0
fffff980`02eb7c70 00000000`00000001 : fffffa80`08b74ae0 fffff980`0a09dde4 fffffa80`0691e720 fffffa80`08b74ae0 : 0xfffff980`02eb7d58
fffff980`02eb7c78 fffffa80`08b74ae0 : fffff980`0a09dde4 fffffa80`0691e720 fffffa80`08b74ae0 fffff980`0a09de14 : 0x1
fffff980`02eb7c80 fffff980`0a09dde4 : fffffa80`0691e720 fffffa80`08b74ae0 fffff980`0a09de14 fffffa80`08528610 : 0xfffffa80`08b74ae0
fffff980`02eb7c88 fffffa80`0691e720 : fffffa80`08b74ae0 fffff980`0a09de14 fffffa80`08528610 fffffa80`05283ea0 : epfwtdi+0x5de4
fffff980`02eb7c90 fffffa80`08b74ae0 : fffff980`0a09de14 fffffa80`08528610 fffffa80`05283ea0 fffffa80`08b8b700 : 0xfffffa80`0691e720
fffff980`02eb7c98 fffff980`0a09de14 : fffffa80`08528610 fffffa80`05283ea0 fffffa80`08b8b700 fffffa80`00000016 : 0xfffffa80`08b74ae0
fffff980`02eb7ca0 fffffa80`08528610 : fffffa80`05283ea0 fffffa80`08b8b700 fffffa80`00000016 fffffa80`055dda20 : epfwtdi+0x5e14
fffff980`02eb7ca8 fffffa80`05283ea0 : fffffa80`08b8b700 fffffa80`00000016 fffffa80`055dda20 fffffa80`0691e720 : 0xfffffa80`08528610
fffff980`02eb7cb0 fffffa80`08b8b700 : fffffa80`00000016 fffffa80`055dda20 fffffa80`0691e720 fffffa80`09008340 : 0xfffffa80`05283ea0
fffff980`02eb7cb8 fffffa80`00000016 : fffffa80`055dda20 fffffa80`0691e720 fffffa80`09008340 fffff800`01c59da3 : 0xfffffa80`08b8b700
fffff980`02eb7cc0 fffffa80`055dda20 : fffffa80`0691e720 fffffa80`09008340 fffff800`01c59da3 fffffa80`06cb3e60 : 0xfffffa80`00000016
fffff980`02eb7cc8 fffffa80`0691e720 : fffffa80`09008340 fffff800`01c59da3 fffffa80`06cb3e60 fffff800`01d68901 : 0xfffffa80`055dda20
fffff980`02eb7cd0 fffffa80`09008340 : fffff800`01c59da3 fffffa80`06cb3e60 fffff800`01d68901 fffffa80`06cb3e00 : 0xfffffa80`0691e720
fffff980`02eb7cd8 fffff800`01c59da3 : fffffa80`06cb3e60 fffff800`01d68901 fffffa80`06cb3e00 fffff980`02eb7d58 : 0xfffffa80`09008340
fffff980`02eb7ce0 fffff800`01ee196b : fffffa80`09008340 fffffffe`9a5f4400 fffffa80`0691e720 00000000`00000001 : nt!ExpWorkerThread+0x12a
fffff980`02eb7d50 fffff800`01c34656 : fffff800`01d4a980 fffffa80`0691e720 fffffa80`0691e040 fffffa80`0691e040 : nt!PspSystemThreadStartup+0x5b
fffff980`02eb7d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


FOLLOWUP_IP:
tdx!TdxIssueQueryAddressRequest+207
fffff980`0a0ba8ef ff5008 call qword ptr [rax+8]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: tdx!TdxIssueQueryAddressRequest+207

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: tdx

IMAGE_NAME: tdx.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4549be90

STACK_COMMAND: .cxr 0xfffff98002eb7240 ; kb

FAILURE_BUCKET_ID: X64_0x7E_tdx!TdxIssueQueryAddressRequest+207

BUCKET_ID: X64_0x7E_tdx!TdxIssueQueryAddressRequest+207

Followup: MachineOwner
 
Hmm a quick google suggests tdx.sys is a driver that may have something to do with networking.

This is interesting and would suggest you need to update or reinstall network card drivers:
http://support.microsoft.com/kb/934611

From other results appears that using peer-to-peer (torrent etc) programs may also be a trigger.

If you have hardware failures it means that the error could be found anywhere (whatever the computer is doing at the time) but from the above I would suggest you update network drivers and make sure you have the latest Vista compatible version of whatever peer-to-peer software you use :)
 
Ok mate, thanks a bunch for your help, thinking about it a bit, i literally installed uTorrent about the same time it started happening, but i didnt think anything of it, until reading your post!

It's supposed to be Vista compatible i thought? I'll check that link and sort out the networking stuff too, to rule that out!

Thanks man, i'll let you know how it goes :)

Have a happy new year! :D

EDIT: Appears all networking devices are up to date on my end, so it seems more likely to be uTorrent?
 
Last edited:
uTorrent is a user mode application that simply innocently uses Sockets. There's no way that is directly causing the problem - that's actually impossible. What's probably happening is that uTorrent is opening a lot of connections, whether just in quantity or in the high frequency that it opens them, and some network driver in your stack can't handle it due to a bug.
 
Yeah. i understand it couldn't be uTorrent directly, but more something that isn't 100% compatible with uTorrent's methods, just i don't really know what else to do about it, i guess it'll probably be fixed in future, either by uTorrent guys adapting it more for Vista, or MS sorting out the networking a bit.

Either way, i rarely use it, so it shouldn't be a problem really.

Thanks to everyone for helping me with this, been most helpful :)
 
You must log in or register to reply here.
Back
Top Bottom