BSOD playing games, browsing the web, programming, doing nothing

Page 2 of 2 FirstFirst 12

  1. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #11

    This BSOD is caused by Nvidia display driver. And unfortunately I dont know any driver version that works good with GTX 770. You may try the drivers on a trial and error basis:

    • 320.49 WHQL
    • 327.23 WHQL
    • 331.58 WHWL
    • 331.65 WHQL
    • 331.82 WHQL

    Get them from Drivers - Download NVIDIA Drivers

    Do a clean install on all of them. Uninstall the previously installed driver first.
    Uninstall All nvidia items in Control Panel > Programs and features

      • 3D Vision Control Driver
      • 3D Vision Driver
      • Graphics Driver
      • HD Audio Driver
      • PhysX
      • nvidia Update

      (Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
    • Now follow Drivers - Clean Left over Files after Uninstalling
    • Download the target WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:


    Lengthy process, but the only stable version of nvidia is 314.22 lately, which does not support 700 series GPUs.

    __________________________________________________________________________________________
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck C4, {f6, 22c, fffffa800c4c2570, fffff8800f574879}
    
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by : nvlddmkm.sys ( nvlddmkm+9a879 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
    A device driver attempting to corrupt the system has been caught.  This is
    because the driver was specified in the registry as being suspect (by the
    administrator) and the kernel has enabled substantial checking of this driver.
    If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
    be among the most commonly seen crashes.
    Arguments:
    Arg1: 00000000000000f6, Referencing user handle as KernelMode.
    Arg2: 000000000000022c, Handle value being referenced.
    Arg3: fffffa800c4c2570, Address of the current process.
    Arg4: fffff8800f574879, Address inside the driver that is performing the incorrect reference.
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0xc4_f6
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    
    PROCESS_NAME:  chrome.exe
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from fffff800033094ec to fffff80002e7cbc0
    
    STACK_TEXT:  
    fffff880`0cdf4888 fffff800`033094ec : 00000000`000000c4 00000000`000000f6 00000000`0000022c fffffa80`0c4c2570 : nt!KeBugCheckEx
    fffff880`0cdf4890 fffff800`0331ebf4 : 00000000`0000022c fffffa80`0c4c2570 00000000`00000004 fffff8a0`02e20a30 : nt!VerifierBugCheckIfAppropriate+0x3c
    fffff880`0cdf48d0 fffff800`030d6890 : fffff8a0`00000003 fffff880`0cdf4b20 fffff880`0cdf4d00 fffff880`0cdf4eb0 : nt!VfCheckUserHandle+0x1b4
    fffff880`0cdf49b0 fffff800`0314c6b5 : fffff8a0`02e7a900 fffff8a0`00000001 fffffa80`06d46500 00000000`00000000 : nt! ?? ::NNGAKEGL::`string'+0x2027e
    fffff880`0cdf4a80 fffff800`02e7be53 : fffffa80`0b518b50 fffff880`0cdf4e38 00000000`00000002 00000000`00000000 : nt!NtQueryValueKey+0x115
    fffff880`0cdf4c10 fffff800`02e78410 : fffff800`0330dd96 fffff880`0f574879 fffff880`0cdf4eb0 fffff880`0cdf4ea8 : nt!KiSystemServiceCopyEnd+0x13
    fffff880`0cdf4e18 fffff800`0330dd96 : fffff880`0f574879 fffff880`0cdf4eb0 fffff880`0cdf4ea8 fffff800`02e78410 : nt!KiServiceLinkage
    fffff880`0cdf4e20 fffff880`0f574879 : fffff880`0cdf58ca fffff880`0cdf4ef0 fffff880`0cdf58b8 fffffa80`07290798 : nt!VfZwQueryValueKey+0x76
    fffff880`0cdf4e70 fffff880`0cdf58ca : fffff880`0cdf4ef0 fffff880`0cdf58b8 fffffa80`07290798 00000000`00000000 : nvlddmkm+0x9a879
    fffff880`0cdf4e78 fffff880`0cdf4ef0 : fffff880`0cdf58b8 fffffa80`07290798 00000000`00000000 fffff880`0cdf4ea0 : 0xfffff880`0cdf58ca
    fffff880`0cdf4e80 fffff880`0cdf58b8 : fffffa80`07290798 00000000`00000000 fffff880`0cdf4ea0 fffff980`00000000 : 0xfffff880`0cdf4ef0
    fffff880`0cdf4e88 fffffa80`07290798 : 00000000`00000000 fffff880`0cdf4ea0 fffff980`00000000 00000000`0000022c : 0xfffff880`0cdf58b8
    fffff880`0cdf4e90 00000000`00000000 : fffff880`0cdf4ea0 fffff980`00000000 00000000`0000022c fffffa80`00280026 : 0xfffffa80`07290798
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nvlddmkm+9a879
    fffff880`0f574879 3d340000c0      cmp     eax,0C0000034h
    
    SYMBOL_STACK_INDEX:  8
    
    SYMBOL_NAME:  nvlddmkm+9a879
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nvlddmkm
    
    IMAGE_NAME:  nvlddmkm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  5290d7c5
    
    FAILURE_BUCKET_ID:  X64_0xc4_f6_VRF_nvlddmkm+9a879
    
    BUCKET_ID:  X64_0xc4_f6_VRF_nvlddmkm+9a879
    
    Followup: MachineOwner
    ---------
    
    0: kd> lmvm nvlddmkm
    start             end                 module name
    fffff880`0f4da000 fffff880`1011b000   nvlddmkm T (no symbols)           
        Loaded symbol image file: nvlddmkm.sys
        Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
        Image name: nvlddmkm.sys
        Timestamp:        Sat Nov 23 21:58:53 2013 (5290D7C5)
        CheckSum:         00C09A5E
        ImageSize:        00C41000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


  2. Posts : 7
    Windows 7 Home Premium x64
    Thread Starter
       #12

    I have tried all the following versions, and they either make my system BSOD or are not compatible with my games (Tested with BF4)

      My Computer


  3. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #13

    Then replace the GPU. Use one that is below 700 series.

    Or ask your game developer if they have any custom settings or patches that is applicable for your system.

    Unfortunately I am seeing no other way out at the current situation.
      My Computer


 
Page 2 of 2 FirstFirst 12

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 04:37.
Find Us