LPC Controller driver

[George1157]

Hi Paul,

Thanks for an amazingly quick reply and the additional tips:-)

I suspect the problem is hardware/config related rather than the DVD because the DVD works fine on other HP PCs, but as it happens I do still have a Win7 bootable rescue disk which I created specifically for this nw8240 laptop prior to the migration to W10. I've just tried it and it boots up the nw8240 into W7 faultlessly so I'm guessing it's something in the v1803 that doesn't like the nw8240.

Incidentally, I don't know if this gives any additional clues but the first time I tried installing v1803 I mistakenly did so by running the setup.exe file as an administrator from the DVD. It apparently went through the whole install process for a couple of hours (giving options to keep or not keep personal files and apps) and then after the final auto-reboot it booted to the original v1709. It did the same when I tried it again and opted for not keeping anything, it still re-booted into v1709 with all my files and apps completely intact.

I'm happy to create and try v1709 from a DVD but that is the version which is currently installed, so won't that be rejected as already present? The v1709 is the last major update which installed successfully, v1803 onwards have been failing since May 2018. I guess a bootable v1709 will at least confirm that W10 can boot from DVD. Do I need to download it from a link from you or can I make a bootable DVD rescue disk from the nw8240?

Cheers.

George

[Paul_Tikkanen]

You're very welcome, George.

OK, so then it is not a hardware issue.

Here is the link to the 1709 32 bit ISO file.

https://software-download.microsoft.com/sg/Win10_1709_English_x32.iso?t=2f481b17-85cf-4c52-b80a-e2d0...

If you can boot from it, it will install. 

Then you can try upgrading to 1803 by running that DVD from the windows desktop, and skip the update check when it asks.

[George1157]

Hi Paul,

Downloading the v1709 file as we speak, so to speak, and will report when finished and tried out. I'm slightly perplexed though, isn't running the v1803 DVD from desktop after booting from v1709 DVD (and skipping the updates check) the same as running the v1803 DVD from desktop after booting into v1709 normally from hdd?

Cheers.

George

[Paul_Tikkanen]

Hi, George.

Yes, it would be the same thing.

I'm grasping at straws here in hope that a clean install will make a difference.

If that doesn't work, I guess you revert to your current system image and you will have to leave things be.

[George1157]

Hi Paul,

The clean v1709 installed successfully from the DVD and I left it in bare bones state except for UK language, keyboard and time zone. I even didn't connect to the internet in case updates started to download automatically. Device Manager confirmed that all drivers were correct.

The v1803 starts installing and goes through a few of the early steps eventually producing the now familiar message "Your PC ran into a problem and needs to restart. We'll restart for you" and "Stop Code IRQL NOT LESS OR EQUAL". After the auto-reboot it again fails to update to v1803 giving the codes for failing at the safe boot stage due to the drivers and reverts the system back to the clean v1709.

Having gone through all this pain I'd love to find out what is causing the updates to fall over, particularly while I've still got a clean basic Win10 machine and before I start reloading the Macrium created image. Windows tools report a healthy machine but do you know if there are any HP tools that can be used to for checking HP machines specifically?

Cheers.

George

[Paul_Tikkanen]

Hi, George:

Sorry that didn't work either.

Unfortunately, I don't have any other suggestions for you to try.

I guess different models fail to update at different points.

As I posted the other day, mine went to v1803 but that was it.

I didn't get any error reports, blue screens, etc.

When W10 restarted for the first time, nothing happened afterward.

So, I press and held the power button until the PC shut off, and when I restarted it, 1803 was still on there.

So, I think you are dead in the water at this point.

[George1157]

Hi Paul,

Not to worry, at least I've got a clean machine so know it wasn't an app that was causing the issue. Before I reload the Macrium image I'll see if I can get anywhere further with deciphering the Setuperr.log and Setupact.log files in case that does point to a specific driver but the time to give up is now really close. If I'm successful I'll update you so that you can any findings for others who may be in a similar position and seeking your help.

Thanks very much for your wisdom and of course your patience.

Cheers.

George

[Paul_Tikkanen]

Anytime, George.

At least we gave it a good try.

Hopefully, you may find an answer to the problem.

Cheers,

Paul