![]() |
|
|
#5 |
|
Junior Member
Join Date: May 2012
Posts: 9
|
I have additional information for you. I attempted to roll the drivers back to previous versions. v6.2 still produces BSOD, however the faulting driver is now back to atikmdag.sys:
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Arguments: Arg1: ffffffffc0000005, The exception code that was not handled Arg2: fffff88004e9b165, The address that the exception occurred at Arg3: fffff88002dd9cc8, Exception Record Address Arg4: fffff88002dd9520, Context Record Address 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+252165 fffff880`04e9b165 8b81a8000000 mov eax,dword ptr [rcx+0A8h] STACK_TEXT: fffff880`02dd9f00 fffff880`04e92cd1 : fffffa80`0ba93020 fffffa80`076dbbc0 00000000`00000006 fffff880`04fcee50 : atikmdag+0x252165 fffff880`02dd9f10 fffff880`04c5490d : fffffa80`076dbbc0 fffffa80`076dbbc0 fffff880`02dda060 fffff880`02dda060 : atikmdag+0x249cd1 fffff880`02dd9f40 fffff880`04c53b10 : fffffa80`076dbbc0 fffff880`02dda060 fffff880`02dda110 00000000`00000000 : atikmdag+0xb90d fffff880`02dd9fb0 fffff880`04c57d9e : fffffa80`076dbbc0 00000000`00000001 fffff880`02dda060 fffff880`02dda060 : atikmdag+0xab10 fffff880`02dd9fe0 fffff880`0430389d : fffff880`02dda100 fffffa80`066e04c0 fffffa80`0a63d040 00000000`00000000 : atikmdag+0xed9e fffff880`02dda030 fffff880`04370ab4 : 00000000`401e0300 fffffa80`078c8000 00000000`4e506456 fffff880`00000798 : atikmpag+0x989d fffff880`02dda0f0 fffff880`04369966 : 00000000`00d1d104 00000000`00000000 00000000`00d1d100 fffff880`02dda2a0 : dlkmd+0x17ab4 fffff880`02dda150 fffff880`044ba5a8 : fffffa80`076dbbc0 fffff880`02dda2a0 fffff880`02dda2a0 fffffa80`00000002 : dlkmd+0x10966 fffff880`02dda220 fffff880`0452a1de : fffff8a0`025f8900 fffff8a0`025f8990 00000000`00000000 fffffa80`0bb93000 : dxgkrnl!DXGADAPTER::DdiCommitVidPn+0x50 fffff880`02dda250 fffff880`044b2282 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff8a0`00000000 : dxgkrnl!DmmCommitVidPn+0x926 fffff880`02dda390 fffff880`044ca2a1 : fffff8a0`0ebcac01 fffff8a0`00f41100 fffff8a0`017c2500 fffff8a0`03e8dc00 : dxgkrnl!DXGADAPTER::CommitVidPn+0x546 fffff880`02dda6a0 fffff960`00665d8d : ffffffff`00000004 ffffffff`fffd74f6 00000000`00000002 00000000`00000006 : dxgkrnl!DxgkCddDisable+0x609 fffff880`02dda870 fffff800`03169e6a : 00000000`00000000 fffffa80`0a40a400 00000000`00000080 fffffa80`0bbc8b30 : cdd!PresentWorkerThread+0xa21 fffff880`02ddac00 fffff800`02ec3f06 : fffff800`03045e80 fffffa80`0a40a400 fffff800`03053cc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`02ddac40 00000000`00000000 : fffff880`02ddb000 fffff880`02dd5000 fffff880`02dd9fe0 00000000`00000000 : nt!KiStartSystemThread+0x16 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: atikmdag+252165 FOLLOWUP_NAME: MachineOwner MODULE_NAME: atikmdag IMAGE_NAME: atikmdag.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4f8f6f72 STACK_COMMAND: .cxr 0xfffff88002dd9520 ; kb FAILURE_BUCKET_ID: X64_0x7E_atikmdag+252165 BUCKET_ID: X64_0x7E_atikmdag+252165 Downgrading to driver v6.1 has stopped BSOD from occurring, both in power save and when you tell the system to logoff. v6.2 and v6.3 BSODs occur during power save AND when you tell the system to logoff. Last edited by Garion; 05-30-2012 at 03:50 PM. |
|
|
|
| Thread Tools | Search this Thread |
| Display Modes | |
|
|