Multiple code errors, BSOD while gaming/netflix/idle...

[redsennacy2189]

This has been happening for the past four months now to no avail. I get BSOD about every 1-4 days, often with different messages, but the average as of right now is 1e.

Built this system in October 2010. I've always had BSOD problems, but with work getting in the way and not really using my comp for a year, I wasn't able to tackle the problem. Now, while playing League of Legends it often crashes, or any other game (every 1-2 days) or when I'm just streaming something on netflix. I've had times when it'll blue screen while it's been at the log in screen. I'm baffled.

I've ran countless Memtest86's (7 pass minimum), seaDOS tool, disk check, sfc /scannow... everything checks out. I've reformatted my computer most recently (it's been often) around mid January.

Around that time, I decided that maybe it was my power supply, ram or video card, so I bought all new stuff. BSOD kept happening, reran tests, still checked out. I've checked and double checked all my drivers. I really am at a loss.

Went on Asus' forums for my motherboard, since RAM wasn't on compatibility list and asked about it. They said it should be fine if it passes memtest. Cool n' Quiet is also disabled on my BIOS, as they said that is also a frequent BSOD antagonist.

No original OS.
Windows 7 full retail, reformatted in January.
CPU, HDD, MoBo, October 2010
PSU, RAM, GPU, November 2011

Specs in profile, but just for reference...
MoBo: ASUS M4A88T-M USB 3.0
PSU: Corsair TX650W
CPU: AMD Phenom II 3.1 GHz
HDD: Seagate Barracuda 1Tb 7200.12
RAM: G. Skill Ripjaw series, DDR3 1600 8Gb (4Gb x 2)
GPU: Powercolor Radeon HD 6850 1 Gb
Avira Anti Virus, Malwarebytes as defense software.

I hope I attached the .zip files correctly.

Thank you!

 

[zigzag3143]

I would run driver verifier to find which driver/drivers are the culprits.

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).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

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 "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 (an estimate on my part).

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.

 

[Maguscreed]

crashes are all over the place.
At this point in time I'm going to suggest checking your memory (at least 5 passes)
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

 

[zigzag3143]

crashes are all over the place.
At this point in time I'm going to suggest checking your memory (at least 5 passes)
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

He already did


"I've ran countless Memtest86's (7 pass minimum), seaDOS tool, disk check, sfc /scannow... everything checks out. I've reformatted my computer most recently (it's been often) around mid January."

 

[Maguscreed]

The only readable crashes I have there are all memory management 1a.
Could this be an xmp problem?

 

[zigzag3143]

@MC
He has Nine different BCC, and has passed memtest. Either it is further hardware, or he has a corrupt driver hence the driver verifier.


@redsennacy2189

This driver may be suspect. (aj08l6wj.SYS)

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

http://www.malwarebytes.org/products

 

[Maguscreed]

Sorry zig I never meant to state your analysis was wrong.

I actually do recall seeing 2 2012 dated drivers I wasn't familiar with.

 

[zigzag3143]

Sorry zig I never meant to state your analysis was wrong.

I actually do recall seeing 2 2012 dated drivers I wasn't familiar with.

No worries. I can always use an extra pair of eyes.

Thanks

 

[redsennacy2189]

what kills me is that i built my ex-bf an identical computer at the same time. He also had BSOD but it resolved when he bought new ram and PSU. It's what prompted me to do the same for mine, but I still have issues.

Yes, I had already ran mem test about 4, different slots, times (7-8 passes each). They all came back with no problem.

Malwarebytes, ironically, i updated and ran right after I posted my results. All clean. As well as Avira's scan. Since I have restarted the computer already, I'll go ahead and run another full scan and post the end results here. In the mean time, my comp is running under the recommended stress test.

I really, really, really hope you guys can help me figure this out. My codes are all over the place, and every time I think I fixed it, another BSOD will happen about a week later. Funny thing is, I've crashed a lot more than there are minidumps.

 

[zigzag3143]

If the ram is good, the next step is driver verifier. It should identify the driver/drivers that are causing the crashes.

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).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

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 "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 (an estimate on my part).

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.

 

[redsennacy2189]

Hm. So maybe I spoke too soon. I restarted the comp for the driver stress test, my comp apparently wouldn't start. I came home to see the windows repair screen, I'm a little unsure of what to do

Try in safe mode?

 

[redsennacy2189]

Yeah. Windows won't load. I keep getting blue screens. Not quite sure what to do. It keeps launching system repair.

 

[zigzag3143]

Yeah. Windows won't load. I keep getting blue screens. Not quite sure what to do. It keeps launching system repair.

Did you have verifier turned on when it crashed?

Have you tried booting into safe mode (F8)?

Have you tried booting from the win 7 DVD?

 

[redsennacy2189]

Yes to all. Verifier was on, windows wouldn't boot, even in safe mode. I tried windows system restore, it refused. I am not opposed to reformatting

 

[zigzag3143]

Yes to all. Verifier was on, windows wouldn't boot, even in safe mode. I tried windows system restore, it refused. I am not opposed to reformatting

Reformatting may be the fastest way to get going again.

 

[redsennacy2189]

Alrighty. I reformatted last night. I've blue screened already twice. Once, just 10 minutes ago, was Memory_management. The other was unknown. I'll upload the .zip files.

I'm starting to doubt my RAM. Maybe it is the culprit after all? I'll run memtest again. Should I try every slot/ram combo again? I was worried that my MoBo and RAM were not compatible, I asked on Asus' forum website and they said that as long as it passes memtest, it should be alright.

Should I be worried it's a mobo issue? They did mention that my board was a fairly old model and that it may have crapped out on me (I'm still under warranty).

 

[zigzag3143]

Alrighty. I reformatted last night. I've blue screened already twice. Once, just 10 minutes ago, was Memory_management. The other was unknown. I'll upload the .zip files.

I'm starting to doubt my RAM. Maybe it is the culprit after all? I'll run memtest again. Should I try every slot/ram combo again? I was worried that my MoBo and RAM were not compatible, I asked on Asus' forum website and they said that as long as it passes memtest, it should be alright.

Should I be worried it's a mobo issue? They did mention that my board was a fairly old model and that it may have crapped out on me (I'm still under warranty).

Most of these are either RAM, or a driver. Since you re-installed (with format right?) it is probably not a driver (if you didnt install anything not on the win 7 dvd) so I would retest ram every stick one at a time first. When you find a good stick try it in every slot. If any slot fails its the slot.

 

[Maguscreed]

To begin with you should test your ram in the configuration you are currently using it.

 

[redsennacy2189]

I'll bring up an interesting point then, if it is the slot. My current set up is
b1 b2 a1 a2
[cpu] x l x l

x being ram placement, the lines being blank slots. When I tried to move my ram to both the B slots, the computer wouldn't even get past the initial mobo screen. It would freeze or just go blank. Bad slots?

I'll rerun mem test tonight in it's current slots. If it's mobo, I still have it under warranty at least.

 

[Maguscreed]

I'll bring up an interesting point then, if it is the slot. My current set up is
b1 b2 a1 a2
[cpu] x l x l

x being ram placement, the lines being blank slots. When I tried to move my ram to both the B slots, the computer wouldn't even get past the initial mobo screen. It would freeze or just go blank. Bad slots?

I'll rerun mem test tonight in it's current slots. If it's mobo, I still have it under warranty at least.

Well if nothing else it does with certainty outline there is a hardware level problem going on here. If you have it under warranty I might try to trade it out. You may also try writing them at this point as sometimes they have a special bios update or patch of some sort they only give out to people experiencing the specific problem. While this is unlikely, it is possible, and regardless it would seem contacting the manufacturer for the next step is the way to go now.