NVIDIA Announces The New Titan X

Rizen said:
Sure thing, I can take some photos of the PCB. I am hoping my meetings at work are quick today so I can start disassembling my loop and card and get it going.

I have some Gelid GC Extreme paste here. Should I use that or the included EK paste?
Click to expand...

Iirc, the EK paste is GC Extreme so either way you are good.
 
thesmokingman said:
Iirc, the EK paste is GC Extreme so either way you are good.
Click to expand...

Ahh. I understand they they used to just drop a labeled GC Extreme tube in there, but the one I got had a EK label on it, without any details.

I didn't know if it was just a matter of branding the GC Extreme as their own, under agreement with the original manufacturer, or if they had actually changed it.
 
Armenius said:
Yes, the community has to do the work. People are having trouble dumping the Pitan BIOS, though. Once it's dumped users go to work analyzing the file to see what addresses map to what functionality.

There might be progress. A user posted an unsigned BIOS in the nvflash thread at Overclock and another user is analyzing it.

[Official] NVFlash with certificate checks bypassed for GTX 950/960/970/980/980Ti/Titan X - Page 70
Click to expand...

I wonder how long it typically takes before someone succeeds in getting BIOS modding to work for a new gen of cards...
 
Has anyone else had trouble with the 372.54 drivers?

After I completed my water loop, I upgraded to these using the GeForce Experience app. They seemed to work well, but when I tried to play Fallout New Vegas it kept crashing.

I figured, huh, maybe my drivers somehow had become corrupt, so I went to Geforce.com to manually download the drivers and reinstall, doing a clean install.

I saw a new section on their website for "Windows 10 Anniversary Update" so I used that section. The drivers kept failing to install though of some reason.

So I did some cleaning up, uninstalling all Nvidia components already installed. and wen to try the install again, still the driver install failed.

Immediately after - however - Windows auto detected the drivers and installed them for me again. After checking, I was now back on the 369.05 launch day drivers. I thought this was odd, but Fallout new Vegas runs fine with these drivers, so I think I'll keep them until I'm done playing it, or until the next driver release after 372.54 comes out.
 
I noticed when downloading the 372.54 drivers from Nvidia, there was the option to choose Windows 10 64bit or Windows 10 Anniversary update 64bit. I just used the standard drivers as I haven't updated to the anniversary version. Plays Witcher 3 fine so far.
 
I think they're both the same, both options regular and anniversary points to the same driver. Best practice is to use DDU safemode then new driver.
 
4RunnerTE said:
Hmm I placed an order in the AM on the east coast today...still pending...
Click to expand...
You got the Purchase confirmation email though, right? I got that virtually right away. Looks like they sent me the shipping confirmation email at 6:24 that day. So yeah, you're probably good.
 
thesmokingman said:
I think they're both the same, both options regular and anniversary points to the same driver. Best practice is to use DDU safemode then new driver.
Click to expand...

Yeah, I tried again today.

DDU in safe mode, followed by a reboot and installing 372.54 drivers results in a driver installation failed message.

If I go into the device manager, right click and manually point it at the 372.54 drivers it will install. After that I can run the Nvidia installer package again and it will install as well, but upon a reboot I'll have a code 43 error.

The 372.54 drivers are completely broken on my system. The only way I can get it to work is to go back to 369.05

The 369.05 drivers work perfectly.
 
Neon01 said:
You got the Purchase confirmation email though, right? I got that virtually right away. Looks like they sent me the shipping confirmation email at 6:24 that day. So yeah, you're probably good.
Click to expand...

Yup, got that email immediately. Hopefully a shipping confirmation tonight!
 
Zarathustra[H] said:
Yeah, I tried again today.

DDU in safe mode, followed by a reboot and installing 372.54 drivers results in a driver installation failed message.

If I go into the device manager, right click and manually point it at the 372.54 drivers it will install. After that I can run the Nvidia installer package again and it will install as well, but upon a reboot I'll have a code 43 error.

The 372.54 drivers are completely broken on my system. The only way I can get it to work is to go back to 369.05

The 369.05 drivers work perfectly.
Click to expand...

Well, it looks like I am far from the only one with trouble. They are up to 40 pages in no time in the 372.54 driver feedback thread over in the Nvidia forums.

Makes you wonder what has been going on. Their flawless drivers has been one of the biggest selling points for buying Nvidia products for a long time, but they seem to really be dropping the ball with Pascal. First the DPC Latency issues and now this abysmal driver release.

Almost makes you wonder if there is a new team developing drivers over at Nvidia or something.
 
Zarathustra[H] said:
Well, it looks like I am far from the only one with trouble. They are up to 40 pages in no time in the 372.54 driver feedback thread over in the Nvidia forums.

Makes you wonder what has been going on. Their flawless drivers has been one of the biggest selling points for buying Nvidia products for a long time, but they seem to really be dropping the ball with Pascal. First the DPC Latency issues and now this abysmal driver release.

Almost makes you wonder if there is a new team developing drivers over at Nvidia or something.
Click to expand...


372.54 are the first wddm 2.1 drivers so maybe that's why it's shoddy.

Yeah I feel there have been many driver issue recently
 
Finished my install.

Loop before I added the Titan X block:



Naked Titan X:



Leak testing. I actually had two leaks so I am REALLY glad I let this run for a couple of hours. I am going to redo my fittings with compression fittings next because two of my barb fittings are garbage. Don't ever use single-barb fittings, do not recommend.



Finished:



So my card before the waterblock was thermally limited and would hover around 1924MHz in game. In GTA V so far I'm running low 40s C and the card is around 2050MHz stable. Going for more now. Bear in mind these temps are with a single 360 radiator that is also cooling a 4770K.

Zarathustra[H], I forgot to check the exact clearance of the block to the PWM header, but it's basically zero. I don't see any way you could snake a wire to that header.
 
May need to up my radiator capacity. Temps are getting into the high 40s, but that's still worlds better than the stock cooler.
 
Ieldra said:
372.54 are the first wddm 2.1 drivers so maybe that's why it's shoddy.

Yeah I feel there have been many driver issue recently
Click to expand...

Knock on wood, 372.54 are working fine for me so far. I'm also coming from amd too, though that doesn't really matter.
 
That's high 40s Celsius lol. Unless your room is 113F...

Game stable so far @ 2088MHz, +260/+500, temps mid-upper 40s.
 
Rizen said:
May need to up my radiator capacity. Temps are getting into the high 40s, but that's still worlds better than the stock cooler.
Click to expand...

I noticed that you got your back plate. I pre-ordered mine a couple weeks back. When was the back plates suppose to ship? I though it was Aug 22nd.
 
Rizen said:
That's high 40s Celsius lol. Unless your room is 113F...

Game stable so far @ 2088MHz, +260/+500, temps mid-upper 40s.
Click to expand...

+260! Awesome. I'm only able to get mine to +175 stable in games, but that does end up giving me around 2063-2099 in games (though that occasionally drops below to around 2030). This new boost system is kinda crazy. I'm unable to get a steady clock speed no matter what I do.
 
Zarathustra[H] said:
I wonder how long it typically takes before someone succeeds in getting BIOS modding to work for a new gen of cards...
Click to expand...

There's increased difficulty this time around with Pascal because the bios's now require signing.

Additionally for the Titan XP, whereas the 1080 is open for AIBs to customise and thus have access to bios creation tools, the Titan XP is nvidia exclusive, so there's no need for any 3rd party to have access to tools to modify a Titan XP bios.

We only get these tools at all from leaks via AIBs.


So unless the situation changes, someone's gunna have to reverse engineer the XP bios. :coffee:
 
Creepin_D said:
I noticed that you got your back plate. I pre-ordered mine a couple weeks back. When was the back plates suppose to ship? I though it was Aug 22nd.
Click to expand...
They're shipping now it seems :) Mine shipped last Thursday.
 
Neon01 said:
+260! Awesome. I'm only able to get mine to +175 stable in games, but that does end up giving me around 2063-2099 in games (though that occasionally drops below to around 2030). This new boost system is kinda crazy. I'm unable to get a steady clock speed no matter what I do.
Click to expand...
Yeah we are at about the same actual in-game frequency. Playing Overwatch and GTA V last night for testing I was getting around 2076-2088 in game. I can get into games at 2114MHz but it's not 100% stable.
 
thesmokingman said:
I think they're both the same, both options regular and anniversary points to the same driver. Best practice is to use DDU safemode then new driver.
Click to expand...
As leldra said, the AU version of the driver is WDDM version 2.1, while the regular are still 2.0. Make sure you get the right version.
Zarathustra[H] said:
Yeah, I tried again today.

DDU in safe mode, followed by a reboot and installing 372.54 drivers results in a driver installation failed message.

If I go into the device manager, right click and manually point it at the 372.54 drivers it will install. After that I can run the Nvidia installer package again and it will install as well, but upon a reboot I'll have a code 43 error.

The 372.54 drivers are completely broken on my system. The only way I can get it to work is to go back to 369.05

The 369.05 drivers work perfectly.
Click to expand...
See above. I'm still on version 1511 of W10 and the new driver works fine when I did an inline upgrade through GeForce Experience.
 
Armenius said:
As leldra said, the AU version of the driver is WDDM version 2.1, while the regular are still 2.0. Make sure you get the right version.

See above. I'm still on version 1511 of W10 and the new driver works fine when I did an inline upgrade through GeForce Experience.
Click to expand...


I'm kind of embarrassed to admit that after doing this (computer building the [H] way) for 25 years I don't even know what WDDM is or what its significance is here.
 
I don't know if you guys already caught this, but I missed it...

From the overclock.net forums:

HaniWithAnI said:
Unwinder replied to me in the Afterburner support thread and confirmed that to enable Voltage offset in Afterburner for TITAN XP you just need to do the following:

You can add unofficial support for TITAN X via editing hardware profile (profiles .\VEN_10DE&DEV_....cfg) and adding the following lines to it:

[Settings]
VDDC_Generic_Detection = 1
Click to expand...

In my experience it doesn't do much as the TL/PL seems to be causing the card to choose a lower voltage regardless of offset (and despite me being under targets for both??? :S), so I end up at the same voltage as before under load. Will likely be most useful to those who have already performed shunt mod or watercooling. Will try it again once I have my hybrid applied, still haven't had the chance to fit it yet.
Click to expand...

This is in Afterburner 4.3.0 beta4 btw.

I have not tested this yet.

probably going to be power limited in a hurry, but it might help a little bit!
 
Zarathustra[H] said:
So, if WDDM 2.1 is mandatory for feature set 12_0 and 12_1, and this is th efirst driver that supports it, how have we been doing DX12 to date? :p
Click to expand...
Shader model 6.0 was added to the mandatory requirements for feature level 12_0 with the Anniversary Update and WDDM 2.1. All other requirements were supported in WDDM 2.0, which was shipped in W10 RTM. SM 6.0 just allows for parallel shader intrinsics.
 
Armenius said:
Shader model 6.0 was added to the mandatory requirements for feature level 12_0 with the Anniversary Update and WDDM 2.1. All other requirements were supported in WDDM 2.0, which was shipped in W10 RTM. SM 6.0 just allows for parallel shader intrinsics.
Click to expand...
Yeah SM exposes wavefront/warp wide intrinsics, a fitting companion for DX12
 
Zarathustra[H] said:
I don't know if you guys already caught this, but I missed it...

From the overclock.net forums:



This is in Afterburner 4.3.0 beta4 btw.

I have not tested this yet.

probably going to be power limited in a hurry, but it might help a little bit!
Click to expand...


Alright, so I followed these instructions with this addition:

open the file that looks like "VEN_10DE&DEV_....cfg" in the afterburner install directory -> profiles folder - you can open it in notepad

paste the following lines (as is, both of them) to the end of it then save. That's all.

[Settings]
VDDC_Generic_Detection = 1
Click to expand...

and it worked.

I now have a voltage slider that I can slide all the way to 100%.

Does this really mean +100% though? As in doubling the voltage? That would seem like it might fry it instantly?

upload_2016-8-23_16-45-13.png
 
Zarathustra[H] said:
Alright, so I followed these instructions with this addition:



and it worked.

I now have a voltage slider that I can slide all the way to 100%.

Does this really mean +100% though? As in doubling the voltage? That would seem like it might fry it instantly?

View attachment 6979
Click to expand...

No worries mate, 16nm finfet is good up to 3V ;)


(no it's not double :p)
it's 100% of the range, GPU boost defines a voltage range, and by setting +100% you are giving it all of the remaining headroom.

eg if standard voltage range caps out at 1060mV, the card may allow 1100mV maximum. If you set 50% it'll go up to 1080mV

6938834194_b152500b87_o1.png
 
You must log in or register to reply here.
Back
Top