PC stops responding, no BSOD

Page 1 of 2 12 LastLast

  1. Posts : 17
    windows 7 home premium 64bit
       #1

    PC stops responding, no BSOD


    Hi,

    My PC has recently stopped responding completely at times. Even Ctrl Alt Del doesn't bring up the usual menu, and I have to use the power button to reboot. There is no BSOD, but windows prompts me to choose between normal boot and safe mode when I reboot. The issue arises regardless of what I'm doing; it has occured when I'm gaming, or just surfing the internet. Running system restore to a restore point before the most recent updates from windows doesn't seem to fix the issue.

    The PC is about 1 year old. It's running Windows 7 64 bit Home Premium, installed with an OEM disc on a custom system. Using a P67A-UD3-B3 motherboard and i5-2400 processor.

    Any help with my problem? I've attached the dump report and performance monitor report.
      My Computer


  2. Posts : 1,413
    Windows 7 Home Premium x64
       #2

    Uninstall Avast and SPybot. Install Microsoft Security Essentials and run a FULL System scan. Also, download and install Malwarebytes, the free version and do not start the trial. Run a FULL SCAN ON ALL USER ACCOUNTS.

    After doing so, please run a Disk Check Disk Check

    After doing that, please run SFC /SCANNOW Command - System File Checker Run it three times, rebooting between each run. Take note of behavior after each task and post back with the results.

    Thanks,

    James
      My Computer


  3. Posts : 17
    windows 7 home premium 64bit
    Thread Starter
       #3

    Thanks,

    I've followed your suggested steps, running MSE full scan and Malwarebytes full scan on an administrator account. I currently have a 1TB HDD partitioned into C (windows installation) and another partition for storing media (movies, music, etc.), and a HDD from an old PC for extra storage (no data on it at the moment). I performed the Malwarebytes scan on all the drives. MSE and Malwarebytes did not report any infections.

    I ran CHKDSK only for C, followed by system file checker. I'm not sure if CHKDSK rectified any errors or bad sectors, but system file checker did not find any problems. I've attached logs from Event Viewer.

    However, this problem arose last weekend, but when I was using my PC to run all the scans it didn't occur again. I'm not sure if it's somehow resolved itself? I hope it's not a hardware/heating issue or anything
      My Computer


  4. Posts : 17
    windows 7 home premium 64bit
    Thread Starter
       #4

    Also, is it recommended to continue using MSE and Malwarebytes as antivirus and anti-spyware respectively?
      My Computer


  5. Posts : 1,413
    Windows 7 Home Premium x64
       #5

    It may have just been Avast. Use your PC as you normally would and see how things progress.

    Yes, continue to use MSE as your AV. You may scan with MBAM whenever you like.
      My Computer


  6. Posts : 17
    windows 7 home premium 64bit
    Thread Starter
       #6

    Okay, I thought the problem was solved, but now it has occurred again.

    The PC seemed okay for a few weeks after uninstalling MSE and spybot, and it was working fine. However, today it started to hang and become unresponsive again, while I was running DOTA2. It was completely unresponsive, so I had to reboot with the power button. The intervals between reboot and crash seemed to be growing shorter, down to a few minutes. After the third crash, I opened firefox, shortly after the screen flashed black (about 1 sec) and windows displayed the following error message:

    "Display Driver NVIDIA Windows Kernel Mode Driver version 301.42 stopped responding and successfully recovered".

    However, the PC remained similarly unresponsive. I rebooted again into safe mode to write this, and so far there are no problems. I'm still using MSE, however spybot S&D resident appears to still be in my system tray, although it says it has 0 known signatures, despite I having uninstalled it.

    Please advise? Thanks

    EDIT: I'm using a Palit GTX560 card, still under warranty, and the WHQL certified 301.42 drivers. The driver has crashed before, and i've received that error message, both using this driver and older drivers. But this is the first time it's stopped responding after recovering. I've RMA-ed this card before, so this is actually the second card (see this thread for details). The first one was a GTX560, i think this one is a factory overclocked gtx560.

    EDIT: I tried redownloading the 301.42 drivers from NVIDIA and performed a clean reinstall of the drivers. It seemed okay for a while, and I was able to play portal2 for more than an hour with no problem. However, when I launched Saints Row:The Third, the PC froze again within a few seconds. I'm launching all the games through Steam.

    EDIT: It's crashed a few more times again, including when running Saint's Row and DOTA2 again
    Last edited by syalam; 15 Jul 2012 at 09:55.
      My Computer


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

    Your display card recovered crash is akin to a 0x116 BugCheck blue screen.

    BugCheck 0x116

    These crash are DirectX/graphics card related. DirectX comes installed with Windows, so this may indicate Windows corruption. It may also be that you have corrupted drivers or a graphics card hardware problem.

    • If you are overclocking any hardware, please stop.

    • Check Windows for corruption. Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations. Use OPTION THREE of SFC /SCANNOW Command - System File Checker to provide us with the sfcdetails.txt file if errors occur.



    Follow the steps for Diagnosing basic problems with DirectX. To re-install your display card drivers as outlined in the DirectX link, use the following steps.

    1. Download the drivers you want for your display card(s)
    2. Click Start Menu
    3. Click Control Panel
    4. Click Uninstall a program
    5. For NVIDIA:
      • Uninstall the NVIDIA Graphics Driver (this should uninstall all NVIDIA software and drivers)
      • Restart your computer
      • Make sure NVIDIA 3D Vision Driver, NVIDIA 3D Vision Video Player, NVIDIA HD Audio Driver, and NVIDIA PhysX System Software are not still listed under Uninstall a program through Control Panel
      • If any remain of the above, uninstall one at a time
      • If asked to restart after uninstalling any of the above, do so, and continue uninstalling any remaining NVIDIA items until all are removed
    6. Restart your computer after uninstalling drivers for all display cards
    7. Install the driver you selected for the display cards once Windows starts


    Remember to try multiple versions of the graphics drivers, download them fresh, and install the freshly downloaded drivers.





       Warning
    Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. WARNING: The steps that follow can void your warranty!!!


    For 0x116 Video TDR Error crashes:

    • 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. Let us know if you need further help.
      My Computer


  8. Posts : 17
    windows 7 home premium 64bit
    Thread Starter
       #8

    Hi,

    Okay, thanks for the advice, I just got back so I'm going to try the steps now. But I'm running a factory overclocked Palit GTX560, should I try to downclock it? And if so, could you give me instructions? Thanks
      My Computer


  9. Posts : 17
    windows 7 home premium 64bit
    Thread Starter
       #9

    I've run system file checker thrice, each time it came up with no problems. I've also followed the advice in the DirectX diagnostic, as well as performing clean installs of the WHQL certified 301.42 driver for NVIDIA cards.

    I downloaded and ran the FurMark stress test. The first time I ran the BurnIn Test, at which point the system crashed after about 15 seconds, at a temperature of 76°C. I opened a side panel and rebooted, running the Benchmark test. This time it crashed after about 20 seconds, at a temperature of 70°C. I'm going to run the GIMPS stress test. I'm using a 600W power supply, which should be enough? I haven't got anything else in the PCI slots, only have two HDDs and running a USB soundcard, so it shouldn't be a lack of power problem?

    I'm going to try running it with a side panel open for the time being, and try and get my hands on a fan, but it's not a viable long term solution. How should I go about reducing the clock rate from the factory overclock? Also, it's a custom rig I got put together at a shop, should I go back and perhaps get another fan or something?
      My Computer


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

    This does not seem like an overheating issue. If the card is factory overclocked, the overclock is likely applied properly and nothing to worry about.

    When you say it stops responding, can you move the mouse?

    Have you gotten the message that the display card stopped responding and recovered recently?
      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 04:14.
Find Us