BSOD Alt+Tab'ing between XCOM and Chrome

cjacobson22

New member
Local time
9:04 AM
Messages
4
My computer has been BSOD'ing quite a bit lately. This particular BSOD happened when I Alt+Tab'ed between XCOM and Chrome, which was playing Pandora. I don't have a clue how to fix the problem so all help is appreciated!

Thank in advance
 

My Computer My Computer

Computer type
PC/Desktop
Computer Manufacturer/Model Number
custom build
OS
Windows 7 Home Premium 64-bit OEM
CPU
AMD FX-4170 Quad-Core 4.20 GHz
Motherboard
GIGABYTE GA-970A-D3 AM3+
Memory
Mushkin Enhanced Silverline 16GB (2 x 8GB) SDRAM DDR3 1333
Graphics Card(s)
SAPPHIRE Radeon HD 6850 1GB 256-bit GDDR5
Hard Drives
HGST Deskstar 7K1000.c 0F10383 1TB 7200 RPM 32MB Cache
Antivirus
Malwarebytes
Browser
Chrome
Welcome to the forums cjacobson22,

Code:
[COLOR="Red"]BugCheck 3B[/COLOR], {[COLOR="SeaGreen"]c0000005[/COLOR], fffff8800418e986, fffff880038e5bc0, 0}

Probably caused by : dxgmms1.sys ( dxgmms1!VidMmDestroyAllocation+46 )

Code:
Usual causes:  System service, Device driver, graphics driver, memory

Code:
2: kd> [COLOR="SeaGreen"]lmvm atikmpag[/COLOR]
start             end                 module name
fffff880`03a9e000 fffff880`03b32000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        [COLOR="Red"]Fri Mar 29 01:09:45 2013[/COLOR] (5154E9D9)
    CheckSum:         00091A60
    ImageSize:        00094000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Your graphics card drivers indicate to be a possible cause, please update to the latest WHQL version, and follow these steps:
WHQL
Release Date: April 24th 2013
Version: 13.4
In Device Manager: 12.104
  1. Download Driver
  2. Start :orb: 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:
Install and perform full scans with:
   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:
 

My Computer My Computer

Computer type
Laptop
After following the steps you provided, I had another BSOD. This time both Chrome, running Pandora, and XCOM were open, but nothing happened to trigger it, that I noticed. I did notice a few things that seemed odd with the driver uninstall/install. Windows appeared to auto install a driver from somewhere, after I uninstalled and restarted. also catalyst reported some warnings. I am not sure how to attach the report file, which is an .xml. I copied the text into a text document and attached that.
 

My Computer My Computer

Computer type
PC/Desktop
Computer Manufacturer/Model Number
custom build
OS
Windows 7 Home Premium 64-bit OEM
CPU
AMD FX-4170 Quad-Core 4.20 GHz
Motherboard
GIGABYTE GA-970A-D3 AM3+
Memory
Mushkin Enhanced Silverline 16GB (2 x 8GB) SDRAM DDR3 1333
Graphics Card(s)
SAPPHIRE Radeon HD 6850 1GB 256-bit GDDR5
Hard Drives
HGST Deskstar 7K1000.c 0F10383 1TB 7200 RPM 32MB Cache
Antivirus
Malwarebytes
Browser
Chrome
Windows will have installed it's own placeholder VGA driver, have you installed the AMD driver now?

Latest Analysis -

Code:
[COLOR="Red"]BugCheck 1000007E[/COLOR], {[COLOR="SeaGreen"]ffffffffc0000005[/COLOR], fffff8800431c351, fffff88013fe8458, fffff88013fe7cb0}

Probably caused by : [COLOR="Red"]atikmpag.sys[/COLOR] ( atikmpag+a351 )

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

Did you install the Beta driver instead of the WHQL driver? Beta drivers haven't been tested for stability, and therefore may cause problems. Please install the latest WHQL driver.

Code:
1: kd> [COLOR="SeaGreen"]lmvm atikmpag[/COLOR]
start             end                 module name
fffff880`04312000 fffff880`043ad000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        [COLOR="red"]Tue Jun 04 22:35:05 2013[/COLOR] (51AE5D89)
    CheckSum:         00099156
    ImageSize:        0009B000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
 

My Computer My Computer

Computer type
Laptop
Had another crash this time, playing a different game. Steam and Mumble both running.
 

My Computer My Computer

Computer type
PC/Desktop
Computer Manufacturer/Model Number
custom build
OS
Windows 7 Home Premium 64-bit OEM
CPU
AMD FX-4170 Quad-Core 4.20 GHz
Motherboard
GIGABYTE GA-970A-D3 AM3+
Memory
Mushkin Enhanced Silverline 16GB (2 x 8GB) SDRAM DDR3 1333
Graphics Card(s)
SAPPHIRE Radeon HD 6850 1GB 256-bit GDDR5
Hard Drives
HGST Deskstar 7K1000.c 0F10383 1TB 7200 RPM 32MB Cache
Antivirus
Malwarebytes
Browser
Chrome
BSOD Analysis:

Code:
[COLOR="Red"]BugCheck 1A[/COLOR], {[COLOR="Blue"]403[/COLOR], fffff680000e58d8, [COLOR="SeaGreen"]a8c00002e6893867[/COLOR], [COLOR="SeaGreen"]fffff680000e0038[/COLOR]}

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

Code:
Usual causes:  Device driver, memory, kernel

This bugcheck indicates that the page tables and PFNs are not synchronized properly.

Code:
3: kd> [COLOR="SeaGreen"].formats a8c00002e6893867; .formats fffff680000e0038[/COLOR]
Evaluate expression:
  Hex:     a8c00002`e6893867
  Decimal: -6287025067351525273
  Octal:   1243000000134642234147
  Binary:  10101000 11000000 00000000 00000010 11100110 10001001 00111000 01100111
  Chars:   ......8g
  Time:    ***** Invalid FILETIME
  Float:   low -3.24002e+023 high -2.13163e-014
  Double:  -2.07909e-112
Evaluate expression:
  Hex:     fffff680`000e0038
  Decimal: -10445359546312
  Octal:   1777777550000003400070
  Binary:  11111111 11111111 11110110 10000000 00000000 00001110 00000000 00111000
  Chars:   .......8
  Time:    ***** Invalid FILETIME
  Float:   low 1.28578e-039 high -1.#QNAN
  Double:  -1.#QNAN

----------------------------------------------------------------------

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:

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.

test|Slot1|Slot2
RAM1| Error | Error
RAM2|Good|Good
It is a RAM, a bad RAM.

But if you have got a result like that:
test|Slot1|Slot2
RAM1| Error |Good
RAM2| Error |Good
It is a motherboard issue. The particular slot is bad.
 

My Computer My Computer

Computer type
Laptop
Back
Top