Strange issue with 3D Profile Manager, please help confirm
2 / 2
I currently have DDU 15.7.4.0
You can try the profiles I uploaded from my driver installation, I'm not sure if it's any different than the profiles you have.
https://forums.geforce.com/default/topic/916941/
It could just be a SLI problem or perhaps something related to the Swift? BTW, how have you been liking your Swift, now that SLI works with it?
This... is maddening.
I've restored back to Jan 8, 2016. Since that time I reinstalled drivers several times and used Heaven many times without issue. But I can duplicate the problem easily - I cannot modify my profiles and keep Heaven working, even with DDU 15.7.2.0 and driver 361.43.
I can't understand what could have changed this. I haven't changed my overclock since then, and it's passed 10 hours of OCCT and various other tests anyway. Oh, I get this issue with my Afterburner overclock set back to stock as well.
I only have one backup going further back, to early December, when I did a clean install of Windows 10 Pro 10586. It's bare bones. But at this rate, I have almost no hope for it either. I'd suspect some sort of hardware failure, but if that were the case, it shouldn't be working prior to doing the import.
Oh - and I've always loved the Swift, even when those issues were still in place. At least in the games I was playing, SLI was working fine. That issue only affected a limited number of games, and the only one that affected me was Witcher 3, and *that* game had a host of issues with 3D that weren't resolved till the SLI issue was fixed, so I never really suffered for it. It's a great monitor.
I've restored back to Jan 8, 2016. Since that time I reinstalled drivers several times and used Heaven many times without issue. But I can duplicate the problem easily - I cannot modify my profiles and keep Heaven working, even with DDU 15.7.2.0 and driver 361.43.
I can't understand what could have changed this. I haven't changed my overclock since then, and it's passed 10 hours of OCCT and various other tests anyway. Oh, I get this issue with my Afterburner overclock set back to stock as well.
I only have one backup going further back, to early December, when I did a clean install of Windows 10 Pro 10586. It's bare bones. But at this rate, I have almost no hope for it either. I'd suspect some sort of hardware failure, but if that were the case, it shouldn't be working prior to doing the import.
Oh - and I've always loved the Swift, even when those issues were still in place. At least in the games I was playing, SLI was working fine. That issue only affected a limited number of games, and the only one that affected me was Witcher 3, and *that* game had a host of issues with 3D that weren't resolved till the SLI issue was fixed, so I never really suffered for it. It's a great monitor.
CPU: Intel Core i7-5930K
Cooler: Thermaltake Water 3.0 Ultimate
Motherboard: Asus RAMPAGE V EXTREME, BIOS 2101
Memory: G.Skill 32GB (4 x 8GB) DDR4-2666
Storage: Intel 750 Series 1.2TB PCI-E SSD
Storage: Sandisk Ultra II 960GB 2.5" SSD
Video: 2x Gigabyte Gaming G1 980 Ti in SLI, Driver 362.00
Case: Thermaltake Core V71 Full Tower
Power Supply: EVGA Supernova P2 1200W 80+ Platinum
Monitor: ROG SWIFT PG278Q 120Hz 27.0" running 1440p in 3DVision
OS: Windows 10 Pro x64 Build 10586
Overclocks:
Processor: 4.4 GHz adaptive (1.296v under load), LLC7 input 1.92v
Processor Cache: 4.2 GHz offset +0.27v (max 1.212v under load)
Memory: 2666 15-15-15-35-CR2 oc'd to 3000 15-15-15-35-CR1 at 1.38v
GPU SLI: Stock voltage, 1455 MHz, 8000Mhz memory
You could try entering Nvidia degug mode and see if it helps, it could help determine if it's an overclock issue. It's accessible via the help drop down menu in the NVCP.
Also try unplugging your monitor from the wall, to reset the g-sync module?
Just grabbing at straws here, it's very odd that this is affecting you but not us.
Perhaps it a Display Port issue, you might check the driver feedback forum.
You could try entering Nvidia degug mode and see if it helps, it could help determine if it's an overclock issue. It's accessible via the help drop down menu in the NVCP.
Also try unplugging your monitor from the wall, to reset the g-sync module?
Just grabbing at straws here, it's very odd that this is affecting you but not us.
Perhaps it a Display Port issue, you might check the driver feedback forum.
Okay, with some strategic alt-tabbing and task manager, I managed to be able to read an error message. The title is "Unigine Fatal Error". These are the first four lines:
D3D11Render:D3D11Render(): Unknown NVidia GPU
Direct3D11 error: device removed
D3D11Texture:create(): can't create RGB416F 64x64 cube texture
Direct3D11 error: device removed
The rest of the error was about 8 more sets of the last two lines, just referring to different textures.
Not all that helpful, but at least I finally managed to read it.
While I was on my Jan 8 restore, I did manage to get Heaven working after doing a *second* import. At that point, figuring restoring wasn't gaining me anything, I went back to yesterday's backup and tried doing the same thing, but so far, no dice.
Okay, with some strategic alt-tabbing and task manager, I managed to be able to read an error message. The title is "Unigine Fatal Error". These are the first four lines:
The rest of the error was about 8 more sets of the last two lines, just referring to different textures.
Not all that helpful, but at least I finally managed to read it.
While I was on my Jan 8 restore, I did manage to get Heaven working after doing a *second* import. At that point, figuring restoring wasn't gaining me anything, I went back to yesterday's backup and tried doing the same thing, but so far, no dice.
CPU: Intel Core i7-5930K
Cooler: Thermaltake Water 3.0 Ultimate
Motherboard: Asus RAMPAGE V EXTREME, BIOS 2101
Memory: G.Skill 32GB (4 x 8GB) DDR4-2666
Storage: Intel 750 Series 1.2TB PCI-E SSD
Storage: Sandisk Ultra II 960GB 2.5" SSD
Video: 2x Gigabyte Gaming G1 980 Ti in SLI, Driver 362.00
Case: Thermaltake Core V71 Full Tower
Power Supply: EVGA Supernova P2 1200W 80+ Platinum
Monitor: ROG SWIFT PG278Q 120Hz 27.0" running 1440p in 3DVision
OS: Windows 10 Pro x64 Build 10586
Overclocks:
Processor: 4.4 GHz adaptive (1.296v under load), LLC7 input 1.92v
Processor Cache: 4.2 GHz offset +0.27v (max 1.212v under load)
Memory: 2666 15-15-15-35-CR2 oc'd to 3000 15-15-15-35-CR1 at 1.38v
GPU SLI: Stock voltage, 1455 MHz, 8000Mhz memory
D-Man, I did try to import the profiles at the link you provided. Sadly didn't help.
Well, with using the current DDU and current driver, I can't seem to get Heaven working at all after a profile import, no matter what I do. When I went back to Jan 8 and was using DDU 15.7.2.0 and driver 361.43, it didn't work initially but after some time and a second import, it did. I'm going to try to keep working with that combination and seeing if it improves things.
D-Man, I did try to import the profiles at the link you provided. Sadly didn't help.
Well, with using the current DDU and current driver, I can't seem to get Heaven working at all after a profile import, no matter what I do. When I went back to Jan 8 and was using DDU 15.7.2.0 and driver 361.43, it didn't work initially but after some time and a second import, it did. I'm going to try to keep working with that combination and seeing if it improves things.
CPU: Intel Core i7-5930K
Cooler: Thermaltake Water 3.0 Ultimate
Motherboard: Asus RAMPAGE V EXTREME, BIOS 2101
Memory: G.Skill 32GB (4 x 8GB) DDR4-2666
Storage: Intel 750 Series 1.2TB PCI-E SSD
Storage: Sandisk Ultra II 960GB 2.5" SSD
Video: 2x Gigabyte Gaming G1 980 Ti in SLI, Driver 362.00
Case: Thermaltake Core V71 Full Tower
Power Supply: EVGA Supernova P2 1200W 80+ Platinum
Monitor: ROG SWIFT PG278Q 120Hz 27.0" running 1440p in 3DVision
OS: Windows 10 Pro x64 Build 10586
Overclocks:
Processor: 4.4 GHz adaptive (1.296v under load), LLC7 input 1.92v
Processor Cache: 4.2 GHz offset +0.27v (max 1.212v under load)
Memory: 2666 15-15-15-35-CR2 oc'd to 3000 15-15-15-35-CR1 at 1.38v
GPU SLI: Stock voltage, 1455 MHz, 8000Mhz memory
[quote]Have you tried to uninstall and reinstall Heaven Benchmark?[/quote]
Multiple times. Just tried it again to be sure. No change.
[quote]Remove a GPU to confirm that it's not SLI related?[/quote]
No, but not willing to. I've been running this all with SLI enabled for months, and both profile modifications and Heaven have coexisted fine. Even if I determine that SLI is involved somehow, I don't see how it would bring me closer to getting back to where I was, when I had SLI enabled and I was problem free.
[quote]Try a different Display perhaps?[/quote]
Not really an option, as I don't have another 3D display, and this is only a problem in 3D.
For the record, when I try to run Heaven after an import, the emitter *does* turn on bright green, and the light on the monitor also turns green indicating it's in 3D mode, but I don't get the "3D Vision Ready" green text.
I'll also note again that if I set "Stereo 3D" to "Disabled", it will then run just fine in 3D (though for some odd reason the depth and convergence are cranked way higher than they are when I run it under Stereo 3D: 3D Vision).
So really, at this point, I'm not aware of any totally lost functionality. The rest of my programs seem to work fine in 3D (e.g. Witcher 3, Shadow of Mordor and Tomb Raider 2013 as my currently installed games all work fine in 3D). And if I really need to run Heaven, I can do so by setting Stereo 3D to disabled. But, that doesn't explain *why* this is happening when it never happened before, with me performing all the steps just like I always have. I'm basically completely obsessing trying to figure out what's happening, because I don't think it's plausible that an inexplicable error like this will end up entirely limited to just Heaven.
Your help and pointing me to ideas is really appreciated. At least, by having the same issue happen even with the profile file you provided, I know the problem isn't happening at the point of export.
Have you tried to uninstall and reinstall Heaven Benchmark?
Multiple times. Just tried it again to be sure. No change.
Remove a GPU to confirm that it's not SLI related?
No, but not willing to. I've been running this all with SLI enabled for months, and both profile modifications and Heaven have coexisted fine. Even if I determine that SLI is involved somehow, I don't see how it would bring me closer to getting back to where I was, when I had SLI enabled and I was problem free.
Try a different Display perhaps?
Not really an option, as I don't have another 3D display, and this is only a problem in 3D.
For the record, when I try to run Heaven after an import, the emitter *does* turn on bright green, and the light on the monitor also turns green indicating it's in 3D mode, but I don't get the "3D Vision Ready" green text.
I'll also note again that if I set "Stereo 3D" to "Disabled", it will then run just fine in 3D (though for some odd reason the depth and convergence are cranked way higher than they are when I run it under Stereo 3D: 3D Vision).
So really, at this point, I'm not aware of any totally lost functionality. The rest of my programs seem to work fine in 3D (e.g. Witcher 3, Shadow of Mordor and Tomb Raider 2013 as my currently installed games all work fine in 3D). And if I really need to run Heaven, I can do so by setting Stereo 3D to disabled. But, that doesn't explain *why* this is happening when it never happened before, with me performing all the steps just like I always have. I'm basically completely obsessing trying to figure out what's happening, because I don't think it's plausible that an inexplicable error like this will end up entirely limited to just Heaven.
Your help and pointing me to ideas is really appreciated. At least, by having the same issue happen even with the profile file you provided, I know the problem isn't happening at the point of export.
CPU: Intel Core i7-5930K
Cooler: Thermaltake Water 3.0 Ultimate
Motherboard: Asus RAMPAGE V EXTREME, BIOS 2101
Memory: G.Skill 32GB (4 x 8GB) DDR4-2666
Storage: Intel 750 Series 1.2TB PCI-E SSD
Storage: Sandisk Ultra II 960GB 2.5" SSD
Video: 2x Gigabyte Gaming G1 980 Ti in SLI, Driver 362.00
Case: Thermaltake Core V71 Full Tower
Power Supply: EVGA Supernova P2 1200W 80+ Platinum
Monitor: ROG SWIFT PG278Q 120Hz 27.0" running 1440p in 3DVision
OS: Windows 10 Pro x64 Build 10586
Overclocks:
Processor: 4.4 GHz adaptive (1.296v under load), LLC7 input 1.92v
Processor Cache: 4.2 GHz offset +0.27v (max 1.212v under load)
Memory: 2666 15-15-15-35-CR2 oc'd to 3000 15-15-15-35-CR1 at 1.38v
GPU SLI: Stock voltage, 1455 MHz, 8000Mhz memory
Additional info, and testing request:
If I install driver 361.91 fresh, and don't do an import, I can run Heaven with "Stereo 3D: 3D Vision" for an hour with no problem. With my overclock. Have run it for 8 hours previously in 3D perfectly stable.
With "Stereo 3D: Disabled", it runs in full 3d vision for a short time (gets about 2/3 of the way through a benchmark) then crashes. That's the same whether before or after import. Also has some frustrum issues while it is running that I didn't notice earlier which I never get with the 3d vision setting.
Which means until I sort this out, I *do* lose functionality if I modify profiles. The disabled setting, while briefly functional, appears to be naturally unstable and useless as a benchmark or stability test.
SO, my test request is, can someone try running heaven with the stereo 3d setting set to disabled and see if they get similar results to what I just described?
If I install driver 361.91 fresh, and don't do an import, I can run Heaven with "Stereo 3D: 3D Vision" for an hour with no problem. With my overclock. Have run it for 8 hours previously in 3D perfectly stable.
With "Stereo 3D: Disabled", it runs in full 3d vision for a short time (gets about 2/3 of the way through a benchmark) then crashes. That's the same whether before or after import. Also has some frustrum issues while it is running that I didn't notice earlier which I never get with the 3d vision setting.
Which means until I sort this out, I *do* lose functionality if I modify profiles. The disabled setting, while briefly functional, appears to be naturally unstable and useless as a benchmark or stability test.
SO, my test request is, can someone try running heaven with the stereo 3d setting set to disabled and see if they get similar results to what I just described?
CPU: Intel Core i7-5930K
Cooler: Thermaltake Water 3.0 Ultimate
Motherboard: Asus RAMPAGE V EXTREME, BIOS 2101
Memory: G.Skill 32GB (4 x 8GB) DDR4-2666
Storage: Intel 750 Series 1.2TB PCI-E SSD
Storage: Sandisk Ultra II 960GB 2.5" SSD
Video: 2x Gigabyte Gaming G1 980 Ti in SLI, Driver 362.00
Case: Thermaltake Core V71 Full Tower
Power Supply: EVGA Supernova P2 1200W 80+ Platinum
Monitor: ROG SWIFT PG278Q 120Hz 27.0" running 1440p in 3DVision
OS: Windows 10 Pro x64 Build 10586
Overclocks:
Processor: 4.4 GHz adaptive (1.296v under load), LLC7 input 1.92v
Processor Cache: 4.2 GHz offset +0.27v (max 1.212v under load)
Memory: 2666 15-15-15-35-CR2 oc'd to 3000 15-15-15-35-CR1 at 1.38v
GPU SLI: Stock voltage, 1455 MHz, 8000Mhz memory
Curioser and curioser...
I went back to my bare bones backup from Dec 12 2015. Turned out I hadn't even installed Heaven yet at that point. Disconnected the internet. Reinstalled driver with the versions I had back at the time, DDU 15.7.1.0 and driver 359.06. Exported profile, modified it, and imported it. Installed and ran Heaven. Worked like a charm.
So, I figure, okay, let's immediately update with 15.7.4.1 and 361.91. Import profiles. Heaven fails. And cannot be fixed.
One interesting thing I noted is that Heaven somehow remembers your configuration settings even after you uninstall and reinstall it. I figured, ok, it leaves a .cfg around somewhere, and I found it, in c:\users\myname\heaven\heaven.cfg. I go there and delete the .cfg file. Reinstall Heaven, start it up, and it *still* remembers all of my settings. I searched my disk high and low for anything with "Heaven" or "Unigine" in it. Not a scrap left. And yet when I uninstall and reinstall Heaven it still remembers all my settings. And for the record I have Windows 10 "Sync your settings" disabled.
Anyway, I'm going to restore the bare bones backup a few more times, trying various combinations of the old and new driver and DDU, and see which combination makes it fail. I'm going to find this stupid bug if it KILLS me.
I went back to my bare bones backup from Dec 12 2015. Turned out I hadn't even installed Heaven yet at that point. Disconnected the internet. Reinstalled driver with the versions I had back at the time, DDU 15.7.1.0 and driver 359.06. Exported profile, modified it, and imported it. Installed and ran Heaven. Worked like a charm.
So, I figure, okay, let's immediately update with 15.7.4.1 and 361.91. Import profiles. Heaven fails. And cannot be fixed.
One interesting thing I noted is that Heaven somehow remembers your configuration settings even after you uninstall and reinstall it. I figured, ok, it leaves a .cfg around somewhere, and I found it, in c:\users\myname\heaven\heaven.cfg. I go there and delete the .cfg file. Reinstall Heaven, start it up, and it *still* remembers all of my settings. I searched my disk high and low for anything with "Heaven" or "Unigine" in it. Not a scrap left. And yet when I uninstall and reinstall Heaven it still remembers all my settings. And for the record I have Windows 10 "Sync your settings" disabled.
Anyway, I'm going to restore the bare bones backup a few more times, trying various combinations of the old and new driver and DDU, and see which combination makes it fail. I'm going to find this stupid bug if it KILLS me.
CPU: Intel Core i7-5930K
Cooler: Thermaltake Water 3.0 Ultimate
Motherboard: Asus RAMPAGE V EXTREME, BIOS 2101
Memory: G.Skill 32GB (4 x 8GB) DDR4-2666
Storage: Intel 750 Series 1.2TB PCI-E SSD
Storage: Sandisk Ultra II 960GB 2.5" SSD
Video: 2x Gigabyte Gaming G1 980 Ti in SLI, Driver 362.00
Case: Thermaltake Core V71 Full Tower
Power Supply: EVGA Supernova P2 1200W 80+ Platinum
Monitor: ROG SWIFT PG278Q 120Hz 27.0" running 1440p in 3DVision
OS: Windows 10 Pro x64 Build 10586
Overclocks:
Processor: 4.4 GHz adaptive (1.296v under load), LLC7 input 1.92v
Processor Cache: 4.2 GHz offset +0.27v (max 1.212v under load)
Memory: 2666 15-15-15-35-CR2 oc'd to 3000 15-15-15-35-CR1 at 1.38v
GPU SLI: Stock voltage, 1455 MHz, 8000Mhz memory
Eureka!
Okay. DDU had nothing to do with it that I can tell. The problem does NOT happen with driver 359.06, and in fact doing DDU and installing 359.06 over the more recent drivers after they have created the problem, and reimporting 359.06 profiles, will fix the problem.
I confirmed that I do consistently get the issue when importing profiles from/into both 361.43 and 361.91.
Man, it's a relief to find out the problem is not due to some sort of system corruption. I can duplicate this on a restored backup of a pristine Windows 10 Pro clean install.
Most folks here who said they couldn't reproduce the problem were running windows 7. Perhaps it is exclusive to windows 10. Or maybe to 980tis.
So if anyone with windows 10 pro and using the 980ti driver could test this, now that the drivers that cause it have been identified, that would be great. In the meantime I think this is enough to post about in the 361.91 feedback thread. In the morning. I'm frikkin tired, took me till 4:30 am to get this established, heh.
EDIT: Reported it here:
[url]https://forums.geforce.com/default/topic/916860/geforce-drivers/official-361-91-game-ready-whql-display-driver-feedback-thread-released-2-15-16-/post/4813162/#4813162[/url]
Okay. DDU had nothing to do with it that I can tell. The problem does NOT happen with driver 359.06, and in fact doing DDU and installing 359.06 over the more recent drivers after they have created the problem, and reimporting 359.06 profiles, will fix the problem.
I confirmed that I do consistently get the issue when importing profiles from/into both 361.43 and 361.91.
Man, it's a relief to find out the problem is not due to some sort of system corruption. I can duplicate this on a restored backup of a pristine Windows 10 Pro clean install.
Most folks here who said they couldn't reproduce the problem were running windows 7. Perhaps it is exclusive to windows 10. Or maybe to 980tis.
So if anyone with windows 10 pro and using the 980ti driver could test this, now that the drivers that cause it have been identified, that would be great. In the meantime I think this is enough to post about in the 361.91 feedback thread. In the morning. I'm frikkin tired, took me till 4:30 am to get this established, heh.
You can try the profiles I uploaded from my driver installation, I'm not sure if it's any different than the profiles you have.
https://forums.geforce.com/default/topic/916941/
It could just be a SLI problem or perhaps something related to the Swift? BTW, how have you been liking your Swift, now that SLI works with it?
I've restored back to Jan 8, 2016. Since that time I reinstalled drivers several times and used Heaven many times without issue. But I can duplicate the problem easily - I cannot modify my profiles and keep Heaven working, even with DDU 15.7.2.0 and driver 361.43.
I can't understand what could have changed this. I haven't changed my overclock since then, and it's passed 10 hours of OCCT and various other tests anyway. Oh, I get this issue with my Afterburner overclock set back to stock as well.
I only have one backup going further back, to early December, when I did a clean install of Windows 10 Pro 10586. It's bare bones. But at this rate, I have almost no hope for it either. I'd suspect some sort of hardware failure, but if that were the case, it shouldn't be working prior to doing the import.
Oh - and I've always loved the Swift, even when those issues were still in place. At least in the games I was playing, SLI was working fine. That issue only affected a limited number of games, and the only one that affected me was Witcher 3, and *that* game had a host of issues with 3D that weren't resolved till the SLI issue was fixed, so I never really suffered for it. It's a great monitor.
CPU: Intel Core i7-5930K
Cooler: Thermaltake Water 3.0 Ultimate
Motherboard: Asus RAMPAGE V EXTREME, BIOS 2101
Memory: G.Skill 32GB (4 x 8GB) DDR4-2666
Storage: Intel 750 Series 1.2TB PCI-E SSD
Storage: Sandisk Ultra II 960GB 2.5" SSD
Video: 2x Gigabyte Gaming G1 980 Ti in SLI, Driver 362.00
Case: Thermaltake Core V71 Full Tower
Power Supply: EVGA Supernova P2 1200W 80+ Platinum
Monitor: ROG SWIFT PG278Q 120Hz 27.0" running 1440p in 3DVision
OS: Windows 10 Pro x64 Build 10586
Overclocks:
Processor: 4.4 GHz adaptive (1.296v under load), LLC7 input 1.92v
Processor Cache: 4.2 GHz offset +0.27v (max 1.212v under load)
Memory: 2666 15-15-15-35-CR2 oc'd to 3000 15-15-15-35-CR1 at 1.38v
GPU SLI: Stock voltage, 1455 MHz, 8000Mhz memory
Also try unplugging your monitor from the wall, to reset the g-sync module?
Just grabbing at straws here, it's very odd that this is affecting you but not us.
Perhaps it a Display Port issue, you might check the driver feedback forum.
D3D11Render:D3D11Render(): Unknown NVidia GPU
Direct3D11 error: device removed
D3D11Texture:create(): can't create RGB416F 64x64 cube texture
Direct3D11 error: device removed
The rest of the error was about 8 more sets of the last two lines, just referring to different textures.
Not all that helpful, but at least I finally managed to read it.
While I was on my Jan 8 restore, I did manage to get Heaven working after doing a *second* import. At that point, figuring restoring wasn't gaining me anything, I went back to yesterday's backup and tried doing the same thing, but so far, no dice.
CPU: Intel Core i7-5930K
Cooler: Thermaltake Water 3.0 Ultimate
Motherboard: Asus RAMPAGE V EXTREME, BIOS 2101
Memory: G.Skill 32GB (4 x 8GB) DDR4-2666
Storage: Intel 750 Series 1.2TB PCI-E SSD
Storage: Sandisk Ultra II 960GB 2.5" SSD
Video: 2x Gigabyte Gaming G1 980 Ti in SLI, Driver 362.00
Case: Thermaltake Core V71 Full Tower
Power Supply: EVGA Supernova P2 1200W 80+ Platinum
Monitor: ROG SWIFT PG278Q 120Hz 27.0" running 1440p in 3DVision
OS: Windows 10 Pro x64 Build 10586
Overclocks:
Processor: 4.4 GHz adaptive (1.296v under load), LLC7 input 1.92v
Processor Cache: 4.2 GHz offset +0.27v (max 1.212v under load)
Memory: 2666 15-15-15-35-CR2 oc'd to 3000 15-15-15-35-CR1 at 1.38v
GPU SLI: Stock voltage, 1455 MHz, 8000Mhz memory
Well, with using the current DDU and current driver, I can't seem to get Heaven working at all after a profile import, no matter what I do. When I went back to Jan 8 and was using DDU 15.7.2.0 and driver 361.43, it didn't work initially but after some time and a second import, it did. I'm going to try to keep working with that combination and seeing if it improves things.
CPU: Intel Core i7-5930K
Cooler: Thermaltake Water 3.0 Ultimate
Motherboard: Asus RAMPAGE V EXTREME, BIOS 2101
Memory: G.Skill 32GB (4 x 8GB) DDR4-2666
Storage: Intel 750 Series 1.2TB PCI-E SSD
Storage: Sandisk Ultra II 960GB 2.5" SSD
Video: 2x Gigabyte Gaming G1 980 Ti in SLI, Driver 362.00
Case: Thermaltake Core V71 Full Tower
Power Supply: EVGA Supernova P2 1200W 80+ Platinum
Monitor: ROG SWIFT PG278Q 120Hz 27.0" running 1440p in 3DVision
OS: Windows 10 Pro x64 Build 10586
Overclocks:
Processor: 4.4 GHz adaptive (1.296v under load), LLC7 input 1.92v
Processor Cache: 4.2 GHz offset +0.27v (max 1.212v under load)
Memory: 2666 15-15-15-35-CR2 oc'd to 3000 15-15-15-35-CR1 at 1.38v
GPU SLI: Stock voltage, 1455 MHz, 8000Mhz memory
Remove a GPU to confirm that it's not SLI related?
Try a different Display perhaps?
Multiple times. Just tried it again to be sure. No change.
No, but not willing to. I've been running this all with SLI enabled for months, and both profile modifications and Heaven have coexisted fine. Even if I determine that SLI is involved somehow, I don't see how it would bring me closer to getting back to where I was, when I had SLI enabled and I was problem free.
Not really an option, as I don't have another 3D display, and this is only a problem in 3D.
For the record, when I try to run Heaven after an import, the emitter *does* turn on bright green, and the light on the monitor also turns green indicating it's in 3D mode, but I don't get the "3D Vision Ready" green text.
I'll also note again that if I set "Stereo 3D" to "Disabled", it will then run just fine in 3D (though for some odd reason the depth and convergence are cranked way higher than they are when I run it under Stereo 3D: 3D Vision).
So really, at this point, I'm not aware of any totally lost functionality. The rest of my programs seem to work fine in 3D (e.g. Witcher 3, Shadow of Mordor and Tomb Raider 2013 as my currently installed games all work fine in 3D). And if I really need to run Heaven, I can do so by setting Stereo 3D to disabled. But, that doesn't explain *why* this is happening when it never happened before, with me performing all the steps just like I always have. I'm basically completely obsessing trying to figure out what's happening, because I don't think it's plausible that an inexplicable error like this will end up entirely limited to just Heaven.
Your help and pointing me to ideas is really appreciated. At least, by having the same issue happen even with the profile file you provided, I know the problem isn't happening at the point of export.
CPU: Intel Core i7-5930K
Cooler: Thermaltake Water 3.0 Ultimate
Motherboard: Asus RAMPAGE V EXTREME, BIOS 2101
Memory: G.Skill 32GB (4 x 8GB) DDR4-2666
Storage: Intel 750 Series 1.2TB PCI-E SSD
Storage: Sandisk Ultra II 960GB 2.5" SSD
Video: 2x Gigabyte Gaming G1 980 Ti in SLI, Driver 362.00
Case: Thermaltake Core V71 Full Tower
Power Supply: EVGA Supernova P2 1200W 80+ Platinum
Monitor: ROG SWIFT PG278Q 120Hz 27.0" running 1440p in 3DVision
OS: Windows 10 Pro x64 Build 10586
Overclocks:
Processor: 4.4 GHz adaptive (1.296v under load), LLC7 input 1.92v
Processor Cache: 4.2 GHz offset +0.27v (max 1.212v under load)
Memory: 2666 15-15-15-35-CR2 oc'd to 3000 15-15-15-35-CR1 at 1.38v
GPU SLI: Stock voltage, 1455 MHz, 8000Mhz memory
CPU: Intel Core i7-5930K
Cooler: Thermaltake Water 3.0 Ultimate
Motherboard: Asus RAMPAGE V EXTREME, BIOS 2101
Memory: G.Skill 32GB (4 x 8GB) DDR4-2666
Storage: Intel 750 Series 1.2TB PCI-E SSD
Storage: Sandisk Ultra II 960GB 2.5" SSD
Video: 2x Gigabyte Gaming G1 980 Ti in SLI, Driver 362.00
Case: Thermaltake Core V71 Full Tower
Power Supply: EVGA Supernova P2 1200W 80+ Platinum
Monitor: ROG SWIFT PG278Q 120Hz 27.0" running 1440p in 3DVision
OS: Windows 10 Pro x64 Build 10586
Overclocks:
Processor: 4.4 GHz adaptive (1.296v under load), LLC7 input 1.92v
Processor Cache: 4.2 GHz offset +0.27v (max 1.212v under load)
Memory: 2666 15-15-15-35-CR2 oc'd to 3000 15-15-15-35-CR1 at 1.38v
GPU SLI: Stock voltage, 1455 MHz, 8000Mhz memory
If I install driver 361.91 fresh, and don't do an import, I can run Heaven with "Stereo 3D: 3D Vision" for an hour with no problem. With my overclock. Have run it for 8 hours previously in 3D perfectly stable.
With "Stereo 3D: Disabled", it runs in full 3d vision for a short time (gets about 2/3 of the way through a benchmark) then crashes. That's the same whether before or after import. Also has some frustrum issues while it is running that I didn't notice earlier which I never get with the 3d vision setting.
Which means until I sort this out, I *do* lose functionality if I modify profiles. The disabled setting, while briefly functional, appears to be naturally unstable and useless as a benchmark or stability test.
SO, my test request is, can someone try running heaven with the stereo 3d setting set to disabled and see if they get similar results to what I just described?
CPU: Intel Core i7-5930K
Cooler: Thermaltake Water 3.0 Ultimate
Motherboard: Asus RAMPAGE V EXTREME, BIOS 2101
Memory: G.Skill 32GB (4 x 8GB) DDR4-2666
Storage: Intel 750 Series 1.2TB PCI-E SSD
Storage: Sandisk Ultra II 960GB 2.5" SSD
Video: 2x Gigabyte Gaming G1 980 Ti in SLI, Driver 362.00
Case: Thermaltake Core V71 Full Tower
Power Supply: EVGA Supernova P2 1200W 80+ Platinum
Monitor: ROG SWIFT PG278Q 120Hz 27.0" running 1440p in 3DVision
OS: Windows 10 Pro x64 Build 10586
Overclocks:
Processor: 4.4 GHz adaptive (1.296v under load), LLC7 input 1.92v
Processor Cache: 4.2 GHz offset +0.27v (max 1.212v under load)
Memory: 2666 15-15-15-35-CR2 oc'd to 3000 15-15-15-35-CR1 at 1.38v
GPU SLI: Stock voltage, 1455 MHz, 8000Mhz memory
I went back to my bare bones backup from Dec 12 2015. Turned out I hadn't even installed Heaven yet at that point. Disconnected the internet. Reinstalled driver with the versions I had back at the time, DDU 15.7.1.0 and driver 359.06. Exported profile, modified it, and imported it. Installed and ran Heaven. Worked like a charm.
So, I figure, okay, let's immediately update with 15.7.4.1 and 361.91. Import profiles. Heaven fails. And cannot be fixed.
One interesting thing I noted is that Heaven somehow remembers your configuration settings even after you uninstall and reinstall it. I figured, ok, it leaves a .cfg around somewhere, and I found it, in c:\users\myname\heaven\heaven.cfg. I go there and delete the .cfg file. Reinstall Heaven, start it up, and it *still* remembers all of my settings. I searched my disk high and low for anything with "Heaven" or "Unigine" in it. Not a scrap left. And yet when I uninstall and reinstall Heaven it still remembers all my settings. And for the record I have Windows 10 "Sync your settings" disabled.
Anyway, I'm going to restore the bare bones backup a few more times, trying various combinations of the old and new driver and DDU, and see which combination makes it fail. I'm going to find this stupid bug if it KILLS me.
CPU: Intel Core i7-5930K
Cooler: Thermaltake Water 3.0 Ultimate
Motherboard: Asus RAMPAGE V EXTREME, BIOS 2101
Memory: G.Skill 32GB (4 x 8GB) DDR4-2666
Storage: Intel 750 Series 1.2TB PCI-E SSD
Storage: Sandisk Ultra II 960GB 2.5" SSD
Video: 2x Gigabyte Gaming G1 980 Ti in SLI, Driver 362.00
Case: Thermaltake Core V71 Full Tower
Power Supply: EVGA Supernova P2 1200W 80+ Platinum
Monitor: ROG SWIFT PG278Q 120Hz 27.0" running 1440p in 3DVision
OS: Windows 10 Pro x64 Build 10586
Overclocks:
Processor: 4.4 GHz adaptive (1.296v under load), LLC7 input 1.92v
Processor Cache: 4.2 GHz offset +0.27v (max 1.212v under load)
Memory: 2666 15-15-15-35-CR2 oc'd to 3000 15-15-15-35-CR1 at 1.38v
GPU SLI: Stock voltage, 1455 MHz, 8000Mhz memory
Okay. DDU had nothing to do with it that I can tell. The problem does NOT happen with driver 359.06, and in fact doing DDU and installing 359.06 over the more recent drivers after they have created the problem, and reimporting 359.06 profiles, will fix the problem.
I confirmed that I do consistently get the issue when importing profiles from/into both 361.43 and 361.91.
Man, it's a relief to find out the problem is not due to some sort of system corruption. I can duplicate this on a restored backup of a pristine Windows 10 Pro clean install.
Most folks here who said they couldn't reproduce the problem were running windows 7. Perhaps it is exclusive to windows 10. Or maybe to 980tis.
So if anyone with windows 10 pro and using the 980ti driver could test this, now that the drivers that cause it have been identified, that would be great. In the meantime I think this is enough to post about in the 361.91 feedback thread. In the morning. I'm frikkin tired, took me till 4:30 am to get this established, heh.
EDIT: Reported it here:
https://forums.geforce.com/default/topic/916860/geforce-drivers/official-361-91-game-ready-whql-display-driver-feedback-thread-released-2-15-16-/post/4813162/#4813162
CPU: Intel Core i7-5930K
Cooler: Thermaltake Water 3.0 Ultimate
Motherboard: Asus RAMPAGE V EXTREME, BIOS 2101
Memory: G.Skill 32GB (4 x 8GB) DDR4-2666
Storage: Intel 750 Series 1.2TB PCI-E SSD
Storage: Sandisk Ultra II 960GB 2.5" SSD
Video: 2x Gigabyte Gaming G1 980 Ti in SLI, Driver 362.00
Case: Thermaltake Core V71 Full Tower
Power Supply: EVGA Supernova P2 1200W 80+ Platinum
Monitor: ROG SWIFT PG278Q 120Hz 27.0" running 1440p in 3DVision
OS: Windows 10 Pro x64 Build 10586
Overclocks:
Processor: 4.4 GHz adaptive (1.296v under load), LLC7 input 1.92v
Processor Cache: 4.2 GHz offset +0.27v (max 1.212v under load)
Memory: 2666 15-15-15-35-CR2 oc'd to 3000 15-15-15-35-CR1 at 1.38v
GPU SLI: Stock voltage, 1455 MHz, 8000Mhz memory