Go Back   Tech Support Forum > Microsoft Support > BSOD, App Crashes And Hangs


[SOLVED] System Crashing BSOD, need help

This is a discussion on [SOLVED] System Crashing BSOD, need help within the BSOD, App Crashes And Hangs forums, part of the Tech Support Forum category.


Reply
 
Thread Tools Search this Thread
Old 01-17-2014, 05:09 PM   #1
Registered Member
 
Join Date: Jan 2014
Posts: 10
OS: Win 7



thanks, i hope you can help me, let me know if i am missing anything

OS - Windows 7
x64
original installed OS - win 7
the OS an OEM version (came pre-installed on system) (alienware, Dell)
Age of system (hardware) - almost 3 years
Age of OS installation - have you re-installed the OS? i have done some factory image reseting, last one about a month ago when problems started
CPU - Intel(R) Core(TM) i7 CPU 930 @ 2.80GHz, 2800 Mhz, 4 core
Video Card - Nvidia geforce GTX 570 (1 year and a half)
System Manufacturer - Alienwere aurora ALX
Exact model number - aurora ALX
Attached Files
File Type: rar BSOD data and perfmon report.rar (1.56 MB, 33 views)
Zantay is offline   Reply With Quote
Sponsored Links
Advertisement
 
Old 01-18-2014, 01:41 AM   #2
TSF Enthusiast
 
Patrick's Avatar

Microsoft Most Valuable Professional
 
Join Date: Apr 2012
Location: Ring 0
Posts: 4,349
OS: W8.1 x64



Hi,

All of the attached DMP files are of the VIDEO_TDR_FAILURE (116) bug check.

This indicates that an attempt to reset the display driver and recover from a timeout failed.

So, let me now explain what VIDEO_TDR_ERROR means. First off, TDR is an acronym for 'Timeout Detection and Recovery'. Timeout Detection and Recovery was introduced in Vista and carried over to Windows 7. Rather than putting exactly what Timeout Detection and Recovery does exactly, I'll just directly quote the MSDN article!
Timeout detection:
The GPU scheduler, which is part of the DirectX graphics kernel subsystem (Dxgkrnl.sys), detects that the GPU is taking more than the permitted amount of time to execute a particular task. The GPU scheduler then tries to preempt this particular task. The preempt operation has a "wait" timeout, which is the actual TDR timeout. This step is thus the timeout detection phase of the process. The default timeout period in Windows Vista and later operating systems is 2 seconds. If the GPU cannot complete or preempt the current task within the TDR timeout period, the operating system diagnoses that the GPU is frozen.
To prevent timeout detection from occurring, hardware vendors should ensure that graphics operations (that is, DMA buffer completion) take no more than 2 seconds in end-user scenarios such as productivity and game play.
Preparation for recovery:
The operating system's GPU scheduler calls the display miniport driver's DxgkDdiResetFromTimeout function to inform the driver that the operating system detected a timeout. The driver must then reinitialize itself and reset the GPU. In addition, the driver must stop accessing memory and should not access hardware. The operating system and the driver collect hardware and other state information that could be useful for post-mortem diagnosis.
Desktop recovery:
The operating system resets the appropriate state of the graphics stack. The video memory manager, which is also part of Dxgkrnl.sys, purges all allocations from video memory. The display miniport driver resets the GPU hardware state. The graphics stack takes the final actions and restores the desktop to the responsive state. As previously mentioned, some legacy DirectX applications might render just black at the end of this recovery, which requires the end user to restart these applications. Well-written DirectX 9Ex and DirectX 10 and later applications that handle Device Remove technology continue to work correctly. An application must release and then recreate its Direct3D device and all of the device's objects. For more information about how DirectX applications recover, see the Windows SDK.
Article here.
With this being said, if Timeout Detection and Recovery fails to recover the display driver, it will then shoot the 0x116 bugcheck. There are many different things that can cause a 0x116, which I will explain below:

(Ensure you have the latest video card drivers. If you are already on the latest video card drivers, uninstall and install a version or a few versions behind the latest to ensure it's not a latest driver only issue. If you have already experimented with the latest video card driver and many previous versions, please give the beta driver for your card a try.)

The following hardware issues can cause a TDR event:

1. Unstable overclock (CPU, GPU, etc). Revert all and any overclocks to stock settings.

2. Bad sector in memory resulting in corrupt data being communicated between the GPU and the system (video memory otherwise known as VRAM or physical memory otherwise known as RAM).

GPU testing: Furmark, run for ~15 minutes and watch temperatures to ensure there's no overheating and watch for artifacts.

RAM testing: Memtest - Refer to the below:

Memtest:

Memtest86+:

Download Memtest86+ here:

Memtest86+ - Advanced Memory Diagnostic Tool

Which should I download?

You can either download the pre-compiled ISO that you would burn to a CD and then boot from the CD, or you can download the auto-installer for the USB key. What this will do is format your USB drive, make it a bootable device, and then install the necessary files. Both do the same job, it's just up to you which you choose, or which you have available (whether it's CD or USB).

How Memtest works:

Memtest86 writes a series of test patterns to most memory addresses, reads back the data written, and compares it for errors.

The default pass does 9 different tests, varying in access patterns and test data. A tenth test, bit fade, is selectable from the menu. It writes all memory with zeroes, then sleeps for 90 minutes before checking to see if bits have changed (perhaps because of refresh problems). This is repeated with all ones for a total time of 3 hours per pass.

Many chipsets can report RAM speeds and timings via SPD (Serial Presence Detect) or EPP (Enhanced Performance Profiles), and some even support changing the expected memory speed. If the expected memory speed is overclocked, Memtest86 can test that memory performance is error-free with these faster settings.

Some hardware is able to report the "PAT status" (PAT: enabled or PAT: disabled). This is a reference to Intel Performance acceleration technology; there may be BIOS settings which affect this aspect of memory timing.

This information, if available to the program, can be displayed via a menu option.

Any other questions, they can most likely be answered by reading this great guide here:

FAQ : please read before posting

3. Corrupt hard drive or Windows install / OS install resulting in corruption to the registry or page file.

HDD diagnostics: Seatools - Refer to the below:

SeaTools | Seagate

You can run it via Windows or DOS. Do note that the only difference is simply the environment you're running it in. In Windows, if you are having what you believe to be device driver related issues that may cause conflicts or false positive, it may be a wise decision to choose the most minimal testing environment (DOS).

Run all tests EXCEPT: Fix All, Long Generic, and anything Advanced.

To reset your page file, follow the instructions below:

a ) Go to Start...Run...and type in "sysdm.cpl" (without the quotes) and press Enter.

- Then click on the Advanced tab,
- Then on the Performance Settings Button,
- Then on the next Advanced tab,
- Then on the Virtual Memory Change button.

b ) In this window, note down the current settings for your pagefile (so you can restore them later on).

-Then click on the "No paging file" radio button, and

- then on the "Set" button. Be sure, if you have multiple hard drives, that you ensure that the paging file is set to 0 on all of them.

-Click OK to exit the dialogs.

c ) Reboot (this will remove the pagefile from your system)

d ) Then go back in following the directions in step a ) and re-enter the settings that you wrote down in step

b ). Follow the steps all the way through (and including) the reboot.

e ) Once you've rebooted this second time, go back in and check to make sure that the settings are as they're supposed to be.

Run System File Checker:

SFC.EXE /SCANNOW

Go to Start and type in "cmd.exe" (without the quotes)

At the top of the search box, right click on the cmd.exe and select "Run as adminstrator"

In the black window that opens, type "SFC.EXE /SCANNOW" (without the quotes) and press Enter.

Let the program run and post back what it says when it's done.

- Overheating of the CPU or GPU and or other components can cause 0x116 bugchecks. Monitor your temperatures and ensure the system is cooled adequately.

- GPU failure. Whether it's heat, power issue (PSU issue), failing VRAM, etc.

The following software issues can cause a TDR event:

- Incompatible drivers of any sort

- Messy / corrupt registry

- Corrupt Direct X - How to install the latest version of DirectX

- Corrupt system files (run System File Checker as advised above)

- Buggy and or corrupt 3rd party drivers. If you suspect a 3rd party driver being the issue, enable Driver Verifier:

Driver Verifier:

What is Driver Verifier?

Driver Verifier is included in Windows 8, 7, Windows Server 2008 R2, Windows Vista, Windows Server 2008, Windows 2000, Windows XP, and Windows Server 2003 to promote stability and reliability; you can use this tool to troubleshoot driver issues. Windows kernel-mode components can cause system corruption or system failures as a result of an improperly written driver, such as an earlier version of a Windows Driver Model (WDM) driver.

Essentially, if there's a 3rd party driver believed to be at issue, enabling Driver Verifier will help flush out the rogue driver if it detects a violation.

Before enabling Driver Verifier, it is recommended to create a System Restore Point:

Vista - START | type rstrui - create a restore point
Windows 7 - START | type create | select "Create a Restore Point"
Windows 8 - Restore Point - Create in Windows 8

How to enable Driver Verifier:

Start > type "verifier" without the quotes > Select the following options -

1. Select - "Create custom settings (for code developers)"
2. Select - "Select individual settings from a full list"
3. Check the following boxes -
- Special Pool
- Pool Tracking
- Force IRQL Checking
- Deadlock Detection
- Security Checks (Windows 7 & 8)
- DDI compliance checking (Windows 8)
- Miscellaneous Checks
4. Select - "Select driver names from a list"
5. Click on the "Provider" tab. This will sort all of the drivers by the provider.
6. Check EVERY box that is NOT provided by Microsoft / Microsoft Corporation.
7. Click on Finish.
8. Restart.

Important information regarding Driver Verifier:

- If Driver Verifier finds a violation, the system will BSOD.

- After enabling Driver Verifier and restarting the system, depending on the culprit, if for example the driver is on start-up, you may not be able to get back into normal Windows because Driver Verifier will flag it, and as stated above, that will cause / force a BSOD.

If this happens, do not panic, do the following:

- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.

- Once in Safe Mode - Start > type "system restore" without the quotes.

- Choose the restore point you created earlier.
If you did not set up a restore point, do not worry, you can still disable Driver Verifier to get back into normal Windows:

- Start > Search > type "cmd" without the quotes.

- To turn off Driver Verifier, type in cmd "verifier /reset" without the quotes.
・ Restart and boot into normal Windows.

How long should I keep Driver Verifier enabled for?

It varies, many experts and analysts have different recommendations. Personally, I recommend keeping it enabled for at least 24 hours. If you don't BSOD by then, disable Driver Verifier.

My system BSOD'd, where can I find the crash dumps?

They will be located in %systemroot%\Minidump

Any other questions can most likely be answered by this article:
Using Driver Verifier to identify issues with Windows drivers for advanced users

Regards,

Patrick
Patrick is offline   Reply With Quote
Old 01-18-2014, 11:53 AM   #3
Registered Member
 
Join Date: Jan 2014
Posts: 10
OS: Win 7



Hi Patrick, thank you for your quick answer, will try to do all those test, but my PC is crashing and every time is worst, is crashing before I even get the test started, any tip for this?
Zantay is offline   Reply With Quote
Old 01-18-2014, 01:05 PM   #4
Registered Member
 
Join Date: Jan 2014
Posts: 10
OS: Win 7



i ran Driver verifier and i got stuck on windows start up, after recovering windows in safe mode i ran windows debugger and i say that the crash was the same VIDEO_TDR_FAILURE (116), is it possible that the recovery deleted the crash dumb file from the verifier?

i also ran the furmark, and it ran for 15 min, with an average temp of 92 c, as i understand is high but not too much right, could the problem be on the temperature?
Zantay is offline   Reply With Quote
Old 01-18-2014, 01:46 PM   #5
TSF Enthusiast
 
Patrick's Avatar

Microsoft Most Valuable Professional
 
Join Date: Apr 2012
Location: Ring 0
Posts: 4,349
OS: W8.1 x64



92c is actually very high, yes. Furmark is a very intensive stress program, so your GPU may not reach those temperatures outside of that environment. What is the temperatures of the GPU when you're playing a game, etc, and not running Furmark?

Regards,

Patrick
Patrick is offline   Reply With Quote
Old 01-18-2014, 02:43 PM   #6
Registered Member
 
Join Date: Jan 2014
Posts: 10
OS: Win 7



I haven't paid much attention but around 50 or 60. C but it crashes even when is less than that, and it hold up for 15 min at 90
Zantay is offline   Reply With Quote
Old 01-18-2014, 03:03 PM   #7
TSF Enthusiast
 
Patrick's Avatar

Microsoft Most Valuable Professional
 
Join Date: Apr 2012
Location: Ring 0
Posts: 4,349
OS: W8.1 x64



Okay, it doesn't appear to be a temperature issue then. Run the rest of the diagnostics I've provided.

Regards,

Patrick
Patrick is offline   Reply With Quote
Old 01-18-2014, 03:15 PM   #8
Registered Member
 
Join Date: Jan 2014
Posts: 10
OS: Win 7



memory one came out clean, it passed without errors

i ran Driver verifier and i got stuck on windows start up, after recovering windows in safe mode i ran windows debugger and i say that the crash was the same VIDEO_TDR_FAILURE (116), is it possible that the recovery deleted the crash dumb file from the verifier?
Zantay is offline   Reply With Quote
Old 01-18-2014, 03:39 PM   #9
Registered Member
 
Join Date: Jan 2014
Posts: 10
OS: Win 7



And hard drive passed it short generic test

system file checker found some file broken and already repair them
Zantay is offline   Reply With Quote
Old 01-18-2014, 04:16 PM   #10
TSF Enthusiast
 
Patrick's Avatar

Microsoft Most Valuable Professional
 
Join Date: Apr 2012
Location: Ring 0
Posts: 4,349
OS: W8.1 x64



Quote:
memory one came out clean, it passed without errors
You went through ~8 passes that fast?

Regards,

Patrick
Patrick is offline   Reply With Quote
Old 01-18-2014, 04:18 PM   #11
Registered Member
 
Join Date: Jan 2014
Posts: 10
OS: Win 7



oh no, i think i misses some, it said test complete click esc to exit but it only had one pass, i will do it again
Zantay is offline   Reply With Quote
Old 01-19-2014, 08:32 AM   #12
Registered Member
 
Join Date: Jan 2014
Posts: 10
OS: Win 7



ok, 8 passes, no errors on Memtest
Zantay is offline   Reply With Quote
Old 01-19-2014, 03:57 PM   #13
TSF Enthusiast
 
Patrick's Avatar

Microsoft Most Valuable Professional
 
Join Date: Apr 2012
Location: Ring 0
Posts: 4,349
OS: W8.1 x64



Since SFC found errors, please run chkdsk:

Chkdsk:
There are various ways to run Chkdsk~


Method 1:

Start > Search bar > Type cmd (right click run as admin to execute Elevated CMD)

Elevated CMD should now be opened, type the following:

chkdsk x: /r

x implies your drive letter, so if your hard drive in question is letter c, it would be:

chkdsk c: /r

Restart system and let chkdsk run.

Method 2:


Open the "Computer" window
Right-click on the drive in question
Select the "Tools" tab
In the Error-checking area, click <Check Now>.

If you'd like to get a log file that contains the chkdsk results, do the following:

Press Windows Key + R and type powershell.exe in the run box

Paste the following command and press enter afterwards:

get-winevent -FilterHashTable @{logname="Application"; id="1001"}| ?{$_.providername –match "wininit"} | fl timecreated, message | out-file Desktop\CHKDSKResults.txt

This will output a .txt file on your Desktop containing the results of the chkdsk.

Regards,

Patrick
Patrick is offline   Reply With Quote
Old 01-21-2014, 04:53 PM   #14
Registered Member
 
Join Date: Jan 2014
Posts: 10
OS: Win 7



already check the HDD. all good, some errors were fixed

i'm not sure if its fixed but it isn't crashing for the last 2 days, could we have fixed it already?
Zantay is offline   Reply With Quote
Old 01-21-2014, 07:48 PM   #15
TSF Enthusiast
 
Patrick's Avatar

Microsoft Most Valuable Professional
 
Join Date: Apr 2012
Location: Ring 0
Posts: 4,349
OS: W8.1 x64



Maybe, maybe not. Keep me updated in the next few days.

Regards,

Patrick
Patrick is offline   Reply With Quote
Old 02-05-2014, 09:07 AM   #16
Registered Member
 
Join Date: Jan 2014
Posts: 10
OS: Win 7



hello Patrick, it has been more than a week without a crash, i think is safe to say is fixed.

so i think it was either a file in windows folder broken or the physical clean up that i made.

thank you very much for all your assistance :D
Zantay is offline   Reply With Quote
Old 02-05-2014, 05:49 PM   #17
TSF Enthusiast
 
Patrick's Avatar

Microsoft Most Valuable Professional
 
Join Date: Apr 2012
Location: Ring 0
Posts: 4,349
OS: W8.1 x64



My pleasure, glad to hear and good work.

Regards,

Patrick
Patrick is offline   Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Windows 7 x64 Crashing on Reboots
Operating System OS - Windows 7 64 bit Original OS - Windows 7 OEM version Shy of four years OS same age as system
Deletham_Tomala BSOD, App Crashes And Hangs 2 03-24-2013 02:14 PM
BSOD usb bugcode driver
Hi everybody, since now a few weeks I have a BSOD problem that occurs up to 4 times a day, rebooting my computer and it's seriously starting to piss me off... I followed the instructions on this page of the forum so if anybody could help me with this proble it would be great, as I need my...
hub151 BSOD, App Crashes And Hangs 3 02-06-2013 05:34 AM
[SOLVED] Network card or network driver causing BSOD
Hi so recently ive been having tons of problems with my computer frequently BSODing its getting really really annoying, im sorta scared to use the internet on my computer when i don't have to because it causes my computer to bluescreen, typically it happens when im on the internet and it usually...
Ravenclaw Cabling and Network Cards 8 12-19-2011 07:14 PM
BSOD, atikmpag.sys
Hi! Since I installed Win7 on my new computersystem, i get these BSOD every first time on a day i start my computer. first some specs OS - Windows 7 Ultimate x86 Windows 7 Ultimate OEM 1/2 year
emddummi BSOD, App Crashes And Hangs 1 03-06-2011 02:55 AM
Blue Screen [moved from Vista/7]
I don't know much about the pain in the bum Blue Screen but i have it. I was told to get the info from the Blue screen when it came up. Here it is - 0x00000077 (0xc000009d, 0xc000009d, 0x00000000, 0x289f4000) I just don't know where i got go from here lol. Can anyone help? Please :P
Death Keeper 34 BSOD, App Crashes And Hangs 4 02-02-2011 07:44 AM

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is on
Smilies are on
[IMG] code is on
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off


Post a Question


» Site Navigation
 > FAQ
  > 10.0.0.2


All times are GMT -7. The time now is 10:33 AM.


vBulletin Security provided by vBSecurity v2.2.2 (Pro) - vBulletin Mods & Addons Copyright © 2017 DragonByte Technologies Ltd.
Copyright 2001 - 2015, Tech Support Forum

Windows 7 - Windows XP - Windows Vista - Trojan Removal - Spyware Removal - Virus Removal - Networking - Security - Top Web Hosts

 

Partially Powered By Products Found At Lampwrights.com