Intermittant BSOD possibly related to wireless adapter

Here's my most recent error (zipped SF diagnostic folder attached):

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: 1e
BCP1: 0000000000000000
BCP2: 0000000000000000
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\073112-24195-01.dmp
C:\Users\Administrator\AppData\Local\Temp\WER-45037-0.sysdata.xml

Here's the image of my cpu-z outputs and SF diagnostic folder.

Seven Forums.zip

I don't know much about windows, but using the program bluescreen view and google my guess would be that my linksys wireless adapter WUSB600N driver is causing the problem, and if that isn't my second guess would be my recently installed ram, despite many passes in memtest86+. The first bluescreen .dmp (072812-20170-01.dmp modified on the 28th) can be ignored as I am pretty sure the hal.dll BSOD was the result of me stress testing an unstable overclock.

I updated the drivers for the wireless adapter from 3.0.1.0 to 3.0.10.0 (I hope that is an upgrade heh, they did have different dates) and haven't seen a bsod yet, but thats only been an hour or so. I really have no clue if I did the right thing or not, but can't hurt I suppose.

If anyone with more knowledge about this kind of thing can give me more info or tell me if I may have fixed the problem let me know. I'll update this thread depending on whether or not I get another BSOD. If I go a few day without one I'll consider the problem solved and delete the thread.

Thanks in advance!

UPDATE:
Ok the driver definately didn't help. Had the exact same bsod as last time.

Heres the .dmp:
073112-41901-01.zip

Any help would be greatly appreciated. I'm at a loss, I'll probably run a memtest again for an extended period.

Hi,

your bios is from 2009 and needs updating:

BiosVersion = F2c
BiosReleaseDate = 05/22/2009

Download:
GIGABYTE - Motherboard - Socket AM3 - GA-MA770T-UD3P (rev. 1.4)

Realtek driver needs updating:

RTKVHD64.sys Tue Jan 20 06:12:51 2009

You also have this old mouse driver:

Amfltx64.sys Mon Oct 15 04:37:21 2007

Please update or uninstall.

Speedfan needs updating too:

You can find updates in our update section.

It does like look like however that the bsod was caused by aswSnx.SYS which is avast Virtualization Driver. Try unstalling avast and using MSE:

Microsoft Security Essentials - Free Antivirus for Windows

Ok so far all I've done is update the bios, which went ok, my audio doesn't detect any output now however, which is probably a result of the out of date realtek driver. I was going to update that next when I got this BSOD:

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: a
BCP1: FFFFF800033A553C
BCP2: 0000000000000002
BCP3: 0000000000000008
BCP4: FFFFF800033A553C
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\073112-32307-01.dmp
C:\Windows\Temp\WER-48625-0.sysdata.xml

073112-32307-01.zip

So I'll probably skip ahead and uninstall Avast now if its the most likely culprit and then continue with the driver updates.

Also it appears that the mouse driver you mentioned is for an old mouse I no longer use because it isn't listed under my current mouse drivers in device manager. Is it safe to delete the file, or should I just change it from a .sys file to a .BAK file as per this thread: These recurrently BSOD are getting me crazy. Help Please - Windows 7 Forums Or is there a better method to uninstall it.

Alternatively, should I just update it even though I don't use the mouse anymore? Heck I don't ever remember having the mouse they show.
http://www.a4tech.com/f/index.aspx

OK I think I got rid of the old mouse drivers fully using this method.

Remove Old Drivers After Upgrading to New Hardware - How-To Geek

Same again, avast driver caused it. Also are you using the latest updated firefox? If you find the machine still blue screens then please run this app: Memtest86+ - Advanced Memory Diagnostic Tool test only one stick of ram at a time (physically remove the others) so you know which, if any, errors out.

Thanks for all your help so far! That last BSOD was before I had uninstalled avast so that makes sense. And I've done a lot of memtests86+ passes already but I haven't tried them one at a time, so I'll have to try that. How many passes should I do?

Now I've done everything you mentioned in that first reply and it seemed like things were okay at first. Then I got this BSOD:

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: 1e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF800033CC435
BCP3: 0000000000000000
BCP4: FFFFFFFFFFFFFFFF
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\073112-36161-01.dmp
C:\Users\Administrator\AppData\Local\Temp\WER-1413665-0.sysdata.xml

073112-36161-01.zip

If it matters, after the BSOD induced restart my usb wireless adapter wouldn't work until I rolled back the drivers to 3.0.1.0.

Also is there a guide or program that can help me figure these errors out on my own? I feel like I'm being a pain in the butt, and teach a man to fish and all that. Thanks so much for your help though, I really appreciate it.

Edit: I'm using firefox 14.0.1 and it says its up to date. If I really can't fix this problem I guess I might just resort to a full reinstallation of windows 7.

Hi,
yup if you could run memtest for 7/8 passes on each stick. Running memtest on all sticks won't always reveal an error this is one of the reasons why it must be done on singular sticks. It goes look like we could be looking at a memory issue but please run the tests and we'll go from there.

Still testing the ram, done the first two sticks to ten passes. I have a feeling that this post from another forum may be very relevant to me since I have a c2 phenom II.

Hardware Canucks - View Single Post - Trouble Shooting Ram

Still not going to mess with any settings until I rule out a bad module.