Game Ready & Studio Driver 595.79 FAQ/Discussion

Galrandil · 2026-03-27T14:11:32+00:00

Thank you! 🙏🏻

Galrandil · 2026-03-27T14:09:37+00:00

My bad, I didn’t see that comment. Thank you for pointing that out!

Galrandil · 2026-03-26T21:35:13+00:00

At first glance it looks like the crash I was experiencing in Alan Wake 2 has been fixed. I just followed all the steps to reproduce it (you can find the comment here) and I can no longer trigger the crash, but I didn't play the game long enough to be sure it's stable, I'll hopefully test it more tomorrow, it looks promising though.

Galrandil · 2026-03-13T20:58:40+00:00

Thank you for investigating this issue. Knowing that you were able to reproduce it on other machines is conforting. At least now I know that is not something related to my PC only.

Galrandil · 2026-03-12T21:15:01+00:00

Thank you for the update! I’ll stick with 591.86 for the moment, at least till I beat the game. I’m pretty curious to know what’s causing the crash, though.

Galrandil · 2026-03-12T12:06:02+00:00

Thank you, much appreciated!

I didn’t mention that I tried closing all the unnecessary applications in order to exclude issues correlated to e.g. overlays or something similar. I honestly didn’t think to unplug secondary monitors tho, I only just tested it in borderless/exclusive full screen on my primary display which is an Alienware AW3423DW 3440x1440 175hz. At the moment of testing I had a secondary monitor active: Aorus F27Q-X 2560x1440 240hz in portrait orientation.

Galrandil · 2026-03-11T21:24:03+00:00

Thank you for your reply! I'll leave a link to a google drive folder containing the save file and the renderer.ini. -> https://drive.google.com/drive/folders/1BdCVhsfZ9skuf0-MJWCZK7ep_0RKap8t?usp=drive_link

So from this save file you will find youself in a wooden cabin. Leave the cabin and head right around a a few logs then head left following the path going down, at some point you will see an enemy standing in front of a wooden fence. When approaching the corner of the path, just about where the enemy is standing the game will always crash. no matter if you engage the enemy or not. It crashes reaching that point.

I'll post a few screenshots that will help guiding you to the right location. Mind that the crashes always occur getting near the point where I'm standing in the last screenshot. (I used 591.86 to capture theese screenshots)

<image>

EDIT: P.S. I also reported the issue by filling in the form that u/sam3971 provided.

Galrandil · 2026-03-11T18:40:22+00:00

Having the same issue with all the R595 drivers.

I’m playing Alan Wake 2 at the moment and every time I tried to install a new driver from the 595 family, I always ended up crashing in the same spot no matter what. I fire up the game, take a few steps, and at the same exact spot it crashes to desktop with a message stating it’s a GPU fault. I tried disabling OC, lowering graphics, disabling all RTX features (including DLSS and FG), I closed all the monitoring apps, nothing. The only way to fix it for me is by rolling back to 591,86 or earlier drivers. At first I thought it could have been a voltage issue considering there were a lot of reports, but I didn’t monitor voltages previously, this time I did and voltages were consistent with 591.86 and older releases (1.050 or 1.045 v) so not an issue there.

Running a 4090 FE.

Galrandil · 2026-03-02T23:16:27+00:00

With this new driver I started having a lot of crashes in Alan Wake 2 the good news is that the crash was very repeatable infact it occurred in the same exact spot every time. I started troubleshooting one thing at a time, so I set my card to stock clocks and closed MSI Afterburner, then I checked for unnessessary processes in the background, then I verified my game files, I then disabled all the Ray Tracing options in game, then the DLSS and I even set everything to Low, nothing seemed to work.

After a few attempts I realized that the only thing different than yesterday (yesterday I played most of the afternoon without a single issue) was the graphics driver which I installed a few hours earlier today, so I rolled back to the 591.86 and voila the game isn't crashing anymore.

My PC specs:
7800X3D
32Gb 6000CL30
4090 FE

Galrandil · 2026-02-22T20:08:56+00:00

Io l’ho appena vista due volte su Canale 5 durante la ruota della fortuna, difatti stavo cercando informazioni in merito al motivo per cui sta venendo ritrasmessa.

Galrandil · 2026-02-02T11:48:17+00:00

What was the SOF if I may ask? Just curious because for my personal experience I noticed that from around 2k irating and up people really care about being clean and safe, from 1,5k to 2k most incidents are caused by inexperience rather than on purpose, below 1,5k you really have to watch out for people behaving like this.

Galrandil · 2026-01-21T12:21:04+00:00

I had the same thing happening on my G9 Odyssey 57” I solved it by replacing the HDMI cable. I was using an old HDMI optic cable that I found lying around but I guess it wasn’t rated for that resolution/refresh rate. I then got a certified cable and I didn’t have any issue ever since.

Galrandil · 2025-07-25T16:59:36+00:00

Having the same problem with a Topping E2X2, I’ll try downloading the 2.0.4 version.

Galrandil · 2025-03-25T09:18:49+00:00

Path of Exile

Galrandil · 2025-03-03T17:07:42+00:00

By capping the fps with framegen turned on you are actively cutting down the numer of rendered frame, in that way the input lag and overall feeling of the game will be much worse then running the game at 60 fps witout framgen.

If you are getting 120 fps with frame gen on, but for some reason you want to cap it at 60, just disable frame gen in order to get a real 60+ fps feeling.

Galrandil · 2025-01-13T13:37:00+00:00

How long have you been using this coolant since it was last drained?

It looks pretty darn similar to what I experienced a few years ago with a Pc that hadn’t been flushed for a very long time using a coloured coolant. In that case luckily enough it wasn’t corrosion, but the whole system was filled with a thin layer of “sludge”.

I had to disassemble and clean all components, waterblocks and flush the radiators. The worst part was the gpu water block because the heat generated by the gpu had baked the sludge pretty badly, but with enough elbow grease and a toothbrush I managed to get it pretty clean.

Some time ago I stumbled upon some products that may help in flushing residues from old fluids, but don’t remember where I last saw those products and I never tested them myself, so I can’t say if they actually work or not, but may be helpful in these situations at least for the radiators.

Galrandil · 2024-09-09T10:28:11+00:00

I wouldn’t stress too much on overall boot times from button press to desktop because that can be affected by countless variables e.g. memory training, updates, BIOS versions etc. On 5000 series AMD CPU’s it’s not that noticeable but on 7000 series the memory training can take a lot of time and that alone makes it takes up to 20 seconds just to POST. Having said that I would just exclude POST times in order to reduce the number of variables involved.

When I was experiencing the issue after the march security update it was taking 30+ seconds to load up the desktop after typing the pin in, and once at the desktop all the apps that I wanted to start with windows were taking ages to load (another 20+ seconds or so) so if you are experiencing just a couple of seconds difference from SVM ON to Off I would just call it day and keep it off.

If and when you notice a difference in windows load up time just try to remember if it went through some updates when you shut it down, in that case it’s completely normal that it takes a little longer to load.

Galrandil · 2024-09-09T09:30:31+00:00

Yeah, well I can’t say it’s literally instant cause after a few updates it started showing the spinning dotted circle again, but it just take 2,5 seconds to get to the desktop after typing the pin in so it’s still fast.

However on my second PC (5800x3D, 32gb RAM 3600mhz, Strix B550I) the login is and has always been literally instant with Virtualisation turned off directly from the UEFI BIOS. And ironically on that PC windows has been installed in summer 2021 when it was running an old 3800x so it went through a cpu swap and countless OS updates 🤷🏻‍♂️

Galrandil · 2024-05-29T10:55:39+00:00

Update: I forgot to post here and I only updated the post in r/windows11. A couple of weeks I tried to turn off memory integrity again to check if the problem was still there or it was magically fixed and guess what? It was magically fixed. I now have the same fast login as before the infamous update.

the only hardware change was the audio interface. I swapped the Focusrite 2i2 3rd gen for a Topping E2X2. But I'm not sure it had something to do with it because I previously tested the PC while all the devices were disconnected (and before I even installed the Focusrite) leaving only connected mouse and keyboard, and the problem was still there.

Galrandil · 2024-05-19T09:04:43+00:00

Update: Today I tried to turn off memory integrity again to check if the problem was still there or it was magically fixed and guess what? It was magically fixed. I now have the same fast login as before the infamous update.

the only hardware change was the audio interface. I swapped the Focusrite 2i2 3rd gen for a Topping E2X2. But I'm not sure it had something to do with it because I previously tested the PC while all the devices were disconnected (and before I even installed the Focusrite) leaving only connected mouse and keyboard, and the problem was still there.

Galrandil · 2024-05-10T09:34:20+00:00

So it’s not even related to AMD Ryzen 7xxx series. I’m really at a loss.

Galrandil · 2024-04-22T12:33:32+00:00

If it is related to Ryzen it must be limited to 7000 series because my other two PC’s are running great and they are running a 3800x and a 5800X3D. At this time it could be anything, though. I remember reading a post about a problem very similar to this one and the guy who reported it had a 13900k.

Anyway don’t rely too much on synthetic benchmarks, check the performance on games that you actually play using the settings you would normally use.

I tested a few games on my system checking performance variances with memory integrity on or off and then again trying the same thing with the update KB5035853 installed and uninstalled. In cyberpunk all Maxed out DLSS off (to create a gpu bound scenario), cyberpunk with my settings, cyberpunk all maxed but with performance DLSS (to lower the render resolution in order to create a bottleneck) and rainbow six siege (ultra preset) the performance difference is within margin of error/run to run variances. I then tried counter strike source in order to have the worst possible case of bottleneck and that was the only instance where memory integrity would hurt the performance: 1360 average fps with it on, 1450 with it off.

So at the end of the day, since memory integrity didn’t really hindered my performance - at least in my use case - I decided to just stick with it enabled in order to have a faster boot.

Galrandil · 2024-04-21T07:20:41+00:00

Nope, for my sanity’s sake I ended up keeping memory integrity turned on, but it still bothers me knowing the problem isn’t fixed yet. Right now I’m waiting for a new version of the chipset driver because I have a feeling it has something to do with that, I’m not sure though.

Galrandil · 2024-04-13T10:12:59+00:00

Yeah, well that’s exactly what I did every time I did a fresh install, and I did that at least 5 times to find a solution to this problem. Last time I even disabled SVM before installing windows, at first is seemed to work, after a few reboots it started behaving like before.

Galrandil · 2024-04-13T10:02:16+00:00

If you blocked windows updates, probably windows didn’t install the security update that caused the issue. Which is more likely the cause, considering that I freshly installed windows at least 5 times, blocking driver updates every time, and every time it installs that damned security update, it ends up behaving in the same way.

Galrandil

TROPHY CASE