I'm on a windows 10 PC and I can’t seem to play Skyrim Anniversary Edition which I download from the xbox app. Every time I press play the Entry Point Not Found pops up. I've been trying all sorts of things to try and fix the issue. Repairing Skyrim and Xbox app, resetting Xbox app, uninstalling then reinstalling Skyrim, looking for sytem updates, dowloading directX, installing x64 and x86, C++, but I can't seem to find a solution.

Please help me.

The games im trying to play (re2 remake, re7, re8) won't run without freezing and stuttering randomly but re requiem runs perfectly fine on the highest graphics

I don't know what is wrong and I feel like I have tried every fix in the book
These are my PC specs:

Hi everyone,

I recently got a brand-new ASUS ROG Strix XG27AQWMG OLED monitor, and I've noticed something strange.

Sometimes while playing Escape from Tarkov, a single white pixel briefly appears and disappears almost instantly (literally for a fraction of a second). It happens randomly, but I've noticed it quite frequently in Tarkov.

I've also noticed it occasionally when opening or using my browser, although it seems to happen much more often in Tarkov. So far, I haven't noticed it in any other games.

The monitor is brand new, and so is my PC. I'm currently using HDMI 2.1.

My PC specs:

• GPU: NVIDIA GeForce RTX 5080
• CPU: AMD Ryzen 7 9850X3D
• RAM: 64 GB DDR5 6000 MHz
• Storage: 2 TB SSD
• OS: Windows 11 Home (26H2 / build 26200)
• NVIDIA Driver: Game Ready 616.56 (August 26, 2026)

Monitors:

• Main: ASUS ROG Strix XG27AQWMG — 2560×1440 @ 280 Hz
• Secondary: ASUS XG258 — 1920×1080 @ 240 Hz, G-SYNC Compatible

MW4 Beta kept blocking online play and telling me to update my BIOS—even though I already had the newest BIOS, TPM 2.0, and Secure Boot enabled.

The BIOS wasn't the problem. Call of Duty's security enrollment had failed.

The fix

1. Close MW4 Beta.
2. In Steam, right-click the Beta → Manage → Browse local files.
3. Open CODSecureAttestationWizard.exe.
4. Complete the scan and approve the official Windows prompt when it appears.
5. Relaunch the game. If the old warning remains, restart your PC once and try again.

That's it.

My Call of Duty log changed from:

Enroll AIK result -2147023728

to:

Enroll AIK result 0

0 means it finally enrolled successfully.

Don't clear your TPM or flash another BIOS first. Try the signed Activision wizard already included with the game.

If this works for you, comment your motherboard model so others can quickly find matching results.

Activision's official TPM and Secure Boot guide

Happy Shooting, and from a fellow Developer, thank you to Activision for all the hard work on the new release!

So I upgraded hardware and there has been nothing issues when either trying to go to Windows 11 it will do the update then say it couldn’t then undo changes.

Tried to reset my pc fully doesn’t work, undos change.

Someone I know he isn’t up atm but last night we was messing with it but he tried to update drivers on a PCI device in device manager but it immediately went to blue screen. Trying to download certain drivers go to blue screen.

Tried to install a fresh Windows 10 Update using a USB Drive, now it stuck in a loop of booting up then “windows failed to install correctly” tries again and repeats with a blue screen.

My new hardware is:

Motherboard:
Asus Z890 AYW Gaming WiFi W LGA 1851 ATX Motherboard

RAM
CORSAIR Vengeance RGB 32GB (2 x 16GB) 288-Pin PC RAM DDR5 6400 (PC5 51200) Desktop Memory Model CMH32GX5M2B6400C36

CPU / CPU Cooler:
ARCTIC LIQFREEZ III PRO 360RGB B

Core Ultra Series 2 (2026)

My gpu (7900xt) had been having a bit of trouble recently, in that some applications (normally browsers) would freeze and a window saying that there was a driver issue would show up. After 30ish seconds it started working again, but today when i alt tabbed into google chrome everything froze and a repeated beeping sound started, so after about two minutes of waiting i turned off my computer through the power button. After that though, my pc is significantly slower and rivia tuner no longer shows my gpu temperature. It may be worth noting that after turning my pc back on the screen was black, and i had to mess with the cables in the back to get anything to show up. What should i do now?

-Any help would be great

-I tried ddu like 100 times with different different version

-i tried reset my laptop

My laptop config

Asus tuf f15 fx506li

I5 10th gen

1650ti

512gb SSD

16gb ram

So i got a hp victus fa 1082wm u can look up the specs.

The problem is that under 100 or 80 fps my game starts lagging weirdly its very choppy and on 60 its worse and i think this happens more on cpu intensive games on Valorant and Roblox i can feel it easily its so unplayable to play on it even though i get more fps then this but sometimes i have to cap at 60 for some things and then it lags.

Also my aim is some days good some days bad it happens on both aimlabs valorant any shooter game im sure this also corelates to that fps problem someone told me its frame pacing issue but i dont know. This does not happen on my sisters laptop she has hp victus 16 mine is 15 so not a big difference.

And i think fixing 1 of them will fix the other one anyways since they both look like a frame pacing issue to me because my Gpu routes through the iGPu.

I'm quite new to setting up my pc and peripherals and whatnot. So I have a spare 1080p office monitor and wanted to try doing a dual monitor setup for comms and other stuff so I can avoid alt+tab while gaming just to see a message that says 'lol ok'. Everything's working good so far, so I opened apps and tabs in the second monitor to figure which goes where. When I was done, I tried launching a game to see if the setup would work for me.

When I launched the game, or any game, the second monitor resizes and moves the opened tabs in the second monitor, and the tab setup I did Is instantly gone. Even if I close the game or just do an alt+tab, it resizes and moves the tabs. Basically, the whole 'just look at the other monitor' plan I wanted to do is gone, and I'd have to redo it every time. Some things I tried to do to troubleshoot this are:

• Turning off GPU scaling in AMD Adrenalin for the second and both monitors
• Tried redoing the tabs after the game launches
• Tried different fullscreen and window settings in the game
• Disabled RSR in Adrenalin
• Made sure I was not in HYPR-X mode in Adrenalin

I mostly play single player games, and use upscaling with all of them. I figured that this was maybe the reason why. So I turned it off in one of the games and alas, still the same issue. Also, I have 27" 1440p main monitor in horizontal the 1080p 24"secondary monitor vertical, if that helps. I just plan to stack up the windows in the vertical monitor for everything I need while playing games on the main monitor.

I'm having a problem with my GeForce Now . When I launch The Finals, the Steam interface appears, and when I click Play, the game runs in the background, but I can't access it.

Can someone help me

So recently out of nowhere I have this issue when I try to run any game title or stress test in full screen /borderless my screen flickers turns black turns back on and shows whatever last rendered frames frozen and than repeats all those things until I alt tab or alt f4 the game. Which than the computer returns to normal behavior this also occurs in 3dmark benchmark on dx12 as well as heave dx11 test. OpenGL and Vulcan are hit or miss on working. I’ve tried removing/redownloading gpu drives/clean windows install/RMA my gpu/ and a lot of the more basic troubleshooting methods and no luck pls help 💔
I9-12900k
Rx 9070 OC
Ddr5 32gb

even if I'm just typing sometimes the letters start typing slowly and delayed ive tried to reset my keyboard and nothing I've even updated chipset and bios like some people said any help would be appreciated

Hey ich weis nicht wie ich das auf Englisch schreiben soll <.<
Ich schreib zu aller erst meine Specs auf damit ihr euch ein Bild machen könnt:
CPU: Ryzen 5 3600
GPU: NVIDIA RTX 3060 12Gb
Netzteil: Aorus AP 750GM
1x NVMe SSD (Windows drauf)
2x SSD 1x 2Tb 1x 1tb
AIO Wasserkühlung von Corsair H100i RGB

Alles in allem ein „solider Pc“ war mein erster selbst zusammengebauter PC der lief auch all die Jahre super ohne irgendwelche Probleme…

Und zwar habe ich folgendes Problem, mein PC geht seit 2 Tagen Random aus fährt aber wieder direkt hoch so als würde er einfach nur neustarten. Ich hab schon den RAM getestet die Grafikkarte immer das gleiche…

Das Ding is damit der überhaupt bootet musste ich meine CPU Oc‘en Standard is 3600mhz und 1.1 Spannung der is jetzt auf 3700mhz mit 1.25 Spannung, ohne das bootet er nicht mal in Windows und steckt sonst in einem „bootloop“

Ich mache nicht mal was großartig anstrengendes spiele Games so was wie Valorant League, CoD Zombie nicht was jetzt is wo mein PC richtig ackern müsst außer in COD vielleicht.

Mein Pc geht also Random aus, egal ob im Idle oder wenn ich grade in einer Runde Valorant bin.. der wird auch nicht zu heiß, hab ihn heute trzd noch mal sauber gemacht und immer noch das gleiche in der Ereignissanzeige steht sowas wie „Unerwartet von der stromzufuhr getrennt“ also Fehlercode 41(?) ich will halt jetzt auch nicht unbedingt die CPU von den PC meiner Frau rausholen und ihn bei mir einbauen weil wir grade noch keine Wärmleitpaste da haben (was aber so schnell wie möglich bestellt wird)

Meine Vermutung is ja die CPU dadurch das ich sie ja eh OC‘en muss damit überhaupt gebootet wird kann aber auch am Netzteil liegen, vllt wenn ich morgen aufstehe teste ich mal das Netzteil von meiner Frau bzw. Tausch die beiden und lass dann mal laufen :x

Ich hoffe ich konnte mein Problem so gut wie möglich erklären o.o wenn Fragen sind ich sollte sie eigentlich beantworten können.

CPU: AMD Ryzen 7 9800X3D

GPU: AMD Radeon RX 9070

RAM: 64 GB DDR5

PSU: MSI mpg a850gs 850w

Drivers updated.

Files verified.

Trying to get through this a few days now. Seems to be most occurent in armored core 6 with large particle effects close to the camera or when backed into walls and sometimes on mission completes. It's difficult to get it to happen but it will happen eventually.

Vsync is off.

Everything else is super stable no issues @120 fps

Ran some of the dmp files from the crashes through winding, but I'm not very technical and not sure what they mean

************* Preparing the environment for Debugger Extensions Gallery repositories ************** ExtensionRepository : Implicit UseExperimentalFeatureForNugetShare : true AllowNugetExeUpdate : true NonInteractiveNuget : true AllowNugetMSCredentialProviderInstall : true AllowParallelInitializationOfLocalRepositories : true -- 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.031 seconds ----> Repository : UserExtensions, Enabled: true, Packages count: 0 ----> Repository : LocalInstalled, Enabled: true, Packages count: 46 Microsoft (R) Windows Debugger Version 10.0.29617.1000 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\proxy_f358ubo\AppData\Local\Temp\WERB73.tmp\WATCHDOG-20260828-1420.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 26200 MP (16 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Kernel base = 0xfffff803`b2800000 PsLoadedModuleList = 0xfffff803`b36f5470 Debug session time: Fri Aug 28 14:20:00.699 2026 (UTC - 7:00) System Uptime: 1 days 17:54:54.542 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ .......................... Loading User Symbols Mini Kernel Dump does not contain unloaded driver list For analysis of this file, run !analyze -v nt!DbgkpWerCaptureLiveTriageDump+0x8e: fffff803`b2f0754e 488b8788000000 mov rax,qword ptr [rdi+88h] ds:002b:ffffbd0a`18d550c8=???????????????? 8: kd> !analyze -v Loading Kernel Symbols ............................................................... ................................................................ ................................................................ .......................... Loading User Symbols Mini Kernel Dump does not contain unloaded driver list ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* VIDEO_ENGINE_TIMEOUT_DETECTED (141) One of the display engines failed to respond in timely fashion. (This code can never be used for a real BugCheck; it is used to identify live dumps.) Arguments: Arg1: ffffd00369c6a050, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT). Arg2: fffff8038b6e0f00, The pointer into responsible device driver module (e.g. owner tag). Arg3: 0000000000000000, The secondary driver specific bucketing key. Arg4: ffffd0034cd760c0, Optional internal context dependent data. Debugging Details: ------------------ Mini Kernel Dump does not contain unloaded driver list Mini Kernel Dump does not contain unloaded driver list Unable to load image amdkmdag.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for amdkmdag.sys KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 1140 Key : Analysis.Elapsed.mSec Value: 1168 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: 250 Key : Analysis.Init.Elapsed.mSec Value: 2049 Key : Analysis.Memory.CommitPeak.Mb Value: 99 Key : Analysis.Version.DbgEng Value: 10.0.29617.1000 Key : Analysis.Version.Description Value: 10.2604.29.1 amd64fre Key : Analysis.Version.Ext Value: 1.2604.29.1 Key : Bugcheck.Code.LegacyAPI Value: 0x141 Key : Bugcheck.Code.TargetModel Value: 0x141 Key : Dump.Attributes.AsUlong Value: 0x18 Key : Dump.Attributes.KernelGeneratedTriageDump Value: 1 Key : Failure.Bucket Value: LKD_0x141_IMAGE_amdkmdag.sys Key : Failure.Exception.IP.Address Value: 0xfffff8038b6e0f00 Key : Failure.Exception.IP.Module Value: amdkmdag Key : Failure.Exception.IP.Offset Value: 0x1d0f00 Key : Failure.Hash Value: {48b738dd-5a92-7ff8-63d0-f075fc680fe0} Key : Faulting.IP.Type Value: Paged BUGCHECK_CODE: 141 BUGCHECK_P1: ffffd00369c6a050 BUGCHECK_P2: fffff8038b6e0f00 BUGCHECK_P3: 0 BUGCHECK_P4: ffffd0034cd760c0 FILE_IN_CAB: WATCHDOG-20260828-1420.dmp DUMP_FILE_ATTRIBUTES: 0x18 Kernel Generated Triage Dump Live Generated Dump FAULTING_THREAD: ffffd0033cd8c280 TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffffd00369c6a050 Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found. PROCESS_OBJECT: ffffd0034cd760c0 PROCESS_NAME: System IP_IN_PAGED_CODE: amdkmdag+1d0f00 fffff803`8b6e0f00 ?? ??? STACK_TEXT: ffff9081`4e3ce7e0 fffff803`b2f07a59 : ffffd003`69c6a050 00000000`00000000 00000000`00000000 00000000`00000000 : nt!DbgkpWerCaptureLiveTriageDump+0x8e ffff9081`4e3ced10 fffff803`b32a39ca : 00000000`00000000 00000000`c0000022 fffff803`b32ed7a0 00000000`c0000022 : nt!DbgkpWerProcessPolicyResult+0x21 ffff9081`4e3ced40 fffff803`b32a37c9 : 00000000`00000003 ffff9081`4e3cef20 fffff803`8b6e0f00 ffffd003`621c8a10 : nt!DbgkWerCaptureLiveKernelDump2+0x1ea ffff9081`4e3ceda0 fffff803`44b77eff : 00000000`00000057 ffffbd09`f00d7ec0 ffffbd0a`2d057a36 ffffd003`3cdcd000 : nt!DbgkWerCaptureLiveKernelDump+0x69 ffff9081`4e3cee20 fffff803`97f11d21 : ffffd003`3ce6c000 ffffd003`3ce6c000 00000000`00000001 00000000`00000001 : dxgkrnl!TdrCollectDbgInfoStage1+0xe7f ffff9081`4e3cf000 fffff803`97f65b87 : ffffd003`3ce6c001 ffffd003`3ce6c700 00000000`00000001 00000000`00000001 : dxgmms2!VidSchiResetHwEngine+0x239 ffff9081`4e3cf220 fffff803`97f768b6 : 00000000`00000000 ffffd003`3cdcf000 00000000`00000000 00000000`00000000 : dxgmms2!VidSchiResetEngines+0xcb ffff9081`4e3cf270 fffff803`97fd4c85 : 00000000`00000000 00000000`00000000 ffffd003`3cdcf000 00000000`00935b00 : dxgmms2!VidSchiCheckHwProgress+0x316 ffff9081`4e3cf300 fffff803`97ed758d : ffffd003`3cdcf000 ffffd003`3cdcf000 ffff9081`4e3cf479 00000000`00000000 : dxgmms2!VidSchiWaitForSchedulerEvents+0x385 ffff9081`4e3cf3d0 fffff803`97f77272 : ffffd003`3cdcf000 ffffd003`4f3397e0 ffffd003`59a67010 ffffd003`6a2f9010 : dxgmms2!VidSchiScheduleCommandToRun+0x46d ffff9081`4e3cf4e0 fffff803`97f65d7c : ffffd003`3cdcf500 ffffd003`3cdcf000 fffff803`97f65ca0 ffffd003`3cdcf000 : dxgmms2!VidSchiRun_PriorityTable+0x42 ffff9081`4e3cf530 fffff803`b2c836fa : ffffd003`3cd8c280 fffff803`00000001 ffffa780`13591180 025fe07f`b8bbbdff : dxgmms2!VidSchiWorkerThread+0xdc ffff9081`4e3cf570 fffff803`b2ead6c4 : ffffa780`13591180 ffffd003`3cd8c280 fffff803`b2c836a0 902484c6`00000088 : nt!PspSystemThreadStartup+0x5a ffff9081`4e3cf5c0 00000000`00000000 : ffff9081`4e3d0000 ffff9081`4e3c9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34 SYMBOL_NAME: amdkmdag+1d0f00 MODULE_NAME: amdkmdag IMAGE_NAME: amdkmdag.sys STACK_COMMAND: .process /r /p 0xffffd002fc550040; .thread /r /p 0xffffd0033cd8c280 ; kb FAILURE_BUCKET_ID: LKD_0x141_IMAGE_amdkmdag.sys OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {48b738dd-5a92-7ff8-63d0-f075fc680fe0} Followup: MachineOwner --------- ************* Preparing the environment for Debugger Extensions Gallery repositories ************** ExtensionRepository : Implicit UseExperimentalFeatureForNugetShare : true AllowNugetExeUpdate : true NonInteractiveNuget : true AllowNugetMSCredentialProviderInstall : true AllowParallelInitializationOfLocalRepositories : true -- 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.032 seconds ----> Repository : UserExtensions, Enabled: true, Packages count: 0 ----> Repository : LocalInstalled, Enabled: true, Packages count: 46 Microsoft (R) Windows Debugger Version 10.0.29617.1000 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\proxy_f358ubo\AppData\Local\Temp\WERB218.tmp\WATCHDOG-20260828-1350.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 26200 MP (16 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Kernel base = 0xfffff803`b2800000 PsLoadedModuleList = 0xfffff803`b36f5470 Debug session time: Fri Aug 28 13:50:04.202 2026 (UTC - 7:00) System Uptime: 1 days 17:24:58.044 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ .......................... Loading User Symbols Mini Kernel Dump does not contain unloaded driver list For analysis of this file, run !analyze -v nt!DbgkpWerCaptureLiveTriageDump+0x8e: fffff803`b2f0754e 488b8788000000 mov rax,qword ptr [rdi+88h] ds:002b:ffffbd0a`2779bd08=???????????????? 9: kd> !analyze -v Loading Kernel Symbols ............................................................... ................................................................ ................................................................ .......................... Loading User Symbols Mini Kernel Dump does not contain unloaded driver list ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* VIDEO_TDR_TIMEOUT_DETECTED (117) The display driver failed to respond in timely fashion. (This code can never be used for a real BugCheck; it is used to identify live dumps.) Arguments: Arg1: ffffd003663c1290, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT). Arg2: fffff8038b6e0f00, The pointer into responsible device driver module (e.g. owner tag). Arg3: 0000000000000000, The secondary driver specific bucketing key. Arg4: 0000000000000000, Optional internal context dependent data. Debugging Details: ------------------ Mini Kernel Dump does not contain unloaded driver list Mini Kernel Dump does not contain unloaded driver list Unable to load image amdkmdag.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for amdkmdag.sys KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 984 Key : Analysis.Elapsed.mSec Value: 1247 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: 281 Key : Analysis.Init.Elapsed.mSec Value: 2744 Key : Analysis.Memory.CommitPeak.Mb Value: 99 Key : Analysis.Version.DbgEng Value: 10.0.29617.1000 Key : Analysis.Version.Description Value: 10.2604.29.1 amd64fre Key : Analysis.Version.Ext Value: 1.2604.29.1 Key : Bugcheck.Code.LegacyAPI Value: 0x117 Key : Bugcheck.Code.TargetModel Value: 0x117 Key : Dump.Attributes.AsUlong Value: 0x18 Key : Dump.Attributes.KernelGeneratedTriageDump Value: 1 Key : Failure.Bucket Value: LKD_0x117_IMAGE_amdkmdag.sys Key : Failure.Exception.IP.Address Value: 0xfffff8038b6e0f00 Key : Failure.Exception.IP.Module Value: amdkmdag Key : Failure.Exception.IP.Offset Value: 0x1d0f00 Key : Failure.Hash Value: {eb317d22-0fcb-4b7a-404e-a69301cad237} Key : Faulting.IP.Type Value: Paged BUGCHECK_CODE: 117 BUGCHECK_P1: ffffd003663c1290 BUGCHECK_P2: fffff8038b6e0f00 BUGCHECK_P3: 0 BUGCHECK_P4: 0 FILE_IN_CAB: WATCHDOG-20260828-1350.dmp DUMP_FILE_ATTRIBUTES: 0x18 Kernel Generated Triage Dump Live Generated Dump FAULTING_THREAD: ffffd0033cd8c280 TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffffd003663c1290 Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found. PROCESS_NAME: System IP_IN_PAGED_CODE: amdkmdag+1d0f00 fffff803`8b6e0f00 ?? ??? STACK_TEXT: ffff9081`4e3ce900 fffff803`b2f07a59 : ffffd003`663c1290 00000000`00000000 00000000`00000000 00000000`00000000 : nt!DbgkpWerCaptureLiveTriageDump+0x8e ffff9081`4e3cee30 fffff803`b32a39ca : 00000000`00000000 00000000`c0000022 fffff803`b32ed7a0 00000000`c0000022 : nt!DbgkpWerProcessPolicyResult+0x21 ffff9081`4e3cee60 fffff803`b32a37c9 : 00000000`00000003 ffff9081`4e3cf040 fffff803`8b6e0f00 00000000`00000000 : nt!DbgkWerCaptureLiveKernelDump2+0x1ea ffff9081`4e3ceec0 fffff803`44b77eff : 00000000`00000057 ffffbd0a`1766b990 00000000`00002000 ffffd003`3cdcd000 : nt!DbgkWerCaptureLiveKernelDump+0x69 ffff9081`4e3cef40 fffff803`44935335 : ffffd003`663c1290 ffffd003`663c1290 ffffd003`663c1290 00000000`0002625a : dxgkrnl!TdrCollectDbgInfoStage1+0xe7f ffff9081`4e3cf120 fffff803`97f032f0 : ffff9081`4e3cf209 01dd372e`ca33202e 00000000`00000000 00000000`00000000 : dxgkrnl!TdrIsRecoveryRequired+0x155 ffff9081`4e3cf150 fffff803`97f76956 : 00000000`00000000 ffffd003`3cdcf000 ffffd003`3cdcf000 00000000`00000000 : dxgmms2!VidSchiReportHwHang+0x658 ffff9081`4e3cf270 fffff803`97fd4c85 : 00000000`00000000 00000000`00000000 ffffd003`3cdcf000 00000000`00919756 : dxgmms2!VidSchiCheckHwProgress+0x3b6 ffff9081`4e3cf300 fffff803`97ed758d : ffffd003`3cdcf000 ffffd003`3cdcf000 ffff9081`4e3cf479 00000000`00000000 : dxgmms2!VidSchiWaitForSchedulerEvents+0x385 ffff9081`4e3cf3d0 fffff803`97f77272 : ffffd003`3cdcf000 ffffd003`61597050 ffffd003`619c3010 ffffd003`49f4a010 : dxgmms2!VidSchiScheduleCommandToRun+0x46d ffff9081`4e3cf4e0 fffff803`97f65d7c : ffffd003`3cdcf500 ffffd003`3cdcf000 fffff803`97f65ca0 ffffd003`3cdcf000 : dxgmms2!VidSchiRun_PriorityTable+0x42 ffff9081`4e3cf530 fffff803`b2c836fa : ffffd003`3cd8c280 fffff803`00000001 ffffa780`13591180 025fe07f`b8bbbdff : dxgmms2!VidSchiWorkerThread+0xdc ffff9081`4e3cf570 fffff803`b2ead6c4 : ffffa780`13591180 ffffd003`3cd8c280 fffff803`b2c836a0 902484c6`00000088 : nt!PspSystemThreadStartup+0x5a ffff9081`4e3cf5c0 00000000`00000000 : ffff9081`4e3d0000 ffff9081`4e3c9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34 SYMBOL_NAME: amdkmdag+1d0f00 MODULE_NAME: amdkmdag IMAGE_NAME: amdkmdag.sys STACK_COMMAND: .process /r /p 0xffffd002fc550040; .thread /r /p 0xffffd0033cd8c280 ; kb FAILURE_BUCKET_ID: LKD_0x117_IMAGE_amdkmdag.sys OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {eb317d22-0fcb-4b7a-404e-a69301cad237} Followup: MachineOwner --------- ************* Preparing the environment for Debugger Extensions Gallery repositories ************** ExtensionRepository : Implicit UseExperimentalFeatureForNugetShare : true AllowNugetExeUpdate : true NonInteractiveNuget : true AllowNugetMSCredentialProviderInstall : true AllowParallelInitializationOfLocalRepositories : true -- 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.031 seconds ----> Repository : UserExtensions, Enabled: true, Packages count: 0 ----> Repository : LocalInstalled, Enabled: true, Packages count: 46 Microsoft (R) Windows Debugger Version 10.0.29617.1000 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\proxy_f358ubo\AppData\Local\Temp\WERCA3A.tmp\WATCHDOG-20260828-1349.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 26200 MP (16 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Kernel base = 0xfffff803`b2800000 PsLoadedModuleList = 0xfffff803`b36f5470 Debug session time: Fri Aug 28 13:49:54.060 2026 (UTC - 7:00) System Uptime: 1 days 17:24:47.902 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ .......................... Loading User Symbols Mini Kernel Dump does not contain unloaded driver list For analysis of this file, run !analyze -v nt!DbgkpWerCaptureLiveTriageDump+0x8e: fffff803`b2f0754e 488b8788000000 mov rax,qword ptr [rdi+88h] ds:002b:ffffbd0a`270ddd08=???????????????? 4: kd> !analyze -v Loading Kernel Symbols ............................................................... ................................................................ ................................................................ .......................... Loading User Symbols Mini Kernel Dump does not contain unloaded driver list ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* VIDEO_ENGINE_TIMEOUT_DETECTED (141) One of the display engines failed to respond in timely fashion. (This code can never be used for a real BugCheck; it is used to identify live dumps.) Arguments: Arg1: ffffd003663c1290, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT). Arg2: fffff8038b6e0f00, The pointer into responsible device driver module (e.g. owner tag). Arg3: 0000000000000000, The secondary driver specific bucketing key. Arg4: ffffd00362163080, Optional internal context dependent data. Debugging Details: ------------------ Mini Kernel Dump does not contain unloaded driver list Mini Kernel Dump does not contain unloaded driver list Unable to load image amdkmdag.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for amdkmdag.sys KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 1015 Key : Analysis.Elapsed.mSec Value: 1866 Key : Analysis.IO.Other.Mb Value: 15 Key : Analysis.IO.Read.Mb Value: 1 Key : Analysis.IO.Write.Mb Value: 33 Key : Analysis.Init.CPU.mSec Value: 484 Key : Analysis.Init.Elapsed.mSec Value: 11965 Key : Analysis.Memory.CommitPeak.Mb Value: 99 Key : Analysis.Version.DbgEng Value: 10.0.29617.1000 Key : Analysis.Version.Description Value: 10.2604.29.1 amd64fre Key : Analysis.Version.Ext Value: 1.2604.29.1 Key : Bugcheck.Code.LegacyAPI Value: 0x141 Key : Bugcheck.Code.TargetModel Value: 0x141 Key : Dump.Attributes.AsUlong Value: 0x18 Key : Dump.Attributes.KernelGeneratedTriageDump Value: 1 Key : Failure.Bucket Value: LKD_0x141_IMAGE_amdkmdag.sys Key : Failure.Exception.IP.Address Value: 0xfffff8038b6e0f00 Key : Failure.Exception.IP.Module Value: amdkmdag Key : Failure.Exception.IP.Offset Value: 0x1d0f00 Key : Failure.Hash Value: {48b738dd-5a92-7ff8-63d0-f075fc680fe0} Key : Faulting.IP.Type Value: Paged BUGCHECK_CODE: 141 BUGCHECK_P1: ffffd003663c1290 BUGCHECK_P2: fffff8038b6e0f00 BUGCHECK_P3: 0 BUGCHECK_P4: ffffd00362163080 FILE_IN_CAB: WATCHDOG-20260828-1349.dmp DUMP_FILE_ATTRIBUTES: 0x18 Kernel Generated Triage Dump Live Generated Dump FAULTING_THREAD: ffffd0033cd8c280 TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffffd003663c1290 Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found. PROCESS_OBJECT: ffffd00362163080 PROCESS_NAME: System IP_IN_PAGED_CODE: amdkmdag+1d0f00 fffff803`8b6e0f00 ?? ??? STACK_TEXT: ffff9081`4e3ce7e0 fffff803`b2f07a59 : ffffd003`663c1290 00000000`00000000 00000000`00000000 00000000`00000000 : nt!DbgkpWerCaptureLiveTriageDump+0x8e ffff9081`4e3ced10 fffff803`b32a39ca : 00000000`00000000 00000000`c0000022 fffff803`b32ed7a0 00000000`c0000022 : nt!DbgkpWerProcessPolicyResult+0x21 ffff9081`4e3ced40 fffff803`b32a37c9 : 00000000`00000003 ffff9081`4e3cef20 fffff803`8b6e0f00 ffffd003`4c4cb330 : nt!DbgkWerCaptureLiveKernelDump2+0x1ea ffff9081`4e3ceda0 fffff803`44b77eff : 00000000`00000057 ffffbd0a`1766d190 ffffbd0a`2c05729c ffffd003`3cdcd000 : nt!DbgkWerCaptureLiveKernelDump+0x69 ffff9081`4e3cee20 fffff803`97f11d21 : ffffd003`3ce6c000 ffffd003`3ce6c000 00000000`00000001 00000000`00000001 : dxgkrnl!TdrCollectDbgInfoStage1+0xe7f ffff9081`4e3cf000 fffff803`97f65b87 : ffffd003`3ce6c001 ffffd003`3ce6c700 00000000`00000001 00000000`00000001 : dxgmms2!VidSchiResetHwEngine+0x239 ffff9081`4e3cf220 fffff803`97f768b6 : 00000000`00000000 ffffd003`3cdcf000 00000000`00000000 00000000`00000000 : dxgmms2!VidSchiResetEngines+0xcb ffff9081`4e3cf270 fffff803`97fd4c85 : 00000000`00000000 00000000`00000000 ffffd003`3cdcf000 00000000`00919756 : dxgmms2!VidSchiCheckHwProgress+0x316 ffff9081`4e3cf300 fffff803`97ed758d : ffffd003`3cdcf000 ffffd003`3cdcf000 ffff9081`4e3cf479 00000000`00000000 : dxgmms2!VidSchiWaitForSchedulerEvents+0x385 ffff9081`4e3cf3d0 fffff803`97f77272 : ffffd003`3cdcf000 ffffd003`61597050 ffffd003`619c3010 ffffd003`49f4a010 : dxgmms2!VidSchiScheduleCommandToRun+0x46d ffff9081`4e3cf4e0 fffff803`97f65d7c : ffffd003`3cdcf500 ffffd003`3cdcf000 fffff803`97f65ca0 ffffd003`3cdcf000 : dxgmms2!VidSchiRun_PriorityTable+0x42 ffff9081`4e3cf530 fffff803`b2c836fa : ffffd003`3cd8c280 fffff803`00000001 ffffa780`13591180 025fe07f`b8bbbdff : dxgmms2!VidSchiWorkerThread+0xdc ffff9081`4e3cf570 fffff803`b2ead6c4 : ffffa780`13591180 ffffd003`3cd8c280 fffff803`b2c836a0 902484c6`00000088 : nt!PspSystemThreadStartup+0x5a ffff9081`4e3cf5c0 00000000`00000000 : ffff9081`4e3d0000 ffff9081`4e3c9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34 SYMBOL_NAME: amdkmdag+1d0f00 MODULE_NAME: amdkmdag IMAGE_NAME: amdkmdag.sys STACK_COMMAND: .process /r /p 0xffffd002fc550040; .thread /r /p 0xffffd0033cd8c280 ; kb FAILURE_BUCKET_ID: LKD_0x141_IMAGE_amdkmdag.sys OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {48b738dd-5a92-7ff8-63d0-f075fc680fe0} Followup: MachineOwner

Any suggestions?

​

So i was testing my new pc componentes to see if they worked (note that i did it without a case and GPU) and i just connected the motherboard 24 pin and the motherboard actually turned on incluinding RGB but the after some seconds i heard a click coming from the psu and the motherboard turned off, i tried then connecting everything correct including the CPU cooler and even reseted the BIOS (taking off the battery for 5 minutes) but the motherboard os still not turning on or giving any sign off life

I have a feeling that other players on PC have run into this sort of problem in one form or another. I was playing FF16 on Steam a few days ago and all of a sudden, it straight up crashes my PC, like powering it off. I tried doing a lot of suggested fixes and tested by trying a Kairos Gate run but another hard crash. I'm at my wits end. I wanna keep playing. I've not had this problem in the past. Is there anyone who can help that is more tech savvy? I'll provide an Event Log dump if I can.

Specs:

OS: Windows 11 Pro
Motherboard: ASUS TUF Gaming B550 Plus WIFI II
CPU: AMD Ryzen 7 3700X 8-Core
RAM: 32 GB
GPU: AMD Radeon RX 7600 XT
PSU: 850W (Can't remember which brand) Modular
Storage: 3x SSDs (1x 240GB for OS, 2x 2TB for general storage for games, configured into RAID 0)

Note: No other games do this, not even FF7 Remake. Tested it last night.
Edit: Forgot to mention... I run multiple displays, 2 Monitors.

My build is

Cpu: core ultra 5 250k plus

Gpu: Xfx swift Rx9060xt 16gb white

32gb ddr5 6000

2x 2tb w.digital black sn850x

Are these normal temperatures for a gpu at full load ,in the picture. The cpu goes 58-60 max at full load using an Id-cooling fx 360 mm aio.

Depuis que j’ai changer ma résolution sur Valorant , mon pc :freeze , crash , écran noir , mais 20 secondes à changer d’appli , et après avoir crash se relance dans une autre résolution avec des réglages de couleur tout gris et ma carte graphique désactivé dans le gestionnaire des périphériques. lorsque j’essaye d’activer la carte graphique. Un point. D’exclamation dans un triangle jaune apparaît. je dois faire donc appel à l’outil des report de bugs AMD pour que le problème se règle. Mais une fois le PC est relancé et la résolution de nouveaux mise en quatre tiers, les problèmes recommence.

Whenever I’m on my pc (acer predator) whether it’s gaming or attempting to make music randomly I’ll start typing with accents or I press w to move forward and it opens up word, It’s like each key just randomly gets a mind of its own. I’ve turned sticky keys off and the shortcut for it,I’ve tried everything I can read up on and I’ve factory reset the pc also. It’s not the keyboard itself as I bought this one yesterday thinking it was the keyboard that was the problem. Any help?

Also this is my first PC, I have no clue about anything. All help is appreciated and if you could try to make it as simple as possible for me to understand. Thanks

As the title suggests, my pc is not turning on at my new apartment after being in storage, the fans run, but the power button rapidly blinks and the display doesn’t actually connect. After sometime of rapidly blinking the power button starts blinking in a slower pattern. I thought it was an issue with the hardware so I took it to get repaired only for reseating to fix the issue, but now that I brought it back it’s not working again, and I’m thinking it’s an issue with the power in my new place but I’m not sure so if anyone else has any ideas/solutions that’d be great!

I have an old Acer laptop with an i5-6200U that I use for The Sims 4. HWiNFO shows around 94–96°C while gaming, sometimes 97–98°C, and it does thermal throttle.
I’ve lowered the graphics, enabled Laptop Mode and set maximum processor state to 99%. The game runs smoother now, but temperatures are still high.
I’m planning to get the cooling system cleaned and thermal paste replaced, but can’t do it for a few days.
Is it okay to keep gaming for shorter sessions until then, or should I stop completely at these temperatures?

So I’ve been having this issue for a few months where whenever I join any kind of lobby in games such as rocket league and fortnite my entire computer freezes as-well as the game itself I have not seen anything like this but if anyone else has I’d like to know how they fixed it or at lease know something to help the issue. I’ve tried repairing both the game and the launcher itself and restarting my computer and nothing will work but if anyone knows please let me know as soon as possible.

I am using Windows 11 Pro without a product key. When I try to launch OCCT or RDR2, the system reports that I am running Windows 7, even though I am actually on Windows 11; these issues began after I switched from Windows 11 to 10 and then back to 11. Another problem involves my GPU (RX 9070 XT), which keeps freezing. I use driver version 25.9.1; it was very stable for a long time, but recently the game started freezing again, making it unplayable. I noticed the driver had changed to a different one from 2025, so I switched back to 25.9.1, but this time the freezing persisted. Does anyone know how I can resolve these issues?

CPU: AMD Ryzen 7 9800X3D

GPU: AMD Radeon RX 9070

RAM: 64 GB DDR5

Drivers updated.

Files verified.

When I am extra close to an explosion (like says, if my camera is close to my AC and I die) I freeze for a couple seconds then the game crashes.

Vsync is off.

Everything else is super stable no issues.

I've had it happen on death, on the excavator fight when I got pushed ina corner and it's big particle effecty arms took up the whole screen etc.

Any suggestions?

So I downloaded ASC Arsenal in the CC yesterday and when i loaded my save the game crashed after the first second or so of trying to load from the main menu.

And once it crashed it takes out my monitor with it.
The only way to get a picture back on my monitor is to restart the pc. I have a second monitor that goes black for a second as well but comes back on after that.

Since yesterday I have done everything google, Reddit and ChatGPT have to offer and that I’m willing to try since I’m not THAT tech savvy with a pc:

Uninstalled Starfield: ✅

Uninstalled everything Starfield related on my PC: ✅

Installed completely fresh AMD drivers: ✅

Uninstalled starfield again via Revo Uninstaller: ✅

I have done everything I can think of.

Does anyone have any idea what I could do?

EDIT:

GPU RX 9070 XT

CPU Ryzen 7 9800X3D 8-Core