BSOD after updating AMD Graphic Drivers

leonnkeong · 20 Nov 2013

Hey there, I have been using this machine since months ago, no BSOD or crashes. But last week I updated my amd driver to the latest one, I get BSOD consistently. Most of them are Memory Management. I'm pretty sure it is not because of other drivers since no problem back then. I can't install back the old driver since BF4 need the latest one, any idea?

PS- Now using the BETA 13.11.

Arc · 21 Nov 2013

Post it following the Blue Screen of Death (BSOD) Posting Instructions.

leonnkeong · 22 Nov 2013

Here you go~

Arc · 22 Nov 2013

Unfortunately the crash dumps are not providing any adequate information about the possible cause of the BSOD. As you know that it started after you updated the display driver, better you attempt to roll it back the earlier driver that worked stable. Follow Device Manager - Roll Back Driver

If still the situation is the same, we have to test the different elements that can cause a stop 0x1A BSOD.
___________________________________________________________________________________________

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa8005afefa0, ffff, 0}

Probably caused by : win32k.sys ( win32k!SURFACE::bDeleteSurface+3c8 )

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

4: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
    contains the address of the PFN for the corrupted page table page.
    On a 32 bit OS, parameter 2 contains a pointer to the number of used
    PTEs, and parameter 3 contains the number of used PTEs.
Arg2: fffffa8005afefa0
Arg3: 000000000000ffff
Arg4: 0000000000000000

Debugging Details:
------------------


BUGCHECK_STR:  0x1a_41790

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff8000694cd50 to fffff800068dbbc0

STACK_TEXT:  
fffff880`096ec128 fffff800`0694cd50 : 00000000`0000001a 00000000`00041790 fffffa80`05afefa0 00000000`0000ffff : nt!KeBugCheckEx
fffff880`096ec130 fffff800`068c83df : fffffa80`00000000 00000000`089b3fff 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x35084
fffff880`096ec2f0 fffff800`068dae53 : ffffffff`ffffffff fffff880`096ec5c0 fffff880`096ec628 00000000`00008000 : nt!NtFreeVirtualMemory+0x61f
fffff880`096ec3f0 fffff800`068d7410 : fffff960`001275b0 00000000`00000001 00000000`00000000 fffff900`c51e4cc0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`096ec588 fffff960`001275b0 : 00000000`00000001 00000000`00000000 fffff900`c51e4cc0 00000000`00000001 : nt!KiServiceLinkage
fffff880`096ec590 fffff960`0012f81d : 00000000`00000000 fffff880`00000001 fffff900`c51e4cc0 fffff900`00000000 : win32k!SURFACE::bDeleteSurface+0x3c8
fffff880`096ec6e0 fffff960`00126de0 : 00000000`000013cc fffff880`096eca00 fffff900`c074b4e0 fffff880`00000000 : win32k!NtGdiCloseProcess+0x2c9
fffff880`096ec740 fffff960`00126527 : 00000000`00000000 fffff880`096ecae0 fffffa80`091a9b50 00000000`00000000 : win32k!GdiProcessCallout+0x200
fffff880`096ec7c0 fffff800`06bb00c1 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`091a9b00 : win32k!W32pProcessCallout+0x6b
fffff880`096ec7f0 fffff800`06b962ed : 00000000`c0000005 00000000`c0000001 fffffa80`78457300 fffffa80`099cfb50 : nt!PspExitThread+0x4d1
fffff880`096ec8f0 fffff800`068ce6fa : 00000000`00000100 fffffa80`091a9c10 00000000`00000001 fffff800`068d17fd : nt!PsExitSpecialApc+0x1d
fffff880`096ec920 fffff800`068cea40 : 00000000`00000246 fffff880`096ec9a0 fffff800`06b96260 00000000`00000001 : nt!KiDeliverApc+0x2ca
fffff880`096ec9a0 fffff800`068daef7 : fffffa80`091a9b50 00000000`00000128 00000000`00000000 fffffa80`09e826d0 : nt!KiInitiateUserApc+0x70
fffff880`096ecae0 00000000`742f2e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`0237eec8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x742f2e09


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!SURFACE::bDeleteSurface+3c8
fffff960`001275b0 e9b0010000      jmp     win32k!SURFACE::bDeleteSurface+0x57d (fffff960`00127765)

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  win32k!SURFACE::bDeleteSurface+3c8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  521d506d

FAILURE_BUCKET_ID:  X64_0x1a_41790_win32k!SURFACE::bDeleteSurface+3c8

BUCKET_ID:  X64_0x1a_41790_win32k!SURFACE::bDeleteSurface+3c8

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