Laptop refuses to boot/ Fresh O/S install stops at error: Machine Check Exception.

[Harleybiker]

During normal use of the laptop, it decided to shut down under its own volition. Attempts to restart it sent me on a constant loop with a message stating that HP Recovery was attempting to carry out a repair: it never went beyond this information screen regardless of how long it was left. I then carried out the following:

1. Extensive diagnostic tests of all hardware of which all devices passed every test (Battery, Wireless module, hard drive, memory, video memory, and system board).

2. Power reset (hard reset).

3. BIOS reset to default setting.

4. Carrying out a fresh install of the operating system from Windows 10 media. The computer recognised the media and began installation for a matter of seconds and then just started to 'loop' back to the start. I tried the installation with both the hard drive installed and uninstalled, the latter just to see if the installation would begin and recognise that no hard drive was present.

5. Legacy/Secure boot alternation.

6. Attempted booting from the HP Cloud Recovery utility and Windows 10 operating system media in order to try an OS repair. Importantly both these methods returned an error code of 'MACHINE STOP EXCEPTION'.

Bearing in mind that all hardware tests were passed and the system will not boot even for a fresh install/recovery media can anyone suggest what the root of the problem may be and how I can attempt to remedy it? Just as a note that all system configuration is as it was when purchased and no BIOS updates have been made; is updating the BIOS possibly the next step? Any suggestions or advice will be gratefully received, Neil.

[Paul_Tikkanen]

Hi, Neil:

I looked at the specs and it shows that your notebook has a single 8 GB memory module.

Although it passed the diagnostics test, my money is on that chip being bad.

Do you have another one of the same specs you can install and see if the problem goes away?

Even a 4 GB memory chip. 

I think you should test a different memory module in there and confirm or deny that the memory is causing the issue.

Below is the link to the service manual.

http://h10032.www1.hp.com/ctg/Manual/c05493089

I've had bad memory chips cause odd ball issues like you are experiencing on 2 different PC's.

Isolating and replacing the bad chip resolved the problem.

[Harleybiker]

Hi Paul, Thank you for your reply. My apologies for not replying earlier but I had to mail-order the RAM in order to try out your suggestion. Unfortunately, this didn't resolve the problem and returned a message 'install an operating system on your hard disk'  even though Windows 10 is in fact installed.

Therefore, with only the new RAM in place, I tried loading WinPE initially with the original SSD hard drive in place which returned a 'Machine Check Exception' error. I then removed the SSD and again tried to load WinPE with an external HDD attached which has just a copy of Windows 10 installed on it (I had tested this drive on another PC and I know it works perfectly). Again this returned a 'Machine Check Exception' error.

I considered installing a fresh copy of Windows 10 onto the SSD but wondered if I need to try and establish what is causing the 'Machine Check Exception' error before carrying on. Are you able to suggest any further tests that I may have missed?

Best wishes, Neil.

[Paul_Tikkanen]

You're very welcome, Neil.

Sorry that replacing the memory chip didn't fix the problem.

I can't think of any other tests you can run.

I would try the clean install of W10 on the SSD and see what happens.

[Harleybiker]

Hi Paul,

Just a courtesy update. I tried loading a fresh W10 install onto the HP via both a bootable USB and via a USB DVD (the latter was just grasping at straws). Both methods failed with the Machine Exception error. I even loaded a fresh install of W10 onto the SSD using another computer and then swoping it to the HP but alas that didn't work. I'm guessing that there might be a CPU error.

Regardless, thank you for your input your thoughts were very welcome. Take care, Neil.

[Paul_Tikkanen]

You're very welcome, Neil.

Sorry that you were not able to fix the problem.

The motherboard is probably no good, and I doubt it would be worth fixing.

You take care too.

Paul