BSOD whea_uncorrectable_error hal.dll+37213 and ntoskrnl

Zeales · Jan 19, 2015

As the title states I'm getting a whea_uncorrectable_error bsod.

According to BlueScreenViewer it's these:

hal.dll+37213
ntoskrnl.exe+1c6699

I have found the hal.dll error on the forums but not even google show a result for the ntoskrnl.exe error.

I have recently upgraded my computer with new CPU, motherboard and PSU. It seems like the error occurs when I put stress on my computer.

I have tried the following things:
Resetting my BIOS to factory default
Run FurMark with no crash
Run Intel Processor Diagnostic Tool 64 bit with no crash
Run 2 passes on memtest86
Run a chkdisk with no errors

I was suspecting my PSU was making the error but it's a 850 Watt Corsair CPU which should be more than enough to run my hardware so I'm guessing it could be faulty?

Here is my DM log:
https://mega.co.nz/#!J4tTwbrb!K6jGrJ823SwG-5ey_bXlpGCi61mZdSAn9zVdG-4JIuk

blueelvis · Jan 22, 2015

Hi Zeales & Welcome to the forums ^_^,

I have analysed your dump files and below has been provided an analysis of the same for informative purposes :-

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred.

Code:

1: kd> !errrec ffffe00172751028
===============================================================================
Common Platform Error Record @ ffffe00172751028
-------------------------------------------------------------------------------
Record Id     : 01d02c1d21ee7ad2
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 1/11/2015 3:59:38 (UTC)
Flags         : 0x00000000


===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ ffffe001727510a8
Section       @ ffffe00172751180
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal


Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Cache error
Operation     : Generic
Flags         : 0x00
Level         : 2
CPU Version   : 0x00000000000306c3
Processor ID  : 0x0000000000000001


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


Local APIC Id : 0x0000000000000001
CPU Id        : c3 06 03 00 00 08 10 01 - 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  @ ffffe00172751240


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


[COLOR=#ff0000][B][U]Error         : GCACHEL2_ERR_ERR (Proc 1 Bank 8)[/U][/B][/COLOR]
  Status      : 0xbe0000000100110a
  Address     : 0x0000000048d6b380
  Misc.       : 0x0000001080000086

So, according to the dump files, the system experienced a crash due to hardware fault. On scrolling below in the above code part, you will see that I have highlighted the error. It seems that there was an error in L2 Cache of the Processor. The cache at fault is consistent in the dump files having 0x124.

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.

Code:

2: kd> .bugcheck
Bugcheck code 0000000A
Arguments 00000000`00000010 00000000`00000002 00000000`00000001 [COLOR=#0000ff]fffff800`3a041c38[/COLOR]

Code:

2: kd> !address [COLOR=#0000ff]fffff800`3a041c38[/COLOR]
Mapping user range ...
Mapping system range ...
Mapping non addressable range ...
Mapping page tables...
Mapping hyperspace...
Mapping HAL reserved range...
Mapping User Probe Area...
Mapping system shared page...
Mapping system cache working set...
Mapping loader mappings...
Mapping system PTEs...
Mapping system paged pool...
Mapping session space...
Mapping dynamic system space...
Mapping PFN database...
Mapping non paged pool...
Mapping VAD regions...
Mapping module regions...
Mapping process, thread, and stack regions...
Mapping system cache regions...




Usage:                  
Base Address:           fffff800`00000000
End Address:            fffff800`3a35b0ff
Region Size:            00000000`3a35b0ff
[B][U][COLOR=#ff8c00]VA Type:                BootLoaded[/COLOR][/U][/B]
VAD Address:            0x27676e69727473
Commit Charge:          0x100000003
Protection:             0x7ffc55aba2f0 []
Memory Usage:           Private
No Change:              yes
More info:              !vad 0xfffff80000000000

There was another bugcheck which was due to accessing invalid memory. Furthermore, the address which referred to the invalid memory, it was Bootloaded which means that it was a part of the Operating System. This is generally seen in the case of bad hardware.

Kindly perform the Free hardware diagnostics (Prime95 first) at the link - Hardware Diagnostics

Also remove ASUS Bloatware and physically disconnect RAZER devices present on the system as it is known to cause problems.

Let me know how it goes ^_^

-Pranav

Zeales · Jan 22, 2015

Hi blueelvis

I just ran the Prime95 test for 30 minutes and it appears that my CPU is getting very warm.

Here is a picture of the Core Temp readings I got: http://i.imgur.com/3WgTy9q.png

I do not know how reliable Core Temp is, but in any case I'm going to remove my CPU fan and re-apply some more CPU paste. If this does not fix the issue, I'm going to try out another CPU fan that isn't the standard Intel fan.
It should be noted that I have not overclocked the CPU.

blueelvis · Jan 25, 2015

Hi Zeales ^_^,

Yes, the readings are extremely hot. I use CoreTemp and I haven't had a problem with it. Although, I have seen some users having a problem with it. I hope the temperatures are not 99 Degree Celsius as soon as you start CoreTemp. If that's the case, kindly re-run Prime95 and use HWInfo to monitor temperatures.

Let me know how it goes with re-applying the thermal paste. You can also place a table fan aiming directly at the CPU and see if the temperatures remain stable or not ^_^.

-Pranav

Zeales · Jan 25, 2015

Hi blueelvis

It is not. It is while I am I am running Prime95.

You are correct in that Core Temp does not measure the temperature accurately - HWInfo appears to be doing that though.
What I have found out is that while my CPU is not running 95-100 degrees, it is still running at high 80s to low 90s when I push it to full load. I have not had time to find new cooler paste but it should happen next weekend. I will of course post again when I have tested that.

blueelvis · Jan 30, 2015

Zeales said:
Hi blueelvis

It is not. It is while I am I am running Prime95.

You are correct in that Core Temp does not measure the temperature accurately - HWInfo appears to be doing that though.
What I have found out is that while my CPU is not running 95-100 degrees, it is still running at high 80s to low 90s when I push it to full load. I have not had time to find new cooler paste but it should happen next weekend. I will of course post again when I have tested that.

Hi Zeales ^-^,

That is very high as well. Let me know how it goes once you get a new thermal paste ^_^

-Pranav

Zeales · Jan 30, 2015

I have just added new thermal paste and these are the results during a Prime95 small FFTs test from HWiNFO64.

http://i.imgur.com/vnFysMe.png

[DEL]Looks bad - I'll see if I can force a BSOD over the next few hours or if these thermal readings are way off.[/DEL]

Nop, I just forced another BSOD from opening 5-7 Twitch.tv streams. It was hitting roughly high 80s low 90s when it happened.

Despite running the Prime95 test for an hour, I still haven't been able to force a BSOD from it. I guess I need to try to run it longer. I'll try that after I've pulled out all my hair.

blueelvis · Jan 30, 2015

The CPU is still very hot. Could you try placing a table fan aiming directly at the CPU and then see if the system is stable or not? You need to get this overheating issue straightened up before we can test further because this would always interfere with something and probably give us wrong results.

Let me know how it goes ^_^

-Pranav

Zeales · Jan 30, 2015

Here's the BSOD crash dump.

https://mega.co.nz/#!lpUGABjK!461gUOpaLaxwdbNHffMM0bdDfTZRRqC5hC94MJ_dRo8

Looks like the same error as previously.

blueelvis · Feb 4, 2015

Hi Zeales ^_^,

I have analysed your dump files and below has been provided an analysis of the same for informative purposes :-

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred.

Code:

3: kd> !errrec ffffe001a2ae0028
===============================================================================
Common Platform Error Record @ ffffe001a2ae0028
-------------------------------------------------------------------------------
Record Id     : 01d03cafba65b9b3
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 1/30/2015 17:29:46 (UTC)
Flags         : 0x00000000
===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ ffffe001a2ae00a8
Section       @ ffffe001a2ae0180
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal
Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Cache error
Operation     : Generic
Flags         : 0x00
Level         : 2
CPU Version   : 0x00000000000306c3
Processor ID  : 0x0000000000000003
===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ ffffe001a2ae00f0
Section       @ ffffe001a2ae0240
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal
Local APIC Id : 0x0000000000000003
CPU Id        : c3 06 03 00 00 08 10 03 - 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  @ ffffe001a2ae0240
===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ ffffe001a2ae0138
Section       @ ffffe001a2ae02c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal
Error         : [COLOR=#FF0000][B][U]GCACHEL2_ERR_ERR (Proc 3 Bank 7)[/U][/B][/COLOR]
  Status      : 0xbe0000000100110a
  Address     : 0x0000000270343280
  Misc.       : 0x0000035086000086

Again we see that there is some error in the L2 Cache of the CPU.

Below is a list of 3rd party drivers present on your system -

Code:

**************************Fri Jan 30 22:59:46.416 2015 (UTC + 5:30)**************************
ElbyCDIO.sys                Fri Dec 17 04:28:13 2010 (4D0A9985)
LGSHidFilt.Sys              Sun May  8 22:30:17 2011 (4DC6CC21)
[COLOR=#FF0000][B][U]dtsoftbus01.sys             Fri Jan 13 19:15:46 2012 (4F10358A)
AsIO.sys                    Wed Aug 22 15:24:47 2012 (5034AC67)
[/U][/B][/COLOR]CSCrySec.sys                Fri Nov 30 19:07:39 2012 (50B8B6A3)
CSVirtualDiskDrv.sys        Fri Nov 30 19:08:38 2012 (50B8B6DE)
klwfp.sys                   Wed Feb 27 14:18:31 2013 (512DC85F)
npf.sys                     Fri Mar  1 07:01:24 2013 (513004EC)
kneps.sys                   Tue Mar  5 14:39:23 2013 (5135B643)
klim6.sys                   Thu Jul 11 13:23:56 2013 (51DE6494)
klkbdflt.sys                Thu Aug  8 18:38:54 2013 (52039866)
klmouflt.sys                Thu Aug  8 18:39:08 2013 (52039874)
intelppm.sys                Thu Aug 22 14:16:35 2013 (5215CFEB)
kl1.sys                     Fri Oct 18 14:48:22 2013 (5260FCDE)
klflt.sys                   Tue Nov 26 18:07:39 2013 (52949613)
asstor64.sys                Fri Mar 14 09:08:20 2014 (532279AC)
e1d64x64.sys                Fri Mar 14 23:40:25 2014 (53234611)
[COLOR=#0000FF][B][U]rzpmgrk.sys                 Fri Apr 18 01:06:12 2014 (53502D2C)
[/U][/B][/COLOR]dump_iaStorA.sys            Sat May  3 04:36:56 2014 (53642510)
iaStorA.sys                 Sat May  3 04:36:56 2014 (53642510)
klif.sys                    Fri May 16 22:00:24 2014 (53763D20)
RTKVHD64.sys                Thu Aug 21 15:42:44 2014 (53F5C61C)
nvhda64v.sys                Thu Oct  9 22:32:27 2014 (5436BFA3)
[COLOR=#0000FF][B][U]rzpnk.sys                   Sat Oct 18 01:08:10 2014 (54417022)
[/U][/B][/COLOR]nvvad64v.sys                Thu Nov 20 21:03:54 2014 (546E09E2)
HWiNFO64A.SYS               Sun Nov 23 21:54:07 2014 (54720A27)
[COLOR=#0000FF][B][U]rzendpt.sys                 Tue Dec 30 15:02:47 2014 (54A2713F)
rzudd.sys                   Tue Dec 30 15:02:50 2014 (54A27142)
[/U][/B][/COLOR]nvlddmkm.sys                Sat Jan 10 03:52:06 2015 (54B0548E)
NvStreamKms.sys             Mon Jan 12 23:26:42 2015 (54B40ADA)

Please remove any ASUS Bloatware (Like ASUS PC Probe Utility) present on the system as it is known to cause problems.
Please remove Daemon Tools since it is also known to cause BSODs.
Please physically disconnect any/all Razer Devices attached to the system as they are known to cause BSODs.

If your temperatures are still hot, make sure there is sufficient airflow inside the system. If you are still facing the errors, I would point the finger towards your CPU being damaged.

Let me know how it goes ^_^

-Pranav

BSOD whea_uncorrectable_error hal.dll+37213 and ntoskrnl

New Member

My Computer

OMG Debugger!

My Computer

New Member

My Computer

OMG Debugger!

My Computer

New Member

My Computer

OMG Debugger!

My Computer

New Member

My Computer

OMG Debugger!

My Computer

New Member

My Computer

OMG Debugger!

My Computer