BoyNamedSue

Will do! Here's a report of what I've achieved today, regarding this. I reverted to an older image of my current system (3/16/14). It was running 1.2.27 as well, but Mi-8 and UH-1 weren't installed. I played around for about 1 1/2 hour and it crashed once. I then installed the Mi-8 and UH-1 modules, fired it up and it lasted about 8 seconds, then crash. Restarted it. Not even 2 secs into it. Crash. Reboot. Restart. It ran for about 7 1/2 mins and then again. Crashed. For the record, I've measured the power draw with a KillAWatt before and after the Mi-8, and the max power registered is 240W. Unigine's Valley scores upwards of 275W with a max of 289W. Next step, after running Prime alone, will be trying my other PSU. Exciting!

I've tried to bring it to crash outside DCS, and it hasn't worked so far. How about this? Could one of the circuits around the house - switch or appliance - cause a power dip and make it crash? If it were the case, then my UPS would have kicked in, but it hasn't. :( I will try my other PSU.

I did as you suggested. Albeit for a short while. Less than 1 hour. Pretty inconclusive I will admit, but usually it takes less than that for it to crash on DCS. I had Unigine's Valley running on its own, then with Prime95 in the background. The GPU and CPU have very low temp value. HWinfo shows me that there are no fluctuations in the voltage rails. I will try to switch the PSU with another from my secondary rig. I wonder if 620W unit could handle this rig. GTX 770 w/i-2500k non-OC?

It does sure sound like a hardware issue. But I have yet to get my hands on any log whatsoever. I initially thought it was my UPS giving me trouble. But the issue persisted after I changed to a regular surge protector. For the record, when the crash occurs, there is no BSOD. I disabled auto reboot, just to make sure I could snag some info. But, unfortunately, there isn't. And there is no crash log either. Strange, I know. Eventvwr merely states that "The previous system shutdown at 12:23:41 AM on ‎3/‎30/‎2014 was unexpected."(this is the first time it happend BTW). Strangely enough, the first occurrence of this quirk, was when I updated DCS world, after purchasing the Mi-8 and UH-1 modules. What I will attempt is to bring it back to a previous state (THANK GOD FOR IMAGING SOFTWARE!!! :) ) and see if I can run it without crashes.

I will have to add my name to the list of people experiencing odd quirks as of late. As a matter of fact, I began experiencing crashes and then reboots while merely flying the Mi-8 in FF mode. Initially, I thought it was only on Mi-8, but I experienced the same crash/reboot on other modules as well(A-10C). I've tried most of what's been recommended after a lengthy search. I've changed controllers, turned off virus killers, changed USB ports, VC installs, tweaked sound card settings, monitored HWinfo stats, revert to a previous version, but it wouldn't work. I don't OC my hardware, and my PS is a beefy Corsair HX850. I've tried to have my rig crash on other games. So far, and as some have noticed, it only happens on DCS. I guess, I could always try and remove some memory sticks for the sake of being thorough, but I am leaning more and more to a faulty 1.2.7 update. I've looked through many posts, and it appears that the latest iteration of DCS World could be a the source of all this. I'm irked. I'd lie if I said I wasn't. But on the other hand, I bought the Mi-8 and the UH-1 modules for less than $30 smackers last Friday. :D And I've got quite a few things keeping me busy for the time being. Let's just hope the next release will iron things out.

That's all you had to do? WOW nothing more than to reinstall windows! YAY sounds like fun! I only hope that your system was so screwed up already that it warranted the reinstall, not that SF actually brought it to its knees. Thank god for imaging software!!

I'm with ijozic on this? Is there any possibility to get both? I'm itching to buy the digital download, but what I really want is the physical copy. Call me old-fashioned! :D