B
BrianD87
Specs:
Windows 10 Pro 1809
AsRock 970 Pro 3
AMD FX8120
NVIDIA GTX 560Ti
8GB DDR3 1600 RAM (all voltages and timings set correctly)
I have been dealing with a BSOD (SYNTHETIC_WATCHDOG_TIMEOUT (1ca)) issue for quite a while now. It started in November of last year, but has started happening more often, almost daily for the past 2 weeks.
I have updated/removed drivers, analyzed dump files, uninstalled random utilities, but no luck. I tried driver verifier, and that just caused an instant BSOD.
Also, when running a Windows Memory Diagnostic, it instantly (before 1%) flashes that "Hardware problems were detected." I have tested both RAM modules together, individually, in different slots, and even a different set of known working RAM, and it always throws this error. However, when running memtest86+, I get no errors whatsoever after several hours.
I have always had Hyper V enabled, with a Windows 10 VM that I would use occasionally, but I have been using it more to work from home recently, and that also when this issue started occurring more often. I noticed another post on reddit and some other forums dealing with a similar issue that they suspected had to do with hyper-v and my dumps looked pretty similar. View: https://www.reddit.com/r/HyperV/comments/djqnhk/encountering_bsods_on_windows_10_hyperv_host/
I do have a copy of the full dump from my most recent BSOD, but it is 8GB in size, so not sure how to upload it. I have the minidump as well.
Any help would be appreciated!
Here is the text from WinDBG:
Microsoft (R) Windows Debugger Version 10.0.18362.1 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\MEMORY.DMP]
Kernel Bitmap Dump File: Full address space is available
************* Path validation summary **************
Response Time (ms) Location
Deferred srv*c:\symbols*Symbol information
Symbol search path is: srv*c:\symbols*Symbol information
Executable search path is:
Windows 10 Kernel Version 18362 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff802`44200000 PsLoadedModuleList = 0xfffff802`44648150
Debug session time: Tue Apr 14 17:15:04.769 2020 (UTC - 4:00)
System Uptime: 0 days 0:48:18.625
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
............
For analysis of this file, run !analyze -v
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYNTHETIC_WATCHDOG_TIMEOUT (1ca)
A system wide watchdog has expired. This indicates that the system
is hung and not processing timer ticks.
Arguments:
Arg1: 000000001baddcef, The time since the watchdog was last reset, in interrupt time.
Arg2: 00000006fd71cfd7, The current interrupt time.
Arg3: 0000000a022d139c, The current QPC timestamp.
Arg4: 0000000000000003, The index of the clock processor.
Debugging Details:
------------------
KEY_VALUES_STRING: 1
PROCESSES_ANALYSIS: 1
SERVICE_ANALYSIS: 1
STACKHASH_ANALYSIS: 1
TIMELINE_ANALYSIS: 1
DUMP_CLASS: 1
DUMP_QUALIFIER: 402
BUILD_VERSION_STRING: 18362.1.amd64fre.19h1_release.190318-1202
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.00
BIOS_DATE: 10/24/2014
BASEBOARD_MANUFACTURER: ASRock
BASEBOARD_PRODUCT: 970 Pro3
BASEBOARD_VERSION:
DUMP_TYPE: 0
BUGCHECK_P1: 1baddcef
BUGCHECK_P2: 6fd71cfd7
BUGCHECK_P3: a022d139c
BUGCHECK_P4: 3
CPU_COUNT: 8
CPU_MHZ: c15
CPU_VENDOR: AuthenticAMD
CPU_FAMILY: 15
CPU_MODEL: 1
CPU_STEPPING: 2
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x1CA
PROCESS_NAME: System
CURRENT_IRQL: f
ANALYSIS_SESSION_HOST: BD8120
ANALYSIS_SESSION_TIME: 04-14-2020 20:03:22.0685
ANALYSIS_VERSION: 10.0.18362.1 amd64fre
BAD_STACK_POINTER: fffff80248b04c68
LAST_CONTROL_TRANSFER: from fffff80244191a55 to fffff802443c2380
STACK_TEXT:
fffff802`48b04c68 fffff802`44191a55 : 00000000`000001ca 00000000`1baddcef 00000006`fd71cfd7 0000000a`022d139c : nt!KeBugCheckEx
fffff802`48b04c70 fffff802`4417bdec : 0000000a`022d139c 00000000`00000001 fffff802`44554614 00000000`00000082 : hal!HalpWatchdogCheckPreResetNMI+0xd5
fffff802`48b04cb0 fffff802`444a500b : 00000000`00000001 0000000a`022b1870 fffff802`41ce0180 fffff802`444b6310 : hal!HalpPreprocessNmi+0x11e5c
fffff802`48b04ce0 fffff802`443cd942 : 00000000`00000001 fffff802`48b04ef0 00000000`00000000 00000000`00000000 : nt!KiProcessNMI+0xcb
fffff802`48b04d30 fffff802`443cd714 : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxNmiInterrupt+0x82
fffff802`48b04e70 fffff802`44504d8e : 00000000`00000000 00000885`4fe124ed 00000000`00000000 0000000a`022b1870 : nt!KiNmiInterrupt+0x214
fffff802`48aeb7a0 fffff802`442bb69c : fffff802`44504db0 ffffc485`a7238010 00000000`00000000 00000000`000002ed : nt!PpmIdleGuestExecute+0x1e
fffff802`48aeb7e0 fffff802`442badee : 00000000`00000003 00000000`00000002 00000000`00000002 00000000`00000000 : nt!PpmIdleExecuteTransition+0x70c
fffff802`48aebb00 fffff802`443c5e88 : 00000000`00000000 fffff802`41ce0180 ffffc485`ab00a080 00000000`00000a3d : nt!PoIdle+0x36e
fffff802`48aebc60 00000000`00000000 : fffff802`48aec000 fffff802`48ae6000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x48
THREAD_SHA1_HASH_MOD_FUNC: cb522721ccf98392c0a19a23914952c2ac4c66ec
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: be98a3f87cbb279b0838b6b9023bfedcfc98852a
THREAD_SHA1_HASH_MOD: 77e3653e8f322fbd447ccc02351d9fed3c4e96be
FOLLOWUP_IP:
nt!KiProcessNMI+cb
fffff802`444a500b 488b3deea11a00 mov rdi,qword ptr [nt!KiNmiCallbackListHead (fffff802`4464f200)]
FAULT_INSTR_CODE: ee3d8b48
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!KiProcessNMI+cb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 0
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: cb
FAILURE_BUCKET_ID: 0x1CA_STACKPTR_ERROR_nt!KiProcessNMI
BUCKET_ID: 0x1CA_STACKPTR_ERROR_nt!KiProcessNMI
PRIMARY_PROBLEM_CLASS: 0x1CA_STACKPTR_ERROR_nt!KiProcessNMI
TARGET_TIME: 2020-04-14T21:15:04.000Z
OSBUILD: 18362
OSSERVICEPACK: 0
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: unknown_date
BUILDDATESTAMP_STR: 190318-1202
BUILDLAB_STR: 19h1_release
BUILDOSVER_STR: 10.0.18362.1.amd64fre.19h1_release.190318-1202
ANALYSIS_SESSION_ELAPSED_TIME: 2f5c
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x1ca_stackptr_error_nt!kiprocessnmi
FAILURE_ID_HASH: {09a889cd-f940-6da5-9668-0c0c98a7d643}
Followup: MachineOwner
---------
Continue reading...
Windows 10 Pro 1809
AsRock 970 Pro 3
AMD FX8120
NVIDIA GTX 560Ti
8GB DDR3 1600 RAM (all voltages and timings set correctly)
I have been dealing with a BSOD (SYNTHETIC_WATCHDOG_TIMEOUT (1ca)) issue for quite a while now. It started in November of last year, but has started happening more often, almost daily for the past 2 weeks.
I have updated/removed drivers, analyzed dump files, uninstalled random utilities, but no luck. I tried driver verifier, and that just caused an instant BSOD.
Also, when running a Windows Memory Diagnostic, it instantly (before 1%) flashes that "Hardware problems were detected." I have tested both RAM modules together, individually, in different slots, and even a different set of known working RAM, and it always throws this error. However, when running memtest86+, I get no errors whatsoever after several hours.
I have always had Hyper V enabled, with a Windows 10 VM that I would use occasionally, but I have been using it more to work from home recently, and that also when this issue started occurring more often. I noticed another post on reddit and some other forums dealing with a similar issue that they suspected had to do with hyper-v and my dumps looked pretty similar. View: https://www.reddit.com/r/HyperV/comments/djqnhk/encountering_bsods_on_windows_10_hyperv_host/
I do have a copy of the full dump from my most recent BSOD, but it is 8GB in size, so not sure how to upload it. I have the minidump as well.
Any help would be appreciated!
Here is the text from WinDBG:
Microsoft (R) Windows Debugger Version 10.0.18362.1 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\MEMORY.DMP]
Kernel Bitmap Dump File: Full address space is available
************* Path validation summary **************
Response Time (ms) Location
Deferred srv*c:\symbols*Symbol information
Symbol search path is: srv*c:\symbols*Symbol information
Executable search path is:
Windows 10 Kernel Version 18362 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff802`44200000 PsLoadedModuleList = 0xfffff802`44648150
Debug session time: Tue Apr 14 17:15:04.769 2020 (UTC - 4:00)
System Uptime: 0 days 0:48:18.625
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
............
For analysis of this file, run !analyze -v
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYNTHETIC_WATCHDOG_TIMEOUT (1ca)
A system wide watchdog has expired. This indicates that the system
is hung and not processing timer ticks.
Arguments:
Arg1: 000000001baddcef, The time since the watchdog was last reset, in interrupt time.
Arg2: 00000006fd71cfd7, The current interrupt time.
Arg3: 0000000a022d139c, The current QPC timestamp.
Arg4: 0000000000000003, The index of the clock processor.
Debugging Details:
------------------
KEY_VALUES_STRING: 1
PROCESSES_ANALYSIS: 1
SERVICE_ANALYSIS: 1
STACKHASH_ANALYSIS: 1
TIMELINE_ANALYSIS: 1
DUMP_CLASS: 1
DUMP_QUALIFIER: 402
BUILD_VERSION_STRING: 18362.1.amd64fre.19h1_release.190318-1202
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.00
BIOS_DATE: 10/24/2014
BASEBOARD_MANUFACTURER: ASRock
BASEBOARD_PRODUCT: 970 Pro3
BASEBOARD_VERSION:
DUMP_TYPE: 0
BUGCHECK_P1: 1baddcef
BUGCHECK_P2: 6fd71cfd7
BUGCHECK_P3: a022d139c
BUGCHECK_P4: 3
CPU_COUNT: 8
CPU_MHZ: c15
CPU_VENDOR: AuthenticAMD
CPU_FAMILY: 15
CPU_MODEL: 1
CPU_STEPPING: 2
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x1CA
PROCESS_NAME: System
CURRENT_IRQL: f
ANALYSIS_SESSION_HOST: BD8120
ANALYSIS_SESSION_TIME: 04-14-2020 20:03:22.0685
ANALYSIS_VERSION: 10.0.18362.1 amd64fre
BAD_STACK_POINTER: fffff80248b04c68
LAST_CONTROL_TRANSFER: from fffff80244191a55 to fffff802443c2380
STACK_TEXT:
fffff802`48b04c68 fffff802`44191a55 : 00000000`000001ca 00000000`1baddcef 00000006`fd71cfd7 0000000a`022d139c : nt!KeBugCheckEx
fffff802`48b04c70 fffff802`4417bdec : 0000000a`022d139c 00000000`00000001 fffff802`44554614 00000000`00000082 : hal!HalpWatchdogCheckPreResetNMI+0xd5
fffff802`48b04cb0 fffff802`444a500b : 00000000`00000001 0000000a`022b1870 fffff802`41ce0180 fffff802`444b6310 : hal!HalpPreprocessNmi+0x11e5c
fffff802`48b04ce0 fffff802`443cd942 : 00000000`00000001 fffff802`48b04ef0 00000000`00000000 00000000`00000000 : nt!KiProcessNMI+0xcb
fffff802`48b04d30 fffff802`443cd714 : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxNmiInterrupt+0x82
fffff802`48b04e70 fffff802`44504d8e : 00000000`00000000 00000885`4fe124ed 00000000`00000000 0000000a`022b1870 : nt!KiNmiInterrupt+0x214
fffff802`48aeb7a0 fffff802`442bb69c : fffff802`44504db0 ffffc485`a7238010 00000000`00000000 00000000`000002ed : nt!PpmIdleGuestExecute+0x1e
fffff802`48aeb7e0 fffff802`442badee : 00000000`00000003 00000000`00000002 00000000`00000002 00000000`00000000 : nt!PpmIdleExecuteTransition+0x70c
fffff802`48aebb00 fffff802`443c5e88 : 00000000`00000000 fffff802`41ce0180 ffffc485`ab00a080 00000000`00000a3d : nt!PoIdle+0x36e
fffff802`48aebc60 00000000`00000000 : fffff802`48aec000 fffff802`48ae6000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x48
THREAD_SHA1_HASH_MOD_FUNC: cb522721ccf98392c0a19a23914952c2ac4c66ec
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: be98a3f87cbb279b0838b6b9023bfedcfc98852a
THREAD_SHA1_HASH_MOD: 77e3653e8f322fbd447ccc02351d9fed3c4e96be
FOLLOWUP_IP:
nt!KiProcessNMI+cb
fffff802`444a500b 488b3deea11a00 mov rdi,qword ptr [nt!KiNmiCallbackListHead (fffff802`4464f200)]
FAULT_INSTR_CODE: ee3d8b48
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!KiProcessNMI+cb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 0
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: cb
FAILURE_BUCKET_ID: 0x1CA_STACKPTR_ERROR_nt!KiProcessNMI
BUCKET_ID: 0x1CA_STACKPTR_ERROR_nt!KiProcessNMI
PRIMARY_PROBLEM_CLASS: 0x1CA_STACKPTR_ERROR_nt!KiProcessNMI
TARGET_TIME: 2020-04-14T21:15:04.000Z
OSBUILD: 18362
OSSERVICEPACK: 0
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: unknown_date
BUILDDATESTAMP_STR: 190318-1202
BUILDLAB_STR: 19h1_release
BUILDOSVER_STR: 10.0.18362.1.amd64fre.19h1_release.190318-1202
ANALYSIS_SESSION_ELAPSED_TIME: 2f5c
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x1ca_stackptr_error_nt!kiprocessnmi
FAILURE_ID_HASH: {09a889cd-f940-6da5-9668-0c0c98a7d643}
Followup: MachineOwner
---------
Continue reading...