Solved Random BSOD 7f

[blackshade]

Sorry to be pushy, but I'm wondering if there's anything else you kind people can suggest? I've posted a couple of times since I was last asked for information, but haven't seen a response.

I'm a bit frantic about this, as you can probably guess, and need to at least try to get this situation sorted before the fullness of my work week is upon me.

Any assistance would be stellar. Thank you all.

 

[YoYo155]

Please follow each crash with a new instance of the files being generated by following this thread.

http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html

 

[blackshade]

Sorry about that. Here are the newest files. Just as an FYI, I've been running in safe mode since the last series of BSOD's and there have been no issues. Perhaps this is driver related after all.

 

[YoYo155]

(haven't looked at the dumps yet)
I doubt it, safe-mode doesn't incorporate the graphical core(s) and you seem to crash
on watching youtube videos, correct?

 

[YoYo155]

Okay I've looked at the recent dumps, and they are the same as before.
I can assume that there is something fundamentally wrong with the GPU's /CPU's
hardware, mainly the FPU according to the dumps.

But I don't see any harm in trying, see what AMD offers in terms of the latest driver
for your GPU.

• Mobile

The current one:

lmvm atikmdag
Browse full module list
start             end                 module name
fffff880`04a45000 fffff880`0507c000   atikmdag   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Browse all global symbols  functions  data
    Timestamp:        [COLOR=Red][B][U]Thu Dec 10 08:42:32 2009[/U][/B][/COLOR]

Try to induce another dump as you did before and report back either way .

 

[blackshade]

Honestly, it's not just video related anymore. It's crashing randomly now. Just whenever it feels like it. Sometimes will run for an hour with no problems, other times it will boot and crash.

One thing I did notice is that the drive usage light would flash constantly as if the drive was looking for something just before the crash.

Since I've been in safe mode all has been quiet.

 

[YoYo155]

That is what I was claiming, give it a shot you have practically nothing to lose.
With respect to the the HDD usage light, that makes sense as the system "knows"
and prepares itself to "blue-screening" in an orderly fashion, it's not as sudden as it looks.

 

[blackshade]

New dump. BSOD'd as I was installing the driver. Not sure whether it took, but if not I'll try again.

 

[YoYo155]

It did, but this it's a different error 0x116 regarding this is what i usually post with regards
to a TDR, but most of it have been done already.

lmvm atikmpag
Browse full module list
start             end                 module name
fffff880`0792a000 fffff880`079cd000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Browse all global symbols  functions  data
    Timestamp:        [COLOR=Red]Fri Apr 18 04:07:07 2014[/COLOR]

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout  failed.

What you're experiencing is called a TDR (Timeout Detection Recovery) is not a bugcheck in the true sense in that something
has went terribly wrong in the kernel which forced the machine to crash.

"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

• Read the full post.

:ar: Test for thermals and stability:

• Download HWinfo and post a Screenshot of the sensors window, one at idle and another while putting load on the PC using Prime95 for the CPU side and Furmark for the GPU.
  • Before running Prime95 make sure to enable Round-off checking (see 1st post under the tutorial).
     Note

  It is not mandatory to run both tests simultaneously, although possible as long as the temperatures are under constant monitoring.

:ar: Testing the RAM:

Test and Diagnose RAM Issues with Memtest86+:

• RAM - Test with Memtest86+

   Tip

• :info: Pay close attention to part 3 of the tutorial "If you have errors"
• :tip: Test the RAM with Memtest86+ for at least 7-10 passes. It may take up to 22 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.

When done with the testing procedure take a picture and upload it here.

:ar: This will help you to determine where the issue is origination from (if any):

First run it with all the existing/installed RAM modules. If it comes with no error, all is good.

But if it starts showing errors, Stop testing. Errors/red lines means one or more RAM is faulty. But the fault may occur due to a faulty DIMM slot, too, which is a motherboard component. Using memtest86+, you can discriminate between a faulty RAM and a faulty motherboard.

How? Say you have two RAM sticks and two DIMM slots. You obtained errors at the test with all RAM sticks installed. Now, remove all the sticks but one. Test it in all the available slots, one by one. Continue the same procedure for all the available sticks.
How to make the inference that is it a RAM issue or it is a motherboard issue? Suppose you have got the result like that:

test|Slot1|Slot2
RAM1| Error | Error
RAM2|Good|Good

It is a RAM, a bad RAM.

But if you have got a result like that:

test|Slot1|Slot2
RAM1| Error |Good
RAM2| Error |Good

It is a motherboard issue. The particular slot is bad.

You could try removing each So-DIMM (RAM module) and see how it works with one in
either slot for a while.
As I stated in my first post in this thread I believe we are dealing with an uncorrectable
hardware issue, sorry.

 

[blackshade]

Well, just wanted to pop back in with an update.

I took the laptop all the way back to factory settings and updated Windows completely. Have been running for the last 8 hours without a blip, so, fingers crossed, it seeems as though we were dealing with a driver/software glitch after all.

I want to thank everyone who tried to assist me, though. You guys really went above and beyond.

I'll mark the thread as solved. Thanks again.

 

[YoYo155]

Well I sure hope so .
If any issues arise be sure to let us know.