Share via

Kernel-Power event 41 - BOSD

Anonymous
2024-10-29T15:31:52+00:00

Hello,

Today, when I was playing War Thunder, I got BOSD. I pressed on the Windows key to go on YouTube and the screen froze and after a few seconds I got blue screen.

I copied below the mini dump.

************* Preparing the environment for Debugger Extensions Gallery repositories **************
   ExtensionRepository : Implicit
   UseExperimentalFeatureForNugetShare : true
   AllowNugetExeUpdate : true
   NonInteractiveNuget : true
   AllowNugetMSCredentialProviderInstall : true
   AllowParallelInitializationOfLocalRepositories : true
   EnableRedirectToChakraJsProvider : false

   -- Configuring repositories
      ----> Repository : LocalInstalled, Enabled: true
      ----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.000 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 42

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

Loading Dump File [C:\Users\bEbE\Desktop\102924-8312-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 22621 MP (32 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff804`5c200000 PsLoadedModuleList = 0xfffff804`5ce134f0
Debug session time: Tue Oct 29 16:50:13.285 2024 (UTC + 2:00)
System Uptime: 0 days 3:12:56.937
Loading Kernel Symbols
...............................................................
................................................................
................................................................
........................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000055`ff797018).  Type ".hh dbgerr001" for details
Loading unloaded module list
.........................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff804`5c614d50 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffb200`c152b9f0=0000000000000101
10: 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: 0000000000000006, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffffb200c1451180, The PRCB address of the hung processor.
Arg4: 0000000000000009, The index of the hung processor.

Debugging Details:
------------------
KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 406

    Key  : Analysis.Elapsed.mSec
    Value: 1209

    Key  : Analysis.IO.Other.Mb
    Value: 0

    Key  : Analysis.IO.Read.Mb
    Value: 1

    Key  : Analysis.IO.Write.Mb
    Value: 0

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27725.1000

    Key  : Analysis.Version.Description
    Value: 10.2408.27.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2408.27.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x101

    Key  : Bugcheck.Code.TargetModel
    Value: 0x101

    Key  : Dump.Attributes.AsUlong
    Value: 1808

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0

    Key  : Failure.Bucket
    Value: CLOCK_WATCHDOG_TIMEOUT_INTERRUPTS_DISABLED_nt!KiSwapContext

    Key  : Failure.Hash
    Value: {65022177-f8d7-d86e-687a-3d30c86c71d3}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 1417df84

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 0

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 1

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 1

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 1

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 1

    Key  : Hypervisor.Flags.HardwareMbecAvailable
    Value: 1

    Key  : Hypervisor.Flags.MaxBankNumber
    Value: 0

    Key  : Hypervisor.Flags.MemoryZeroingControl
    Value: 0

    Key  : Hypervisor.Flags.NoExtendedRangeFlush
    Value: 0

    Key  : Hypervisor.Flags.NoNonArchCoreSharing
    Value: 1

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 1

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 1

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 21631230

    Key  : Hypervisor.Flags.ValueHex
    Value: 14a10fe

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 1

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 1

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 1

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 1

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 1

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 1

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.Value
    Value: 1015

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 3f7

    Key  : Stack.Pointer
    Value: ISR
BUGCHECK_CODE:  101

BUGCHECK_P1: 6

BUGCHECK_P2: 0

BUGCHECK_P3: ffffb200c1451180

BUGCHECK_P4: 9

FILE_IN_CAB:  102924-8312-01.dmp

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b

DUMP_FILE_ATTRIBUTES: 0x1808
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffff9b0fd5fc0080

FAULTING_PROCESSOR: 9

PROCESS_NAME:  aces.exe

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

STACK_TEXT:  
ffffc206`ea5277f0 fffff804`5c41661e     : ffffc206`ea5279b9 00000000`00000000 00000000`00000000 ffffb200`c1511180 : nt!KiSwapContext+0x76
ffffc206`ea527930 fffff804`01617985     : 00000000`c0558948 00000000`00000008 00000000`00000000 00000000`00000008 : nt!KiDispatchInterrupt+0x67e
ffffc206`ea527a20 00000000`c0558948     : 00000000`00000008 00000000`00000000 00000000`00000008 00000055`80495418 : 0xfffff804`01617985
ffffc206`ea527a28 00000000`00000008     : 00000000`00000000 00000000`00000008 00000055`80495418 00000000`00000019 : 0xc0558948
ffffc206`ea527a30 00000000`00000000     : 00000000`00000008 00000055`80495418 00000000`00000019 00000055`80495650 : 0x8

SYMBOL_NAME:  nt!KiSwapContext+76

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.22621.4391

STACK_COMMAND:  .process /r /p 0xffff9b0fd51130c0; .thread 0xffff9b0fd5fc0080 ; kb

BUCKET_ID_FUNC_OFFSET:  76

FAILURE_BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_INTERRUPTS_DISABLED_nt!KiSwapContext

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {65022177-f8d7-d86e-687a-3d30c86c71d3}

Followup:     MachineOwner
---------
Windows for home | Windows 11 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

3 answers

Sort by: Most helpful
  1. Anonymous
    2024-10-31T01:10:29+00:00

    Hi, Oana-Georgiana Secuian

    Thank you for your reply!

    I noticed that your CPU is 14th generation Intel. Previously, Intel had reported that there were process problems with 13th and 14th generation CPUs (especially i7 and i9). This process defect can cause the CPU to run at high intensity, resulting in black screen, blue screen and inability to boot. Therefore, if you still encounter a blue screen after trying all the solutions that can be operated in Windows system, you need to consider the manufacturing defect of the CPU. You can consult Intel official after-sales support for details.

    You can reply to my private message according to the steps below and send us your minidump file in the private message so that we can further analyze whether the cause of the blue screen is related to the CPU driver and related programs:

    1.You can send private message through the Messages link at the top right of the page.

    2.Check your sent PM by going to My Profile, and then selecting View private messages on the left pane of your profile page.

     

     

    You may see the message that I sent you earlier.

    If you still encounter difficulties, you are welcome to contact us at any time.

    Best Regards

    Nicholas.Z - MSFT | Microsoft Community Support Specialist

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2024-10-30T15:46:49+00:00

    Hi, Nicholas.Z - MSFT | Microsoft Community Support Specialist

    So.

    **I. Hardware check:**I also tested the ram yesterday and today (windows memory diagnostic tool) and it didn't find anything, 0 errors. I always use HWINFO 64, HW MONITOR AND MSI AFTERBURNER and all temperatures are good, examples:

    Intense gameing:

    Rust 10-12 hours,

    Red Dead Redemption2 4-6 hours

    Ghost of Tsushima 6 hours

    Farr cry6 10 hours and so on... Warthunder between 5-15hours every day the cpu did not exceed 65, it is between 50-65 video card there is no point in saying never passed by 61 degrees and the rest of the components including the power source or the ssd are at normal temperatures, the ssd below 45-50:

    The PC:

    i9 14900k

    RTX 4090 ROG strix white

    64 RAM CORSAIR ddr5 CMP64GX5M2B6400C32W

    CORSAIR MP700 PRO GEN 5.0 NVM2 2TB

    POWER SUPPLY HX1500I CORSAIR

    **III.Malware Scan:**I did an anti-virus scan with windows security and nothing,

    **IV. Repair your system:**I did all 4 tips in cmd and nothing, 0 errors or anything else, I also have a picture of the result.

    Image

    I also tested the processor in aida64, cinebench r23 and cpuid please cpu-z.

    In the past I have had BOSDs and I would like to attach the minidumps but I don't know how.

    if you can help me to send you the minidumps as you know better to look in them

    Best Regards

    Oana-Georgiana Secuian

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2024-10-30T02:56:21+00:00

    Hi, Oana-Georgiana Secuian

    Welcome to Microsoft Community.

    We understand that you are experiencing a blue screen issue while playing War Thunder, and from the blue screen log you provided, the error code is "CLOCK_WATCHDOG_TIMEOUT". This usually occurs when one or more processors in a multi-core system are having problems and they are unable to respond to clock interrupts within the allocated timeframe. 

    Possible causes: -Hardware problems (such as RAM failures, component overheating, or hardware failures) may trigger such errors.-Software conflicts (especially those involving drivers or low-level system processes) may also cause this problem.-Malware or corrupted system files may cause unexpected behavior leading to a blue screen of death. It is recommended that you can try the following steps:

    I. Hardware check: Run a diagnostic on your RAM using Windows Memory Diagnostic Tool or other trusted software.And use specialized software to check the temperatures of key components such as the CPU and GPU to make sure they are within safe operating limits.II.Software updates:Make sure all device drivers (especially those for motherboard chipsets and network adapters) are up to date. Please visit your hardware manufacturer's official website to download the drivers corresponding to your hardware model and system version. III.Malware Scan:

    Perform a thorough malware scan using Windows Defender or a reputable antivirus program. **IV. Repair your system:**1. Search for CMD, find the command prompt, and choose to run in administrator mode.2. Enter the following commands one by one, and be sure to execute the next command after the previous one is completed.DISM /Online /Cleanup-Image /ScanHealthDISM /Online /Cleanup-Image /CheckHealthDISM /Online /Cleanup-Image /RestoreHealthSFC /Scannow3. After the scan is complete, you can check the scan information to see if the problem has been detected and fixed.V.Clean Boot: Try to perform a clean boot to determine if any third-party applications are causing conflicts:1. Tap Windows+R and type msconfig2. Open System Configuration and select the General tab - Selective Startup.3. Remove the check from Load startup items.4. Go to the Services tab - click Hide all microsoft services in the lower left corner, and then click Disable all.5. Click OK and restart your computer. (Be sure to select Hide all Microsoft services first and then click Disable all, otherwise it may cause unforeseen problems such as not being able to access the system.)Check to see if the problem still recurs.*Disclaimer: A “clean boot” starts Windows with a minimal set of drivers and startup programs. It helps to determine whether a background service is interfering with your game or program and to isolate the cause of a problem.**These steps of "clean boot" might look complicated at first glance. However, to avoid any trouble for you, please follow them in order and step-by step so that it will help you get back on track.*VI. Repairing the systemIn order to rule out problems caused by Windows system components, you can repair your system directly through Media Creation Tool, which is not a reinstallation of the system, it will repair your system without deleting files or applications. However, if you have important data on your computer, we still recommend backing it up in advance.Once you have completed your backup, follow the steps in the guide below:Download Windows 11Visit the site above and select Download Tool Now - Run the Media Creation Tool - Select Yes - Select Accept - Select Create Installation Media for Another Computer - Select DVD ISO File - Save As Local File.If you want to download version 23H2 of Windows 11 then you can follow the link provided by volunteer host Ramesh in the link below to get the ISO and then follow the same stepsDownload iso of windows 11 that is older than the newest update (a - Microsoft CommunityRun the local WINDOWS. iso file - Right click - Mount - Select Run setup.exe - Select Don't use for now - Select Keep personal files and settings - Select Next - Wait for WINDOWS Repair to finish installing - Restart your WINDOWS computer.Disclaimer: Let’s try performing an in-place install or in-place upgrade which will refresh your Windows files and operating system without removing files or applications. That being said, we always recommend that if you have important data, you should back it up before making large system changes. If you want to back up your data first, please do so. Once you are done backing up, you can follow the steps in the following guides:How to run In-place upgrade in Windows 11 - Microsoft CommunityIf these steps do not solve the problem, after our inquiry, this is more common among War Thunder gamers, which is related to the game itself, we recommend you to consult the game official directly.

    Best Regards

    Nicholas.Z - MSFT | Microsoft Community Support Specialist

    Was this answer helpful?

    0 comments No comments