📎 AI Summary:
The WindowsForum thread discusses a user's recurring BSOD errors, primarily WHEA_UNCORRECTABLE_ERROR and bugcheck 124, which are indicative of hardware issues. Despite various troubleshooting steps, including memtest, BIOS updates, and driver checks, the root cause remains unclear, with suggestions focusing on hardware stability, thermal monitoring, and resetting to default settings. Overall, the advice leans toward potential hardware problems like overheating or faulty components, and further diagnostics are recommended to resolve the issue.
ElectronM

ElectronM

New Member
Member details
Joined
Mar 24, 2014
Messages
3
Thread Author #1
Random BSOD at times, I've noticed when running multiple programs at once.

BSOD displaying, WHEA_UNCORRECTABLE_ERROR. Ran memtest86+ on the two DRAM sticks at different times at about 5 passes. Displayed no errors.

Mobo: Asus Z87-A
CPU: i7-4770k
GPU: GTX 750 Ti
8 Gigs of RAM

BlueScreenView displays hal.dll and ntoskml.exe as possible causes.
 

Attachments

Solution
kemical
Code: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, ffffe000026e8028, bf800000, 124}

Probably caused by : GenuineIntel

Followup: MachineOwner
Hi,
that's better... Ok well all three dump files sent were of the same type Bugcheck 124 which as mentioned can mean a hardware error. Sometimes a Bios update will be the...
Sort by date Sort by votes
kemical

kemical

Essential Member
Member details
Joined
Aug 28, 2007
Messages
36,163
#2
Code: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A0000001, {5, 0, 0, 0}

Probably caused by : atikmdag.sys ( atikmdag+277ce )

Followup: MachineOwner

Hi,
this bugcheck is quite rare and specifically happens when AMD GPU is faulty or drivers need updating. Something else could be at the cause however and only looking through the dump file will reveal perhaps what..

BiosVersion = V1.19
BiosReleaseDate = 03/07/2012
Your bios has updates relating to the graphics subsystem and updating could be the key. It is extremely important you make sure you download the correct bios for your motherboard. I have a link for P67A-GD65 (B3).
Link Removed
Please follow MSI's instructions:
BIOS & ME update SOP

Post any new dump files
 

Upvote 0 Downvote
ElectronM

ElectronM

New Member
Member details
Joined
Mar 24, 2014
Messages
3
Thread Author #3
Hmm...that's weird.

I don't have an AMD GPU and My motherboard isn't P67A-GD65.

Here's a new dump file.

Code: 
Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\032414-39375-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.16384.amd64fre.winblue_rtm.130821-1623
Machine Name:
Kernel base = 0xfffff800`0d00c000 PsLoadedModuleList = 0xfffff800`0d2d39b0
Debug session time: Mon Mar 24 16:42:17.419 2014 (UTC - 5:00)
System Uptime: 0 days 1:15:13.051
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
.........................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, ffffe000029f3028, bf800000, 124}

Probably caused by : GenuineIntel

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

1: 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: ffffe000029f3028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000124, 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: 
ffffd000`201e5c38 fffff800`0d7c4c93 : 00000000`00000124 00000000`00000000 ffffe000`029f3028 00000000`bf800000 : nt!KeBugCheckEx
ffffd000`201e5c40 fffff800`0d1c7401 : 00000000`00000001 ffffe000`0022f1a0 ffffe000`0022f1a0 ffffe000`029f3028 : hal!HalBugCheckSystem+0xcf
ffffd000`201e5c80 fffff800`0d7c5120 : 00000000`00000728 00000000`00000001 ffffd000`201e6070 00000000`00000000 : nt!WheaReportHwError+0x22d
ffffd000`201e5ce0 fffff800`0d7c548d : ffffe000`00000010 ffffe000`0022f1a0 ffffd000`201e5e88 ffffe000`0022f1a0 : hal!HalpMcaReportError+0x50
ffffd000`201e5e30 fffff800`0d7c5378 : ffffe000`0022ebf0 00000000`00000001 00000000`00000001 00000000`00000000 : hal!HalpMceHandlerCore+0xe1
ffffd000`201e5e80 fffff800`0d7c55c2 : 00000000`00000008 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe4
ffffd000`201e5ec0 fffff800`0d7c574f : ffffe000`0022ebf0 ffffd000`201e60f0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xce
ffffd000`201e5ef0 fffff800`0d166bbb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
ffffd000`201e5f20 fffff800`0d166971 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
ffffd000`201e6060 fffff800`00cb8eaf : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x171
ffffd000`213a2120 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!TcpTcbFastDatagram+0x1454


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
---------
 

Upvote 0 Downvote
kemical

kemical

Essential Member
Member details
Joined
Aug 28, 2007
Messages
36,163
#4
I really need to see your actual dump file so please use the tool found here:
Link Removed

I went back and downloaded your first bsod zip file and got the same results. I'm not sure how these files have become mixed up but there was a previous user with the exact same mobo and I wonder if somehow his zip file is now in your thread... Weird. Please post your new dump file and I'll debug it asap. Oh and bugcheck 124 is a hardware error although I would say you probably need to update your bios but let me see the dump and i can tell you further.

I went and checked that last user I spoke of and it is the same file... Damn that's strange. I'll notify the powers that be. Apologies for the confusion.

Another thought, when you post the new info make sure you don't name it 'BSOD files' in case the website is somehow replacing the new copy with the old.
 

Last edited:
Upvote 0 Downvote
kemical

kemical

Essential Member
Member details
Joined
Aug 28, 2007
Messages
36,163
#6
Code: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, ffffe000026e8028, bf800000, 124}

Probably caused by : GenuineIntel

Followup: MachineOwner
Hi,
that's better... Ok well all three dump files sent were of the same type Bugcheck 124 which as mentioned can mean a hardware error. Sometimes a Bios update will be the reason but you already have the latest version so it could be something else like overclocking or temperature. I didn't see any sign of overclocking but if you are return to default values to see if bsod stops. You say the bsod normally happens when multiple apps are open? That could mean temperature and have you checked your CPU temp values at idle and at stress?
This app will help you monitor:
http://www.cpuid.com/softwares/hwmonitor.html
Try stressing the CPU using this program:
http://www.mersenne.org/freesoft/
Run for around an hour or until baseline readings have been taken. This will also test the stability of the chip.
Check your CPU with this Intel diagnostic tool:
Link Removed

Just check that windows hasn't become corrupt. Open an admin command prompt and type:
sfc /scannow
Press enter and await results.

If your running SSD's check for firmware updates. If your running SATA disks right click on the C drive, choose properties, Tools (along the top), Error checking and finally check now. This should run a chkdsk for you.

Driver wise you don't look too bad although I see your running AVG which has been known on occasion to cause issues. Try un-installing and using MSE:
Link Removed

Post any new dump files.
 

Upvote 1 Downvote
Solution
You must log in or register to reply here.