Recent frequent BSOD

[tHeMarriedGuy]

Is Windows 7 . . .
- x86 (32-bit) or x64 ? x86
- the original installed OS on the system? No - Vista 32-bit was originally installed.
- an OEM or full retail version? Full retail
- OEM = came pre-installed on system
- Full Retail = you purchased it from retailer

- What is the age of system (hardware)? 2 years 1 month
- What is the age of OS installation (have you re-installed the OS?) Windows 7 was installed early this year.

I've attempted to check out the dump file using WinDbg and the only thing I've been able to find in it is "tdx.sys". I don't know where to find information beyond that because the tutorials I've viewed haven't made it clear. I figured someone who has a better idea of what they're doing can figure out for me what the problem is exactly.

I should also note that the problems have only been recent (within the past few weeks, starting on 8/11/10). Prior to that, the BSOD was a very, very rare thing.

 

[Lomai]

Hi

Welcome to Seven Forums
Have a look at this SF Thread - tdx.sys causing BSOD - Fixed!

Hope things work out

Regards

 

[tHeMarriedGuy]

Hi

Welcome to Seven Forums
Have a look at this SF Thread - tdx.sys causing BSOD - Fixed!

Hope things work out

Regards

Yeah, I checked that one out but couldn't figure out how to determine what was specifically causing it. I don't even know what type of wireless card I have--but I don't think it's made by Broadcom and without being able to see with certainty that the problem is with it, I don't want to download stuff from there.

 

[Lomai]

Could you post your system specifications? Name and make of your PC?
you could post a snip of your device manager by right-clicking my computer>Select Properties>Select Device Manager in the Left Pane>Expand the Network adapters so it lists the hardware interfaces

 

[tHeMarriedGuy]

Dell Inspiron 1525

Network adapters:
-Intel (R) Wireless WiFi Link 4965AGN
-Marvell Yukon 88E8040 PCI-E Fast Ethernet

 

[richc46]

Why work alone,
Post the dump here and the fourm will help you.
http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

 

[tHeMarriedGuy]

I thought I had posted it, but it looks like I had to save it as a .zip file rather than .zipx.

 

[Lomai]

Well you in good hands now with Richard on board.
If you need the drivers for your network card, go to this link and be sure to enter the correct details in on that page - where it asks for the platform and Marvell part number. Don't spend too much time on the photo of the lady on the page otherwise we may need a new nick for you tomorrow
Read through carefully and follow the prompts to download the driver (it's about 2MB in size)

Hope things work out..I have to turn in

Take care and regards

 

[richc46]

Wow a lot of dumps.

I looked at a small percentage and they all showed these drivers as the problem. Install up to date drivers and you should be ok. If problem persisist, submit new dump report.

Bckd.sys file description
Productname: ClientLibs
Description: bckd.sys
Company: Blue Coat Systems, Inc.

and

tdx.sys which requires special action.
This is the NetIO Legacy Transport Driver Interface (TDI) Support driver
http://www.computerhope.com/cgi-bin/process.pl?p=tdx.sys


If you need additional information. This is how you would obtain it.
How to Find Drivers
search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone - will help you search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- - if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads
To remove any left over driver remnants, especially from graphics cards, use driver sweeper http://www.guru3d.com/category/driversweeper/

Try doing an SFC to see if that helps correct the problem
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

It is also suggested that you uninstall any recently installed software as this is most likely the cause of the problem

TDX problems are often caused by the anti virus used, Please uninstall your current AV and try Microsoft Security Essentials at least for test purposes.


Thanks Lomai, you did an excellent job, rep given.

 

[richc46]

I have done further research and updated your report. Please be sure to check my post above, even if you have done so previously.

 

[tHeMarriedGuy]

tdx.sys which requires special action.
This is the NetIO Legacy Transport Driver Interface (TDI) Support driver
What is the tdx.sys file?

This link just took me to a page telling what tdx.sys is, not giving an updated driver.

 

[Lomai]

Use this link to update the driver for your network card

Marvell Support

Keep us posted on your results and regards

 

[richc46]

I did not give you a link for a
tdk driver because it is a MS driver and very rarely is that the actual cause of the BSOD. In fact after doing many BSODs a MS driver was never the cause. In my report I indicated that Special action should be taken and gave you some information regarding that driver eg, change your Anti Virus. It is my suggestion at this juncture not to uninstall and replace. Remove the bckd driver and try with MSE antivirus and let us know how it goes.

 

[tHeMarriedGuy]

I think removing the Blue Coat K9 driver fixed the problem. I'll let you know for sure later this evening (as to whether or not I've gotten a BSOD again).

 

[richc46]

If you read my first post, I think so too. Do not fool around with the MS drivers, I have never seen one be the cause of a BSOD. I wish you luck.

 

[tHeMarriedGuy]

It's been nearly 24 hours without another BSOD, so I think the problem is really fixed. Thanks so much, guys!

 

[richc46]

We are happy that it worked out.