Solved BSOD while installing Windows 7, error WHEA 0x00000124

[axe0]

OH those magic words

I don't have another MB with Skylake

Been plowing thru event log
keeps reporting processor 2 event id's 18/19,
sometimes doesn't even report it, then states a problem with processor 3
in my ignorance coz im not a BSOD expert, would that imply a voltage problem??

Roy

The WHEA error structure shows why the call to the BSOD was made, it doesn't mean that core 2 is the cause.
However, due to the fact that core 2 called the BSOD for an unknown hardware error, basic hardware troubleshooting should be performed as first step.

1. Any overclocking, revert them
2. Stress test hardware
3. Reset the BIOS
4. Check for BIOS.
midvik, although software indicates that the tested hardware is fine, software is never 100% accurate. For this reason, the best test is to place the part in a different system and see how the stability of the test goes.

===============================================================================
Common Platform Error Record @ fffffa8008844028
-------------------------------------------------------------------------------
Record Id     : 01d28e193d991983
Severity      : Fatal (1)
Length        : 864
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 2/23/2017 21:10:27 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa80088440a8
Section       @ fffffa8008844180
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Micro-Architectural Error
Flags         : 0x00
CPU Version   : 0x00000000000506e3
Processor ID  : 0x0000000000000002

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa80088440f0
Section       @ fffffa8008844240
Offset        : 536
Length        : 64
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000002
CPU Id        : e3 06 05 00 00 08 10 02 - bf fb fa 7f 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

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa8008844138
Section       @ fffffa8008844280
Offset        : 600
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : Unknown (Proc 2 Bank 0)
  Status      : 0xb200000000010005




Event[868]:
  Log Name: System
  Source: Microsoft-Windows-WHEA-Logger
  Date: 2017-02-23T20:41:22.442
  Event ID: 18
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: midvik-PC
  Description: 
A fatal hardware error has occurred.

Reported by component: Processor Core
Error Source: Machine Check Exception
Error Type: Internal parity error
Processor ID: 2

The details view of this entry contains further information.

 

[ICIT2LOL]

Hi, so after many more tests i decided to let professionals do the work and took my pc to the repair shop. It's there for a few days now and no news so far. Can't wait to hear what was the problem. Once i get it fixed, i'll post here so it may help someone with the same or similar problem.

Ok mate it will be interesting to see what they come up with.

 

[midvik]

Hi all! So finally after long time news came that cpu is definite problem and was replaced for another one. Now it works without problem. I thank you all for your time and patience.

 

[ICIT2LOL]

Good to hear mate.