Code:
BugCheck 1000008E, {c0000005, 949ce5da, a3552ab0, 0}
Probably caused by : memory_corruption
Code:
Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint in startup without having a debugger attached, Hardware incompatibility, Faulty system service, 3rd party remote control, Memory
Code:
CHKIMG_EXTENSION: !chkimg -lo 50 -d !win32k
949ce5d9 - win32k!RGNOBJ::vCopy+8
[ 7d:fd ]
1 error : !win32k (949ce5d9)
Code:
1: kd> !chkimg -lo 50 -db !win32k
1 error : !win32k (949ce5d9)
949ce5d0 90 8b ff 55 8b ec 56 57 8b *fd 08 8b 07 83 c0 30 ...U..VW.......0
We can see that the module has become corrupted for some reason, I highly suspect hardware.
I managed to find this driver within the raw stack:
Code:
1: kd> lmvm atikmdag
start end module name
93024000 9395a000 atikmdag T (no symbols)
Loaded symbol image file: atikmdag.sys
Image path: atikmdag.sys
Image name: atikmdag.sys
Timestamp: Fri Apr 06 02:44:39 2012 (4F7E4A87)
CheckSum: 008EDADD
ImageSize: 00936000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Please update to the latest WHQL driver available from here: AMD Graphics Drivers & Software
WHQL
Release Date:
April 24th 2013
Version: 13.4
In Device Manager: 12.104
Code:
BugCheck 124, {0, 84f564dc, 0, 0}
Probably caused by : GenuineIntel
Code:
Usual causes: Hardware, Incompatibility, May be driver corruption
Code:
1: kd> !errrec 84f564dc
===============================================================================
Common Platform Error Record @ 84f564dc
-------------------------------------------------------------------------------
Record Id : 01ce6e7d6ae867cb
Severity : Fatal (1)
Length : 928
Creator : Microsoft
Notify Type : Machine Check Exception
Timestamp : 6/21/2013 12:47:02 (UTC)
Flags : 0x00000002 PreviousError
===============================================================================
Section 0 : Processor Generic
-------------------------------------------------------------------------------
Descriptor @ 84f5655c
Section @ 84f56634
Offset : 344
Length : 192
Flags : 0x00000001 Primary
Severity : Fatal
Proc. Type : x86/x64
Instr. Set : x86
Error Type : Micro-Architectural Error
Flags : 0x00
CPU Version : 0x0000000000000f34
Processor ID : 0x0000000000000000
===============================================================================
Section 1 : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor @ 84f565a4
Section @ 84f566f4
Offset : 536
Length : 128
Flags : 0x00000000
Severity : Fatal
Local APIC Id : 0x0000000000000000
CPU Id : 34 0f 00 00 00 08 02 00 - 1d 44 00 00 ff fb eb bf
00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
Proc. Info 0 @ 84f566f4
===============================================================================
Section 2 : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor @ 84f565ec
Section @ 84f56774
Offset : 664
Length : 264
Flags : 0x00000000
Severity : Fatal
Error : Internal timer (Proc 0 Bank 0)
Status : 0xa200000084010400
The first parameter or argument has the value of 0x0, which is a Machine Check Exception, which means the CPU has detected a hardware problem and the address points to a processor error because the CPU has found one, so it could be a different form of hardware which is causing the issue.
In such a situation, it is best to use these steps:
All the hardware seeming to be running stable and tests reporting no errors, could mean a bad motherboard.