BSOD while playing games

fatfriarg · 16 Jul 2013

Hi guys, I've been having this problem for the last few months where, whenever I try to play a game, after about 10-30mins I have a BSOD. This has so far happened to Borderlands 2, Assassins Creed 3, Far Cry 3 and various others. It has also done it a few times when trying to watch videos online. I have had various incidents where Windows Explorer will stop working or where other small things stop working (e.g. desktop gadgets). I have so far tried various things (disk degragmenting, full system virus scan and registry cleaning, turning off Avast) but to no avail. I am at my wit's end, as I can now barely do anything on my computer without serious problems. Any help would be great!!!
p.s. this is my first time posting here, so I'm not sure if there's anything I've done wrong in this post.
I've attached the necessarry .zip file

Arc · 16 Jul 2013

Hello fatfriarg.

You are highly overclocked.

Code:

CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3502

As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings. Also set the BIOS to default, too.
How To Clear CMOS (Reset BIOS)

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy.

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator
At least 30% extra is safe. Also let us know about the wattage of the PSU.

It seems that one BSOD is during scanning with Avast? Scan the system for possible virus infection with the following programs.

Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

Click on the Start button
Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
Select the “Startup” tab.
Deselect all items other than the antivirus.
Apply > OK
Accept then restart.

Let us know the results.

_____________________________________________________________________________________
BSOD ANALYSIS:

Code:

BugCheck 1A, {411, fffff6800000de48, 81d0000134eb6886, fffff8a016c4f501}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+6071 )

Followup: MachineOwner
-------------------------------------------------------------------------------------
BugCheck 3B, {c0000005, fffff960000b9d61, fffff88003dfddc0, 0}

Probably caused by : memory_corruption

Followup: memory_corruption
--------------------------------------------------------------------------------------
BugCheck C2, {b, fffff8a001a076d0, 69010b, fffff8a001a07d70}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+268 )

Followup: MachineOwner
-----------------------------------------------------------------------------------------
BugCheck 4E, {99, 1a8789, 2, 1a8088}

Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

Followup: MachineOwner
---------

x BlueRobot · 16 Jul 2013

Code:

BugCheck 1A, {411, fffff6800000de48, 81d0000134eb6886, fffff8a016c4f501}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+6071 )

Code:

Usual causes:  Device driver, memory, kernel

This bugcheck indicates that a PTE has become corrupt, a PTE is a mapping between a physical and virtual memory address stored in the page table.

Code:

2: kd> !pte fffff6800000de48
                                           VA 0000000001bc9000 <-- Virtual Address
PXE at FFFFF6FB7DBED000    PPE at FFFFF6FB7DA00000    PDE at FFFFF6FB40000068    PTE at FFFFF6800000DE48
Unable to get PXE FFFFF6FB7DBED000

Remove:

Code:

Start Menu\Programs\Advanced System Optimizer 3
Start Menu\Programs\Advanced System Optimizer 3\Backup and Recovery
Start Menu\Programs\Advanced System Optimizer 3\Common Problem Fixers
Start Menu\Programs\Advanced System Optimizer 3\Disk Tuneup
Start Menu\Programs\Advanced System Optimizer 3\Registry Tuneup
Start Menu\Programs\Advanced System Optimizer 3\Regular Maintenance
Start Menu\Programs\Advanced System Optimizer 3\Security and Privacy
Start Menu\Programs\Advanced System Optimizer 3\Windows Optimization

Removal Tool - Revo Uninstaller Pro - Uninstall Software, Remove Programs easily, Forced Uninstall, Leftovers Uninstaller

Windows 7 doesn't require any programs which make changes to the operating system and registry, these programs tend to cause problems by modifying and deleting files.

Registry Cleaner Tests - Why NOT To Use One!

Windows is a closed source system. Developers of registry cleaners do not have the core code of Windows 7 and are not working on definitive information, but rather they are going on past knowledge and experience. Automatic cleaners will usually have to do some guesswork.

Modifying registry keys incorrectly can cause Windows instability, or make Windows unbootable. No registry cleaner is completely safe and the potential is ever present to cause more problems than they claim to fix.

Registry cleaners cannot distinguish between good and bad. If you run a registry cleaner, it will delete all those keys which are obsolete and sitting idle; but in reality, those keys may well be needed by some programs or windows at a later time.

Windows 7 is much more efficient at managing the registry than previous Windows versions. If you run any other registry cleaner and do not know precisely what you are doing, you will have problems down the road. There are no gains to be had from using a registry cleaner and the risk is great.

Run Driver Verifier to scan for any corrupted drivers which may be causing problems, this program works by running various stress tests on drivers, in order to produce a BSOD which will locate the driver; run for least 24 hours:

Driver Verifier - Enable and Disable

Information

Additional Help - Using Driver Verifier to identify issues with Drivers

fatfriarg · 16 Jul 2013

Thanks guys, I'll get right on it.