Hal.dll and ntoskrnl.exe causing bsod

[howzitkiffen]

I've combed the internet and several people have the same problem with the same motherboard, but none of the things listed has helped me pin down a culprit. Im getting whea_uncorrectable_error anywhere from 10 seconds to 1hr after startup.

Windows 10 home
I7 2600
Gskill ripjaw 1600 ddr3 16gb
Gtx1080

I've run memtest with no errors I've also tried each stick of RAM in various configurations. I've also tried running with just one condense swapping out to see if maybe that was the problem. I ran Intel's testing software on my processor it passed all tests. It's also liquid cooled so not running hot. I ran without my graphics card and still BSOD.
I also flashed my BIOS and reinstalled windows with the latest version on a different SSD which I'm now using. I've updated most of my drivers using a driver utility but I have no way of knowing that they're the correct ones.

One thing to note is that it's not crashing in safe mode.

also worthy of note it absolutely does not crash unless I'm in the operating system. If I'm in the Bios or doing a Windows installation( which I've Done 3 times now) it does not crash.

 

[Colif]

1. Can you download and run who crashed - it will give us a glimpse of the errors you getting and might help us solve them

Copy/paste summary in here and I see what I can do

Hal.dll = hardware abstraction layer: its part of windows that talks direct to hardware
ntoskrnl = New Technology Operating System Kernel. Brains of Windows.

Those 2 file names don't tell me enough to know what problem is, as 2nd is blamed for lots of different errors such as memory errors or Driver errors. So the who crashed report will at least tell me what errors you are getting

if you do the next part, it will show more info, I just can't read the dumps myself

2. Can you follow option one here: http://www.tenforums.com/tutorials/5560-bsod-minidump-configure-create-windows-10-a.html
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c windows/minidump
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it

 

[howzitkiffen]

1. Can you download and run who crashed - it will give us a glimpse of the errors you getting and might help us solve them

Copy/paste summary in here and I see what I can do

Hal.dll = hardware abstraction layer: its part of windows that talks direct to hardware
ntoskrnl = New Technology Operating System Kernel. Brains of Windows.

Those 2 file names don't tell me enough to know what problem is, as 2nd is blamed for lots of different errors such as memory errors or Driver errors. So the who crashed report will at least tell me what errors you are getting

if you do the next part, it will show more info, I just can't read the dumps myself

2. Can you follow option one here: http://www.tenforums.com/tutorials/5560-bsod-minidump-configure-create-windows-10-a.html
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c windows/minidump
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it

ok let me see what i can do

 

[howzitkiffen]

ok it says:
On Sun 6/4/2017 2:51:36 AM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalBugCheckSystem+0xCF)
Bugcheck code: 0x124 (0x0, 0xFFFF8D0DF8991028, 0xB2000000, 0x10019)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
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. This problem might also be caused because of overheating (thermal issue).
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.

This is pretty much what bluescreen viewer said.
But it does have this one thats different


On Sun 6/4/2017 2:46:02 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\060417-12062-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR

ill follow your tutorial and see what else I can find.

 

[Colif]

Windows Hardware error Architecture (WHEA) errors are Hardware but can be caused by drivers sometimes, the Dump might help us narrow down the cause more, as it could be anything.

the custom error is a bug with who crashed, dump should know what it is.

 

[howzitkiffen]

how do I attach files? It's not giving me the option.

 

[howzitkiffen]

ok the pc keeps crashing but i have all the mini dump files saved to one drive, so as soon as i figure out how to upload them with toms hardware i can post them.

 

[howzitkiffen]

Windows Hardware error Architecture (WHEA) errors are Hardware but can be caused by drivers sometimes, the Dump might help us narrow down the cause more, as it could be anything.

the custom error is a bug with who crashed, dump should know what it is.

OK i have the link to all the files https://www.dropbox.com/sh/19c2rgypbbz0a8z/AAASfe_hx3kBZHEOyNNBL6dna?dl=0
they are in this drop box. THANK YOU so much for your help.

 

[gardenman]

Hi howzitkiffen, I downloaded and viewed the dump files in the MS debugger and here are the results: https://pastebin.com/pmQUDLpL

Additional commands tried after I pasted to pastebin:

Spoiler

7: kd> !whea
Error Source Table @ fffff802b09364a0
0 Error Sources

7: kd> !errpkt fffff802b09364a0
Unable to locate symbol for nt!WHEA_ERROR_PACKET

7: kd> !errpkt ffffc908ad106028
Unable to locate symbol for nt!WHEA_ERROR_PACKET

You had the error: [WHEA_UNCORRECTABLE_ERROR (124)] This bug check is typically related to physical hardware failures. It can be heat related, defective hardware, memory or even a processor that is beginning to fail or has failed. If over-clocking has been enabled, try disabling it. Confirm that any cooling systems such as fans are functional. Run system diagnostics to confirm that the system memory is not defective. It is less likely, but possible that a driver is causing the hardware to fail with this bug check.

Only 1 of the dump files were valid minidump files, or it could be that my Debugger could just only read 1 of the files. I tried them all. [Here] is what it kept telling me. I've never seen this problem before.

I can't help you with this, wait for Colif or someone else to reply. Good luck.

 

[howzitkiffen]

yeah i already tested the memory, the processor, the gpu, ruled out the harddrive. the only thing i can imagine left would be mobo. I may just need to buy a new one.

 

[howzitkiffen]

still no closer

 

[Colif]

EVENT_WHEA_TLB_ERROR: Translation lookaside buffer machine check exception. - need to work out what this

A Translation lookaside buffer (TLB) is a memory cache that is used to reduce the time taken to access a user memory location.[1][2] It is a part of the chip’s memory-management unit (MMU). The TLB stores the recent translations of virtual memory to physical memory and can be called an address-translation cache. A TLB may reside between the CPU and the CPU cache, between CPU cache and the main memory or between the different levels of the multi-level cache. The majority of desktop, laptop, and server processors include one or more TLBs in the memory management hardware, and it is nearly always present in any processor that utilizes paged or segmented virtual memory.

https://en.wikipedia.org/wiki/Translation_lookaside_buffer

go through these steps and swap Windows 10 for windows 7 on step 7: https://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html#post354696

A few old drivers there you might want to see if any upgrades, not likely to be on motherboard site though

ISCTD64.sys Tue Nov 27 14:52:34 2012 (50B51A02)
Intel Smart Connect Technology Driver Info here: http://www.intel.com/p/en_US/support/highlights/sftwr-prod/smrt_cnct
available at Intel Download Center: https://downloadcenter.intel.com/SearchResult.aspx?lang=eng&keyword=Intel%20Smart%20Connect
http://www.carrona.org/drivers/driver.php?id=ISCTD64.sys

TeeDriverW8x64.sys Tue Jul 7 13:43:32 2015 (559C0FC4)
Intel Management Engine Interface http://downloadcenter.intel.com
http://www.carrona.org/drivers/driver.php?id=TeeDriverW8x64.sys

 

[howzitkiffen]

EVENT_WHEA_TLB_ERROR: Translation lookaside buffer machine check exception. - need to work out what this

A Translation lookaside buffer (TLB) is a memory cache that is used to reduce the time taken to access a user memory location.[1][2] It is a part of the chip’s memory-management unit (MMU). The TLB stores the recent translations of virtual memory to physical memory and can be called an address-translation cache. A TLB may reside between the CPU and the CPU cache, between CPU cache and the main memory or between the different levels of the multi-level cache. The majority of desktop, laptop, and server processors include one or more TLBs in the memory management hardware, and it is nearly always present in any processor that utilizes paged or segmented virtual memory.

https://en.wikipedia.org/wiki/Translation_lookaside_buffer

go through these steps and swap Windows 10 for windows 7 on step 7: https://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html#post354696

A few old drivers there you might want to see if any upgrades, not likely to be on motherboard site though

ISCTD64.sys Tue Nov 27 14:52:34 2012 (50B51A02)
Intel Smart Connect Technology Driver Info here: http://www.intel.com/p/en_US/support/highlights/sftwr-prod/smrt_cnct
available at Intel Download Center: https://downloadcenter.intel.com/SearchResult.aspx?lang=eng&keyword=Intel%20Smart%20Connect
http://www.carrona.org/drivers/driver.php?id=ISCTD64.sys

TeeDriverW8x64.sys Tue Jul 7 13:43:32 2015 (559C0FC4)
Intel Management Engine Interface http://downloadcenter.intel.com
http://www.carrona.org/drivers/driver.php?id=TeeDriverW8x64.sys

QUICK update. I got a new MoBo in today, installed windows on a new drive, and bam whea_uncorrectable...also a lot of machine check exception BSoD's. I'm completely screwed. My entire business was on that computer..... I'm GOING to lose everything i have. It's completely bricked up. Anything INSIDE the OS just causes crashes. Doesn't matter what motherboard i use nor what disk. Memtest is still testing fine on ram, and intels cpu testing software is still testing fine... I don't know what to do.

 

[howzitkiffen]

EVENT_WHEA_TLB_ERROR: Translation lookaside buffer machine check exception. - need to work out what this

A Translation lookaside buffer (TLB) is a memory cache that is used to reduce the time taken to access a user memory location.[1][2] It is a part of the chip’s memory-management unit (MMU). The TLB stores the recent translations of virtual memory to physical memory and can be called an address-translation cache. A TLB may reside between the CPU and the CPU cache, between CPU cache and the main memory or between the different levels of the multi-level cache. The majority of desktop, laptop, and server processors include one or more TLBs in the memory management hardware, and it is nearly always present in any processor that utilizes paged or segmented virtual memory.

https://en.wikipedia.org/wiki/Translation_lookaside_buffer

go through these steps and swap Windows 10 for windows 7 on step 7: https://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html#post354696

A few old drivers there you might want to see if any upgrades, not likely to be on motherboard site though

ISCTD64.sys Tue Nov 27 14:52:34 2012 (50B51A02)
Intel Smart Connect Technology Driver Info here: http://www.intel.com/p/en_US/support/highlights/sftwr-prod/smrt_cnct
available at Intel Download Center: https://downloadcenter.intel.com/SearchResult.aspx?lang=eng&keyword=Intel%20Smart%20Connect
http://www.carrona.org/drivers/driver.php?id=ISCTD64.sys

TeeDriverW8x64.sys Tue Jul 7 13:43:32 2015 (559C0FC4)
Intel Management Engine Interface http://downloadcenter.intel.com
http://www.carrona.org/drivers/driver.php?id=TeeDriverW8x64.sys

QUICK update. I got a new MoBo in today, installed windows on a new drive, and bam whea_uncorrectable...also a lot of machine check exception BSoD's. I'm completely screwed. My entire business was on that computer..... I'm GOING to lose everything i have. It's completely bricked up. Anything INSIDE the OS just causes crashes. Doesn't matter what motherboard i use nor what disk. Memtest is still testing fine on ram, and intels cpu testing software is still testing fine... I don't know what to do.

Also followed up on all those steps you gave me. Not sure where to go from here.

 

[Colif]

WHEA errors are created by the CPU - I am not saying caused, they are actions performed by CPU to report an error. The errors themselves can be caused by drivers in some cases, or might be reporting a physical fault of CPU itself.

what, apart from motherboard and drive is new?
can you upload the dump files again as I might get someone else to look at them