2500k
8gb g.skill ripjaws
ASUS P8 Z68-V LX
zotac 580 gtx
OCZ Agility 3 60gb ssd
250gb wd hdd


Good morning, I am pulling my hair out over my new build.



I insert the Windows 7 Pro installation disk (downloaded ISO, burnt at 2x speed) and it gets to about 30%, freezes and then displays the following error:

0x80070002

I have tried a number of methods to fix this including:

- Different ram combinations
- Unplugging all peripherals
- Unplugging HDD (leaving only ssd drive connected)


Would be grateful for any help, thanks in advance!

When you say that, the first feeling i get is that you downloaded the ISO image from somewhere. I hope its not illegeal... as in like torrents, warez etc...

Have you ever thought of it this way:
Maybe the ISO image is corrupt ...

Thanks for your reply!

No, the ISO is legit - downloaded from Microsoft website (after purchasing Win7 Pro) - I initially downloaded the upgrade client into windows xp, but it appeared to be corrupt (and error message stating certain files were missing...).

I read somewhere that perhaps my SSD is corrupt from a previous install? I tried creating 2 partitions and installing windows to the second partition - same error pops up.


I should note - The error message pops up at 29% nearly every time - and it is right after my dvd drive stops activity.

Hmm. I ain't that experienced about SSDs that much...
I don't really know if a toolused to check the HDD for its health will work on an SSD or not..
try it out, let me know if it works.

Download it from the below link:
http://crystalmark.info/download/index-e.html#CrystalDiskInfo

Ok, if that doesn't work... try this one out:

http://ssd-life.com/eng/download-ssdlife.html

Ok so I managed to fix the problem at last!

What I did was:

Installed Windows onto an old hard drive I had - This proved that the DC I had burned was not at fault.
Once inside Windows, I used EASUS partition manager to wipe and format the SSD.

I then rebooted and successfully installed windows on the SSD.

So it appeared to be a problem with the SSD - possibly the remnants of a faulty install from before.

Thanks for your suggestions though guys!