Zainstaluj Steam
zaloguj się
|
język
简体中文 (chiński uproszczony)
繁體中文 (chiński tradycyjny)
日本語 (japoński)
한국어 (koreański)
ไทย (tajski)
български (bułgarski)
Čeština (czeski)
Dansk (duński)
Deutsch (niemiecki)
English (angielski)
Español – España (hiszpański)
Español – Latinoamérica (hiszpański latynoamerykański)
Ελληνικά (grecki)
Français (francuski)
Italiano (włoski)
Bahasa Indonesia (indonezyjski)
Magyar (węgierski)
Nederlands (niderlandzki)
Norsk (norweski)
Português (portugalski – Portugalia)
Português – Brasil (portugalski brazylijski)
Română (rumuński)
Русский (rosyjski)
Suomi (fiński)
Svenska (szwedzki)
Türkçe (turecki)
Tiếng Việt (wietnamski)
Українська (ukraiński)
Zgłoś problem z tłumaczeniem
However, let's put that a aside for a second. What I am telling you, as a software developer, is that it is quite literally not possible for any piece of of code running in usermode(basically everything, with the execption of the OS kernel and kernelmode drivers) to cause a system shutdown directly in the way you describe. What they may do is they may submid requests to kernelmode code that may at some point malfunction. But in this case it is a bug in the driver at fault, and not something that the game developer can do anything about.
But, in your case, since you do not appear to have any mini-dumps generated, as would be the case in 99% of kernelmode errors. What most likely causes your machine to reboot is a sudden disrruption in the PWR_OK signal from the 24 pin connector of your PSU. This pin is usually directly connected to the reset pin on most CPU, and as such will cause the system to "cold reboot" instantly as you describe. This is done to prevent the CPU from operating at unsafe voltages, which could result in hardware damage or data corruption.
I understand your frustration, but short of trying another PSU, could you atleast make sure that your current PSU-fan spins during normal operation?
btw, your BIOS settings are on Normal not Auto? If it's on Auto, change it! If you have high speed memory ie 2400+ try testing it without the XMP profile at stock speeds.
Does it say anything else?? Like for example something about memory or uncorrectable WHEA? That might help you narrow it down somewhat.
Edit: And by the way ntoskrnl.exe is the kernel/main component of windows itself
0x101 = increase vcore
0x124 = increase/decrease vcore or QPI/VTT...have to test to see which one it is
0x0A = unstable RAM/IMC, increase QPI first, if that doesn't work increase vcore
0x1E = increase vcore
0x3B = increase vcore
0xD1 = QPI/VTT, increase/decrease as necessary
0x9C = QPI/VTT most likely, but increasing vcore has helped in some instances
0x50 = RAM timings/Frequency or uncore multi unstable, increase RAM voltage or adjust QPI/VTT, or lower uncore if you're higher than 2x
0x116 = Low IOH (NB) voltage, GPU issue (most common when running multi-GPU/overclocking GPU)
Also another bit of evidence is that Elite was doing the same thing and was resolved later on for those users that were having this problem, suggesting to the fact that since Frontier made both Elite and Planet Coaster the cause is them.
Also aswel there has been a small handful of players (from the looks of it) have different rigs and PSU's and it happens exactly the same way.
In addition, the game crashed my monitor display and it didnt switch off my PC on other occasions - is my emergency cut off switch tempermental?
Also checking if a PSU fan spins to see if its working doesnt mean its not as somewhere in my Corsair handbook for my PSU it states not to worry and this is normal operation and only kicks in when it gets super hot.
In addition check my top post -its still happening with my friends PSU.
Rolled back my Video card driver to previous drivers (up to a year) 6 of them at random.
Uninstalled and reinstalled (crash was more aggressive)
Underclocked my CPU back to factory
Installed windows 10 to try the OS - (now rolled back to 8.1)
Swapped my PSU 1000W to my friends PSU 1200W
Took out my GTX 780s swapped them around, tried them singlularly, put in my old 580 tested that.
Put in old RAM sticks up the value of 16 MB - tested.
Allocated unlimited voltage to GTX 780 overclock suite.
Played game on lowest graphics settings
Uninstalled Steam and reinstalled and then reinstalled Planet Coaster
NO LUCK!
Things to try next ...
Wait for results of ticket
The way I fixed it was by limiting the FPS to 120, I really am not sure why that worked but I think my PSU was too old at that point and got weak, so when I played the minigame and the GPU pumped thousands of FPS the PSU couldn't keep up with the power demand or something.