Getting Random BSOD with some frequency

[UsDeadPool]

I am not doing anything particular when my system crashes. I have not been able to duplicate any forced crashes to narrow down the culprit. I have run prime95 for 20 or so min to stress test my cpu to see if there is an issue there and it ran no problem. I have run memtest to verify no issues there. I have just run check disk on my mechanical HDD's and it found no issues. I am officially stuck at this point as to what is causing my issues and I cannot get the windows debugger tool to work due to being unable to find the right symbols. Any help would be great. The dumb thing has crashed 5 times in the last 48 hours. Any help would be greatly appreciated. Thank you in advance

 

 

You can find a rar files with the last 3 dump files made in the last 48 hours at this link.

https://mega.co.nz/#!a8QC2YwJ!TQjFDsIjAJk84B8aH8LXXdKxXVgag2ke--DLPzlf7U4

[CoolaxGaming]

Which cpu u have

[UsDeadPool]

i7 4770k I do not have it over clocked either

[JeffreyEagan]

All of these BSOD's are caused by HAL.dll and NTOSKRNL.exe.

 

HAL is your hardware abstraction layer while NTOSKRNL is basically the kernel of the OS.

 

bug check 0x124 is a WHEA_UNCORRECTABLE_ERROR, basically meaning it could be a number of different things.

 

Try working through this list: http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

 

Also, this BSOD can be caused by underclocking, so make sure you aren't tweaking any voltage settings or multipliers.

[Enderman]

http://www.tomshardware.com/answers/id-2209014/bsod-ntoskrnl-exe-windows.html

http://www.windowsanswers.net/articles/fix-dll-errors?tid=dllgoogdco&p2=^SW1^xdm123&gclid=CL_v7PLqvsMCFc9lfgodhi4A6Q

[UsDeadPool]

I did see that the issues are caused by hal.dll and the NTOSKRNL.exe I have not been able to find out a cause or a solution. The NTOSKRNL is the windows kernel and the hal.dll file from what I can see is a hold over from windows xp. I have not found anything suggesting a resolution unless I have been overlooking them.

[JeffreyEagan]

I did see that the issues are caused by hal.dll and the NTOSKRNL.exe I have not been able to find out a cause or a solution. The NTOSKRNL is the windows kernel and the hal.dll file from what I can see is a hold over from windows xp. I have not found anything suggesting a resolution unless I have been overlooking them.

HAL is the hardware abstraction layer, it's somewhat needed in any sort of OS.

[UsDeadPool]

HAL is the hardware abstraction layer, it's somewhat needed in any sort of OS.

My mistake then thanks for clarifying that.

[JeffreyEagan]

My mistake then thanks for clarifying that.

Look up to my first post, work through that.

[UsDeadPool]

Look up to my first post, work through that.

I am working on that now. Doing the driver updates as I type. Thanks much so far

[JeffreyEagan]

I am working on that now. Doing the driver updates as I type. Thanks much so far

No problem, that's what we're here for.