Variety of BSOD mostly BCCode 116 probably some driver


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

    Variety of BSOD mostly BCCode 116 probably some driver


    Been having multiple BSODs while trying to start up steam games, most notably Mount and Blade, all the blue screens suggest driver failures. I've already tried updates but the windows driver manager says their all up to date. An attempted auto update from the Intel site had the most recent crash. Other games and programs seem to work but they are less processing intensive.
      My Computer


  2. Posts : 15,026
    Windows 10 Home 64Bit
       #2

    MSINFO32:
    Please go to Start and type in "msinfo32.exe" (without the quotes) and press Enter
    Save the report as an .nfo file, then zip up the .nfo file and upload/attach the .zip file with your next post.
    Also, save a copy as a .txt file and include it also (it's much more difficult to read, but we have greater success in getting the info from it).

    systeminfo:
    Please open an elevated (Run as administrator) Command Prompt and type (or copy/paste) "systeminfo.exe >%USERPROFILE%\Desktop\systeminfo.txt" (without the quotes) and press Enter. Then navigate to Desktop to retrieve the syteminfo.txt file. If you have difficulties with making this work, please post back. Then zip up the .txt file and upload/attach the .zip file with your next post.

    Perform steps as mentioned on this thread: STOP 0x116: VIDEO_TDR_ERROR troubleshooting

    Start up updating the ATI drivers to the latest..

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 116, {fffffa8005c87010, fffff880042b12dc, 0, 2}
    
    Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for atikmpag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
    Probably caused by : atikmpag.sys ( atikmpag+72dc )
    
    Followup: MachineOwner
    ---------
    
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: fffffa8005c87010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff880042b12dc, The pointer into responsible device driver module (e.g. owner tag).
    Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
    Arg4: 0000000000000002, Optional internal context dependent data.
    
    Debugging Details:
    ------------------
    
    
    FAULTING_IP: 
    atikmpag+72dc
    fffff880`042b12dc 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_COMMAND:  .bugcheck ; kb
    
    FOLLOWUP_IP: 
    atikmpag+72dc
    fffff880`042b12dc 4883ec28        sub     rsp,28h
    
    SYMBOL_NAME:  atikmpag+72dc
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: atikmpag
    
    IMAGE_NAME:  atikmpag.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4d4c4b35
    
    FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys
    
    BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys
    
    Followup: MachineOwner
    ---------
    
    1: kd> lmvm atikmpag
    start             end                 module name
    fffff880`042aa000 fffff880`042f7000   atikmpag T (no symbols)           
        Loaded symbol image file: atikmpag.sys
        Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
        Image name: atikmpag.sys
        Timestamp:        Sat Feb 05 00:53:41 2011 (4D4C4B35)
        CheckSum:         000523CE
        ImageSize:        0004D000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Follow steps in the guide by Capt Jack Sparrow - Bug Check 0x116: VIDEO_TDR_ERROR Troubleshooting Tips | Captain Debugger

    TVeblen said:
    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 Computer


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

    Sudden change


    I'm first posting the diagnostic information you requested before troubleshooting. Also, on my most recent startup, my PC had another BSOD and restarted normally, then installed (or reinstalled) drivers associated with the audio, video, and networking hardware, but everything seems to be working. Does this mean anything to you?
      My Computer


  4. Posts : 15,026
    Windows 10 Home 64Bit
       #4

    Uninstall your current antivirus as it is contributing to your BSOD's. Replace with Microsoft Security Essentials & the Free version of Malwarebytes, update and make full scans separately:
    • Do not start the trial version of MalwareBytes

    You may also take a look at:
    Reduce items at start up:
    Your Antivirus software is basically whats just needed there.

    Make scans with -

    Use the System File Checker tool and Run Disk Check:

    Monitor hardware temperature with system monitoring software like Speccy or HWMonitor:


    Let us know if you still get BSOD's.
      My Computer


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

    Is it really necessary to remove mcaffee antivirus? It's worked pretty well in the past and I would rather remove whatever is conflicting with it. Also can you find any particular driver problems since that seems to be referenced in other BCCode 116 threads. I will try the file and root-kit checker suggestions.
      My Computer


  6. Posts : 15,026
    Windows 10 Home 64Bit
       #6

    Good luck.
      My Computer


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

    A couple questions, since the only thing that's happened around the start of these errors appears to be windows updates listed as being security updates does this mean that those are conflicting with McAffee and windows lists the 3rd party software as the source of the problems? Can I just turn off McAffee to see if this has an effect before uninstalling software I've payed for? I also have the chance to install a visual studio 2010 service update 1, has this had any effect on driver errors?
      My Computer


  8. Posts : 15,026
    Windows 10 Home 64Bit
       #8

    grundmwm said:
    Can I just turn off McAffee to see if this has an effect before uninstalling software I've payed for? I also have the chance to install a visual studio 2010 service update 1, has this had any effect on driver errors?
    You can try, I'm not sure.
      My Computer


 

  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 16:55.
Find Us