BSOD Bug Check 124 hal.sys ntkrpamp.exe

[banditv1]

Hello,
I am new to the forums.
Suddenly I have started experiencing random BSODs related to Bug Check 124 hal.sys ntkrpamp.exe.
Troubleshooting I have tried already.
1. Reloaded the system updated drivers, verified the newest version of the BIOS was installed, and verified all drivers are signed.
2. Removed all components down to the hard drive.
3. Scanned the memory with memtest+
4. Checked the hard drive for bad sectors.
5. Ran calculations stress tests on the CPU max temp reached 54 C.
6. Clean install windows only.

The system was running without any issues then suddenly the BSODS started.
I suspect the system board or the CPU may be failing, however I am not one to quit until I know what's wrong before give in to spending money.
Any help will be greatly appreciated.

Below is the who crashed log and I have uploaded the additional requested information.


On Sun 2/8/2015 4:28:55 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020715-62618-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlpa.exe[/FONT] (nt+0x40B7F)
Bugcheck code: 0xA (0xFFFFFFFF80B82654, 0xFF, 0x0, 0xFFFFFFFF82ACD43C)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\ntkrnlpa.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



[FONT=Segoe UI, Arial]On Sun 2/8/2015 4:28:55 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrpamp.exe[/FONT] (nt!Kei386EoiHelper+0x28B7)
Bugcheck code: 0xA (0xFFFFFFFF80B82654, 0xFF, 0x0, 0xFFFFFFFF82ACD43C)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ntkrpamp.exe .
Google query: [FONT=Segoe UI, Arial]ntkrpamp.exe IRQL_NOT_LESS_OR_EQUAL[/FONT]


[/FONT]
[FONT=Segoe UI, Arial]On Sun 2/8/2015 2:26:44 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020715-20560-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]hal.sys[/FONT] (hal+0xEFCD)
Bugcheck code: 0x124 (0x0, 0xFFFFFFFF86061024, 0xFFFFFFFFB6122000, 0x136)
Error: [FONT=Segoe UI, Arial]WHEA_UNCORRECTABLE_ERROR[/FONT]
Bug check description: 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).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: hal.sys .
Google query: [FONT=Segoe UI, Arial]hal.sys WHEA_UNCORRECTABLE_ERROR[/FONT]


[/FONT]
[FONT=Segoe UI, Arial]On Sat 2/7/2015 2:39:43 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020715-17472-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]hal.sys[/FONT] (hal+0xEFCD)
Bugcheck code: 0x124 (0x0, 0xFFFFFFFF85FDF1E4, 0xFFFFFFFFB6000000, 0x181)
Error: [FONT=Segoe UI, Arial]WHEA_UNCORRECTABLE_ERROR[/FONT]
Bug check description: 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).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: hal.sys .
Google query: [FONT=Segoe UI, Arial]hal.sys WHEA_UNCORRECTABLE_ERROR[/FONT]


[/FONT]
[FONT=Segoe UI, Arial]On Sat 2/7/2015 1:10:08 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020715-17768-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlpa.exe[/FONT] (nt+0x415CB)
Bugcheck code: 0xA (0xFFFFFFFF8CE89A00, 0x2, 0x0, 0xFFFFFFFF828998D8)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\ntkrnlpa.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Sat 2/7/2015 11:38:43 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020715-19250-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]hal.sys[/FONT] (hal+0xEFCD)
Bugcheck code: 0x124 (0x0, 0xFFFFFFFF85F6E1E4, 0xFFFFFFFFF613A000, 0x136)
Error: [FONT=Segoe UI, Arial]WHEA_UNCORRECTABLE_ERROR[/FONT]
Bug check description: 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).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: hal.sys .
Google query: [FONT=Segoe UI, Arial]hal.sys WHEA_UNCORRECTABLE_ERROR[/FONT]


[/FONT]
[FONT=Segoe UI, Arial]On Sat 2/7/2015 11:28:58 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020715-19671-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]hal.sys[/FONT] (hal+0xEFCD)
Bugcheck code: 0x124 (0x0, 0xFFFFFFFF85EAE1E4, 0xFFFFFFFFF6002000, 0x17A)
Error: [FONT=Segoe UI, Arial]WHEA_UNCORRECTABLE_ERROR[/FONT]
Bug check description: 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).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: hal.sys .
Google query: [FONT=Segoe UI, Arial]hal.sys WHEA_UNCORRECTABLE_ERROR[/FONT]
[/FONT]
[FONT=Segoe UI, Arial]2 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers: [FONT=Segoe UI, Arial]hal.sys [/FONT][FONT=Segoe UI, Arial]ntkrpamp.exe [/FONT]

[/FONT]

 

[Golden]

0x124's are typically related to a hardware issue and can only be isolated by stress testing the major components. I realise you may have already done some of this, but our experience is they have to be run a certain way. Please see suggestions below:

If overclocking, reset all overclocks back to their default settings and then follow these:

RAM - run for a minimum of 8 consecutive passes
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

CPU - run the HIGH test
http://www.sevenforums.com/tutorials/220743-cpu-stress-test-using-intelburntest.html

Video - run the FURMARK test for 20mins
http://www.sevenforums.com/tutorials/330579-graphics-card-problems-diagnose.html
http://www.sevenforums.com/tutorials/100356-video-card-stress-test-furmark.html

Storage - run the SHORT test using the DOS version
http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html

 

[banditv1]

Golden,
As you requested I have run the listed tests.
Memtest ran over night no failures.
CPU Test results I cannot run the high test because the system has 2 gigs of memory I ran the standard test
Time (s) 133.455 Speed (GFlops)6.6980 Result 3.265950e-002
Time (s) 132.507 Speed (GFlops)6.7459 Result 3.265950e-002
FurMark test no artifacts Temp leveled out at 80 C
Segate tools Drive passed all tests.

The system BSODed again while running idle.
Attached a new report and here is the whocrashed report as well.

On Sun 2/8/2015 6:46:32 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020815-34367-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]cng.sys[/FONT] (cng+0x615E)
Bugcheck code: 0xA (0xFFFFFFFF8E351A00, 0x2, 0x0, 0xFFFFFFFF82CC0EBE)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\drivers\cng.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Kernel Cryptography, Next Generation
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time

 

[banditv1]

Here is some updated information.
Every time I try to watch a you tube video in IE 11. The system will hard freeze and have to be powered down.
I have had no issues browsing the web or posting on this forum.

I have verified I have all the latest video drivers, flash player, java, and have reset IE 11 to the default.
I hope this additional information will help with the diagnostics.

 

[banditv1]

Additional information.