GTA V - Problems & Solutions List (Please keep GTA discussion here)
51 / 94
[quote=""]Hmm.. very weird thing... On my SLI setup (3D Surround) 3D doesn't disable. Game doesn't crash with "Stopped responding message"
On my Laptop however I get both. Now the "disable" part can be "fixed" by going to settings and change the refresh rate.
However the crashes are annoying as hell... Anyone found any work around regarding this? Specific driver or stuff like this? (I looked through the thread but can't find anything related to this exactly.... Maybe I missed the info ?)
I would appreciate if someone can point it to me;)
Cheers![/quote]
What do you get in event viewer on application logs when the game crashes? What error shows up? I haven't even tried playing GTA again cause I feel like I'll just be wasting time trying to get it to work. I may start playing other backlog games I have loke Shadow of Mordor to relieve the stress of getting GTA to work. So frustrating.
said:Hmm.. very weird thing... On my SLI setup (3D Surround) 3D doesn't disable. Game doesn't crash with "Stopped responding message"
On my Laptop however I get both. Now the "disable" part can be "fixed" by going to settings and change the refresh rate.
However the crashes are annoying as hell... Anyone found any work around regarding this? Specific driver or stuff like this? (I looked through the thread but can't find anything related to this exactly.... Maybe I missed the info ?)
I would appreciate if someone can point it to me;)
Cheers!
What do you get in event viewer on application logs when the game crashes? What error shows up? I haven't even tried playing GTA again cause I feel like I'll just be wasting time trying to get it to work. I may start playing other backlog games I have loke Shadow of Mordor to relieve the stress of getting GTA to work. So frustrating.
PROJECT PROMETHEUS:
Intel Core i5 3570K @ 4.6GHz - Corsair H100 Liquid Cooling
Palit JetStream GTX680/EVGA Superclocked GTX680 in SLI
Asus P8Z77-V
Crucial M4 128GB SATA3 SSD/WD Caviar Green 3TB SATA3 HDD
Corsair Vengeance 2x4GB @ 1600
Seasonic M12II 850W Bronze Certified
Asus VG278H 1920x1080 120Hz 3D Vision 2
CM Storm Trooper
CM Storm Quickfire Pro (MX Black Switch)
CM Storm Spawn
Logitech Z623/Fiio E10 DAC/Superlux HD681 EVO/Superlux HD661
[quote=""][quote=""]Hmm.. very weird thing... On my SLI setup (3D Surround) 3D doesn't disable. Game doesn't crash with "Stopped responding message"
On my Laptop however I get both. Now the "disable" part can be "fixed" by going to settings and change the refresh rate.
However the crashes are annoying as hell... Anyone found any work around regarding this? Specific driver or stuff like this? (I looked through the thread but can't find anything related to this exactly.... Maybe I missed the info ?)
I would appreciate if someone can point it to me;)
Cheers![/quote]What do you get in event viewer on application logs when the game crashes? What error shows up? I haven't even tried playing GTA again cause I feel like I'll just be wasting time trying to get it to work. I may start playing other backlog games I have loke Shadow of Mordor to relieve the stress of getting GTA to work. So frustrating.[/quote]
Yeah, I'd hold off for a bit longer. There is no solution to the crashes that I've heard. I also just recently sent my 100% reproducible test case to both R* and my contact at NVidia, and I know it's getting some attention, and 100% reproducible generally makes it interesting to fix and a slam dunk to fix. I'll keep you posted.
The interesting part of this bug is that it ONLY crashes when in 3D. In 2D it runs fine. This explains why the crash has persisted this long. My test case is dead simple- just run the benchmark for 200 tries in 3D. If anyone finds a scenario where that works, we'll have a winner.
I just installed and ran 353.06 and it still crashes in my test case there. It's notable that I don't have the stereo-to-mono problem that I see in 353.30 though.
said:Hmm.. very weird thing... On my SLI setup (3D Surround) 3D doesn't disable. Game doesn't crash with "Stopped responding message"
On my Laptop however I get both. Now the "disable" part can be "fixed" by going to settings and change the refresh rate.
However the crashes are annoying as hell... Anyone found any work around regarding this? Specific driver or stuff like this? (I looked through the thread but can't find anything related to this exactly.... Maybe I missed the info ?)
I would appreciate if someone can point it to me;)
Cheers!
What do you get in event viewer on application logs when the game crashes? What error shows up? I haven't even tried playing GTA again cause I feel like I'll just be wasting time trying to get it to work. I may start playing other backlog games I have loke Shadow of Mordor to relieve the stress of getting GTA to work. So frustrating.
Yeah, I'd hold off for a bit longer. There is no solution to the crashes that I've heard. I also just recently sent my 100% reproducible test case to both R* and my contact at NVidia, and I know it's getting some attention, and 100% reproducible generally makes it interesting to fix and a slam dunk to fix. I'll keep you posted.
The interesting part of this bug is that it ONLY crashes when in 3D. In 2D it runs fine. This explains why the crash has persisted this long. My test case is dead simple- just run the benchmark for 200 tries in 3D. If anyone finds a scenario where that works, we'll have a winner.
I just installed and ran 353.06 and it still crashes in my test case there. It's notable that I don't have the stereo-to-mono problem that I see in 353.30 though.
Acer H5360 (1280x720@120Hz) - ASUS VG248QE with GSync mod - 3D Vision 1&2 - Driver 372.54
GTX 970 - i5-4670K@4.2GHz - 12GB RAM - Win7x64+evilKB2670838 - 4 Disk X25 RAID
SAGER NP9870-S - GTX 980 - i7-6700K - Win10 Pro 1607 Latest 3Dmigoto Release Bo3b's School for ShaderHackers
@tbonesan
It sure is a looker, when it's working. Riding a motorbike at over 100mph whilst threading and weaving through proper 3D traffic is pretty exhilarating stuff. That's not even counting the gameplay.
@bo3b
I'm currently running your benchmark again, but doubling the duration this time. The whole process will last at least 8 hours, if it works. I'll present my results to you, but only if it completes the entire benchmark.
@vulcan78
Vulcs, do you have a copy of this game? If so, is it working for you? Again, if so, could you kindly run a 200 rep bench test and present any results here? I'm asking because you're still using the 700 Series. As I've mentioned to bo3b, I've not updated my operating system at all. It may or may not have an effect on how this game performs in 3D, but it'll be interesting to find out. I'll have to assume that you have updated your own OS, which I also assume is still Win 7. I'd appreciate any assistance that you can offer, if you're in a position to do so.
It sure is a looker, when it's working. Riding a motorbike at over 100mph whilst threading and weaving through proper 3D traffic is pretty exhilarating stuff. That's not even counting the gameplay.
@bo3b
I'm currently running your benchmark again, but doubling the duration this time. The whole process will last at least 8 hours, if it works. I'll present my results to you, but only if it completes the entire benchmark.
@vulcan78
Vulcs, do you have a copy of this game? If so, is it working for you? Again, if so, could you kindly run a 200 rep bench test and present any results here? I'm asking because you're still using the 700 Series. As I've mentioned to bo3b, I've not updated my operating system at all. It may or may not have an effect on how this game performs in 3D, but it'll be interesting to find out. I'll have to assume that you have updated your own OS, which I also assume is still Win 7. I'd appreciate any assistance that you can offer, if you're in a position to do so.
3D works well on my GTAV on the newest drivers. I'm running Win 8.1 with the Asus Mars 760x2... However... it seems to periodically de-sync a little bit, causing odd ghosting every few seconds.
3D works well on my GTAV on the newest drivers. I'm running Win 8.1 with the Asus Mars 760x2... However... it seems to periodically de-sync a little bit, causing odd ghosting every few seconds.
@bo3b
Received an error saying that GTA V eventually ran out memory. The last successful pass on this test was at 204. Is that a memory error that you would expect at that stage in the test, or do you suspect that perhaps it's simply game instability? Anyway, I gave it a shot.
@vulcan78
I'll take that as a no then.
Received an error saying that GTA V eventually ran out memory. The last successful pass on this test was at 204. Is that a memory error that you would expect at that stage in the test, or do you suspect that perhaps it's simply game instability? Anyway, I gave it a shot.
[quote=""]@bo3b
Received an error saying that GTA V eventually ran out memory. The last successful pass on this test was at 204. Is that a memory error that you would expect at that stage in the test, or do you suspect that perhaps it's simply game instability? Anyway, I gave it a shot.
@vulcan78
I'll take that as a no then.[/quote]
Interesting. Could be that this crash is a 3D specific out of memory problem. Reporting tools don't show out of VRAM, but I've seen some indication that it spikes system memory right before it crashes.
Hard to tell what is going on. I'm running 353.06 at the moment, and it dropped out on 3D immediately today, whereas yesterday it worked fine for 30 minutes I had. Then a little later, relaunch, 3D engages and works fine for maybe 2 minutes and drops out. Play with control panel settings and now it's stable on 3D for as long as I can, but gets to a crash.
So 353.06 is not as terrible as it seems? Far Cry 4 also worked similarly.
Received an error saying that GTA V eventually ran out memory. The last successful pass on this test was at 204. Is that a memory error that you would expect at that stage in the test, or do you suspect that perhaps it's simply game instability? Anyway, I gave it a shot.
@vulcan78
I'll take that as a no then.
Interesting. Could be that this crash is a 3D specific out of memory problem. Reporting tools don't show out of VRAM, but I've seen some indication that it spikes system memory right before it crashes.
Hard to tell what is going on. I'm running 353.06 at the moment, and it dropped out on 3D immediately today, whereas yesterday it worked fine for 30 minutes I had. Then a little later, relaunch, 3D engages and works fine for maybe 2 minutes and drops out. Play with control panel settings and now it's stable on 3D for as long as I can, but gets to a crash.
So 353.06 is not as terrible as it seems? Far Cry 4 also worked similarly.
Acer H5360 (1280x720@120Hz) - ASUS VG248QE with GSync mod - 3D Vision 1&2 - Driver 372.54
GTX 970 - i5-4670K@4.2GHz - 12GB RAM - Win7x64+evilKB2670838 - 4 Disk X25 RAID
SAGER NP9870-S - GTX 980 - i7-6700K - Win10 Pro 1607 Latest 3Dmigoto Release Bo3b's School for ShaderHackers
[quote=""][quote=""]@bo3b
Received an error saying that GTA V eventually ran out memory. The last successful pass on this test was at 204. Is that a memory error that you would expect at that stage in the test, or do you suspect that perhaps it's simply game instability? Anyway, I gave it a shot.
@vulcan78
I'll take that as a no then.[/quote]
Interesting. Could be that this crash is a 3D specific out of memory problem. Reporting tools don't show out of VRAM, but I've seen some indication that it spikes system memory right before it crashes.
Hard to tell what is going on. I'm running 353.06 at the moment, and it dropped out on 3D immediately today, whereas yesterday it worked fine for 30 minutes I had. Then a little later, relaunch, 3D engages and works fine for maybe 2 minutes and drops out. Play with control panel settings and now it's stable on 3D for as long as I can, but gets to a crash.
So 353.06 is not as terrible as it seems? Far Cry 4 also worked similarly.[/quote]
If the 3D drops the best way to re-enable it is to go to graphics section and change the refresh rate to a different value and apply changes. The engine re-inits and 3D is back;)
But those damn crashes in the nvidia kernel/driver is what is annoying as hell...It crashes anywhere between 10 to 30 minutes.... Yesterday I tried 5 times to make a mission until I finally was able to make it...
The 3D dropping is not a big issue with the above workaround... the driver crashing is.
This is tested on 353.06/30.
On 350.12 however things are different:
- If 3D vision breaks is broken until you completely restart the game.
- I didn't experience any driver crashes but since I cannot recover the 3D I need to restart the game anyway :(
Another difference I noticed is in the intro movie:
353.06 right eye lags and shows only one frame.
350.12 both eyes are rendered correctly...
Something is terribly wrong with the drivers.... I expect the driver crashes are related with the general driver instability right now (353.06/30)...
Received an error saying that GTA V eventually ran out memory. The last successful pass on this test was at 204. Is that a memory error that you would expect at that stage in the test, or do you suspect that perhaps it's simply game instability? Anyway, I gave it a shot.
@vulcan78
I'll take that as a no then.
Interesting. Could be that this crash is a 3D specific out of memory problem. Reporting tools don't show out of VRAM, but I've seen some indication that it spikes system memory right before it crashes.
Hard to tell what is going on. I'm running 353.06 at the moment, and it dropped out on 3D immediately today, whereas yesterday it worked fine for 30 minutes I had. Then a little later, relaunch, 3D engages and works fine for maybe 2 minutes and drops out. Play with control panel settings and now it's stable on 3D for as long as I can, but gets to a crash.
So 353.06 is not as terrible as it seems? Far Cry 4 also worked similarly.
If the 3D drops the best way to re-enable it is to go to graphics section and change the refresh rate to a different value and apply changes. The engine re-inits and 3D is back;)
But those damn crashes in the nvidia kernel/driver is what is annoying as hell...It crashes anywhere between 10 to 30 minutes.... Yesterday I tried 5 times to make a mission until I finally was able to make it...
The 3D dropping is not a big issue with the above workaround... the driver crashing is.
This is tested on 353.06/30.
On 350.12 however things are different:
- If 3D vision breaks is broken until you completely restart the game.
- I didn't experience any driver crashes but since I cannot recover the 3D I need to restart the game anyway :(
Another difference I noticed is in the intro movie:
353.06 right eye lags and shows only one frame.
350.12 both eyes are rendered correctly...
Something is terribly wrong with the drivers.... I expect the driver crashes are related with the general driver instability right now (353.06/30)...
1x Palit RTX 2080Ti Pro Gaming OC(watercooled and overclocked to hell)
3x 3D Vision Ready Asus VG278HE monitors (5760x1080).
Intel i9 9900K (overclocked to 5.3 and watercooled ofc).
Asus Maximus XI Hero Mobo.
16 GB Team Group T-Force Dark Pro DDR4 @ 3600.
Lots of Disks:
- Raid 0 - 256GB Sandisk Extreme SSD.
- Raid 0 - WD Black - 2TB.
- SanDisk SSD PLUS 480 GB.
- Intel 760p 256GB M.2 PCIe NVMe SSD.
Creative Sound Blaster Z.
Windows 10 x64 Pro.
etc
@bo3b
Shall just keep retesting as often as I can, and see if any sort of pattern emerges as far as workable limits are concerned. I'll obviously keep an eye on the error log, and report anything that's actually worth mentioning. I'll take the iteration down to 250 this time, just to see if it gets there.
Shall just keep retesting as often as I can, and see if any sort of pattern emerges as far as workable limits are concerned. I'll obviously keep an eye on the error log, and report anything that's actually worth mentioning. I'll take the iteration down to 250 this time, just to see if it gets there.
Using my benchmark stability testing, I've narrowed down two of the big settings that cause crashes. Or at least, with them off, it crashes after 170 or so runs, not after 3.
Textures=0. This one really hurts because it makes things look a lot better. Still, pretty and dead doesn't work for me.
720p. This is easy for me to use on projector, although 1080p scaled down looks terrific. I'm also willing to put up with jaggies for stability.
This is not perfect, still crashes, but it makes it dramatically more stable for me, and still let's me play in 3D. As a 3D slut, I'm willing to do anything to play in 3D.
Using my benchmark stability testing, I've narrowed down two of the big settings that cause crashes. Or at least, with them off, it crashes after 170 or so runs, not after 3.
Textures=0. This one really hurts because it makes things look a lot better. Still, pretty and dead doesn't work for me.
720p. This is easy for me to use on projector, although 1080p scaled down looks terrific. I'm also willing to put up with jaggies for stability.
This is not perfect, still crashes, but it makes it dramatically more stable for me, and still let's me play in 3D. As a 3D slut, I'm willing to do anything to play in 3D.
Acer H5360 (1280x720@120Hz) - ASUS VG248QE with GSync mod - 3D Vision 1&2 - Driver 372.54
GTX 970 - i5-4670K@4.2GHz - 12GB RAM - Win7x64+evilKB2670838 - 4 Disk X25 RAID
SAGER NP9870-S - GTX 980 - i7-6700K - Win10 Pro 1607 Latest 3Dmigoto Release Bo3b's School for ShaderHackers
@bo3b
As you speculated, this test may well have a defined memory ceiling depending directly upon how much VRAM or system RAM is available. When the memory ran out, the system hung, but after a ctrl-alt-del back to the desktop, once again there was no application error to be found in the event log. As my sig shows, I have a decent amount of system RAM available, and the amount of VRAM on a Titan certainly was good for it's day. Could you clarify that by reporting tools, I assume you're talking about the event viewer itself, indicating that the lack of VRAM actually provided the ceiling, as no specific memory error appeared in the application event log?
Well it got to 203 at least, so I've included those last few reps. Performance appears to be holding steady throughout the test.
Frames Per Second (Higher is better) Min, Max, Avg
Pass 0, 4.465684, 108.301537, 45.478676
Pass 9, 12.256461, 103.151283, 48.727169
Pass 19, 11.575042, 84.844582, 43.320328
Pass 29, 8.675290, 86.617744, 42.347965
Pass 39, 11.279039, 87.540222, 42.715347
Pass 49, 12.326242, 85.808701, 42.792034
Pass 59, 10.726724, 84.746223, 42.823673
Pass 69, 9.267789, 86.823494, 42.674473
Pass 79, 11.072723, 81.193520, 41.811520
Pass 89, 11.535713, 82.750084, 42.221924
Pass 99, 10.520137, 82.388947, 42.324978
Pass 109, 9.221301, 86.994965, 42.233105
Pass 119, 12.566946, 84.869728, 41.470741
Pass 129, 10.056978, 83.340195, 41.906254
Pass 139, 11.608872, 86.356506, 41.969318
Pass 149, 11.064985, 85.339813, 42.204830
Pass 159, 10.977068, 82.058372, 41.867153
Pass 169, 9.590775, 83.916229, 42.156914
Pass 179, 9.236497, 80.866745, 41.645508
Pass 189, 9.371942, 84.792236, 41.197365
Pass 199, 8.841561, 84.915878, 42.180401
Pass 200, 10.977734, 83.223114, 41.852669
Pass 201, 11.111181, 84.548111, 41.979183
Pass 202, 9.474828, 83.144569, 42.650940
Pass 203, 11.478868, 84.185585, 42.506622
Time in milliseconds(ms). (Lower is better). Min, Max, Avg
Pass 0, 9.233479, 223.929840, 21.988327
Pass 9, 9.694499, 81.589622, 20.522432
Pass 19, 11.786257, 86.392776, 23.083851
Pass 29, 11.544978, 115.269920, 23.613886
Pass 39, 11.423321, 88.660034, 23.410789
Pass 49, 11.653830, 81.127724, 23.368835
Pass 59, 11.799936, 93.225113, 23.351570
Pass 69, 11.517620, 107.900604, 23.433212
Pass 79, 12.316254, 90.312019, 23.916853
Pass 89, 12.084579, 86.687317, 23.684378
Pass 99, 12.137550, 95.055801, 23.626711
Pass 109, 11.494918, 108.444565, 23.678108
Pass 119, 11.782764, 79.573830, 24.113386
Pass 129, 11.999012, 99.433449, 23.862787
Pass 139, 11.579904, 86.141014, 23.826929
Pass 149, 11.717860, 90.375175, 23.693970
Pass 159, 12.186447, 91.099007, 23.885073
Pass 169, 11.916646, 104.266869, 23.720901
Pass 179, 12.366023, 108.266151, 24.012194
Pass 189, 11.793532, 106.701477, 24.273397
Pass 199, 11.776361, 113.102196, 23.707693
Pass 200, 12.015893, 91.093483, 23.893339
Pass 201, 11.827585, 89.999435, 23.821331
Pass 202, 12.027244, 105.542816, 23.446142
Pass 203, 11.878518, 87.116608, 23.525745
You've obviously improved stability significantly by switching off textures, which is something at least. A resolution of a Gajillion by a Gazillion still couldn't top 3D @ 1080p for me. It's either 3D...or nothing at all.
I don't know if there's any more useful data that I can provide for you at this point, but if there is, just let me know.
As you speculated, this test may well have a defined memory ceiling depending directly upon how much VRAM or system RAM is available. When the memory ran out, the system hung, but after a ctrl-alt-del back to the desktop, once again there was no application error to be found in the event log. As my sig shows, I have a decent amount of system RAM available, and the amount of VRAM on a Titan certainly was good for it's day. Could you clarify that by reporting tools, I assume you're talking about the event viewer itself, indicating that the lack of VRAM actually provided the ceiling, as no specific memory error appeared in the application event log?
Well it got to 203 at least, so I've included those last few reps. Performance appears to be holding steady throughout the test.
You've obviously improved stability significantly by switching off textures, which is something at least. A resolution of a Gajillion by a Gazillion still couldn't top 3D @ 1080p for me. It's either 3D...or nothing at all.
I don't know if there's any more useful data that I can provide for you at this point, but if there is, just let me know.
@ToThePoint: This is great info, thanks for running the test. This means that you have fairly similar results as compared to later drivers, with a slight improvement in stability. I think we have as much info on stability as we can at the moment, hopefully they will give us a fix on my bug reports.
Doesn't hurt to keep running overnight tests. With a stable spot, might try tweaking parameters one by one to see what works. I wouldn't block any game play, but if the computer is just sitting around it might clarify some things. Last night for example I set grass to 1, and it was still stable, so now I know I can use that.
I get the same sort of results, and the game crashes when it runs out of memory in some strange way. I sometimes get an error dialog saying "game out of memory", mostly I get a hard crash in the nvidia driver, and occasionally I get big red text (from the driver I'm sure, very much like wrong frequency text), saying "out of memory".
The test tools like Nvidia inspector, overlays and the Task Monitor all use some system calls, which may or may not be reporting the memory correctly. It sure acts like a VRAM issue, but tools report it as fine.
It seems to be leaking textures somehow. Anything that lowers the texture use makes it work better without crashing. So, lowered to zero quality helps a lot, lower resolution helps because they are smaller. Capping the frame rate with vSync also seems to help because we draw fewer frames overall (leaking some on each frame).
Driving all around town like the madman I am makes it stream in a whole lot more textures, with leaks.
So, if you are trying to do a mission and avoid a crash- I think you can help it out by saving your game right before you start the mission, and try to avoid covering too much of the city. Restart the game from that reload, and you optimize your chances. Not positive, but this is my best guess at the moment.
@ToThePoint: This is great info, thanks for running the test. This means that you have fairly similar results as compared to later drivers, with a slight improvement in stability. I think we have as much info on stability as we can at the moment, hopefully they will give us a fix on my bug reports.
Doesn't hurt to keep running overnight tests. With a stable spot, might try tweaking parameters one by one to see what works. I wouldn't block any game play, but if the computer is just sitting around it might clarify some things. Last night for example I set grass to 1, and it was still stable, so now I know I can use that.
I get the same sort of results, and the game crashes when it runs out of memory in some strange way. I sometimes get an error dialog saying "game out of memory", mostly I get a hard crash in the nvidia driver, and occasionally I get big red text (from the driver I'm sure, very much like wrong frequency text), saying "out of memory".
The test tools like Nvidia inspector, overlays and the Task Monitor all use some system calls, which may or may not be reporting the memory correctly. It sure acts like a VRAM issue, but tools report it as fine.
It seems to be leaking textures somehow. Anything that lowers the texture use makes it work better without crashing. So, lowered to zero quality helps a lot, lower resolution helps because they are smaller. Capping the frame rate with vSync also seems to help because we draw fewer frames overall (leaking some on each frame).
Driving all around town like the madman I am makes it stream in a whole lot more textures, with leaks.
So, if you are trying to do a mission and avoid a crash- I think you can help it out by saving your game right before you start the mission, and try to avoid covering too much of the city. Restart the game from that reload, and you optimize your chances. Not positive, but this is my best guess at the moment.
Acer H5360 (1280x720@120Hz) - ASUS VG248QE with GSync mod - 3D Vision 1&2 - Driver 372.54
GTX 970 - i5-4670K@4.2GHz - 12GB RAM - Win7x64+evilKB2670838 - 4 Disk X25 RAID
SAGER NP9870-S - GTX 980 - i7-6700K - Win10 Pro 1607 Latest 3Dmigoto Release Bo3b's School for ShaderHackers
@bo3b
Glad to be of service, and yeah, it's very nice indeed to see some consistency in our results. As you say, stability is far from a done deal here, and although I'd closed my ticket with Rockstar a while back, thank you for keeping your enquiries open with Rockstar and NVidia and letting them know that there's still plenty of work to be done.
Knowing your persistence, you'll have tweaked your settings so much in the meantime, that you'll end up catching up and passing me sooner or later. It's inevitable.
Thanks for clarifying my reporting tool query, and the fact that on balance it's more likely to be a VRAM shortage caused by texture leakage. And yes, I too save regularly just to cut down the impact on the game engine as much as possible, just in case. Fortunately, my game's stable enough not to have to worry too much about dialling down settings, but I no longer touch the settings now. I just leave them the hell alone.
Thankfully, my experiences of late as far as crashes go isn't a 3D drop or a CTD, but rather me parting company with my bike at very high speed, whilst of course up to that point, having ridden around the city like a madman. I could have sworn I'd seen another madman driving around the city but I couldn't be sure. So it was you then. :)
Glad to be of service, and yeah, it's very nice indeed to see some consistency in our results. As you say, stability is far from a done deal here, and although I'd closed my ticket with Rockstar a while back, thank you for keeping your enquiries open with Rockstar and NVidia and letting them know that there's still plenty of work to be done.
Knowing your persistence, you'll have tweaked your settings so much in the meantime, that you'll end up catching up and passing me sooner or later. It's inevitable.
Thanks for clarifying my reporting tool query, and the fact that on balance it's more likely to be a VRAM shortage caused by texture leakage. And yes, I too save regularly just to cut down the impact on the game engine as much as possible, just in case. Fortunately, my game's stable enough not to have to worry too much about dialling down settings, but I no longer touch the settings now. I just leave them the hell alone.
Thankfully, my experiences of late as far as crashes go isn't a 3D drop or a CTD, but rather me parting company with my bike at very high speed, whilst of course up to that point, having ridden around the city like a madman. I could have sworn I'd seen another madman driving around the city but I couldn't be sure. So it was you then. :)
yeah honestly, gta V in 3d is like the biggest cock tease in the history of gaming. it's absolutely fantastic- for 15 minutes, then you get blown off massively. wtf. whoever gets this sorted out, whether they be from rokcstar, nvidia or someone here, is a true legend.
yeah honestly, gta V in 3d is like the biggest cock tease in the history of gaming. it's absolutely fantastic- for 15 minutes, then you get blown off massively. wtf. whoever gets this sorted out, whether they be from rokcstar, nvidia or someone here, is a true legend.
What do you get in event viewer on application logs when the game crashes? What error shows up? I haven't even tried playing GTA again cause I feel like I'll just be wasting time trying to get it to work. I may start playing other backlog games I have loke Shadow of Mordor to relieve the stress of getting GTA to work. So frustrating.
PROJECT PROMETHEUS:
Intel Core i5 3570K @ 4.6GHz - Corsair H100 Liquid Cooling
Palit JetStream GTX680/EVGA Superclocked GTX680 in SLI
Asus P8Z77-V
Crucial M4 128GB SATA3 SSD/WD Caviar Green 3TB SATA3 HDD
Corsair Vengeance 2x4GB @ 1600
Seasonic M12II 850W Bronze Certified
Asus VG278H 1920x1080 120Hz 3D Vision 2
CM Storm Trooper
CM Storm Quickfire Pro (MX Black Switch)
CM Storm Spawn
Logitech Z623/Fiio E10 DAC/Superlux HD681 EVO/Superlux HD661
Yeah, I'd hold off for a bit longer. There is no solution to the crashes that I've heard. I also just recently sent my 100% reproducible test case to both R* and my contact at NVidia, and I know it's getting some attention, and 100% reproducible generally makes it interesting to fix and a slam dunk to fix. I'll keep you posted.
The interesting part of this bug is that it ONLY crashes when in 3D. In 2D it runs fine. This explains why the crash has persisted this long. My test case is dead simple- just run the benchmark for 200 tries in 3D. If anyone finds a scenario where that works, we'll have a winner.
I just installed and ran 353.06 and it still crashes in my test case there. It's notable that I don't have the stereo-to-mono problem that I see in 353.30 though.
Acer H5360 (1280x720@120Hz) - ASUS VG248QE with GSync mod - 3D Vision 1&2 - Driver 372.54
GTX 970 - i5-4670K@4.2GHz - 12GB RAM - Win7x64+evilKB2670838 - 4 Disk X25 RAID
SAGER NP9870-S - GTX 980 - i7-6700K - Win10 Pro 1607
Latest 3Dmigoto Release
Bo3b's School for ShaderHackers
1) 30% chance of it launching in 3D
2) Crashing
*sigh*
It sure is a looker, when it's working. Riding a motorbike at over 100mph whilst threading and weaving through proper 3D traffic is pretty exhilarating stuff. That's not even counting the gameplay.
@bo3b
I'm currently running your benchmark again, but doubling the duration this time. The whole process will last at least 8 hours, if it works. I'll present my results to you, but only if it completes the entire benchmark.
@vulcan78
Vulcs, do you have a copy of this game? If so, is it working for you? Again, if so, could you kindly run a 200 rep bench test and present any results here? I'm asking because you're still using the 700 Series. As I've mentioned to bo3b, I've not updated my operating system at all. It may or may not have an effect on how this game performs in 3D, but it'll be interesting to find out. I'll have to assume that you have updated your own OS, which I also assume is still Win 7. I'd appreciate any assistance that you can offer, if you're in a position to do so.
Intel Core i7 4770k @ 4.4Ghz, 3x GTX Titan, 16GB Tactical Tracer LED, CPU/GPU Dual-Loop Water-Cooled - Driver 331.82 (Win8.0), Driver 388.71 (Win7), DX11.0
harisukro: "You sir, are 'Steely Eyed Missile Man'" (Quote from Apollo 13)
Received an error saying that GTA V eventually ran out memory. The last successful pass on this test was at 204. Is that a memory error that you would expect at that stage in the test, or do you suspect that perhaps it's simply game instability? Anyway, I gave it a shot.
@vulcan78
I'll take that as a no then.
Intel Core i7 4770k @ 4.4Ghz, 3x GTX Titan, 16GB Tactical Tracer LED, CPU/GPU Dual-Loop Water-Cooled - Driver 331.82 (Win8.0), Driver 388.71 (Win7), DX11.0
harisukro: "You sir, are 'Steely Eyed Missile Man'" (Quote from Apollo 13)
Interesting. Could be that this crash is a 3D specific out of memory problem. Reporting tools don't show out of VRAM, but I've seen some indication that it spikes system memory right before it crashes.
Hard to tell what is going on. I'm running 353.06 at the moment, and it dropped out on 3D immediately today, whereas yesterday it worked fine for 30 minutes I had. Then a little later, relaunch, 3D engages and works fine for maybe 2 minutes and drops out. Play with control panel settings and now it's stable on 3D for as long as I can, but gets to a crash.
So 353.06 is not as terrible as it seems? Far Cry 4 also worked similarly.
Acer H5360 (1280x720@120Hz) - ASUS VG248QE with GSync mod - 3D Vision 1&2 - Driver 372.54
GTX 970 - i5-4670K@4.2GHz - 12GB RAM - Win7x64+evilKB2670838 - 4 Disk X25 RAID
SAGER NP9870-S - GTX 980 - i7-6700K - Win10 Pro 1607
Latest 3Dmigoto Release
Bo3b's School for ShaderHackers
If the 3D drops the best way to re-enable it is to go to graphics section and change the refresh rate to a different value and apply changes. The engine re-inits and 3D is back;)
But those damn crashes in the nvidia kernel/driver is what is annoying as hell...It crashes anywhere between 10 to 30 minutes.... Yesterday I tried 5 times to make a mission until I finally was able to make it...
The 3D dropping is not a big issue with the above workaround... the driver crashing is.
This is tested on 353.06/30.
On 350.12 however things are different:
- If 3D vision breaks is broken until you completely restart the game.
- I didn't experience any driver crashes but since I cannot recover the 3D I need to restart the game anyway :(
Another difference I noticed is in the intro movie:
353.06 right eye lags and shows only one frame.
350.12 both eyes are rendered correctly...
Something is terribly wrong with the drivers.... I expect the driver crashes are related with the general driver instability right now (353.06/30)...
1x Palit RTX 2080Ti Pro Gaming OC(watercooled and overclocked to hell)
3x 3D Vision Ready Asus VG278HE monitors (5760x1080).
Intel i9 9900K (overclocked to 5.3 and watercooled ofc).
Asus Maximus XI Hero Mobo.
16 GB Team Group T-Force Dark Pro DDR4 @ 3600.
Lots of Disks:
- Raid 0 - 256GB Sandisk Extreme SSD.
- Raid 0 - WD Black - 2TB.
- SanDisk SSD PLUS 480 GB.
- Intel 760p 256GB M.2 PCIe NVMe SSD.
Creative Sound Blaster Z.
Windows 10 x64 Pro.
etc
My website with my fixes and OpenGL to 3D Vision wrapper:
http://3dsurroundgaming.com
(If you like some of the stuff that I've done and want to donate something, you can do it with PayPal at tavyhome@gmail.com)
Shall just keep retesting as often as I can, and see if any sort of pattern emerges as far as workable limits are concerned. I'll obviously keep an eye on the error log, and report anything that's actually worth mentioning. I'll take the iteration down to 250 this time, just to see if it gets there.
Intel Core i7 4770k @ 4.4Ghz, 3x GTX Titan, 16GB Tactical Tracer LED, CPU/GPU Dual-Loop Water-Cooled - Driver 331.82 (Win8.0), Driver 388.71 (Win7), DX11.0
harisukro: "You sir, are 'Steely Eyed Missile Man'" (Quote from Apollo 13)
Textures=0. This one really hurts because it makes things look a lot better. Still, pretty and dead doesn't work for me.
720p. This is easy for me to use on projector, although 1080p scaled down looks terrific. I'm also willing to put up with jaggies for stability.
This is not perfect, still crashes, but it makes it dramatically more stable for me, and still let's me play in 3D. As a 3D slut, I'm willing to do anything to play in 3D.
Acer H5360 (1280x720@120Hz) - ASUS VG248QE with GSync mod - 3D Vision 1&2 - Driver 372.54
GTX 970 - i5-4670K@4.2GHz - 12GB RAM - Win7x64+evilKB2670838 - 4 Disk X25 RAID
SAGER NP9870-S - GTX 980 - i7-6700K - Win10 Pro 1607
Latest 3Dmigoto Release
Bo3b's School for ShaderHackers
As you speculated, this test may well have a defined memory ceiling depending directly upon how much VRAM or system RAM is available. When the memory ran out, the system hung, but after a ctrl-alt-del back to the desktop, once again there was no application error to be found in the event log. As my sig shows, I have a decent amount of system RAM available, and the amount of VRAM on a Titan certainly was good for it's day. Could you clarify that by reporting tools, I assume you're talking about the event viewer itself, indicating that the lack of VRAM actually provided the ceiling, as no specific memory error appeared in the application event log?
Well it got to 203 at least, so I've included those last few reps. Performance appears to be holding steady throughout the test.
Frames Per Second (Higher is better) Min, Max, Avg
Pass 0, 4.465684, 108.301537, 45.478676
Pass 9, 12.256461, 103.151283, 48.727169
Pass 19, 11.575042, 84.844582, 43.320328
Pass 29, 8.675290, 86.617744, 42.347965
Pass 39, 11.279039, 87.540222, 42.715347
Pass 49, 12.326242, 85.808701, 42.792034
Pass 59, 10.726724, 84.746223, 42.823673
Pass 69, 9.267789, 86.823494, 42.674473
Pass 79, 11.072723, 81.193520, 41.811520
Pass 89, 11.535713, 82.750084, 42.221924
Pass 99, 10.520137, 82.388947, 42.324978
Pass 109, 9.221301, 86.994965, 42.233105
Pass 119, 12.566946, 84.869728, 41.470741
Pass 129, 10.056978, 83.340195, 41.906254
Pass 139, 11.608872, 86.356506, 41.969318
Pass 149, 11.064985, 85.339813, 42.204830
Pass 159, 10.977068, 82.058372, 41.867153
Pass 169, 9.590775, 83.916229, 42.156914
Pass 179, 9.236497, 80.866745, 41.645508
Pass 189, 9.371942, 84.792236, 41.197365
Pass 199, 8.841561, 84.915878, 42.180401
Pass 200, 10.977734, 83.223114, 41.852669
Pass 201, 11.111181, 84.548111, 41.979183
Pass 202, 9.474828, 83.144569, 42.650940
Pass 203, 11.478868, 84.185585, 42.506622
Time in milliseconds(ms). (Lower is better). Min, Max, Avg
Pass 0, 9.233479, 223.929840, 21.988327
Pass 9, 9.694499, 81.589622, 20.522432
Pass 19, 11.786257, 86.392776, 23.083851
Pass 29, 11.544978, 115.269920, 23.613886
Pass 39, 11.423321, 88.660034, 23.410789
Pass 49, 11.653830, 81.127724, 23.368835
Pass 59, 11.799936, 93.225113, 23.351570
Pass 69, 11.517620, 107.900604, 23.433212
Pass 79, 12.316254, 90.312019, 23.916853
Pass 89, 12.084579, 86.687317, 23.684378
Pass 99, 12.137550, 95.055801, 23.626711
Pass 109, 11.494918, 108.444565, 23.678108
Pass 119, 11.782764, 79.573830, 24.113386
Pass 129, 11.999012, 99.433449, 23.862787
Pass 139, 11.579904, 86.141014, 23.826929
Pass 149, 11.717860, 90.375175, 23.693970
Pass 159, 12.186447, 91.099007, 23.885073
Pass 169, 11.916646, 104.266869, 23.720901
Pass 179, 12.366023, 108.266151, 24.012194
Pass 189, 11.793532, 106.701477, 24.273397
Pass 199, 11.776361, 113.102196, 23.707693
Pass 200, 12.015893, 91.093483, 23.893339
Pass 201, 11.827585, 89.999435, 23.821331
Pass 202, 12.027244, 105.542816, 23.446142
Pass 203, 11.878518, 87.116608, 23.525745
You've obviously improved stability significantly by switching off textures, which is something at least. A resolution of a Gajillion by a Gazillion still couldn't top 3D @ 1080p for me. It's either 3D...or nothing at all.
I don't know if there's any more useful data that I can provide for you at this point, but if there is, just let me know.
Intel Core i7 4770k @ 4.4Ghz, 3x GTX Titan, 16GB Tactical Tracer LED, CPU/GPU Dual-Loop Water-Cooled - Driver 331.82 (Win8.0), Driver 388.71 (Win7), DX11.0
harisukro: "You sir, are 'Steely Eyed Missile Man'" (Quote from Apollo 13)
Doesn't hurt to keep running overnight tests. With a stable spot, might try tweaking parameters one by one to see what works. I wouldn't block any game play, but if the computer is just sitting around it might clarify some things. Last night for example I set grass to 1, and it was still stable, so now I know I can use that.
I get the same sort of results, and the game crashes when it runs out of memory in some strange way. I sometimes get an error dialog saying "game out of memory", mostly I get a hard crash in the nvidia driver, and occasionally I get big red text (from the driver I'm sure, very much like wrong frequency text), saying "out of memory".
The test tools like Nvidia inspector, overlays and the Task Monitor all use some system calls, which may or may not be reporting the memory correctly. It sure acts like a VRAM issue, but tools report it as fine.
It seems to be leaking textures somehow. Anything that lowers the texture use makes it work better without crashing. So, lowered to zero quality helps a lot, lower resolution helps because they are smaller. Capping the frame rate with vSync also seems to help because we draw fewer frames overall (leaking some on each frame).
Driving all around town like the madman I am makes it stream in a whole lot more textures, with leaks.
So, if you are trying to do a mission and avoid a crash- I think you can help it out by saving your game right before you start the mission, and try to avoid covering too much of the city. Restart the game from that reload, and you optimize your chances. Not positive, but this is my best guess at the moment.
Acer H5360 (1280x720@120Hz) - ASUS VG248QE with GSync mod - 3D Vision 1&2 - Driver 372.54
GTX 970 - i5-4670K@4.2GHz - 12GB RAM - Win7x64+evilKB2670838 - 4 Disk X25 RAID
SAGER NP9870-S - GTX 980 - i7-6700K - Win10 Pro 1607
Latest 3Dmigoto Release
Bo3b's School for ShaderHackers
Glad to be of service, and yeah, it's very nice indeed to see some consistency in our results. As you say, stability is far from a done deal here, and although I'd closed my ticket with Rockstar a while back, thank you for keeping your enquiries open with Rockstar and NVidia and letting them know that there's still plenty of work to be done.
Knowing your persistence, you'll have tweaked your settings so much in the meantime, that you'll end up catching up and passing me sooner or later. It's inevitable.
Thanks for clarifying my reporting tool query, and the fact that on balance it's more likely to be a VRAM shortage caused by texture leakage. And yes, I too save regularly just to cut down the impact on the game engine as much as possible, just in case. Fortunately, my game's stable enough not to have to worry too much about dialling down settings, but I no longer touch the settings now. I just leave them the hell alone.
Thankfully, my experiences of late as far as crashes go isn't a 3D drop or a CTD, but rather me parting company with my bike at very high speed, whilst of course up to that point, having ridden around the city like a madman. I could have sworn I'd seen another madman driving around the city but I couldn't be sure. So it was you then. :)
Intel Core i7 4770k @ 4.4Ghz, 3x GTX Titan, 16GB Tactical Tracer LED, CPU/GPU Dual-Loop Water-Cooled - Driver 331.82 (Win8.0), Driver 388.71 (Win7), DX11.0
harisukro: "You sir, are 'Steely Eyed Missile Man'" (Quote from Apollo 13)