Windows 10: BSOD random restarts on new hardware, error 0x00000124

Yes, it does. No problems at all. Moreover, linux has all the drivers out of the box. The only problem that it crashes randomly exactly like Windows and leaves no traces of that.

 

Is the CPU core voltage correct and or are the turbo settings correct? Just seen a case on Toms Hardware where auto was applying over voltage and a higher Turbo than it should have been.

 

Last BSOD was with Turbo disabled. Before it was set to auto.

 

Please fill in your system specsPlease follow this tutorial and download the tool. The tool will give you detailed information about your system specs, please fill in your system specs more completely including PSU, cooling and other used stuff like mouse, keyboard, monitor, case, etc.
The PSU, cooling and other stuff are NOT mentioned in the tool.
In the left corner below in your post you find 'My System Specs'. After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.

 

Updated my system specs.

Latest mini dump contents:
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffffe1805e281180, The PRCB address of the hung processor.
Arg4: 0000000000000002, The index of the hung processor.

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10.0.15063.296 (WinBuild.160101.0800)

SYSTEM_MANUFACTURER: System manufacturer

SYSTEM_PRODUCT_NAME: System Product Name

SYSTEM_SKU: SKU

SYSTEM_VERSION: System Version

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 0906

BIOS_DATE: 03/22/2017

BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT: STRIX Z270G GAMING

BASEBOARD_VERSION: Rev 1.xx

DUMP_TYPE: 2

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

BUGCHECK_P1: 18

BUGCHECK_P2: 0

BUGCHECK_P3: ffffe1805e281180

BUGCHECK_P4: 2

BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_8_PROC

CPU_COUNT: 8

CPU_MHZ: 1068

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: 9

CPU_MICROCODE: 6,9e,9,0 (F,M,S,R) SIG: 42'00000000 (cache) 42'00000000 (init)

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

CURRENT_IRQL: d

ANALYSIS_SESSION_HOST: DESKTOP-RM91385

ANALYSIS_SESSION_TIME: 05-25-2017 14:52:29.0729

ANALYSIS_VERSION: 10.0.15063.137 amd64fre

STACK_TEXT:
fffff800`6dd33bc8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx


STACK_COMMAND: kb

THREAD_SHA1_HASH_MOD_FUNC: 81a83ae0317433a47fcc36991983df3b6e638b71

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 6e16edd8c7dd677734fdbcd2397a2e35e9fae964

THREAD_SHA1_HASH_MOD: 76cd06466d098060a9eb26e5fd2a25cb1f3fe0a3

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

BUCKET_ID: ZEROED_STACK_CLOCK_WATCHDOG_TIMEOUT_8_PROC

DEFAULT_BUCKET_ID: ZEROED_STACK_CLOCK_WATCHDOG_TIMEOUT_8_PROC

PRIMARY_PROBLEM_CLASS: ZEROED_STACK

FAILURE_BUCKET_ID: ZEROED_STACK_CLOCK_WATCHDOG_TIMEOUT_8_PROC

TARGET_TIME: 2017-05-25T12:51:05.000Z

OSBUILD: 15063

OSSERVICEPACK: 296

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2017-04-28 01:52:30

BUILDDATESTAMP_STR: 160101.0800

BUILDLAB_STR: WinBuild

BUILDOSVER_STR: 10.0.15063.296

ANALYSIS_SESSION_ELAPSED_TIME: 35b

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:zeroed_stack_clock_watchdog_timeout_8_proc

FAILURE_ID_HASH: {19e7e96e-9b82-56a8-a247-c2b766198fd7}

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

IntelBurnTest after 20 passes triggers no errors as well as Prime 95.

I noticed that most crashes happen under graphics load. Got three crashes today: first one did not show any BSOD and just rebooted (YouTube + FurMark); other two were CLOCK_WATCHDOG_TIMEOUT (Cities Skylines). See dump above.

 

A kernel dump would be more useful, upload it to a 3rd party uploader and post a share link in your next reply.

 

I believe you mean the C:\Windows\MEMORY.DMP file.

eeaga may not know the distinction, though it may be inferred by the implication that it is a larger file.

 

Since my last post I only had 0x124 bug checks while playing Cities Skylines. I gathered info with log collector again, all latest mini dump files are there.

Windows settings for system failure are set to generate Kernel memory dump. Here is a link to WINDOWS.DMP.

I am seriously thinking about RMA for both mobo and processor.

 

Could you upload a kernel dump of a 0x101 next time *Smile

Please remove your Qualcomm Atheros network adapter.

 

Hey guys. The problem was solved by replacing the processor. No crashes for two weeks now. I felt like I had to report this for people who might run into similar issues.

 

Glad to hear your issue is resolved and thank you for posting what the cause was *Smile