Question Graphical artifacts & crash after playing a game ?

Jan 29, 2022
4
0
10
Hello all

I got to admit that I don't know what's going on with my pc, was playing a game and all of a sudden my pc got stuck and after a few seconds it showed some graphical artifacts.

Here is the info from the memory.dmp

I've also attached it here: https://anonfiles.com/h1F67cE7xe/MEMORY_DMP

Hopefully someone can help me out, thanks in advance.



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


Loading Dump File [C:\Users\rTc\Downloads\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff80720a00000 PsLoadedModuleList = 0xfffff8072162a2b0
Debug session time: Sun Jan 30 01:01:42.694 2022 (UTC + 1:00)
System Uptime: 1 days 9:02:17.922
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.......................
Loading User Symbols
PEB is paged out (Peb.Ldr = 0000004b71fa3018). Type ".hh dbgerr001" for details Loading unloaded module list ...................... For analysis of this file, run !analyze -v 10: kd> !analyze -v ******************************************************************************* [LIST] [*]* [*]Bugcheck Analysis * [*]* [/LIST] ******************************************************************************* 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: ffffa40061250180, The PRCB address of the hung processor. Arg4: 0000000000000008, The index of the hung processor. Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 1952 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 5048 Key : Analysis.Init.CPU.mSec Value: 1671 Key : Analysis.Init.Elapsed.mSec Value: 66357 Key : Analysis.Memory.CommitPeak.Mb Value: 134 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 BUGCHECK_CODE: 101 BUGCHECK_P1: c BUGCHECK_P2: 0 BUGCHECK_P3: ffffa40061250180 BUGCHECK_P4: 8 FAULTING_PROCESSOR: 8 PROCESS_NAME: FIFA22.exe BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 TRAP_FRAME: ffff83830b9b6a30 -- (.trap 0xffff83830b9b6a30) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. Unable to get program counter rax=0000000000000000 rbx=0000000000000000 rcx=fffff80720c1e855 rdx=ffff83830acbf570 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80720ca5c0c rsp=ffff83830b9b6c00 rbp=0000000000000004 r8=0000000000000004 r9=ffff83830b9b6c00 r10=0000000000000000 r11=0000000000000001 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=1 vif nv up ei pl nz ac pe nc 6c39:5c0c ?? ??? Resetting default scope IP_IN_FREE_BLOCK: 0 STACK_TEXT: ffffa400613e0c88 fffff80720e1f56e : 0000000000000101 000000000000000c 0000000000000000 ffffa40061250180 : nt!KeBugCheckEx ffffa400613e0c90 fffff80720c1c3cd : 0000000000000000 ffffa400613c7180 0000000000000246 000000000074267b : nt!KeAccumulateTicks+0x2063be ffffa400613e0cf0 fffff80720c1c971 : 0000000000742400 0000000000453b21 ffffa400613c7180 0000000000000001 : nt!KiUpdateRunTime+0x5d ffffa400613e0d40 fffff80720c167e3 : ffffa400613c7180 0000000000000000 fffff80721631980 0000000000000000 : nt!KiUpdateTime+0x4a1 ffffa400613e0e80 fffff80720c1f1a2 : ffff83830b9b6880 ffff83830b9b6900 ffff83830b9b6900 000000000000000c : nt!KeClockInterruptNotify+0x2e3 ffffa400613e0f30 fffff80720cde195 : 00000114ed7b57ba ffffe18f430ea500 ffffe18f430ea5b0 0000000000000000 : nt!HalpTimerClockInterrupt+0xe2 ffffa400613e0f60 fffff80720df8d8a : ffff83830b9b6900 ffffe18f430ea500 0000000000000001 0000000000000000 : nt!KiCallInterruptServiceRoutine+0xa5 ffffa400613e0fb0 fffff80720df92f7 : ffff83830b9b6a70 ffff83830b9b6a70 0000000000000006 fffff80720df937f : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa ffff83830b9b6880 fffff80720c80c67 : 0000000000000010 0000000000040286 ffff83830b9b6a30 0000000000000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37 ffff83830b9b6a10 fffff80720c80bdc : 0000000000000000 ffff83830b9b6c00 0000000000000040 0000000000000001 : nt!KeYieldProcessorEx+0x17 ffff83830b9b6a40 fffff80720c1e855 : ffff83830acbf570 0000000000000004 ffff83830b9b6c00 0000000000000000 : nt!KxSetTimeStampBusy+0x28 ffff83830b9b6a70 fffff80720c1e5cb : 0000000000000004 0000000000000000 ffffffffffffffff 0000000000000002 : nt!KxFlushEntireTb+0x185 ffff83830b9b6ac0 fffff80720cf4efa : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KeFlushTb+0x7b ffff83830b9b6b20 fffff80720cf71b1 : 0000000000000000 0000000000000000 fffffb000a9f0e30 fffffb000a9f0e30 : nt!MiFlushEntireTbDueToAttributeChange+0x3a ffff83830b9b6c10 fffff80720ca5ac5 : fffff80721650bc0 0000000000000001 00000000000000a1 0000393c00000000 : nt!MiChangePageAttributeBatch+0x91 ffff83830b9b6c80 fffff80720ca2848 : ffff83830b9b7050 0000000000000000 0000000000000001 0000000000000000 : nt!MiGetPageChain+0xd75 ffff83830b9b6ec0 fffff80720ca1d98 : ffff83830b9b7050 ffff83830b9b72a0 ffffe18f00000000 0000000000000000 : nt!MiResolvePrivateZeroFault+0x6e8 ffff83830b9b6ff0 fffff80720ca116d : 00000000c0000016 0000000000000002 0000000000000000 0000000000000002 : nt!MiResolveDemandZeroFault+0x208 ffff83830b9b70e0 fffff80720c9f259 : 0000000000000111 0000000000000004 00000000c0000016 0000000000000000 : nt!MiDispatchFault+0x22d ffff83830b9b7220 fffff80720e0545e : ffffe18f4e24f080 0000000000000000 0000000000000000 0000000000000000 : nt!MmAccessFault+0x189 ffff83830b9b73c0 00007ffe0a26f9f9 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x35e 0000004b037f5200 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffe0a26f9f9


SYMBOL_NAME: nt!KeAccumulateTicks+2063be

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 2063be

FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumulateTicks

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {95498f51-33a9-903b-59e5-d236937d8ecf}

Followup: MachineOwner
---------
 
Jan 29, 2022
4
0
10
Thanks for your answer, here is my pc. Please note that I'm not on the latest bios nor gcard driver. I never update bios unless it's critical and about the gcard driver, its the one that performs the best for gaming for my rig.

Cpu: Intel i7 11700k overclocked to 4.9 with the help of youtuber channels FR33THY and Boostedmedia.
Cpu Cooler: Noctua NH-D15
Mobo: Asus Prime Z590-A
Mem: Corsair Vengeance DDR4 3200 mhz
Gcard: Gigabyte RTX 3070
Gcard Driver: 496.13
PSU: Corsair RM750X V2 750W

Harddrives:
2x Samsung SSD 970 EVO 1TB (1000 GB, PCI-E 3.0 x4)
Samsung SSD 840 EVO 250GB (250 GB, SATA-III)
Samsung SSD 840 PRO Series (SATA-III)
Western Digital WD1002FAEX-00Z3A0 (1 TB, 7200 RPM, SATA-III)
 
Last edited:
Thanks for your answer, here is my pc. Please note that I'm not on the latest bios nor gcard driver. I never update bios unless it's critical and about the gcard driver, its the one that performs the best for gaming for my rig.

Cpu: Intel i7 11700k overclocked to 4.9 with the help of youtuber channels FR33THY and Boostedmedia.
Cpu Cooler: Noctua NH-D15
Mobo: Asus Prime Z590-A
Mem: Corsair Vengeance DDR4 3200 mhz
Gcard: Gigabyte RTX 3070
Gcard Driver: 496.13
PSU: Corsair RM750X V2 750W

Harddrives:
2x Samsung SSD 970 EVO 1TB (1000 GB, PCI-E 3.0 x4)
Samsung SSD 840 EVO 250GB (250 GB, SATA-III)
Samsung SSD 840 PRO Series (SATA-III)
Western Digital WD1002FAEX-00Z3A0 (1 TB, 7200 RPM, SATA-III)
Start with bringing everything back to stock speed and see if you still have the problem.
 
  • Like
Reactions: drivinfast247

TRENDING THREADS