Vista Blue Screen of Death???

[Guest]

hi,
I have been running Windows Vista Home Premium x32 for 2 months. Everything
was running fine until recently - I've started getting a BSOD every so often.
All my drivers are up to date, and I've used the microsoft memory diagnostic,
which reports no errors. Anyway...

The screen dump is as follows:

STOP 0X0000007E

(0XC0000005, 0X8C9B26FD, 0X878C1B38, 0X878C1834)

tdx.sys Address 8C9B26FD base of 8C9A8000, Datestamp 454b2f

Can anybody shed some light on what's causing this error? Any help would be
much appreciated!

 

[Guest]

NEED HELP!!!

This MS Discussion Group Link for a New Post will not work ...
Only the Reply Link works...
Can you Help???

OS: Vista HP
IE7

thanks

 

[Synapse Syndrome]

NEED HELP!!!

This MS Discussion Group Link for a New Post will not work ...
Only the Reply Link works...
Can you Help???

OS: Vista HP
IE7

Access this newsgroup with a newsreader.

Click on this link and put in your details and you should get back here.

news://microsoft.public.windows.vista.general

ss.

 

[xfile]

Hi,

Did you install anything recently?

The only relevant information that I could find from MS KB is the following
article based on part of your error message: tdx.sys

Windows Vista may stop responding when you install software that adds legacy
network drivers:

http://support.microsoft.com/kb/934611


You may need to contact MS support for hotfix and good luck.

 

[Guest]

Hi,

thanks for the tip! I installed that hotfix and the BSOD disappeared...
temporarily, until I received another a few hours later stating
"IRQL_NOT_LESS_OR_EQUAL" etc.

After running verifier.exe, it turns out that I have 5 unsigned drivers,
which are all part of "Eset Smart Security BETA 1b" (the future version of
NOD32). The BSODS started about a day after I installed this, so I think I
might have located the problem,

Thanks for your help.

 

[xfile]

You're welcome and good luck.

Hi,

thanks for the tip! I installed that hotfix and the BSOD disappeared...
temporarily, until I received another a few hours later stating
"IRQL_NOT_LESS_OR_EQUAL" etc.

After running verifier.exe, it turns out that I have 5 unsigned drivers,
which are all part of "Eset Smart Security BETA 1b" (the future version of
NOD32). The BSODS started about a day after I installed this, so I think I
might have located the problem,

Thanks for your help.

 

[Gary G. Little]

Can you back off to the release version of NOD32? I've been using NOD32
since it was released for VISTA for 8 months now with nary a problem.

Also ... how tight do you have things screwed down on Verifier? Did you take
the standard settings or set all options?