Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Wednesday, April 4, 2018 6:28 PM
I started getting this crash and error last week multiple times a day on about an 8 month old install. Needed to do a clean install of Windows anyways so formatted and did a fresh install. Shortly after new install I got the crash again. Did memory test, no errors. Ended up doing another fresh install with my system disconnected from the network on the chance it was drivers, left it on to see if it would crash again.
Crashed again, checked BIOS was at newest version, reset BIOS to defaults and disabled overclock. Left system running for a few hours and got no crash. Did updates do Windows 10, installed updated drivers to everything. No new drivers or applications installed since 04-01-18 last Windows update was on 04-01-18. Today the system has crashed twice, once while system was idle once while playing a game.
On a side note I dual boot Ubuntu from the same HDD and have had no crashes or errors.
Here is the MEMORY.DMP with !whea
Microsoft (R) Windows Debugger Version 10.0.16299.15 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 16299 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 16299.15.amd64fre.rs3_release.170928-1534
Machine Name:
Kernel base = 0xfffff801`bfa8c000 PsLoadedModuleList = 0xfffff801`bfdf3110
Debug session time: Wed Apr 4 11:23:33.535 2018 (UTC - 5:00)
System Uptime: 0 days 11:07:32.183
Loading Kernel Symbols
...............................................................
................................................................
....................................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`00419018). Type ".hh dbgerr001" for details
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, ffffd9896544b028, b2000000, 10014}
Probably caused by : GenuineIntel
Followup: MachineOwner
0: 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: ffffd9896544b028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000010014, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
DUMP_CLASS: 1
DUMP_QUALIFIER: 401
BUILD_VERSION_STRING: 16299.15.amd64fre.rs3_release.170928-1534
SYSTEM_PRODUCT_NAME: To Be Filled By O.E.M.
SYSTEM_SKU: To Be Filled By O.E.M.
SYSTEM_VERSION: To Be Filled By O.E.M.
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: P2.70
BIOS_DATE: 04/14/2016
BASEBOARD_MANUFACTURER: ASRock
BASEBOARD_PRODUCT: Z87 Extreme3
BASEBOARD_VERSION:
DUMP_TYPE: 1
BUGCHECK_P1: 0
BUGCHECK_P2: ffffd9896544b028
BUGCHECK_P3: b2000000
BUGCHECK_P4: 10014
BUGCHECK_STR: 0x124_GenuineIntel
CPU_COUNT: 4
CPU_MHZ: d47
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 3c
CPU_STEPPING: 3
CPU_MICROCODE: 6,3c,3,0 (F,M,S,R) SIG: 1E'00000000 (cache) 1E'00000000 (init)
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: stellaris.exe
CURRENT_IRQL: f
ANALYSIS_SESSION_HOST: MAGI
ANALYSIS_SESSION_TIME: 04-04-2018 13:25:25.0164
ANALYSIS_VERSION: 10.0.16299.15 x86fre
STACK_TEXT:
fffff801`c1c8e9e8 fffff801`bfa48eff : 00000000`00000124 00000000`00000000 ffffd989`6544b028 00000000`b2000000 : nt!KeBugCheckEx
fffff801`c1c8e9f0 fffff804`3a8e148a : ffffd989`6544b028 ffffd989`647eda30 ffffd989`647eda30 ffffd989`647eda30 : hal!HalBugCheckSystem+0xcf
fffff801`c1c8ea30 fffff801`bfd111c1 : ffffd989`6544b028 00000000`00000000 ffffd989`647eda30 ffffd989`647eda30 : PSHED!PshedBugCheckSystem+0xa
fffff801`c1c8ea60 fffff801`bfa49440 : 00000000`00000728 00000000`00000000 00000000`00000000 00000000`00000000 : nt!WheaReportHwError+0x261
fffff801`c1c8eac0 fffff801`bfa497a0 : 00000000`00000010 00000000`00000000 fffff801`c1c8ec68 00000000`00000000 : hal!HalpMcaReportError+0x50
fffff801`c1c8ec10 fffff801`bfa4968e : ffffd989`63ee8730 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerCore+0xe0
fffff801`c1c8ec60 fffff801`bfa498d2 : 00000000`00000004 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xda
fffff801`c1c8eca0 fffff801`bfa49a60 : ffffd989`63ee8730 fffff801`c1c8eed0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xce
fffff801`c1c8ecd0 fffff801`bfc1183b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff801`c1c8ed00 fffff801`bfc114bd : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
fffff801`c1c8ee40 fffff804`3afd7565 : 00000000`00000000 ffffd989`66891240 fffff183`bfe686b8 00000000`00000000 : nt!KiMcheckAbort+0x47d
fffff183`bfe68540 fffff804`3b0a113f : 00000000`00000001 fffff183`bfe68b80 fffff183`bfe68ad0 fffff183`bfe68870 : dxgkrnl!DXGADAPTERBYHANDLE::DXGADAPTERBYHANDLE+0x99
fffff183`bfe68590 ffffe9a0`139a983b : fffff183`bfe68ad0 ffffd989`6b6fa080 00000000`5f0686c0 ffffe9a0`00000000 : dxgkrnl!DxgkEscape+0x16f
fffff183`bfe68ab0 fffff801`bfc14003 : ffffd989`6b6fa080 00000000`00000000 00000000`00000000 ffffd989`6b85e901 : win32kbase!NtGdiDdDDIEscape+0x4b
fffff183`bfe68b00 00000000`5f074474 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`14c7e498 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x5f074474
THREAD_SHA1_HASH_MOD_FUNC: 0f6b055ca6193d0110e9aeb542a990dd38bc1705
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 94edf30b3adb8308ee1b60af40f7830e7daf5eb1
THREAD_SHA1_HASH_MOD: 26adbb50ca59cdb0546e4ef3655016a5b95213ef
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: GenuineIntel
IMAGE_NAME: GenuineIntel
DEBUG_FLR_IMAGE_TIMESTAMP: 0
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_TLB
BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_TLB
PRIMARY_PROBLEM_CLASS: 0x124_GenuineIntel_PROCESSOR_TLB
TARGET_TIME: 2018-04-04T16:23:33.000Z
OSBUILD: 16299
OSSERVICEPACK: 0
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 784
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2018-03-13 00:24:03
BUILDDATESTAMP_STR: 170928-1534
BUILDLAB_STR: rs3_release
BUILDOSVER_STR: 10.0.16299.15.amd64fre.rs3_release.170928-1534
ANALYSIS_SESSION_ELAPSED_TIME: 10ef
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x124_genuineintel_processor_tlb
FAILURE_ID_HASH: {03e060e2-37bb-3e02-4bd4-77932f0be153}
Followup: MachineOwner
0: kd> !whea
Error Source Table @ fffff801bfe16800
4 Error Sources
Error Source 0 @ ffffd9896536ebd0
Notify Type : {65450bd0-d989-ffff-0868-e1bf01f8ffff}
Type : 0x0 (MCE)
Error Count : 1
Record Count : 4
Record Length : 728
Error Records : wrapper @ ffffd9896544b000 record @ ffffd9896544b028
: wrapper @ ffffd9896544b728 record @ ffffd9896544b750
: wrapper @ ffffd9896544be50 record @ ffffd9896544be78
: wrapper @ ffffd9896544c578 record @ ffffd9896544c5a0
Descriptor : @ ffffd9896536ec29
Length : 3cc
Max Raw Data Length : 141
Num Records To Preallocate : 4
Max Sections Per Record : 4
Error Source ID : 0
Flags : 00000000
Error Source 1 @ ffffd98965450bd0
Notify Type : {65450790-d989-ffff-d0eb-366589d9ffff}
Type : 0x1 (CMC)
Error Count : 0
Record Count : 4
Record Length : 728
Error Records : wrapper @ ffffd98965449000 record @ ffffd98965449028
: wrapper @ ffffd98965449728 record @ ffffd98965449750
: wrapper @ ffffd98965449e50 record @ ffffd98965449e78
: wrapper @ ffffd9896544a578 record @ ffffd9896544a5a0
Descriptor : @ ffffd98965450c29
Length : 3cc
Max Raw Data Length : 141
Num Records To Preallocate : 4
Max Sections Per Record : 4
Error Source ID : 1
Flags : 00000000
Error Source 2 @ ffffd98965450790
Notify Type : {6541e010-d989-ffff-d00b-456589d9ffff}
Type : 0x3 (NMI)
Error Count : 0
Record Count : 1
Record Length : 6c0
Error Records : wrapper @ ffffd98965452940 record @ ffffd98965452968
Descriptor : @ ffffd989654507e9
Length : 3cc
Max Raw Data Length : 100
Num Records To Preallocate : 1
Max Sections Per Record : 3
Error Source ID : 2
Flags : 00000000
Error Source 3 @ ffffd9896541e010
Notify Type : {bfe16808-f801-ffff-9007-456589d9ffff}
Type : 0x7 (BOOT)
Error Count : 0
Record Count : 0
Record Length : 0
Error Records : Descriptor : @ ffffd9896541e069
Length : 3cc
Max Raw Data Length : 400
Num Records To Preallocate : 1
Max Sections Per Record : 1
Error Source ID : 3
Flags : 00000000
All replies (9)
Wednesday, April 4, 2018 6:41 PM
Whea 0x124 bugchecks are often related to hardware problems. However other software can cause these bugchecks.
To evaluate the BSOD please post logs for troubleshooting.
Using administrative command prompt copy and paste this whole command:
Make sure the default language is English so that the logs can be scanned and read.
https://www.tenforums.com/tutorials/3813-language-add-remove-change-windows-10-a.html
The command will automatically collect the computer files and place them on the desktop.
Then use one drive or drop box to place share links into the thread for troubleshooting.
This command will automatically collect these files: msinfo32, dxdiag, mini dumps, drivers, hosts, install, uninstall, services, startup, event viewer files, etc.
Open administrative command prompt and copy and paste the whole command:
copy %SystemRoot%\minidump\.dmp "%USERPROFILE%\Desktop\&dxdiag /t %Temp%\dxdiag.txt© %Temp%\dxdiag.txt "%USERPROFILE%\Desktop\SFdebugFiles\&type %SystemRoot%\System32\drivers\etc\hosts >> "%USERPROFILE%\Desktop\hosts.txt"&systeminfo > "%USERPROFILE%\Desktop\systeminfo.txt"&driverquery /v > "%USERPROFILE%\Desktop\drivers.txt" &msinfo32 /nfo "%USERPROFILE%\Desktop\msinfo32.nfo"&wevtutil qe System /f:text > "%USERPROFILE%\Desktop\eventlog.txt"® export HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall "%USERPROFILE%\Desktop\uninstall.txt"® export "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components" "%USERPROFILE%\Desktop\installed.txt"&net start > "%USERPROFILE%\Desktop\services.txt"&REM wmic startup list full /format:htable >"%USERPROFILE%\Desktop\startup.html"&wmic STARTUP GET Caption, Command, User >"%USERPROFILE%\Desktop\startup.txt"
There is 1 file for you to find manually: memory dump file:
C:\Windows\MEMORY.DMP
Use file explorer > this PC > local C: drive > right upper corner search enter each of the above to find results.
Sometimes the dxdiag file needs to be found and saved manually: In the left lower corner search type: dxdiag > When the DirectX Diagnostic Tool opens click on the next page button so that each tab is opened > click on save all information > save to desktop > post one drive or drop box share link into the thread
Please remember to mark the replies as answers if they help.
Wednesday, April 4, 2018 7:50 PM
Here is a Dropbox link for the requested files
https://www.dropbox.com/sh/1elyg2z17ji44t8/AACIL-PAl5HE_T72o_EUa3BPa?dl=0
Wednesday, April 4, 2018 8:37 PM
Is the computer under warranty?
There was only 1 mini and memory dump for debugging.
The logs had minimal information with the recent clean install.
Open the website for the motherboard manufacturer > enter the model > select the operating system view the latest BIOS > post a link into the thread for the most up to date BIOS for the computer's configuration.
The debugging displayed problems with 1 misbehaving hardware driver:
nvlddmkm.sys Fri Mar 23 18:02:22 2018 (5AB5877E)
Driver c:\windows\system32\driverstore\filerepository\nv_dispi.inf_amd64_c1a085cc86772d3f\nvlddmkm.sys (23.21.13.9135, 16.73 MB (17,544,792 bytes), 4/1/2018 1:36 AM)
There was also problems displayed with the CPU: TLB
Severity : Fatal
Error : DTLBL0_ERR (Proc 0 Bank 2)
1) uninstall the Nvidia GPU driver using DDU (display driver uninstaller)
2) re-install the Nvidia GPU driver from the Nvidia website
3) make sure that you check the clean install box and if available install the physx driver.
Display Driver Uninstaller Download version 17.0.8.2 (or a newer version if available)
https://www.sevenforums.com/tutorials/367109-display-driver-uninstaller-how-use.html
http://www.nvidia.com/Download/index.aspx
http://www.majorgeeks.com/files/details/display_driver_uninstaller.html
3) post the information on the most up to date BIOS for the computer's configuration
Please make sure to post the website link with this BIOS update.
4) For any BSOD after updating the Nvidia driver > run the above administrative command prompt command and place new logs into the newest post using 7zip to keep the files organized.
Wednesday, April 4, 2018 9:28 PM
The computer is not under warranty, it is a custom build I did roughly 4 years ago.
ASRock Z87 Extreme3
http://www.asrock.com/mb/Intel/Z87%20Extreme3/#BIOS
Most recent version is 2.70 as of 2016/6/29
Nvidia drivers uninstalled with DDU in safemode.
Nvidia v391.35 installed with Perform a Clean Installation selected. All components installed.
As of yet there have been no other crashes, but it hasn't been that long since these steps were performed.
Friday, April 6, 2018 2:48 AM
Since performing your suggested steps I've had a few additional BSOD. I've recreated the log files and added them to a zip file as requested as well.
https://www.dropbox.com/s/pujjft5qr1cvn7b/LogFiles.7z?dl=0
Friday, April 6, 2018 6:03 AM
There were 2 mini dump files and 1 memory dump file debugged.
- Uninstall ESET using the applicable uninstall tool:
https://support.eset.com/kb2289/
a) Make sure that Windows defender is on
b) ESET can be reinstalled 2 weeks after the last BSOD
2) Choose one of the temperature monitoring software applications: Speecy, HW monitor, Speed fan:
Speccy - Free Download - Piriform: Speccy - System Information - Free
https://www.piriform.com/speccy
HWMONITOR | Softwares | CPUID: HWMONITOR | Softwares | CPUID
http://www.cpuid.com/softwares/hwmonitor.html
SpeedFan - Access temperature sensor in your computer: SpeedFan - Access temperature sensor in your computer
http://www.almico.com/speedfan.php
For the WHEA 0x124 the major hardware components are tested: CPU, GPU, Drive, RAM
Run memtest86+ version 5.01 for at least 8 passes.
http://www.memtest.org/
This may take hours so plan to run it overnight.
a) Please make sure you use the Memtest86+ version 5.01 with the link below.
http://www.memtest.org/
The testing is done not by time but by passes.
The more passes the better.
There are a significant number of false negatives if fewer than 8 passes are made.
A false negative is a test pass when there is malfunctioning RAM.
There is 16 GB of RAM on the computer.
Memtest86+ version 5.01 testing takes approximately 1 - 2 hours /GB RAM
Just 1 error is a fail and you can abort testing.
Then test 1 RAM module at a time in the same DIMM each for 8 or more passes.
b) When Memtest86+ version 5.01 has completed 8 or more passes use a camera or smart phone camera to take a picture and post an image into the thread.
https://answers.microsoft.com/en-us/windows/wiki/windows_10-update/memory-problems/21c3f63f-f570-4522-b2ef-ecc7b7ff6461
https://www.tenforums.com/tutorials/14201-memtest86-test-ram.htmlRun HD Tune
http://www.hdtune.com/
Post images into the thread for test results on these tabs:
a) Health (SMART)
b) Benchmark
c) Full error scanMake sure that there is no over clocking while troubleshooting
Reset the BIOS:
How to Clear Your Computers CMOS to Reset BIOS Settings:
https://www.howtogeek.com/131623/how-to-clear-your-computers-cmos-to-reset-bios-settings/
3 Ways to Reset Your BIOS - wikiHow:
http://www.wikihow.com/Reset-Your-BIOS
8) Open administrative command prompt and type or copy and paste: chkdsk /x /f /r
The type of the file system is NTFS.
Cannot lock current drive.
Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)
Type: Y
reboot
This may take many hours and can be run overnight.
There were multiple new misbehaving software drivers:
eamonm.sys
em018k_64.sys
ehdrv.sys
These were all ESET drivers.
The WHEA 0x124 error has switched from
First BSOD:
Severity : Fatal
Error : DTLBL0_ERR (Proc 0 Bank 2)
Second BSOD:
Severity : Fatal
Error : DCACHEL0_WR_ERR (Proc 0 Bank 1)
The Nvidia drivers misbehaved again with the same version:
First BSOD:
nvlddmkm.sys Fri Mar 23 18:02:22 2018 (5AB5877E)
c:\windows\system32\driverstore\filerepository\nv_dispi.inf_amd64_c1a085cc86772d3f\nvlddmkm.sys (23.21.13.9135, 16.73 MB (17,544,792 bytes), 4/1/2018 1:36 AM)
Second BSOD:
nvlddmkm.sys Fri Mar 23 18:02:22 2018 (5AB5877E)
c:\windows\system32\driverstore\filerepository\nv_dispi.inf_amd64_c1a085cc86772d3f\nvlddmkm.sys (23.21.13.9135, 16.73 MB (17,544,792 bytes), 4/5/2018 11:38 AM)
Friday, April 6, 2018 8:22 AM
From the dump, seems that the bsod issue is related to hardware error. And since you have already re-installed the system, then it may not related to the system itself. It is suggested that you can test your machine hardware to make sure that they all work well, especially CPU etc .
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Tuesday, April 10, 2018 9:19 AM
Are there any updates?
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Wednesday, April 11, 2018 6:22 PM
Please update your progress with the earlier steps.
If you submit new logs they can be troubleshooted.