Computer crashes when starting up games

[James Jae]

Hello everyone,

so I have the Aorus x7v2 gaming laptop, I've had it for almost a year now. When I first got the computer everything ran fine- up until recently I'm not sure when it all went wrong but when I launch games on the computer I'm always stuck at the startup and the computer completely freezes and then reboots itself, I just upgraded to Windows 10 (because why not, right?) and I'm still having this issue. Can anyone help? What should I provide you guys with in order to help fix this issue.

https://www.youtube.com/watch?v=F_km-VnTluQ

This is a video of what happens, I show the screen I'm prompted with towards the end.

 

[Vynavill]

Does this happen with ALL games? Otherwise, which games is this happening with?

Also, provide your full system specs and, if possible, temperatures. Looks like it's rebooting to BIOS, for some yet unknown reason, but if it happens with just a handful of games and it NEVER happened before upgrading the OS, it's rather safe to assume it's a W10 incompatibility issue.

 

[James Jae]

Does this happen with ALL games? Otherwise, which games is this happening with?

Also, provide your full system specs and, if possible, temperatures. Looks like it's rebooting to BIOS, for some yet unknown reason, but if it happens with just a handful of games and it NEVER happened before upgrading the OS, it's rather safe to assume it's a W10 incompatibility issue.

Well this was happening in Windows 8.1 aswell and it's mainly with Nosgoth and Dragon Nest; which isnt playable with Windows 10 as of current but Nosgoth still works (for others). It reboots to Bios and I'm not sure what to do so I usually go back to my PC as normal.

Specs:

 

[Vynavill]

Well...It's a laptop, but 50 degrees at (seemingly) idle is slightly high. As a side note, I see no information there about the GPU. I can Google up the model, but no one can know the temperatures unless you tell them 😛
They're not necessarily the issue, but it's usually good to ascertain they're not, for good measure.

Anyway, for Dragon Nest, I'd wait until it's made compatible before actually judging, while for Nosgoth, I really don't know.
From what I've experienced, rebooting into BIOS is something that usually happens out of a direct request or due to an overheating issue.

If you have any game that weights on your hardware as much as (or more than) Nosgoth, try and see if a reboot happens with that as well.
Otherwise, you might want to take a look at the event log windows automatically keeps and see why it's rebooting, if there's any reason.

 

[James Jae]

https://drive.google.com/open?id=0BzdQq2h4bsHgeUtxY25VSE0yWFk

I tried to turn on the pc to get temps and this is what happens and now when I'm at the login it seems my wifi isn't working and i can't even type in the login

 

[Vynavill]

That error code usually comes up due to a hardware failure, from what I've found looking around the Internet. The issue is it doesn't tell which one, so it might range from an external peripheral that got marked as mandatory (for some reason) to a component in your laptop (most of the times, either the DVD drive, if you have one or the HDD).

As implied, you need your OS media to run recovery mode and hope for the best. If you don't have a DVD drive, you can make a USB via an installation tool provided by Microsoft.

 

[James Jae]

That error code usually comes up due to a hardware failure, from what I've found looking around the Internet. The issue is it doesn't tell which one, so it might range from an external peripheral that got marked as mandatory (for some reason) to a component in your laptop (most of the times, either the DVD drive, if you have one or the HDD).

As implied, you need your OS media to run recovery mode and hope for the best. If you don't have a DVD drive, you can make a USB via an installation tool provided by Microsoft.

Somehow I left the computer on over night and I'm able to get on here again, I'm going to leave it on as long as I can but is there anything I should download right now *ASAP* to see what could have went wrong?