BSOD with same bug check code third time in the last 2 weeks

[essenbe]

Let it run as long as you can. That is all the dump files are telling us.

 

[essenbe]

Adechi, if you haven't had any errors, stop. We'll try something else.

 

[Adechi]

Alright 22 passes with no errors, I'll stop it now.

 

[essenbe]

That's great, sort of. If you know what I mean. Please download some good software to monitor your CPU and Graphics temps. In your case they may be the same thing. I want you to run a couple of tests. Please try to run Furmark going by this tutorial. In your case do not check post FX. Your temps will go up really high and very fast. Monitor them constantly. If they get too high, stop the test. Run it until the temps quit rising and level out. Then stop the test. Please post a screenshot just before stopping the test. http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html. During the test watch for artifacts.

Does your SSD have a toolbox to tell you how well it is running? Please run Seatools on your mechanical drive. Use Seatools for DOS http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html#Part2. Read the instructions carefully. I am not sure how we are going to test the SSD.

 

[Adechi]

Yes the SSD has a toolbox, and I got HWmonitor for temperature monitoring. I'll do the Furmark tests tomorrow along with SeaTools.

 

[Adechi]

Alright I did the test and had no artifacts, not sure if these are the screenshots you want but here you go. The temperature screenshot is from around 95% through the test. Also I had another blue screen with a new bug code so here are the dump files.

 

[essenbe]

Was the BSOD during or immediately after the Furmark test?

This is what the dump file is saying

Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, fffff8000333641f, 1, 0}
Probably caused by : memory_corruption
[COLOR=red]Followup: memory_corruption[/COLOR]

fffff880`0429a2a0  fffff880`04159200Unable to load image \SystemRoot\system32\drivers\aswSnx.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswSnx.sys
[COLOR=red]*** ERROR: Module load completed but symbols could not be loaded for aswSnx.sys[/COLOR]
 aswSnx+0xe5200

That is your Avast. Please uninstall it from control panel an then run the Avast uninstall utility Avast Clear https://www.avast.com/uninstall-utility. Replace it with Microsoft Security Essentials (Microsoft Security Essentials - Microsoft Windows). Also do not run Malwarebytes real time protection. Use it as an on demand scanner. It is generally advisable to not run 2 AV programs at the same time. Although Avast and Malwarebytes are different types of programs, it can cause conflicts.

 

[essenbe]

Are you having issues with your sound? You are getting a ton of errors from SndVol.EXE which is the Windows sound control.

 

[Adechi]

The BSOD was actually before the test while I was playing Garry's Mod. I replaced Avast with MSE, but do I disable malicious website protection as well in MalwareBytes? Also one time whenever I would try to open the volume mixer or adjuster it would crash but I would be able to control it using my keyboards volume adjuster. Other than that no issues.

 

[essenbe]

Just disable real time protection with Malwarebytes. I think it may help. Some people run both, but it causes some big problems. Once we get everything straight, you can try it on real time again and see how it goes. As far as the sound, you had a ton of errors with that. It is the built in sound volume/mixer for Windows 7. So, I really don't have any idea what to do about it unless you have some other sound programs/hardware installed that may be conflicting with it.

Just understand. What I am doing now is trying everything I can to get rid of anything that may be causing a problem, so you can get your system stable. After we can get it stable, you can try whatever you want to. I would just suggest when that time comes, to try one thing at a time and give it plenty of time to test it. If something goes wrong, you will know what it is. If nothing goes wrong, you can add something else. So, at this point, my concern is to get you stable if I can, whatever it takes.

 

[Adechi]

I just had two BSODs today one with the same bug code as the time I was playing Garry's Mod a few days ago and another one with the 019 bug code, here are the dump files. Something is acting up again because for a few days it was fine.

 

[essenbe]

Same result, just different error codes.

Use !analyze -v to get detailed debugging information.
BugCheck 109, {a3a039d8a636c56b, b3b7465ef8b394c1, fffff80003336338, 1}
*** WARNING: Unable to verify checksum for win32k.sys
[COLOR=red]Probably caused by : memory_corruption[/COLOR]
Followup: memory_corruption

Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, fffff8000333641f, 1, 0}
*** WARNING: Unable to verify checksum for win32k.sys
[COLOR=red]Probably caused by : memory_corruption[/COLOR]
Followup: memory_corruption

Do you have backups of all of your files? And, do you have an extra hard drive or SSD we could use for a test?

 

[Adechi]

No backups, and I have another HDD where I keep all my Steam games.

 

[essenbe]

You need to backup your personal files and games to an external source. It looks like we are going to need to do a Repair install or a Clean Install. It would be best if you had another hard drive. That way we could do a clean install to that one and not bother your current install. Are you sure you have the latest Firmware to your SSD?

Did you build this computer? It keeps showing Memory errors, but you have tested the Memory more than enough. Have you been monitoring Temps? The only explanations I can come up with are the Hard drive, the Graphics, but your Graphics is on the CPU, or a bent CPU socket pin. It appears as though you have some corrupted System Files that the sfc scan does not pick up. The remedy for that would be a clean install. The hard Drive and corrupted system files can be 'lumped together' in my mind. Have you altered any system settings such as the page file or anything like that? I believe you said you had a tool Box for the SSD. Use it and run every test you can to make sure the SSD is working properly and make sure it has the latest Firmware on it. Alsi, I hope you are not overclocked. I believe we set optimized defaults in BIOS recently.

 

[Adechi]

Yes this is a custom built, no alterations of system settings and no overclocking. The SSD has the latest firmware and temps have been staying around 35-50 Celsius for the CPU. I'll back up my files and try the repair install.

 

[essenbe]

OK, just know that a repair install is about the last step before a clean install. You can also look at a system restore to a point before this started happening. http://www.sevenforums.com/tutorials/700-system-restore.html

http://www.sevenforums.com/tutorials/3413-repair-install.html