Solved BSOD when opening Chrome 'Attempt to reset and recover driver timeout'

[Duncanoe]

Hi guys, just wondering if I could get some help on a BSoD I've been getting recently. It has always occurred after I have opened Chrome shortly after logging in. For some reason the BSoD does not occur if I go on a game in Steam then go back to Chrome. I've attached the dmp file that explains the problem as well as the following:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 2057

Additional information about the problem:
BCCode: 116
BCP1: FFFFFA800D4654E0
BCP2: FFFFF88004A0AE5C
BCP3: 0000000000000000
BCP4: 0000000000000002
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1


Hope you guys can help me out, thanks.

 

[Boozad]

Your logs are incomplete, important files are missing that we need to analyze your issue/s. Follow Blue Screen of Death (BSOD) Posting Instructions, let the tool run until it has completely finished and then upload the new logs.

 

[Duncanoe]

Apologies, I've attached the file to this message, thanks!

 

[Boozad]

You've received three different bugchecks, 0x124 (hardware) 0x50 (hardware amongst other things) and three 0x116. The 0x116 are VIDEO_TDR_ERROR (Timeout detection recovery) which means there is a problem with your GPU whether it be drivers, heat, power to the GPU or just a bad card. Given the 0x124 and 0x50 I'm leaning towards the card being problematic.

First off try updating your drivers for it, they're old and could possibly be the problem. Download the latest drivers for your card from here and save it to your desktop. Next, download DDU and follow http://www.sevenforums.com/tutorials/367109-display-driver-uninstaller-how-use.html to completely uninstall your ATI package.
Reboot and install the driver you downloaded. Test the system for stability.

BugCheck 116, {fffffa800d4654e0, fffff88004a0ae5c, 0, 2}

Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2
[COLOR=Red]*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys[/COLOR]
Probably caused by : atikmpag.sys ( atikmpag+ae5c )

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

5: kd> lmvm atikmpag
start             end                 module name
fffff880`04a00000 fffff880`04a9e000   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 Aug 30 23:32:32 2013[/COLOR] (52211D80)
    CheckSum:         0009C9D2
    ImageSize:        0009E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800496a8f8, 0, 0}

Probably caused by : AuthenticAMD

Followup: MachineOwner

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff880061e2eb8, 1, fffff800032db9fb, 0}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!SepAccessCheck+14b )

Followup: MachineOwner

​

 

[Duncanoe]

Updated the drivers and after a restart everything seems to be working well! Thanks a lot for your help!

 

[Boozad]

You're welcome, glad to hear all seems well. We'll be here if you encounter any more issues.