Windows randomly blue screens

[DrDeimos]

So I came home today to find my computer had blue screened around 2:25pm according to the event log. This has happened before about four days ago but nothing since till again today. Can someone please help me figure this out not sure what to do to fix it

The error is as follows : The computer has rebooted from a bugcheck.

The bugcheck was: 0x00000124 (0x0000000000000000, 0xfffffa801e93b028, 0x00000000bf800000, 0x0000000000200401). A dump was saved in: C:\Windows\Minidump\072115-15381-01.dmp. Report Id: 072115-15381-01.

I did rebuild my system with a new mobo and cpu in May of this year. I have tested the memory sticks on my system with the windows memory test tool and it came back negative for errors.

System spec
mobo: Gigabyte Black Edition LGA 1150 Intel Z97 Z97X-UD5H-BK
cpu: i7-4790K
ram: 32gb

link to mini dump:
https://www.dropbox.com/s/momn2ea8n7vkkzg/072115-15381-01.dmp?dl=0

 

[Wile E Coyote]

Stop 0x124 - what it means and what to try

This is a hardware issue, give as much detail as possible.

STOP 0x00000124: WHEA_UNCORRECTABLE_ERROR
Usual causes: Hardware, Incompatibility, May be driver corruption
This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA)

The dump file blames the GenuineIntel_PROCESSOR_CACHE

Your CPU may or may not be to blame.
Run Prime95 to test your CPU.
CPU - Stress Test with Prime95
http://www.majorgeeks.com/files/details/prime95.html

Select the Small FFTs test.
Enter the amount of cores for your CPU.
In Advanced tab select 'Round off checking'.
Use Real Temp , to check the CPU temps when at idle, under load and/or testing.
Tell us what the idle temp is, Don't go over 72°C, this is the Intel recommended max CPU core temp.

Some of your drivers should be updated.

I would try Iobits Driver Booster.http://www.majorgeeks.com/mg/getmirror/iobit_driver_booster,2.html it will find the latest drivers for your system.

 

[DrDeimos]

So I ran the driver update tool and it updated the chipset and some other intel related drivers. I tried to run the Prime95 but well the second after I turned it on the cpu sky rockets to 85C and then 90 so I cant let it it run. So I tried the intel cpu test tool which the cpu at 100% for 20 min it sits at 62C . First run nothing happened during the short burn. Then about 5 min later the computer crashed. Looked at the log and same as before cpu kernal. I also noted that my VMware Workstation was having errors as well about the same time and at about the same time as this after noon. I uninstalled it as technically it access the cpu when a VM is running but none were at the time but I uninstalled it any ways. As it was having errors right before the system log registered the crash both today and on the 17th.

Ran the burn test again with the Intel tool and again finished fine with no errors reported and so far the computer has not crashed.
here is the most recent dump report https://www.dropbox.com/s/8ye7xwke2ujuxxa/072115-288898-01.dmp?dl=0

Stop 0x124 - what it means and what to try

This is a hardware issue, give as much detail as possible.

STOP 0x00000124: WHEA_UNCORRECTABLE_ERROR
Usual causes: Hardware, Incompatibility, May be driver corruption
This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA)

The dump file blames the GenuineIntel_PROCESSOR_CACHE

Your CPU may or may not be to blame.
Run Prime95 to test your CPU.
CPU - Stress Test with Prime95
http://www.majorgeeks.com/files/details/prime95.html

Select the Small FFTs test.
Enter the amount of cores for your CPU.
In Advanced tab select 'Round off checking'.
Use Real Temp , to check the CPU temps when at idle, under load and/or testing.
Tell us what the idle temp is, Don't go over 72°C, this is the Intel recommended max CPU core temp.

Some of your drivers should be updated.

I would try Iobits Driver Booster.http://www.majorgeeks.com/mg/getmirror/iobit_driver_booster,2.html it will find the latest drivers for your system.

 

[Wile E Coyote]

Let's give it a day or two too see if it crashes.

And if it does not then it should be fine.

Then make sure you click the solution solved.So others don't join in unless they have the same kinda issue.

 

[DrDeimos]

So I thought the problem was solved but then today again after playing some elite dangerous and wows I walked away and went into the kitchen. Was gone maybe 15 min walked back to the pc which was doing nothing to watch it blue screen and restart just as I walked into the room. error messages follow:

A fatal hardware error has occurred.

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

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xfffffa801b3c5028, 0x00000000bf800000, 0x0000000000200401).

Link to minidump
https://www.dropbox.com/s/tsf7a40dut2pqre/080215-15537-01.dmp?dl=0

So is this a bad CPU core then that randomly hits the bad spot at idle and crashes or something else?

 

[Wile E Coyote]

So I thought the problem was solved but then today again after playing some elite dangerous and wows I walked away and went into the kitchen. Was gone maybe 15 min walked back to the pc which was doing nothing to watch it blue screen and restart just as I walked into the room. error messages follow:

A fatal hardware error has occurred.

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

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xfffffa801b3c5028, 0x00000000bf800000, 0x0000000000200401).

Link to minidump
https://www.dropbox.com/s/tsf7a40dut2pqre/080215-15537-01.dmp?dl=0

So is this a bad CPU core then that randomly hits the bad spot at idle and crashes or something else?

I have been busy.

Ok i would recommend on double checking your CPU to make sure it is in the slot correctly and add little bit of thermal past.To see what happens.

 

[Paul NZ]

Update the BIOS too. If you can update it in the BIOS update it there. Not in Windows

Altho the 0x124 stop error is ntoskrnl.exe not hal.dll

See if there's an update for your Acronis program. Its 4 yrs old. This file afcdp.sys is 4 yrs old

This file is also old wdcsam64.sys from 2008. Western digital drivers for something

See if there's an update for both of them. Old drivers can crash windows

Wouldnt be surprised if your Symantec program is causing it

Your Logitech GamePanel Virtual Bus Enumerator Drivers are also old from 2009

Its possible this file is causing this CORK70.sys. Something that may belong to Corsair gaming or something