Crashes since 3-14-2014

[ZaltysZ]

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.

 

Sounds like a power issue: UPS/PSU/motherboard (faulty caps). If you are comfortable, try doing a stress test. Such tests usually reveal major power issues quickly.

[AtaliaA1]

This is a strange issue. I hope it is a hardware issue, the thought that DCS is the cause would be very disappointing.

 

When this happened to me yrs. ago, it was caused by a screw on the motherboard being out of place. it was touching the power cable to the hard drive and shorting out my system.

[SkateZilla]

Most likely a PSU issue.

[BoyNamedSue]

Sounds like a power issue: UPS/PSU/motherboard (faulty caps). If you are comfortable, try doing a stress test. Such tests usually reveal major power issues quickly.

 

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?

[BoyNamedSue]

Most likely a PSU issue.

 

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.

[ZaltysZ]

The GPU and CPU have very low temp value.

HWinfo shows me that there are no fluctuations in the voltage rails.

 

Try running Prime95 alone. Does CPU temp get much higher? It might be counterintuitive, but running Prime95 while stress testing VGA might not be stressful enough. This is because CPU is tortured the most while running Prime95 with small FFTs or In-Place Large FFTs, what heavily relies on CPU cache for "tight" computations. Running something else alongside might mess with the cache and give load more close to Prime95 Blend type stress test.

[BoyNamedSue]

Try running Prime95 alone. Does CPU temp get much higher? It might be counterintuitive, but running Prime95 while stress testing VGA might not be stressful enough. This is because CPU is tortured the most while running Prime95 with small FFTs or In-Place Large FFTs, what heavily relies on CPU cache for "tight" computations. Running something else alongside might mess with the cache and give load more close to Prime95 Blend type stress test.

 

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!

[streakeagle]

I am having similar crashes: no BSOD, screen just goes black and PC reboots. This only happens with DCS and is far more likely to happen if I changes views, i.e. go from cockpit to external, but can and has happened without any view change or during exit from flying. I assumed it was a temp problem, but I can hold my cpu and gpu temps fairly low (watched/trended them on a 2nd monitor while playing. Next I assumed it was RAM: reseated RAM and ran some RAM tests. RAM comes up good. I am pretty much down to power supply and/or motherboard, but why does this only happen while playing DCS?

[AtaliaA1]

I am having similar crashes: no BSOD, screen just goes black and PC reboots. This only happens with DCS and is far more likely to happen if I changes views, i.e. go from cockpit to external, but can and has happened without any view change or during exit from flying. I assumed it was a temp problem, but I can hold my cpu and gpu temps fairly low (watched/trended them on a 2nd monitor while playing. Next I assumed it was RAM: reseated RAM and ran some RAM tests. RAM comes up good. I am pretty much down to power supply and/or motherboard, but why does this only happen while playing DCS?

 

 

 

 

 

Has to be a coincidence. Software hasn't been able to Blue Screen sense Bill Gates' TV Demo. yrs. ago. embarrassed him on Live TV.

 

This is a hardware issue that just happens while playing DCS. Is this a newly built system? I had a screw fall behind my Mother Board yrs. back and this would happen. Also had a Bad USB on Mother Board that did the same thing.

[grifo]

I'm reading this post after a while I opened a new thread for the same problem happening to me since a couple of mounths... Has someone found a solution or a way to re-create the crash? It is happening in some random times, but always in the same way. I don't think we all have the same hardware problems...

Edited May 16, 2014 by grifo