Solved bsod from stand by

Nelson35 · Jan 10, 2017

Hey guys. I got a bsod today and wanted you all to take a look at it. When I woke it from stand by the computer itself was on, but the screen didn't wake up. This is the 3rd time that the screen would power down and not come back on until I pressed ctrl+alt+delete.

ICIT2LOL · Jan 10, 2017

Hello Nelson mate it might not be the issue but there seems to be a graphics driver problem.

The usual suggestion for this is ti uninstall the Catalyst Control Centre and run the graphics using the manufacturers driver APU I am not entirely sure this is the one but try .

Having said that it might be worth trying this first - reseating the card and also any cables to and from the machine and monitor.

Code:

ADDITIONAL_DEBUG_TEXT:  
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.

FAULTING_MODULE: fffff8000325e000 nt

DEBUG_FLR_IMAGE_TIMESTAMP:  57dc442d

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

FAULTING_IP: 
atikmdag+103c40
fffff880`0f528c40 488b5030        mov     rdx,qword ptr [rax+30h]

EXCEPTION_RECORD:  fffff8800b69c4e8 -- (.exr 0xfffff8800b69c4e8)
ExceptionAddress: fffff8800f528c40 (atikmdag+0x0000000000103c40)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000030
Attempt to read from address 0000000000000030

CONTEXT:  fffff8800b69bd40 -- (.cxr 0xfffff8800b69bd40;r)
rax=0000000000000000 rbx=fffffa800c91d228 rcx=fffffa800cabe030
rdx=0000000000000001 rsi=fffffa800aadf180 rdi=000000000000001f
rip=fffff8800f528c40 rsp=fffff8800b69c728 rbp=0000000000000000
 r8=0000000000000000  r9=000000000000000b r10=000000000000002b
r11=fffff8800b69c680 r12=0000000000000002 r13=0000000000000004
r14=0000000000000002 r15=0000000000000002
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
atikmdag+0x103c40:
fffff880`0f528c40 488b5030        mov     rdx,qword ptr [rax+30h] ds:002b:00000000`00000030=????????????????
Last set context:
rax=0000000000000000 rbx=fffffa800c91d228 rcx=fffffa800cabe030
rdx=0000000000000001 rsi=fffffa800aadf180 rdi=000000000000001f
rip=fffff8800f528c40 rsp=fffff8800b69c728 rbp=0000000000000000
 r8=0000000000000000  r9=000000000000000b r10=000000000000002b
r11=fffff8800b69c680 r12=0000000000000002 r13=0000000000000004
r14=0000000000000002 r15=0000000000000002
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
atikmdag+0x103c40:
fffff880`0f528c40 488b5030        mov     rdx,qword ptr [rax+30h] ds:002b:00000000`00000030=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x7E

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

LAST_CONTROL_TRANSFER:  from fffff8800f4dd864 to fffff8800f528c40

STACK_TEXT:  
fffff880`0b69c728 fffff880`0f4dd864 : 00000000`00000000 00000000`00000001 00000000`00000058 00000000`00000002 : atikmdag+0x103c40
fffff880`0b69c730 00000000`00000000 : 00000000`00000001 00000000`00000058 00000000`00000002 fffff880`0f6f5b80 : atikmdag+0xb8864


FOLLOWUP_IP: 
atikmdag+103c40
fffff880`0f528c40 488b5030        mov     rdx,qword ptr [rax+30h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  atikmdag+103c40

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME:  [COLOR="Red"]atikmdag.sys[/COLOR]

STACK_COMMAND:  .cxr 0xfffff8800b69bd40 ; kb

BUCKET_ID:  WRONG_SYMBOLS

FAILURE_BUCKET_ID:  WRONG_SYMBOLS

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:wrong_symbols

FAILURE_ID_HASH:  {70b057e8-2462-896f-28e7-ac72d4d365f8}

Followup: MachineOwner

Nelson35 · Jan 11, 2017

ICIT2LOL said:

Hello Nelson mate it might not be the issue but there seems to be a graphics driver problem.

The usual suggestion for this is ti uninstall the Catalyst Control Centre and run the graphics using the manufacturers driver APU I am not entirely sure this is the one but try .

Having said that it might be worth trying this first - reseating the card and also any cables to and from the machine and monitor.

Code:

ADDITIONAL_DEBUG_TEXT:  
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.

FAULTING_MODULE: fffff8000325e000 nt

DEBUG_FLR_IMAGE_TIMESTAMP:  57dc442d

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

FAULTING_IP: 
atikmdag+103c40
fffff880`0f528c40 488b5030        mov     rdx,qword ptr [rax+30h]

EXCEPTION_RECORD:  fffff8800b69c4e8 -- (.exr 0xfffff8800b69c4e8)
ExceptionAddress: fffff8800f528c40 (atikmdag+0x0000000000103c40)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000030
Attempt to read from address 0000000000000030

CONTEXT:  fffff8800b69bd40 -- (.cxr 0xfffff8800b69bd40;r)
rax=0000000000000000 rbx=fffffa800c91d228 rcx=fffffa800cabe030
rdx=0000000000000001 rsi=fffffa800aadf180 rdi=000000000000001f
rip=fffff8800f528c40 rsp=fffff8800b69c728 rbp=0000000000000000
 r8=0000000000000000  r9=000000000000000b r10=000000000000002b
r11=fffff8800b69c680 r12=0000000000000002 r13=0000000000000004
r14=0000000000000002 r15=0000000000000002
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
atikmdag+0x103c40:
fffff880`0f528c40 488b5030        mov     rdx,qword ptr [rax+30h] ds:002b:00000000`00000030=????????????????
Last set context:
rax=0000000000000000 rbx=fffffa800c91d228 rcx=fffffa800cabe030
rdx=0000000000000001 rsi=fffffa800aadf180 rdi=000000000000001f
rip=fffff8800f528c40 rsp=fffff8800b69c728 rbp=0000000000000000
 r8=0000000000000000  r9=000000000000000b r10=000000000000002b
r11=fffff8800b69c680 r12=0000000000000002 r13=0000000000000004
r14=0000000000000002 r15=0000000000000002
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
atikmdag+0x103c40:
fffff880`0f528c40 488b5030        mov     rdx,qword ptr [rax+30h] ds:002b:00000000`00000030=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x7E

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

LAST_CONTROL_TRANSFER:  from fffff8800f4dd864 to fffff8800f528c40

STACK_TEXT:  
fffff880`0b69c728 fffff880`0f4dd864 : 00000000`00000000 00000000`00000001 00000000`00000058 00000000`00000002 : atikmdag+0x103c40
fffff880`0b69c730 00000000`00000000 : 00000000`00000001 00000000`00000058 00000000`00000002 fffff880`0f6f5b80 : atikmdag+0xb8864


FOLLOWUP_IP: 
atikmdag+103c40
fffff880`0f528c40 488b5030        mov     rdx,qword ptr [rax+30h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  atikmdag+103c40

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME:  [COLOR=Red]atikmdag.sys[/COLOR]

STACK_COMMAND:  .cxr 0xfffff8800b69bd40 ; kb

BUCKET_ID:  WRONG_SYMBOLS

FAILURE_BUCKET_ID:  WRONG_SYMBOLS

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:wrong_symbols

FAILURE_ID_HASH:  {70b057e8-2462-896f-28e7-ac72d4d365f8}

Followup: MachineOwner

I've upgraded the drivers now, so I guess it's time to play the waiting game.

ICIT2LOL · Jan 11, 2017

Yes mate it is and just as a by the by it might be worth testing a few of the components too as I see the board is now getting on a bit. Plus if you wanted too you could even try updating some of the mobo drivers Access Denied and I am thinking specifically of the basic ones like the chipset for example. But that is just an afterthought.

Nelson35 · Jan 11, 2017

ICIT2LOL said:
Yes mate it is and just as a by the by it might be worth testing a few of the components too as I see the board is now getting on a bit. Plus if you wanted too you could even try updating some of the mobo drivers Access Denied and I am thinking specifically of the basic ones like the chipset for example. But that is just an afterthought.

I'm not exactly confident enough to mess with the mobo drivers.

ICIT2LOL · Jan 11, 2017

Ok Nelson now updating say the chipset is not a difficult or hazardous thing to do unlike the BIOS which if not done correctly or there is power outage whilst doing it - can brick the board.

But the choice is yours mate.

Nelson35 · Jan 12, 2017

ICIT2LOL said:
Ok Nelson now updating say the chipset is not a difficult or hazardous thing to do unlike the BIOS which if not done correctly or there is power outage whilst doing it - can brick the board.

But the choice is yours mate.

Are these the files I should download If I update the chipset?

ICIT2LOL · Jan 13, 2017

Ok Nelson yes the Intel Chipset Driver top one is the one to go with.

Just download where it says global it will download (obviously) and then just run the download. It should not take long - let us know how things go.

Nelson35 · Jan 15, 2017

I wanted to add that today when I woke the PC out of standby the aero effect jumped off by itself then a little later came back on. I don't know what that could mean. It also did that thing where the screen was on, but it was still black. I had to press ctrl+alt+delete to get it back on.

Solved bsod from stand by

Nelson35

New member

My Computer

ICIT2LOL

Confusion Therapist

My Computer

Nelson35

New member

My Computer

ICIT2LOL

Confusion Therapist

My Computer

Nelson35

New member

My Computer

ICIT2LOL

Confusion Therapist

My Computer

Nelson35

New member

My Computer

ICIT2LOL

Confusion Therapist

My Computer

Nelson35

New member

My Computer

Similar threads