Download & Discuss Geforce Driver 361.43 WHQL

Discussion in 'Videocards - NVIDIA GeForce Drivers Section' started by alanm, Dec 21, 2015.

  1. usoldier

    usoldier Member

    Messages:
    41
    Likes Received:
    1
    GPU:
    Asus 970 Strix OC
    I dont know if its this drivers but witcher 3 closes to desktop with no error :(

    Last set of drivers was causing H1Z1 to close to desktop seams to be fixed with this new drivers.

    Any idea what i should try to stop witcher 3 closing to desktop?
     
  2. Darren Hodgson

    Darren Hodgson Ancient Guru

    Messages:
    15,838
    Likes Received:
    387
    GPU:
    EVGA GTX 1080 Ti SC2
    Will do. Thank you, Wagnard. That is most kind of you.

    All the best.
     
  3. Darren Hodgson

    Darren Hodgson Ancient Guru

    Messages:
    15,838
    Likes Received:
    387
    GPU:
    EVGA GTX 1080 Ti SC2
    Yes, I have uninstalled the Dell Display Manager but the same BSODs still occur in the same games and applications... unfortunately. :(

    I have reverted back to the v359.06 drivers using DDU to a 100% clean install and I can now set Kerbal Space Program's AA from 2x to 8x without it BSODing. With the v361.43 drivers it will always BSOD when changing that setting and hitting Apply.

    Seems the v359.06 is just more stable for me on my system for games. v361.43 is like Russian Roulette with most games seemingly working fine but specific others such as Legend of Eisenwald and Pillars of Eternity causing instant BSODs just on loading them.

    Really weird behaviour to be honest. I have never ever had a driver this crash-prone on my system.
     
  4. PapaJohn

    PapaJohn Member Guru

    Messages:
    175
    Likes Received:
    8
    GPU:
    GTX 970
    As I did, which is why I started a thread on this very forum, but no one provided any meaningful help unfortunately. For some reason, these drivers just seem to work for my setup.....I'm not complaining :)
     

  5. Darren Hodgson

    Darren Hodgson Ancient Guru

    Messages:
    15,838
    Likes Received:
    387
    GPU:
    EVGA GTX 1080 Ti SC2
    This the report that WhoCrashed v5.51 shows:

    On Thu 24 Dec 2015 9:17:23 am GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\122415-20062-01.dmp
    This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x11E18D)
    Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8012F6DE18D, 0xFFFFD00022205F28, 0xFFFFD00022205740)
    Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
    file path: C:\WINDOWS\system32\drivers\nvlddmkm.sys
    product: NVIDIA Windows Kernel Mode Driver, Version 359.06
    company: NVIDIA Corporation
    description: NVIDIA Windows Kernel Mode Driver, Version 359.06
    Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 359.06 , NVIDIA Corporation).
    Google query: NVIDIA Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



    On Wed 23 Dec 2015 7:38:08 pm GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\122315-21843-01.dmp
    This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x11E18D)
    Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80058ECE18D, 0xFFFFD000A9733F28, 0xFFFFD000A9733740)
    Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
    file path: C:\WINDOWS\system32\drivers\nvlddmkm.sys
    product: NVIDIA Windows Kernel Mode Driver, Version 359.06
    company: NVIDIA Corporation
    description: NVIDIA Windows Kernel Mode Driver, Version 359.06
    Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 359.06 , NVIDIA Corporation).
    Google query: NVIDIA Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



    On Wed 23 Dec 2015 7:10:50 pm GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\122315-19562-01.dmp
    This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x11E18D)
    Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80060CDE18D, 0xFFFFD000272ACF28, 0xFFFFD000272AC740)
    Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
    file path: C:\WINDOWS\system32\drivers\nvlddmkm.sys
    product: NVIDIA Windows Kernel Mode Driver, Version 359.06
    company: NVIDIA Corporation
    description: NVIDIA Windows Kernel Mode Driver, Version 359.06
    Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 359.06 , NVIDIA Corporation).
    Google query: NVIDIA Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



    On Tue 22 Dec 2015 7:57:43 am GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\122215-24468-01.dmp
    This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x11E18D)
    Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800CC87E18D, 0xFFFFD00027294F28, 0xFFFFD00027294740)
    Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
    file path: C:\WINDOWS\system32\drivers\nvlddmkm.sys
    product: NVIDIA Windows Kernel Mode Driver, Version 359.06
    company: NVIDIA Corporation
    description: NVIDIA Windows Kernel Mode Driver, Version 359.06
    Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 359.06 , NVIDIA Corporation).
    Google query: NVIDIA Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



    On Tue 22 Dec 2015 7:22:45 am GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\122215-19781-01.dmp
    This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x11E18D)
    Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF801CA1DE18D, 0xFFFFD00025AACF28, 0xFFFFD00025AAC740)
    Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
    file path: C:\WINDOWS\system32\drivers\nvlddmkm.sys
    product: NVIDIA Windows Kernel Mode Driver, Version 359.06
    company: NVIDIA Corporation
    description: NVIDIA Windows Kernel Mode Driver, Version 359.06
    Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 359.06 , NVIDIA Corporation).
    Google query: NVIDIA Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



    On Tue 22 Dec 2015 12:46:08 am GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\122215-21093-01.dmp
    This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x11E18D)
    Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800ED1BE18D, 0xFFFFD000489AAF28, 0xFFFFD000489AA740)
    Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
    file path: C:\WINDOWS\system32\drivers\nvlddmkm.sys
    product: NVIDIA Windows Kernel Mode Driver, Version 359.06
    company: NVIDIA Corporation
    description: NVIDIA Windows Kernel Mode Driver, Version 359.06
    Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 359.06 , NVIDIA Corporation).
    Google query: NVIDIA Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



    On Mon 21 Dec 2015 11:55:01 pm GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\122115-19718-01.dmp
    This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x11E18D)
    Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF801272EE18D, 0xFFFFD000249ECF28, 0xFFFFD000249EC740)
    Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
    file path: C:\WINDOWS\system32\drivers\nvlddmkm.sys
    product: NVIDIA Windows Kernel Mode Driver, Version 359.06
    company: NVIDIA Corporation
    description: NVIDIA Windows Kernel Mode Driver, Version 359.06
    Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 359.06 , NVIDIA Corporation).
    Google query: NVIDIA Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



    On Mon 21 Dec 2015 11:40:47 pm GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\122115-21515-01.dmp
    This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x11E18D)
    Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF801D77AE18D, 0xFFFFD0015E511F28, 0xFFFFD0015E511740)
    Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
    file path: C:\WINDOWS\system32\drivers\nvlddmkm.sys
    product: NVIDIA Windows Kernel Mode Driver, Version 359.06
    company: NVIDIA Corporation
    description: NVIDIA Windows Kernel Mode Driver, Version 359.06
    Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 359.06 , NVIDIA Corporation).
    Google query: NVIDIA Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



    On Mon 21 Dec 2015 10:45:16 pm GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\122115-19562-01.dmp
    This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x11E18D)
    Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800BBFFE18D, 0xFFFFD000205B9F28, 0xFFFFD000205B9740)
    Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
    file path: C:\WINDOWS\system32\drivers\nvlddmkm.sys
    product: NVIDIA Windows Kernel Mode Driver, Version 359.06
    company: NVIDIA Corporation
    description: NVIDIA Windows Kernel Mode Driver, Version 359.06
    Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 359.06 , NVIDIA Corporation).
    Google query: NVIDIA Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



    On Mon 21 Dec 2015 10:40:41 pm GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\122115-20656-01.dmp
    This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x11E18D)
    Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80125CAE18D, 0xFFFFD000274D7F28, 0xFFFFD000274D7740)
    Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
    file path: C:\WINDOWS\system32\drivers\nvlddmkm.sys
    product: NVIDIA Windows Kernel Mode Driver, Version 359.06
    company: NVIDIA Corporation
    description: NVIDIA Windows Kernel Mode Driver, Version 359.06
    Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 359.06 , NVIDIA Corporation).
    Google query: NVIDIA Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M





    --------------------------------------------------------------------------------
    Conclusion
    --------------------------------------------------------------------------------

    10 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

    nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 359.06 , NVIDIA Corporation)

    If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.


    Read the topic general suggestions for troubleshooting system crashes for more information.

    Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

    The really strange thing about that report is that all but one of those crashes occurred after a CLEAN install of the v361.43 drivers yet the driver version is reported as v359.06!!! :3eyes:
     
  6. Wagnard

    Wagnard Ancient Guru

    Messages:
    2,632
    Likes Received:
    267
    GPU:
    MSI Geforce GTX 1080
    Is kerbal Space Demo also affected? I tried on my systems and there were no problem switching AA to 8x (full and non fullscreen)
    Here is some tech info of the dmp: It doesnt say much more to me than a memory access violation possibliy on the nvidia driver.
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Some common problems are exception code 0x80000003.  This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG.  This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG.  This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff80060cde18d, The address that the exception occurred at
    Arg3: ffffd000272acf28, Exception Record Address
    Arg4: ffffd000272ac740, Context Record Address
    
    Debugging Details:
    ------------------
    
    TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
    
    FAULTING_IP: 
    nvlddmkm+11e18d
    fffff800`60cde18d 40387938        cmp     byte ptr [rcx+38h],dil
    
    EXCEPTION_RECORD:  ffffd000272acf28 -- (.exr 0xffffd000272acf28)
    ExceptionAddress: fffff80060cde18d (nvlddmkm+0x000000000011e18d)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: 0000000000000038
    Attempt to read from address 0000000000000038
    
    CONTEXT:  ffffd000272ac740 -- (.cxr 0xffffd000272ac740)
    rax=ffffe00145c24198 rbx=ffffe00141bbb000 rcx=0000000000000000
    rdx=ffffe0014a6f19b0 rsi=ffffe00145c22000 rdi=0000000000000000
    rip=fffff80060cde18d rsp=ffffd000272ad160 rbp=ffffd000272ad260
     r8=ffffe00141bbb000  r9=0000000000000000 r10=0000000000000000
    r11=fffff8005f3f5f4f r12=fffff800615d82e0 r13=0000000000000000
    r14=ffffe0014a6f19b0 r15=ffffe00145c22000
    iopl=0         nv up ei pl zr na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
    nvlddmkm+0x11e18d:
    fffff800`60cde18d 40387938        cmp     byte ptr [rcx+38h],dil ds:002b:00000000`00000038=??
    Resetting default scope
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    BAD_PAGES_DETECTED: e400
    
    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
    
    EXCEPTION_PARAMETER1:  0000000000000000
    
    EXCEPTION_PARAMETER2:  0000000000000038
    
    READ_ADDRESS: unable to get nt!MmSpecialPoolStart
    unable to get nt!MmSpecialPoolEnd
    unable to get nt!MmPagedPoolEnd
    unable to get nt!MmNonPagedPoolStart
    unable to get nt!MmSizeOfNonPagedPoolInBytes
     0000000000000038 
    
    FOLLOWUP_IP: 
    nvlddmkm+11e18d
    fffff800`60cde18d 40387938        cmp     byte ptr [rcx+38h],dil
    
    BUGCHECK_STR:  AV
    
    DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
    
    EXCEPTION_STR:  0xe400
    
    LAST_CONTROL_TRANSFER:  from ffffe00141bbb000 to fffff80060cde18d
    
    STACK_TEXT:  
    ffffd000`272ad160 ffffe001`41bbb000 : ffffe001`45c22000 00000000`00000000 00000000`00000000 00000000`00000000 : nvlddmkm+0x11e18d
    ffffd000`272ad168 ffffe001`45c22000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffffe001`41bbb000
    ffffd000`272ad170 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffffe001`45c22000
    
    
    SYMBOL_NAME:  PAGE_NOT_ZERO
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: Unknown_Module
    
    IMAGE_NAME:  Unknown_Image
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    STACK_COMMAND:  .cxr 0xffffd000272ac740 ; kb
    
    BUCKET_ID:  PAGE_NOT_ZERO
    
    Followup: MachineOwner
    ---------
    
     *** Memory manager detected 58368 instance(s) of page corruption, target is likely to have memory corruption.
     
    Last edited: Dec 24, 2015
  7. Wagnard

    Wagnard Ancient Guru

    Messages:
    2,632
    Likes Received:
    267
    GPU:
    MSI Geforce GTX 1080
    Its because you currently have 359.06 installed. This info doesn't come from the dmp itself.
     
  8. Webhiker

    Webhiker Master Guru

    Messages:
    567
    Likes Received:
    133
    GPU:
    EVGA GTX 1080i SC2
    I doubt you will notice any change in startup speed. Starting in windows 8 the OS uses Fast startup or Hybrid Boot. It does so by doing a Hybrid Shutdown ( partial hibernation ) when shutting down. This saves only the kernal session and device drivers to the hiberfil.sys file on disk instead of closing it when you shut down your PC. So effectively, when you start again, it will pick up from where it left off instead of doing a cold boot. But it's been know to cause some issues.
    The reason I suggest you try to turn it off. Is because of the KMODE_EXCEPTION in the error dump you showed. If it doesn't help you can always turn it back on :) .

    You can read more about it here : https://blogs.msdn.microsoft.com/b8/2011/09/08/delivering-fast-boot-times-in-windows-8/
     
    Last edited: Dec 24, 2015
  9. Darren Hodgson

    Darren Hodgson Ancient Guru

    Messages:
    15,838
    Likes Received:
    387
    GPU:
    EVGA GTX 1080 Ti SC2
    Thanks Wagnard.

    Seems that my issue could be a conflict between the new driver and possibly something else I am running, something that did not cause issues with previous drivers?

    I have uninstalled the Dell Display Manager and the BSODs still occur so it is not that. Of course, I am using MSI Afterburner (current version 4.2.0) and RTSS (v6.4.1) but I have been using both for years now. I admit that I did not try disabling either of those but I find it hard to believe that they would cause this issue anyway as at worst they simply cause games to crash to the desktop not BSODs and far more people would be reporting BSODs given how popular the program is (understandably, as it is a superb tool).
     
  10. Wagnard

    Wagnard Ancient Guru

    Messages:
    2,632
    Likes Received:
    267
    GPU:
    MSI Geforce GTX 1080
    Maybe a bit extreme, but I see you seems to have a SoundBlaster card, they use to have some conflict in the past with the nV driver. Maybe just try to disable the card via device manager and see if it still crash.
     

  11. jonaand

    jonaand Member Guru

    Messages:
    157
    Likes Received:
    1
    GPU:
    gtx 1080
    this driver with cuda 8.0.5
    we can convert in hevc using hardware with dvdfab 9223

    anyone know another program that use hardware in hevc with this new version of cuda
     
  12. Wagnard

    Wagnard Ancient Guru

    Messages:
    2,632
    Likes Received:
    267
    GPU:
    MSI Geforce GTX 1080
    I found someone else with similar issue as your with a 970M

    Here is a more detailed bugcheck from your dmp.
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1000007E, {ffffffffc0000005, fffff80060cde18d, ffffd000272acf28, ffffd000272ac740}
    
    Probably caused by : nvlddmkm.sys ( nvlddmkm+11e18d )
    
    Followup:     MachineOwner
    ---------
    
    4: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Some common problems are exception code 0x80000003.  This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG.  This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG.  This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff80060cde18d, The address that the exception occurred at
    Arg3: ffffd000272acf28, Exception Record Address
    Arg4: ffffd000272ac740, Context Record Address
    
    Debugging Details:
    ------------------
    
    
    DUMP_CLASS: 1
    
    DUMP_QUALIFIER: 400
    
    BUILD_VERSION_STRING:  10586.17.amd64fre.th2_release.151121-2308
    
    SYSTEM_MANUFACTURER:  ASUS
    
    SYSTEM_PRODUCT_NAME:  All Series
    
    SYSTEM_SKU:  All
    
    SYSTEM_VERSION:  System Version
    
    BIOS_VENDOR:  American Megatrends Inc.
    
    BIOS_VERSION:  2103
    
    BIOS_DATE:  08/15/2014
    
    BASEBOARD_MANUFACTURER:  ASUSTeK COMPUTER INC.
    
    BASEBOARD_PRODUCT:  Z87-DELUXE
    
    BASEBOARD_VERSION:  Rev 1.xx
    
    DUMP_TYPE:  2
    
    DUMP_FILE_ATTRIBUTES: 0x8
      Kernel Generated Triage Dump
    
    BUGCHECK_P1: ffffffffc0000005
    
    BUGCHECK_P2: fffff80060cde18d
    
    BUGCHECK_P3: ffffd000272acf28
    
    BUGCHECK_P4: ffffd000272ac740
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.
    
    FAULTING_IP: 
    nvlddmkm+11e18d
    fffff800`60cde18d 40387938        cmp     byte ptr [rcx+38h],dil
    
    EXCEPTION_RECORD:  ffffd000272acf28 -- (.exr 0xffffd000272acf28)
    ExceptionAddress: fffff80060cde18d (nvlddmkm+0x000000000011e18d)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: 0000000000000038
    Attempt to read from address 0000000000000038
    
    CONTEXT:  ffffd000272ac740 -- (.cxr 0xffffd000272ac740)
    rax=ffffe00145c24198 rbx=ffffe00141bbb000 rcx=0000000000000000
    rdx=ffffe0014a6f19b0 rsi=ffffe00145c22000 rdi=0000000000000000
    rip=fffff80060cde18d rsp=ffffd000272ad160 rbp=ffffd000272ad260
     r8=ffffe00141bbb000  r9=0000000000000000 r10=0000000000000000
    r11=fffff8005f3f5f4f r12=fffff800615d82e0 r13=0000000000000000
    r14=ffffe0014a6f19b0 r15=ffffe00145c22000
    iopl=0         nv up ei pl zr na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
    nvlddmkm+0x11e18d:
    fffff800`60cde18d 40387938        cmp     byte ptr [rcx+38h],dil ds:002b:00000000`00000038=??
    Resetting default scope
    
    CPU_COUNT: 8
    
    CPU_MHZ: dac
    
    CPU_VENDOR:  GenuineIntel
    
    CPU_FAMILY: 6
    
    CPU_MODEL: 3c
    
    CPU_STEPPING: 3
    
    CPU_MICROCODE: 6,3c,3,0 (F,M,S,R)  SIG: 1E'00000000 (cache) 1E'00000000 (init)
    
    CUSTOMER_CRASH_COUNT:  1
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.
    
    EXCEPTION_CODE_STR:  c0000005
    
    EXCEPTION_PARAMETER1:  0000000000000000
    
    EXCEPTION_PARAMETER2:  0000000000000038
    
    READ_ADDRESS: fffff8015dd83520: Unable to get MiVisibleState
     0000000000000038 
    
    FOLLOWUP_IP: 
    nvlddmkm+11e18d
    fffff800`60cde18d 40387938        cmp     byte ptr [rcx+38h],dil
    
    BUGCHECK_STR:  AV
    
    DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
    
    ANALYSIS_SESSION_HOST:  WAGNARD-X64
    
    ANALYSIS_SESSION_TIME:  12-24-2015 12:26:17.0756
    
    ANALYSIS_VERSION: 10.0.10586.567 x86fre
    
    LAST_CONTROL_TRANSFER:  from ffffe00141bbb000 to fffff80060cde18d
    
    STACK_TEXT:  
    ffffd000`272ad160 ffffe001`41bbb000 : ffffe001`45c22000 00000000`00000000 00000000`00000000 00000000`00000000 : nvlddmkm+0x11e18d
    ffffd000`272ad168 ffffe001`45c22000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffffe001`41bbb000
    ffffd000`272ad170 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffffe001`45c22000
    
    
    THREAD_SHA1_HASH_MOD_FUNC:  d79c3f9e9541b50dff558588ee91b494a55f2aae
    
    THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  aec45d7f8a6ffa744cacd570be4de2306ffa003f
    
    THREAD_SHA1_HASH_MOD:  d79c3f9e9541b50dff558588ee91b494a55f2aae
    
    FAULT_INSTR_CODE:  38793840
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  nvlddmkm+11e18d
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nvlddmkm
    
    IMAGE_NAME:  nvlddmkm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  56716f32
    
    STACK_COMMAND:  .cxr 0xffffd000272ac740 ; kb
    
    BUCKET_ID_FUNC_OFFSET:  11e18d
    
    FAILURE_BUCKET_ID:  AV_nvlddmkm!Unknown_Function
    
    BUCKET_ID:  AV_nvlddmkm!Unknown_Function
    
    PRIMARY_PROBLEM_CLASS:  AV_nvlddmkm!Unknown_Function
    
    TARGET_TIME:  2015-12-23T19:10:50.000Z
    
    OSBUILD:  10586
    
    OSSERVICEPACK:  0
    
    SERVICEPACK_NUMBER: 0
    
    OS_REVISION: 0
    
    SUITE_MASK:  272
    
    PRODUCT_TYPE:  1
    
    OSPLATFORM_TYPE:  x64
    
    OSNAME:  Windows 10
    
    OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS
    
    OS_LOCALE:  
    
    USER_LCID:  0
    
    OSBUILD_TIMESTAMP:  2015-11-22 04:24:24
    
    BUILDDATESTAMP_STR:  151121-2308
    
    BUILDLAB_STR:  th2_release
    
    BUILDOSVER_STR:  10.0.10586.17.amd64fre.th2_release.151121-2308
    
    ANALYSIS_SESSION_ELAPSED_TIME: 64e
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:av_nvlddmkm!unknown_function
    
    FAILURE_ID_HASH:  {7eea5677-f68d-2154-717e-887e07e55cd3}
    
    Followup:     MachineOwner
    ---------
    
    4: kd> lmvm nvlddmkm
    Browse full module list
    start             end                 module name
    fffff800`60bc0000 fffff800`617db000   nvlddmkm T (no symbols)           
        Loaded symbol image file: nvlddmkm.sys
        Image path: nvlddmkm.sys
        Image name: nvlddmkm.sys
        Browse all global symbols  functions  data
        Timestamp:        Wed Dec 16 09:03:30 2015 (56716F32)
        CheckSum:         00BE13AE
        ImageSize:        00C1B000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    
    Ill try to contact someone at nV about this, but its the 24dec so dont expect anything soon.
     
  13. Darren Hodgson

    Darren Hodgson Ancient Guru

    Messages:
    15,838
    Likes Received:
    387
    GPU:
    EVGA GTX 1080 Ti SC2
    Thanks again, Wagnard.
     
  14. phatbx133

    phatbx133 Master Guru

    Messages:
    828
    Likes Received:
    9
    GPU:
    MSI GTX 1050ti 4GB
    I just finished the game called Afterfall Insanity Extended Edition for 2 days done with this driver works well, no hiccup, shutter or freeze at all.

    Now uninstall that game off the library:banana:

    This driver is keeper.
     
  15. bOse

    bOse Active Member

    Messages:
    63
    Likes Received:
    6
    GPU:
    ASUS GTX 960
    How do these run with bf4 ?
     

  16. lexkalin

    lexkalin New Member

    Messages:
    2
    Likes Received:
    0
    GPU:
    EVGA GTX 970 SSC ACX 2.0+
    Hey guys, does anyone knows how to get rid of this problem? When I use DSR and the exit the game all my icons arrangements are messed up and I have to manually drag and drop them to where they belong. Any workaround? Using Win 10 and 361.43 if that makes any difference.
     
  17. KillerC

    KillerC Master Guru

    Messages:
    417
    Likes Received:
    0
    GPU:
    EVGA 2080 RTX
    Roger that, thank you for the suggestion and follow up.

    I played somewhere around 3 hours of Fallout 4 and have done as much as I can to get it to BSOD again and, so far, no more BSOD.

    Not sure if the fast boot did it or not, I have never had a problem with it before.

    Thanks man!!
     
  18. Shady757

    Shady757 Member Guru

    Messages:
    177
    Likes Received:
    2
    GPU:
    Gigabyte G1 GTX 970/GSYNC

    You say you play Rust, I do too. I'm wondering if you have the same issue as me; basically, sometimes when I start the game and load in, my FPS will be VERY low, like 20, and the GPU usage will be maxed out.

    I can restart the game, over and over, and it doesn't do anything. The only fix is rebooting, or disabling the device in Device Manager and re-enabling it.
     
  19. scaramonga

    scaramonga Member Guru

    Messages:
    154
    Likes Received:
    13
    GPU:
    1080 Ti FTW3 W/C
    ^^THIS!^^

    God damn slower with every driver set, and if you have lots of profiles, it takes an age to refresh them now :(
     
  20. AntiSnipe

    AntiSnipe Master Guru

    Messages:
    221
    Likes Received:
    54
    GPU:
    MSI GTX 1060 3G
    I wish they would "update the control panel" until it looked something like this

    [​IMG]
     

Share This Page