Bluescreen Pillars of eternity 2 [2023] Can we finally put an End to this?

[Larry Ohboi]

I see a lot of topic related to this over the years everytime it is the same comments without any solution. 

My PC hardware setup, like for a lot of ppl, for sure is not the issue. I receive the Bluescreen mainly when I change locations - Loading screen (95%) or when I try to save a game (5%). I can stay in combat or roam around the city without any problem.

I can play a lot of different games with high resource usage without any Problem.

Interesting fact: GPU usage at first was at 95-99%  (without encountering Temperature issues)

After Optimizing via Geforce Experience it corrected itself to like 40%. But still, the Bluescreens happen (I try to convince myself it happens a little bit less often)

Windows is up to date

Hardware drivers are up to date

 

The Dump file or at least what I can read out of it  is down below. If I should put any more info please let me know I will reply fast so this topic will finally help people

PC Specs System:

 

Hardware:

• Intel Core™ i9-10900K Prozessor
• Windows 10 Home
• MSI® NVIDIA® GeForce RTX™ 3080 VENTUS 3X 10G OC
• MSI® MPG Z490 GAMING EDGE WIFI Mainboard
• 2 TB PCIe SSD
• 32 GB Kingston® Fury RGB DDR4 Arbeitsspeicher mit 3.200 MHz
• Alphacool Eisbaer 240 Wasserkühlung

Dump file is too big to put here

 

This is what I can show:

 

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

Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 22621 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0xfffff802`1e600000 PsLoadedModuleList = 0xfffff802`1f213460
Debug session time: Thu Jul 20 10:02:21.325 2023 (UTC + 2:00)
System Uptime: 0 days 10:17:47.984
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.............
Loading User Symbols

Loading unloaded module list
................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff802`1ea2ec80 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffa901`06e1aa30=0000000000000101
14: 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: 000000000000000c, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffffa90106c51180, The PRCB address of the hung processor.
Arg4: 000000000000000b, The index of the hung processor.

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1015
    Key  : Analysis.Elapsed.mSec
    Value: 1602
    Key  : Analysis.IO.Other.Mb
    Value: 0
    Key  : Analysis.IO.Read.Mb
    Value: 0
    Key  : Analysis.IO.Write.Mb
    Value: 0
    Key  : Analysis.Init.CPU.mSec
    Value: 186
    Key  : Analysis.Init.Elapsed.mSec
    Value: 13945
    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 93
    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x101
    Key  : Dump.Attributes.AsUlong
    Value: 8
    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1
    Key  : Failure.Bucket
    Value: CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumulateTicks
    Key  : Failure.Hash
    Value: {95498f51-33a9-903b-59e5-d236937d8ecf}
BUGCHECK_CODE:  101
BUGCHECK_P1: c
BUGCHECK_P2: 0
BUGCHECK_P3: ffffa90106c51180
BUGCHECK_P4: b
FILE_IN_CAB:  072023-8609-01.dmp
DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump
FAULTING_PROCESSOR: b
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT:  1
PROCESS_NAME:  System
STACK_TEXT:  
ffffa901`06e1aa28 fffff802`1eac9244     : 00000000`00000101 00000000`0000000c 00000000`00000000 ffffa901`06c51180 : nt!KeBugCheckEx
ffffa901`06e1aa30 fffff802`1e8721ac     : 00000000`00000000 ffffa901`06e00180 00000000`002432fe 00000000`00000202 : nt!KeAccumulateTicks+0x256b44
ffffa901`06e1aa90 fffff802`1e86f853     : 00000000`00000010 00000000`00001388 00000000`00243200 00000000`0015938f : nt!KiUpdateRunTime+0xcc
ffffa901`06e1ac00 fffff802`1e8703c8     : 00000000`00000000 00000000`00000000 ffffa901`06e00180 00000000`00000000 : nt!KiUpdateTime+0x613
ffffa901`06e1aea0 fffff802`1e86fd49     : fffff802`1f25fee8 00000000`00000001 00000000`00000001 00000000`0000000c : nt!KeClockInterruptNotify+0x228
ffffa901`06e1af40 fffff802`1e81d08c     : 00000056`4eae4599 ffff810b`de14e680 ffff810b`de14e730 00000000`00000000 : nt!HalpTimerClockInterrupt+0x109
ffffa901`06e1af70 fffff802`1ea30dda     : ffff9409`91b58a50 ffff810b`de14e680 ffff9409`91b58ca0 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0x9c
ffffa901`06e1afb0 fffff802`1ea31647     : 00000000`151e3e16 ffff810b`de14e680 00000000`00000002 ffffa901`06e03250 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffff9409`91b589d0 fffff802`1e8b1a96     : ffff9409`91b58c00 ffffa901`06e00180 00000000`00000001 ffff9409`91b58c00 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffff9409`91b58b60 fffff802`1e8adc67     : ffffd680`13addf01 80000006`8f4a6921 ffffd680`13addf01 00000000`00000000 : nt!MiFlushTbList+0x616
ffff9409`91b58c40 fffff802`1e89b3a7     : ffff9409`91b58f30 ffff9409`91b58f30 ffff810c`10aebbb8 ffff810c`10aebbb8 : nt!MmSetAddressRangeModifiedEx+0x2c7
ffff9409`91b58da0 fffff802`1e89a431     : 00000000`00000000 ffff9409`00040000 ffff810c`1056ea38 00000000`00000000 : nt!CcFlushCacheOneRange+0xe7
ffff9409`91b58e70 fffff802`1e8fd64b     : 00000000`00000000 ffff9409`91b58fe0 ffff810c`1700dea0 ffff810b`00000000 : nt!CcFlushCachePriv+0xc5
ffff9409`91b58ee0 fffff802`1e8fd44f     : ffff810c`178ccd70 00000000`00000000 ffff810c`1700dea0 00000000`00000000 : nt!CcWriteBehindInternal+0x8b
ffff9409`91b59050 fffff802`1e8fa490     : ffff810c`1700dea0 00000000`00000000 ffff810b`fa8ac790 ffff810b`fa8ac7f8 : nt!CcWriteBehind+0xb7
ffff9409`91b59150 fffff802`1e9526e5     : ffff810b`de0c8c50 ffff810c`163e2540 ffff810b`de0c8c50 fffff802`00000000 : nt!CcWorkerThread+0x3f0
ffff9409`91b592c0 fffff802`1e9569f7     : ffff810c`163e2540 00000000`000008f6 ffff810c`163e2540 fffff802`1e952590 : nt!ExpWorkerThread+0x155
ffff9409`91b594b0 fffff802`1ea33be4     : ffffa901`06e91180 ffff810c`163e2540 fffff802`1e9569a0 ff0e020e`ff0e020e : nt!PspSystemThreadStartup+0x57
ffff9409`91b59500 00000000`00000000     : ffff9409`91b5a000 ffff9409`91b53000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34
SYMBOL_NAME:  nt!KeAccumulateTicks+256b44
MODULE_NAME: nt
IMAGE_NAME:  ntkrnlmp.exe
IMAGE_VERSION:  10.0.22621.1992
STACK_COMMAND:  .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET:  256b44
FAILURE_BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumulateTicks
OSPLATFORM_TYPE:  x64
OSNAME:  Windows 10
FAILURE_ID_HASH:  {95498f51-33a9-903b-59e5-d236937d8ecf}
Followup:     MachineOwner
---------

[Larry Ohboi]

The System was shut down after a critical error : error code:  0x0000009c (0x0000000080000001, 0xffff8f806a99eb20, 0x0000000000000000, 0x0000000000000000).A dumpfile was saved  in: C:\WINDOWS\Minidump\072023-6875-01.dmp. Berichts-ID: 20d61fbc-d733-45cb-856c-4d1a1196a936.

[Larry Ohboi]

More Error Codes i found in case you can help me :

- Der Server "{8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19}"could not be registered with DCOM within the specified time period.

- Image file creation failed due to an error while creating the image copy.

- Kernel-Power 41

[Larry Ohboi]

The computer was restarted after a fatal error. The error code was: 0x00000101 (0x00000000000c, 0x0000000000, 0xffff878036c51180, 0x00000000000b). A full image was stored in: C:\WINDOWS\Minidump\072023-7109-01.dmp. Berichts-ID: 7a266a82-fc31-4a92-9c08-8d1d2016b63d.

[Larry Ohboi]

For ppl with the same or a similiar Problem. For me , updating the Bios worked

Specifically for me I had the Erazer Hunter from Medion. To get this bios update with this PC you need to enter the Medion Forum and ask for the update file. They will respond very fast and send you a step by step guide.