Random WHEA_UNCORRECTABLE_ERROR BSOD Durring anything

[Athom97]

I've been getting this for months and have tried many things to fix it but nothing seems to work. Here's the zip file. Thanks in advanced. View attachment 67058

 

[lifetec]

All dumpfiles are

 *******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, ffffe0014c695028, bf800000, 114}
Probably caused by : GenuineIntel
Followup: MachineOwner
---------
2: 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: ffffe0014c695028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000114, 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:  TiWorker.exe
CURRENT_IRQL:  f
ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) x86fre
STACK_TEXT:  
ffffd000`a02a9cf8 fffff802`0a9da213 : 00000000`00000124 00000000`00000000 ffffe001`4c695028 00000000`bf800000 : nt!KeBugCheckEx
ffffd000`a02a9d00 fffff802`0a3d3c85 : 00000000`00000001 ffffe001`478da310 ffffe001`478da310 ffffe001`4c695028 : hal!HalBugCheckSystem+0xcf
ffffd000`a02a9d40 fffff802`0a9da6a0 : 00000000`00000728 00000000`00000002 ffffd000`a02aa130 00000000`00000000 : nt!WheaReportHwError+0x22d
ffffd000`a02a9da0 fffff802`0a9daa0d : ffffe001`00000010 ffffe001`478da310 ffffd000`a02a9f48 ffffe001`478da310 : hal!HalpMcaReportError+0x50
ffffd000`a02a9ef0 fffff802`0a9da8f8 : ffffe001`478d9ca0 00000000`00000001 00000000`00000002 00000000`00000000 : hal!HalpMceHandlerCore+0xe1
ffffd000`a02a9f40 fffff802`0a9dab42 : 00000000`00000004 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe4
ffffd000`a02a9f80 fffff802`0a9daccf : ffffe001`478d9ca0 ffffd000`a02aa1b0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xce
ffffd000`a02a9fb0 fffff802`0a36e3bb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
ffffd000`a02a9fe0 fffff802`0a36e171 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
ffffd000`a02aa120 fffff802`0a26dd96 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x171
ffffd000`a378ef10 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeAbPostRelease+0x186

Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ ffffe0014c695138
Section       @ ffffe0014c6952c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal
Error         : DCACHEL0_RD_ERR (Proc 2 Bank 1)
  Status      : 0xbf80000000000114
  Address     : 0x00000001821ddf40
  Misc.       : 0x0000000000000086

This could point to a problem with the CPU (with the cache) , but to exclude problems with your systemfiles.
Run first SFC
Use SFC to check and repair windows systemfiles.

See this tutorial http://www.eightforums.com/tutorials/3047-sfc-scannow-command-run-windows-8-a.html

Note
If SFC could not fix something, then run the command again to see if it may beable to the next time. Sometimes it may take running the sfc /scannow command 3 times restarting the PC after each time to completely fix everything that it's able to.

If not, then run the Dism /Online /Cleanup-Image/RestoreHealth command to repair any component store corruption, restart the PCafterwards, and try the sfc /scannowcommand again.

If this does not solve the BSOD test your CPU.
IntelProcessor Diagnostic Tool (works in Windows)
x64 - http://downloadcenter.intel.com/Deta...mples&lang=eng

 

[Athom97]

WHEA_UNCORRECTABLE_ERROR During Anything

It's been occurring since I got my laptop in August. What I don't know is if it's a hardware problem or not.View attachment 67182

 

[Athom97]

I've tried all of the above and still get random BSODs. Here's the new zip View attachment 67183

 

[lifetec]

It is again bugcheck WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred.

I suspect your CPU is faulty.
Did you run the Inte;l Cpu test.
What was the result.

 

[Athom97]

I ran the test and it passed everything here's a screenshot. View attachment 67188

 

[lifetec]

Could you make a new zip with the latest BSOD, the last one you have uploaded only has BSOD till 14 januari.

I found this pattern a few times in the WER
Module Path: C:\Windows\system32\ihvmanager\AthIHVManager.dll =(part of Atheros Wireless lan driver)
followed by
Event[2237]:
Log Name: System
Source: Microsoft-Windows-WER-SystemErrorReporting
Date: 2016-01-12T15:08:25.000
Event ID: 1001
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: Acer
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xffffe00122f40028, 0x00000000bf800000, 0x0000000000000114). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 011216-11437-01.

Maybe this driver is corrupted.
Please uninstall and reinstall this driver.

 

[Athom97]

View attachment 67196 And how do I uninstall and reinstall the driver. Thanks for the help.

 

[lifetec]

And how do I uninstall and reinstall the driver. Thanks for the help.

Go to Device manager > networkadapters> Atheros Wireless lan driver > delete > reboot > reinstall


All your dumpfiles are again the same bugcheck 124

But i had a other BSOD thread were 360 internet security and Tencent Manager were causing BSOD.
Remove these programs and see if this stops the BSod on your system.

 

[Athom97]

I uninstalled the driver but I can't reinstall it I'm sending this from my phone.

 

[Athom97]

Never mind I was able to reinstall it.
And I deleted the other programs I'll let you know if I get another BSOD.

 

[Athom97]

I still got a BSOD. Here's the new zip. View attachment 67197

 

[lifetec]

Still the same bugcheck

Please uninstall McAfee. use the McAfee Remover.

If the system keeps BSOD than please run Driver Verifier maybe this can find the abusing driver.
You can enable "DriverVerifier" according to instructions from the below link.
http://www.tenforums.com/tutorials/5470-driver-verifier-enable-disable-windows-10-a.html
"Verifier" is a Microsoft's own tool to stress test third partydrivers and find the buggy one. If it detects a violation, a blue screen willbe created immediately and the dump will give us the name of offending driverstraight forward. After enabling "Verifier" , system will be a bitslow and laggy during to the background verification process. After you got twoor more blue screens, please upload the new crash dumps and we will knowwhether the issue is caused by third party drivers or low level hardware (averifier enabled dump which blames Windows system files is a clear confirmationof hardware problem).
"Verifier" should be only used to monitor third party drivers.Selecting Microsoft system drivers is totally unnecessary and doing so may make the system nonbootable.
Additional:
First read instructionsfrom the below link and set "Windows" to write "Small Memorydumps".
SetMiniDump

 

[Athom97]

I ran the driver verifier, but it caused two other BSODs to appear as well I had o restore the laptop in order to use it for more than one minute. The other two were BAD_POOL_CALLER and PAGE_FAULT_BEYOND_END_OF_ALLOCATION. Here's the new zip, but I'm not 100% sure if it will have the minidumps even though it said no files would be affected. View attachment 67200

 

[lifetec]

There is one new Verifier dumpfile inside

  *******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C2, {9d, 7c, 1, fffff80127ab15bc}
*** WARNING: Unable to verify timestamp for mfesapsn.sys
*** ERROR: Module load completed but symbols could not be loaded for mfesapsn.sys
Probably caused by : mfesapsn.sys ( mfesapsn+25bc )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
BAD_POOL_CALLER (c2)
The current thread is making a bad pool request.  Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 000000000000009d, Attempt to allocate pool with a tag that does not contain any letters or digits.
 Using these tags makes tracking pool issues very hard.
Arg2: 000000000000007c, Incorrect pool tag used.
Arg3: 0000000000000001, Pool type
Arg4: fffff80127ab15bc, Caller's address.
Debugging Details:
------------------

FAULTING_IP: 
VerifierExt!ExAllocatePoolWithTagPriority_internal_wrapper+7b
fffff801`23558a17 8b0d23a10100    mov     ecx,dword ptr [VerifierExt!XdvActiveExtensionBitmap (fffff801`23572b40)]
BUGCHECK_STR:  0xc2_9d
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  mcsacore.exe
CURRENT_IRQL:  1
ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) x86fre
LAST_CONTROL_TRANSFER:  from fffff803fca8a6b0 to fffff803fc55a2a0
STACK_TEXT:  
ffffd000`f2cd2168 fffff803`fca8a6b0 : 00000000`000000c2 00000000`0000009d 00000000`0000007c 00000000`00000001 : nt!KeBugCheckEx
ffffd000`f2cd2170 fffff803`fcaa0c1b : 00000000`00000000 00000000`0000007c 00000000`00000000 fffff803`fc4ae164 : nt!VerifierBugCheckIfAppropriate+0x3c
ffffd000`f2cd21b0 fffff803`fca7fbbd : 00000000`000000c8 00000000`00000020 00000000`0000007c 00000000`00000001 : nt!ExAllocatePoolSanityChecks+0xa7
ffffd000`f2cd2200 fffff801`23558a17 : 00000000`00000081 00000000`000000c8 00000000`0000007c 00000000`0000007c : nt!VeAllocatePoolWithTagPriority+0x89
ffffd000`f2cd2270 fffff803`fca8009a : ffffe000`e50d7f48 fffff801`27ab4000 ffffe000`e50d7f68 fffff801`27ab21f9 : VerifierExt!ExAllocatePoolWithTagPriority_internal_wrapper+0x7b
ffffd000`f2cd22b0 fffff801`27ab15bc : fffff803`fc8ac614 fffff803`fc7b9e83 00000000`00000000 fffff801`27ab4000 : nt!VerifierExAllocatePoolEx+0x2a
ffffd000`f2cd22f0 fffff803`fc8ac614 : fffff803`fc7b9e83 00000000`00000000 fffff801`27ab4000 ffffd000`f2cd2380 : mfesapsn+0x25bc
ffffd000`f2cd22f8 fffff801`27ab1970 : fffff801`2355baf7 ffffe000`e50d7db0 ffffcf81`4d10eea0 ffffcf81`4d10eea0 : nt!ObpLookupObjectName+0x784
ffffd000`f2cd2428 fffff801`2355baf7 : ffffe000`e50d7db0 ffffcf81`4d10eea0 ffffcf81`4d10eea0 fffff801`27ab1970 : mfesapsn+0x2970
ffffd000`f2cd2430 fffff803`fca7e911 : ffffcf81`4d10eea0 00000000`00000002 ffffe000`ec027890 fffff803`fc44bfc5 : VerifierExt!xdv_IRP_MJ_CREATE_wrapper+0xfb
ffffd000`f2cd2490 fffff803`fc7ad2c1 : 00000000`00000025 ffffd000`f2cd27e1 00000000`00000000 ffffe000`ec171940 : nt!IovCallDriver+0x3cd
ffffd000`f2cd24e0 fffff803`fc8ac614 : 00000000`00000000 00000000`00000000 ffffe000`e50d7d80 ffffe000`e50d7d80 : nt!IopParseDevice+0x6c1
ffffd000`f2cd2700 fffff803`fc7b9e83 : 00000000`00000000 ffffd000`f2cd28a8 00000000`00000040 ffffe000`e412bf20 : nt!ObpLookupObjectName+0x784
ffffd000`f2cd2830 fffff803`fc79d9ab : 00010148`00000001 ffffe000`ec093ba8 00000000`00000001 00000000`00000020 : nt!ObOpenObjectByName+0x1e3
ffffd000`f2cd2960 fffff803`fc79d634 : 00000091`4d70f4d8 00000000`c0100080 00000091`4d70f530 ffffe000`00001000 : nt!IopCreateFile+0x36b
ffffd000`f2cd2a00 fffff803`fc565ab3 : ffffe000`eb590080 ffffd000`f2cd2b80 ffffd000`f2cd2aa8 fffff6bf`fc5e5260 : nt!NtCreateFile+0x78
ffffd000`f2cd2a90 00007ff8`bdb1138a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000091`4d70f458 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`bdb1138a

STACK_COMMAND:  kb
FOLLOWUP_IP: 
mfesapsn+25bc
fffff801`27ab15bc 488bf8          mov     rdi,rax
SYMBOL_STACK_INDEX:  6
SYMBOL_NAME:  mfesapsn+25bc
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: mfesapsn
IMAGE_NAME:  mfesapsn.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  5658b68b
FAILURE_BUCKET_ID:  0xc2_9d_VRF_mfesapsn+25bc
BUCKET_ID:  0xc2_9d_VRF_mfesapsn+25bc
ANALYSIS_SOURCE:  KM
FAILURE_ID_HASH_STRING:  km:0xc2_9d_vrf_mfesapsn+25bc
FAILURE_ID_HASH:  {6debb4ae-796b-b8b6-e8d1-e0892908c2ee}
Followup: MachineOwner
---------

This driver is part of McAfee
Driver Description: McAfee WebAdvisor Driver
Driver Update Site: Download - McAfee Downloads - Antivirus, Antimalware, Virus Scan, Free Trials | Intel Security
Support - http://support.mcafee.com
Please uninstall Mcafee and use the McAfee remover as i said earlier.

 

[Athom97]

I uninstalled mcafee and still got the BSOD. Here's the new zip and thanks for all of the help so far. View attachment 67215

 

[lifetec]

Please update the zip again there is no content inside,

 

[Athom97]

Here's the new zip. View attachment 67224

 

[lifetec]

The dumpfiles are again the same bugcheck 124
But you have installed again 360 internet security which probably also is a culprit for the BSOD.
This way it is difficult to troubleshoot.

Run Driver verifirier again.

 

[Athom97]

Are there any specific settings I should put drive versifier on.