Transport Fever 2

Transport Fever 2

View Stats:
Crashed and restarted my Computer
After installing the latest update the game seemed to be playing well, then it just froze, the screen went black, my computer shut down and restarted. Luckily it hasn't seemed to have done any lasting damage to my computer system. Very disturbing incident!.
< >
Showing 1-15 of 18 comments
Martin Jun 25, 2020 @ 5:40am 
Good practice after patching to restart your pc anyway. At the very least restart steam. just incase there's another patch waiting.
SoftwareSimian Jun 25, 2020 @ 6:50am 
Crash-and-reboot is unlikely to be this (or any) game, far more likely to be flaky hardware (poor cooling, clocked too high, actually defective, just getting old, etc) or hardware drivers.
Crash-to-desktop you can blame the application (game), crash-and-reboot is usually something lower-level.
marc345 Jun 25, 2020 @ 6:52am 
Can also be due to high energy use and a bad power supply.
Martin Jun 25, 2020 @ 8:41am 
Originally posted by SoftwareSimian:
Crash-and-reboot is unlikely to be this (or any) game, far more likely to be flaky hardware (poor cooling, clocked too high, actually defective, just getting old, etc) or hardware drivers.
Crash-to-desktop you can blame the application (game), crash-and-reboot is usually something lower-level.
Yeh for me it's usually turned out to be a failing psu. But lately was due to my overclocking my ram slightly too high. That's solved now tho. And it wasn't tpf causing it.

But it can be due to a patch, if you've run the software and it's still in memory for example, updating the file then starting it can cause fatals that might bluescreen you and force a restart or cause gpu to overheat and cause a restart..

And since it's just patched again.. off to restart.. :D
Last edited by Martin; Jun 25, 2020 @ 8:43am
desrtfox071 Jun 25, 2020 @ 10:11am 
crashes and reboots are not caused by userspace applications, i.e games, but are instead caused by OS issues, driver issues, or hardware issues. Please apply all OS patches and update all drivers. Assuming that doesn't fix the issues, then run some datalogging monitor tool to keep track of heat and voltage. Heat issues and voltage drop issues are very common on modern PCs. Additionally, the OP should probably run some tests on the RAM and drive integrity. Userspace applications can expose underlying conditions, but they can't cause them, so the issue lies in hardware, OS, or drivers. Hopefully this will at least point the OP in the correct direction to fix the underlying issues.
Tom Jun 25, 2020 @ 1:07pm 
Yeah, +1 for those that mentioned failing power supply. The answers so far look like good suggestions.

I've had this happen to me in transport fever and X4. Lowering the graphics settings stopped the sudden restarts for me - less load on graphics card. But this isn't really a solution to the fundamental problem, which most likely is to fix/replace your psu
larry_roberts Jun 25, 2020 @ 5:23pm 
Originally posted by SoftwareSimian:
Crash-and-reboot is unlikely to be this (or any) game, far more likely to be flaky hardware (poor cooling, clocked too high, actually defective, just getting old, etc) or hardware drivers.
Crash-to-desktop you can blame the application (game), crash-and-reboot is usually something lower-level.

I've heard this said to many others who have witnessed similar events, how come it only happens with this game?!. Also as I turned on my computer just a few minutes ago there was another small TF2 update, clearly the dev's are correcting ongoing problems with the game!. Maybe they have pushed the game to it's absolute limits (and I appreciate just how good the game is), but if they risk damaging peoples computers that is taking things a bit too far!.
larry_roberts Jun 25, 2020 @ 5:42pm 
Originally posted by Martin:
Good practice after patching to restart your pc anyway. At the very least restart steam. just incase there's another patch waiting.

Yes I would have done this, but I have a problem with my computer, if I go to windows settings (win 10 latest update) and it tells me 'downloading updates' I know I mustn't shut down my computer. if I shut down my computer at that point it won't restart again, it hangs at BIOS screen, all I can do when that happens is switch the computer off and on again about 3 or 4 times until it reluctantly (dots spinning slowly) restarts!. I've found that if I go to windows update and there are no updates in progress I can shut the computer down and it will start/restart fine!. I've spoken to microsoft and one chap recommended a complex repair job (which may have done more harm than good, if I could manage to follow it) and other pointed me to a web page which showed me how to shut down automatic updates, which I don't really want to do!.

So, I'am going to stick to ensuring that the settings page isn't telling me 'downloads in progress' even though (when I go to win update) windows update is telling me last download at etc.

The point is I don't want some program restarting my computer until I'am ready to do it!. Sorry for the long winded explanation!.
desrtfox071 Jun 25, 2020 @ 5:43pm 
Originally posted by larry_roberts:
Originally posted by SoftwareSimian:
Crash-and-reboot is unlikely to be this (or any) game, far more likely to be flaky hardware (poor cooling, clocked too high, actually defective, just getting old, etc) or hardware drivers.
Crash-to-desktop you can blame the application (game), crash-and-reboot is usually something lower-level.

I've heard this said to many others who have witnessed similar events, how come it only happens with this game?!. Also as I turned on my computer just a few minutes ago there was another small TF2 update, clearly the dev's are correcting ongoing problems with the game!. Maybe they have pushed the game to it's absolute limits (and I appreciate just how good the game is), but if they risk damaging peoples computers that is taking things a bit too far!.
It "only" happens with this game because this game is the only application you run that stresses your PC in the this particular way. This stress causes a failure in your hardware or OS or drivers.

The HAL prevents userspace applications from hard crashing your system. Such failures are cause only by your hardware, OS or driver issues.
larry_roberts Jun 25, 2020 @ 5:48pm 
Originally posted by desrtfox071:
Originally posted by larry_roberts:

I've heard this said to many others who have witnessed similar events, how come it only happens with this game?!. Also as I turned on my computer just a few minutes ago there was another small TF2 update, clearly the dev's are correcting ongoing problems with the game!. Maybe they have pushed the game to it's absolute limits (and I appreciate just how good the game is), but if they risk damaging peoples computers that is taking things a bit too far!.
It "only" happens with this game because this game is the only application you run that stresses your PC in the this particular way. This stress causes a failure in your hardware or OS or drivers.

The HAL prevents userspace applications from hard crashing your system. Such failures are cause only by your hardware, OS or driver issues.

Your point about 'this is the only application that stresses my PC this way' may well be valid!.
desrtfox071 Jun 25, 2020 @ 6:00pm 
Originally posted by larry_roberts:
Originally posted by desrtfox071:
It "only" happens with this game because this game is the only application you run that stresses your PC in the this particular way. This stress causes a failure in your hardware or OS or drivers.

The HAL prevents userspace applications from hard crashing your system. Such failures are cause only by your hardware, OS or driver issues.

Your point about 'this is the only application that stresses my PC this way' may well be valid!.
Yeah, but keep in mind that this could happen from something else in the future because it isn't the game causing the issue. Until you find the actual cause, this may still happen.

Think of it like this: You drive up to your local fast food restaurant drive through (just go with it even if you don't eat fast food). You order 10,000 meals. The restaurant says "OK. Coming right up". Then the restaurant proceeds to burn itself down. This is similar to what's going on here. The person placing the order (the game) is not the cause of the burndown. Something else caused that burndown, but not very many people order 10,000 meals.


(The window attendant at the drive through is kind of like the HAL in modern OSes. The HAL responds to requests from the userspace applications. If the HAL says OK, then in theory, the PC should perform. Either way though, the application only sends requests through the HAL to the hardware. It doesn't talk to the hardware directly.)
Last edited by desrtfox071; Jun 25, 2020 @ 6:04pm
larry_roberts Jun 25, 2020 @ 6:21pm 
desrtfox071: You, obviously, know a great deal about computers. I mentioned -earlier- an issue I'am having with windows (10) update, is there any easy (it's got to be easy for me) way to fix this!. Thankyou, for your words of wisdom above!.
desrtfox071 Jun 25, 2020 @ 6:37pm 
Originally posted by larry_roberts:
desrtfox071: You, obviously, know a great deal about computers. I mentioned -earlier- an issue I'am having with windows (10) update, is there any easy (it's got to be easy for me) way to fix this!. Thankyou, for your words of wisdom above!.
I'm not sure I'm fully understanding your issue, so I'm going to paraphrase it so you can correct me.

It seems like you're saying that if you reboot your PC while a Win10 update is in progress, your PC won't boot, and sits at the BIOS screen. then you have to reset the PC several times to get it to properly boot. If you reboot your PC when a Win10 update is not in progress, everything works fine?

If that is the case I would suggest, first not rebooting during the patch application process - the OS specifically states this. Second, if it's only in the downloading phase of the update and you still get the issue, this sounds like a write issue to your drive. I would suggest running some diagnostic checks on your OS drive. When you're sitting at the BIOS screen, does it say anything, like "No OS/boot drive available" or something about RAM, or maybe even no keyboard connected?

The boot failure means that there is almost certainly a hardware issue somewhere. That could be your mainboard, your OS drive or RAM. There are other possibilities as well, but if this happens again, write down, or take a photo of what your BIOS screen displays when it is hung. That should give some insight as to what piece of the PC isn't responding correctly. Again, though, based on your description I would lean towards the OS drive, and drive corruption.

You are only pressing the reset button when the system is frozen, correct? You aren't pressing the reset button to generally reboot your PC, right? You should do that from within the OS options to reboot.

Last edited by desrtfox071; Jun 25, 2020 @ 6:38pm
larry_roberts Jun 25, 2020 @ 8:01pm 
desrtfox071:

It seems like you're saying that if you reboot your PC while a Win10 update is in progress, your PC won't boot, and sits at the BIOS screen. then you have to reset the PC several times to get it to properly boot. If you reboot your PC when a Win10 update is not in progress, everything works fine?. I normally only press the on button to turn the computer on, but if it's frozen at the BIOS I have no choice but to turn it off and on again a few times!.

Yes and No, it 's saying (on the first settings page) that it's updating but when I click on it (where it says updating) or go to windows update it says windows updates checked X time ago, so clearly it's not actually updating , yet if I try to restart my computer without confirming updates are not actually taking place I get the problem. Also it's only recently win 10 showed the new settings page (i.e with my name microsoft account, one drive manage, windows update at the top of the settings page) prior to this I didn't get the windows update details on the settings page and (although I suspected it) I didn't really know what was stopping the computer booting up!.

So, at least now, I get some warning that my computer isn't going to boot up next time I start/restart it but if I forget to check windows update before I shut down the computer then I'am going to have the problem again. I get the feeling that windows update isn't quite fully completing the update check and leaving the erroneous message about downloading!.

Also, you talk about the reset button, to me it's just the on/off button for the computer, and, again, I suspect that if I unplugged the computer (when it's refusing to restart) that might clear the problem, or if I switched off my modem (is it called, that's how dumb I'am about computers) that might clear the problem. It's like the computer is trying to access the internet while it's booting up and that's whats blocking the boot up process!. It's just an annoying problem!. I just have ensure I check windows updates before shutting the computer down!.

I have run some diagnostics checks on my computer and one microsoft agent came up with this:

Windows Resource Protection did not find any integrity violations


Okay. I suggest you to perform Automatic Repair using Windows 10 installation media.
If you don’t have an installation media. I request you to download and create an installation media of Windows 10 from the below link.
Download Windows 10
http://www.microsoft.com/en-us/software-download/windows10
Refer to the steps below to perform an Automatic Repair:
1. Insert the installation USB media and boot Windows Technical Preview from it.
2. In the ‘Windows setup’ page select the ‘language to install’, ‘Time and currency format’ and the ‘keyboard or input method’ and click on ‘next’.
3. Click on ‘Repair your computer’ and select ‘Troubleshoot’.
4. Select ‘Automatic Repair’ and select the operating system.
5. You will then see a blue screen and an option to choose. Choose the option Troubleshoot and select advanced options.
6. You may choose Automatic Repair from Advanced boot option.
7. Follow the instructions.

Which (with me being a technical idiot) seems like it might cause more problems than it will solve and also (as I said) I'am looking for an easy fix!.

Thankyou for your advice (sorry to lay this on you), this is the wrong place to air this anyway!.
Last edited by larry_roberts; Jun 25, 2020 @ 8:09pm
Martin Jun 25, 2020 @ 9:01pm 
Originally posted by desrtfox071:
Originally posted by larry_roberts:

I've heard this said to many others who have witnessed similar events, how come it only happens with this game?!. Also as I turned on my computer just a few minutes ago there was another small TF2 update, clearly the dev's are correcting ongoing problems with the game!. Maybe they have pushed the game to it's absolute limits (and I appreciate just how good the game is), but if they risk damaging peoples computers that is taking things a bit too far!.
It "only" happens with this game because this game is the only application you run that stresses your PC in the this particular way. This stress causes a failure in your hardware or OS or drivers.

The HAL prevents userspace applications from hard crashing your system. Such failures are cause only by your hardware, OS or driver issues.

This is a pointless argument, if the software is patched so that it "improves" how the hardware reads data, but somehow fails or if in making it improved, it causes the hardware to overheat or use higher voltages, which in turn can cause issues stemming from a wearing out psu or a psu which isn't spinning it's fan up properly due possibly to dust collections.. it's still the patch that caused the problem.. so it's still a software issue and yes you do still get bluescreens and sometimes restarts. It's a combination issue, caused in part by software and in part by failing hardware. All hardware fails eventually.

Yes, in the perfect world people would reinstall their os, they'd run memtests and hardware checkers etc, but realistically, people cannot do these things because they don't know how to. It's easier for them to just think, it worked before, it was patched, it doesn't work now, so it's the game to blame. And essentially they're right, if the game worked fine before the changes.

Software and Hardware are meshed together and arguing exact causes and what do or doesn't cause reboots etc is pointless, because it's an issue that can be caused by so many different issues all stemming from a software update or change to the core code, updating drivers is only required if the core code itself has actually been updated to use those new drivers, otherwise, you could actually be making it worse by updating them, which is why sometimes it's suggested to roll back drivers.. ie un update.

Tpf2 is a resource hungry game, any sudden changes can cause problems. Let's work out exactly what they are before playing the blame game or trying to make everything a technically technical issue.

With reference to reinstall or repairing win10, due to the speed win10 installs and moderately updates, depending on internet download speed, cpu, hdd etcetc. I'd usually suggest that if you feel an o/s repair is needed, to backup your important files, then reinstall windows. windows drivers, motherboard drivers etc fresh, rather than repair.. as repairing usually only replaces core software, it doesn't fix the underlying issue or even replace other core systems that could be interacting. I find it's best to start with a clean slate.. even going to the point of deleting the partition on the hard drive, re partitioning and reinstalling fresh.

In this instance i'd hold off doing anything drastic unless it happens with every game start. There's usually a good chance that a simple "switch it off, switch it on" will fix it.

In the past I've found that the cause of the crash was actually the saving process the game made. Changing this resolved the problem. Didn't do any hardware changes or driver updates. Just changed autosave from 1 to 5..
Last edited by Martin; Jun 25, 2020 @ 9:14pm
< >
Showing 1-15 of 18 comments
Per page: 1530 50

Date Posted: Jun 25, 2020 @ 4:41am
Posts: 18