New
#1
BSOD on a new HP laptop (0x000000010e, 0x000000050)
Hi guys.
First of all, sorry if my post isn't perfectly written but English isn't my first language.
I am contacting you because I rented a HP laptop in March and have had problems since then. More specifically, I keep getting BSOD (usually one or two a day, but more rarely none or more) when I close it (I mean physically, not when I shut Windows down) and the technical service can't find out the problem.
So, here we start.
A month ago, after getting another BSOD I sent it back and the guy from the technical service said it was the HDD that had probably got damaged by an electrical shock and he replaced it but asked me to put a UPS (I am using a Nilox they suggested me) between the plug and the laptop so it could be more protected. It really didn't solve anything.
I sent it back a couple of weeks ago and I withdrew it on Friday. The guy said HP updated the BIOS and a few other things because they think the problem is software related. After 2 days, same as before.
I tried to check the RAM using both HP built-in software and Memtest86+, none of which found any problem with it.
I also tried to update some more software, to see if anything was causing this. It found an upgrade for the driver of my video and network cards, but it didn't solve anything.
I don't know if this is possible or not, but may it be that when they decided to upgrade my RAM from the original 8 GB to 16 GB they didn't think it might cause my laptop to be unstable? Because in the description of the errors Windows gives me when it shuts down it says it's like power was missing (but this can't happen, since I have both a battery and a UPS).
I'll attach all the specifics of my laptop, the .zip file from the Log Collector and some images of the errors Windows gave me.
Thank you in advance,
19mirko91
EDIT: I forgot to say BSOD are very random. I almost always get them when I am not using my laptop. For instance, today I left my house for 30 minutes and my laptop was fine, but when I got home it had had a BSOD.