Announcement

Collapse
No announcement yet.

Getting BCCode 116 wondering if its my RAM

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Getting BCCode 116 wondering if its my RAM

    CPU: Intel Core i5-2300 Sandy Bridge 2.8GHz (3.1GHz Turbo Boost) LGA 1155 95W Quad-Core Desktop Processor

    MB: ASRock P67 PRO3 LGA 1155 Intel P67 SATA 6Gb/s USB 3.0 ATX Intel Motherboard

    Memory: G.SKILL Ripjaws Series 8GB (2 x 4GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800) Desktop Memory Model F3-12800CL9D-8GBRL

    Graphics card: MSI N470GTX Twin Frozr II GeForce GTX 470 (Fermi) 1280MB 320-bit GDDR5 PCI Express 2.0 x16 HDCP Ready SLI Support Video Card

    I have been getting BCCode 116 with two separate kinds of video cards. The first card I had was an AMD Raedon 6800 and my screen would go black or become distorted with a bunch of colors. I then got the video card listed above hoping to solve the problem. It continued to happen just not as frequently. It would happen a lot if my computer had to restart for windows updates, however once it finally was stable it would not crash anymore. Here is a debug analysis
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 116, {fffffa800afca010, fffff880106c6f10, ffffffffc000009a, 4}
    
    Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
    *** 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+801f10 )
    
    
    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: fffffa800afca010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff880106c6f10, The pointer into responsible device driver module (e.g. owner tag).
    Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
    Arg4: 0000000000000004, Optional internal context dependent data.
    
    Debugging Details:
    ------------------
    
    
    FAULTING_IP: 
    nvlddmkm+801f10
    fffff880`106c6f10 4883ec28        sub     rsp,28h
    
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
    
    CUSTOMER_CRASH_COUNT:  1
    
    BUGCHECK_STR:  0x116
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    STACK_TEXT:  
    fffff880`03dc0b48 fffff880`04472000 : 00000000`00000116 fffffa80`0afca010 fffff880`106c6f10 ffffffff`c000009a : nt!KeBugCheckEx
    fffff880`03dc0b50 fffff880`04445867 : fffff880`106c6f10 fffffa80`09e1c000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
    fffff880`03dc0b90 fffff880`04471e0f : 00000000`ffffd84d 00000000`00000080 fffffa80`0afca010 00000000`0000000f : dxgkrnl!DXGADAPTER::Reset+0x2a3
    fffff880`03dc0c40 fffff880`04540ec1 : fffffa80`09ed6a20 00000000`00000080 00000000`00000000 fffffa80`09e90410 : dxgkrnl!TdrResetFromTimeout+0x23
    fffff880`03dc0cc0 fffff800`03362bc6 : 00000000`042d2cb5 fffffa80`09ae9b60 fffffa80`06a09040 fffffa80`09ae9b60 : dxgmms1!VidSchiWorkerThread+0x101
    fffff880`03dc0d00 fffff800`0309dbc6 : fffff800`03239e80 fffffa80`09ae9b60 fffff800`03247c40 fffff880`01222534 : nt!PspSystemThreadStartup+0x5a
    fffff880`03dc0d40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    FOLLOWUP_IP: 
    nvlddmkm+801f10
    fffff880`106c6f10 4883ec28        sub     rsp,28h
    
    SYMBOL_NAME:  nvlddmkm+801f10
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nvlddmkm
    
    IMAGE_NAME:  nvlddmkm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4dd73a68
    
    FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    
    BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    
    Followup: MachineOwner
    ---------
    I have read that it is a Graphics card/ RAM issue but I have tried two different graphics cards and I have also had two different Mobos(the same kind) since the p67 pro3s got recalled. The only thing I havent changed has been my RAM. I have ran memtest86+ for hours on each separate stick and it came back with no errors. I also ran OCC for my gpu and for my graphics card memory with no errors. Is it possible that the RAM i have is not compatible with my mb? And would that show up on a memtest86+?

    EDIT: I have also reformatted, cleaned, and reseated everything. I have also heard it BCCode can be a driver issue but I have the most recent drivers. Also when i was trying to update my drivers for my graphics card after i reformatted, my screen would go black and I would get the BCCode 116 . It took me several tries to get it to install without bsod.
    Last edited by cykid15; 07-01-2011, 03:13 PM.

  • #2
    Do you have the latest BIOS for the mobo? Also, do you have have the latest driver for the graphics card, 275.33 (64 bit version)? If so on both, might try the latest nVidia Beta driver, 275.50 which can be found here:

    http://downloads.guru3d.com/download.php?det=2738
    Last edited by Tradesman; 07-01-2011, 08:06 PM.


    Pls offer comments on support I provide, HERE, in order to help me do a better job here:

    Tman

    Comment


    • #3
      Yes I have the latest bios. And I have tried Nvidia's and MSI's latest drivers for the card. Like I said this has happened with two completely different cards and two of the same kind of motherboards. So I find it hard to believe that I would get two bad cards or two bad motherboards.

      Comment


      • #4
        Have you tried running memtest on each stick individually, it may well be a bad stick. Could you try the sticks in another system and CPU? The 2300 often will run 1600, but not always (it's rated, as are most for 1333). Might try the sticks at 1333, with standard voltage and timings at 8-8-8-23 (roughly same performance as 1600 at CL9). If you get errors with memtest on one or more sticks then may want to see if your re/e-tailer will exchange them or RMA through GSkill.


        Pls offer comments on support I provide, HERE, in order to help me do a better job here:

        Tman

        Comment


        • #5
          I have ran each stick separately on memtest without errors. Right now on the main page of my bios it has

          DDR3_A1 : 4096 MB (DDR3-1333)
          DDR3_B1: 4096 MB (DDR3-1333)

          my DRAM settings are as follows
          DRAM Frequency : DDR3 1333
          and the timings are 9 9 9 24
          CR: 1N

          So I am already running at 1333 like you suggest right? and i just have to change my timings to 8 8 8 23?

          I also do not have another desktop currently that I can try the sticks on. Maybe in a few days I could try it on a friend's.
          Last edited by cykid15; 07-02-2011, 10:15 AM.

          Comment


          • #6
            Try changing the timings and the CR needs to be 2N


            Pls offer comments on support I provide, HERE, in order to help me do a better job here:

            Tman

            Comment

            Working...
            X