BSOD on fresh new install, unknown cause

Hello and welcome John now before we start on the dump files which are mentioning something about Genuine Intel could you let us know what Windows media did you use on the new motherboard because if it was an OEM for the old mobo without Microsoft's ok you cannot use it on a new board. If the media is retail then no problems.

There is just one other little thing you have a problem device listed in msinfo32 see pic might be an idea to get that driver installed.

Ok sorry late reply John mate yes what I meant by media was the Windows DVD an OEM or retail version. Because an OEM version is tied to the first board it is installed on and cannot be used on a new board without Microsoft giving the ok to do so.
For example if the original board died you would phone Microsoft tell them your predicament and (to be fair to them) they usually let you use that OEM with its' own code on the new board. If you did this more than say twice then they would not so helpful.
Now if the DVD is a retail version then it could be used on a new board without their permission but only for one machine at a time. This is of course because the retail version is that much more expensive.

The driver for the Ethernet is not a problem then I would guess there is some form it works in when the system was installed.
Now am not sure what the dumps are showing but can you recheck the CPU is propperly seated and the cooler also a snug fit because there are some pointers to a CPU problem from some searches I have made

Code:

BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  OcButtonServic

CURRENT_IRQL:  f

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

STACK_TEXT:  
fffff880`0371fb58 fffff800`02c1ea3b : 00000000`00000124 00000000`00000000 fffffa80`1262b028 00000000`bf800000 : nt!KeBugCheckEx
fffff880`0371fb60 fffff800`02de1713 : 00000000`00000001 fffffa80`1250cc50 00000000`00000000 fffffa80`1250cca0 : hal!HalBugCheckSystem+0x1e3
fffff880`0371fba0 fffff800`02c1e700 : 00000000`00000728 fffffa80`1250cc50 fffff880`0371ff30 fffff880`0371ff00 : nt!WheaReportHwError+0x263
fffff880`0371fc00 fffff800`02c1e052 : fffffa80`1250cc50 fffff880`0371ff30 fffffa80`1250cc50 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`0371fd50 fffff800`02c1df0d : 00000000`00000008 00000000`00000001 fffff880`0371ffb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`0371fd90 fffff800`02c11e88 : 00000000`00000000 00000000`00000010 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`0371fdc0 fffff800`02cc87ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`0371fdf0 fffff800`02cc8613 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`0371ff30 fffff800`02cc0b08 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`0b9f6638 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!memmove+0x208


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION:  

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x124_genuineintel_processor_mae

FAILURE_ID_HASH:  {addebe90-d04a-b9c9-a39c-2531fe75dd4e}

Followup: MachineOwner

ICIT2LOL, the data you post is pretty much the standard output from a 0x124 and in the case of a 0x124 doesn't show anything useful Have you received my PM about the 0x124? :)

With a 0x124, you can view the problem with the !errrec command on the 'Address of the WHEA_ERROR_RECORD structure'

Code:

WHEA_UNCORRECTABLE_ERROR (124)ifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8012610028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000200401, Low order 32-bits of the MCi_STATUS value

In this case it is an internal error that hasn't been documented publicly (internal unclassified), this means that we have to go back to the standard troubleshooting process for the 0x124. Fortunately this standard troubleshooting process does often find the root cause in a 0x124 :)
I would suggest to read the instructions below.

Code:

4: kd> !errrec fffffa8012610028
===============================================================================
Common Platform Error Record @ fffffa8012610028
-------------------------------------------------------------------------------
Record Id     : 01d137701e64e2c2
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 12/15/2015 20:01:29 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa80126100a8
Section       @ fffffa8012610180
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  : 0x0000000000000004

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa80126100f0
Section       @ fffffa8012610240
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000004
CPU Id        : e3 06 05 00 00 08 10 04 - 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

Proc. Info 0  @ fffffa8012610240

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa8012610138
Section       @ fffffa80126102c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : Internal unclassified (Proc 4 Bank 1)
  Status      : 0xbf80000000200401
  Address     : 0x00000000fee00040
  Misc.       : 0x0000000000000086

STOP 0x124 Troubleshooting

Read carefully before proceeding.

   Warning

If you're overclocking your system, revert back to stock clocks now.

   Note

Test the system once the overclock is removed before continuing with the steps outlined below.

Part One: CPU Stress Test
Part Two: MemTest86+ RAM Diagnostic
Part Three: Hard Drive Diagnostics
Part Four: GPU Stress Test

ONE

 CPU TEST

Run Prime95 to stress test your CPU. Prime95 - Stress Test Your CPU - Windows 7 Help Forums

   Warning

Your CPU temperatures will rise quickly while under this stress test. Keep a keen eye on them and abort the test if overheating occurs.

TWO

 RAM TEST

Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 7 Help Forums

   Note

MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

THREE

 HDD TEST

Run SeaTools to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums

   Note

Do not run SeaTools on an SSD as the results will be invalid.

Run chkdsk
Disk Check - Windows 7 Help Forums

Run HDTune to

• scan for errors, no quick scan but full scan
• check the health,
• benchmark.

It may take some time, but please take the time you need to perform it properly.
Let me know what the results are

• of the error scan,
• make a screenshot of the health of every hard drive and post the screenshots,
• post screenshots with the benchmark of the
  
  • transfer rate,
  • access time,
  • burst rate,
  • cpu usage.

FOUR

 GPU TEST

Run Furmark to stress test your GPU. FurMark - GPU Stress Test - Windows 7 Help Forums

   Note

Run Furmark for around 30 minutes.

   Warning

Your GPU temperatures will rise quickly while Furmark is running. Keep a keen eye on them and abort the test if overheating occurs.

A fatal hardware error has occurred. Parameter 1 ident

Forum inbox for what exactly?

You can run HDTune and chkdsk on the SSHD.

That was meant to ICIT2LOL