Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD when browsing or idle

27 Jun 2013   #1
espica

Windows 7 Home Premium 64bit
 
 
BSOD when browsing or idle

Hello.

I have an Asus G74S, I've had some problems with it hanging after turning it back ON from sleep. I put it to Hibernate all the time now. It still hangs from time to time but it's not often.

I don't remember exactly when the video started to crash, it recovered but some icons were missing from the clock area. I've noticed it happens more often when I left the laptop idle for some time.

Not long ago it started to freeze for a few seconds at a time, the mouse pointer doesn't move, keyboard doesn't register. It happens at least twice a day. I updated the wireless card drivers today because I read the old drivers I had are known to cause problems.

This month my laptop started to reboot on its own. The screen turns black (turns OFF I think) and after some seconds the laptop restarts. It's happening more often, not every day though.

I attached a file with the info gathered by SF Diagnostic Tool.
Also, I don't know if this is included in that info, this is the screen that Windows display after rebooting from the crash:
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 116
BCP1: FFFFFA8012666010
BCP2: FFFFF880059C4010
BCP3: 0000000000000000
BCP4: 000000000000000D
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\062713-35427-01.dmp

Thanks in advance.


My System SpecsSystem Spec
.
27 Jun 2013   #2
espica

Windows 7 Home Premium 64bit
 
 

I just had a video crash.
Not sure what to do so I got an info grab again.
My System SpecsSystem Spec
28 Jun 2013   #3
koolkat77

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit
 
 

Follow steps in the guide by Capt Jack Sparrow - Bug Check 0x116: VIDEO_TDR_ERROR Troubleshooting Tips | Captain Debugger

Quote   Quote: Originally Posted by TVeblen View Post
What you are experiencing is a TDR event (Timeout Detection & Recovery). There are many causes of these events, mostly hardware related. Please read my checklist below and see if you can diagnose your particular cause.

A couple of things jump out immediately. Your specs say you have 5GB of RAM, an odd number. That suggests that you added some RAM at some point. Mismatched or failing RAM modules can cause TDRs. You might want to test those sticks one at a time in Slot 1 before anything else. RAM problems can explain some of your other issues too.

Looking at some of your other posts I see you are running dual monitors also. This could be exposing a defect in your 9500GT that is triggering the TDRs. You should test with only one monitor attached to see if this is the case.

You are running lots of stuff on that box, so I would be as deliberate as possible in doing the diagnostic work.

*******
"Display driver xxxxx stopped responding and was recovered"

Timeout Detection & Recovery (TDR) = "Display Driver Stopped Responding and was Recovered" is a useful feature that started in Vista and is also in W7 that allows the OS to try and recover from a video timeout so that the system does not crash to a bluescreen. Symptoms included a screen flash with the TDR message appearing one or more times or the screen blinking out to black. If the system cannot recover it will crash (Stop Error 116 typical). The issue is that the video card is not responding as expected. The solution is in the: why?

There is no one-size-fits-all solution to TDR errors. But the problem is usually found in the local environment (your computer). Finding the cause is a matter of checking every possible cause and uncovering the culprit through a simple process of elimination. By methodically running down a checklist of diagnostic procedures you should be able to find the cause and can correct it.

There are numerous reports of hardware solutions to TDR's. The most common are:
  • Poor Cooling
  • Problems with the power supply
  • Overclocking Issues
  • Bad System memory or incorrect memory timings
  • Defective PC Components

The order you do the diagnostics is not all that important. My personal strategy is to do the cheap & easy stuff first, the cheap & harder stuff next, and then the stuff that costs last. But whatever order you do it in you need to check or confirm the following:

SOFTWARE
Poorly written software and games will cause TDRs. But if this were the case it would affect lots of people, not just a few. Check the game's website & forums for patches and tips.
See if other people in the forums are having the same problem and if they were able to solve it and how.
You could also be asking too much of your video card. Check to see if your video card is tested and recommended for the game/program. Test the game at reduced settings.

WHAT ACTIONS CAUSE THE PROBLEM
It helps if you can isolate the actions that trigger the TDR. Most often it will be an application using 3D graphics. But if the incidents occur constantly it would point more towards defective hardware. If it happens more specifically (just when running Game X) it points towards overheating, settings, software, or driver issues.

GENERAL SYSTEM PERFORMANCE
You need to eliminate the possibility that your computer has a global problem. You can use a program like Prime95 to stress test your system. Free Software - GIMPS
You can run the "Stress Test" for a few hours or overnight. This will not tell you what the problem is, but it is helpful to uncover any issues your system has with instability and cooling.

OVERHEATING
Running a video intensive game for hours can generate some serious heat and overheating will cause video errors. You can check your temps by looking at your BIOS readings or use a free program like Speedfan SpeedFan - Access temperature sensor in your computer .
A real easy test is to just pull the side panel(s) off your case (You can also blow a house fan directly into the open case) and see if the problem goes away or gets better. If it does then the issue is definitely overheating. If you are overheating you need to look at installing some cooling upgrades. You want to look at ventilating the case (more or bigger fans), Upgrade your case to a larger gaming case (lots of fans, water-cooling), etc.
There are free utilities like BurninTest PassMark BurnInTest software - PC Reliability and Load Testing that you can use to test your system's cooling capability. Caution is recommended using these types of programs.

VIDEO DRIVERS
Bad drivers happen and they can get corrupted. Before installing or reinstalling any video drivers first completely uninstall all video software and the drivers. (Some people say to run a cleaner program from safe mode, some say this is unnecessary). Never rely on the driver package to overwrite the old drivers. Also: Delete the video driver folder (ex: C:\NVIDIA) in Windows Explorer (or windows may install the same drivers again!).
After uninstalling the old drivers and rebooting Windows 7 will install it's own WDDM 1.1 driver. Check for the video problem while using the generic Windows driver.
You can then install the latest drivers for your card (or try older drivers).
See This Tutorial: Installing and updating drivers in 7

DEVICE MANAGER
Look in Device Manager and make sure there are no problem devices (yellow ! icon). Correct these by loading the correct drivers or disable the problem device and see if the video problem goes away.

POOR CONNECTIONS
Reseat video card and memory modules. Make sure the contacts are clean. Check all the electrical connections.

CHECK YOUR MOTHERBOARD VOLTAGES
In BIOS, check the listed voltages against the manufacturer recommended specs. Reset the voltages to factory defaults and see if the video problems disappear.

MEMORY
Memory errors can cause video problems. Run a program like Memtest86+ for at least 3 passes to see if there are any memory errors. Memtest86+ - Advanced Memory Diagnostic Tool .
You can also test for a bad memory module by installing one stick and testing, and then switch it out for the next stick, etc.

OVERCLOCKING
Overclocking can be a trial and error process. The clocks and/or multipliers you set or change for CPU, Memory, or GPU could be unstable. Eliminate this as a possibility by resetting these to their defaults to see if that clears the video problems. The simplest way to do this is to "Restore Bios Defaults", or Clear CMOS.

UNDERCLOCKING
Some people have reported that by going into the video cards control panel and "down-clocking" the cards performance settings they were able to clear up the TDRs. Since W7 does not seem to tolerate any hiccups in the GPU, this would allow you to run a poor perforning card in the W7 enviroment.
So for instance, you could set the GPU clock from a 777 MHz factory setting to 750MHz, and the ram clock from a 1126MHz factory setting to 1050Mhz, or similar small change for your particular card.

BIOS
Check for and install an updated BIOS, particularly if it says the newer BIOS corrects memory errors or bug fixes. You could also try loading the BIOS defaults.
While you are there, check the motherboard manufacturers forums to see if others are having issues with the same board.

WINDOWS POWER MANAGEMENT
Eliminate Power Management settings as a possible cause, especially if you are working with a laptop. These settings could be particularly important if the issue is in playing games.
Go to Control Panel > Hardware & Sound > Power Options. Under "Select a Power Plan" you will find that "Balanced" is the default setting.
At the bottom you will see a Down arrow next to "Show Additional Plans". Click that and select "High Performance". See if the TDR issue is affected.
Alternately, you can click "Change Plan Settings" next to the "Balanced" plan and change the setting to "Never" put the computer to sleep (This is the default on a desktop) and/or change when the display is turned off as a test.

POWER SUPPLY
You need to know that your power supply is delivering sufficient power. Power supply problems are the most common cause of video problems, especially using high end cards.
Check the power supply's amperage ratings. Be sure it has the ample amperage for your video card and the rest of the system.
Test the supply with multimeter to measure for a steady 12v to the card's power connectors. (The only true way to test a power supply would be to use the very expensive diagnostic equipment used in labs). But for us regular folks: I tested my power supply by hooking up my multimeter to the PCI-E connectors that I was using to power my video card (I used a spare pair from the power supply to run the card while I was testing). I then observed the meter while I used the computer, first watching the voltage, then the amps, to see if there was any drop-off or erratic behavior while booting or using the computer. My readings were rock solid. So I declared my power supply good.
Otherwise you need to replace the supply to eliminate this possibility. Or borrow one from another computer.

VIDEO CARD
I suspect that a video card must perform flawlessly to operate in a Windows 7 environment and run the most recent games. If you tried all the above diagnostics and no problems were found then that leaves you with only one possibility: a defective video card. Some brands have the problem more consistently than others. You could check their forums for clues.
You could try your card in another computer running W7 to see if the problem goes along with the card.
You could try a different card in your computer. I bought an inexpensive card to use. My TDR's disappeared using a "lesser" card. Or borrow a card from another computer.
Otherwise RMA or replace the card.

TDR complaints have come from PC owners running virtually every PC configuration. They occur regardless of which video engine, manufacturer, driver, or system used. They are too numerous to write off as a random problem, but at the same time if people are getting their systems to run correctly using the same hardware and software that you are then it follows that your problem must be solvable.

More Info Here:
Timeout Detection and Recovery of GPUs through WDDM
NVIDIA Statement on TDR Errors - NVIDIA Forums
27116: ATIKMDAG has stopped responding error message
My System SpecsSystem Spec
.

28 Jun 2013   #4
espica

Windows 7 Home Premium 64bit
 
 

I did a fresh install of the latest video drivers. I haven't had any crashes so far.

I'm going to do the GIMPS test tonight. I tried it to make sure it works, I got temperatures in the cores in the 94-100 degrees range. GPU was 74 or so.
Using RealTemp3.70 the temperatures right now (only Firefox and Steam windows) are in the 61-66 range. GPU is 58
Are these high temperatures? While running GIMPS what are expected temperatures?

I also downloaded the memory test and video memory test applications. I'll do the memory test before the GIMPS.

Thanks.
My System SpecsSystem Spec
28 Jun 2013   #5
Britton30
Microsoft MVP

Windows 7 Ultimate X64 SP1
 
 

Your CPU temps are at the max. Intel Core i7-2630QM Mobile processor - FF8062700837005
don't rum Prime95 until you can run cooler, max of about 80-85C. It should not be over 50C-60C unless you are testing. Clean all your vents with compressed canned air and use it on a hard surface, a cooling pad may be in order.
My System SpecsSystem Spec
29 Jun 2013   #6
espica

Windows 7 Home Premium 64bit
 
 

I did the memory test. It took close to one day to complete it. It made 8 passes, no errors.

I'm going to clean the air vents now. I'll check the temperatures before doing the next test, hopefully the laptop will run cooler.
My System SpecsSystem Spec
29 Jun 2013   #7
espica

Windows 7 Home Premium 64bit
 
 

I dusted my laptop, put a cooling pad under it too.
Temperature now is between 42-47
GPU is 42
Only Steam and two Firefox windows open.
Good temp for doing the Prime95 test?

Now I feel bad for leaving my laptop ON for almost a day doing the memory test.
My System SpecsSystem Spec
29 Jun 2013   #8
espica

Windows 7 Home Premium 64bit
 
 

It just froze again. I'm going to start the Prime95 in an hour or so.

Other problem, when I cleaned the vents I only removed the battery and the HDD, RAM cover, I didn't move anything inside, now when Windows asks me for my user password the keyboard doesn't work, I have to put the laptop to hibernate and after I turn it ON again the keyboard works again.
My System SpecsSystem Spec
29 Jun 2013   #9
koolkat77

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit
 
 

Perform a clean boot and see if that makes a difference.
Troubleshoot a Problem by Performing a Clean Startup in Windows 7 or Vista

Norton
Code:
SRTSP64.SYS                 Tue Apr 23 04:26:52 2013 (5175B92C)
SRTSP64.SYS                 Sat Jan 26 03:26:16 2013 (5102F878)
SRTSPX64.SYS                Sat Jan 26 03:30:05 2013 (5102F95D)
SYMDS64.SYS                 Fri Apr 26 05:19:47 2013 (5179BA13)
SYMDS64.SYS                 Thu Jan 17 07:56:45 2013 (50F75A5D)
SYMEFA64.SYS                Sat Jan 19 06:31:37 2013 (50F9E969)
SYMEVENT64x86.SYS           Wed Aug 22 11:33:18 2012 (50346F1E)
SYMEVENT64x86.SYS           Thu May 24 06:52:24 2012 (4FBD8648)
SYMNETS.SYS                 Wed Apr 10 05:24:13 2013 (5164A31D)
SYMNETS.SYS                 Sat Jul 21 08:07:07 2012 (500A0ECB)
IDSvia64.sys                Wed Aug 29 08:48:40 2012 (503D8308)
Ironx64.SYS                 Tue Jul 24 06:34:50 2012 (500DEDAA)
BHDrvx64.sys                Tue May 21 02:47:31 2013 (519A8BE3)
ENG64.SYS                   Fri Apr 26 12:10:48 2013 (517A1A68)
EX64.SYS                    Fri Apr 26 12:08:58 2013 (517A19FA)
EraserUtilRebootDrv.sys     Wed Aug  1 05:36:50 2012 (50186C12)
Norton tends to cause BSOD-s and seen it create several issues for users. Recommend uninstalling it with the Norton Removal Tool and replace with Microsoft Security Essentials. See if this stops the BSOD-s. Download and run the Norton Removal Tool to remove the Norton Product

Microsoft Security Essentials and Malwarebytes are recommended from a strict BSOD perspective. They do not cause blue screens on the system as other AV products do.

Microsoft Security Essentials, Free antivirus for windows and Malwarebytes Anti-Malware Free

information   Information
  • Do not start the free trial of MalwareBytes, unselect that option when prompted.


  • Update and make full scans with both separately.

Kaspersky TDSSKiller - How to remove malware belonging to the family Rootkit.Win32.TDSS (aka Tidserv, TDSServ, Alureon)

ESET online scanner - One-time virus scanner free with ESET online scanner

Disk Check
For errors on your Hard drive(s): How to Run Disk Check in Windows 7

Asus Charger Driver Likely BSOD cause. Please remove the software with Revo Uninstaller Free.
Code:
AiCharger.sys               Fri Sep 23 08:04:40 2011 (4E7BE938)
Revo Uninstaller
Download and install Revo Uninstaller free from here: Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems

Opt for "Advanced Mode" and uninstall the software (also delete the leftover registry entries).

BSOD BUGCHECK SUMMARY
Code:
Debug session time: Thu Jun 27 13:43:15.724 2013 (UTC + 6:00)
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime: 1 days 6:41:25.738
*** 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+13b010 )
BugCheck 116, {fffffa8012666010, fffff880059c4010, 0, d}
BugCheck Info: VIDEO_TDR_FAILURE (116)
Bugcheck code 00000116
Arguments: 
Arg1: fffffa8012666010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880059c4010, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 000000000000000d, Optional internal context dependent data.
BUGCHECK_STR:  0x116
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
MaxSpeed:     2000
CurrentSpeed: 1995
BiosVersion = G74Sx.201
BiosReleaseDate = 04/27/2011
SystemManufacturer = ASUSTeK Computer Inc.
SystemProductName = G74Sx
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Debug session time: Wed Jun 26 07:00:40.260 2013 (UTC + 6:00)
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime: 1 days 1:56:01.275
*** 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+13b010 )
BugCheck 116, {fffffa80141064e0, fffff88006784010, 0, d}
BugCheck Info: VIDEO_TDR_FAILURE (116)
Bugcheck code 00000116
Arguments: 
Arg1: fffffa80141064e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88006784010, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 000000000000000d, Optional internal context dependent data.
BUGCHECK_STR:  0x116
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
MaxSpeed:     2000
CurrentSpeed: 1995
BiosVersion = G74Sx.201
BiosReleaseDate = 04/27/2011
SystemManufacturer = ASUSTeK Computer Inc.
SystemProductName = G74Sx
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Debug session time: Mon Jun 17 09:51:42.670 2013 (UTC + 6:00)
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime: 0 days 10:51:51.033
*** 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+13b010 )
BugCheck 116, {fffffa80118394e0, fffff880059ca010, 0, d}
BugCheck Info: VIDEO_TDR_FAILURE (116)
Bugcheck code 00000116
Arguments: 
Arg1: fffffa80118394e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880059ca010, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 000000000000000d, Optional internal context dependent data.
BUGCHECK_STR:  0x116
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
MaxSpeed:     2000
CurrentSpeed: 1995
BiosVersion = G74Sx.201
BiosReleaseDate = 04/27/2011
SystemManufacturer = ASUSTeK Computer Inc.
SystemProductName = G74Sx
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
My System SpecsSystem Spec
01 Jul 2013   #10
espica

Windows 7 Home Premium 64bit
 
 

I uninstalled Asus Charger Driver with Revo Uninstaller, I thought it had solved the problem after seven or so hours running with no problems but then I got a video crash.

I'm going to do a Clean Startup and leave the laptop idle for a few hours or until the video crashes or BSOD.

Could Power4Gear cause the BSOD problem?
My System SpecsSystem Spec
Reply

 BSOD when browsing or idle




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD during regular use (gaming, web browsing), and when idle
I have had HDD issues for the past few months, back in August I ran a thorough hard drive test on it and found out I had a bad (hard) sector within it and would need to replace it soon. Now it is late December and I still don't have a new hard drive, so I am sure some of these problems have occured...
BSOD Help and Support
Random BSOD ntoskrnl.exe mostly while browsing, or idle
so I got many BSOD lately, with different bug check string. I don't know what the cause, so pls help me, thx
BSOD Help and Support
BSoD randomly during gameplay or web browsing or even Idle
System Information: Windows 7 Home Premium 64bit Intel i7 2600 ASUS P8Z68-V LE motherboard 8GB GSkill ram Nvidia GeForce GTS 450 Recently reformatted, about 2 weeks ago.(Also happens before this reformat on a different HDD) I've just gotten this new setup for maybe half a year now, and...
BSOD Help and Support
BSOD during idle/browsing/games (driver power state failure)
Windows 7 Home Premium 64 bit. I installed it myself but the case windows came in says OEM. 2 months old computer. Attached dump file. Thanks in advance.
BSOD Help and Support
Blue screening on Idle or web browsing
Been having a weird issue with my system. Basically the system will only BSoD if it's idle or I'm just browsing the Internet or using Word or another small program. I'm sure it's not a fault with the hardware as it runs in 32 bit fine (Although I could be very wrong!). Only thing I reckon it is...
BSOD Help and Support
BSOD, During all but Idle (Web browsing, File system work)
Is Windows 7 . . . - x86 (32-bit) or x64 ? x64 - the original installed OS on the system? No, but I installed clean. - an OEM or full retail version? Retail of Pro - What is the age of system (hardware)? Old 2 years of run time or more - What is the age of OS installation (have you...
BSOD Help and Support


Our Sites

Site Links

About Us

Find 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:27.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App