NVIDIA GeForce driver 369.09

Discussion in 'Videocards - NVIDIA GeForce Drivers Section' started by maur0, Aug 4, 2016.

  1. maur0

    maur0 Master Guru

    Messages:
    935
    Likes Received:
    96
    GPU:
    point of view gtx 570 1gb
    Desktop (windows 10 aniversary update)

    x86 http://download.windowsupdate.com/c..._c87d10ee8e51eac64dd957b4a776d827a9874a76.cab

    x64 http://download.windowsupdate.com/c..._f44d993a4269ca64c6cbf10ab7ec27a0231161e1.cab

    [news] windows vista, 7, and 8.1 [64-bit] modded by me 13 day more new this driver, than the version of Windows 10
    http://uptobox.com/dx8lud6a68qb

    [​IMG]

    [Manufacturer]
    %NVIDIA_A% = NVIDIA_Devices,NTamd64.10.0,NTamd64.10.0...14310

    this driver support WDDM 2.1 for windows 10 build 14393.xx, but not support full directx12 for fermi users.

    HP OEM Quadro mobile

    x64 http://download.windowsupdate.com/c..._beb5f7b41fd717b08dbcc0aafa42f190d953a0b0.cab

    x86 http://download.windowsupdate.com/d..._7031db960713ba902295e38c5bed0eaf658fdf46.cab

    new driver branch: r369_04-3
     
    Last edited: Aug 10, 2016
  2. siriq

    siriq Guest

    Messages:
    794
    Likes Received:
    21
    GPU:
    Evga GTX 570 Classified
    I am going to sleep, so i won't test it :D
    BTW, the wddm 2.1 is for fix memory addressing issue. It is about virtual addressing thing with MS. It didn't work under wddm 2.0 fine because of 4KB vs 64KB addressing issue of nvidia hardware.

    Means less crash from now on Nvidia hardware than before with the same software.


    Just a bit of hint, Vulkan Fermi support has been cancelled because of this issue and Nvidia wasn't aware of it. Instead, they have released some sort of new update in Vulkan pr project press, with out Fermi. :banana:
    God bless NV software engineers :bang:

    https://msdn.microsoft.com/en-us/library/windows/hardware/dn894175(v=vs.85).aspx
    Article says, should work with : physical page size

    As mentioned previously the video memory manager supports two page sizes. System memory is always managed in 4KB pages, while memory segments may be managed at either 4KB or 64KB granularity as determined by the kernel mode driver. In the real word, 4KB isn't working with NV hardware. That is why came up with WDDM 2.1 .

    God bless anandtech, guru3d and other tech sites to be silent in this matter over a year :D


    Just to get this up , memory management is not really working with WDDM 2.0 with the current state of support from both MS and NV.

    So much of the truth from NV . This company tells you nothing if possible to keep it behind the doors.
     
    Last edited: Aug 4, 2016
  3. frcento

    frcento Guest

    Messages:
    29
    Likes Received:
    0
    GPU:
    560 SLI @ 1000MHz
  4. BangTail

    BangTail Guest

    Messages:
    3,568
    Likes Received:
    1,099
    GPU:
    EVGA 2080 Ti XC
    These broke "nvidiaProfileInspector" for me, anyone else?

    **EDIT**

    Strangely, this only affects 2 out of 4 PCs.

    It is definitely the driver as reverting gets rid of it.

    The only thing the 2 that won't run it have in common is that they are both SLI (disabling SLI does not alleviate it).

    Anyone know where NvidiaprofileInspector stores it's settings, I had a quick gander in the obvious locations but didn't see anything.
     
    Last edited: Aug 4, 2016

  5. redrumy3

    redrumy3 Master Guru

    Messages:
    456
    Likes Received:
    16
    GPU:
    Nvidia 3090 FE
    Lots of drivers \o/
    [​IMG]
     
  6. holystarlight

    holystarlight Master Guru

    Messages:
    792
    Likes Received:
    62
    GPU:
    Nvidia 4090

    Same for me, NvidiaprofileInspector crashes after few seconds, other than that driver seems good here
     
  7. jonaand

    jonaand Member Guru

    Messages:
    168
    Likes Received:
    2
    GPU:
    gtx 1080
    what is advantages about wdmi 2.1 vs wdmi 2.0
     
  8. CPC_RedDawn

    CPC_RedDawn Ancient Guru

    Messages:
    10,409
    Likes Received:
    3,077
    GPU:
    PNY RTX4090
    why such a huge difference in driver version?

    369.05
    [​IMG]

    369.09
    [​IMG]
     
  9. yosef019

    yosef019 Ancient Guru

    Messages:
    2,186
    Likes Received:
    17
    GPU:
    EVGA 1080 ti
    because its microsoft magic edited drivers now windows can see how much fps in games you have
     
  10. BangTail

    BangTail Guest

    Messages:
    3,568
    Likes Received:
    1,099
    GPU:
    EVGA 2080 Ti XC
    Ah, thanks for posting, good to know it's not just me :)

    Cheers!
     

  11. peppercute

    peppercute Guest

    Messages:
    459
    Likes Received:
    104
    GPU:
    Msi 2080Ti TRIO
    dr_rus, i told u abount new branch
    R369.09 (r369_04-3) / 21.21.13.6909 (8-1-2016)
     
  12. scaramonga

    scaramonga Master Guru

    Messages:
    236
    Likes Received:
    80
    GPU:
    RTX 3090 W/C
    [​IMG]
     
  13. Blackfyre

    Blackfyre Maha Guru

    Messages:
    1,385
    Likes Received:
    389
    GPU:
    RTX 3090
    For anyone interested:

    3DMark

    Firestrike & Timespy results are all within margins of error, identical/similar results. I try to maintain identical testing conditions too. They are 'greener' across 95% of the spectrum with the new driver (but within margins of error anyway), click on the links below for comparisons.

    Restart computer after leaving it for five minutes with no background activity, run 3DMark after restart, run Time Spy with DEMO, then wait 60 seconds after completion and run Fire Strike with DEMO.

    369.09 (LEFT) verses 368.95 (RIGHT)

    COMPARISON: FIRE STRIKE
    http://www.3dmark.com/compare/fs/9629941/fs/9603718

    COMPARISON: TIME SPY
    http://www.3dmark.com/compare/spy/207965/spy/201470
     
    Cilene likes this.
  14. LesserHellspawn

    LesserHellspawn Master Guru

    Messages:
    690
    Likes Received:
    32
    GPU:
    RTX 3080ti Eagle
    I'm extremely wary of new drivers at the moment, everything after 368.69 has given me grief.
     
  15. X7007

    X7007 Ancient Guru

    Messages:
    1,874
    Likes Received:
    72
    GPU:
    ZOTAC 4090 EXT AMP
    Yes nvidia inspector crashes while it scanning when u run it

    Anyone found a fix ?

    Code:
    Faulting application name: nvidiaProfileInspector.exe, version: 2.1.2.0, time stamp: 0x56fc37c8
    Faulting module name: KERNELBASE.dll, version: 10.0.14393.0, time stamp: 0x57899809
    Exception code: 0xe0434352
    Fault offset: 0x0000000000017788
    Faulting process id: 0x1274
    Faulting application start time: 0x01d1ee273d5c13ed
    Faulting application path: C:\Users\x7007\Desktop\1\NV-Inspector\nvidiaProfileInspector.exe
    Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
    Report Id: c8cff6b4-7de8-4087-9dd4-01501caca684
    Faulting package full name: 
    Faulting package-relative application ID:
    
    
    
    
    Application: nvidiaProfileInspector.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an unhandled exception.
    Exception Info: System.IO.FileNotFoundException
       at System.IO.__Error.WinIOError(Int32, System.String)
       at System.IO.FileStream.Init(System.String, System.IO.FileMode, System.IO.FileAccess, Int32, Boolean, System.IO.FileShare, Int32, System.IO.FileOptions, SECURITY_ATTRIBUTES, System.String, Boolean, Boolean, Boolean)
       at System.IO.FileStream..ctor(System.String, System.IO.FileMode, System.IO.FileAccess, System.IO.FileShare, Int32, System.IO.FileOptions, System.String, Boolean, Boolean, Boolean)
       at System.IO.File.InternalReadAllBytes(System.String, Boolean)
       at nspector.Common.Meta.NvD3dUmxSettingMetaService.ParseNvD3dUmxNames(System.String)
       at nspector.Common.Meta.NvD3dUmxSettingMetaService..ctor()
       at nspector.Common.DrsSettingsMetaService.ResetMetaCache(Boolean)
       at nspector.frmDrvSettings.frmDrvSettings_OnScanDoneDoNothing()
       at nspector.Common.DrsScannerService.ScanForModifiedProfiles()
       at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
       at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
       at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
       at System.Threading.ThreadHelper.ThreadStart()
    
     
    Last edited: Aug 4, 2016

  16. Prophet

    Prophet Master Guru

    Messages:
    865
    Likes Received:
    34
    GPU:
    Msi 680
    Hows dpc in game. If you check, please check dpc whille the pc is completely idle, while having shut down all programs.
     
  17. khanmein

    khanmein Guest

    Messages:
    1,646
    Likes Received:
    72
    GPU:
    EVGA GTX 1070 SC
    did u tried to use latest Microsoft .Net Framework?
     
  18. mbk1969

    mbk1969 Ancient Guru

    Messages:
    15,536
    Likes Received:
    13,556
    GPU:
    GF RTX 4070
    System.IO.FileNotFoundException - some file was not found. You can spy after inspector program with Procmon.exe (from SysInternal suit) for a file operations to reveal which file is not found.
     
  19. Fifka

    Fifka Active Member

    Messages:
    62
    Likes Received:
    3
    GPU:
    Gigabyte RTX 2080OC
    Is anniversary update required for WDDM 2.1 to work ?
     
  20. khanmein

    khanmein Guest

    Messages:
    1,646
    Likes Received:
    72
    GPU:
    EVGA GTX 1070 SC
    if no mistake no need. y don't u try yourself?
     

Share This Page