Sudden system restart

[Automan]

Hi all, I'm experiencing random system restart when switching between internal-external views with the Ka-50. Since it's not a CTD, the system is not able to write crash log.

I'm using the latest DCS 1.5.4, but I'm not flying too much with the Black Shark, so I don't know if this behaviour was also present in old versions of DCS.

I don't think it's an hardware issue, since I'm not experiencing this crash in other modules.

Anyone also experienced this issue, or I'm the only one?

[BIGNEWY]

attach your whole logs folder immediately after the crash it may give us some clues.

 

also check your windows event log to look for the likely cause

[Pitot]

Not experiencing it with other modules is not a proof that it's not a hardware issue. Maybe Ka50 views are programmed so that something in it crashes your GPU driver or something else, making it a (your) system specific thing. I agree that you should check and post windows system logs/error logs.

[BitMaster]

Try another NV driver as well. Could very well be driver related.

[Automan]

In the Windows log, i've seen that at the time of the crash the system event shows a critical error: Kernel-power. But this only states that the system was restarted without a regular arrest.

The DCS log, basing on the save filetime, have registered the events 2 minutes before the sudden restart, so don't think it's useful and I've delete the log to start a new from scratch.

Anyway today I've started several times the Ka-50 playing with F1-F2, and I didn't got a restart... as the Murphy law says: when you take your car to a mechanic because it makes a funny sound you will not be able to demonstrate it to the mechanic since the sound will become inaudible:book:

[psbob]

Same Problem here.

I have already checked my Video card, memory and ssd.

 

I think its because of a Windows bug in the new 16something build, hat causes some heavy SSD problems if Windows is installed on it.

 

After 5 days i finally fixed the Problem....

 

Now running win7 again ;)

[Kerb]

I had a similar issue recently. Turned out to be a CPU thermal issues from an incorrectly seated heat-sink and fan.

 

I could play every other game in my catalogue all day long. It was only DCS 1.5 and 2 and only in certain aircraft and at certain times of the day that would cause the system to power off/restart without warning.

 

It's easy enough to rule out. Download and run a CPU and GPU temp application and you can monitor for thermal issues.

[Brewnix]

I once had a instant power shut down while gaming. But it had to do with a stuck fan that when things got heated up it would add more juice to spin the fan faster but since it was stuck it would just trip the power supply. Kind a of like a breaker on your house. Pulling to much current for the power rail I was using.

[aairon]

I have a degree in electrical engineering and have worked on marine electronics of all types for the last 35+ years and I had an issue some time back ( a year or so) where my computer was just shutting down while I was playing certain games that stressed both the cpu and gpu so I assumed the power supply was crapping out (engineering term) this went on for a couple of months DMM said voltage and current were within limits at the time of shutdown I wasn't going to put a O scope to it for that effort I could wait lol, sometimes it was blue screened and when that happened I used bluescreen viewer to read that it was a kernel failure or sum such meaning just about anything.

I was too broke to justify spending money to play a couple of FPS games.

Well time came when I decided I could justify it as it could get worse I went about shutting down and started to pull the plug (physically) and as I grasped the plug I found it barely plugged in it had been partially pulled out.

So I'm thinking no friggin way that was the issue no friggin possible way.

Well just for grins I plugged it in firmly and fired up the old box and hammered the crap out of it and it hasn't objected yet, Had someone asked me if I was sure it was plugged in good I'm afraid what I would have said.

The reason for my surprise is that normally if that were the case there would have been many other failures and eventualy it should have lost connection completely after a couple of failures due to arcing and oxidation,

I'm definitely am not saying your issue is anything like this other then sometimes the issues may not be so obvious.

Edited August 19, 2016 by aairon

[Scooternutz]

How many watts is your power supply and you may need a new one.

[Erforce]

Hi.

i had the same problem for almost a year with a gigabyte GTX 780 and a corsair RM750 gold.

- It was not a RAM issue (cause CTD most time)

- It was not a heat issue (Watercooled, and CPU/GPU stress tests passed without problem)

 

crashs occured mostly when the GPU switched power mode, like in a simple scene, or alt-tabbing to explorer, or even in standby mode, because who knows what windows is doing when you're not in front of the computer !

 

i immediately knew this has to do either with the power feed switch between PSU or GPU, because the 780 worked perfectly with an old cooler master 750w bronze, (i bought the RM for noise purposes) and the RM worked well with 1 or 2 GTX 670.

 

i resolved my problem last week when i bought a MSI GTX 1070, my RM750 likes it, and i gave the 780 with the cooler master to the 2nd PC.

 

i was lucky to have another PC to swap pieces, if it's not your case, i suggest you to borrow another GPU from a friend to see if this help, because finding a spare PSU is not easy.

 

Note :

I had instant reboot most of the time

Sometimes I had this error "display driver stopped responding and has been recovered"

and less often, a good crash with dump file : "This was probably caused by the following module: nvlddmkm.sys"

 

i tried many tweaks, drivers with no luck, only changing the PSU or GPU fixed to problem.