BSOD random times, fresh win 7 install, new motherboard, added another gtx 470

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by jle7385, Oct 23, 2012.

  1. jle7385

    jle7385 New Member

    Joined:
    Oct 23, 2012
    Messages:
    4
    Likes Received:
    0
    I keep getting BlueScreen errors and the pc is restarting after I switched motherboards from a gigabyte p55-usb3 to a biostar t5xe cfx-sli. I kept all the same components except I added another gtx 470. Thermal paste was freshly applied all around, all the idle and load temps seem normal. 30c/50c cpu and 40c/85c gpu.

    Let me give you the rundown first:

    1st Shutdown:

    1. Installed Win 7 Prof 64 bit on freshly formatted hard drive
    2. Installed Drivers from motherboard cd (Biostar T5XE CFX-SLI)
    3. Ran Windows update for awhile, restarted a few times, installed other programs
    4. While browsing the net the pc shutdown and gave me a prompt upon startup with a "problem event name: bluescreen"

    It also gave me the locations of a dump and a system file which I have included in the Shutdown #1 file.

    2nd Shutdown:

    1. After reviewing the error and searching the web I had read that it could be a possible heat issue, which didn't make sense as the first time I was just browsing the web. Idle the CPU is 30c and the GPU (SLI) is 40c for each card.
    2. I downloaded the Unigine Heaven benchmark and ran it
    3. PC shutdown in the middle of the benchmark and gave me different results in the post shutdown message. Files are in the Shutdown #2 file.

    I used arctic silver on the cpu and on the gpu's. Everything is connected tightly and the only other thing installed is a wireless pci card which should have no problem. I used to use the exact same components on a gigabyte board (p55-usb3). The only reason I installed the Biostar Motherboard was to install another GTX 470 and run SLI. Everything seems normal as far as temps, the pc isn't slow, etc...I just decided to turn it off to avoid any possible damage and take the files I grabbed and post on a forum. This seemed like a good place to continue. The sevenforums file is also attached. Thanks. (I labeled the shutdowns #1 and #2 just to make it easier...in total this happened 2 or 3 more times during senarios relating to shutdown #1.)
     

    Attached Files:

  2. GeneralHiningII

    GeneralHiningII Honorable Member

    Joined:
    Sep 21, 2012
    Messages:
    745
    Likes Received:
    7
    According to all the analysis's run, it's still a problem with your graphics driver.

    Analysis:

    Code:
    Analysis:
    Debug session time: Tue Oct 23 12:59:39.078 2012 (UTC + 11:00)
    Loading Dump File [C:\Users\MZ\SysnativeBSODs\102212-24031-01.dmp]
    Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
    System Uptime: 0 days 1:58:19.125
    BugCheck 116, {fffffa800b44a4e0, fffff8800fae0630, ffffffffc000009a, 4}
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by :[COLOR=#ff0000] nvlddmkm.sys ( nvlddmkm+ade630 )[/COLOR]
    Bugcheck code 00000116
    DEFAULT_BUCKET_ID:  [COLOR=#ff0000]GRAPHICS_DRIVER_TDR_FAULT[/COLOR]
    BUGCHECK_STR:  0x116
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    MaxSpeed:     2930
    CurrentSpeed: 2931
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    Debug session time: Tue Oct 23 10:48:26.140 2012 (UTC + 11:00)
    Loading Dump File [C:\Users\MZ\SysnativeBSODs\102212-29656-01.dmp]
    Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
    System Uptime: 0 days 0:00:41.312
    BugCheck 116, {fffffa8009a84010, fffff8800fbb0630, ffffffffc000009a, 4}
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by : [COLOR=#ff0000]nvlddmkm.sys ( nvlddmkm+ade630 )[/COLOR]
    Bugcheck code 00000116
    DEFAULT_BUCKET_ID:  [COLOR=#ff0000]GRAPHICS_DRIVER_TDR_FAULT[/COLOR]
    BUGCHECK_STR:  0x116
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    MaxSpeed:     2930
    CurrentSpeed: 2931
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    Debug session time: Tue Oct 23 10:46:31.830 2012 (UTC + 11:00)
    Loading Dump File [C:\Users\MZ\SysnativeBSODs\102212-29515-01.dmp]
    Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
    System Uptime: 0 days 0:01:33.001
    BugCheck 116, {fffffa800a6634e0, fffff8800fb6f630, ffffffffc000009a, 4}
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by : [COLOR=#ff0000]nvlddmkm.sys ( nvlddmkm+ade630 [/COLOR])
    Bugcheck code 00000116
    DEFAULT_BUCKET_ID:  [COLOR=#ff0000]GRAPHICS_DRIVER_TDR_FAULT[/COLOR]
    BUGCHECK_STR:  0x116
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    MaxSpeed:     2930
    CurrentSpeed: 2931
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    Debug session time: Tue Oct 23 10:44:02.788 2012 (UTC + 11:00)
    Loading Dump File [C:\Users\MZ\SysnativeBSODs\102212-26562-01.dmp]
    Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
    System Uptime: 0 days 1:09:35.834
    BugCheck 116, {fffffa8008152010, fffff8800fb1a630, ffffffffc000009a, 4}
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by : [COLOR=#ff0000]nvlddmkm.sys ( nvlddmkm+ade630 )[/COLOR]
    Bugcheck code 00000116
    DEFAULT_BUCKET_ID:  [COLOR=#ff0000]GRAPHICS_DRIVER_TDR_FAULT[/COLOR]
    BUGCHECK_STR:  0x116
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    MaxSpeed:     2930
    CurrentSpeed: 2931
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    Debug session time: Tue Oct 23 09:33:00.142 2012 (UTC + 11:00)
    Loading Dump File [C:\Users\MZ\SysnativeBSODs\102212-28703-01.dmp]
    Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
    System Uptime: 0 days 0:01:30.189
    BugCheck 101, {18, 0, fffff88002f64180, 2}
    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    Bugcheck code 00000101
    BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  csrss.exe
    FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    Debug session time: Tue Oct 23 09:30:39.309 2012 (UTC + 11:00)
    Loading Dump File [C:\Users\MZ\SysnativeBSODs\102212-30984-01.dmp]
    Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
    System Uptime: 0 days 0:19:35.340
    BugCheck 116, {fffffa80085694e0, fffff8800fb90630, ffffffffc000009a, 4}
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by : [COLOR=#ff0000]nvlddmkm.sys ( nvlddmkm+ade630 )[/COLOR]
    Bugcheck code 00000116
    DEFAULT_BUCKET_ID:  [COLOR=#ff0000]GRAPHICS_DRIVER_TDR_FAULT[/COLOR]
    BUGCHECK_STR:  0x116
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    MaxSpeed:     2930
    CurrentSpeed: 2931
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    Debug session time: Tue Oct 23 09:09:49.092 2012 (UTC + 11:00)
    Loading Dump File [C:\Users\MZ\SysnativeBSODs\102212-38812-01.dmp]
    Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
    System Uptime: 0 days 0:36:26.139
    BugCheck 116, {fffffa800a0a74e0, fffff8800fbc8630, ffffffffc000009a, 4}
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by : [COLOR=#ff0000]nvlddmkm.sys ( nvlddmkm+ade630 )[/COLOR]
    Bugcheck code 00000116
    DEFAULT_BUCKET_ID:  [COLOR=#ff0000]GRAPHICS_DRIVER_TDR_FAULT[/COLOR]
    BUGCHECK_STR:  0x116
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    MaxSpeed:     2930
    CurrentSpeed: 2931
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    Debug session time: Tue Oct 23 07:06:18.046 2012 (UTC + 11:00)
    Loading Dump File [C:\Users\MZ\SysnativeBSODs\102212-29359-01.dmp]
    Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
    System Uptime: 0 days 0:01:03.093
    BugCheck 116, {fffffa8009b0e330, fffff8800fbbf630, ffffffffc000009a, 4}
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by : [COLOR=#ff0000]nvlddmkm.sys ( nvlddmkm+ade630 )[/COLOR]
    Bugcheck code 00000116
    DEFAULT_BUCKET_ID:  [COLOR=#ff0000]GRAPHICS_DRIVER_TDR_FAULT[/COLOR]
    BUGCHECK_STR:  0x116
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    MaxSpeed:     2930
    CurrentSpeed: 2931
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    Debug session time: Tue Oct 23 07:04:00.874 2012 (UTC + 11:00)
    Loading Dump File [C:\Users\MZ\SysnativeBSODs\102212-44859-01.dmp]
    Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
    System Uptime: 0 days 0:11:21.045
    BugCheck 116, {fffffa8007f444e0, fffff8800fbdc630, ffffffffc000009a, 4}
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by : [COLOR=#ff0000]nvlddmkm.sys ( nvlddmkm+ade630 )[/COLOR]
    Bugcheck code 00000116
    DEFAULT_BUCKET_ID:  [COLOR=#ff0000]GRAPHICS_DRIVER_TDR_FAULT[/COLOR]
    BUGCHECK_STR:  0x116
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    MaxSpeed:     2930
    CurrentSpeed: 2931
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    
    nvlddmkm.sys is a NVIDIA driver - GRAPHICS_DRIVER_TDR_FAULT - TDR_FAULT means that the specified driver/device failed to respond within a certain amount of time. Which means your graphics driver wasn't installed properly. (Ignore the 6th entry - it's just repeating the problems caused by the other ones).

    What I suggest: A clean install of your Graphics Driver.

    How to do it (before doing these, download BUT DON'T INSTALL the newest drivers from Drivers | GeForce and save the download to your desktop)

    1. Reboot the computer, repeatedly press F8 to access Advanced Boot Options. Select Safe Mode.
    2. When Safe Mode has loaded, Start > QuickSearch “Device Manager” or Start > Control Panel > View by: Large Icons > Device Manager.
    3. On Device Manager - Display Adapters > [select onboard GPU] – right click > Uninstall. Select the option Delete the driver software for this device.
    4. Uninstall the GPU, and reboot the computer normally.
    5. On Windows, wait for the card to reinstall. When the card is reinstalled, you should receive the message “Device [GPU Name] has been successfully installed – Geforce 310”. When this notification appears, close it.
    6. Double-click your driver download (which should've been previously downloaded) and run it - on the install screen, make sure to tick the box labelled "Clean Install". Let the driver install itself, and then reboot once more.

    Try running the computer again.

    3rd Party Drivers:
    All drivers in red should be updated or removed - I will explain which to update and which to remove.
    Code:
    [B][COLOR=#FF0000]BIOS64.sys                  Sun Jun  8 10:12:00 2003 (3EE27F50)[/COLOR][/B]
    [B][COLOR=#FF0000]BS_I2cIo.sys                Mon Jun 16 16:45:18 2008 (48560BFE)[/COLOR][/B]
    tmpECA2.tmp                 Sat Jul 26 23:29:37 2008 (488B26C1)
    [B][COLOR=#FF0000]Rt64win7.sys                Sat May 23 00:52:30 2009 (4A16BC2E)[/COLOR][/B]
    intelppm.sys                Tue Jul 14 09:19:25 2009 (4A5BC0FD)
    [B][COLOR=#FF0000]RTKVHD64.sys                Mon Jul 20 20:52:29 2009 (4A644C6D)[/COLOR][/B]
    [B][COLOR=#FF0000]LGVirHid.sys                Tue Nov 24 12:36:48 2009 (4B0B38B0)[/COLOR][/B]
    [B][COLOR=#FF0000]LGBusEnum.sys               Tue Nov 24 12:36:48 2009 (4B0B38B0)[/COLOR][/B]
    amdxata.sys                 Sat Mar 20 03:18:18 2010 (4BA3A3CA)
    [B][COLOR=#FF0000]RTCore64.sys                Tue Sep  6 22:24:50 2011 (4E661112)[/COLOR][/B]
    nvhda64v.sys                Wed Jul  4 01:25:04 2012 (4FF30ED0)
    DirectIo64.sys              Mon Aug 13 14:30:24 2012 (502882E0)
    MpFilter.sys                Fri Aug 24 09:03:14 2012 (5036B6B2)
    nvlddmkm.sys                Wed Oct  3 04:21:13 2012 (506B3099)
    
    Driver Reference Table -BIOS64.sys
    Update this - aBIOSTAR Input/Output Driver.

    Driver Reference Table -BS_I2cIo.sys
    Update this - aBIOSTAR Flash Drive Utility Driver.


    Driver Reference Table -Rt64win7.sys
    Update this - Realtek AUDIO Driver.


    Driver Reference Table -RTKVHD64.sys
    Update this - Realtek High Def AUDIO Driver.


    Driver Reference Table -LGVirHid.sys
    Update this - Logitech Gamepanel Device Driver.


    Driver Reference Table -LGBusEnum.sys
    Update this - Logitech Keyboard Driver


    Driver Reference Table -RTCore64.sys
    REMOVE THIS -
    This is an overclocking software which is known to cause issues with Windows 7 - REMOVE IT IMMEDIATELY.
     
  3. jle7385

    jle7385 New Member

    Joined:
    Oct 23, 2012
    Messages:
    4
    Likes Received:
    0
    Ok. Sorry for the time it took for me to post back... Swing shift.. 3 kids.. Etc.

    It appears that the first bsod, the watchdog one is gone. I updated all the drivers, and even tried upgrading to windows 8 and am no longer receiving that error.

    As far as the bccode 116 I am still consistently getting it while benchmarking, and running the wei, or gaming. I followed the guide listed in the previous reply to no avail. Each card by itself wasn't even going past 78c with the burn in test on furmark. I am only getting this error when both cards are in sli. A friend put the cards in his pc and they ran fine. However, he had been using a different sli bridge due to the placement of his pci xpress slots. That's the only thing that I can think of that may be bad. Do you guys think this could be a sli bridge issue? Or possible a issue with the 2nd slot on my motherboard? I don't know! Lol, I'm getting very frustrated here. I know that heat and drivers shouldn't be the issue anymore. Let me know your thoughts
     
  4. usasma

    usasma Fantastic Member
    Microsoft Community Contributor

    Joined:
    Mar 22, 2010
    Messages:
    3,048
    Likes Received:
    83
    Sorry for the delay in responding, but I was without power for 3 days due to Hurricane Sandy.

    I'd check the first video card in the second slot to see if you have any issues there.
    I dunno much about SLI and would suggest that you post over here for more expert assistance: Windows 7 Graphics
     

Share This Page

Loading...