BSOD playing Team Fortress 2

[Alfy]

At first I thought it was because my laptop was overheating, but I lifted the laptop so that the air flows out better and still had a BSOD. Any help is appreciated.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: d1
BCP1: FFFFF88009187000
BCP2: 0000000000000002
BCP3: 0000000000000000
BCP4: FFFFF88010219254
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\072612-17986-01.dmp
C:\Users\Albert\AppData\Local\Temp\WER-35459-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\windows\system32\en-US\erofflps.txt

-Alfy

 

[richc46]

Welcome
This driver appears to be the cause of your BSODs. Update the driver and report back
e22w7x64.sys


Product:
Killer e2200 PCI-E Gigabit Ethernet ControllerCompany: Qualcomm Atheros, Inc.Description: Killer e2200 PCI-E Gigabit Ethernet ControllerVersion: 8.0.2.31 *1MD5: 19A1E658E858CB93CCA526438086881E *1Size: 161616 *1Directory: %SYSDIR%\DRIVERS\e22w7x64.sysOperating System: Windows 7

Update the driver and report back.

 

[Alfy]

Thanks for the fast response. My laptop is a new model by MSI and it's not listed on the program. I went ahead and downloaded an updated driver on a different website and will let you know if the BSOD still comes.

 

[richc46]

I hope that you dont get anymore BSODs

 

[Alfy]

The BSOD was solved for a couple of days, which was nice. But another one came up today when plugging in an ethernet cord and a 2nd monitor to my laptop.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: d1
BCP1: 0000000000000004
BCP2: 0000000000000002
BCP3: 0000000000000001
BCP4: FFFFF8801119E11B
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\072912-16598-01.dmp
C:\Users\Albert\AppData\Local\Temp\WER-22682-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\windows\system32\en-US\erofflps.txt

 

[richc46]

Post again tomorrow to remind me, Im not at my computer and dont have the software to read your files.

 

[Alfy]

Reposting as requested. Thanks in advance.

 

[richc46]

The reports indicate the same driver as the problem
Run an anti virus scan and download and run a scan with Malarebytes
e22w7x64.sys - What is the e22w7x64.sys ?
The above article indicates it may be a virus.

 

[Alfy]

Hmm... it's odd that it would be a virus. It's a default program that came with the laptop when I bought it. If I disable it, my internet is automatically disconnected.

 

[richc46]

Yes, but a virus can hide in there. To date, I maintain that this driver is the problem. You say updating did not help We have a difference of opinion, which mus be settled if we want to solve this thing. A virus is a possible answer.

 

[Alfy]

I did a McAfee anti-virus full scan, as well as a Malware Bytes full scan, and nothing came up with either. Since it is a new program, there might be a future driver that will prevent the blue screen (just an assumption I came up with).

 

[richc46]

I can feel your frustration and am sorry. I must go by the reports, which are rarely consistent, but are consistent in your case. They all indicate that driver as the problem. See if you can roll back, via device manager, then click on the driver description. Make a system restore point first.
The dates on the driver are all very current early 2012. Possibly there was an older driver that worked better before that date.

 

[Alfy]

This laptop is less than 2 months old, and this model for this computer came out a couple of months ago, so unfortunately there are no roll back drivers that I can rely on for this driver (its grayed out). I will look for another version for this driver online, since I know this is the problem. Thanks for your help (again)!

 

[richc46]

Lets make a test. Can you uninstall the driver (you lose internet) and use the computer for a while, lets see if you BSOD.

 

[Alfy]

I could, but the BSODs seem to come up very randomly, as in only once every couple of days, or once a week. The first few times just happened to be when I was playing TF2, but that obviously isn't the case so I can't duplicate the BSOD. I need my internet to do my classwork (taking a summer class), so it could be a while before I could verify that the BSODs do happen from the driver via this method. And I fully trust that the problem is from the driver you specified and will do some additional research to see if others get this problem. With the information you given me, I might be able to find a different driver/alternate solution to this problem.

 

[richc46]

Do you know how to get to device manager?
Once there make sure no driver has a small yellow mark next to it, especially network adaptors.

 

[Alfy]

No I know how to get to device manager. I have had driver problems that I fixed myself before. It says its up to date and is working properly.

 

[richc46]

So frustrating for us both. Lets see if you work with a clean boot will the BSODs come back. Set up a clean boot and see if you have problems. If you do not, the problem is caused by a conflict with that driver and other applications. Worth a shot, I think.
http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html

 

[Alfy]

Okay I will try this. Thanks for the advice and will report if anymore come after this.

 

[richc46]

Usually the reports just give clues and we have to use our experience to get to the cause. In your case they are all giving the answer, but the solution does not seem to work. The clean boot will show if there are conflicts between the driver and other software. If we find that we got this solved. We have to hope that in clean boot there are not BSODs. Use the clean boot until you get a BSOD or you are sure you are good and there will be no problems.