Jump to content

Computer Reboots On Launch?


17 replies to this topic

#1 blood4blood

    Member

  • PipPipPipPipPipPipPip
  • Bridesmaid
  • 527 posts
  • LocationVirginia

Posted 07 December 2017 - 04:15 PM

In the last few days my computer has rebooted a couple times while launching into a game. It's never done this before, and MWO was the only thing running. When I got back in I tried to re-join the game, but the re-join button was greyed out. Anyone else have this problem, or has my gaming PC got a ghost it never had before?

Edit: FWIW, it's an IBuyPower gaming PC running Windows 10 Home edition. I can get specs if needed.

Edited by blood4blood, 07 December 2017 - 04:17 PM.


#2 nightstalkker

    Member

  • PipPip
  • The Widow Maker
  • The Widow Maker
  • 35 posts
  • Locationcity of angels

Posted 07 December 2017 - 06:29 PM

a few weeks ago i had problems where my pc was doing the same thing. it got to the point where i final got a blue screen that said "critical process died" and no matter what i did my pc was stuck in restart mode. final i had to reinstall window completely.

#3 blood4blood

    Member

  • PipPipPipPipPipPipPip
  • Bridesmaid
  • 527 posts
  • LocationVirginia

Posted 22 December 2017 - 02:17 PM

Bumping this because it's happened twice this afternoon, and still only happens while playing MWO. Never happens with any other game. Also, PGI, quit with the re-join penalties when the only reason I couldn't re-join quicker is how long it takes to get through MWO's loading screens. My computer fully reboots in less time than it took to type this post, and I'm still waiting on the first MWO splash screen.

#4 knight-of-ni

    Member

  • PipPipPipPipPipPipPipPip
  • Overlord
  • Overlord
  • 1,627 posts
  • Location/dev/null

Posted 22 December 2017 - 03:07 PM

Spontaneous reboots are a sign of a hardware failure, even if it only seems to happen while playing MWO.
Run a memory checker.

#5 UnofficialOperator

    Member

  • PipPipPipPipPipPipPipPip
  • Ace Of Spades
  • Ace Of Spades
  • 1,493 posts
  • LocationIn your head

Posted 22 December 2017 - 03:40 PM

overheating gpu maybe?

#6 Tarl Cabot

    Member

  • PipPipPipPipPipPipPipPipPipPip
  • Tai-sho
  • Tai-sho
  • 7,824 posts
  • LocationImperial City, Luthien - Draconis Combine

Posted 22 December 2017 - 04:14 PM

Several reasons for the computer to reboot. By default if it is a software issue that would lead to BSOD or such by default most computers are setup to reboot now instead of stopping and showing the BSOD. Other reasons will be as above, overheating component or a component that is failing/unstable.

Disabling auto reboot is basically the same for the OS.

https://www.tenforum...ndows-10-a.html

https://www.eightfor...le-disable.html

I would also suggest downloading CPUID HWmonitor to help keep track of temps of CPU/GPU. It may be a good ideal of opening the case and clearing out the heatsinks of dust buildup Posted Image and to make sure the fans are operating correctly. Seeing the time of year it is, the need to heat up homes, both dust buildup and location of system may be working together to create an unsatisfactory environment.

Since you mentioned it has only done it while playing MWO, I am leaning more towards heat being the issue, and I do not mean of your mech... :) It could still be a system error tied in there but you need to get this resolved before a component is lost, or if a component is dying, locating the problem and replacing it before it takes other components with it.

Edited by Tarl Cabot, 22 December 2017 - 04:22 PM.


#7 Ghogiel

    Member

  • PipPipPipPipPipPipPipPipPipPip
  • CS 2021 Gold Champ
  • CS 2021 Gold Champ
  • 6,852 posts

Posted 22 December 2017 - 04:23 PM

Could be just about anything breaking down, my bets are on the psu, ram or gpu

#8 nehebkau

    Member

  • PipPipPipPipPipPipPipPipPip
  • 3,386 posts
  • LocationIn a water-rights dispute with a Beaver

Posted 22 December 2017 - 04:27 PM

@ OP
could be lots of things. You gotta follow your basic troubleshooting.... run a disk repair and memory test, load on a hardware monitor that logs to disk and turn it on and make your system crash.
Just to narrow it down you could have (in order of likeliness)
1. corrupt game data
2. corrupt drivers
3. memory fault
4. Physical drive failure
5. GPU heat issue
6. GPU failure
7. cpu heat issues (requiring reseating the heat sink)
8. PSU problems -- may need a new one
9. mainboard failing
10. Your partner turns on the giant magnetic cathode ray tube on the floor below you causing an EMP every time you load MWO

View PostTarl Cabot, on 22 December 2017 - 04:14 PM, said:

I would also suggest downloading CPUID HWmonitor to help keep track of temps of CPU/GPU. It may be a good ideal of

Edited by nehebkau, 22 December 2017 - 04:29 PM.


#9 Nightbird

    Member

  • PipPipPipPipPipPipPipPipPipPip
  • The God of Death
  • The God of Death
  • 7,518 posts

Posted 22 December 2017 - 06:05 PM

PSU is dying, can't provide power to CPU and PSU at the same time.

#10 blood4blood

    Member

  • PipPipPipPipPipPipPip
  • Bridesmaid
  • 527 posts
  • LocationVirginia

Posted 22 December 2017 - 08:14 PM

TY for the input, I'm going to run some tests. FWIW, I'm getting no BSOD, it just goes directly from game to reboot, no crash messages, no error messages, no blue screen, nothing but a normal reboot (and no error messages once it reboots either). Based on some limited, automated Win 10 troubleshooting, it wants to run the game in compatibility mode for Win 8, using the old launcher instead of the current portal. Hmmmm....I didn't have this problem until upgrading the launcher/portal, so there might be something going on there.

EDIT: Also, I play older more poorly optimized games (!) on this comp that make all the fans go to top speed. MWO doesn't, so even though I was also thinking heat/PSU at first, I really don't think that's it this time.

Edited by blood4blood, 22 December 2017 - 08:15 PM.


#11 Tarl Cabot

    Member

  • PipPipPipPipPipPipPipPipPipPip
  • Tai-sho
  • Tai-sho
  • 7,824 posts
  • LocationImperial City, Luthien - Draconis Combine

Posted 22 December 2017 - 09:59 PM

Unless you have changed Windows setting to NOT boot upon error, you will not see a BSOD, it simply reboots and you will generally not see anything else when logging back in. Your post does not say whether or not you have actually TURNED IT OFF, that is why I posted the links.

Edited by Tarl Cabot, 22 December 2017 - 10:00 PM.


#12 Sup4hsl4p

    Rookie

  • Philanthropist
  • 5 posts

Posted 22 December 2017 - 10:10 PM

^Haven't changed defaults, so no, I have not turned it off. (And yes, this is one of my alt accounts.)

EDIT: Have been running in compatibility Win 8 mode using the old launcher since that last post, and no problems at all so far. I think it's a patcher/launcher issue of some kind.

Edited by draiocht, 27 December 2017 - 05:08 PM.
alt forum account closed


#13 LordNothing

    Member

  • PipPipPipPipPipPipPipPipPipPipPipPip
  • Ace Of Spades
  • Ace Of Spades
  • 17,686 posts

Posted 22 December 2017 - 10:22 PM

sounds like a brownout. power supply issue.

i always blame the psu and im usually right 90% of the time.

Edited by LordNothing, 22 December 2017 - 10:23 PM.


#14 blood4blood

    Member

  • PipPipPipPipPipPipPip
  • Bridesmaid
  • 527 posts
  • LocationVirginia

Posted 22 December 2017 - 11:59 PM

Well, did about 5 hours straight in compatibility Win 8 mode using the old launcher, without a single error, no overheats, no PSU issues. Guess I'll just go back to the old launcher for a while.

#15 Tarl Cabot

    Member

  • PipPipPipPipPipPipPipPipPipPip
  • Tai-sho
  • Tai-sho
  • 7,824 posts
  • LocationImperial City, Luthien - Draconis Combine

Posted 23 December 2017 - 01:37 AM

View Postblood4blood, on 22 December 2017 - 11:59 PM, said:

Well, did about 5 hours straight in compatibility Win 8 mode using the old launcher, without a single error, no overheats, no PSU issues. Guess I'll just go back to the old launcher for a while.

Just remember, you first reported this on Dec 07 then again on Dec 22, so it would appear to be intermittent.

Turn off the auto reboot on error. Right now you should be able to look at your event logs since if it was a software/driver issue it would likely be listed, whereas if it was hardware issue/failure no errors would have been generated. And check your fan program settings. The heat threshold when they start ramping up may be set too low.

Edited by Tarl Cabot, 28 December 2017 - 03:17 AM.


#16 Jackal Noble

    Member

  • PipPipPipPipPipPipPipPipPip
  • 4,863 posts
  • LocationTerra

Posted 23 December 2017 - 01:49 AM

Never mind the fact that MWO is quite literally the worst optimized game on the current market and or probably decade. God only knows what effect it has on the life of one's hardware.

#17 draiocht

    Member

  • PipPipPipPipPipPipPip
  • 791 posts

Posted 27 December 2017 - 05:32 PM

[mod]This thread has been moved to
Workarounds.[/mod]

In case useful, help may be sought from PGI's Technical Support Staff by emailing technical@mwomercs.com.

#18 NARC BAIT

    Member

  • PipPipPipPipPipPipPip
  • Ace Of Spades
  • 518 posts
  • Twitch: Link
  • LocationAustralia

Posted 27 December 2017 - 07:48 PM

you didnt really mention enough information about the hardware to draw many conclusions .... and thats probably why everyone is quick to blame the PSU, before we even know what it is .... ryzen processors paired with some motherboards cat go into a protection mode far too early .... and some intel systems tend to output enough heat to push other pieces over tolerance ....

what do you mean exactly when you say the 'old launcher' ? do you actually mean the launcher that we used before the current portal ? you can bypass the 'portal', and just launch the game directly, and only use the portal on patch day ... but I wouldn't think it would make much difference .... about the same as using windows 8 compatibility mode, I would expect ... in terms of the age of the engine, you should probably be using a compatibility level more like vista/xp, but again, I cant imagine much benefit .... if you've got a x64 version of windows, you could simply try executing the 32 bit binary .... could be that simple ....

if your pc outrightly reboots with no error messages, no bsod etc, then you should probably start out by looking at the event viewer ....

for reasons that are beyond me, MWO can be quite stressful to a system in ways that most other software wont ... I actually find that its FAR quicker to reveal memory instability for me than some proper memory stress testing software ... in an instance that can take memtest take more than 6 hours to show an error, MWO will crash out in under an hour ....

I'd recommend you chase down some monitoring tools, like hwinfo32/64, to see how much duress your system is going through, if you also install MSI afterburner ( or just RTSS - rivatuner statistics server) you can configure hwinfo to show values on screen, while your gaming ...





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users