Can someone explain to me why my Acer Predator laptop keeps turning off after a few minutes: Blue screen with the explanation that a problem has occurred on my PC, the time to recognize the error code I don't have this display again within approximately half a second is away.
When I start it up again it says: no bootable device. Then you have to go into the BIOS and bring the Nvme2 from drive C back to the first place in the boot sequence.
I'm at the end of my game… Smile
Reinstall windows
If no bootable device is available / has been selected in the boot option, then it can't start from it either.
Would try to install a BIOS update.
To analyze the cause of the blue screen:
https://docs.microsoft.com/...crash-dump
https://docs.microsoft.com/...-dump-file
Meaningless.
Could be a driver problem, was anything changed / installed recently?
Otherwise I'd start in safe mode and see if that's the case there. I also had the case that problems were gone after a single start in the safe mode.
So without an error code it is always difficult to say, but it can be a broken bootloader or a broken hard drive. I would rather not assume overheating, that would not really explain why the boot order is changed.
I think the easiest way is to reinstall Windows.
A broken bootloader
Then Windows would not even start.
a broken hard drive
Could be, but then the system would a) not start at all or b) not always stop after the same time. That would usually make itself felt differently.
I think the easiest way is to reinstall Windows.
Pointless here…
So without an error code it's always difficult to tell
Correct. Therefore my advice to have a memory image generated and then evaluated. Everything else is just haphazard guesswork.
why the boot order is changed.
Either hardware problems or the BIOS causes problems (-> update)
Then Windows would not even start.
Well that's possible, depending on how broken it is. Have we ever had the problem with us?
Could be, but then the system would a) not start at all or b) not always stop after the same time. That would usually make itself felt differently.
Of course, the system can still start with a broken hard drive. When it comes to hard drives, there's broken and not really healing. These are wearing parts and depending on how old they are, the PC may crash after a while
Pointless here…
No… Could fix the problem and it will be done quickly.
Correct. Therefore my advice to have a memory image generated and then evaluated. Everything else is just haphazard guesswork.
Yes, you are right about that, but haphazard guessing is not really that either.
Either hardware problems or the BIOS causes problems (-> update)
That's right, but before I recommend someone do a BIOS update, I'd rather go through other possible factors. That's why I deliberately left it out at first.
It could also be due to a virus that has penetrated deep into the system. I've already had something like this with a customer. The virus was anchored relatively deep in the system and always crashed after 5 minutes. With the virus the rest crashed and there was a BSoD. This would also be fixed by restarting Windows.
Well that's possible, depending on how broken it is. Have we ever had the problem with us?
If a started OS crashes, it has nothing to do with the boot loader - it also doesn't change the boot order.
Of course, the system can still start with a broken hard drive. When it comes to hard drives, there's broken and not really healing. These are wearing parts and depending on how old they are, the PC may crash after a while
As I wrote earlier:
Could be, but then the system would a) not even start or
b) don't always go out after the same time. That would usually make itself felt differently.
;)
That's right, but before I recommend someone do a BIOS update, I'd rather go through other possible factors. That's why I deliberately left it out at first.
Well, that the boot order changes - there's either a hardware error or the BIOS to blame. Especially since the BIOS should be updated occasionally anyway…
It could also be due to a virus that has penetrated deep into the system. I've already had something like this with a customer. The virus was anchored relatively deep in the system and always crashed after 5 minutes. With the virus the rest crashed and there was a BSoD. This would also be fixed by restarting Windows.
Maybe - but that's rarely the case. Simply reinstalling on good luck does not bring much, especially since a data backup is required beforehand and if a virus is actually present, the files should be cleaned first, otherwise the reinstallation is pointless.
With the exception of certain viruses and Trojans, reinstallation is rarely required.
