Kernel Error 0x8000000000000002 BSOD Event ID 41, task 63

[Cire3]

Well I do have good news and bad news. As for the Good news. I replaced DVI with a HDMI cable and everything seems fine with that. But I still have a few errors popping up.

 

[usasma]

Nothing worth noting (IMO) in this latest logfile.

 

[Cire3]

So is that a good thing or a bad thing? Haha I'll give it time and God willingly I can mark this as solved.

 

[Cire3]

This recently came up "system firmware has changed the processor's memory type range registers (MTRRs) across a sleep state transition (S4). This can result in reduced resume performance" Should I be concerned? NOTE: My desktop case's light blinks when this happens. I'm not sure whats up.

 

[usasma]

As you don't relate any problems resuming from sleep, I'd say it wasn't something to be concerned about.

 

[Cire3]

So I guess that's a wrap! So far I haven't had a black screen or a Kernel error in a week and a half! Thank you much, I truly appreciate it. The black screens stopped ever since I switched to a HDMI cable. Although the system firmware has changed the processor's memory type range registers (MTRRs) across a sleep state transition (S4). This can result in reduced resume performance came up I'm not sure it will kill me. Thanks a ton!

 

[usasma]

Glad to hear it. Thanks for letting us know!

 

[Cire3]

So I think I jinxed myself. I was just on Youtube and got a BSOD. Here's the event log NOTE: Ive been doing some reading and people have been having issues with the HTML 5 feature on Youtube causing them to get a BSOD. Funny thing is I think those people were using AMD Radeons as well. I'm not sure if that's it but It can be. I recently used HTML5 for youtube so it loads faster. I switched to Flash so I hope that's the issue. Yet again I have no clue, sorry if I got your hopes up high. This is a burden, I hope I'm not an inconvenience xD

 

[usasma]

I am a BSOD specialist, I'll need the memory dumps in order to analyze this.
Please provide this information so we can provide a complete analysis (from the Pinned Topic at the top of the forum): http://www.eightforums.com/bsod-cra...e-screen-death-bsod-posting-instructions.html Please use Option 1 as it provides Event Viewer logs (and the Grab All option includes the memory dumps).

The memory dump is a STOP 0x7E and points to your ATI drivers.
Please see this link for more info on the STOP 0x7E error: BSOD Index
In particular, note the "Usual causes" section:

Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control,

As you've recently updated the ATI drivers, I have to suspect that there's a hardware problem here.
But first, please run Driver Verifier according to these instructions (just in case it is a driver issue): Driver Verifier Settings
After that, please run these hardware diagnostics (if you haven't run them already): Hardware Diagnostics
Although I figure that you can trust the people at the service center to run the tests that they said they ran - I'd suggest that you double check their work by re-running their tests.

 

[Cire3]

Here's the Diagnostics

 

[usasma]

AMD OverDrive (AODDriver2.sys) is either a stand-alone application, or a component of the AMD VISION Engine Control Center. This driver is known to cause BSOD's on some Windows systems.
NOTE: these symptoms were from the previous release of OverDrive. The new release uses the same driver name, but is dated from 4 November 2013.

Please un-install all AMD/ATI video stuff from Control Panel...Programs...Un-install a program
Then, download (but DO NOT install) a fresh copy of the ATI drivers from Global Provider of Innovative Graphics, Processors and Media Solutions | AMD (in the upper right corner of the page)
Use this procedure to install the DRIVER ONLY: ATI video cards - DRIVER ONLY installation procedure - Sysnative Forums

If the device (AODDriver or AODDriver4.01) remains a problem, open Device Manager, select the "View" item.
Then select "Show hidden devices" and scroll down to the Non-Plug and Play Drivers section.
Locate the AODDriver entry, right click on it and select "Un-install". Reboot for changes to take affect.

Sometimes the driver remains and continues to cause BSOD's. If this is the case for you, post back and we'll give further instructions for safely removing it.

If overclocking, please stop. Remove the overclock and return the system to stock/standard values while we're troubleshooting. Once the system is stable again, feel free to resume the overclocking.

I'll be interested in the results of Driver Verifier - it may surprise us with some information. (I'm wondering about some of the drivers that showed up in the memory dump).

Beyond that, I'd be interested in the results of the video stress tests along with the results of Prime95.
I suspect either a problem with the video card (most likely in it's memory), or a problem with the motherboard.

Analysis:
The following is for informational purposes only.

[font=lucida console]**************************Wed May  7 00:15:30.349 2014 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\050614-13640-01.dmp]
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Built by: [B]9600[/B].17041.amd64fre.winblue_gdr.140305-1710
System Uptime:[B]0 days 5:33:16.070[/B]
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by :[B]atikmdag.sys ( atikmdag+c7dbb )[/B]
BugCheck [B]1000007E, {ffffffffc0000005, fffff800a0541dbb, ffffd001c801e0a8, ffffd001c801d8b0}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x1000007E]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)[/url]
Arguments: 
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff800a0541dbb, The address that the exception occurred at
Arg3: ffffd001c801e0a8, Exception Record Address
Arg4: ffffd001c801d8b0, Context Record Address
PROCESS_NAME:  System
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
FAILURE_BUCKET_ID: [B]AV_atikmdag+c7dbb[/B]
  BIOS Version                  2301
  BIOS Release Date             01/06/2014
  Manufacturer                  To be filled by O.E.M.
  Product Name                  To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.

[font=lucida console]**************************Wed May  7 00:15:30.349 2014 (UTC - 4:00)**************************
GEARAspiWDM.sys             Thu May  3 15:56:17 2012 (4FA2E2E1)
usbfilter.sys               Tue Aug 28 21:27:12 2012 (503D6FF0)
Rt630x64.sys                Fri May 10 05:59:08 2013 (518CC4EC)
asmtxhci.sys                Fri Aug 16 15:28:42 2013 (520E7D6A)
asmthub3.sys                Fri Aug 16 15:28:54 2013 (520E7D76)
RTKVHD64.sys                Wed Aug 21 00:48:22 2013 (52144696)
asstor64.sys                Mon Sep 16 04:39:08 2013 (5236C3AC)
dump_asstor64.sys           Mon Sep 16 04:39:08 2013 (5236C3AC)
mbam.sys                    Wed Oct 30 12:11:45 2013 (52712FC1)
athwbx.sys                  Wed Nov 13 03:05:17 2013 (528332BD)
[COLOR=RED][B]AODDriver2.sys              Tue Feb 11 06:06:52 2014 (52FA044C)[/B][/COLOR]
MBAMSwissArmy.sys           Thu Feb 20 18:49:10 2014 (53069476)
mwac.sys                    Tue Mar  4 10:45:58 2014 (5315F536)
AMDACPKSL.SYS               Tue Mar 11 19:49:44 2014 (531FA118)
AtihdWB6.sys                Tue Mar 11 19:50:02 2014 (531FA12A)
Wof.sys                     Thu Mar 13 04:27:29 2014 (53216BF1)
atikmpag.sys                Thu Apr 17 21:07:07 2014 (53507ABB)
atikmdag.sys                Thu Apr 17 22:13:16 2014 (53508A3C)
[/font]

http://www.carrona.org/drivers/driver.php?id=GEARAspiWDM.sys
http://www.carrona.org/drivers/driver.php?id=usbfilter.sys
http://www.carrona.org/drivers/driver.php?id=Rt630x64.sys
http://www.carrona.org/drivers/driver.php?id=asmtxhci.sys
http://www.carrona.org/drivers/driver.php?id=asmthub3.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
asstor64.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
dump_asstor64.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=mbam.sys
http://www.carrona.org/drivers/driver.php?id=athwbx.sys
http://www.carrona.org/drivers/driver.php?id=AODDriver2.sys
http://www.carrona.org/drivers/driver.php?id=MBAMSwissArmy.sys
mwac.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=AMDACPKSL.SYS
http://www.carrona.org/drivers/driver.php?id=AtihdWB6.sys
Wof.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
http://www.carrona.org/drivers/driver.php?id=atikmdag.sys

 

[Cire3]

I haven't had A BSOD so far. I just left my PC be for a bit. I'll keep you posted

 

[Cire3]

Bad news. Today I was trying to log in and this came up. I have no clue why this happened. Then when I clicked Ok my screen went completely black. So I had to reset

 

[usasma]

The error status of 0xc000000e is "

[FONT=&amp]A device which does not exist was specified."​

​

[/FONT]

I have no actual idea of exactly why it happened, but would suggest that you do this as a precaution:

Then please run the following DISM commands to see if there's any problems with the system (from an elevated (Run as administrator) Command Prompt). Press Enter after each one:

Dism /Online /Cleanup-Image /ScanHealth

Dism /Online /Cleanup-Image /CheckHealth

Dism /Online /Cleanup-Image /RestoreHealth

FYI - I have repaired systems using the last command even though problems weren't found with the first 2 - so I suggest running them all.

From this article: Repair a Windows Image

You can also run sfc.exe /scannow from an elevated (Run as administrator) Command Prompt to check for further corruption.

Also, Please do the following:
- open Event Viewer (run eventvwr.msc from the "Run" dialog))
- expand the Custom Views category (left click on the > next to the words "Custom Views")
- right click on Administrative Events
- select "Save all Events in Custom View as..."
- save the file as Admin.evtx
- zip up the file (right click on it, select "Send to", select "Compressed (zipped) folder")
- upload it with your next post (if it's too big, then upload it to a free file-hosting service and post a link here).

 

[Cire3]

Okay, here you go

 

[usasma]

The only error that I saw was that the AMD Overdrive service couldn't start.
Please check in services.msc to see if you can stop and disable this service (only the AMD Overdrive - not the other AMD services).

 

[Cire3]

Thing is the other AMD services are the ones only showing up. Nothing from the Overdrive

 

[usasma]

This is an error in the service trying to start - not necessarily in the service itself.
Try this free program: Autoruns for Windows
Set a Restore Point (just in case),
Then run the above program and search for "AODDriver" (without the quotes)

When you find it, uncheck it (on the left hand side of the entry) and then reboot to see if that helps.

 

[Cire3]

Searched for AODDriver and nothing came up. That's quite odd.

 

[usasma]

A bit unusual, but not unheard of.
It could be that the startups are pointing to something different.
Could you please:
- open Autoruns (but do not click on anything)
- select File...Save and save the file as somthing like autoruns.arn
- zip it up and upload it with your next post.