|Message||The specified extended attribute handle is invalid.|
This appears to be a raw Win32 error. More information may be available in error 0x80070116.
This is a Blue Screen of Death stop code. More information is available in the Knowledge Base article Bug Check 0x116: VIDEO_TDR_ERROR.
This code indicates success, rather than an error. This may not be the correct interpretation of this code, or possibly the program is handling errors incorrectly.
|Description||The default facility code.|
|Error Code||278 (0x0116)|
There seems to be a "cute" typical issue with hot-running GPUs due to thermal expansion - the balls of solder under the GPU chip are constantly expanding and shrinking, sometimes cracking. When GPU enters idle state (usually when you stop the GPU-loading application), it cools down rapidly, the contact breaks and BAM! Artifacting and BSOD. Probably I'm having the same problem too.
Try something OpenCL- or CUDA-based (memtestCL or memtestG80) on Linux, with open source drivers, to lure out the errors. If you get them, Windows and proprietary drivers will be out of the equation and it'll be down to firmware, VRAM or GPU, which you wouldn't want to test and repair by yourself, I suppose.
When this happens I try to exclude the software as well. Could be a hardware/software combination.
What happens if you boot up a Live Linux CD? Knoppix, Ubuntu or whatever? Is the system able to run the Linux system for an extensive number of time without failure. Then maybe you have a software problem.
Alternatively you could try to boot start windows in fail-safe mode (does it still exist in Windows7? I am a Linux guy myself).
Ok, just a few suggestions to eliminate the reasons. Far too often I've found instable systems being the cause of software/misconfiguration rather than actual hardware problems.
start by updating your vid card driver (reinstall if its already latest). the faulting module is an ATI driver component as I'm sure you've surmised.
run 'dxdiag' (directX diagnostics) from the run bar or CLI. does it notice any issues? try reinstalling directX if problem still persists.
if no issues are found, and the problem continues, shut down all programs and run 'sfc.exe/SCANNOW' to check that all your system files are integral.
run an MS memory diagnostic. is all well?
last open the box while its off, and confirm that any PCIe power rails to the card are connected. does your card have any power slots that your PSU does not have a rail for? Turn the box on. does the vidcard fan start spinning quickly as expected? no rattling or anything?
start turning down any advanced vidcard features (AA, textures, VSynch, etc) and see where that leads you. if you turn your game graphics down to minimum, does the problem still occure at about the same time into the game?
if all that fails, my next step would be to rebuild the OS with latest drivers and DX, and see if its still reproducible. if so, replace your vid card. if not, then you are fixed.
It is important for the troubleshooting to know WHEN the error appears. What do you do on your computer when it happens? Also, do you see both GPUs in the device manager or just one VgaSave? At this moment it can be anything from failing GPU to corrupted driver(s). Also, Windows uses VgaSave driver because you stopped the ATI driver to manage the ATI GPU in any way. You can identify the device this driver manages by going in to device Properties, click on tab "Details" and from the drop-down box select "Hardware IDs", which is usually second down. It should be in English or very nearly literal translation.
It will give you string like:
which you can try to identify the device with here.
As for further troubleshooting when the error happens...
Has anything changed before the error started? Drivers update, upgraded hardware, unexpected system freeze or black screen or anything? Is there anything else that happens in the system - errors, warnings, etc - which do not cause BSOD?
Now things get interesting. This laptop has 1st gen i5 CPU, which should have onboard GPU (but please confirm - there are newer models with different CPU). But we have to be sure. Is there an BIOS option disabling it? If yes, enable it and see if you have Intel HD appearing in DevManager (yes, you should have TWO display adapters listed there if all is ok, second being ATI). If not, you have a laptop with just one GPU, which is the ATI.
In that latter case and taking into consideration your info about BSOD it seems that indeed the Radeon has breathed it's last.
After going through some data on Dell n5010 system available on dell websites there are two important bits of information:
In other words: I don't know what is going on, but it looks like with this laptop model you got either IGPU or ATI. Not both. Not sure it's how Dell chose it or ATI can't do it.
EDIT 3: N5010 with ATI discrete graphics is both not designed by Dell to be switchable and Radeon 5650 doesn't support it anyway. However, with soldering equipment one can bypass the faulty ATI chip and system will then work with IGPU enabled. But this is amateur work to say the least.
So, it looks like the ATI chip is either faulty or the driver is corrupted. I recommend uninstalling all ATI drivers and any ATI software either manually or using ATI Uninstaller. When that's done do an extra reboot and then install driver provided by Dell on the product support page ONLY. If that works - all is well. If you're back to not working device in Device Manager it means the chip is failing. This is first and final warning you get before it stops working completely and you're left with laptop withe either black screen after turning it on or beeping error code(s).
This sounds like a heat problem to me did you overclock the chip? You may want to use something like http://www.techpowerup.com/realtemp/ to see how hot it is getting you may just need a better heat sink and cooling system.
I have had similar problems with my own computers and others that I have fixed in the past. In more or less all cases where I have had similar behaviour to your system (lots of strange, seemingly unconnected problems), it has been due to one of the following two problems:
Either the PSU has outputted fluctuating voltage or the actual power supplied from the grid has fluctuated. Nowdays I never buy cheap PSUs since I know how hard it can be to diagnose these kinds of problems. The wattage on the PSU is no guarantee that it is good since it might still give fluctuating power (which is usually what matters). Try running some kind of monitoring program that can display the motherboard voltages on your computer (speedfan for instance) and check if they are stable and close to the wanted values. If possible, try using a UPS so that you don't get any voltage fluctuations from the grid. Bad power supply also has a tendency to damage other components in the computer which makes it even harder to debug.
Some motherboards are extremely choosy when it comes to RAM. Check with your motherboard manufacturer, they usually give very detailed recommendations on what to use (brand, size, serial-number). I have had this trouble even on a pre-assembled computer, where the people who assembled it apparantly did not check this since the RAM in it was listed as 'Not recommended'. Took me quite some time to figure this out. Doing memchecks do not always find this for some reason.
Do the following:
0x116 bugcheks are hard to debug, because the public symbols don't include all data. You can try to use the AMD Catalyst 12.11 Beta driver and hope this fixes the issue.
It was a driver issue. After upgrading to Windows 8, I saw that there was a new AMD Graphics Driver for Windows 8. Solved my problem since I installed it. This is the driver.
This thread at Overclock.net was started by someone using an ATI card, getting that same BSOD (error and file). People suggested multiple different theories, and one of them pointed to a driver related issue and solution that worked for some people (apparently this isn't uncommon). In the first thread however, it turned out to be a faulty card that the owner got replaced for free by the manufacturer.
So. here is what I would do. First, follow these instructions from that second link I gave you...
Try and do it in this order: [Fixes] Catalyst Drivers Error & OC & Eyefinity & General Issues
Uninstall Afterburner and Catalyst from manager.
Clean it with Atiman Uninstaller v.6.3.1 (turn off UAC to install this).
Install MSI Afterburner 2.2.0 Beta 14 Download
Enable "unoffcial overclocking" HOW TO: Enable UNOFFICIAL overclocking mode in MSI AfterBurner
Afterburner settings > enable all voltage controls.
Note: Exit Afterburner prior to editing .cfg file and ULPS.
Crossfire User- Do the following between steps 4 and 5:
- Go to regedit (start > search programs and files > "regedit").
- In drop down menu: find file > type "enableulps".
- For ALL instances (keep pressing F3) change the "1" value to a "0".
- Reboot PC.
Use latest Afternurner 2.2.0 Beta 15
.. and again, this seemed to work for some of the people with the same error code and system file popping up on a BSOD. If that doesn't work, look into getting the card replaced under warranty (if you can).
Did some research
STOP 0x0000007F (UNEXPECTED_KERNEL_MODE_TRAP)
This error message can occur if either of the following conditions exists: Your computer has hardware or software problems (hardware failure is the most common cause).
You try to over clock the speed of your computer's processor (for example, you set a 150 MhZ processor to run at 187 MhZ). The above STOP error means a trap occurred in kernel mode and the trap is either one the kernel is not allowed to have or is always fatal. The most common causes of a STOP 0x7F are:
Low-level hardware corruption, such as corrupt memory (RAM)
Mismatched memory modules
A malfunctioning motherboard
Your specific case is 0x00000008 means: Double Fault
A double fault occurs when an exception occurs while trying to call the handler for a prior exception. Normally, the two exceptions can be handled serially, however there are several exceptions that cannot be handled serially and in this situation the processor signals a double fault. The two primary causes for this are hardware and kernel stack overflows. Hardware problems are usually related to CPU, RAM, or bus. Kernel stack overflows are almost always caused by faulty kernel-mode drivers.
To resolve this issue, use the appropriate method:
If either software or hardware can cause a particular trap, a debug is required to determine which is the cause. If you suspect a hardware problem, try the following hardware troubleshooting steps:
Test the RAM in the computer by running the diagnostic software that is provided by the computer manufacturer. Replace any RAM that is reported as bad. Also, make sure that all the RAM in the computer is the same speed.
Try removing or swapping out controllers, cards, or other peripherals.
Try a different motherboard on the computer.
If you are over clocking the speed of your processor, set it back to the speed at which it is designed to run.
Check with the hardware vendor for any updated hardware drivers or BIOS updates, or both.
This error occurs when there is a compatibility issue between the graphic card, the hardware or its driver.
What You should do is go to device manager, uninstall the display driver and do a restart.
Turned out to be bad RAM + HDD. The original RAM was specified at 1.65V, (6 sticks), and even though 4-5 passes of memtest would run fine the BSODs disappeared once I switched to 1.5V RAM (3 sticks).
The hard drive was also broken, but replacing the harddrive just reduced the number of different stop codes.
User contributions licensed under CC BY-SA 3.0