Random BSODs playing WoW, error 0x1000007e, 0x00000050, 0x0000003b

I'm experiencing random BSOD crashes while playing World of Warcraft (and, sometimes Skyrim). The BSOD does not always happen -- more often, the game itself will just crash to desktop with an error #132 message. If you're interested in reading the crash reports from WoW's client, I can post them here or you can read them on the thread I created on their Tech Support forums: ERROR #132 Fatal exception! Crashes - Forums - World of Warcraft

The BSOD's are a little less frequent.

I've attached a zip file as instructed in the sticky.

Thanks in advance for your help!

Code:

BugCheck 1000007E, {ffffffffc0000005, fffff880048f8e81, fffff88005dc04e8, fffff88005dbfd40}

Probably caused by : atikmdag.sys ( atikmdag+a4e81 )

Code:

Usual causes:  Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control

Code:

2: kd> lmvm atikmdag
start             end                 module name
fffff880`04854000 fffff880`052dd000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        Fri Sep 28 03:14:57 2012 (50650821)
    CheckSum:         00A3EAAC
    ImageSize:        00A89000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

The latest driver seems to be dated as 3rd December 2012, please update:

• Latest AMD Catalyst Video Driver for Windows 7

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

I followed your instructions, but am now unable to access the AMD VISION Engine Control center. I get this message (attached image).

Have you reinstalled the driver?

-When I uninstalled the driver in Device Manager, I checked the box for "delete the driver software for this device."
-When I restarted my computer after that, I got a notification in the taskbar saying "Installing device driver software." I let it finish. It asked me if I wanted to restart now or later, i said now.
-After that restart, I ran Device Sweeper and restarted again.
-This time, the notification in the taskbar did not appear
-I installed the "AMD Catalyst 12.11 Beta11 Driver for Windows® 8, Windows 7 and Windows Vista® - with .NET 4 Support" which I had previously downloaded and placed on the desktop.
-During this install, I got a message saying that it finished, but that warnings occurred. I clicked "View error log" and got this:

I've resolved the error message problem with getting into AMD CCC.
I reinstalled Microsoft .NET Framework 4.0, then I uninstalled AMD through Control Panel. Before I rebooted, I ran Drive Sweeper, then downloaded the 12.11 Beta11 Driver.
I can now access CCC fine.

It looks like the driver was actually updated today, so I'm in the process of updating it again.
I'll post again if I continue to have issues after this. Thanks for your help so far.

Okay that's good to know, hopefully you won't have any further problems.

Unfortunately, my problems have returned. I had my first BSOD since the update just now. I have also been experiencing a lot of temporary freezing. Everything will freeze for a minute or so, then go back to normal.

This is all while having Firefox (playing a streaming radio station), and WoW open.

I've attached a new Zip file.

Code:

BugCheck 50, {fffff8b59e2a95f8, 0, fffff88003f3dffb, 5}

Could not read faulting driver name
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+ab )

Code:

Usual causes:  Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus,  Device driver, NTFS corruption, BIOS

Memory:

• RAM - Test with Memtest86+

Run Memtest86+ for least 9-10 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.