Lately we have notices a good lot of BSOD issues with 14.12 omega driver installed.
Uninstall your installed latest version of the display driver.
Then clean up any possible leftover.
Then install version 14.9 WHQL only.
Late us know the result. Additional steps may be required depending on the situation.
EDIT: Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.
- Click on the Start button
- Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
- Select the “Startup” tab.
- Deselect all items other than the antivirus.
- Apply > OK
- Accept then restart.
At least, remove the "Killer Network Manager" from startup.
_______________________________________
Code:
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff8800f313160, fffff88003ef1dd8, fffff88003ef1630}
Probably caused by : atikmdag.sys ( atikmdag+cd160 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8800f313160, The address that the exception occurred at
Arg3: fffff88003ef1dd8, Exception Record Address
Arg4: fffff88003ef1630, 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+cd160
fffff880`0f313160 488b4130 mov rax,qword ptr [rcx+30h]
EXCEPTION_RECORD: fffff88003ef1dd8 -- (.exr 0xfffff88003ef1dd8)
ExceptionAddress: fffff8800f313160 (atikmdag+0x00000000000cd160)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000030
Attempt to read from address 0000000000000030
CONTEXT: fffff88003ef1630 -- (.cxr 0xfffff88003ef1630;r)
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000002 rsi=fffff8a01206d198 rdi=0000000000000001
rip=fffff8800f313160 rsp=fffff88003ef2018 rbp=fffff8a01caba198
r8=0000000000000003 r9=0000000000000008 r10=fffff80002e59000
r11=fffff88003fe9840 r12=fffff8a01caba010 r13=0000000000000000
r14=fffffa800ba74f01 r15=fffff8a01ca7a198
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
atikmdag+0xcd160:
fffff880`0f313160 488b4130 mov rax,qword ptr [rcx+30h] ds:002b:00000000`00000030=????????????????
Last set context:
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000002 rsi=fffff8a01206d198 rdi=0000000000000001
rip=fffff8800f313160 rsp=fffff88003ef2018 rbp=fffff8a01caba198
r8=0000000000000003 r9=0000000000000008 r10=fffff80002e59000
r11=fffff88003fe9840 r12=fffff8a01caba010 r13=0000000000000000
r14=fffffa800ba74f01 r15=fffff8a01ca7a198
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
atikmdag+0xcd160:
fffff880`0f313160 488b4130 mov rax,qword ptr [rcx+30h] ds:002b:00000000`00000030=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000030
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003106100
GetUlongFromAddress: unable to read from fffff800031061c0
0000000000000030 Nonpaged pool
FOLLOWUP_IP:
atikmdag+cd160
fffff880`0f313160 488b4130 mov rax,qword ptr [rcx+30h]
BUGCHECK_STR: 0x7E
DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
LAST_CONTROL_TRANSFER: from fffff8800f37c539 to fffff8800f313160
STACK_TEXT:
fffff880`03ef2018 fffff880`0f37c539 : 00000000`00000000 fffff8a0`1caba198 00000000`00000000 fffff8a0`126ec198 : atikmdag+0xcd160
fffff880`03ef2020 00000000`00000000 : fffff8a0`1caba198 00000000`00000000 fffff8a0`126ec198 000000f4`10008000 : atikmdag+0x136539
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: atikmdag+cd160
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: atikmdag
IMAGE_NAME: atikmdag.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 546ea3c3
STACK_COMMAND: .cxr 0xfffff88003ef1630 ; kb
FAILURE_BUCKET_ID: X64_0x7E_atikmdag+cd160
BUCKET_ID: X64_0x7E_atikmdag+cd160
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x7e_atikmdag+cd160
FAILURE_ID_HASH: {cad8ac66-9a19-b808-09ab-072337b957bb}
Followup: MachineOwner
---------
2: kd> lmvm atikmdag
start end module name
fffff880`0f246000 fffff880`104ca000 atikmdag T (no symbols)
Loaded symbol image file: atikmdag.sys
Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
Image name: atikmdag.sys
Timestamp: Fri Nov 21 08:00:27 2014 (546EA3C3)
CheckSum: 0121F198
ImageSize: 01284000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Code:
BugCheck 1000007E, {ffffffffc0000005, fffff80002e90bd0, fffff880033caea8, fffff880033ca700}
*** WARNING: Unable to verify timestamp for bflwfx64.sys
*** ERROR: Module load completed but symbols could not be loaded for bflwfx64.sys
Probably caused by : bflwfx64.sys ( bflwfx64+7898 )
Followup: MachineOwner
---------
Quote