Discussion in 'Videocards - NVIDIA GeForce Drivers Section' started by Cyris, May 16, 2015.
Process Explorer seem to be detecting video memory properly.
Look up paragraphs on wikipedia. That was like diahorrea in text form
In English, please.
Since i Installed W10x64 early version till now ALL Games where Perfect Smooth Specially on Build 10074 + 352.63 Drivers. Today i download these ones and OMG they suck bad, stutter lag heaven...I re did to see if it was true and not some error and same. I went back to the old version and smooth as always.
Anyone had this experience ?
Btw this are the games NONE Stutters or lag like in W7 or W8.1, not till this Driver release on W10
Holy **** so many games, shame on you have Borderlands 2 but no pre sequal
For some reason, Starcraft II fps is locked to your refresh rate, 120 at my case like Vsync is on all the time, no matter if i disable it completely from NVIDIA control panel, from the game itself or make FPS limit via afterburner.
GeForce DirectX 12 Drivers for Windows 10 Now WHQL-Certified
As the launch of Windows 10 and DirectX 12 nears, our GeForce drivers have taken a major step forward: WHQL certification has arrived.
It’s no small task. Next to the operating system, the graphics driver is one of the most complex pieces of code on a PC.
We worked closely with Microsoft to develop the new DX12 standard. And that effort has paid off with day-one WHQL certification.
Plus, our Maxwell and Kepler GPU architectures already support DX12, with support for Fermi coming later.
You can modify the installer file and try the driver with older OS, but you will end up with error code 39
Windows cannot load the device driver for this hardware. The driver may be corrupted or missing. (Code 39)
There are several causes of Code 39 errors:
A required device driver is missing.
A required binary file is corrupted.
There is a problem with the file I/O process.
A driver that is referencing an entry point in another binary file is unable to load.
Here is some info from MSDN what has changed under the hood:
The display driver model from Windows 8.1 and Windows Phone have converged into a unified model for Windows 10 Insider Preview.
A new memory model is implemented that gives each GPU a per-process virtual address space. Direct addressing of video memory is still supported by WDDMv2 for graphics hardware that requires it, but that is considered a legacy case. IHVs are expected to develop new hardware that supports virtual addressing. Significant changes have been made to the DDI to enable this new memory model.
DX12 / WDMM 2.0 functions in the new kernel mode driver nvlddmkm2.sys
Also: CUDA runtime reads version 7.5.8 - so get ready for the next CUDA toolkit
-D__CUDA_ARCH__=300 -D__CUDA_ARCH__=350 -D__CUDA_ARCH__=370
-D__CUDA_ARCH__=500 -D__CUDA_ARCH__=520 -D__CUDA_ARCH__=530
« Last Edit: May 16, 2015, 07:25:48 AM by Stefan »
More often than not pressing the windows start button would crash the driver (and most of the time my screens would go blank and only a system reset would sort it)
But I've updated and it's stopped doing that now.
I'm glad, because that was getting very annoying.
Where did you hear about WDDM 3.0? :3eyes: From the future?
Yeah that's a big list, I have ~ 120 games installed as well
That's why I always have certain expectations with new drivers, I don't want 1/5 of my games to have issues..
I actually have around 500 or so games installed.
people ask me what I do with my time............
I want to ask something.
when it is stuttering for you guys. is the hdd getting thrashed while it stuttering?
I been doing some testing and seems that there is some streaming issue related to memory.
I was testing dying light at 4k and the hdd was being thrashed* each time the game stuttered. and couple times the game came to a complete halt until the thrashing* on the drive stopped.
Im unable to run wolfenstein old blood at 4k in with these driver and other windows 10 drivers.
it gives opengl memory error.
I can run the game in windows 8.1 at 4k and there is no problem.
*I dont know what word to actually use. so I used thrashing
There is a driver mod that adds Fermi support - however, it turns the driver into an unsigned driver (which Windows 10 will disallow by default). Also, installing the modified driver breaks GFE tweak support. I have installed the modified driver for my GTX550Ti (Fermi) - however, it does NOT expose any DX12 level support in Fermi just yet.
Lastly, there is the issue of the price of properly-supported GPUs (Kepler and even Maxwell) - Kepler and Maxwell now overlap at the $100USD price point - and I'm talking new (not refurbs) and retail - not e-tail. What is it worth for nVidia to commit to supporting DX12 on Fermi (just from a price standpoint)?
There Is A Way
Do you have the modded .INF file?
If so, after replacing the standard .INF with the modded one, you have to reboot into Advanced Mode AND disable driver signing (option 7) prior to installing the modded driver. Then, reboot into normal mode.
If my information is correct, not all NV-Series get DirectX 12 as their functional level. It is possible that some get only the DX11.3 feature.
Why Are We Stalling?
I could of swore that one time when using different dx 12 drivers that it showed 12 feature level for my card.
also dxdiag only shows feature level going to 11.0
Fermi and Kepler are supposedly similar, so much of the DX12 codebase will probably be shared. If that's the case, it's probably not that expensive and hard for Nvidia to support DX12 for Fermi as well.
Marketing wise, Nvidia gets good credit by supporting DX12 on its three latest architectures. And for developers, having DX12 support on Fermi will increase the DX12 userbase from day one.
I'm having a problem with those drivers on win10. Everytime I restart windows the nvidia driver stops working, reporting this error: (Code 43: Windows has stopped this device because it has reported problems)
A fix is to disable the driver, then enable it again, then everything works fine until the next reboot.
I've tried to do clean installs using DDU, but nothing seems to fix it. Does any of you guys saw this issue before?
Carfax convince me to installed windows 10 build 10074. System work perfectly well except that some apps are not compatibles like my Kaspersky anti virus. Had to purchased one that was compatible
Umm,its a windows 10 driver. Thus why they call it a win 10 driver. Sheesh.