System Reset, Not BSOD, When Using Skyrim Creation Kit

For the past few days my Win7 computer would reset to BIOS. No warnings, just BAM! hard reboot of the computer.

I've unchecked the box under computer/properties that would Automatically Restart the system on crash. So that's just one thing I've tried in order to try to find the issue.

I think this may be a driver issue but I'm not sure. I've installed several iterations of the graphics drivers and other things but the issue remains.

I originally thought it was an issue with certain areas in the Skyrim Creation Kit. It seemed, up until this morning, that one little spot in the editor and the system would reboot, every time. But this morning I was looking at the screen and it reset....my hand wasn't even on the mouse. Like a ghost reached down and hit the reset button on the case. The crashes have not happened unless the Skyrim Creation Kit is running, however, the CK is almost always running anyways.

I'm fairly certain this is a heat related issue because it didn't start until the temps in the house started to rise. However, using "RealTemp", the temperature hovers around 37-40c idle and about 55-60c under load, which is quite good (because of the water cooler probably).

I've posted about this problem on the forums at Bethsoft too: CTD? Naw...Reboot? Yay! - Bethesda Softworks Forums

What I think I need is an app that will create a dump of things like temps etc when the crash occurs.

I've look at the Event Viewer and it shows a generic error about power being lost (Duh! The computer reset lol)

Any help would be greatly appreciated!

My Setup:

Core-I7 2600K @ 4ghz
H60 water cooler (for CPU)
Asus P8P67 Deluxe mainboard
8 GB Corsair Vengeance 1866 (CAS 9) RAM
MSI GTX-580oc Geforce video card
128 GB Crucial RealSSD C300 System drive (SSD) + 3 other drives
1,000w Ultra X3 modular PSU

I see your problem was solved with a re-install of DirectX. I wonder if a scan with SFC /SCANNOW Command - System File Checker would have picked it up.

Regardless, nice work finding the corrupted DirectX. I also agree about clean installing once a year (or even once every six months for some). I just did a clean install this weekend myself, so I can relate to you doing one as a result of the problem you fixed with DirectX.

Download: DirectX SDK - (June 2010) - Microsoft Download Center - Download Details is what you used to re-install?