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 (ベトナム語)
Українська (ウクライナ語)
翻訳の問題を報告
I meant though like have you just tried gaming with it capped (or uncapped and gsync/freesync off) for that matter.
Still same problems?
And with every application I could close, closed, I tested Blur Busters again. The test works now; it syncs. Especially with MSI Afterburner disabled. If it's enabled the test doesn't sync at all. That way I opened some games, but no luck it's still there.
I have about... 1 monitor connected = )
I might as well find myself a hardware priest to take a look at my system; exorcise it or something.
Many of those 165Hz screens are pre-OC'ed (from 120 or 144) to achieve that 165Hz anyways. Not all are 100% stable at the 165.
Some you might need to look at the Monitor OSD Menu Settings and see if it had an OC option, if so turn tbat off and it should go back to 120 or 144. Then in OS Settings
If you haven't tried a different output port on the gpu, I'd try that just to see. Also, try disabling the igpu.
Edit: I just realized that cpu doesn't have an igpu
p.s. Sometimes changing Fullscreen-windowed mode to exclusive Fullscreen (or the other way around) improves things as well. In my experience it differed per game.
Edit: Just switch to linux ;)
165Hz Monitors should also have options for 120 and 144; have you tried this?
Also disable ALL forms of VSync & GSync along with any FPS Max Limits; as this will impact benchmarks and lower power output; which for testing purposes, you don't want to do.
Honestly after all you have done, it sounds like either a terrible PSU, or a faulty GPU.
People who say "Oh yea I switched to Linux and my problems are gone" that's just 100% BS and they know it. They were just too lazy to figure out what was even the problems to begin with.
Linux is just too limiting for some users and it's more of a PITA to get some games working on there as opposed to WinOS.
Doing a Clean WinOS Install however by itself is not enough, cause while that might get rid of any interfering junkware you might have had, now you have to build the OS all back up again by turning off all the MS junk, tweak the OS for max gaming performance and install all your drivers and go configure everything.
What all your BIOS is configured to could also be playing a role in all of this. For example when RTX 40 series first came out, many realized that for these to not have problems, they needed to change the BIOS setting regarding the PCIE Speed from Auto and lock that into either 3.0 or 4.0; leaving it on AUTO caused obvious problems with 4.0 GPUs.
I agree, but you will lose use of many mods if you use them. I love using POP OS!
Now that the power supply and card seem to be ruled out try the suggested Rivatuner but if that fails then start looking at what Windows Event Viewer has listed in it. If it has some critical codes or other program failures (not all crash the system) then as you asked before about the motherboard, you may have other underlying issues. If there are events with codes, mostly the same then issues are to were the codes are related, if you get random codes the the issue could be hardware related.
I worked on one PC years back for a friend for about a month trying the find the issue, Event Viewer showed different errors, the PC crashed to desktop, even restarted on many of those errors. Not one of the errors lead me in the right direction until finally after weeks it started throwing a critical core failure error. I've seen many hardware failures in my days working on PC's since 1999 but that was the first time I had seen a single core go out an a multi core CPU. Most of the time the CPU is just dead, and a lot of those are from not doing maintenance like cleaning and re-paste of the CPU every 2-3 years at least.
You can still use MS AB without that.
What is even the point of RTSS in 2024?
RTSS is required for the overlay.
You can modify anything in the virtual windows env, including mods, extra ran exe's, trainers and the like
The monitor stuff, unfortunately, led to another dead end. Long story short: deactivated MSI and the test did sync, opened games with MSI disabled but the stutter's still there.
On a motherboard with a b450 chipset, the x16 PCIe 3.0 GPU lanes are not shared with a storage component. Leave the NVMe in the upper slot (M2_1), which is directly connected to the CPU. If installed in the lower slot (M2_2), you lose bandwidth and the data is managed by the chipset.
Consult the storage section of the motherboard's manual on how the manufacturer decided to implement the chipset's feature on the motherboard.
If you collect data on the behaviour of your PC and share it, I take the time and look at it.
Firstly, I suggest to use Intel Presentmon 2.1.1. as monitoring tool. Stutters are better quantifiable through the animation error metric.
Then repeat the gameplay section with the stuttery behaviour while collecting data with hwinfo64. To have a look on the behaviour of your hardawre. Set the Polling Period to 500 ms in hwinfo64.
Both applications generate .csv files. Share them.
Some games might have slight stutter when either newly run or have not been ran in a long time as it needs some gameplay time to build up GPU Shader Cache. Some games do this at game launch if no cache is on-disk already in the AppData folder for said game. Games like Death Stranding and Detroit Become Himan for example you will have a long loading period at launch while the CPU creates the GPU Shader Cache. Some games do not do it like that and instead do it on the fly during actual gameplay.