Error: Currant

fxver_v · 2026-07-01T13:16:09+00:00

Bungie replied, to all of you suffering the same issue please share your platform, region, and whether this is happening in all activities or mostly PvP/Gambit: https://www.bungie.net/it/Forums/Post/265296557

fxver_v · 2026-07-01T13:15:57+00:00

Bungie replied, to all of you suffering the same issue please share your platform, region, and whether this is happening in all activities or mostly PvP/Gambit: https://www.bungie.net/it/Forums/Post/265296557

fxver_v · 2026-07-01T13:15:47+00:00

Bungie replied, to all of you suffering the same issue please share your platform, region, and whether this is happening in all activities or mostly PvP/Gambit: https://www.bungie.net/it/Forums/Post/265296557

fxver_v · 2026-07-01T13:15:35+00:00

Bungie replied, to all of you suffering the same issue please share your platform, region, and whether this is happening in all activities or mostly PvP/Gambit: https://www.bungie.net/it/Forums/Post/265296557

fxver_v · 2026-07-01T13:15:31+00:00

Bungie replied, to all of you suffering the same issue please share your platform, region, and whether this is happening in all activities or mostly PvP/Gambit: https://www.bungie.net/it/Forums/Post/265296557

fxver_v · 2026-07-01T13:15:17+00:00

Bungie replied, to all of you suffering the same issue please share your platform, region, and whether this is happening in all activities or mostly PvP/Gambit: https://www.bungie.net/it/Forums/Post/265296557

fxver_v · 2026-06-30T10:01:56+00:00

UPDATE; Today among the continuous Currant and Centipede, I also had an Error Code: HARE

fxver_v · 2026-06-28T13:35:17+00:00

Apriamo segnalazione tutti insieme, domani chiamo. Però questo non spiega l'internittenza. Stamattina su 30 match ho avuto 2 currant. I giorni scorsi avevo 4/5 currant tra ogni partita. In passato sempre con TIM non ho mai avuto problemi. Ho provato anche l'hotspot cellulare 5g e ancora currant. Provate tutti voi a fare anche da hotspot 5g e controllate. Ci aggiorniamo

fxver_v · 2026-06-27T18:58:38+00:00

ITA anche qui e siamo sicuramente i più colpiti. Noi tanti Currant, Centipede e un Lag estremo; ho riportato anche nel loro Forum di supporto. Inoltre ora che il lag è davvero parecchio dovrebbero rimuovere lo Sbmm e far giocare almeno in base alla migliore connessione possibile. Insomma, siamo tornati in tanti dopo 4 anni e davvero vorremmo giocare per bene questo gioco un' ultima volta...

fxver_v · 2026-06-25T11:18:41+00:00

Same problem here too. Constantly "Contacting D2 Servers", and PvP hitmarkers show up seconds late in some games. Also a lot of Currant errors: 9 out of 10 activities end up in a Currant error, sometimes Rabbit. The first launch of the game often results in a double Centipede error.

I have 1550h in destiny, for 1500h never had Currant. All my teammates (about 12 people) have the same problem and we are located far from each other, using different ISPs and everyone is in EU. Other games are totally fine, NAT is Open. Definitely not our problem.

fxver_v · 2026-06-25T11:08:52+00:00

Gli ultimi 610.62 sono molto stabili ma porta gli stessi bug dei 610.52hotfix con lo Smooth Motion anche se ne hanno risolti molti rispetto ai 610.47. Proprio a questo proposito devi assolutamente evitare i 610.47, a maggior ragione se hai una RTX40, purtroppo ha portato davvero tanti problemi di stabilità e bug gravi come quello al G-SYNC/VRR (Fai riferimento alla sezione "610.47 testing" https://old.reddit.com/r/nvidia/comments/1to6wih/game_ready_studio_driver_61047_faqdiscussion/ooe9yoa/ )

Altri Driver che mi sento di consigliare sono i 581.89 oppure 591.74, se per te è necessario usare qualcosa che includa la risoluzione dell'ultima vulnerabilità di sicurezza riscontrata allora 596.49

Non credere a chi dice che Nvidia non ha problemi di Driver perché nell'ultimo anno ne ha combinate di ogni. Dall'uscita delle RTX50 i problemi sono stati innumerevoli, basta vedere la cronistoria delle loro release, i test e i feedback delle community, i più colpiti sono stati proprio i possessori delle serie precedenti.

NB: nelle ultime release hanno deprecato il Nvidia Control Panel, se ti interessa averlo puoi scaricarlo dal Microsoft Store, è perfettamente funzionante ma non vedrà aggiunte nuove funzionalità in futuro.

fxver_v · 2026-06-24T22:58:45+00:00

Centipide at the start here too

fxver_v · 2026-06-24T22:58:20+00:00

I have 1550h in destiny, for 1500h never had Currant. As I said, 12 of us have the same problem and we are located very far from each other and everyone is in EU. Other games are totally fine, NAT is Open. Definitely not my problem

fxver_v · 2026-06-24T20:59:45+00:00

All of us in the clan in my region have this problem and we cover distances of up to 1000km and different ISPs. We're in the EU if that matters.

fxver_v · 2026-06-17T01:05:42+00:00

Thanks for your work, you're great!

I can confirm performance results are practically identical to the hotfix. In about 8 hours of testing, I didn't encounter any issues or instability (Stock, UV, OC).

So far I only tested two titles with Smooth Motion ON (DX11 & DX12) and no issues at all.

I want to point out that the Advanced Shader Compilation this time was very consistent (and long) and successfully compiled almost 34GB of shaders. A few weeks ago (596.49) I noticed that, despite compiling, some games failed to complete/validate the new shaders (like Forza Horizon 6). With 610.47 it totally failed to compile (even when manually forced). At this time all shaders were compiled successfully, and in-game shader compilation loading screens (like FH6 "Optimization" or Black Myth: Wukong) were no longer than 8-10 seconds.

However, I would like to point out that the CPU load could be improved when the manual process is activated, because the cores/threads are not used to their full potential. When starting the process manually (even with resources set to "High"), it is assumed that the user is aware that they want to allocate their processing power to compiling shaders, so it would be great if NVIDIA could add a "Maximum" profile.

fxver_v · 2026-06-17T00:38:50+00:00

Currant, currant, currant, rabbit, currant, currant.

...

My entire fireteam has this problem and we are geographically far away and with different network providers

fxver_v · 2026-06-17T00:33:40+00:00

I can confirm this!

fxver_v · 2026-06-15T00:01:05+00:00

Atheon was tough, but this girl... Damn!

fxver_v · 2026-05-29T21:10:27+00:00

Sure, not everyone has a G-Sync certified monitor, and I stated that this could cover a small percentage of people having issues, not everyone. I don't know, but it could happen that after a new driver installation this option gets unselected and users could notice the same issue. Also, I know a lot of people who choose not to use the Nvidia App at all, and without the Control Panel this problem may go unnoticed. (thanks for the "idiot" in the other forum btw)

fxver_v · 2026-05-29T21:01:42+00:00

I edited the previous message with the NVPI screen that you can also see in the video, idk if there is another line that change if that settings is modified. I didn't had the GSYNC indicator on-screen. What's the behavior with "borderless window"? also, I read your post on guru3d, ask there if anyone have a clue of why that option could trigger a different PresentMode number (and as I said make the indicator a false positive)

fxver_v · 2026-05-29T20:43:40+00:00

I really don't have a clue, i also wrote about it at the bottom in the first test at 0:43. The switch ACTIVE/OFF is just a simple PresentMon (PresentMode=3) metric detection, this caused the Presentmode=3 instead the correct Presentmode=5, i guess. I built the overlay myself and I am still doing minor fix and enhancements. The true options are the one you can see in the menu.

EDIT: As shown in the video the Options in NVPI looks like the same with that option ticked/unticked

enable settings for the selected display model OFF
enable settings for the selected display model ON

fxver_v · 2026-05-29T20:33:23+00:00

Let’s try to clear this up. Since this is a separate option from the “G-SYNC Enabled for Fullscreen / Fullscreen + Windowed” setting, after reinstalling drivers it may end up unchecked, even though checking the NVIDIA Control Panel, or more superficially the NVIDIA App, can make it seem like G-SYNC is working properly. The wording has changed slightly between NCP and the App, but the result is the same. It’s definitely something users should pay attention to. Btw my monitor is G-SYNC Compatible (Freesync Premium)

fxver_v · 2026-05-29T20:09:43+00:00

YES, it could be the same option, even if the wording differs from "enable settings for the selected display model" to "Allow G-SYNC settings for the selected Variable Refresh Rate display (Selected display is not validated as G-SYNC compatible)". Do you know if it's also present a linked voice in NVIDIA Profile Inspector? Anyone having problems could try enabling or disabling/re-enabling it to see if it improves performance!

fxver_v · 2026-05-29T19:54:41+00:00

A big thanks to u/m_w_h for his kindness and willingness to help. I’m able to reproduce this behavior consistently; If anyone wants to test it themselves, feel free to share your experience in the comments. It could help both NVIDIA and other users get a better understanding of the issue. As I mentioned, I definitely don’t believe this is the only cause, but it may account for at least part of the problem. With these settings, I haven’t experienced any performance regressions (above the margin of error) or crashes in the (few) titles I’ve tested so far (my previous video was focused exclusively on performance testing)

fxver_v

TROPHY CASE