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
Welcome to the forums cjacobson22,
Code:BugCheck 3B, {c0000005, fffff8800418e986, fffff880038e5bc0, 0} Probably caused by : dxgmms1.sys ( dxgmms1!VidMmDestroyAllocation+46 )Code:Usual causes: System service, Device driver, graphics driver, memoryYour graphics card drivers indicate to be a possible cause, please update to the latest WHQL version, and follow these steps:Code:2: kd> lmvm atikmpag 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: Fri Mar 29 01:09:45 2013 (5154E9D9) CheckSum: 00091A60 ImageSize: 00094000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
WHQL
Release Date: April 24th 2013
Version: 13.4
In Device Manager: 12.104
- Download Driver
- Start
Type: Device Manager
- Expand Display Adapters
- Right-Click Driver Name, Uninstall
- Reboot
- Run Driver Sweeper
- Reboot
- 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:
- Malwarebytes : Free anti-malware download
- Microsoft Security Essentials | Protect against viruses, spyware, and other malware
InformationRemember 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:
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.
Windows will have installed it's own placeholder VGA driver, have you installed the AMD driver now?
Latest Analysis -
Code:BugCheck 1000007E, {ffffffffc0000005, fffff8800431c351, fffff88013fe8458, fffff88013fe7cb0} Probably caused by : atikmpag.sys ( atikmpag+a351 )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: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:1: kd> lmvm atikmpag 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: Tue Jun 04 22:35:05 2013 (51AE5D89) CheckSum: 00099156 ImageSize: 0009B000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Had another crash this time, playing a different game. Steam and Mumble both running.
BSOD Analysis:
Code:BugCheck 1A, {403, fffff680000e58d8, a8c00002e6893867, fffff680000e0038} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+3211c )This bugcheck indicates that the page tables and PFNs are not synchronized properly.Code:Usual causes: Device driver, memory, kernel
----------------------------------------------------------------------Code:3: kd> .formats a8c00002e6893867; .formats fffff680000e0038 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:
InformationAdditional Help - Using Driver Verifier to identify issues with Drivers
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.
Quote