BSOD playing Counter Strike 1.6, sometimes random or in XBMC

[sizanx]

Hey,

Sometimes I get random BSOD's, it's not something that happens every day however it's getting irritating. The last time it happend was today in Counter Strike 1.6 with the "SYSTEM_SERVICE_EXCEPTION" error. So I followed your Verifier Driver tutorial and got 2 BSOD's with IRQL_NOT_LESS_OR_EQUAL caused by aswTdi.sys (Avast Driver)..

However I just installed Avast yesterday, and as you can see in my dmp files, I have had BSODs before with SYSTEM_SERVICE_EXCEPTION and others, so I don't think that's the main issue.

Sometimes I also get BSOD while watching a movie or something with XBMC, it happens randomly, but not often.

I have thought maybe it's the ATi/AMD GPU (some BSOD ref.), and I have been checking temps, it's about 60C - I have changed the thermal paste and cleaned it - but still sometimes BSOD. I have played a lot of BF3 without getting BSOD, and that's a heck a lot of more strain on the GPU than CS 1.6.

My own guess is the GPU drivers, but I have been updating regularly

Btw the System Health Report says "Atheros AR9285 Wireless Network Adapter" is disabled, and that's true, I have disabled it.

I hope you guys can help

-----------------------------
System Info:
Windows 7 X64 Enterprise
Install date: 28-08-2011
Intel Core i5 2500k
Zotac Z68 ITX
2x 4GB Corsair Vengeance DDR3 RAM
Club 3D Radeon HD4980
System Disk: Crucial m4 128GB
Storage: 2x500GB WD, 1TB WD - 7200rpm

The hardware is from august 2011, except for SSD (june 2011), storage (2009,2010) and GPU (2009).

 

[JMH]

sizanx,

These crashes were caused by memory corruption/exception (Cx05) 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-7 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.

 

[zigzag3143]

Caused by pool corruption, usually a driver (probably your Avast)

Avast can be a contributing cause of BSOD'S . Please remove and replace with Microsoft Security Essentials AT LEAST TO TEST


http://files.avast.com/files/eng/aswclear5.exe

Microsoft Security Essentials - Free Antivirus for Windows

 

[sizanx]

thanks for the replies, I will follow your advice. I'll run 7 passes of memtest tomorrow

 

[zigzag3143]

thanks for the replies, I will follow your advice. I'll run 7 passes of memtest tomorrow

Let us know if you need help.

 

[sizanx]

I did 7 passes with memtest, no errors.

However I uninstalled the AMD/ATi Display drivers, then used driver sweeper to clean the rest and reinstalled. Haven't had a BSOD since, so maybe I hit the sweet spot

 

[zigzag3143]

I did 7 passes with memtest, no errors.

However I uninstalled the AMD/ATi Display drivers, then used driver sweeper to clean the rest and reinstalled. Haven't had a BSOD since, so maybe I hit the sweet spot

Good news and fingers crossed. Plus you know your ram is ok.