0x8000000000000002 kernel power BSOD - Windows 8 x64

Code: 
3: kd> .bugcheck
Bugcheck code 0000007A
Arguments fffff8a0`012bf238 ffffffff`c000000e 00000001`009fe880 fffff901`03817000

3rd argument shows NTSTATUS 0xc000000e, which indicates a device which does not exist was specified/disk hardware error.

Before I recommend checking the hard disk itself, get rid of McAfee and let's see what happens because I'm curious.

McAfee removal - How to uninstall or re-install supported McAfee products using the Consumer Products Removal tool

Windows Defender (how to turn on after removal)

A.Navigate to Control Panel (with icons). You can do this by hitting Start > Search > Control Panel. Once in Control Panel, change the drop-down from Category to Large and/or Small icons.

B.Among the list of icons, find and click Action Center.

C.Assuming the removal of your prior antivirus software went properly, you will notice for both Spyware and unwated software protection (important) and Virus protection (important), it'll have a button labeled Turn on now. Click this button (it doesn't matter which, as Windows Defender serves as both in Windows 8/8.1).
 
Thanks for the reply. Mcafee IME is absolute garbage and has caused countless issues in the past, so I wouldn't be surprised if it is the culprit.

I will remove it as suggested. Presumably I then have to wait to see if any further BSODs occur?

Thanks again
 
Just to add to this, I have just booted it and it couldn't find a boot device, and the BIOS pointed to a network boot. Restarted and into windows fine. It did this before, but not for a good while again until today.
 
Is that a definite one then gents? New HD? I've run a hard drive inspector and it didn't find any major problems except for 87% reliability, but I'm assuming this is going to be a chipset issue rather than a platter/heads issue which I would imagine that checks.
 
I'd give a run of Seatools just to be sure:

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 driver related issues that may cause conflicts or a false positive, it may be a wise decision to choose the most minimal testing environment (DOS). I always recommend running Seatools in DOS if absolutely possible.

-- Run all tests EXCEPT: Fix All and anything Advanced.
 
Was that with the DOS or Windows version? If it happens with DOS too, looks like that's that.

You're welcome.
 
Yes it was the dos version, booting from the cd. However, I have just received the new hard disk and thought I would run the seatools again just to be sure, and it says the same - no hard drives found, and no controllers detected also.

Any ideas anyone? Does that suggest a controller issue, or just that seatools isn't working properly for some reason? I have set the bios to boot from legacy instead of UEFI, obviously.

Thanks
 
The controller needs to be set to IDE for it to work, if you haven't done.
Other than that, could be a bad board or power/sata cable.
Does the drive work though? Any issues in Windows? If not, then don't worry about it.
 
I've just found that out and now the old drive is detected also. Now running tests on it. Hoping it finds errors otherwise I have bought a new drive for no reason. Booting to network previously suggests something must be up with it, though.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top