Turns out Nvidia drivers were ALSO burning through your SSD and randomly writing gigabytes of data just like AMD lmaoClown industry
why is a driver even writing to diskwhy isn't it writing to cloud instead
>>110368841It should be sending hourly snapshots of your RAM to Sam Altman to make sure you have a worthy usecase
>>110368841logs in this very case
>>110368817Insanity.
I haven't updated my graphics drivers in 6 months, I'm good
linux won
>>110368949why, not what
To see if you're affected, go toC:\ProgramData\NVIDIA Corporation\nvtopps\nctIf your "nvlog.nvlgstg" file is being overwritten every few seconds, you are affectedRolling back to driver 621.01 should fix this issue
>>110368817How do we disable it aside from updating?And how to check if our driver does that? Mine is v475.14 (because Win7), it is not in this list and nothing from nvidia appears in the resources monitor but just in case I'd like to know.
fuck me
>DUDE THIS SHIT IS WRITTING SHIT TONS OF DATA TO MY HD>DUDE IM SOMEHOW PAYING $800 IN SUBSCRIPTIONS A MONTHDo people just not track their stuff?
>nvlgga stole my bytes
>TOTAL VIBEGOD VICTO-ack
managed to do my first driver rollback because of this. thank
>>110368817fires peta jensengets revenge against us
drivers written by claudeâ„¢ASTRA VVONTEAM RED VVON
>>110368817This is a only Windows issue, also the Windows system writes to disk constantly even without a NVidia driverWhat a absolute joke of a OS
Does this affect Linux? If it does we can just symlink nvlog.nvlgstg to /dev/null.
old good new bad haha
should I be worried?
>/v/ thread is full of retards>look up /g/ - technology version of thread>absolute mongoloids looking for the log file itself The log's existence isn't the issue you fucking mongoloids. It's the constant writing to the drive. How is the technology board less capable of understanding the issue than the twitter screencap and political drama masquerading as a videogame board?
>>110370466People are really stupid about this issue. They think the writes are nothing but it's still adding CPU context switching overhead which rapes your fps.
>>110368817The latest AMD GPU driver is also broken Dynasty Warriors 3. And all the Amd drivers from last year instacrash L4D2.
>>110368817>Laughing in Linux Using miceosaar in this day and age
>>110370193No, this is Windows only
>>110370483works fine on my steam deck
>>110370466>It's the constant writing to the drive.It's constantly writing to the log file, though, isn't it?
>>110368817no evidence of this at all btw
>>110370563Deleting or blocking the log file won't fix it. The log isn't the problem. It's the constant writing to it that is. People who aren't affected by the issue still have the log file.
>>110368817kek I was already avoiding the 620 branch because they fucked a lot of shit about color, was just waiting for them to fix it before I move from my studio driver.
>>110370481The overhead of writing a log file is extremely low, even if it's running out of control like this. Obviously it should be stopped because it's stupid, but it's hardly catastrophic.
>>110370571>Deleting or blocking the log file won't fix it.Who said to do that?You can see from the file metadata itself how recently it has been written to.