FINAL FANTASY XV WINDOWS EDITION

FINAL FANTASY XV WINDOWS EDITION

View Stats:
Maverik770 Mar 14, 2018 @ 10:32am
Display Driver Crash (Grey Screen Lockup) Megathread. **SOLVED**
Hey everyone.

So performance with FFXV has actually been quite good considering my less than stellar CPU/Rig but I am totally plagued by the "Grey Screen" lockup/crash issue that many others are also being affected by.

I have tried EVERYTHING to resolve the issue and cannot. This is the only game I own on Steam (out of thousands) that crashes like this.

The only scrap of information I can find about the actual crashes/lock ups is that most of the time when it occurs I find the following in my Windows Event Viewer under Custom Views - Administrative Events:

Warning: Display driver amdkmdap stopped responding and has successfully recovered.

Something within this game is failing hard and causing the actual Display Driver to crash out and have to recover which then in turn causes the game's display to lockup with the "Grey Screen". So it seems to me that the Grey Screen issue is mostly related to the game crashing out Display Drivers.

I have seen many people reporting this on both AMD and Nvidia GPUs so it does not seem to be related to one specific GPU type. Further this issue is exacerbated heavily in the multiplayer Comrades mode. It happens so frequently in that mode it's almost unplayable. Single player crashes still occur but are much less frequent than the multiplayer mode.

Things I have done to try and fix this:

- Updated drivers to latest AMD 18.3.2 using full clean wipe and install with DDU.

- Borderless Fullscreen mode: This did help a lot with stability during both single player and multiplayer but results in the occassional odd graphical anomalies that do not occur during normal Fullscreen mode. Plus Comrades multiplayer still crashes way too frequently.

- Special K's performance mod: I did not expect that to reslolve the crashing but figured it was worth a shot.

- Validating Game Files Through Steam: Zero change or impact on the crashing.

- TRAM: I have set TRAM to multiple different levels and the game still intermittently crashes.

- Playing with KB+M only as I have read that using a controller can cause the game to switch between input devices which can cause hitches and other issues.

- Disabled FreeSync on both my GPU and Monitor: No change to the crashing at all as far as I could tell.

- Windows Page Filing: So far I have had zero luck setting larger manual page filing sizes but I am going to do some more testing with this later today and will update accordingly. But I do not think it is going to resolve the crashes.

My Specs
CPU: AMD FX-6350
GPU: Radeon RX 580 8 GBs (MSI Gaming X) - Running newest 18.3.2 Adrenalin Drivers
RAM: 16 GBs Corsair Vengeance DDR3 1600Mhz
OS: Windows 10 Pro
OS Drive: 120 GBs ADATA SSD
Game Drive: 1 TB WD Black Sata 3 HDD
PSU: XFX 650w Modular

I know my rig is not top of the line by any stretch and that I have aging parts in here. However, I would really like to emphasize that the game runs very well aside form these crashes. I can run the game in High preset with the HD Assets and get a very consistent smooth 45-60 FPS at all time. Again, I do not experience these crashes in ANY other games here on Steam. And I own and play a lot of games on Steam.

I know my CPU is an ancient POS but it works fine for this and numerous other games on Steam and seeing as performance is not my issue and I have error messages directly pointing at Display Drivers I do not think the problem is CPU related.

So the point of this thread is for people experiencing these crashes and "grey screen" lock up issues to share and post information about their rigs and situations so maybe we can start making some head way on these crashes and get some resolution to those of us experiencing this.

If you are experiencing these crashes and grey screen lock ups please post your system specs and any additional information about how the crashes/lock ups occur. ie: single player mode, Comrades mode, certain areas of the game world, during certain scenes, etc. Pleas epost any fixes you have attempted and what the results were.

Also please check your Windows Event Viewer logs in the Custom Views -> Administrative Events category to see if you are also getting these odd "Display Driver" crash errors right at the time your game hitches and locks up/crashes and post them along with your data. If you find any other errors or messages that could be useful (especially in the Event Viewer) please post those as well.

I'm confident that as a community we can work together and find a resolution to this issue for everyone affected. Thanks to everyone for your help and information going forward! :gs_joy::8bitheart::pixelprompto:

**1st Update**

See post number 15 below for my long winded and way too detailed solution on how I fixed my Display Driver (Grey Screen) lockup and crash issues. I really hope it can help others experiencing these crashes.

**2nd Update**

Some users are reporting that their Display Driver issues only recently started occurring after the recent official game update from Square that addressed the issue of Summons tanking out framerates. It would seem if you're in the boat of users who only started having crashes post summons patch then my solution for tweakingGPU power draw or clock cycles may not help you at all. Although it certainly still wouldn't hurt to try it either as you're probably looking for any possible solutions to resolve the crashes.

People who were experiencing display driver crashes and grey screen lock ups both before and after the summons patch should definitely try my posted solution.

**SOLUTION**

Apparently Steam won't let me mark my own reply lower down in this thread as the answer to this thread or I would flag it accordingly so it would be bumped up here to the top below my original post. Which is completely absurd that I can't mark my own posted solution as the actual solution to the whole thread. But I digress...

I resolved my problem by dialing back the default clock speed of my GPU from 1380 MHz to 1300 MHz. Please read post #15 below for the full details on how I tweaked, tested and resolved this issue on my computer. I hope it can help other people who are experiencing these Display Driver - Grey Screen crashes and lock ups.
Last edited by Maverik770; Mar 23, 2018 @ 3:17pm
< >
Showing 1-15 of 18 comments
The problem with these isolated cases of bugs and errors persists due to the fact that people aren't reporting this on the official Nvidia and AMD forums. They all come here or they simply go on random other forums to get things sorted.

What you guys need to do is band together and create a megathread where you all complain about this issue. If it is indeed the driver's fault Nvidia or AMD WILL sort it out.

Steam forums though? I don't even think that the actual game developers even read anything here. Let alone Nvidia or AMD.
Last edited by Magillanica Lou Mayvin; Mar 14, 2018 @ 10:41am
Maverik770 Mar 14, 2018 @ 10:50am 
Originally posted by Grandmaster Foo:
The problem with these isolated cases of bugs and errors persists due to the fact that people aren't reporting this on the official Nvidia and AMD forums. They all come here or they simply go on random other forums to get things sorted.

What you guys need to do is band together and create a megathread where you all complain about this issue. If it is indeed the driver's fault Nvidia or AMD WILL sort it out.

Steam forums though? I don't even think that the actual game developers even read anything here. Let alone Nvidia or AMD.
That is the entire point of this thread. It is meant to be a megathread pertaining to these crash issues. I do not believe the issue is a driver problem on Nvidia or AMD. I believe that it is most likely a game specific issue that Square would need to address. So yes, I could post this megathread on Square's forums too. But frankly, I don't think that Square reads their own forums or the Steam forums for that matter.

I have zero faith that any one else is going to fix these crashes for the community. Whether that be Square themselves or Nvidia/AMD. I feel that it is going to be up to us community members to find and resolve this issue through our own means.

Steam has thousands of people playing FFXV and experiencing this game crashing issue so I think this is a great place to start the megathread. But to your credit I probably will post it over on the Square official forums later as well just to gather as much data from as many users as possible.
Last edited by Maverik770; Mar 14, 2018 @ 10:51am
Well I will say this much, I have only ever seen 3 users on this forum complain about gray screen lockup. 2 on AMD and one on Nvidia gpus. One of them got it sorted by activating borderless mode.
Maverik770 Mar 14, 2018 @ 11:05am 
I've seen multiple threads and people talking about the issue. But I have also purposely been searching for those threads and posts as well.

I included the Borderless Window method in my main post above. It does HELP with the issue but it does not eliminate it and it causes other issues that were normally not present. So it is by far not a full resolution to the problem. Especially in Comrades mode. Borderless Window barely does anything to resolve how often Comrades mode crashes with this same error.

I don't think the devs really meant for the game to run in Borderless Window mode. Hence why the option is hidden in the .ini file only. Its causes graphical artifacts and anomalies to randomly occur.
Last edited by Maverik770; Mar 14, 2018 @ 11:06am
Originally posted by Maverik770:
I've seen multiple threads and people talking about the issue. But I have also purposely been searching for those threads and posts as well.

I included the Borderless Window method in my main post above. It does HELP with the issue but it does not eliminate it and it causes other issues that were normally not present. So it is by far not a full resolution to the problem. Especially in Comrades mode. Borderless Window barely does anything tor esolve how often Comrades mode crashes.

I don't think the devs really meant for the game to run in Borderless Window mode. Hence why the option is hidden in the .ini file only. Its causes graphical artifacts and anomalies to randomly occur.

Dunno about that, I run the game in borderless mode and have no artifacts or anomalies. But I do borderless because I need to ALT tab all the time and if I run fullscreen and press ALT TAB then it makes the whole game windowed and puts on a watermark grid all over my screen. So using borderless fixed that for me.
m4u1nh0 Mar 14, 2018 @ 11:10am 
Gtx 1080, hotfix drivers, DDU install, clean fresh windows install, no issues whatsoever, grey screen, random crashes with no explanation, running out of memory randomly all sorts happens in this game... love the game performance is good but reliability is worse then a junkie with a £20 quid note!
Last edited by m4u1nh0; Mar 14, 2018 @ 11:10am
Maverik770 Mar 14, 2018 @ 11:41am 
Originally posted by Mezrianna:
@Grandmaster Foo, that's because they're in the technical support forum :P

But yeah, I'm experiencing grey and black screen lock ups as are many other people since this latest patch from what I see over there.

i7-4770k
1080ti
32GB RAM
and game is on an SSD. Max settings. 2560x1440. G-sync on.

Prior to the patch the game ran for hours on end and I never experienced a crash; new patch comes out and I can't get past the main menu without a crash.

I've tried many of the same things, verifying game files, clean driver install, special K, etc. Nope. Nothing. Just black and grey screens. Rather annoying since the first 30 hours I put into this worked beautifully.
That's awful. I'm sorry to hear that your crashing has become that bad. My issues occurred before and after the recent game patch so I can't speak to any changes caused by the patch.

Have you tried adjusting your Windows Page Filing or different Compability Settings on the game's exe file yet? What about the Borderless Fullscreen mode?

I intend to run tests with those things later today and will update this thread accordingly.
Maverik770 Mar 14, 2018 @ 11:42am 
Originally posted by Grandmaster Foo:
Originally posted by Maverik770:
I've seen multiple threads and people talking about the issue. But I have also purposely been searching for those threads and posts as well.

I included the Borderless Window method in my main post above. It does HELP with the issue but it does not eliminate it and it causes other issues that were normally not present. So it is by far not a full resolution to the problem. Especially in Comrades mode. Borderless Window barely does anything tor esolve how often Comrades mode crashes.

I don't think the devs really meant for the game to run in Borderless Window mode. Hence why the option is hidden in the .ini file only. Its causes graphical artifacts and anomalies to randomly occur.

Dunno about that, I run the game in borderless mode and have no artifacts or anomalies. But I do borderless because I need to ALT tab all the time and if I run fullscreen and press ALT TAB then it makes the whole game windowed and puts on a watermark grid all over my screen. So using borderless fixed that for me.
Yeah, it's really, really strange. I can't think of any reasons why running in Borderless Window would cause random graphical anomalies but it does. I will take a screenshot later and post it for everyone to see. I have zero explanation for it. I have ran plenty of other games in Borderless Window just fine without issue. The whole problem makes no sense at all.
CrysisCore20 Mar 14, 2018 @ 12:25pm 
THANK GOD IT'S NOT JUST ME! They really need to fix this and considering they only patched the Summon issue this week I'm worried they'll never care. It is Square Enix.
Bärchen Mar 14, 2018 @ 1:38pm 
Thats right, tried a lot of troubleshooting, but nothing worked.
The Game Crashes so many time, that i cant continue playing... hope for a solution or a fix soon.:steamsad:
Maverik770 Mar 14, 2018 @ 8:24pm 
Originally posted by CrysisCore20:
THANK GOD IT'S NOT JUST ME! They really need to fix this and considering they only patched the Summon issue this week I'm worried they'll never care. It is Square Enix.
I agree completely. That's my biggest worry too.
Maverik770 Mar 14, 2018 @ 8:26pm 
Originally posted by Bärchen:
Thats right, tried a lot of troubleshooting, but nothing worked.
The Game Crashes so many time, that i cant continue playing... hope for a solution or a fix soon.:steamsad:
Did you try the Borderless Window mode yet? It's the single change that made the most positive impact for me on reducing the crashes. But it also introduced weird graphics glitches for me. If you haven't tried Borderless Fullscreen give that a shot.

I'm going to do more testing tonight to see if I can find any other ideas.
Maverik770 Mar 14, 2018 @ 8:42pm 
Can you guys please check your Windows Event Viewer logs under Custom Views -> Administrative Events to see if you're getting any messages in there around the time your game is crashing or locking up? I'd love to know if you are and if so, what the error messages are.

Also can you please post your machine's specs? Do you run the game off a HDD or SSD?
Maverik770 Mar 15, 2018 @ 3:06pm 
**SOLUTION**

Alright so I did some pretty extensive testing last night and I think I may have nailed down the cause of this issue, at least for myself. I wouldn't be the least bit surprised that the cause of this issue could be very similar for other people as well:

The problem is in fact caused by the GPU being unstable, most likely by not enough power being provided to the GPU. I had a strong suspicion that could be the issue but apparently I hadn't gone far enough to confirm it in my initial power testing.

As we know, this game really pushes hardware, especially if you are running a resolution above 1080p. Hell, even 1080p at "High" or above settings is very demanding on your GPU. That is why for myself and many others this game is exposing issues in your GPU and/or it's configuration that other games normally wouldn't. This can create an illusion that the issue is isolated to only FFXV. And to an extent that may be true but FFXV isn't necessarily the cause.

FFXV is not the best optimized game out there on PC and as Kaldaien, as well as many other members of the community who have been digging into the guts of this game to see how it works, have found that the game does some really bad and wonky stuff in terms of how it handles and processes things. In short, it doesn't process calls in the best way possible and this can lead to really hammering your hardware more than needed. On top of that, obviously, the game is super demanding even in the best case scenarios, especially on your GPU.

I have a MSI RX 580 8 GBs Gaming X GPU which has it's base max clock speed configured for 1380 MHz. I have never OC'd it myself beyond that point. That is the factory overclock set on it out of the box, directly by MSI. I use AMD's Official Adrenalin 18.3.2 drivers, not MSI's custom drivers made for the GPU or MSI Afterburner for that matter.

What I'm finding in my testing is that the standard AMD Adrenalin driver (including Wattman Utility) has a cap on power draw of about 1.2v or 1200mv for my GPU. Or maybe it's the GPU itself that has a power cap of 1200mv? I'm still not 100% sure where the power draw cap is being imposed from. But if I load up Radeon Settings panel and go into Wattman Control, I cannot push more than 1200mv to my RX 580. Setting the voltages to manual control will not allow me to input anything higher than 1200mv.

My conclusion here (at least so far, I plan to do more testing) is that apparently 1200mv is just not quite enough power for the max clock speed of 1380 MHz in extreme cases. At least not on my GPU. In an extreme case such as FFXV where it is actually pushing my GPU to it's max speed of 1380 MHz constantly, 1200mv just isn't quite enough power and it eventually causes the AMD Driver to take a dump and have to auto recover itself. When that happens FFXV hangs for a split second and then goes into the dreaded "Grey Screen" lockup scenario. FFXV cannot recover the graphical feed after the Display Driver has crashed and recovered. Then you're left to kill the game process in Task Manager.

I wondered if this could be caused by anything else such as overheating but monitoring my rig through utilities such as CPU-Z, GPU-Z and HW Monitor show my GPU reaching a max temp of 74c and it never goes above that. Which should not be nearly hot enough to cause crashes to the display driver like this. Also notably, it reaches that same max temp of 74c in other games in which no crashing or issues of any kind occur.

It seems from my research that GPUs from 3rd party companies that contain high overclocks can sometimes have power draw issues as the default AMD drivers are made with default operting values of their reference models in mind and not necessarily the much higher overclock speeds that 3rd party manufacturers put on their GPUs out of the box.

Since AMD's built in Wattman would not allow me to push power above 1200mv to try and further stabilize my GPU at it's max speed of 1380 MHz, I went the opposite direction and dropped my max clock speed for "State 7 (Highest Peak Load State)" to 1300 MHz. I put the voltages back to "Auto" mode because Wattman is fine with allowing up to the 1200mv on it's own already so there didn't seem to be a need to manually force it to 1200mv at all times.

As soon as I did this and loaded FFXV back up, everything worked perfectly. No crashes, no lock ups, no grey screens. It just works now. I played for hours in both Single player and Comrades multiplayer without a single lock up, grey screen or crash of any kind. I was using the "High" presets option with the HD "Assets" option turned. Geomapping and all Nvidia options disabled. Framerate cap at 60 FPS and VSync On with Hardware Fullscreen Enabled (Not Borderless Window).

A few people have told me that I should be able to use something like MSI Afterburner to push above the 1200mv to try and further stabilize my card at it's max clock speed of 1380 MHz and I may yet try that as I would like to get that extra 80 MHz back. It is also possible I did not have to lower from 1380 MHz all the way to 1300 MHz. It may be possible to push the clock speed back up a tiny bit whilst still at a max power draw of 1200mv. It will require some more testing and fine tuning to hit that sweet spot.

Performance wise I honestly didn't notice much of a difference at all. Framerates seemed almost identical and the experience was quite smooth, probably exactly the same as before. It's possible I may have been averaging 1-5 FPS lower overall (if even) but that's a worth while trade off for a solid, stable experience with no crashes or lock ups. Admittedly I am not all that far in the game so I have not hit the big problematic areas of the game yet (Lestallum, Summons, etc.) that people say cause the most issues. So we will see what happens when I do reach those points in the game. But at least I will be able to actually get to those points now that I can play the game crash free!

If you are experiencing game lock ups, crashes, grey (or black) screens you should absolutely test this yourself! I really didn't think this would be the issue after my initial test of bumping power up to the max 1200mv but apparently I just hadn't gone far enough. A very simple way would be to use Wattman or your Nvidia Control Panel equivalent and just slightly dial down your clock speed a little bit at a time, load the game, test to see if the issue has improved and adjust accordingly. If you have room to spare on increasing power draw then you can go in that direction instead. But from what I'm seeing a lot of these 3rd party GPUs that come heavily OC'd out of the box require a bit more power than you may be able to reach in your default Driver control panel.

I'm a bit miffed that my GPU out of the box has this hidden issue in extreme cases as you would expect MSI to stabilize this thing for normal power draws form the default drivers but apparently this is a pretty common thing and I am not using MSI's custom drivers so that could be part of the issue as well. Don't overlook this possibility! I beat my head against my desk for days trying so many resolutions to resolve this issue and all it took was 30 seconds to dial back my GPU's clock speed a measly 80 MHz and boom, silky smooth stable gameplay.

I really hope this can help others with this issue. I'm sure plenty of others are experiencing crashes and lock ups that genuinely may not pertain to their GPUs at all but a great way to check is to look in your Event Viewer logs frequently after you crash. You may not find the event log every single time your game crashes but if your issue is related to this then a majority of the crashes will most likely create a "WARNING" entry that states something about your Display Driver crashing and recovering.

This is the exact message that I was finding in my Windows Event Viewer under Custom Views -> Administrative Events:

Warning: Display driver amdkmdap stopped responding and has successfully recovered.

If you see that message or a similar one in your Event Viewer and are confident you have done a clean display driver install/update then you very likely need to fiddle with your GPU's clock speeds and power draw.

Perhaps it's more a problem because of how shoddy this game processes things on the back end or it really does just require that much power from your GPU? I don't know but I had never had this issue in any other games and I have played hundreds of them on this GPU.

I will post further updates as I do more testing to try and nail this down a bit more conclusively and provide more details for everyone.

Happy Hunting Everyone! :extrastrongcoffee::p2chell:
Last edited by Maverik770; Mar 15, 2018 @ 3:19pm
CrysisCore20 Mar 15, 2018 @ 4:26pm 
Originally posted by Maverik770:
**SOLUTION**

Alright so I did some pretty extensive testing last night and I think I may have nailed down the cause of this issue, at least for myself. I wouldn't be the least bit surprised that the cause of this issue could be very similar for other people as well:

The problem is in fact caused by the GPU being unstable, most likely by not enough power being provided to the GPU. I had a strong suspicion that could be the issue but apparently I hadn't gone far enough to confirm it in my initial power testing.

As we know, this game really pushes hardware, especially if you are running a resolution above 1080p. Hell, even 1080p at "High" or above settings is very demanding on your GPU. That is why for myself and many others this game is exposing issues in your GPU and/or it's configuration that other games normally wouldn't. This can create an illusion that the issue is isolated to only FFXV. And to an extent that may be true but FFXV isn't necessarily the cause.

FFXV is not the best optimized game out there on PC and as Kaldaien, as well as many other members of the community who have been digging into the guts of this game to see how it works, have found that the game does some really bad and wonky stuff in terms of how it handles and processes things. In short, it doesn't process calls in the best way possible and this can lead to really hammering your hardware more than needed. On top of that, obviously, the game is super demanding even in the best case scenarios, especially on your GPU.

I have a MSI RX 580 8 GBs Gaming X GPU which has it's base max clock speed configured for 1380 MHz. I have never OC'd it myself beyond that point. That is the factory overclock set on it out of the box, directly by MSI. I use AMD's Official Adrenalin 18.3.2 drivers, not MSI's custom drivers made for the GPU or MSI Afterburner for that matter.

What I'm finding in my testing is that the standard AMD Adrenalin driver (including Wattman Utility) has a cap on power draw of about 1.2v or 1200mv for my GPU. Or maybe it's the GPU itself that has a power cap of 1200mv? I'm still not 100% sure where the power draw cap is being imposed from. But if I load up Radeon Settings panel and go into Wattman Control, I cannot push more than 1200mv to my RX 580. Setting the voltages to manual control will not allow me to input anything higher than 1200mv.

My conclusion here (at least so far, I plan to do more testing) is that apparently 1200mv is just not quite enough power for the max clock speed of 1380 MHz in extreme cases. At least not on my GPU. In an extreme case such as FFXV where it is actually pushing my GPU to it's max speed of 1380 MHz constantly, 1200mv just isn't quite enough power and it eventually causes the AMD Driver to take a dump and have to auto recover itself. When that happens FFXV hangs for a split second and then goes into the dreaded "Grey Screen" lockup scenario. FFXV cannot recover the graphical feed after the Display Driver has crashed and recovered. Then you're left to kill the game process in Task Manager.

I wondered if this could be caused by anything else such as overheating but monitoring my rig through utilities such as CPU-Z, GPU-Z and HW Monitor show my GPU reaching a max temp of 74c and it never goes above that. Which should not be nearly hot enough to cause crashes to the display driver like this. Also notably, it reaches that same max temp of 74c in other games in which no crashing or issues of any kind occur.

It seems from my research that GPUs from 3rd party companies that contain high overclocks can sometimes have power draw issues as the default AMD drivers are made with default operting values of their reference models in mind and not necessarily the much higher overclock speeds that 3rd party manufacturers put on their GPUs out of the box.

Since AMD's built in Wattman would not allow me to push power above 1200mv to try and further stabilize my GPU at it's max speed of 1380 MHz, I went the opposite direction and dropped my max clock speed for "State 7 (Highest Peak Load State)" to 1300 MHz. I put the voltages back to "Auto" mode because Wattman is fine with allowing up to the 1200mv on it's own already so there didn't seem to be a need to manually force it to 1200mv at all times.

As soon as I did this and loaded FFXV back up, everything worked perfectly. No crashes, no lock ups, no grey screens. It just works now. I played for hours in both Single player and Comrades multiplayer without a single lock up, grey screen or crash of any kind. I was using the "High" presets option with the HD "Assets" option turned. Geomapping and all Nvidia options disabled. Framerate cap at 60 FPS and VSync On with Hardware Fullscreen Enabled (Not Borderless Window).

A few people have told me that I should be able to use something like MSI Afterburner to push above the 1200mv to try and further stabilize my card at it's max clock speed of 1380 MHz and I may yet try that as I would like to get that extra 80 MHz back. It is also possible I did not have to lower from 1380 MHz all the way to 1300 MHz. It may be possible to push the clock speed back up a tiny bit whilst still at a max power draw of 1200mv. It will require some more testing and fine tuning to hit that sweet spot.

Performance wise I honestly didn't notice much of a difference at all. Framerates seemed almost identical and the experience was quite smooth, probably exactly the same as before. It's possible I may have been averaging 1-5 FPS lower overall (if even) but that's a worth while trade off for a solid, stable experience with no crashes or lock ups. Admittedly I am not all that far in the game so I have not hit the big problematic areas of the game yet (Lestallum, Summons, etc.) that people say cause the most issues. So we will see what happens when I do reach those points in the game. But at least I will be able to actually get to those points now that I can play the game crash free!

If you are experiencing game lock ups, crashes, grey (or black) screens you should absolutely test this yourself! I really didn't think this would be the issue after my initial test of bumping power up to the max 1200mv but apparently I just hadn't gone far enough. A very simple way would be to use Wattman or your Nvidia Control Panel equivalent and just slightly dial down your clock speed a little bit at a time, load the game, test to see if the issue has improved and adjust accordingly. If you have room to spare on increasing power draw then you can go in that direction instead. But from what I'm seeing a lot of these 3rd party GPUs that come heavily OC'd out of the box require a bit more power than you may be able to reach in your default Driver control panel.

I'm a bit miffed that my GPU out of the box has this hidden issue in extreme cases as you would expect MSI to stabilize this thing for normal power draws form the default drivers but apparently this is a pretty common thing and I am not using MSI's custom drivers so that could be part of the issue as well. Don't overlook this possibility! I beat my head against my desk for days trying so many resolutions to resolve this issue and all it took was 30 seconds to dial back my GPU's clock speed a measly 80 MHz and boom, silky smooth stable gameplay.

I really hope this can help others with this issue. I'm sure plenty of others are experiencing crashes and lock ups that genuinely may not pertain to their GPUs at all but a great way to check is to look in your Event Viewer logs frequently after you crash. You may not find the event log every single time your game crashes but if your issue is related to this then a majority of the crashes will most likely create a "WARNING" entry that states something about your Display Driver crashing and recovering.

This is the exact message that I was finding in my Windows Event Viewer under Custom Views -> Administrative Events:

Warning: Display driver amdkmdap stopped responding and has successfully recovered.

If you see that message or a similar one in your Event Viewer and are confident you have done a clean display driver install/update then you very likely need to fiddle with your GPU's clock speeds and power draw.

Perhaps it's more a problem because of how shoddy this game processes things on the back end or it really does just require that much power from your GPU? I don't know but I had never had this issue in any other games and I have played hundreds of them on this GPU.

I will post further updates as I do more testing to try and nail this down a bit more conclusively and provide more details for everyone.

Happy Hunting Everyone! :extrastrongcoffee::p2chell:
Great post! To clarify: we should try lowering our GPU clock speeds to levels more sustainable. Is that correct?
< >
Showing 1-15 of 18 comments
Per page: 1530 50

Date Posted: Mar 14, 2018 @ 10:32am
Posts: 18