AnsweredAssumed Answered

Why is my computer blue screening on mcupdate_AuthenticAMD.dll?

Question asked by bradman1968 on Sep 22, 2015
Latest reply on Sep 23, 2015 by bradman1968

My PC is blue screening, apparently in relation to:

 

mcupdate_AuthenticAMD.dll. Any suggestions would be much appreciated.

 

SYSTEM_SKU:  SKU

SYSTEM_VERSION:  To be filled by O.E.M.

BIOS_DATE:  04/07/2014

BASEBOARD_PRODUCT:  M5A99FX PRO R2.0

BASEBOARD_VERSION:  Rev 1.xx

ADDITIONAL_DEBUG_TEXT: 

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

WRONG_SYMBOLS_TIMESTAMP: 55d5626b

WRONG_SYMBOLS_SIZE: 852000

FAULTING_MODULE: fffff80045a0c000 nt

DEBUG_FLR_IMAGE_TIMESTAMP:  55d5626b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff80045ae0ca2

BUGCHECK_P3: ffffd0002121ee50

BUGCHECK_P4: 0

EXCEPTION_CODE: (NTSTATUS) 0x55d5626b - <Unable to get error code text>

FAULTING_IP:

nt+d4ca2

fffff800`45ae0ca2 48890a          mov     qword ptr [rdx],rcx

 

CONTEXT:  ffffd0002121ee50 -- (.cxr 0xffffd0002121ee50)

rax=0000000000000000 rbx=ffffe000f559ae20 rcx=ffffd0002121f8d0

rdx=8802000000000000 rsi=0000000000000001 rdi=ffffd0002121f8d0

rip=fffff80045ae0ca2 rsp=ffffd0002121f870 rbp=ffffe000f4684080

r8=ffffd0002121f930  r9=0000000000000000 r10=0000000000000000

r11=fffff96152618c93 r12=0000000000000000 r13=0000000000000000

r14=0000000000010001 r15=0000000000000000

iopl=0         nv up di ng nz na po nc

cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010086

nt+0xd4ca2:

fffff800`45ae0ca2 48890a          mov     qword ptr [rdx],rcx ds:002b:88020000`00000000=????????????????

Resetting default scope

 

CPU_COUNT: 8

CPU_MHZ: 10ef

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 15

CPU_MODEL: 2

CPU_STEPPING: 0

CUSTOMER_CRASH_COUNT:  1

CURRENT_IRQL:  0

ANALYSIS_VERSION: 10.0.10240.9 amd64fre

LAST_CONTROL_TRANSFER:  from 000000000000fe30 to fffff80045ae0ca2

 

STACK_TEXT: 

ffffd000`2121f870 00000000`0000fe30 : 00000000`00000000 ffffe000`f885b930 fffff961`522b1a9e 00000000`00000000 : nt+0xd4ca2

ffffd000`2121f878 00000000`00000000 : ffffe000`f885b930 fffff961`522b1a9e 00000000`00000000 fffff800`45a5e504 : 0xfe30

 

FOLLOWUP_IP:

nt+d4ca2

fffff800`45ae0ca2 48890a          mov     qword ptr [rdx],rcx

 

 

SYMBOL_STACK_INDEX:  0

FOLLOWUP_NAME:  MachineOwner

STACK_COMMAND:  .cxr 0xffffd0002121ee50 ; kb

BUGCHECK_STR:  55D5626B

 

FAILURE_EXCEPTION_CODE:  55D5626B

EXCEPTION_STR:  WRONG_SYMBOLS

IMAGE_NAME:  ntoskrnl.wrong.symbols.exe

MODULE_NAME: nt_wrong_symbols

 

SYMBOL_NAME:  nt_wrong_symbols!55D5626B852000

BUCKET_ID:  WRONG_SYMBOLS_X64_10240.16463.amd64fre.th1.150819-1946_TIMESTAMP_150820-051523

DEFAULT_BUCKET_ID:  WRONG_SYMBOLS_X64_10240.16463.amd64fre.th1.150819-1946_TIMESTAMP_150820-051523

PRIMARY_PROBLEM_CLASS:  WRONG_SYMBOLS

FAILURE_BUCKET_ID:  WRONG_SYMBOLS_X64_10240.16463.amd64fre.th1.150819-1946_TIMESTAMP_150820-051523_55D5626B_nt_wrong_symbols!55D5626B852000

 

 

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:wrong_symbols_x64_10240.16463.amd64fre.th1.150819-1946_timestamp_150820-051523_55d5626b_nt_wrong_symbols!55d5626b852000

FAILURE_ID_HASH:  {bb43ace6-3e71-60ab-9dfa-75f6752a2342}

Followup:     MachineOwner

Outcomes