Solved New build, Microsoft-Windows-Kernel-Power Error: 0x8000000000000002

[wbsimpson11]

I have been running MemTest86+ since last night and had completed 3 passes when I woke this morning. 0 errors right now. Still running it while I am here at work today. Wont get home till late tonight so should have a good 24 hour run on it just to be sure.

 

[wbsimpson11]

Ran MemTest86+ for 21 hours, 9 passes, 0 errors. Will do the SSD to HHD swap this weekend.

 

[writhziden]

Looks good for the RAM. Let us know how the swap goes.

 

[wbsimpson11]

Here we are, 1 week after my last post. Last weekend I removed all harddrives from the system. I moved the 240GB SSD to the Intel 3.0 Controller and then in the BIOS, I disabled the Marvell controller.

With the 240GB being the only drive now on the system, I did a completely fresh install. I had most of the updated drives I needed already burned onto a disk before I wiped the system. I avoided most of the drivers on the installation disks, since most of them, if not all are not the latest version.

Once it was all loaded, I then moved the 240GB back to an Intell 6.0 Controller, then hooked up one of the Seagate Barricuda 3TB drives to the other Intell 6.0 and formatted it. It took a little bit of working to get it to read the entire 3TB initially, but once I got it figured out using the Seagate tools to add the extra space and then going back into disk management, it was all there. Once this drive was done, I removed it from the controller and then hooked up the other identical 3TB and repeated the process.

With all my drives reading the way they are supposed too, I now have on my Intel 6.0 Contoller, the 240GB SSD running my OS, and a 3TB, partitioned to 6 seperate drives (music, pics, video...). The other 3TB, unfortuantly without the Marvell controller, is hooked up to the Intell 3.0 Controller. This is going to be a backup drive anyways so it should not hurt to much.

The system is stable right now and I have had absolutely no issues with BSODs in the last week since I reloaded it in the manner. The Marvell Controller on the P8Z68 board along with the 240GB SSD apparently do not like each other very much and by disabling it to from the start of the process, it went alot smoother with very little hiccups.

The only thing I really have to left to do (not sure I want too), it to now reenable the Marvell, and then move the other 3TB that is on the 3.0 currently. Hopefully with everything else running fine and all the drivers updated as I can, the Marvell will not be the black sheep in the family anymore.

Last night, I started to work on the overclocking of the system, but it is all new to me doing that. Using the Asus AI Suite II, auto Turbo, I am right now, stabel at 4.1Ghz, but I know I can get it much higher, if not into 5.0Ghz Range.

 

[writhziden]

Just be careful and keep backups of the system before you make major changes like adding the Marvell Controller to the mix. Marvell did have some problems with SSD drives in the past, and it was supposed to be resolved with newer drivers... Not sure if you are having problems because you were using old Marvell drivers, or if there is still some incompatibility between the two. Time will tell, I suppose.

 

[wbsimpson11]

I still may not even mess with it honestly. If I do descide to get the wild hair to do it, I will back everything up without a doubt.

Still running great and right now working on the OC. Stable at 4.5Ghz at 1.318V as of this morning, but only in the first stages of seeing where I can take it.

Thanks for all the help.
Wes

 

[writhziden]

You're welcome. Best wishes!