安裝 Steam
登入
|
語言
簡體中文
日本語（日文）
한국어（韓文）
ไทย（泰文）
Български（保加利亞文）
Čeština（捷克文）
Dansk（丹麥文）
Deutsch（德文）
English（英文）
Español - España（西班牙文 - 西班牙）
Español - Latinoamérica（西班牙文 - 拉丁美洲）
Ελληνικά（希臘文）
Français（法文）
Italiano（義大利文）
Bahasa Indonesia（印尼語）
Magyar（匈牙利文）
Nederlands（荷蘭文）
Norsk（挪威文）
Polski（波蘭文）
Português（葡萄牙文 - 葡萄牙）
Português - Brasil（葡萄牙文 - 巴西）
Română（羅馬尼亞文）
Русский（俄文）
Suomi（芬蘭文）
Svenska（瑞典文）
Türkçe（土耳其文）
tiếng Việt（越南文）
Українська（烏克蘭文）
回報翻譯問題
討論區規矩與守則
檢舉此篇文章
https://www.3dmark.com/compare/spy/36500772/spy/36547882
Oddly there was also some monitoring failure, so the new results don't include some data such as clocks and temperatures. Results say "Hardware monitoring was disabled" but it's enabled in the 3DMark UI, I double-checked, also repeated the bench with same results.
Something really odd going on my system, and since I am a hardware enthusiast it can be many things :) I'm running Windows 11 on the Release Preview; I'm running the latest BIOS from Asus which is a beta. Would be too much effort for me to remove those factors for cleaner testing.
In other news, AMD has apparently reproduced this internally and it is starting to look more and more like a driver issue, so at this time I can only offer "rollback to previous or ignore and wait for future driver fixes".
It seems Time Spy ONLY (no others, Not even time spy extreme) has some weird clocking issues - GPU and VRAM clocks drop to varying lower levels throughout the scenes.
I also tried rolling back drivers (full reinstall, DDU, etc) to 23.2.2 and 23.2.1 with no change.
Checked / Changes Power settings (High Perf in control panel), vs. Balanced and the Power modes in the modern Settings app). No Changes.
Running Windows 11 on the Beta channel. Build 10.0.22624.1391. Those with this issue, you running this build?
affected Time Spy benchmark: https://www.3dmark.com/spy/36377966 https://www.3dmark.com/spy/36376592 Time Spy graphics only ~20000
Windows 11 (10.0.22624.1391): https://www.3dmark.com/spy/36383221
Time Spy graphics ~38000
Windows 11 (10.0.22621), removed KB5022913: https://www.3dmark.com/spy/36380978
Time Spy graphics ~38000
Windows 11 (10.0.22621.1265), before KB5022913 release (Feb 26 2023): https://www.3dmark.com/spy/36163896
Time Spy graphics 37610
I cannot stop Windows Update installing the patch, so I choose Beta channel of Windows Insider to avoid this issue.
The Windows Insider and build numbers have been less straight forward than in the past. Simply, but somewhat inaccurate, the last 4 digits of the build are the 'fixes' and the previous 5 digits are the 'feature'.
I believe the problem happened somewhere before the build version .1391. IIRC .1244 didn't have this issue. I don't believe the the 10.0.22621/22624 build makes a difference, but what comes after it,
Windows 11 version 10.0.22624.1391 is the latest beta with 'Moment 2' features enabled, 10.0.22621.1391 has the same 'fixes' minus 'Moment 2' features.
Dr. Yang, can you edit/update your info with the exact build?
Also, as the Dev said, we should use the Windows Insider Feedback tool to report this.
One final thought - Playing Crysis remastered and Far Cry 6 yesterday I *THINK* i'm seeing and feeling some frame pacing issues, it didn't feel as smooth as it should and has in the past. I could be biased now, knowing there something affecting Time Spy performance at the hardware level...
Tried to add exact build number based on Windows Update history. The only problematic build was 10.0.22621.1344 (FEB 28 2023). I experienced random frame drop when playing PUBG.
The issue was sent to Windows Insider feedback. I think currently there is no need for 3DMark to make any update on this issue.
The only 'Changes' I can think of are - Microsoft Store updates - one of them is the XBOX Game Bar app. The other update i performed was a 'Start 11' update from 1.38 to 1.41.