Question : ESENT, Corrupt Database, Event ID 474

So, I've ran into an issue on a new PC build that I'm helping with.

Hardware is:
Phenom 2 x6 1055t
ASUS Crosshair IV
G.SKILL Ripjaws Series 4GB DDR3 SDRAM DDR3 1600 F3-12800CL7D-4GBRH
2x 640 WD Black HD's in Raid0
ATI Radeon Sapphire HD 5850
Windows 7 x64 Pro

Upon fresh install of the OS on the raid0 array, the OS immediately has issues. The event log is full of ESENT errors, event ID 474, and a few others, all seemingly related to cryptographic services and this corrupt database.

I've followed microsoft articles regarding correcting this issue, mainly using the Esentutl to try to repair it, and then to check integrity. The tool successfully repairs, integrity check succeeds. I restart crypto services, and it errors out again, corrupting again.

http://technet.microsoft.com/en-us/library/cc734109%28WS.10%29.aspx

I've tried deleating catroot2 and emptying all files tmp and oem files, but when it rebuilds, it's corrupted again.

I've tried unregistering the .dll's listed, but some of them are not present. I'm not sure if the list is accurate for windows 7.

Keep in mind, all of this happens on fresh hardware, clean OS install.

Considering hardware options, the following has been done to try to isolate or identify hardware culprits:

No Raid array, single hdd install, tried on both hdd's individually
Changed ram, ram slot/channel, ram timings
Changed hdd cable, sata slot.
Changed Mobo (RMA'd. Don't ask.)
Changed GPU (issue at first seemed to be a graphics issue)
Changed install disk/version of windows 7. Started with win7pro x64, now using win7ultimate x64.

This issue is preventing windows updates, windows defender, programs to be installed, and it also causes drivers to appear to be unsigned when they are in fact signed.

Thoughts?

Answer : ESENT, Corrupt Database, Event ID 474

No, it was just a fresh built pc.

Anyway, we found the problem; it was a faulty CPU. As soon as we swapped it out, the database rebuilt itself fine, no checksum errors, etc etc.

Figured it had to be something retarded like that as there was almost zero info on the web about these specific problems. There was stuff that was pretty close, but didn't cover all of the symptoms/descriptions.