BSOD, hal.dll+37203, WHEA_UNCORRECTABLE_ERROR

Leeb · Jun 22, 2014

Hello Everyone,

I do greatly apologize for bothering you all however i am come to a complete stop in trying to diagnose why my system is blue screening.

All hardware is at STOCK voltages and configurations, It was overclocked however as i couldn't get it to run stable i removed the OC.

This error normally happens when FLASH or JAVA to some extent is running, it can sometimes happen in games.

I have some monitoring software on my machine to control all the water cooling, i have heard that some monitor software which monitors hardware level sensors can cause such bluescreens to occur however i need to know what's the exact cause to the faulting module.

Is it possible anyone could analyse my dumps please.

I've used SF Diagnostic Tool to generate the RAR.

Many many Thanks, look forward to hearing from you.

Best Regards!

blueelvis · Jun 22, 2014

Hi Leeb & Welcome to the forums ^_^,

Please edit your post to remove the Skype username and the line stating that you are willing to pay for further support as you maybe contacted by a hacker as well to install spying software and all.
So, please remove that as this forum can be read by anyone without logging in.

As far as your dump files are concerned, you should expect a reply from me within an hour or so.(Currently busy troubleshooting my own desktop

)

Leeb · Jun 22, 2014

I've edited the post, very sorry about that.

Leeb · Jun 22, 2014

To keep you updated.

I've ran a PRIME95 test for 24 hours+

No threads failed, CPU got to 38 degrees.

I've ran several memory tests including LinX testing all 32GB of memory.

Memory got to 47 degrees c, CPU got to 40.

I've also ran several GPU benchmark tests, All 4 780TI classified are watercooled and got to no more than 57 Degrees c

All tests completed and didn't blue screen, it's the most random thing ever.

The only thing i have done which i am uncertain off is the VCORE voltage.

I have the Rampage IV Extreme Black Edition and this motherboard does some very strange things with voltages, the voltage at stock goes over 1.36 volts on the VCORE.

It has settings called DIGI+ power control which calculates the V-DROOP etc... however i have no reference to the standard VCORE voltage.

I have used my SANDY BRIDGE 3970x for reference and set it to offset -0.115 which makes the cpu at 1.2GHZ = 0.825VCORE at 4GHZ = 1.180VCORE.

All PRIME 95 tests have passed over 24 hours so i can't see this being a CPU related error.

Best Regards.

blueelvis · Jun 22, 2014

Hi Leeb,

First of all, that's one hell of a system ^_^. I have analyzed your Dump file and below has been provided an analysis of the dump file for informative purposes :-

Code:

10: kd> !analyze -v*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************


WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffe001c1d7b028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be200000, High order 32-bits of the MCi_STATUS value.
Arg4: 00000000000b110a, Low order 32-bits of the MCi_STATUS value.


Debugging Details:
------------------




BUGCHECK_STR:  0x124_GenuineIntel


CUSTOMER_CRASH_COUNT:  1


DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT


PROCESS_NAME:  System


CURRENT_IRQL:  f


ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre


STACK_TEXT:  
ffffd001`47736ef8 fffff801`141c0203 : 00000000`00000124 00000000`00000000 ffffe001`c1d7b028 00000000`be200000 : nt!KeBugCheckEx
ffffd001`47736f00 fffff801`13bc0825 : 00000000`00000001 ffffe001`bcce4e60 ffffe001`bcce4e60 ffffe001`c1d7b028 : hal!HalBugCheckSystem+0xcf
ffffd001`47736f40 fffff801`141c068c : 00000000`00000728 00000000`0000000a ffffd001`47737330 00000000`00000000 : nt!WheaReportHwError+0x22d
ffffd001`47736fa0 fffff801`141c0a11 : ffffe001`00000010 ffffe001`bcce4e60 ffffd001`47737148 ffffe001`bcce4e60 : hal!HalpMcaReportError+0x50
ffffd001`477370f0 fffff801`141c08f4 : ffffe001`bcce3f30 00000000`00000001 00000000`0000000a 00000000`00000000 : hal!HalpMceHandlerCore+0xe1
ffffd001`47737140 fffff801`141c0b4e : 00000000`0000000c 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe4
ffffd001`47737180 fffff801`141c0cd7 : ffffe001`bcce3f30 ffffd001`477373b0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xce
ffffd001`477371b0 fffff801`13b5eabb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
ffffd001`477371e0 fffff801`13b5e871 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
ffffd001`47737320 fffff800`119e2214 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x171
ffffd001`4775b8e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm!MWaitIdle+0x18




STACK_COMMAND:  kb


FOLLOWUP_NAME:  MachineOwner


MODULE_NAME: GenuineIntel


IMAGE_NAME:  GenuineIntel


DEBUG_FLR_IMAGE_TIMESTAMP:  0


IMAGE_VERSION:  


FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_CACHE


BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_CACHE


ANALYSIS_SOURCE:  KM


FAILURE_ID_HASH_STRING:  km:0x124_genuineintel_processor_cache


FAILURE_ID_HASH:  {4c8f3f5e-1af5-ed8b-df14-d42663b1dfa7}


Followup: MachineOwner
---------


10: kd> !errrec ffffe001c1d7b028
===============================================================================
Common Platform Error Record @ ffffe001c1d7b028
-------------------------------------------------------------------------------
Record Id     : 01cf8db378850b25
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 6/22/2014 14:11:50 (UTC)
Flags         : 0x00000000


===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ ffffe001c1d7b0a8
Section       @ ffffe001c1d7b180
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   : 0x00000000000306e4
Processor ID  : 0x000000000000000a


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


Local APIC Id : 0x000000000000000a
CPU Id        : e4 06 03 00 00 08 20 0a - bf e3 be 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  @ ffffe001c1d7b240


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


Error         : [B][U]GCACHEL2_ERR_ERR (Proc 10 Bank 20)[/U][/B]                        <--------Error
  Status      : 0xbe200000000b110a
  Address     : 0x000000010721aa80
  Misc.       : 0xdcfe2050821c0086

As you can see that according to the dump file, there is Cache Error in the L2 Cache. Now, WHEA_UNCORRECTABLE_ERROR is generally caused by faulty hardware but sometimes it can be caused by Lower Level drivers as well. Below is a list of 3rd party drivers which you should update before we could proceed further :-

Code:

**************************Sun Jun 22 19:41:50.783 2014 (UTC + 5:30)**************************
[COLOR=#ff0000][U][B]AsUpIO.sys                  Tue Aug  3 08:17:59 2010 (4C57835F)[/B][/U][/COLOR]
[COLOR=#ff0000][U][B]ASUSFILTER.sys              Tue Sep 20 21:16:33 2011 (4E78B559)[/B][/U][/COLOR]
PxHlpa64.sys                Mon Oct 17 19:59:34 2011 (4E9C3BCE)
[U][B][COLOR=#ff0000]AiChargerPlus.sys           Thu Apr 19 06:47:35 2012 (4F8F67AF)[/COLOR][/B][/U]
[U][B][COLOR=#ff0000]AsIO.sys                    Wed Aug 22 15:24:47 2012 (5034AC67)[/COLOR][/B][/U]
asmtufdriver.sys            Fri Sep 28 16:25:29 2012 (50658221)
e1c64x64.sys                Fri Jun 21 03:29:00 2013 (51C37B24)
dump_iaStorA.sys            Fri Aug  2 07:09:52 2013 (51FB0DE8)
iaStorA.sys                 Fri Aug  2 07:09:52 2013 (51FB0DE8)
intelppm.sys                Thu Aug 22 14:16:35 2013 (5215CFEB)
TeeDriverx64.sys            Thu Sep  5 23:32:18 2013 (5228C72A)
ksaud.sys                   Wed Oct 16 09:27:35 2013 (525E0EAF)
nvhda64v.sys                Thu Nov 28 19:08:09 2013 (52974741)
asstor64.sys                Mon Jan 27 15:00:34 2014 (52E6273A)
kerneld.x64                 Wed Feb 12 02:46:18 2014 (52FA9322)
asmtxhci.sys                Fri Mar  7 07:46:05 2014 (53192BE5)
asmthub3.sys                Fri Mar  7 07:46:10 2014 (53192BEA)
nvvad64v.sys                Fri Mar 28 19:02:06 2014 (533579D6)
NvStreamKms.sys             Wed Apr 30 06:29:44 2014 (53604B00)
nvlddmkm.sys                Tue May 20 04:38:44 2014 (537A8EFC)

http://www.carrona.org/drivers/driver.php?id=AsUpIO.sys
http://www.carrona.org/drivers/driver.php?id=ASUSFILTER.sys
http://www.carrona.org/drivers/driver.php?id=PxHlpa64.sys
http://www.carrona.org/drivers/driver.php?id=AiChargerPlus.sys
http://www.carrona.org/drivers/driver.php?id=AsIO.sys
asmtufdriver.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
e1c64x64.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=dump_iaStorA.sys
http://www.carrona.org/drivers/driver.php?id=iaStorA.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=TeeDriverx64.sys
http://www.carrona.org/drivers/driver.php?id=ksaud.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
asstor64.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=kerneld.x64
http://www.carrona.org/drivers/driver.php?id=asmtxhci.sys
http://www.carrona.org/drivers/driver.php?id=asmthub3.sys
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
http://www.carrona.org/drivers/driver.php?id=NvStreamKms.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys

The drivers in RED are the ASUS Bloatware which are well known for causing BSOD's so I would say to remove every trace of ASUS Bloatware from your system. Post back, in case you still face problems and we would be glad to help you out ^_^.

EDIT :- Btw, I have almost no idea about overclocking but the only fact that you should revert them to the default settings before we troubleshoot further. Isn't there a RESET Bios options in the BIOS settings?

Leeb · Jun 22, 2014

If i set everything to AUTO in the bios which is default the stock voltages for my CPU go crazy.

Normally i wouldn't expect this CPU to go over 1.2 VCORE but with stock the CPU is hitting 1.3 - 1.4VCORE which is just far to high.

In regards to the drives in question i will get them removed and see how i get on from this point.

I'll keep you updated.

Leeb · Jun 22, 2014

Is there anything further you can give me in regards to the L2 cache failure.

Operation Per Second --> 7310369

Error --> 0
Prime Number Generation Test Pass---

--- Reading Cache Size ---

- Detected L1 Data Cache Size --> 1 x 32
- Detected L1 Inst Cache Size --> 1 x 32

- Detected L2 Cache Size --> 256
- Detected L3 Cache Size --> 15360

Cache Size Test Passed!!!

Is what i got from the Intel Processor Diag tool.

blueelvis · Jun 23, 2014

You should refer your processor manual for setting the correct voltages I would say or contact Intel about your specific processor. From your Log file, I got only one dump file which points to that bugcheck. If you get more BSOD, then please post the dump files so we could see if there is any pattern in the BSOD appearing or not.

Leeb · Jun 23, 2014

Latest dump file without ASUS SUITE 3 installed and a complete brand new installation of Windows 8.1 64bit.

Can you see if it's the same report please.

Thanks very much for all your help btw.

blueelvis · Jun 23, 2014

Hi Leeb,

Code:

4: kd> !analyze -v*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************


WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffe000a4f7a028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be200000, High order 32-bits of the MCi_STATUS value.
Arg4: 00000000000b010a, Low order 32-bits of the MCi_STATUS value.


Debugging Details:
------------------


*************************************************************************


ADDITIONAL_DEBUG_TEXT:  
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.


FAULTING_MODULE: fffff80377a81000 nt


DEBUG_FLR_IMAGE_TIMESTAMP:  0


BUGCHECK_STR:  0x124_GenuineIntel


CUSTOMER_CRASH_COUNT:  1


DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT


CURRENT_IRQL:  0


ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre


STACK_TEXT:  
ffffd001`d7b50ef8 fffff803`77a48203 : 00000000`00000124 00000000`00000000 ffffe000`a4f7a028 00000000`be200000 : nt!KeBugCheckEx
ffffd001`d7b50f00 fffff803`77c41825 : 00000000`00000001 ffffe000`9fee3d40 ffffe000`9fee3d40 ffffe000`a4f7a028 : hal!HalBugCheckSystem+0xcf
ffffd001`d7b50f40 fffff803`77a4868c : 00000000`00000728 00000000`00000004 ffffd001`d7b51330 00000000`00000000 : nt!WheaReportHwError+0x22d
ffffd001`d7b50fa0 fffff803`77a48a11 : ffffe000`00000010 ffffe000`9fee3d40 ffffd001`d7b51148 ffffe000`9fee3d40 : hal!HalpMcaReportError+0x50
ffffd001`d7b510f0 fffff803`77a488f4 : ffffe000`9fee3290 00000000`00000001 00000000`00000004 00000000`00000000 : hal!HalpMceHandlerCore+0xe1
ffffd001`d7b51140 fffff803`77a48b4e : 00000000`0000000c 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe4
ffffd001`d7b51180 fffff803`77a48cd7 : ffffe000`9fee3290 ffffd001`d7b513b0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xce
ffffd001`d7b511b0 fffff803`77bdfabb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
ffffd001`d7b511e0 fffff803`77bdf871 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!setjmpex+0x27bb
ffffd001`d7b51320 fffff801`5b002214 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!setjmpex+0x2571
ffffd001`d7b718e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm!MWaitIdle+0x18




STACK_COMMAND:  kb


FOLLOWUP_NAME:  MachineOwner


MODULE_NAME: GenuineIntel


IMAGE_NAME:  GenuineIntel


IMAGE_VERSION:  


BUCKET_ID:  WRONG_SYMBOLS


FAILURE_BUCKET_ID:  WRONG_SYMBOLS


ANALYSIS_SOURCE:  KM


FAILURE_ID_HASH_STRING:  km:wrong_symbols


FAILURE_ID_HASH:  {70b057e8-2462-896f-28e7-ac72d4d365f8}


Followup: MachineOwner
---------


4: kd> !errrec ffffe000a4f7a028
===============================================================================
Common Platform Error Record @ ffffe000a4f7a028
-------------------------------------------------------------------------------
Record Id     : 01cf8ede735d9123
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 6/23/2014 17:03:02 (UTC)
Flags         : 0x00000000


===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ ffffe000a4f7a0a8
Section       @ ffffe000a4f7a180
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   : 0x00000000000306e4
Processor ID  : 0x0000000000000004


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


Local APIC Id : 0x0000000000000004
CPU Id        : e4 06 03 00 00 08 20 04 - bf e3 be 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
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_WHEA_XPF_PROCESSOR_ERROR_SECTION                ***
***                                                                   ***
*************************************************************************


Proc. Info 0  @ ffffe000a4f7a240


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


*************************************************************************
***                                                                   ***
***                                                                   ***
*************************************************************************
Error         : GCACHEL2_ERR_ERR (Proc 4 Bank 20)
  Status      : 0xbe200000000b010a
  Address     : 0x0000000847c94a00
  Misc.       : 0xdcfe2890829bc086

According to the above analysis, the Cache error this time on the Different Processor, so I would say that your system is not stable at the overclocked speed. I did not find any specific 3rd party drivers as well. Please revert your system back to stock settings and then report back.

Leeb · Jun 23, 2014

I think the issue here could well be voltages.

Unfortunately i have everything set to stock right now but with the lovely ASUS DIGI+ Power Control makes it very hard to get stock voltages.

It has a unique way of doing things but is also the best board for the job.

I think it's very possible that under some form of C states functions of the CPU the V-DROOP controlled by the VCCSA Load-Line Calibration can-not correspond with the required voltage quick enough thus creating an un-correctable hardware fault.

Now i know it's highly un-likely that it's a hardware fault, i believe more to be a voltage configuration issue.

I will report back with my findings in here and perform some detailed tests so all users that are having these common issues can hopefully get them resolved as well.

Cheers!

BSOD, hal.dll+37203, WHEA_UNCORRECTABLE_ERROR

New Member

My Computer

OMG Debugger!

My Computer

New Member

My Computer

New Member

My Computer

OMG Debugger!

My Computer

New Member

My Computer

New Member

My Computer

OMG Debugger!

My Computer

New Member

My Computer

OMG Debugger!

My Computer

New Member

My Computer