GTX 980 ti SLI running two 4k Monitors crashing

[DocJuan24]

Specs: eVGA GTX 980 ti SLI, 2x Samsung 28e590D monitors, eVGA SuperNOVA 1200 P2 Power Supply, AMD FX 9370 water cooled, GTX 980 ti's running SLI.

One monitor I could run a Twitch stream and play games like GTA V maxed etc no issues with the Twitch stream minimized in the background.

However I purchased my second 4k monitor this week and hooked it up tonight and tried running GTA V on one of my monitors and shifted the Twitch stream over to the second monitor. (I'm mirroring the desktop so not extending into some crazy resolution.) both monitors are running 3840x2160, anyway everything is working fine for the first 5 minutes of game play, after that the 2nd monitor starts flickering black and moments later my PC freezes and goes to a blue screen.

My suspicion (IS that 980 ti's can't handle dual 4k.) I just want to confirm them, or is one of them faulty etc, could it be that I have one hooked up via DP, and one HDMI?

Is there a way to get this configuration to work? Is this actually a CPU issue? These are things I want to rule out before deciding on purchasing Titans. Can the Titans even run 2 4k monitors?

Thanks!

Specs if needed.


CPU: AMD FX-9370 Black edition 4.4 GHz
CPU Cooler: Corsair H110i GTX Liquid CPU Cooler
Motherboard: ASUS ROG Crosshair V Formula-Z
Memory: 1 x G.SKILL Ripjaws X Series 16GB (2 x 8GB) 240-Pin DDR3
Storage: SAMSUNG MZ 500GB Solid State Drive
Video Card: Dual Nvidia GeForce GTX 980 Ti Video Card
Case: Corsair 760T White ATX Full Tower Case
Power Supply: eVGA SuperNOVA 1200 P2
Operating System: Microsoft Windows 10 (64-bit)
Keyboard: Razer Ananasi
Mouse: Razer Deathadder CHROMA
Monitor: 2x Samsung 28" 4k monitors @ 60hz
-edited to update correct power supply-

 

[DocJuan24]

Yes. You're both right, if that's the case. If there is a VERY low ambient temp, the CPU is downclocked and you're running a 240 or 280mm cooler, then temps can be much lower than normal, but they still wouldn't be 20-30°C with a high load. Those are more like idle temps, not temps under load and I don't care if you're running a custom loop they still wouldn't be that low under a major load.

Let's clarify, so there can be no mistake.

Please download Prime95 version 26.6, and ONLY version 26.6, and run small FFT for five to ten minutes then take a screenshot of both HWinfo (First half. Include CPU 0 and CPU package temp) AND Overdrive thermal margin, WITH Prime still running. It's possible that twitch and GTA-V are not fully loading the CPU. I just want to positively determine there are no thermal issues before moving on to other pastures.

http://windows-downloads-center.blogspot.com/2011/04/prime95-266.html

Will do when I get home from work this afterrnoon! Thanks so much to both of you for giving me a hand with this.

 

[Darkbreeze]

Absolutely not a problem.

 

[DocJuan24]

Yes. You're both right, if that's the case. If there is a VERY low ambient temp, the CPU is downclocked and you're running a 240 or 280mm cooler, then temps can be much lower than normal, but they still wouldn't be 20-30°C with a high load. Those are more like idle temps, not temps under load and I don't care if you're running a custom loop they still wouldn't be that low under a major load.

Let's clarify, so there can be no mistake.

Please download Prime95 version 26.6, and ONLY version 26.6, and run small FFT for five to ten minutes then take a screenshot of both HWinfo (First half. Include CPU 0 and CPU package temp) AND Overdrive thermal margin, WITH Prime still running. It's possible that twitch and GTA-V are not fully loading the CPU. I just want to positively determine there are no thermal issues before moving on to other pastures.

http://windows-downloads-center.blogspot.com/2011/04/prime95-266.html

Okay here we go!

and HWInfo

 

[Darkbreeze]

You must have the greatest FX chip ever released into the wild.

Seriously. Even though it's only at FX-8350 speeds, it's still a pretty terrific thermal scenario. I don't know why your chip isn't running at normal speeds. Are you absolutely certain it's a 9370? Did you buy that chip off Amazon or Ebay? I know there were some 8350 and 8320's being sold at higher end chips a while back but yours is reporting as a 9370 so I dunno.

With those thermal readings I'd say you could run it at it's stock configuration with no problem. Maybe try resetting the bios to stock settings and see if it increases the base clock and turbo to where they belong. None of which probably has to do with your original problem and question though unless it's the fact that there is simply a problem with the chip or motherboard that's not allowing it to run at normal speeds and causing it to crash.

 

[DocJuan24]

You must have the greatest FX chip ever released into the wild.

Seriously. Even though it's only at FX-8350 speeds, it's still a pretty terrific thermal scenario. I don't know why your chip isn't running at normal speeds. Are you absolutely certain it's a 9370? Did you buy that chip off Amazon or Ebay? I know there were some 8350 and 8320's being sold at higher end chips a while back but yours is reporting as a 9370 so I dunno.

With those thermal readings I'd say you could run it at it's stock configuration with no problem. Maybe try resetting the bios to stock settings and see if it increases the base clock and turbo to where they belong. None of which probably has to do with your original problem and question though unless it's the fact that there is simply a problem with the chip or motherboard that's not allowing it to run at normal speeds and causing it to crash.

You know what? I did buy it off of Amazon, and it didn't come in the packaging that an AMD CPU should come in. Doing a little bit of investigating I ran CPU-Z and it's showing the chipset as a 8350. This could be a possibility?

I'm now worried about my i7-6700k that I purchased from Amazon. The packaging looks legit, the top of the chip looks legit.

 

[Darkbreeze]

I kind of figured it might be something like that, but it's strange that it shows as a 9370 in HWinfo. You might even have to decipher the part number on the top of the CPU. Even that could be faked though. I'd rather have an 8350 anyhow, except that you probably paid 8370 prices. I'd REALLY go with the 6700k anyway though. The performance is vastly superior.

You might want to contact Amazon and tell them that the vendor who sold you that chip might be committing fraud. Tell them it was sold as a 9370 but is being reported as an 8350 in CPU-Z.

 

[DocJuan24]

I kind of figured it might be something like that, but it's strange that it shows as a 9370 in HWinfo. You might even have to decipher the part number on the top of the CPU. Even that could be faked though. I'd rather have an 8350 anyhow, except that you probably paid 8370 prices. I'd REALLY go with the 6700k anyway though. The performance is vastly superior.

You might want to contact Amazon and tell them that the vendor who sold you that chip might be committing fraud. Tell them it was sold as a 9370 but is being reported as an 8350 in CPU-Z.

I picked up this last night. Because I want to keep the 6700k for a 2nd PC build.
Intel Core i7-5820K Haswell-E 6-Core 3.3 GHz LGA 2011-v3 140W BX80648I75820K Desktop Processor
MSI X99A SLI KRAIT EDITION LGA 2011-v3 Intel X99 SATA 6Gb/s USB 3.1 USB 3.0 ATX Intel Motherboard


When I swap out the mobo and PC am I going to have to do anything windows wise or to my HDDs?

Also to keep on topic you don't think it's the GPU's that was causing the flickering? More of a CPU issue?

 

[azzazel_99]

Windows now has drivers for both amd and intel so you shouldn't have to do anything.

 

[Darkbreeze]

Some people have swapped from AMD to Intel, or visa versa, without too many problems, but, ME personally, I would never EVER change platforms without doing a clean install, AND you are going to have to reactivate Windows which will probably require that you contact Microsoft help desk via online chat after it's up and running, and tell them that the previous motherboard had to be replaced due to failure/issues.

If you have a valid Windows 8.1 license, you can just plug that in during the clean install and most likely not have to worry about contacting Microshaft. If you had 7 or 10, whether it was upgraded or purchased outright, you will probably need to contact them and have them reset the activation. You can try this first though, which works some of the time. Open the run dialog by right clicking the start menu and selecting run. Type in slui.exe 3, exactly like that with the 3, then enter your valid product key for 7, 8 or 10. Sometimes that works fine, other times you need to contact Microshaft and get them to reset the activation for your product key if the BIOS ID string has changed due to replacement or changing of the motherboard.

Since the chipsets are different between AMD and Intel, almost all of the core drivers are also different. Doing a clean install is the only way to ensure a clean slate that doesn't incorporate the problems that were already clearly present in the current installation. Disconnect ALL drives, after backing up any important files, and then perform a clean install to the target drive you want the OS installed on EXACTLY as follows:

1. Do this EXACTLY as outlined. AND, after backing up any files you need to back up such as browser favorites, documents, music, videos or pictures, disconnect all drives except the drive you want windows installed on:

http://www.tenforums.com/tutorials/1950-windows-10-clean-install.html

2. After that is done, do this:

http://www.tenforums.com/tutorials/4189-fast-startup-turn-off-windows-10-a.html

3. Next, do this:

http://www.tomshardware.com/faq/id-2763685/stop-windows-automatically-updating-device-drivers.html

4. Then, install all of the relevant drivers, storage controller/SATA, chipset, etc. from the motherboard product page.

5. Then download and run the DDU. Click "No" if it asks to update and then click No on the second box that pops up. Choose the Safe mode (Restart) option in the drop down box when you run the DDU:

http://www.guru3d.com/files-get/display-driver-uninstaller-download,20.html

6. After the DDU restarts in safe mode and you run it, and it completes and reboots, then install the latest GPU card driver from your models product page.


Lastly, reconnect any drives you previously disconnected.

 

[Darkbreeze]

Windows now has drivers for both amd and intel so you shouldn't have to do anything.

Windows has always had drivers for both AMD and Intel, that's is not relevant to changing platforms.

 

[Darkbreeze]

I kind of figured it might be something like that, but it's strange that it shows as a 9370 in HWinfo. You might even have to decipher the part number on the top of the CPU. Even that could be faked though. I'd rather have an 8350 anyhow, except that you probably paid 8370 prices. I'd REALLY go with the 6700k anyway though. The performance is vastly superior.

You might want to contact Amazon and tell them that the vendor who sold you that chip might be committing fraud. Tell them it was sold as a 9370 but is being reported as an 8350 in CPU-Z.

I picked up this last night. Because I want to keep the 6700k for a 2nd PC build.
Intel Core i7-5820K Haswell-E 6-Core 3.3 GHz LGA 2011-v3 140W BX80648I75820K Desktop Processor
MSI X99A SLI KRAIT EDITION LGA 2011-v3 Intel X99 SATA 6Gb/s USB 3.1 USB 3.0 ATX Intel Motherboard


When I swap out the mobo and PC am I going to have to do anything windows wise or to my HDDs?

Also to keep on topic you don't think it's the GPU's that was causing the flickering? More of a CPU issue?

Not entirely sure what the deal is with the flickering, but I think the clean install of windows and platform change will for certain tell us if it's a problem with a card or not because the OS will be fresh and on a different platform, so if it's still there, it pretty much has to be either one of the cards or the power supply.

You do realize you need DDR4 for that motherboard and CPU right? You didn't mention getting new memory so I just wanted to double check.

 

[azzazel_99]

What i meant by amd and intel default drivers is back in the day you would hit all kinds of issues switching platforms but not anymore really. Usually there isnt any issues.

 

[Darkbreeze]

It's not as bad as it once was, but it's as bad once as it ever was. Oh wait, that's a different saying. S'posed to be I'm not as GOOD as I once was, but I'm as good ONCE as I ever was. Anyhow, swapping platforms on the same OS installation can go both ways. I've seen it recently, with windows 7, 8.1 and 10, work flawlessly, and fail fabulously. I always, as does every other experienced builder and systems tech I know, recommend a clean install with any major hardware change, especially if you're changing platforms and even more so if there is already an existing problem going on with the system.


More often than not, just doing a clean install, the RIGHT way, by deleting all the existing partitions including the boot partition, and rebuilding the boot partition with a clean install, wipes out any problems the system was having as long as it wasn't strictly a hardware issue.

 

[DocJuan24]

Hmm..swapped out processor and mobo, same issue. Running 3DMark I'm getting black screen on 2nd monitor. I get a great score on 3DMark 8-9k puts me in 95% of most CPU's, but the screen flickers.

Question, didn't NVIDIA release a set of drivers recently that were bloody awful?

I'm really hoping I don't have to RMA both of these 980s. :/

Update:

WTF is this Horse Shit?
First GFX Card.

Second GFX Card.

Reading them both as x8, x8

Should be reading them @ x16 x8. I set them up exactly as instructed to get x16 x8.

I have

PCI-E 1 GTX 980 ti

PCI- Wireless Adapter

PCI-E 2- Empty

PCI-E 3- GTX 980 ti

PCI- Empty

PCI-E 4- Empty

 

[Toothless010]

"updating to the latest Nvidia 364.47 drivers triggered Blue Screen of Death issues, black screens, and all sorts of other craziness on multi-monitor Windows"

The latest NVidia drivers are 364.72 dated 03.28.2016

http://www.nvidia.com/download/driverResults.aspx/100868/en-us

found this topic interesting to follow

 

[DocJuan24]

"updating to the latest Nvidia 364.47 drivers triggered Blue Screen of Death issues, black screens, and all sorts of other craziness on multi-monitor Windows"

The latest NVidia drivers are 364.72 dated 03.28.2016

http://www.nvidia.com/download/driverResults.aspx/100868/en-us

found this topic interesting to follow

I'll be damned those might be the ones I loaded from my thumbdrive when I re-installed on these new mobo. I think that might have been the issue all along. I'll clean them out tomorrow morning and install the new ones.

In the meantime can't figure out why my SLI titans are running in x8, x8, unless I need to have them seated PCI-E 3.0 1 and 2. Although I don't know how you could get that to happen as both cards are rather thick.

 

[Darkbreeze]

What's the board model you're using now?

Did you do a clean install of Windows after changing the motherboard and CPU?

 

[DocJuan24]

I did. Even did a clean install of the most up to date NVIDIA drivers. 2nd screen still flickers black, comes back in, goes black again.

The model of the mobo is MSI X99A SLI KRAIT EDITION LGA 2011-v3 Intel X99

 

[azzazel_99]

When in sli dont both cards normally run in 8x anyway? Dont think you can grt both in 16x mode

 

[Darkbreeze]

You can, depending on the platform. The 5820k only has 28 PCI lanes though, and since 16 x2=32, there is no way for that to have dual x16 cards.

 

[DocJuan24]

Going to do a fresh install. Will post results.

Oh I knew when I purchased the board that I wasn't going to get the x16, x16 with the 28 lane CPU. But I was at least hoping for x16, x8. I guess it's not really doable unless I go with an EATX board? :/

 

[DocJuan24]

So I did a fresh install. New drivers everything, same issue when running 3DMark.

This time I got: NVIDIA Display driver stopped responding and recovered.

Log Name: System
Source: Display
Date: 4/9/2016 5:51:53 PM
Event ID: 4101
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Description:
Display driver nvlddmkm stopped responding and has successfully recovered.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Display" />
<EventID Qualifiers="0">4101</EventID>
<Level>3</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2016-04-09T21:51:53.122392900Z" />
<EventRecordID>728</EventRecordID>
<Channel>System</Channel>
<Security />
</System>
<EventData>
<Data>nvlddmkm</Data>


I'm about 2 minutes away from doing an RMA on both of these GPU's.

 

[Darkbreeze]

Either it's a bad board, bad SLI bridge or bad card I'd think. Maybe PSU. Did you say you have the latest motherboard bios installed?

Both cards work normally individually?

I don't think you ever answered whether you are using a power strip or not. If you are, eliminate it and plug directly into the wall.

 

[DocJuan24]

Either it's a bad board, bad SLI bridge or bad card I'd think. Maybe PSU. Did you say you have the latest motherboard bios installed?

Both cards work normally individually?

I don't think you ever answered whether you are using a power strip or not. If you are, eliminate it and plug directly into the wall.

I just swapped out the boards from the AMD one to the Intel one. I mean the odds of the same issue on a second board?

I'll try another SLI Bridge.

I do have the latest BIOS update installed.

It's connected to a UPS. I just connected the tower directly to the wall and same issue.

This is frustrating. It truly is. I added new RAM to the build as well. G.SKILL TridentZ Series 16GB (2 x 8GB) 288-Pin DDR4 SDRAM DDR4 3000

I'm at my wits end. Anything you want me to do with a single GPU?

 

[Darkbreeze]

Run Furmark for ten minutes. Run the Heaven benchmark. See if anything strange happens with either single card. Forgot you changed boards. Clearly, not a board issue.

I'd say it probably has to be a bad card or PSU. Can't be memory, motherboard, OS, driver or non PSU power related issue, so that's all that's left except drives. Maybe run Seatools for windows (Short DST and long generic) on all connected drives just to be sure.