How Can You Fix PC Dll Errors Effectively?: BSOD ntoskrnl.exe +14dca0 Windows 8.1 Pro

BSOD ntoskrnl.exe +14dca0 Windows 8.1 Pro

Hey Community

I build myself a new computer last month and it was working like a charm.
But since 2 weeks ago I get random BSOD with an WHEA_UNCORRECTABEL_ERROR almost every day I try to work with it.
The Bluescreens seem to occur without any real pattern, Sometimes I
get them while working in Photoshop, then while playing Borderlands, sometimes when I watch videos on the Internet and once the whole system crashed when I tried to install an earlier version of DirectX.
I still have the warranty from my parts which is why
it would be awesome if you could help me find out what part is causing the BSOD so I can replace it.
THE MACHINE :
CPU: Intel i7 4770k
RAM: Crucial 16GB kit (8GBx2), 240-pin DIMM, DDR3 PC3-12800 Memory Module
GPU: PALIT Geforce GTX 770
Mainboard: ASUS Z87 PRO
PSU: CORSAIR CX600M
SSD: SAMSUNG 840 PRO 256GB
Drive: PIONEER BLU RAY DRIVE
WHAT I DID SO FAR:
Updated to the latest Windows Version.
Updated my Graphiccard drivers.
Installed the latest firmware for my SSD
Updated my BIOS to the latest version possible.
I ran memetest86+ for a whole night 10 passes no Error.
I made a stress test with BurnIN for every component avaiable no Error.
I ran a Chkdsk without any Error.
I ran Scannow and it told me there was no Error.
ASUS AI SUITE Software "fixed" my PC performance but I set everything back to standard in the BIOS and deinstalled everthing of the software, erased remaining bits with a cleaning tool and manually removed the folder and the planned schedules that kept starting
the programm.
Eventhough my hardware indicates that this could be due to OC, I must stress that I didn't change anything from the given presets.
I ran Verify Driver but nothing really changed.
You can find my Minidmps here. https://www.dropbox.com/sh/ou5nexqqk1dvuml/HmG78cPCNE
Thank you for the help in advance,
Kind Regards
JterHorst

Keys to the Problem BSOD ntoskrnl.exe +14dca0 Windows 8.1 Pro

Download Error Fixer (Free)

JH
These are called BCC124 and are hardware related. SInce yours refers to "genuine Intel" I would start by running the CPU stress tests.

Stop 0x124 is a hardware error
If you are overclocking try resetting your processor to standard settings and see if that helps.
If you continue to get BSODs here are some more things you may want to consider.
This is usually heat related, defective hardware, memory or even processor though it is"possible" that it is driver related (rare).

Stop 0x124 - what it means and what to try
Synopsis:
A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.
Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress.

Generic "Stop 0x124" Troubleshooting Strategy:

1) Ensure that none of the hardware components are overclocked. Hardware that is driven beyond its design specifications - by overclocking - can malfunction in unpredictable ways.
2) Ensure that the machine is adequately cooled.
If there is any doubt, open up the side of the PC case (be mindful of any relevant warranty conditions!) and point a mains fan squarely at the motherboard.
That will rule out most (lack of) cooling issues.
3) Update all hardware-related drivers: video, sound, RAID (if any), NIC...
anything that interacts with a piece of hardware.
It is good practice to run the latest drivers anyway.
4) Update the motherboard BIOS according to the manufacturer's instructions and clear the CMOS.
Their website should provide detailed instructions as to the brand and model-specific procedure.
5) Rarely, bugs in the OS may cause "false positive" 0x124 events where the hardware wasn't complaining but Windows thought otherwise (because of the bug).
At the time of writing, Windows 7 is not known to suffer from any such defects, but it is nevertheless important to always keep Windows itself updated.
6) Attempt to (stress) test those hardware components which can be put through their paces artificially.
The most obvious examples are the RAM and HDD(s).
For the RAM, use the 3rd-party memtest86 utility to run many hours worth of testing.
(6-8 passes to stress the ram out)
For hard drives, check whether CHKDSK /R finds any problems on the drive(s), notably "bad sectors".
Unreliable RAM, in particular, is deadly as far as software is concerned, and anything other than a 100% clear memory test result is cause for concern.
Unfortunately, even a 100% clear result from the diagnostics utilities does not guarantee that the RAM is
free from defects - only that none were encountered during the test passes.
7) As the last of the non-invasive troubleshooting steps, perform a "vanilla" reinstallation of Windows: just the OS itself without any additional applications, games, utilities, updates, or new drivers - NOTHING AT ALL that is
not sourced from the Windows 7 disc.
Should that fail to mitigate the 0x124 problem, jump to the next steps.
If you run the "vanilla" installation long enough to convince yourself that not a single 0x124 crash has occurred, start installing updates and applications slowly, always pausing between successive additions long enough to get a feel for whether the machine
is still free from 0x124 crashes.
Should the crashing resume, obviously the very last software addition(s) may be somehow linked to the root cause.
If stop 0x124 errors persist despite the steps above, and the hardware is under warranty, consider returning it and requesting a replacement which does not suffer periodic MCE events.
Be aware that attempting the subsequent hardware troubleshooting steps may, in some cases, void your warranty:
8) Clean and carefully remove any dust from the inside of the machine.
Reseat all connectors and memory modules.
Use a can of compressed air to clean out the RAM DIMM sockets as much as possible.
9) If all else fails, start removing items of hardware one-by-one in the hope that the culprit is something non-essential which can be removed.
Obviously, this type of testing is a lot easier if you've got access to equivalent components in order to perform swaps.
Should you find yourself in the situation of having performed all of the steps above without a resolution of the symptom, unfortunately the most likely reason is because the error message is literally correct
- something is fundamentally wrong with the machine's hardware.

More advanced reading can be found here from a MS MVP IT PRO
http://captaindbg.com/bug-check-0x124-whea_uncorrectable_error-how-to-troubleshoot/

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

Loading Dump File [C:\Users\Ken\Desktop\040514-4093-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*H:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*H:\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.16452.amd64fre.winblue_gdr.131030-1505
Machine Name:
Kernel base = 0xfffff803`53011000 PsLoadedModuleList = 0xfffff803`532d5990
Debug session time: Sat Apr 5 10:30:48.289 2014 (UTC - 4:00)
System Uptime: 0 days 4:26:46.941
Loading Kernel Symbols
..

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

.............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, 0, ffffe00001f41028, bf800000, 124

Probably caused by : GenuineIntel

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

3: 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: ffffe00001f41028, 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:
------------------

DUMP_FILE_ATTRIBUTES: 0xc
Insufficient Dumpfile Size
Kernel Generated Triage Dump

BUGCHECK_STR: 0x124_GenuineIntel

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: Borderlands.ex

CURRENT_IRQL: f

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

STACK_TEXT:
ffffd000`206aed78 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx

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

To check for Windows updates. Open Windows Update by clicking the Start button , clicking All Programs, and then clicking Windows Update. In the left pane, click Check for updates, and then wait while Windows looks for the latest updates for your computer. If any updates are found, click Install updates.

Install the latest updates for Windows and for the program displaying the error. Note that the update for the program might be listed as an optional update on the Windows Update page.

Open Windows Update by clicking the Start button Picture of the Start button. In the search box, type Update, and then, in the list of results, click Windows Update.

Another Safe way to Fix the Problem: BSOD ntoskrnl.exe +14dca0 Windows 8.1 Pro:

How to Fix BSOD ntoskrnl.exe +14dca0 Windows 8.1 Pro with SmartPCFixer?

1. Click the button to download SmartPCFixer . Install it on your computer. Run it, and it will scan your system. The junk files will be shown in the scan result.