For RX 7900 Series - AMD FreeSync issues is confirmed. If you have BOD issues. Disable FreeSync

@illusiveman Because why, red&greed team, do they have to spend time and resources to correct something that someone else did wrong ie did not meet the standard

 

Well yeah...monitor manufacturers messed up (probably because of greed to save a couple of cents/panel or idk why) but they didn't provide any patches via firmware or any RMA because they didn't care. Probably a few like me, you and others managed to fix it with CRU but I think the majority of users didn't know how to fix it....It was up to AMD and NV to support these monitors with non-standard timings as user bug reports kept increasing, they had no choice. And AMD certainly took their time, I used CRU for around 2 years lol.

Totally agree.

 

Hello, very thanks, CRU works for 144 Hz.
For 165 Hz there are red color in refresh rate and ok button is disabled. Do you know why? Thanks

 

From CRU

First delete 165Hz from CTA-861 in Extension blocks:

then add DisplayID 1.3 in Extension blocks:

and in driver:

 

Thanks, 144 Hz and 165 Hz now works. I have new monitor and graphics card...

 

Freesync is pretty buggy right now on 23.2.2 even for rx6000 series probably older cards to no bsod tho but those may have been around for long time but just blackscreens instead while alt tabbing altho thats probably another issue, i hope they fix drivers soon for rdna3 as well i kind of wanna buy new laptop with rdna3 maybe, since my issues gone away on Linux.

Do rdna3 owners when freesync work sometimes get refresh rate missmatching actual in game fps cos that bug been around for years but for some reason is far more common now.

Its like having 200 fps but the game feels like 60 fps cos the screen is at 60hz or 65hz cos freesync froze or bugged out.

 

Never had any problems with Freesync, then again its the "Freesync Premium" apparently and i turned it on from monitor settings and thats about it.

 

My system crashed and the AMD driver version is 23.2.2 and the problem still persists. I have attached crash the crash dump footprint.
/cheer Carlo

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


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Full address space is available

Primary dump contents written successfully

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 22621 MP (24 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 22621.1.amd64fre.ni_release.220506-1250
Machine Name:
Kernel base = 0xfffff802`50c00000 PsLoadedModuleList = 0xfffff802`51813450
Debug session time: Tue Feb 28 17:07:30.419 2023 (UTC + 1:00)
System Uptime: 0 days 0:13:10.094
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..............................
Loading User Symbols

Loading unloaded module list
............

+------------------------------------------------------------------------+
| This target supports Hardware-enforced Stack Protection. A HW based |
| "Shadow Stack" may be available to assist in debugging and analysis. |
| See aka.ms/userhsp for more info. |
| |
| dps @ssp |
| |
+------------------------------------------------------------------------+

For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff802`51028c50 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffde81`9cbbce50=0000000000000133
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
DISPATCH_LEVEL or above.
Arg2: 0000000000001e00, The watchdog period (in ticks).
Arg3: fffff8025191c340, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding the cumulative timeout
Arg4: 0000000000000000

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

*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: TickPeriods ***
*** ***
*************************************************************************

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1593

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 1618

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

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

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

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

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

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

Key : Bugcheck.Code.DumpHeader
Value: 0x133

Key : Bugcheck.Code.KiBugCheckData
Value: 0x133

Key : Bugcheck.Code.Register
Value: 0x133

Key : Dump.Attributes.AsUlong
Value: 1800

Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1

Key : Dump.Attributes.ErrorCode
Value: 0

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

Key : Dump.Attributes.ProgressPercentage
Value: 100

Key : WER.OS.Branch
Value: ni_release

Key : WER.OS.Timestamp
Value: 2022-05-06T12:50:00Z

Key : WER.OS.Version
Value: 10.0.22621.1


FILE_IN_CAB: MEMORY.DMP

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


DUMP_FILE_ATTRIBUTES: 0x1800

BUGCHECK_CODE: 133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff8025191c340

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

TRAP_FRAME: ffffde819cbbd4a0 -- (.trap 0xffffde819cbbd4a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000036e66ac33d7 rbx=0000000000000000 rcx=fffff7dc00001000
rdx=0000036e00000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80250e244af rsp=ffffde819cbbd630 rbp=0000000000000001
r8=0000000000001d01 r9=fffff802a5dee3d0 r10=0000fffff80250f9
r11=ffffce7d9b000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
nt!HalpTimerStallExecutionProcessor+0xff:
fffff802`50e244af e8cc000000 call nt!HalpTimerGetInternalData (fffff802`50e24580)
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: System

STACK_TEXT:
ffffde81`9cbbce48 fffff802`50e27a3f : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff802`5191c340 : nt!KeBugCheckEx
ffffde81`9cbbce50 fffff802`50e26874 : 0000036e`66ac6101 00000000`00000000 00000000`0000c585 00000000`00000000 : nt!KeAccumulateTicks+0x23f
ffffde81`9cbbceb0 fffff802`50e26756 : 00000000`00000018 00000000`00000000 ffffde81`9cbc0180 00000001`d6ed7400 : nt!KiUpdateRunTime+0xf4
ffffde81`9cbbd070 fffff802`50e2497e : 00000000`00000000 ffffde81`9cbc0180 ffffffff`ffffffff 00000000`00000007 : nt!KiUpdateTime+0x13e6
ffffde81`9cbbd330 fffff802`50e2418a : fffff802`5185fc98 ffffbc0c`1ef9b530 ffffbc0c`1ef9b530 00000000`00000000 : nt!KeClockInterruptNotify+0x3de
ffffde81`9cbbd3e0 fffff802`50f44c1e : 00000001`d6f1e758 ffffbc0c`1ef9b480 ffffde81`9cbc0180 00000000`00001255 : nt!HalpTimerClockInterrupt+0x10a
ffffde81`9cbbd410 fffff802`5102adaa : ffffde81`9cbbd520 ffffbc0c`1ef9b480 0000036e`66ac33d7 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0x19e
ffffde81`9cbbd450 fffff802`5102b617 : 00000000`001f0003 fffff802`a1ec3ac5 ffffbc0c`00000000 00001f80`0000071e : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffde81`9cbbd4a0 fffff802`50e244af : fffff802`00000000 00000000`00000000 00000000`00000000 fffff802`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffde81`9cbbd630 fffff802`50e22511 : 00000003`00000001 ffffbc0c`2ea64bd0 00000000`000005c9 fffff802`00003697 : nt!HalpTimerStallExecutionProcessor+0xff
ffffde81`9cbbd6d0 fffff802`a2175fd1 : ffffbc0c`2ea64bd0 00000000`000005c9 ffffbc0c`2d72ec20 00000002`00003696 : nt!KeStallExecutionProcessor+0x41
ffffde81`9cbbd710 fffff802`a1f2611f : ffffbc0c`00000001 00000000`00003697 00000000`00000000 00000029`00000000 : amdkmdag+0x1f75fd1
ffffde81`9cbbd750 fffff802`a202be15 : ffffbc0c`2d72ec20 00000000`00000000 fffff802`a5f18310 00000000`00000002 : amdkmdag+0x1d2611f
ffffde81`9cbbd780 fffff802`a20c0dda : 00000000`000005c9 ffffde81`9cbbd8f8 00000000`000005c9 00000001`d697b62a : amdkmdag+0x1e2be15
ffffde81`9cbbd860 fffff802`a1f0e64e : ffffde81`9cbbda18 ffffde81`9cbbdca0 ffffde81`9cbbdce9 00000001`d697b62a : amdkmdag+0x1ec0dda
ffffde81`9cbbd8b0 fffff802`a21e1063 : ffffde81`9cbbdce9 ffffbc0c`49a1d1e8 ffffbc0c`29bc04e0 ffffde81`9cbbda18 : amdkmdag+0x1d0e64e
ffffde81`9cbbd8f0 fffff802`a042b844 : ffffbc0c`2e972010 ffffde81`9cbbdca0 00000000`00000000 00001f80`00011100 : amdkmdag+0x1fe1063
ffffde81`9cbbdc20 fffff802`a042c16c : ffffbc0c`2e877730 00000000`00005027 00000000`00000000 00000000`00005027 : amdkmdag+0x22b844
ffffde81`9cbbdc50 fffff802`a043122e : ffffbc0c`2d219020 ffffbc0c`00000000 ffffbc0c`29bc04e0 fffff802`00000000 : amdkmdag+0x22c16c
ffffde81`9cbbdd50 fffff802`a043b354 : ffffbc0c`29bbc000 ffffde81`9cbbde69 00000000`00000000 00000000`00000000 : amdkmdag+0x23122e
ffffde81`9cbbdda0 fffff802`a0428db2 : ffffbc0c`29bbc000 00000000`00000000 00000000`00000002 00000000`00000000 : amdkmdag+0x23b354
ffffde81`9cbbddd0 fffff802`a02579c4 : ffffbc0c`29c8a000 fffff802`50eb97a1 ffffbc0c`2e975000 ffffde81`9cbbde69 : amdkmdag+0x228db2
ffffde81`9cbbde00 fffff802`86023bbc : 00000000`00000000 00000000`00000000 ffffde81`9cbc0180 ffffbc0c`29cd7030 : amdkmdag+0x579c4
ffffde81`9cbbded0 fffff802`50f5cda1 : ffffde81`9ca68500 fffff802`00000002 00000000`01000f32 00000000`00400a02 : dxgkrnl!DpiFdoMessageInterruptRoutine+0x5c
ffffde81`9cbbdf20 fffff802`50f44beb : 00000000`00031e0b fffff802`50edaa4c ffffbc0c`48155020 ffffde81`9ca68500 : nt!KiInterruptMessageDispatch+0x11
ffffde81`9cbbdf50 fffff802`5102ab2f : ffffab0d`6e847240 ffffde81`9ca68500 00000000`00031e0b 70100080`04002001 : nt!KiCallInterruptServiceRoutine+0x16b
ffffde81`9cbbdf90 fffff802`5102adf7 : 00000000`00000000 00000000`00000000 00000000`00000000 00001f80`00000200 : nt!KiInterruptSubDispatch+0x11f
ffffab0d`6e8471c0 fffff802`50ff7ac6 : ffffde81`9cbc0180 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatch+0x37
ffffab0d`6e847350 fffff802`51030db4 : ffffab0d`6e847430 00000000`00000000 ffffbc0c`48155020 00000000`00000000 : nt!KiSwInterruptDispatch+0x1b6
ffffab0d`6e847430 fffff802`5102da0a : 00000000`00000000 ffffbc0c`1ef60040 ffffbc0c`498a3300 ffffbc0c`4acc3500 : nt!KiSwInterrupt+0x3d4
ffffab0d`6e8475c0 00000000`00000000 : ffffab0d`6e848000 ffffab0d`6e841000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


SYMBOL_NAME: amdkmdag+1f75fd1

MODULE_NAME: amdkmdag

IMAGE_NAME: amdkmdag.sys

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 1f75fd1

FAILURE_BUCKET_ID: 0x133_ISR_amdkmdag!unknown_function

OS_VERSION: 10.0.22621.1

BUILDLAB_STR: ni_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {ce335412-b260-6bc1-3af9-ea5584f041c4}

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

 

There's something to this Freesync business, I mean, I find my system when gaming to be more stable without Freesync enabled. With it enabled, I'd get random freezes and/or crash when I play Dead Space Remake (with Driver Timeout error message). But with it disabled on my monitor (hence Adrenalin control panel shows it to be "Not supported'), I can play four solid hours of DSR without issue. Really weird, I do hope the driver team is working on a more stable driver for games in general, as nI'd like to play games with Freesync enabled.

 

Freesync is really broken on rx6000 series as well im having high fps all the time but my display decides to lock into 63 hz until i alt tab and alt tab back out, its getting really annoying its as if AMD is secretly using me as guinee pig cos from day to day it works then it breaks the next day its very inconsistent.

If i have 140 fps i should not have display locked into 63hz but at 120 hz with enchanced sync engaged instead its making my game feel laggy, im trying to figure out whats causing all these issues but its not as easy some issues are not avoidable except for turning off freesync which what i payed for why would i turn that off.

edit: i think just locking game within refresh rate fixes possibly disabling enchanced sync freesync only seems to break if running outside monitor refresh range

60 fps 60 hz freesync supose to feel smoother then how buggy 140 fps 66hz feels something really broken about freeync right now hope they fix it soon and make it useable for rdna3

 

I built a new PC a little over a month ago and been pulling my hair out trying to figure out why games keep having major hitching after initial loading into areas or into the game. In Hogwarts especially my screen would go completely black like 15% of time when fast traveling or even just booting up the game and seemingly nothing I could do other than hard reset my PC and try again. After a month of troubleshooting and trying everything, I can possibly think of and having no clue if it's a hardware issue or not since everything passes stress tests. I finally discovered on my own that turning freesync off solved it. Then once I figured that out I was able to find more sources like this one of similar issues. I'm fairly frustrated if this is a known issue by AMD why they aren't making this problem more visible, would have saved me hundreds of hours of troubleshooting. Now i am just hoping for a driver update so I can use freesync later. Here is what I got:

7900 xtx
7700x cpu
32gb ram
win 11
Alienware AW3423DW Ultra wide monitor at 175hz 3440 x 1440p

I also tried lowering the refresh rate as low as 120fps with no help, only turning off freesync has solved all my crashes and hitching in games.

 

Disabling Freesync is more likely the workaround, and not the cause. The cause is probably an iffy ESD settings for your monitor, and use CRU to make it more compliant.

 

I'm assuming these settings are monitor specific? I'm currently dealing with similar issues in my multi-monitor setup, is there a way to find these settings?

 

You can use CRU to look at your settings, and edit them. There are profiles for industry standard settings.

 

https://www.amd.com/en/support/kb/release-notes/rn-rad-win-23-3-1 -> this may be the driver update we are looking for

 

Iam having this exact issue with the latest Amd drivers. Can some one help me out. I am using a Alienware 280hz screen.

EDIT: my monitor is a Dell Alienware AW2723DF

 

Anyone got a solution for LG OLED C2?

 

Solution to what exactly?

 

Is the issue specific to certain models of monitors/TVs? I'm using a Samsung 3840x1080 144Hz monitor with Freesync Pro, framerate target control set to 144Hz with no issue since....well, since I'd gotten this monitor. Never experienced any BSOD issue since installing my RX 7900 XTX early February when I got back home from Toronto.