These are the errors I've been having and they all happen upon start up and won't even let me get to the desktop at all. It's a HP laptop 15-ac120nr. Only thing i can seem to access is the BIOS settings by spamming the F10 button.. It's my sisters laptop and she said she was watching a movie and the battery died and after that the errors have been popping up constantly. Seems like every fix I've found it requires you to be able to get to the desktop..

Errors:
Fault in nonpaged area
System Service Exception
attempted to write random memory
Machine check Exception
kmode exception not handled
System thread exception not handled
IRQL NOT LESS OR EQUAL

things I've tried:
Booting into safemode
System restoring
Booting a new ISO image from a usb
Hard drive check - passed
Memory test - passed
Removing ram and replacing

This post was edited by CvD on Sep 25 2016 09:35am

https://www.youtube.com/watch?v=qTlHwkVuv5Q

I suggest you don't keep the files and if you want anything on laptop to boot a linux disc and back it up before the restore.

This post was edited by King Atrhur on Sep 25 2016 09:37am

I've actually tried this already also. It pops up an error before it gets to the pages or during the restoring process.

Then you need an OEM or windows disc and need to try a full install.
If you bluescreen after that its hardware failure.

With that many random bugcheck codes, I'd say hardware fault is highly likely. And if RAM has been replaced already, it's likely the mainboard.

if your getting a bluescreen the chance is the HDD is going bad, it will still pass stress test, I have drives that will pass that are bad, if you have a spare drive I would recommend doing a fresh install on a different HDD/SSD and install that into the pc, if it takes then you know it was a hard-drive issue! GL

Not always. HDD-related BSODs tend to be very specific error codes (0x7B, 0x24), and these errors aren't in that list. Of course, there's an outside chance that it could be HDD related, but in my experience, those codes, when related to hardware, tend to be either RAM, CPU or board.

if it was RAM or a CPU or Board issue, you would get a beep seq, this usually will tell you that something hardware related is causing a mistart in your pc, when you BLUE-Screen it can be caused by overheating or HDD isses, and sometimes hardware issues, but usually you would get something on start-up stating a beep seq that would lead you more to Ram issues CPU or BIO issues

in my life-time of working on PC's when I get blue-screen issues it usually was fixed on a hdd/ssd switch-out, I will agree MOBO will cause bluescreen's but in your case I would try the cheap route and try drive switching, before ruling your CPU/MOBO/RAM are the issue, its the cheapest fix

This post was edited by VFW on Sep 26 2016 10:11am

Not all board issues cause beep codes. I've seen dozens of times where blown caps in the board will create BSODs without a POST beep code. Same thing with faulty RAM, although OP stated he replaced the RAM already.

Again I agree there, but if he replaced the Ram and its still a issue, why not do the HDD/SSD to rule it out, because if it were to fix his issues, then he might be able to save himself money on trying to repair unneeded issues with CPU/MOBO I have spare hdd/ssds sitting around I would just remove the one in currently and pop another in with a OS on it if it loads it then you know it was a drive issues, I'm thinking on terms of fixes you can do witout spending money (hoping he has spare drives of course)

if that werent to fix it, you then know its a bigger issue, which will tell you either to buy new or replace what you have!

This post was edited by VFW on Sep 26 2016 10:17am