Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Have you tried using Ubuntu / other Linux distro installed on flash disk?
Without analyzing those dumps, superficially they suggest a hardware fault, not directly related to any specific device or its driver. PSHED is WHEA's hardware error driver. HAL is hardware abstraction layer, the thing that talks between your hardware and kernel. ntoskrnl is the windows NT kernel.
From that and everything else you got (seemingly random BSODs when plugged in, doesn't BSOD when unplugged, halts when adjusting power configuration, doesn't crash when booted to memtest) I'm guessing it's related to ACPI and hopefully not a physically faulty hardware component that would have to be replaced.
These things are really hard to debug without having physical access to the machine, so many variables, so many things to look for and try... You said you've tried OS reinstall, and that fixed it - for a day? I assume you started installing drivers and software after that day. Maybe try booting into safe mode, and start removing/disabling extraneous stuff one by one. The URL in BSODs has instructions on how to do that.
I'd take it to some 3rd party mechanics if it has any connection with faulty electricity tbh. When the shit hit the fan, it hits hard, sometimes as hard as buying new one.
Both error code refer to faulty hardware / driver somewhere, image is default BSOD hardware-related code while WHEA is code for sudden shutdown to protect system from data loss, basically side effect from it.
As for voltage, it should be handled by the charger adaptor, which is why you shouldn't use other laptop's charger, even when it fits, unless you already triple check it has exact same voltage / ampere stuff.
If you could open up your laptop, have you tried the good ol' classic "plug off and give hard blow on it" trick? Maybe your RAM socket are dirty (which hopefully might fixed your problem), else I'd just bring it to nearby PC service
Well there's a clue at least. You could try running without battery. If it still bsod, then there's something wrong with charging port, else, it's battery.
Or it can simply caused by faulty driver, since Google search also pointed out to display-related driver and "fast charging" 3rd party app
I'd like to tell you to google the stop code, but ever since Microsoft advocated doing that, it's been hard to find anything useful amongst the deluge of crud. You could also try googling the stop code with your laptop model in case it happens to be a common issue with your hardware.
Welp, WHEA is Windows Hardware Error Architecture. Your hardware is still failing. Or it could be a very badly behaving device driver, but that's unlikely.
A good starting point would be analyzing your minidumps or memory dumps. I recommend BlueScreenView for that. Microsoft's own WinDbg is another good tool but it's not beginner-friendly.
If all the dumps point to same driver file, there's your faulty hardware. If they point to seemingly random files, it could be faulty CPU/RAM/motherboard or perhaps something unforeseeable.
I can't vouch for the warranty repair quality of MSI (or any other firm selling gaming PCs), but at least your laptop passed their tests. Could be they aren't very good at their job. Could be it got damaged in transit. But you should think if there's anything weird in the way you use the laptop. Is it always getting normal air circulation?
And can you think of any patterns when the BSODs occur? Like, say, only during heavy CPU load? Or RAM? GPU? VRAM? Only during specific games or other activity? Only after the laptop's been on for n hours?
. It will be quite the learning process.
what kind of gear am I looking for also
