FYI: Experiencing BSOD

I've had four BSODs in Win7 x64 since I did a clean install. Two of them were immediately after the OS installation and before the numerous patches were applied. It stopped doing it after that. Over the last week it did it twice. I analyzed the minidump tonight and it is caused by 10.12 Catalyst. It happens when you walk away and the LCD times out. A little research indicates that this is fairly common with 5850 and 5870 cards... even the desktop models.

The fix seems to be removing and reinstalling 10.12 or reverting to 10.11. I just wanted to share in case you run into this since google says I'm not the first person to experience this.

 

Good to know!

 

Here is the relevant piece of the debug output:

Code:

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
atikmdag+90817
fffff880`0492d817 8b4820          mov     ecx,dword ptr [rax+20h]

CONTEXT:  fffff88008e66900 -- (.cxr 0xfffff88008e66900)
rax=0000000000000000 rbx=fffffa80090d5290 rcx=fffffa8009ea3d90
rdx=0000000000000001 rsi=0000000000000015 rdi=fffffa800a1c2340
rip=fffff8800492d817 rsp=fffff88008e672d0 rbp=fffffa8009ea3d90
 r8=0000000000000015  r9=fffff88004cef970 r10=0000000000000000
r11=fffff88008e67420 r12=0000000000000000 r13=fffffa80072c4010
r14=0000000000000001 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
atikmdag+0x90817:
fffff880`0492d817 8b4820          mov     ecx,dword ptr [rax+20h] ds:002b:00000000`00000020=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

Google atikmdag+90817 and you'll find that it's not terribly uncommon with 10.12.

 

Same goes for the nvidia cards... atikmdag.sys is the driver service of ATI, nvlddmkm.sys is the one of nvidia cards. Google one of these two and you'll find hundreds of reports.

There are several possible causes for this, Microsoft of course says it's driver related but in most cases it can't be resolved with a clean driver instal...

See this link for some information about what's causing this... and check out the comments... there are a lot.

Event ID 4101 ? Display Driver Timeout Detection and Recovery

 

Figures, I just went from 10.10 to 10.12 last night -___-

Thanks for the heads up Jody

Edit: Hadnt refreshed this page, but ill be sure to pay close attention to it. Havent had any BSODS on 10.12 yet

 

I used to have the same screen timeout lockups with 10.12.

Currently on the Mobility Mod of 11.1 and haven't got any crashes yet. Still crossing my fingers though.