BSOD Playing Dragon Age after reinstall of Windows 7

Long story short.. Had to reinstall my OS after getting a nasty virus over a year ago. After that point I would get BSOD while playing games such as Skyrim and Dragon Age. These were games I had no problem with before the reinstall.
At that point I sought help on here and other forums. I honestly just gave up finally and just played other games that did not cause BSOD.

Yesterday I decided to give it another try and I reinstalled windows again. I reinstalled Dragon Age this morning and was able to play a few hours until I had a BSOD.
I am fairly sure I got all the correct drivers back in order after the reinstall. Any help would be great.

Ive attached the file from the SF Diag Tool.

Code:

BugCheck BE, {2051f, 90f000013a555005, fffff88002f22cd0, a}

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

Code:

Usual causes:  Device driver, Memory

A driver has attempted to write to a read-only memory, this could also be due to outdated firmware.

Code:

0: kd> lmvm atikmpag
start             end                 module name
fffff880`06c00000 fffff880`06c8d000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Wed Dec 19 19:32:55 2012 (50D21667)
    CheckSum:         00095A98
    ImageSize:        0008D000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

• AMD Graphics Drivers & Software

1. Download Driver
2. Start Type: Device Manager
3. Expand Display Adapters
4. Right-Click Driver Name, Uninstall
5. Reboot
6. Run Driver Sweeper
7. Reboot
8. Install Downloaded Driver

Driver Sweeper will scan for any left over files from the old driver, old driver files can cause conflicts with new driver installations. Create a System Restore point beforehand, in case any problems or issues arise.

Driver Sweeper:

• Drivers - Clean Left over Files after Uninstalling

Remove:

Code:

Start Menu\Programs\AVG

AVG is known to cause BSODs, it's best to remove this program using the official AVG Removal Tool.

Install and perform full scans with:

• Malwarebytes : Free anti-malware download
• Microsoft Security Essentials | Protect against viruses, spyware, and other malware

   Information

Remember to install the free version of Malwarebytes not the free trail; untick the free trial box during installation. MSE is the most lightweight and compatible with the Windows 7 operating system

You can also view this thread for a complete free and lightweight security protection combination:

• Good and Free system security combination.

All right finally had a chance to do everything you said BlueRobot. Was able to get a few hours of game play in and then I had a CTD of Dragon Age. I guess that's better than a BSOD though.

Looking through the Event Viewer I found Event 1000 Application Error with the following info:

Faulting application name: DAOrigins.exe, version: 1.5.13263.0, time stamp: 0x4eb1a54c
Faulting module name: DAOrigins.exe, version: 1.5.13263.0, time stamp: 0x4eb1a54c
Exception code: 0xc0000005
Fault offset: 0x00623389
Faulting process id: 0xa10
Faulting application start time: 0x01ce3c6ce7a1b6b3
Faulting application path: C:\Program Files (x86)\Dragon Age\bin_ship\DAOrigins.exe
Faulting module path: C:\Program Files (x86)\Dragon Age\bin_ship\DAOrigins.exe
Report Id: 3b0710d3-a861-11e2-a73a-842b2bbbbf67

Any ideas? Thanks very much for your help so far.

0xc0000005 is usually linked to drivers referencing invalid or non-existent memory addresses, which also could be corrupted. Poorly written drivers can also cause this problem.

What were the results of the scans? Did you update the driver? Remove AVG?

Do you have any ideas on how I could fix this?

Yes, read post #1.

I did every thing you said to do in your first response. Removed AVG, uninstalled the diver, ran driver sweeper, reinstalled the driver, installed and scanned with Malwarebytes and Microsoft Security Essentials. Neither found anything.

• RAM - Test with Memtest86+

Run Memtest86+ for least 7-9 passes, and preferably overnight as it can take a while to fully complete.

Test each RAM stick individually, if an error is found then move the same RAM stick into the next DIMM slot and test again, if errors are found for the same RAM stick in every available slot then you have a faulty RAM module. On the other hand, if no errors are found in the next slot or the other slots for the same RAM module, then you have a faulty DIMM slot.

Test each RAM stick and every motherboard DIMM slot available.

Arc said:

No code has to be inserted here. It is a RAM, a bad RAM.

But if you have got a result like that:
No code has to be inserted here. It is a motherboard issue. The particular slot is bad.