Mining in the game causing my computer to shutdown and restart.

[OperationDx]

I would say this is a nasty bug that could damage your computer.

[piddlefoot]

Do you have any software that monitors the motherboard heat ? Like ASUS suite or the like ?
Might be worth checking no slots are getting hot, if a video card is 60 degrees the slot is usually 70 degrees might be worth a look.

If its not heat then your likely getting a software conflict, whether its a driver or just something specific you installed that hates Empyrion is hard to know, but Empyrion has had alot of issues with sound related software thats not default motherboard sound, so if your running 3rd party sound software I would start there and shut it down to test. Or a physical sound card I would remove for testing.

When you mine its uses more CPU and RAM than when your doing almost anything else in the game. The active game file that is running in Unity is constantly having new info writen to it, when you mine your changing the map surface and this all needs to be saved on the fly so the game engine ''winds up'' a bit when you mine and the video card uses a little more too.

Can you access windows and bring up the 'conflict' log ?
That might show you where theres a conflict with Empyrion.

Have you , just by chance, tried swapping the RAM in your PC, slot one into slot two and slot two ram into slot one sort of thing ?

Maybe you have a bad sector that when writen to throws an exception.

Its really guesswork from here champ but I wish you luck.

I notice a few people have had issues with that model motherboard and there RAM slots dieing, might be worth reading into also.

[Umbrella]

You should be getting a BSOD with some detailed information that could help point out the problem. Be sure you're system has it enabled otherwise it might just shutdown. Alot of users asuming overheating because you're system like everyone eles will auto shutdown without BSOD for safty reason to prevent damage from you're hardware.

Also, are you on Win10? go back in you're nvidia driver to 340's or maybe try windows under 10 or another system.

[gibsondude]

Have you managed to solve the problem? I too am suffering quite badly with this game... It ran ok for a week or so, but as my base built up (Over 10,000 blocks) random shutdowns began to occur. I was under the impression that one of my HDD's was on its way out due to a few BSOD's with "Unexpected_store_exception" error codes whilst playing the game, so I replaced it with an SSD and reinstalled Windows 10 and a fresh download of Empyrion. Now though, I no longer get the BSOD's, my 'pooter just shuts off... Really annoying... I don't think it's temps causing the issue... I ran all the fans in my system at 100% and tried the game... 10 minutes in and it shut off again... The idle temperature on my CPU varies between 14-23C and under load it never goes past 60C... GPU is similar, Idles around 28C but doesn't exceed 70C under stress... Any ideas?

My rig:
AMD FX8320 - 8 Core @ 4ghz
G-Skill RipjawsX 16Gb 2133 DDR3
Gigabyte 990X Gaming Sli Motherboard
Gigabyte Nvidia GeForce GTX970
Corsair H80i Watercooler
ACE 850watt PSU

[zaphodikus]

I only have a 750TI and when I'm in a tight spot building a ship, the graphics drivers will die sometimes - and then recover. I'm guessing due to a resource leak. It ends up happening every few minutes after that, but Normally if I reboot later on, the drivers are fine and I move to another bit of building.

[zaphodikus]

amd cpu's are known for randomly suddenly overheating - replaced the cpu and mobo on my son's machine just 3 weeks ago - started out it was overheating RAM, but the CPU also went suddenly and damaged the mobo.

[piddlefoot]

Thats not really true, AMD CPUs only heat up for a reason, they dont just heat spike on there own dude.

As you play and add more blocks to your structure and it goes into the tens of thousands of blocks, as you spin your character around the PC has to allow for drawing new parts of the map and your builds in the distance or other builds, the longer a game goes the more work a CPU and GPU are doing in Empyrion.

Your systems are simply being overwhelmed with small heat spikes by the sounds of it.

But heres the really bad news.

MOST GPUs around 1000mhtz with no Water cooling and even some with, that are wound up to close to 100% use where Every shader pipe is in action sucking real volts into the chip, making the chip almost vibrate with life so to speak, will overheat after a short time, they really dont come with very good cooling abilities, and theres a good reason for this.

Designed Obsolesence.

A chip that runs really hot usually only runs for 5 to 8 years and fries and alot of the time fries before that, but worse in that time it will run like a pig under heavy loads, with shut-downs becoming the norm for heat spikes.

Even water cooling is full of gimicks and alot of poorly designed cooling systems, you really need an exceptional water cooling system for your high end GPU with a very large radiator so it holds ALOT more water.

Keep in mind I live in the tropics of Queensland Australia where our average temps are much higher than most other areas, if you live in a snowy area alot of this isnt going to apply to you, but if yo live in a hot area, when buying a video card, consider its cooling capabilities.

Even in a snow region setting up an Extreme Fan Profile is still a really good idea.

[zaphodikus]

True, it is hearsay, that seems to go around very easily. I did a bit of research and AMD overheating issues are very much anecdotal/hyped up.

[gibsondude]

I don't want to speak too soon, but I think I may have solved my own problem! I did a bit of digging around in my system event log and noticed that straight before a critical crash, a call was sent to npsvctrig.sys... Possibly a critical system file or a driver of some kind... I ran the driver verifier app built into Windows 10 to see if any drivers were having issues:

Here is the procedure:
Go to Start and type in "verifier" (without the quotes) and press Enter
Select "Create custom settings (for code developers)" and click "Next"
Select everything. Don't check "DDI compliance checking" and "randomized low resource simulation", then click "Next"
Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
Select "Finish"
Then reboot.

Now, for me, windows wouldn't boot past the login screen after enabling the driver verifier... I rebooted several times and kept getting a BSOD everytime...
Booted into safemode and turned off driver verifier (by typing "verifier /reset" from an elevated command prompt, without quotes).
Rebooted, windows loaded... Downloaded a program called BlueScreenView from http://www.nirsoft.net/utils/blue_screen_view.html and loaded up one of the *dmp files created by driver verifier (c:\windows\minidump\)... right at the top of the list there was 1 conflict, a file called gdrv.sys, again, google to the rescue... As it turns out, gdrv.sys is a file used by quite a few Gigabyte motherboard and Gfx applications... I uninstalled everything related to Gigabyte on my system and re-ran the driver verifier process again... Only this time, windows booted straight away... No BSOD or anything... I've just had a 5 hour session on Empyrion and everything was groovy, no reboots, no glitching and even the massive frame drops seem to have subsided...

As for npsvctrig.sys, well, I don't know what its issue was, but it's not whining anymore, so I've left the lil' bugger alone... It must have just conflicted with gdrv.sys for some reason, but now the latter has been removed, npsvctrig.sys can do its thang :D

Edit:
Also, just to add... I still don't know why this conflict was only happening whilst playing Empyrion...

[dakman-The Pie Master]

โพสต์ดั้งเดิมโดย gibsondude:

I don't want to speak too soon, but I think I may have solved my own problem! I did a bit of digging around in my system event log and noticed that straight before a critical crash, a call was sent to npsvctrig.sys... Possibly a critical system file or a driver of some kind... I ran the driver verifier app built into Windows 10 to see if any drivers were having issues:

Here is the procedure:
Go to Start and type in "verifier" (without the quotes) and press Enter
Select "Create custom settings (for code developers)" and click "Next"
Select everything. Don't check "DDI compliance checking" and "randomized low resource simulation", then click "Next"
Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
Select "Finish"
Then reboot.

Now, for me, windows wouldn't boot past the login screen after enabling the driver verifier... I rebooted several times and kept getting a BSOD everytime...
Booted into safemode and turned off driver verifier (by typing "verifier /reset" from an elevated command prompt, without quotes).
Rebooted, windows loaded... Downloaded a program called BlueScreenView from http://www.nirsoft.net/utils/blue_screen_view.html and loaded up one of the *dmp files created by driver verifier (c:\windows\minidump\)... right at the top of the list there was 1 conflict, a file called gdrv.sys, again, google to the rescue... As it turns out, gdrv.sys is a file used by quite a few Gigabyte motherboard and Gfx applications... I uninstalled everything related to Gigabyte on my system and re-ran the driver verifier process again... Only this time, windows booted straight away... No BSOD or anything... I've just had a 5 hour session on Empyrion and everything was groovy, no reboots, no glitching and even the massive frame drops seem to have subsided...

As for npsvctrig.sys, well, I don't know what its issue was, but it's not whining anymore, so I've left the lil' bugger alone... It must have just conflicted with gdrv.sys for some reason, but now the latter has been removed, npsvctrig.sys can do its thang :D

Edit:
Also, just to add... I still don't know why this conflict was only happening whilst playing Empyrion...

That's awesome dude! I mya have to do that with my friend's computer, since it seems he is having the exact same issue, plus I think he has a Gigabyte MOBO.

[VulcanTourist]

I have a Gigabyte Z77X-D3H motherboard, and have had no similar issue even though several Gigabyte utilities are allowed to execute at boot and at least an updater runs 24/7. I do not seem to have the same utility(-ies) as you, however. Given your original description of the symptom, though, my suspicion based on career and personal experience would have been a thermal issue with the graphics card.

In addition to BlueScreenView for BSOD diagnostic purposes, I would also recommend another utility called WhoCrashed, if you can find it.

[talk2rider]

I smoked two identical "el crappo" PSUs playing Empyrion. It turned out the model of power supply that came with my "gaming PC" was NOT a single rail PSU. One side of the power supply would overheat and shutoff, causing the load to all go to the other side which immediately resulted in a puff of smoke. The fix was to buy a single rail power supply and try to keep it cooler. Apparently the GPU really gets a workout with Empyrion and draws its max power. Played 300+ hours of modded-up Skyrim no problem, started running Empyrion and it couldn't take it. Everything seems to be fine now though with the better PSU. I have the AMD R9 390 GPU by the way. Seems to be a pretty good card driver-wise, but I hear it is not very efficient.

[VulcanTourist]

โพสต์ดั้งเดิมโดย talk2rider:

I smoked two identical "el crappo" PSUs playing Empyrion. It turned out the model of power supply that came with my "gaming PC" was NOT a single rail PSU. One side of the power supply would overheat and shutoff, causing the load to all go to the other side which immediately resulted in a puff of smoke. The fix was to buy a single rail power supply and try to keep it cooler. Apparently the GPU really gets a workout with Empyrion and draws its max power. Played 300+ hours of modded-up Skyrim no problem, started running Empyrion and it couldn't take it. Everything seems to be fine now though with the better PSU. I have the AMD R9 390 GPU by the way. Seems to be a pretty good card driver-wise, but I hear it is not very efficient.

Your anecdote is another good example why I abandoned AMD graphics processors with my last upgrade. The Nvidia generation at the time (I chose GTX 960) was so much more efficient with power there was no possible debate. If you had an equivalent Nvidia product the cheap power supply might still have been sufficient. The same happened with CPUs when Intel released the Ivy Bridge generation: bye-bye, AMD. I love the underdog, but not when the underdog is six feet under.

[talk2rider]

I would tend to agree with you. I was new to all this and bought what I thought was a decent gaming pc for $800. I was not completely sure I would even use it that much, but as it turns out I really like gaming on the PC. My XBOX ONE is now just a door stop.

[ChosenOne]

โพสต์ดั้งเดิมโดย OperationDx:

I would say this is a nasty bug that could damage your computer.

It's a known issue in the game. When you mine the levels of heat of the pc and the gpu are going up like crazy.. So if you do not have a good cooling system, then better do not touch this game for the sake of your pc

[VulcanTourist]

โพสต์ดั้งเดิมโดย ChosenOne:

โพสต์ดั้งเดิมโดย OperationDx:

I would say this is a nasty bug that could damage your computer.

It's a known issue in the game. When you mine the levels of heat of the pc and the gpu are going up like crazy.. So if you do not have a good cooling system, then better do not touch this game for the sake of your pc

That is quite the blanket statement ya got there, to compound the fear-mongering hyperbole that preceded it. Do you both work for Homeland Security?