Windows Black Screen

Question

Hello, I was on my computer playing a video game Halo: Infinite when all of a sudden the game froze and the screen turned black and wouldn't get a display. When I restarted my computer I opened the Event Viewer program and had a bugcheck event log, I opened the dump file and this is what is said:

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

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

************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff801`08400000 PsLoadedModuleList = 0xfffff801`0902a230
Debug session time: Sat Aug  6 00:23:31.489 2022 (UTC + 9:30)
System Uptime: 14 days 8:39:12.141
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..........
Loading User Symbols
Loading unloaded module list
..................................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff801`087f8590 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffd380`50152c90=0000000000000101
6: 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: 0000000000000010, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffffd3804fddd180, The PRCB address of the hung processor.
Arg4: 0000000000000002, The index of the hung processor.

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2312

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 3953

    Key  : Analysis.Init.CPU.mSec
    Value: 265

    Key  : Analysis.Init.Elapsed.mSec
    Value: 3237

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 87

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x101

    Key  : Bugcheck.Code.Register
    Value: 0x101

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1

FILE_IN_CAB:  080622-12593-01.dmp

BUGCHECK_CODE:  101

BUGCHECK_P1: 10

BUGCHECK_P2: 0

BUGCHECK_P3: ffffd3804fddd180

BUGCHECK_P4: 2

FAULTING_PROCESSOR: 2

FAULTING_THREAD:  ffff8d86b15f9080

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  Discord.exe

BAD_STACK_POINTER:  ffffa20d1763efb8

STACK_TEXT:  
ffffa20d`1763efb8 ffff780b`d9e83f64     : 00000b48`e11d67b5 ffff8d86`a258d0f0 ffffd380`4fddd180 00000000`00000000 : intelppm!MWaitIdle+0x1f
ffffa20d`1763efc0 00000b48`e11d67b5     : ffff8d86`a258d0f0 ffffd380`4fddd180 00000000`00000000 00000000`00000003 : 0xffff780b`d9e83f64
ffffa20d`1763efc8 ffff8d86`a258d0f0     : ffffd380`4fddd180 00000000`00000000 00000000`00000003 fffff801`086ac66b : 0x00000b48`e11d67b5
ffffa20d`1763efd0 ffffd380`4fddd180     : 00000000`00000000 00000000`00000003 fffff801`086ac66b ffff8d86`a258d318 : 0xffff8d86`a258d0f0
ffffa20d`1763efd8 00000000`00000000     : 00000000`00000003 fffff801`086ac66b ffff8d86`a258d318 00000000`00000000 : 0xffffd380`4fddd180

SYMBOL_NAME:  intelppm!MWaitIdle+1f

MODULE_NAME: intelppm

IMAGE_NAME:  intelppm.sys

IMAGE_VERSION:  10.0.19041.1620

STACK_COMMAND:  .process /r /p 0xffff8d86b28b70c0; .thread 0xffff8d86b15f9080 ; kb

BUCKET_ID_FUNC_OFFSET:  1f

FAILURE_BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_INTERRUPTS_DISABLED_STACKPTR_ERROR_intelppm!MWaitIdle

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {872c8f1b-4661-53bd-eafe-e4b46979aa55}

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

I don't really understand what it's saying but I believe this error "CLOCK_WATCHDOG_TIMEOUT" seems to be the problem?
Thank you for anyone's assistance.

Answer 1

Hi Che Stephenson

The LED light sequence would be different for most motherboards, I am not familiar with your motherboard, please do perform the MemTest86 4 pass scan if the crash does happen again.

Answer 2

Thanks for the reply. I've updated the bios to the latest version and I'm pretty sure I have all the chipset drivers installed. Does the minidump file indicate actually what chipset driver is the issue?

This is the first time I've encountered this issue so I'm not sure when it will happen again (if it does).

Also now when I turn on my computer the VGA, RAM, CPU and boot red lights turn on once individually but still get a boot and computer seems to still work. Does this mean anything?

If it does happen again I'll do a MemTest like you suggested, and report back.

Answer 3

Hi Che Stephenson

Your minidump file indicates memory (RAM) corruption and the chipset devide driver.

1

Go to the support page for your PC or Motherboard on the manufacturers website, then from there, download and install the version of Chipset drivers they recommend and while there, check for any BIOS update that may need to be installed

2

Wait to see if your system stabilizes, if not, the best option is to download the widely available free utility MemTest86, then run a full 4 pass scan with that to test your RAM for physical errors

Answer 4

https://1drv.ms/u/s!Amm_l-iX6D84g0Pev2SgNmz1K02V?e=YuNl2d

Here we go :)

Answer 5

Hi Che Stephenson

I am Dave, I will help you with this.

Please upload any minidump files you have, I will check those to see if they provide any insight into a potential cause of the system crashes.

Open Windows File Explorer.

Navigate to C:\Windows\Minidump

Copy any minidump files onto your Desktop, then zip those up.

Upload the zip file to the Cloud (OneDrive, DropBox... etc.), then choose to share those and get a share link.

Then post the link here to the zip file, so we can take a look for you.