BSOD playing games or stress testing, bugcheck str 0x7f_8

Hello guys and girls,

Every time I try to play games or do something that's cpu or gpu intensive I get a BSOD. I've tried finding the faulty driver but to no avail. If anyone could help me with this problem I'd be very appreciative. Thanks in advance.

p.s. I think that the problems might be caused by overheating but I'm not sure. I haven't cleaned the fans in my laptop in a while but I while try that asap.

EDIT:

In hindsight, I realized I could have added more information. So far I've tried switching memory sticks. That didn't work. I've tried driver verifier and it did point out some conflicting drivers, but installing and reinstalling the proper drivers didn't stop the BSOD's. Also it seems that I'm getting BSOD's only when I'm stress testing my gpu (not overclocked) not my CPU (which heats to 92 degrees Celsius max, too much?). I tried underclocking both my CPU and GPU but that didn't work. I've updated my BIOS too. If you need more info please let me know.

Welcome to SF Halleluja :).

A little more information would be even nicer .
Please follow the Blue Screen of Death (BSOD) Posting Instructions.

Now as to the three dumps uploaded, they are all 0x7F with a the first argument being 8
EXCEPTION_DOUBLE_FAULT.
That means that the OS had already started processing a bugcheck (BSOD) and while it was doing so
a second bugcheck occurred which it can't handle and we get the Double Fault
being that we don't really get the real cause of the bugcheck.

How did you go about stress testing the GPU?
What is the make, model and age of your PSU?
Fill out this form and post back the result:

• Power Supply Calculator

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.

Looking to hearing from you.

Halleluja said:

Thanks for the reply. My pc is an Asus laptop: K53SV. It's about 2,5 years old and has the original battery. The adapter is from a third party, don't even know the brand.

I didn't run Furmark for too long. It took literally less than 10 minutes to get my GPU to 92 degrees. Not sure if that's normal or not. When I stopped the test I instantly got a BSOD too. It's the same as the ones I posted earlier.

If you need more please let me know.

Thanks for the added information :).

Let's address the thermal issue first.

   Warning

The Following Steps Will Void Your Warranty!
If you are uncomfortable opening the PC have a technician perform it for you.

Addressing the overheating issue:

• Make sure you can hear or see the fan working, if it is continue with these steps.

1. Shut-Down the PC
2. Unplug from the power brick.
3. Remove the battery.
4. Let the PC cool down for as long as needed until its only warm to the touch or not at all.
5. Buy a can of compressed air.
6. If you have a cover on the bottom that can be unscrewed, remove it for grater access.
7. When using the compressed air, use short bursts and DO NOT! use it upside-down!!
8. First blow into the intake (the grill with the fan) again short bursts.
9. Next do the same to the exhaust.
10. If you have access the opposite side of the fan blow through there as well.
11. Next grab a flashlight and point it inward from the exhaust and look for anything that may be blocking the light from passing through when looking from the intake side (the fan).

Happy cleaning :)

Hello :).

Code:

DRIVER_OVERRAN_STACK_BUFFER (f7)
A driver has overrun a stack-based buffer.  This overrun could potentially
allow a malicious user to gain control of this machine.
DESCRIPTION
A driver overran a stack-based buffer (or local variable) in a way that would
have overwritten the function's return address and jumped back to an arbitrary
address when the function returned.  This is the classic "buffer overrun"
hacking attack and the system has been brought down to prevent a malicious user
from gaining complete control of it.
Do a kb to get a stack backtrace -- the last routine on the stack before the
buffer overrun handlers and bugcheck call is the one that overran its local
variable(s).
Arguments:
Arg1: 000033f572deaa68, Actual security check cookie from the stack
Arg2: 000013f572deaa68, Expected security check cookie
Arg3: ffffec0a8d215597, Complement of the expected security check cookie
Arg4: 0000000000000000, zero

Code:

DEFAULT_BUCKET_ID:  GS_FALSE_POSITIVE_MISSING_GSFRAME

SECURITY_COOKIE:  Expected 000013f572deaa68 found 000033f572deaa68

.formats 000013f572deaa68
Evaluate expression:
  Binary:  00000000 00000000 00010011 11110101 01110010 11011110 10101010 01101000

.formats 000033f572deaa68
Evaluate expression:
  Binary:  00000000 00000000 00110011 11110101 01110010 11011110 10101010 01101000

Please scan for possible infection and file corruption:

• Download TDSS-Killer and scan for rootkits.
• Download Kaspersky Rescue CD and scan for other types of infections. (a how-to tutorial)
• Download Malwarebytes and DON'T activate the trail (uncheck the box at the end of the installation)
• Follow this tutorial on how to use the SFC/ SCANNOW tool in Windows.

(*Kaspersky Rescue CD from a USB thumbdrive)

If the scans come back with a clean bill of health please follow this detailed
quote and enable Driver Verifier to help uncover the culprit.

Arc said:

Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

Halleluja said:

Hey guys. I did all the malware and virus checking: my system didn't pass. Microsoft Security Essentials found a trojan and also a keygen that was infected. I deleted them both but still get BSOD. This is one is different from the others again. I have driver verifier running properly but it doesn't show the faulty driver. Anyway I added the latest crash dump to this post. Thanks so much

Did you scan the PC using all the tools listed above?

DV didn't point out a specific culprit try letting the machine crash a few more times after
completing the scans posted in post #6.

I did find a very outdated driver,

Code:

Amfltx64.sys Mon Oct 15 06:37:21 2007

• Driver Reference Table - Amfltx64.sys
• Please stop using the mouse at least as a counteractive measure until the BSOD's are gone.

It's my pleasure :) .

Usually when DV doesn't pinpoint a specific driver it is an indication of a hardware fault.
A question, did you flash the PC's BIOS since you got it?
If you did, where did you get it from?

Are the crashing consistent when in 'the walking dead' menu?
The bugchecks aren't holding a lot of useful info but they do show network related drivers.
Please switch to an Ethernet conection if possible or comletely disable the wireless connection
and try to cause a BSOD the same way as before.

Either way update the driver.

Code:

lmvm athrx
Browse full module list
start             end                 module name
fffff880`05002000 fffff880`053fd000   athrx      (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\athrx.sys
    Image name: athrx.sys
    Browse all global symbols  functions  data
 
 

    Timestamp:        Tue Jun 25 08:56:14 2013

• athrx.sys
• Drivers for Atheros AR9285
• Update following this tutorial - HERE

Please provide an updated version of the following:

Please upload the MSINFO32 file:

Start → Run → type MSINFO32 then hit Enter.
In MSINFO32 go to, File → Save → name it your user-name.
Once the file is saved right click it and choose Send to → Compressed (zipped) folder.

Please export and upload your system event log.

1. Start → type eventvwr → hit Enter.
2. Toggle open the triangle to the left of Windows Logs, right-click on System and choose Save All Events As...
3. 
4. A dialogue box will pop up asking you to name the file and select the save directory, name the file the same as your Seven Forums user-name and save it to the desktop.
5. A second dialogue box will appear asking you to select the Display Information, select Display information for these languages and check the box next to English (if you don't have English automatically offered check the box at the bottom to display additional languages - Show all available languages and check English).
6. 
7. Wait a few moments until the cursor returns to normal. The file will now be on your desktop (given it's the directory it was saved to) UserName.evtx, next to it there will be a folder called LocaleMetaData select both the .evtx file as well as the folder and compress them using Winrar / 7zip and attach it in your next post.