Random BSODs while playing WoW/TF2, browsing internet.

[Tenack]

I use a World of Warcraft Steelseries gaming mouse, a Logitech G110 gaming keyboard, and a X12 turtle beach headset. I'm at school right now so when i get home tonight I'll load the dumps I got last night after running driver verifier and follow your directions.

 

[Tenack]

heres the dump files. been hell trying to go 2 minutes without a BSOD

 

[writhziden]

That crash was due to Verifier, but it did not point to a driver. It may have just been a fluke due to Verifier. Disable Verifier and see if stability has increased with the USB troubleshooting steps you did.

 

[Tenack]

I disable Verifier by deleting the existing settings, correct? That's what I did anyway. So I haven't really seen any improvements. I tried updating my Chipset from the link you provided and I tried unplugging it and holding the power button for 30secs. Nothing seems better. Got a MEMORY MANAGEMENT BSOD a second ago, and Perfmon still says devices are disabled and/or aren't working properly. WAN Miniport(IKEv2) and AODDriver4.01 are specified. It says 2 plug in play devices aren't configured correctly and that there is 1 Network configuration fail count.

Here are the dmp files

 

[writhziden]

Still pointing toward USB devices. Remove the headset from the system. See if it is more stable.

Do you have a regular keyboard and mouse you could use in place of the two gaming versions you are currently using?

Disable Verifier by running an http://www.sevenforums.com/tutorials/783-elevated-command-prompt.html and typing

verifier /reset​

 

[Tenack]

I don't

 

[writhziden]

The best way to determine which of the three is causing the USB crashes is to remove all three, replace all USB devices with only those necessary (standard mouse and keyboard) and see if the system is more stable.

Without that option, you will just have to try without the headset and hope it was the culprit.

 

[Tenack]

I removed the headset to see if it was more stable. I got a driver is not unstacked buffered error or something like that, it flashed by too quickly for me to see it.

Here's the dmp.

 

[Tenack]

I downloaded whocrashed and ran it. It says that my hardware isn't the issue, but there are third party drivers causing my problems. It just doesn't point out which ones. I have a feeling it has something to do with my Network driver(WHICH I HAVE UPDATED FROM REALTEKS SITE LIKE 10 TIMES!!!!) and my Sound driver(for some reason I just have two HIGH DEFINITION SOUND DEVICE drivers in my device manager(i dont understand why), and possibly this AODDriver that keeps showing up in perfmon report. I'm just glad that this isn't a hardware error. I feel like we may be getting closer to fixing the problem.

 

[RxDawg]

I've thought of something. Any chance all these BSOD's could be related to running 32bit programs/drivers/whatever in 64bit Windows systems? If that's the case, is there a better way to run 32 bit software? I see a run in compatability mode but I'm unfamiliar with how it works exactly.

The reason I say this is I discovered there is a 64bit WoW client that I didn't know about. I downloaded it and have been running it without any problems so far. But it's only been a few days and I haven't shut down my computer that entire time yet (I seem to have more trouble after cold starts). So I'm skeptical that things will stay good.

 

[zigzag3143]

I downloaded whocrashed and ran it. It says that my hardware isn't the issue, but there are third party drivers causing my problems. It just doesn't point out which ones. I have a feeling it has something to do with my Network driver(WHICH I HAVE UPDATED FROM REALTEKS SITE LIKE 10 TIMES!!!!) and my Sound driver(for some reason I just have two HIGH DEFINITION SOUND DEVICE drivers in my device manager(i dont understand why), and possibly this AODDriver that keeps showing up in perfmon report. I'm just glad that this isn't a hardware error. I feel like we may be getting closer to fixing the problem.

I am a big fan of Nir Sofer's work, BUT blueScreenView more often than not, doesn't point out the correct causes. Similarly Who crashed is even worse.

I prefer to use WinDbg (the Windows Debugging Tools) to read the memory dumps. It is the Gold standard for those of us that do this and often will give us the answer by itself. (we don't need the full jcgriff2 report each time).

Just to be sure please download malwarebytes and run it

Please download the free version of Malwarebytes.
Update it immediately.
Do a full system scan
Let us know the results at the end.

Malwarebytes : Download free malware, virus and spyware tools to get your computer back in shape!


DRIVER_OVERRAN_STACK_BUFFER (f7)
A driver has overrun a stack-based buffer. This overrun could potentially
allow a malicious user to gain control of this machine.
DESCRIPTION
A driver overran a stack-based buffer (or local variable) in a way that would
have overwritten the function's return address and jumped back to an arbitrary
address when the function returned. This is the classic "buffer overrun"
hacking attack and the system has been brought down to prevent a malicious user
from gaining complete control of it.


And yes it could be WOW.

PROCESS_NAME: Wow-64.exe

 

[Tenack]

I've been running the 64 bit client for a while now. My problems still persist RxDawg.

@zigzag: what do you mean it could be WoW.exe? It still crashes sometimes at the desktop or in Firefox.

 

[zigzag3143]

I've been running the 64 bit client for a while now. My problems still persist RxDawg.

@zigzag: what do you mean it could be WoW.exe? It still crashes sometimes at the desktop or in Firefox.

Did you run Malwarebytes

 

[Tenack]

I've ran Malwarebytes plenty of times in the past and it never really seemed to get anything. Always had zero results. I'm running it again right now.

Right now I'm using my other HDD and still having the same BSOD's. It seems I can't escape it no matter which HDD I'm using. Whocrashed again points to third party drivers but I swear I've tried updating everything(in safe mode, the whole nine yards).

I've tried reformatting/reinstalling too. I just don't get why the hell it has to be this huge of a deal. I know plenty of people that NEVER have problems :/

Anyway here is the latest dmp. I swapped HDDs to see if things would improve, and they seemed to....but when I booted up this morning I got a BSOD pretty quickly after browsing the net and playing a bit of WoW.

 

[Tenack]

no malicious items were detected.

 

[Tenack]

Had another BugCode USB Driver error. Seriously, there has to be some solutions for this.

 

[Tenack]

So, my monitor started acting funny. Displaying green screens and red vertical lines. then it wouldn't turn on at all, so I plugged my computer in to my tv while it was still on and the display was normal. I haven't had an error since.

Is it possible that my monitor was causing the problem the entire time because it was dying?

 

[zigzag3143]

I've ran Malwarebytes plenty of times in the past and it never really seemed to get anything. Always had zero results. I'm running it again right now.

Right now I'm using my other HDD and still having the same BSOD's. It seems I can't escape it no matter which HDD I'm using. Whocrashed again points to third party drivers but I swear I've tried updating everything(in safe mode, the whole nine yards).

I've tried reformatting/reinstalling too. I just don't get why the hell it has to be this huge of a deal. I know plenty of people that NEVER have problems :/

Anyway here is the latest dmp. I swapped HDDs to see if things would improve, and they seemed to....but when I booted up this morning I got a BSOD pretty quickly after browsing the net and playing a bit of WoW.

These crashes were caused by memory corruption/exception (probably a driver).
Please run these two tests to verify your memory and find which driver is causing the problem.

* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have raid update its Driver.



Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



Driver verifier

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

 

[RxDawg]

followup - Yep, my 64bit WoW client crashed too. But I also crash when surfing the web or doing pretty much any other mundane things on the PC including just being idle. I ordered a new motherboard yesterday. I'm going to try replacing it... If that doesn't fix it then I think I'm getting rid of my PC and starting over.

P.S. That was an interesting note about the monitor.

 

[Tenack]

zigzag, I appreciate your help, but I've already ran driver verifier and memtest. Writh ran me through those steps before, and we just ended up with unknown drivers causing the problem. Keyword is unknown.

I haven't had a BSOD since I switched monitors, but now when playing WoW my screen will just randomly turn black and the computer will still run.