F15C - PC Turning off

[Leno]

Hello Guys

 

I have a issue with my F15C <mod edit: profanity>

After few minutes flying, my PC just turn off and restart

thought it might be the temperature of my CPU and GPU but both are within the limits.

I really don't know what's going on.

 

 

My Spec

i7

GTX 680

8 GB RAM

Edited March 24, 2015 by SkateZilla

[=Mac=]

GPU driver up to date?

WINDOWS power scheme set to never turn off the cpu?

 

Just some suggestions.

[blackbelter]

Your issue is unlikely to be related to DCS or F15...

 

Check event viewer, and see what happened just before the restart.

[Shmick]

What blackbelter said (though there may not be an event viewer entry for it).

 

I had exactly those symptoms when I upgraded my GPU and the power supply couldn't handle it - as soon as the card tried to draw the oomph needed for proper 3D rendering, the PSU'd auto-reset.

[Arcto10]

Agree with the guys here, I had this issue occur 3 times with various GPU's over my long gaming history. Every time it was an EW for a GPU failure or PSU failure!

[jcbak]

Another vote for PSU.....

[Gladman]

Yep PSU

 

My experience with this occured when I overclocked my system too far. Dual GTX 780's and a 4790K all going as far as I could take them and yeah, that took a little more juice than my system could handle.

Edited March 24, 2015 by Gladman

[cichlidfan]

Power Supply :)

[HiJack]

Power Supply :)

+1

[Wrench]

Mongo had the same problem. Turned out to be a bad PSU

[shagrat]

The 680 requires a LOT of power!

What PSU (how many watts) do you have?

Also, a lot of HDDs use considerable power, as does certain older CPUs...

The peak output of PSUs usually is only "peak", means not for more than a few seconds usually. So if the system requires 580watts total and your PSU is, say a 600watts design, it might run into trouble...

[Demongornot]

Simple way to verify if this is related to your computer or to DCS :

Download and run a Benchmark software, Unigine Heaven and/or Valley for example, download Whocrashed it might catch why the computer crash and if possible make a test with MSI Kombustor ! (Don't worry it won't Kombust your GPU :lol: )

And also a CPU stress test !

 

I also recommend you to use MSI Afterburner or any others software that can permit you to manually set a curve for your GPU fan !

Because factory settings are made by dump guy (actually by smart guy that expect your GPU to have premature degradation cause of heat for you to buy a new card to get more money...)

In EVERY actual graphic card, even those with huge dual or triple fans, you ALWAYS encounter the situation that your GPU is hot enough that the temperature safety will shut down your computer while your fan was at less than 80% in some conditions (most of the time it only overhead but not enough to shut down but your card don't like it) !

 

 

For my MSI 7970 Lightning Boost (GE) edition, i use this curve :

30°c = 40% fan (I have a hot room), 50°c = 50% fan, 80°c = 80% fan and 90°c = 100% fan

For the 90°c well this is because my MSI 7970 Lightning is made out of military class components and made for high temperature and overclocking, so it don't fear to be at constantly 95° for long periods and since I don't play much actually...

But for you, check the maximum temperature for your card and try to make a curve for being comfortably far from it without trying to be too cold (you will just get noise from fan but nothing more), you want your curve to be smooth enough to avoid your fan to have oscillation which they will not like and will be too agreeable to hear.

 

And MSI have always less heat problems than Nvidia which are popular to have already made some GPU model (GTX 590 for example) that literally burn, so it may be a power supply issue like others say but the PSU is not always in fault when your computer restart, it might also be your GPU or even your CPU that overheat and the build it safety that catch to avoid your 200$ & 3,5 billions transistors GPU to become a beautiful SGM -> Smoke Generator Unit :lol:

 

So don't trust the "factory limit" temperature, and it may be you that think that this is the card temperature limit but in fact your model is less forgiving !

Edited March 24, 2015 by Demongornot

[Leno]

Thank you guys i appreciate the help!

 

I will check all this items, and I'm sorry I forgot to mention my Power Supply :music_whistling:

 

I use a Seventeam ATX 750W V-Force, I think that this psu is enough for my system.

The strange thing is that this only happens with F15c. I can fly A10C, P51 and other birds without problems, but anyway I will check my psu.

 

any idea what might be, please let me know

 

Regards

[SkateZilla]

Please Post Detailed Specs (Winkey+R, DXDIAG, Save All Information to TXT, Attach)

 

Also Please Check Windows Event Logs for Hardware and Software (WinKey+R, eventvwr, Windows Logs, System Log and Software Log).

 

A GTX680, i7 *The NEWEST Ones*, 2 DDR3 Ram DIMMS, 1 720RPM SATA-III HDD w/ CPU at 90% Utilization would comsume about 520w.

 

Now the old i7s used more power, and for every USB Device you plug in you add about 2-3w, and every standard fan uses about 3-4 watts//

 

So Listing:

i7, GTX680, 8GB of Ram doesnt answer the question properly,

 

Mainboard:

Chip Type/Model w/ Current Clock Settings

HDD Devices, USB Devices, Fans

Sound Cards, Ram, etc etc.

 

 

Also, Please refrain from using profanity.

 

A 750w PSU Degrades over time, and might be only putting out 725w, and make sure the fans are clean, as it can over heat and shut it self off (THE PSU).

Edited March 24, 2015 by SkateZilla

[Leno]

Also, Please refrain from using profanity.

 

Sorry, will not happen again!

[SkateZilla]

Also, a Reboot could be because of a STOP Command issued by the kernel, (Ie Blue Screen).

 

By Default windows XP and newer would only flash the screen for maybe a second before rebooting the machine. So that would be revealed with checking the event viewer.

[Leno]

My Spec, more detail this time :thumbup:

 

Windows 7 Ult. 64

CPU - i7 3770 3,4GHz (old i7)

GPU - EVGA GTX 680

2 DDR3 RAM 4GB Corsair

2 HD SATA 3 (two 1Tb Seagate 7200)

1 HD SATA 2 (250Gb Seagate 7200)

PSU Seventeam ATX 750W V-Force

MB - ASUS P8H61-M (I know this is not a good MB for games and want to change it ASAP)

USB Devices - Mouse, Hotas cougar and Pro Pedal CH

I Also use 2 standard fan, one on side and another behind

 

I attached DXdiag.txt and I will send later the other log when the error occurs again

DxDiag.txt

Edited March 25, 2015 by Leno

[shagrat]

OK, in general the 750w PSU should give enough power. Even with degradation and 700w it should be enough. A potential root cause may be the 3 HDDs eating up power from the 12v bus... Do you happen to use adapters for old HDD power plugs to power the 680? Or do you supply power only from the 6/8pin GPU power plugs?

As Skatezilla pointed out, a stop error might also cause trouble like a "reboot", e.g. if one of your RAMs isn't 100% OK and DCS stumbles into a memory area which produces crap you get a bluescreen.

The event log is a good idea, it usually should at least point out the timestamp when the reboot occurred. You need to filter for errors...

 

Oh, by the way, video driver is up-to-date? Did you recently update to a new driver, do you have nvidia experience installed (had some troubles and is generally a bad idea unless you really need it). Always try the normal plain video drivers. No 3D add one unless you actually use 3D, no pretty features unless you really need them.

 

It is always difficult to remotely troubleshoot a system, as you can't see for yourself, but just point out what might be the root cause.

If the log does not show anything obvious, a good standard procedure is to reduce the possible components to cause errors. Start with a minimum system, unplug USB devices other than mouse and keyboard, reduce the HDDs if possible, may be run the PC with just one 4GB RAM or at least do a RAM test.

From that do a stress test and add components until the error occurs again.

Fingers crossed it is just the driver, or a simple issue.

[SkateZilla]

OK, in general the 750w PSU should give enough power. Even with degradation and 700w it should be enough. A potential root cause may be the 3 HDDs eating up power from the 12v bus... Do you happen to use adapters for old HDD power plugs to power the 680? Or do you supply power only from the 6/8pin GPU power plugs?

As Skatezilla pointed out, a stop error might also cause trouble like a "reboot", e.g. if one of your RAMs isn't 100% OK and DCS stumbles into a memory area which produces crap you get a bluescreen.

The event log is a good idea, it usually should at least point out the timestamp when the reboot occurred. You need to filter for errors...

 

Oh, by the way, video driver is up-to-date? Did you recently update to a new driver, do you have nvidia experience installed (had some troubles and is generally a bad idea unless you really need it). Always try the normal plain video drivers. No 3D add one unless you actually use 3D, no pretty features unless you really need them.

 

It is always difficult to remotely troubleshoot a system, as you can't see for yourself, but just point out what might be the root cause.

If the log does not show anything obvious, a good standard procedure is to reduce the possible components to cause errors. Start with a minimum system, unplug USB devices other than mouse and keyboard, reduce the HDDs if possible, may be run the PC with just one 4GB RAM or at least do a RAM test.

From that do a stress test and add components until the error occurs again.

Fingers crossed it is just the driver, or a simple issue.

 

A PSU with a weak 12v rail would suffer under load,

 

Seeining as it only happens with F-15C it might be a corrupt dll causing a blue screen

[Shmick]

Skate's point about the 12 V rail is important, too: My old PSU actually had two separate 12 V rails, neither of which could supply the 25+ A burst current the GTX 580 wants (if I remember correctly). If it'd had one rail with the combined power output I may have been in the clear.

 

Another thing to be aware of is that a "750 W" PSU may not be... They could quote a power figure including the reactive component, which doesn't help you. An 80% power factor PSU of "1000 W" will deliver only 800 W of power you can use.

 

 

With others that it's interesting that only the DCS F-15C that seems to cause it, though! Have you tried that CPU / GPU stress test?

 

 

EDIT: Updated reading suggests multi-12V-rail units that don't support combining 'em to increase the available power are a rarity nowadays... My old PSU was quite crappy!

Edited March 25, 2015 by Shmick

[Leno]

With others that it's interesting that only the DCS F-15C that seems to cause it, though! Have you tried that CPU / GPU stress test?

 

I will do the stress tests again and also run the mem test, I may have a problem in the RAM mem.

but what bothers me is that I can run other simulators without problems and other games that demand quite a lot from the PC

 

once I have the results I will post them here

 

is there any software I could use to check the voltages of the PSU?

 

thanks all

[shagrat]

PSU, not that I know of. There is GPU-z for video cards that could write a monitoring log, so you could check if the video card is overheating, vRAM exceeded, or voltage rising unexpected.

CPU-z provides similar for the CPU.

[Svend_Dellepude]

It's not the programming of your cougar that eventually restarts your PC by accident?

[Home Fries]

It's not the programming of your cougar that eventually restarts your PC by accident?

Highly doubtful.

 

Either the Cougar is programmed in Foxy, in which case only the Cougar firmware is programmed, or the Cougar is programmed in TARGET, in which case a crash will at most dump the USB connection to the Cougar.

 

@Leno, you have an excellent video card. EVGA is the best!

[Svend_Dellepude]

What i meant was that the cougar would by accident send CTRL+ALT+DEL or something because there was a programming error causing some keys to hang.

Since it only happens in the F-15 and the guy might have created a different profile for each module.

Just an idea.