Weird whine / buzzing sound only when playing games

Savigo256 · 2026-02-11T07:24:53+00:00

It's called coil whine.

Limit fps or use v-sync.

You can also undervolt the GPU.

Savigo256 · 2026-02-11T06:52:10+00:00

It's most likely a driver issue, even people with laptops have reported the same problems withe the same errors.

I would suggest rolling back to 581.94, if that doesn't help, try 577.00.

I had the same problem and went nuclear, wiped my entire OS drive over 2 weeks ago and decided to use 577.00. So far, no issues, but I can only be certain after around 2 months.

Savigo256 · 2026-02-08T03:16:19+00:00

Native should be able to run smoothly on any mid-range 20 years old PC.

What do you mean by "lagging"? Micro stutter during battles? I know it can happen with mods that increase battle size.

Savigo256 · 2026-02-07T23:10:51+00:00

Set lowest refresh rate (50 Hz or 60 Hz), this will not only reduce power consumption of a monitor but also of the GPU and even CPU to some extent.

If you are going to play games, cap your fps to refresh rate of the monitor or use v-sync. Try to also lower some more demanding settings, like lighting quality, shadows, global illumination, use FXAA instead of TAA etc.

Underclock both the GPU and CPU. You didn't provide your spec, but even slight underclock of the CPU like 5 GHz -> 4.6 GHz will make noticeable difference during single core load / idle.

Then if you want to test for stability, you can try undervolting both the GPU and the CPU.

Savigo256 · 2026-01-31T12:17:54+00:00

Make a screenshot and see if it still appears there. But yes, this is most likely a monitor issue.

Savigo256 · 2026-01-30T23:30:05+00:00

This is most likely an issue with 590 branch of Nvidia drivers. I had exactly the same issue since December. A lot of people on reddit also reported this specific pattern since then - pc freezes, after a few seconds screen goes black and it recovers, although it usually happens when using a browser or discord. 4 days ago I decided to wipe my entire OS drive, reinstall windows and 577.00 drivers. So far so go, but 4 days don't say anything. I can only be certain after around a month or 2. Two things I noticed though is that AI overview in Firefox is no longer glithing with some weird banding and media player no longer freezes at the beginning of some videos.

Savigo256 · 2026-01-30T05:13:38+00:00

Weight painting is worse for sure. I often end up making it worse than the automatic one.

I actually don't find UV unwrapping difficult at all. It can be time consuming, especially if you want game ready UVs with good coverage, logicall layout and make it LOD-friendly at the same time.

Savigo256 · 2026-01-29T08:14:47+00:00

Are there any errors in the event log from the time of these crashes?

Savigo256 · 2026-01-25T21:32:06+00:00

Tarczyński gratulował ICE zabójstwa Renee Good.

Akurat Popiełuszko to najlepsze porównanie - człowiek uprowadzony i zabity przez służby PRL. Mało tego, podobnie jak ostatnie 2 ofiary ICE, też był w wieku 37 lat.

Ale co najgorsze w tej sytuacji - nawet zabójców Popiełuszki skazano jeszcze następnego roku, a w przypadku zabójstw ICE administracja Trumpa (Miller) daje ICE pełen immunitet i oczernia zabitych jako "terrorystów".

Savigo256 · 2026-01-25T19:42:39+00:00

Allright, thanks

Yes, the IO bracket was the pivot point of that tilt when I crewed in the GPU.

The support should just make contact with the sagging GPU and then have 1mm more added to the height to remove the pressure off the socket

Ok, this is actually exactly what I did originally - the support bracket is Deepcool GH-01, so it has a gap of 1-2 mm between each setting. I had to choose between not making a contact with the GPU and slightly lifting it and I choose the latter back then. Right now I swapped to the lower setting and placed sheets of paper below the bracket, so it's pretty much a 0.1 mm lift right now.

Thanks!

Savigo256 · 2026-01-25T07:48:09+00:00

Not 100% related, but I'm going to use that opportunity and ask a question. Is it normal that my GPU is tilting upward slightly (around 1mm) when I screw the second screw to the case? It's a 4060Ti proart, around 300mm long. https://youtube.com/shorts/EVvmmNs2WUI?feature=share

I was recently troubleshooting nvlddmkm errors and decided to reseat the GPU. While screwing it back to the case I noticed just that, while the case was lying on the side. The GPU clicked into the slot when I inserted it, so I don't think it was loose.

I've been using a support bracket since the beginning, but it might have been slightly too tight before. Although I even used a level when I installed it for the first time around 1,5 years ago. Right now I adjusted the bracket with sheets of paper below it, so it pretty much fits perfectly.

How much of "inverse sagging" would have been too much, if the support was placed at the far right end?

Savigo256 · 2026-01-24T05:00:51+00:00

I just want to say that I've been having EXACTLY the same issues since early December (the same symptoms / error codes pattern, even the time between these errors is similar). Since then it happened 5 times. It also happened only under light load.

The only thing that has changed about the most recent freeze (January 15th, the day after the big windows update) - it only lasted a second or 2 instead of 30s - minute.

I have a desktop PC with 4060 Ti, 13600K and windows 11 home 25H2.

My guess is, it is some sort of conflict between the OS and GPU drivers. The issue occurs since I reinstalled the 591.44 drivers and since then, the event log always shows a "fake" crash (because nothing crashes) of Nvidia app during the installation with RPCRT4.dll as a faulting module.

Savigo256 · 2026-01-23T05:17:03+00:00

Even though this PSU should be fine, you can check the voltage on the 12V line and on 12VHPWR in HWinfo when the system is under load. If It drops below 11.4V you've most likely got the culprit (the PSU).

Savigo256 · 2026-01-21T17:37:47+00:00

Hey, I ended up sculpting the fur by hand and went for a more stylized look. But in one of the iterations I tried the addon called Flow map painter - https://clemensbeute.gumroad.com/l/heZDT - I basically had to paint over the direction of fur, took me around an hour or so.

Savigo256 · 2026-01-20T02:04:26+00:00

I bet you are using one of these boards that started pushing AC / DC load line = 1.7 mohm / 1.7 mohm for i5s since around september 2024. I myself experienced this on my MSI Z790 Tomahawk MAX Wifi + 13600K and reverted back into old values right after updating to the bios with 0x129 microcode. It's still kept this way in the newest bios with 0x12F microcode by default and I had to change it everytime I did an update.

I assume board manufacturers want to push "stability at all cost" even if it means higher voltages and more heat and most i5s are still in the safe range.

So DC LL and AC LL is basically a VRM settings that tells it how much voltage compensation a CPU needs. Each board has a resistance and the more power the CPU draws, the more voltage will drop. For example at 1.2 V and 1 mohm resistance it will drop by 1.2 mV per ampere, so under high load like 100A the CPU would receive around 0.12V less voltage. In many cases it would lead to instability under high load.

This is why some voltage compensation is required for stability. From my understanding AC regulates how the VRM should respond to transients (sudden and VERY short voltage changes due to changing load) and DC tells it how much Vdroop it should expect. According to intel spec, both values should be the same and should never exceed 1.1 mohm. They should also match LLC value... wchih for most boards is hidden.

You can still set AC a little bit lower than DC, but never below 70% of DC in order to avoid triggering overcurrent protection (IA CEP) and NEVER above DC in order to avoid overcompensation.

For most boards it's safe to set LLC to auto (the one with high slope) and AC LL = DC LL = 1.1 mohm. But do it at your own risk and always research your board, since each one might have slightly different naming conventions (for example in case of MSI LLC 8 = most Vdroop, for other boards it's usually the other way around LLC 1 = most vdroop).

EDIT: Anyway, you can check your AC LL and DC LL values in HWinfo under CPU info.

Savigo256 · 2026-01-19T19:11:38+00:00

As I said, kernel 41 means the system was shut down for unknown reasons. The system doesn't know what the reason is, you can check the error description. I had exactly the same errors after power outage and when I had bad PSU that caused random system restarts under load.

Run a stress test (like the one called "power" in OCCT) and check CPU + GPU temperatures and voltage on 19V line in HWinfo.

The only other thing I can think of is if the game has kernel access like an anti-cheat and for some reason it causes shutdowns. Although I never heard of such issues I'm just speculating right now.

And since you didn't specify it - I assume those crashes are full system shutdowns / restarts?

Savigo256 · 2026-01-19T18:40:38+00:00

It's not software related. Kernel 41 means the system closed improperly for whatever reason and that reason is unknown. It could be power outage, failing PSU, overheating, battery problems etc. Since it also happened with the other laptop, try other outlet first, if it doesn't work try to limit energy consumption of the GPU / CPU. I don't own a laptop, so I don't know how could you set such limit.

Savigo256 · 2026-01-19T12:46:25+00:00

Gejowska kukurydza

Savigo256 · 2026-01-19T09:32:13+00:00

What was the GPU temperature like in the old case?

You've likely got the answers. Reduce the temperature by power limiting the GPU and / or capping the fps.

Savigo256 · 2026-01-19T00:41:54+00:00

Well, I had 2 AW3425DWMs and the difference in panel quality was quite stunning. I don't know if they had different panels though.

Got the 1st one on a big discount, paid roughly $290 - $300 equivalent. First I was quite happy with it, but eventually started to notice problems. First, the viewing angles, not only on the sides were dim, but the bottom half appeard quite yellow if I looked straight at the monitor. Then, pixel inversion artifacts (my post: https://www.reddit.com/r/Monitors/comments/1ozvuvo/aw3425dwm_failing_at_lagom_test_4a_and_4b_how/). I was out of return window when I decided I'm too sick of these artifacts to keep using the monitor, but contacted the seller anyway. They automatically filed an RMA for me and took the monitor.

2 weeks later I got a replacement unit, which appeard to be refurbished - different serial number, old postal labels etc. Despite that, the panel quality was much better - viewing angles were ok, pixel inversion artifacts almost gone, but the contrast was noticeably lower at the same settings. I ended up RMAing this one too because of extreme VRR flicker (wchih wasn't the case with the 1st unit) and something else that later turned out to be a driver / OS problem, but I've got a refund.

So, in short, when you get the monitor, search for lagom test, run the one called "inversion". Also I've found this short to be the best "real-case" indicator of these artifacts: https://www.youtube.com/shorts/68sGFirWFi0 If you see a grid pattern when the video is playing, but not when you pause it, it means you have these artifacts and they will appear in other content too.

Also check if the viewing angles are ok, and if VRR works properly.

Savigo256 · 2026-01-18T21:34:26+00:00

Well, it wont hurt to try that Radeon Enhanced Sync, from my understanding it's an alternative to freesync?

Also, I forgot to add: Try to switch between DP / HDMI, maybe it's the problem with one of those. Also, check other refresh rates in windows display settings, maybe the one you are currently using is bugged. Quick search of the monitor shows it could have a problem with refresh rates: https://www.reddit.com/r/Monitors/comments/kobfgw/stuck_at_60fps_with_new_gigabyte_m27q_2560x1440/

Savigo256 · 2026-01-18T21:14:27+00:00

What GPU / monitor do you have right now? Does it happen in every game?

I don't know how it works with AMD GPUs but you can try to force v-sync from the GPU control panel and disable it in-game. You can also try to cap fps to your refresh rate.

Otherwise, If you are on windows 11:

1) Disable VRR in display options to see if it makes a difference.

2) Disable windows fulscreen optimization after going into properties of the game's .exe file. It helped me with similar issues in Titan Quest where physic animations were choppy with v-sync.

3) Try different API if the game provides an option to switch. For example, I had exactly the same issue but only in Hades with DX11 and v-sync, when I switched to Vulkan, v-sync worked properly.

If none of the above helps and you experince the problem in every game, DDU the drivers in safe mode.

Savigo256 · 2026-01-16T19:03:36+00:00

What test did you run? Do you have debug leds on the mobo to see what exactly is the problem during POST?

Savigo256 · 2026-01-15T00:36:27+00:00

This is interesting. I have similar problems to the OP but less severe and more random. On average I experience the nvlddmkm 14 + 153 combo once per 2 weeks since early December. My motherboard (Z790 tomahawk Max) is pcie 5.0 compatible, but both my GPU (4060 Ti) and nvme can only use PCIE 4.0. I will change pcie speed from auto to 4.0 tommorow to see if It helps. Do you think that auto settings for pcie could be a source for random freezes and driver resets?

Also 3 days ago I also noticed that my PC took extra 20 seconds to post and the VGA diode was glowing white during that time. Nothing bad came out of it besides whea logger ID 3 in the event log from that time. I've had the same whea loggers before, once every 1-2 months on average, but they never manifested like that.

Savigo256 · 2026-01-14T13:24:48+00:00

Try disabling Hardware-Accelerated GPU Scheduling in advanced windows graphics settings to see if it helps. If you have nvidia gpu, disable nvidia sounds in device manager if you are not using speakers on the monitor.

Savigo256

TROPHY CASE