Steam telepítése
belépés
|
nyelv
简体中文 (egyszerűsített kínai)
繁體中文 (hagyományos kínai)
日本語 (japán)
한국어 (koreai)
ไทย (thai)
Български (bolgár)
Čeština (cseh)
Dansk (dán)
Deutsch (német)
English (angol)
Español - España (spanyolországi spanyol)
Español - Latinoamérica (latin-amerikai spanyol)
Ελληνικά (görög)
Français (francia)
Italiano (olasz)
Bahasa Indonesia (indonéz)
Nederlands (holland)
Norsk (norvég)
Polski (lengyel)
Português (portugáliai portugál)
Português - Brasil (brazíliai portugál)
Română (román)
Русский (orosz)
Suomi (finn)
Svenska (svéd)
Türkçe (török)
Tiếng Việt (vietnámi)
Українська (ukrán)
Fordítási probléma jelentése
As for the npsvctrig - it looked like a filter driver name, but it's not tied to the filesystem, but rather to named pipes. Which is typically used to communicate between applications - and probably means that if it crashed, that it has a bug or had RAM issues. So probably a dead end lead there.
Let us know how it goes @OperatioinDx .
How about you cool it with the slights. If it is killing a persons PC they have a right to warn anyone, including the developers. Trying to make people uncomfortable for potentially serious faults they've had with the game is counter productive.
There is no way Empyrion is "killing" a PC like the one described by the OP even with maxxed out settings.
I have the same GPU and an older CPU (i7-3930K), and basically the same PSU (1000W version of the same line) and they barely break a sweat playing Empyrion. I have to do some serious modding in Minecraft (which wastes computer resources fiercely due to using Java), Skyrim or other heavity moddable game to get my computer to even take a deep breath (i.e.: fans to spin up).
OP:
Thoroughly read and try out ButtHamsters diagnostic advice. This guy has all the knowledge and experience I do and is much more inclined to bend over backwards helping people as he is not jaded and cynical like I am.
It is critical that you test everyhing about your computer, check that every component is installed and seated perfectly and that they aren't being overclocked or otherwise stressed in any way so that you can track down the problem.
Try SDI (Snappy Driver Installer), it is a free, open source driver survey and update utility. Don't let it update your GPU driver though, and NEVER let Microsoft Update install GPU drivers for you. Always download and use the drivers direct from nVidia, and keep several versions on had in case you need to restore an old version. Having the latest graphics driver is only rarely a good idea, and is something far too many supposed professionals constantly recommend as a blanket "solution" for game problems that just plain does not work. Check online for a list of the "best" and most stable versions.
Test your RAM thoroughly with MemTest86+ or some other RAM testing utility.
Run diagnostic and benchmarking utilities (Unigene Heaven is the best benchmark, bar none, at least for nVidia cards, and it's beautiful to watch too).
Snipping out my story about bad RAM, as it's boring and tedious. TL:DR test it thoroughly.
The OP was literally that it was knocking their PC out and no one says it isn't. You're essentially accusing someone of lying back in March. This isn't a new topic. This was boosted by someone else coming in just recently looking to see how it was resolved as they are having issues. Even low spec games can kill a PC, though I imagine with some extra factors than just the game did it. Going no it can't isn't productive. Accusing people of hyperbole and fear mongering is pointless and prickish.
But for me, it's the fact that the OP @OperationDX wants some help diagnosing the problem. If a game wanted to kill your PC, all it needs to do is run a crypto algorithm for about 60 seconds and that would do the trick for a lot of people with stock hardwware and no protection in place. It takes craft to kill a PC, and games hit all your senses, so they context switch too often too kill any one component under the hood.
Actually it is an overheat issue.. ive had two friends test it.. whenever they are near a bunch of lights ingame, or if they are mining, their GPU temps rise from 60 to 85 whenever they mine.
I turned my Graphics to Fast, Resolution to 1280x720 (16:9), and cap frames at 30. Shutdown went away.
Heat always spiked really hard and i was sure that the processing of particles when mining or blocks in POI's was the cause but I couldnt figure out why it would restart instead of just shut down. Then i read a thread that essentially said AMD stuff is power hungry and Empyrion makes my system use all its resources...so its likely going over the PSU capability which I believe is my bottleneck.
CPU - AMD FX-8350 4.0GHz 8-Core Processor
Cooler - Cooler Master Hyper 212 Plus 76.8 CFM Sleeve Bearing CPU Cooler (upgraded to dual Cooler Master SickleFlow 69.7 CFM 120mm Fan (one push, one pull out the top of the case))
Mobo - Gigabyte GA-970A-D3P ATX AM3+/AM3 Motherboard
RAM - G.Skill Ripjaws X Series 16GB (2 x 8GB) DDR3-1600 Memory
GPU - XFX Radeon R9 290 4GB Double Dissipation Video Card
PSU - Thermaltake Toughpower 550W 80+ Gold Certified Semi-Modular ATX Power Supply
Case - Corsair SPEC-02 ATX Mid Tower Case
HDD - Samsung 840 EVO 120GB 2.5" Solid State Drive
Seagate Barracuda 1TB 3.5" 7200RPM Internal Hard Drive