[Windows 7 64bit] Constant Freezing , no BSOD , no minidumps made

Page 1 of 2 12 LastLast

  1. Posts : 6
    Windows 7 Pro 64bit
       #1

    [Windows 7 64bit] Constant Freezing , no BSOD , dumps now included


    Hello there,

    I have a fairly old system here that is constantly freezing. By freezing I mean the video freezes and it just sits there. The image on the screen does not change at all. While this is occurring I can hear the hard drive working. A hard restart is needed to recover the system.

    When the system comes back there are never any minidumps being created, and I do not see any odd errors in event viewer. The freezing generally occurs during resource intensive programs, but has occurred while opening up a web browser. The freezing feels really random, it can happen multiple times a day, or only once a week. This has been going on for a few months now.

    The only error in event viewer seems to be:
    "The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."

    Things I have tried are:
    - Replace power supply
    - Uninstall any unessential programs or drivers
    - Stress test individual components using memtest, prime95 etc.
    - Switch memory sticks
    - Rebuilt system
    - Monitored temperatures
    - Clean installed video drivers

    As a side note I also experience the dreaded nvidia driver restarts, screen goes black and driver restores itself.

    [System Specs]
    Microsoft Windows 7 Professional 64bit
    Q6600 ~2.4Ghz
    Gigabyte GA-EP43-UD3L
    OCZ XTC Vista Upgrade Edition OCZ2VU8002G 2GB x2
    OCZ XTC Platinum Rev.2 OCZ2P800R21G 1GB x2
    Asus GTX460 (not oced)
    ULTRA 750w
    Creative SB X-Fi Xtreme Audio Sound Card PCI

    Dumps now Included. Dumps are from C:\Windows\LiveKernelReports\WATCHDOG
    Last edited by Ryan25; 02 Feb 2012 at 21:49. Reason: Adding dumps
      My Computer


  2. Posts : 6
    Windows 7 Pro 64bit
    Thread Starter
       #2

    I have a full hardware report here in txt format made using EVEREST.

    **UPDATE**

    I tried this "driver verifier" , I followed the steps that is shown on the forum post. When I went to restart from making the changes the computer blue screens before windows is loaded. I turned it back off using safe mode. Still no minidumps and this is all that is shown on event viewer.

    "Driver detected an internal error in its data structures for ."
    Last edited by Ryan25; 02 Feb 2012 at 19:59.
      My Computer


  3. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #3

    Code:
    
    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [G:\Kingston\BSODDmpFiles\Ryan25Dumps\WD-20120202-1219.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
    Machine Name:
    Kernel base = 0xfffff800`03265000 PsLoadedModuleList = 0xfffff800`034aa670
    Debug session time: Thu Feb  2 10:19:36.599 2012 (GMT-7)
    System Uptime: 0 days 0:12:36.144
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ............................................
    Loading User Symbols
    Mini Kernel Dump does not contain unloaded driver list
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 117, {fffffa80050724e0, fffff8800f3c69c8, 0, 0}
    
    Unable to load image 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+1759c8 )
    
    Followup: MachineOwner
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    VIDEO_TDR_TIMEOUT_DETECTED (117)
    The display driver failed to respond in timely fashion.
    (This code can never be used for real bugcheck).
    Arguments:
    Arg1: fffffa80050724e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff8800f3c69c8, The pointer into responsible device driver module (e.g owner tag).
    Arg3: 0000000000000000, The secondary driver specific bucketing key.
    Arg4: 0000000000000000, Optional internal context dependent data.
    
    Debugging Details:
    ------------------
    
    
    FAULTING_IP: 
    nvlddmkm+1759c8
    fffff880`0f3c69c8 ??              ???
    
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_TIMEOUT
    
    TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b
    
    
    BUGCHECK_STR:  0x117
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    STACK_TEXT:  
    fffff880`05edb490 fffff880`0ff285f7 : fffffa80`050724e0 fffff8a0`116231ba 00000000`00000000 fffff880`0ff28343 : watchdog!WdDbgReportRecreate+0xa3
    fffff880`05edb9b0 fffff880`0ff29075 : fffff8a0`1175cffc fffff8a0`103f9480 fffff8a0`116231ba 00000000`00139e42 : dxgkrnl!TdrUpdateDbgReport+0xcb
    fffff880`05edba00 fffff880`0ff29ce2 : fffffa80`050724e0 fffffa80`050724e0 fffffa80`0390e850 fffffa80`06951410 : dxgkrnl!TdrCollectDbgInfoStage1+0x92d
    fffff880`05edbaa0 fffff880`0f20ff07 : fffffa80`050724e0 00000000`00000000 fffffa80`0390e850 fffffa80`06951410 : dxgkrnl!TdrIsRecoveryRequired+0x17a
    fffff880`05edbad0 fffff880`0f23dd5a : fffffa80`ffffffff 00000000`0000bcb0 fffff880`05edbc30 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
    fffff880`05edbbb0 fffff880`0f20b29e : fffffa80`06951410 ffffffff`feced300 fffffa80`069a7d50 00000000`00000000 : dxgmms1!VidSchWaitForCompletionEvent+0x196
    fffff880`05edbbf0 fffff880`0f237e7a : 00000000`00000000 fffffa80`069a7d50 00000000`00000080 fffffa80`06951410 : dxgmms1!VidSchiScheduleCommandToRun+0x1b2
    fffff880`05edbd00 fffff800`0357cfee : 00000000`02d3b2bf fffffa80`0698cb60 fffffa80`036cc040 fffffa80`0698cb60 : dxgmms1!VidSchiWorkerThread+0xba
    fffff880`05edbd40 fffff800`032d35e6 : fffff800`03457e80 fffffa80`0698cb60 fffff800`03465cc0 fffff880`01439384 : nt!PspSystemThreadStartup+0x5a
    fffff880`05edbd80 00000000`00000000 : fffff880`05edc000 fffff880`05ed6000 fffff880`05eda720 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    FOLLOWUP_IP: 
    nvlddmkm+1759c8
    fffff880`0f3c69c8 ??              ???
    
    SYMBOL_NAME:  nvlddmkm+1759c8
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nvlddmkm
    
    IMAGE_NAME:  nvlddmkm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4e99233b
    
    FAILURE_BUCKET_ID:  X64_0x117_IMAGE_nvlddmkm.sys
    
    BUCKET_ID:  X64_0x117_IMAGE_nvlddmkm.sys
    
    Followup: MachineOwner
    ---------
    Similar to BugCheck 116.

    H2SO4 said:
    These are all stop 0x116 VIDEO_TDR_FAILURE conditions.

    It's not a true crash, in the sense that the bluescreen was initiated only because the combination of video driver and video hardware was being unresponsive, and not because of any synchronous processing exception.

    Since Vista, the "Timeout Detection and Recovery" (TDR) components of the OS video subsystem have been capable of doing some truly impressive things to try to recover from issues which would have caused earlier OSs like XP to crash. As a last resort, the TDR subsystem sends the video driver a "please restart yourself now!" command and waits a few seconds. If there's no response, the OS concludes that the video driver/hardware combo has truly collapsed in a heap, and it fires off that stop 0x116 BSOD.

    If playing with video driver versions hasn't helped, make sure the box is not overheating. Try removing a side panel and aiming a big mains fan straight at the motherboard and GPU. Run it like that for a few hours or days - long enough to ascertain whether cooler temperatures make a difference. If so, it might be as simple as dust buildup and subsequently inadequate cooling.
    The above quote was taken from https://www.sevenforums.com/crashes-d...tml#post280172, which is linked to in usasma's thread about this error. Closely follow the first three posts of usasma's thread outlining STOP 0x116: VIDEO_TDR_ERROR troubleshooting and proceed through each step that you have not yet done. Let us know if you need further help.

    Also, based on what you have tried so far, my first thought is you have a bad graphics card, a problem with your motherboard where it connects with the graphics card, or a graphics card that is not seated properly. Have you attempted to remove the graphics card and then firmly put it back in the machine? Also, have you checked for dust on the card and motherboard?


    Please remove any CD/DVD virtualization software, such as Daemon Tools/Alcohol 120%, as they use a driver called sptd.sys that is known to cause BSODs. Use add/remove programs to remove the software. After removing the software, use the sptd.sys uninstaller to remove sptd.sys from the system.

    I prefer TotalMounter as my CD/DVD virtualization software as it allows me to burn images to a virtual CD/DVD if I just want an ISO file instead of a disc, and it is free.

    Many use MagicISO - Convert BIN to ISO, Create, Edit, Burn, Extract ISO file, ISO/BIN converter/extractor/editor as well, which is also free.
      My Computer


  4. Posts : 6
    Windows 7 Pro 64bit
    Thread Starter
       #4

    Thank you for all the suggestions. I am familiar with the VIDEO_TDR_ERROR, I have experienced it before on vista but not very often on windows 7 till now. I will double check the graphics card to make sure its tight in the slot. I cant imagine the card is damaged because its only about 1 year old.

    I do have Daemon Tools installed, I will remove it and sptd.sys right away and see if that helps.

    Also I have stress tested the video card for several hours without issue, the temperatures tend reach 65-70c at max load, 35-40c at idle. While stress testing I don't get these TDR errors, or driver restarts. It seems to only occur while using high resource applications such as battlefield 3.

    Question: Would it be possible that the creative sound card is causing any issues? I know creative has poor windows 7 support still.
      My Computer


  5. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #5

    Temperatures seem about average, so I doubt that is a concern. See how things go after readjusting the card in the slot and removing sptd.sys
      My Computer


  6. Posts : 6
    Windows 7 Pro 64bit
    Thread Starter
       #6

    It seemed to have improved a bit. While I was testing the system I did not freeze a single time, but I still did get the TDR errors causing the display driver to crash. I decided to format my system, fast and easy to do so I figured why not. So far so good, I played battlefield 3 for about 4 hours tonight without any crashing, freezing or driver issues. Problems may still occur, never know but I think its looking positive.

    Oh, I also removed my creative sound card. Figured I would take out a variable if I didn't need to have it.
      My Computer


  7. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #7

    Glad to see an improvement in stability after the troubleshooting steps.

    Run through your normal routine for a while and post back periodically (every few days) about how the stability has been.
      My Computer


  8. Posts : 6
    Windows 7 Pro 64bit
    Thread Starter
       #8

    I will do that, thank you for all your help. I cant believe the level of tech support I have have received here. I feel I should be paying for this, your response time is near instant.
      My Computer


  9. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #9

    Trust me, that is not the case for everyone (the instant response, I mean; tech support on here is exemplary ). We do this as volunteers, so we are on when time permits. You just happen to have posted when I was on and able to respond quickly. Sometimes, it takes me 10-12 hours to respond to a post.
      My Computer


  10. Posts : 6
    Windows 7 Pro 64bit
    Thread Starter
       #10

    Just an update, I have been slowly installing applications so if something does go wrong I can pinpoint it. But I have yet to have a single issue so my guess is I had some bad drivers or software installed causing troubles. Everything is great so I hope this system will last me at least another year.

    Thank you again for the great assistance.
      My Computer


 
Page 1 of 2 12 LastLast

  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 19:35.
Find Us