I will find the other thread for you. I know there is already one out with a lot of information in it, on this topic. I am not sure anyone has actually been able to fully test this yet, but this will cut down on repeat threads.

This is from mobile, so it may not click properly: http://forums.evga.com/m/tm.aspx?m=2310062&p=4

If not, just look up (search) Titan X system requirements

The actual titan box says 2 gb ram required, 4 or more recommended.

Scarlet-Tech

ARMYguy
The actual titan box says 2 gb ram required, 4 or more recommended.

That was discussed as well, that Nvidia misprints it in the book, not in the system requirement. It is 24-48 as stated on their site, which is ridiculous, but not to be worried about anyway.

I guess nobody will be running this GPU on Win7 32bit eh?

Me, including many others, have spoken NUMEROUS times to NVidia regarding this issue as we didn't believe it as well (you can ask them yourself if you want) and they keep saying the same thing: 24GB minimum is REQUIRED for the card to run STABLE and for you to be able to utilize its 12GB VRAM. Right from the horses mouth guys. Unless they confirm otherwise, looks like that is the case.
 
Edit: YES I have seen systems run it with 16GB RAM before anyone tells me that again. But NVidia is receiving a lot of calls from Titan X owners who state that their GPU is only able to use 4GB rather than 12GB advertised. 

Sajin

TonyMartinStark
Me, including many others, have spoken NUMEROUS times to NVidia regarding this issue as we didn't believe it as well (you can ask them yourself if you want) and they keep saying the same thing: 24GB minimum is REQUIRED for the card to run STABLE and for you to be able to utilize its 12GB VRAM. Right from the horses mouth guys. Unless they confirm otherwise, looks like that is the case.
 
Edit: YES I have seen systems run it with 16GB RAM before anyone tells me that again. But NVidia is receiving a lot of calls from Titan X owners who state that their GPU is only able to use 4GB rather than 12GB advertised. 

http://forums.evga.com/FindPost/2313353

?

Sajin

TonyMartinStark

Sajin

TonyMartinStark
Me, including many others, have spoken NUMEROUS times to NVidia regarding this issue as we didn't believe it as well (you can ask them yourself if you want) and they keep saying the same thing: 24GB minimum is REQUIRED for the card to run STABLE and for you to be able to utilize its 12GB VRAM. Right from the horses mouth guys. Unless they confirm otherwise, looks like that is the case.
 
Edit: YES I have seen systems run it with 16GB RAM before anyone tells me that again. But NVidia is receiving a lot of calls from Titan X owners who state that their GPU is only able to use 4GB rather than 12GB advertised. 

http://forums.evga.com/FindPost/2313353

?

You can clearly allocate above 4GB of VRAM with only 16GB of system ram installed.

Did you tell NVidia that? I didn't do my own tests since I'm still waiting for the Titan. I simply relay what I'm told to you and others.

TonyMartinStark

Sajin

TonyMartinStark

Sajin

TonyMartinStark
Me, including many others, have spoken NUMEROUS times to NVidia regarding this issue as we didn't believe it as well (you can ask them yourself if you want) and they keep saying the same thing: 24GB minimum is REQUIRED for the card to run STABLE and for you to be able to utilize its 12GB VRAM. Right from the horses mouth guys. Unless they confirm otherwise, looks like that is the case.
 
Edit: YES I have seen systems run it with 16GB RAM before anyone tells me that again. But NVidia is receiving a lot of calls from Titan X owners who state that their GPU is only able to use 4GB rather than 12GB advertised. 

http://forums.evga.com/FindPost/2313353

?

You can clearly allocate above 4GB of VRAM with only 16GB of system ram installed.

Did you tell NVidia that? I didn't do my own tests since I'm still waiting for the Titan. I simply relay what I'm told to you and others.

In that same thread I forgot to mention that not only was my Titan allocating over 4GB VRAM just fine using EVGA OC Scanner, but I only have 8GB RAM installed. So....something is not being communicated clearly enough on Nvidia's end. Unless they're specifically saying if it uses up all 12GB VRAM then you need 24+GB RAM to run stable, which I agree.   

TonyMartinStark
 
Something is just not right and I'm balding thinking about it. I'm on the verge of ordering more RAM and upgrading windows. Also, I told them specifically regarding whether we need more RAM only once we exceed VRAM and she/he/it told me "NO!" The card simply needs a minimum of 24GB to utilize all VRAM and run stable over time.

 By any chance, do you have a link/image of that conversation/thread? 

I just spoke with Nvidia chat.  I got the same answers. Quote "We are not really sure how the people are managing to get it work on 16 GB PC because the card itself is a 12 GB card. With 16 GB card, they might be able to run the card but in future, they will face performance issues. The minimum requirement is atleast 24 GB" 
 
I then asked what kind of issues and got "They might face stuttering, lag , tearing or eventually, the card may stopped working."

The card may stop working? How?... not sure how much trust I'm putting into chat reps. I have had zero issues fully utilizing the cards.

To All,
 
I believe what the Nvidia reps are saying is true but they're not explaining this properly so that most can understand. The topic actually has nothing to do so much w/ the TitanX or system mem per se, this issue stems from the Windows OS itself. It's old coding algorithm within Windows that was written years ago (all the way back to Win 3.x days) to address graphics frame buffering conflicts on limited mem systems. Graphics cards back then didn't have the amounts of mem like today & that mem was VERY EXPENSIVE back in them days so the OS was coded to 1st allocate the "amount" of graphics mem into system mem to use as a "swap file" to essentially "double" the amount of "available" mem for graphics frame buffering as system mem is the next faster medium in relation to graphics mem frequencies (speed) to minimize the performance impact caused between the 2 mem frequencies (speed, not capacity here) & if there's not enough available system mem to do this the OS will then create the swap file on the HDD to get the necessary amount of "space" for the swap file to mirror the amount of graphics mem for graphics frame buffering purposes. The stuttering that they're talking about will occur when the onboard graphics card's frame buffers (mem) becomes full then the OS will allow the GPU to start storing extra rendered graphics frames on the system mem "swap file" to prevent the GPU from having to stop rendering graphics frames until the actual frames are ready to be drawn (flipped) to the monitor. Since system mem runs slower than graphic card mem any frames that are flipped from the system mem buffer will move slower thus creating a slight pause in frame sequencing to the monitor which is called stuttering. If the graphics mem buffer & system mem swap file buffer fills up then the OS will allow the GPU to start sending rendered graphics frames to the created HDD swap file to store rendered graphics frames on the HDD's allocated extra unused space until the graphics frame is called to be drawn to the monitor & since the HDD spins even slower than system mem which is slower than onboard graphics mem the potential for stuttering can get exponentially worse & if this gets too erratic for all to mesh well enough the OS will usually call out a page fault & shut the system down to try to prevent a meltdown, usually due to some part of the system (mostly the CPU & mem) becoming unstable due to overload.
Now bring all this into today........ Yes a lot of things have changed over the years but this old coding has been carried forward in successive vers of Windows & is still being used in the OS as some computer manufacturers/users will STILL under equip a system, mostly due to cost constraints, so the graphics cards of today, even though they have massive amounts of onboard mem still have to follow this coding algorithm within the Windows OS to be in compliance w/ the OS & operate on it.........& yes this will be the case w/ Win 10 as well.
Will the cards work if a computer doesn't have enough available system mem to create the necessary "swap file" that will "double" the available mem available for the graphics frame buffer? Yes they will as I just demonstrated what will happen....the "swap file" will be created on the HDD(s) if there is enough free disk space to do it. Will the cards still work if a computer doesn't have enough available system mem or enough available HDD space....Nope. The OS will call out a page fault at that time & shut the computer down as this is outside of the OS coding compliance. With today's computers most users will have far more than enough HDD free space as opposed to extra available system mem so the shutdown call will most likely never come BUT the graphics sequencing will suck BIG TIME to the point that the game\app will be practically unplayable\usable. You DO NOT want to get here, trust me. But please stop blaming this issue on Nvidia......blame this on MS WINDOWS! And since the overwhelming market share for Microsoft is catering to businesses who are the MAJOR users to under equip a computer so MS ain't gonna change\remove this algorithm any time soon so you can also blame your place of employment for this as well.....let's see how far you get doing that...........just saying..................
 
Since the TitanX is equipped w/ 12 Gb of onboard graphics mem the OS will want to find 12 Gb of available addressable system mem to build the "swap buffer file" to comply w/ it's coding structure as stuttering will be much less here. Add the 2 together (12Gb + 12Gb) you will get the 24Gb that the reps are telling you. Since system mem is used by the CPU as well as other devices then you would in practice "need" more than 12Gb of system mem to accommodate all this so the rule of thumb is to "double" the "double" so add 24Gb to 24Gb you will get 48Gb which is what they're saying as recommended.
 
If you get all this then there are some things that you could do to lessen the stuttering effect but you will need to upgrade some equipment. If your mobo will support faster mem modules than what you're currently using then upgrade them as this will close the speed difference between the 2 mem thus lessen the stuttering effects. If not then you may consider to upgrade the whole mobo\system to get a faster subsystem along w/ faster mem modules to mitigate this. Use SSD's instead of HDD's to do the same thing if the buffer is made on the drive, up to installing a purpose fast PCI-E SSD to take advantage of the wider & faster PCI-E lanes over the SATA bus to lessen this as well, but the best thing to do is to make sure that the games\apps you play\use don't need more than 12Gb graphics frame buffer then no issue per se, but the OS is STILL going to create the extra graphics frame buffer where it can. This is going to occur regardless so I would suggest to get used to it & understand what your options are as griping about this ain't gonna change anything............this is a fact, folks. Windows OS 101..............
 
BTW, as already stated earlier in this thread you can forget trying to use this card on a Windows 32-bit system as that system can address only 4Gb mem TOTAL (system mem + graphics mem) so the majority of the vid card's 12Gb will be useless & you will most surely have issues running this card on this system. If you weren't planning to upgrade your OS then don't buy this card. You will need to be using a Windows 64-bit OS to properly address this mem & going by what the reps are saying you will need to be using Windows Pro vers OS at a minimum as Pro vers will address up to 192GB total mem so the swap file can be properly handled as long as the mobo that you have can use 32Gb or more mem.....Windows Home vers OS can only address up to 16Gb total mem. You have been warned.............
 
You will need to learn\know where your shortcomings are to know what to do\where your options are and\or your willingness to do what is necessary to comply fully to determine if this card is for you............just saying........
 
Don't shoot the messenger here. I just read a lot of misinformation being posted here & just trying to help folks understand WHY the reps are saying what they're saying.
 
<salute>
 
 

flyhii
To All,
 
I believe what the Nvidia reps are saying is true but they're not explaining this properly so that most can understand. The topic actually has nothing to do so much w/ the TitanX or system mem per se, this issue stems from the Windows OS itself. It's old coding algorithm within Windows that was written years ago (all the way back to Win 3.x days) to address graphics frame buffering conflicts on limited mem systems. Graphics cards back then didn't have the amounts of mem like today & that mem was VERY EXPENSIVE back in them days so the OS was coded to 1st allocate the "amount" of graphics mem into system mem to use as a "swap file" to essentially "double" the amount of "available" mem for graphics frame buffering as system mem is the next faster medium in relation to graphics mem frequencies (speed) to minimize the performance impact caused between the 2 mem frequencies (speed, not capacity here) & if there's not enough available system mem to do this the OS will then create the swap file on the HDD to get the necessary amount of "space" for the swap file to mirror the amount of graphics mem for graphics frame buffering purposes. The stuttering that they're talking about will occur when the onboard graphics card's frame buffers (mem) becomes full then the OS will allow the GPU to start storing extra rendered graphics frames on the system mem "swap file" to prevent the GPU from having to stop rendering graphics frames until the actual frames are ready to be drawn (flipped) to the monitor. Since system mem runs slower than graphic card mem any frames that are flipped from the system mem buffer will move slower thus creating a slight pause in frame sequencing to the monitor which is called stuttering. If the graphics mem buffer & system mem swap file buffer fills up then the OS will allow the GPU to start sending rendered graphics frames to the created HDD swap file to store rendered graphics frames on the HDD's allocated extra unused space until the graphics frame is called to be drawn to the monitor & since the HDD spins even slower than system mem which is slower than onboard graphics mem the potential for stuttering can get exponentially worse & if this gets too erratic for all to mesh well enough the OS will usually call out a page fault & shut the system down to try to prevent a meltdown, usually due to some part of the system (mostly the CPU & mem) becoming unstable due to overload.
Now bring all this into today........ Yes a lot of things have changed over the years but this old coding has been carried forward in successive vers of Windows & is still being used in the OS as some computer manufacturers/users will STILL under equip a system, mostly due to cost constraints, so the graphics cards of today, even though they have massive amounts of onboard mem still have to follow this coding algorithm within the Windows OS to be in compliance w/ the OS & operate on it.........& yes this will be the case w/ Win 10 as well.
Will the cards work if a computer doesn't have enough available system mem to create the necessary "swap file" that will "double" the available mem available for the graphics frame buffer? Yes they will as I just demonstrated what will happen....the "swap file" will be created on the HDD(s) if there is enough free disk space to do it. Will the cards still work if a computer doesn't have enough available system mem or enough available HDD space....Nope. The OS will call out a page fault at that time & shut the computer down as this is outside of the OS coding compliance. With today's computers most users will have far more than enough HDD free space as opposed to extra available system mem so the shutdown call will most likely never come BUT the graphics sequencing will suck BIG TIME to the point that the game\app will be practically unplayable\usable. You DO NOT want to get here, trust me. But please stop blaming this issue on Nvidia......blame this on MS WINDOWS! And since the overwhelming market share for Microsoft is catering to businesses who are the MAJOR users to under equip a computer so MS ain't gonna change\remove this algorithm any time soon so you can also blame your place of employment for this as well.....let's see how far you get doing that...........just saying..................
 
Since the TitanX is equipped w/ 12 Gb of onboard graphics mem the OS will want to find 12 Gb of available addressable system mem to build the "swap buffer file" to comply w/ it's coding structure as stuttering will be much less here. Add the 2 together (12Gb + 12Gb) you will get the 24Gb that the reps are telling you. Since system mem is used by the CPU as well as other devices then you would in practice "need" more than 12Gb of system mem to accommodate all this so the rule of thumb is to "double" the "double" so add 24Gb to 24Gb you will get 48Gb which is what they're saying as recommended.
 
If you get all this then there are some things that you could do to lessen the stuttering effect but you will need to upgrade some equipment. If your mobo will support faster mem modules than what you're currently using then upgrade them as this will close the speed difference between the 2 mem thus lessen the stuttering effects. If not then you may consider to upgrade the whole mobo\system to get a faster subsystem along w/ faster mem modules to mitigate this. Use SSD's instead of HDD's to do the same thing if the buffer is made on the drive, up to installing a purpose fast PCI-E SSD to take advantage of the wider & faster PCI-E lanes over the SATA bus to lessen this as well, but the best thing to do is to make sure that the games\apps you play\use don't need more than 12Gb graphics frame buffer then no issue per se, but the OS is STILL going to create the extra graphics frame buffer where it can. This is going to occur regardless so I would suggest to get used to it & understand what your options are as griping about this ain't gonna change anything............this is a fact, folks. Windows OS 101..............
 
BTW, as already stated earlier in this thread you can forget trying to use this card on a Windows 32-bit system as that system can address only 4Gb mem TOTAL (system mem + graphics mem) so the majority of the vid card's 12Gb will be useless & you will most surely have issues running this card on this system. If you weren't planning to upgrade your OS then don't buy this card. You will need to be using a Windows 64-bit OS to properly address this mem & going by what the reps are saying you will need to be using Windows Pro vers OS at a minimum as Pro vers will address up to 192GB total mem so the swap file can be properly handled as long as the mobo that you have can use 32Gb or more mem.....Windows Home vers OS can only address up to 16Gb total mem. You have been warned.............
 
You will need to learn\know where your shortcomings are to know what to do\where your options are and\or your willingness to do what is necessary to comply fully to determine if this card is for you............just saying........
 
Don't shoot the messenger here. I just read a lot of misinformation being posted here & just trying to help folks understand WHY the reps are saying what they're saying.
 
<salute>
 
 

Quite a good explanation! Although, as i recall, nobody blames nvidia. They just blame the confusion in information. Ill know for myself in a week. Cant wait

TonyMartinStark
Just wondering but, does anyone have a clue as to when the Superclocked Titan X will be available? I might have missed it.

It's available now, but it's like all the other Titan X's that are hot commodity right now.

TonyMartinStark

AnonymousGuy

TonyMartinStark
Just wondering but, does anyone have a clue as to when the Superclocked Titan X will be available? I might have missed it.

It's available now, but it's like all the other Titan X's that are hot commodity right now.

Wait a minute, you can actually BUY it now? All it shows for me is "Auto Notify". Been like that for daaaayyyyysssssssssss man.

Yep, there's people that already have the SC's.  Personally I wouldn't wait specifically for that card since you'll be able to get the same + better overclock with a vanilla card.  If you don't want to bother overclocking you can flash the SC bios to a vanilla card.

TonyMartinStark

AnonymousGuy

TonyMartinStark

AnonymousGuy

TonyMartinStark
Just wondering but, does anyone have a clue as to when the Superclocked Titan X will be available? I might have missed it.

It's available now, but it's like all the other Titan X's that are hot commodity right now.

Wait a minute, you can actually BUY it now? All it shows for me is "Auto Notify". Been like that for daaaayyyyysssssssssss man.

Yep, there's people that already have the SC's.  Personally I wouldn't wait specifically for that card since you'll be able to get the same + better overclock with a vanilla card.  If you don't want to bother overclocking you can flash the SC bios to a vanilla card.

But NONE of the Titan X's are available. All show the god damn "Auto notify" button I've pressed a million times hoping for a miracle. NONE at NewEgg, NONE at EVGA. I think Nvidia has it buy only the basic version. Also I don't know how to do any of what you mention man. (Flashing & overclocking).

Probably we're in a lull right now where their initial production of Titan X's from Taiwan / China have sold and they're waiting for the next plane / boat to restock all the distributors.  Asus has vanilla ones for sale too on Newegg, but EVGA has a better warranty.
 
Overclocking is dead easy.  Most of the Titan X reviews have an "Overclocking" section that shows their settings.  Read any overclocking guide for any recent NV cards and you know how the process goes.  The SC is basically a vanilla card + 127 Mhz on the core clock and +0 on the memory.  Pretty yawn-worthy.  I'm sitting at +250 core and +550 memory.