05-24-2020 02:35 PM
I have HP EliteBook 8470p laptop at home. Recently i installed larger SSD (Samsung QVO 860, 1TB) and also reinstalled Windows. It was fresh install from USB, build 1909, dated 9-Jan-2020. I enabled UEFI boot before reinstall to make sure everything is correct. Install went fine, i proceeded to install drivers and update Windows with latest bugfixes.
After several restarts during driver install, Windows suddenly failed to boot. Boot drive was not found.
If i turn laptop off and then back again - it boots. After this every restart leads to Windows unable to boot.
But if i shut down Windows and then turn laptop back on - everything is fine. I disabled fast boot in Windows - did not help.
I feel like i am missing some small crucial detail. Since it aways happens after restart, there must be something i did wrong.
Any ideas how to remedy this?
Solved! Go to Solution.
05-24-2020 02:52 PM - edited 05-24-2020 02:56 PM
From what you have written, it doesn't sound like anything you did or failed to do is causing the issue.
The only suggestion I can offer would be to install the W10 Intel RST driver for the chipset your notebook comes with.
05-24-2020 04:04 PM
Thanks for the suggestion. I already have this driver version installed. I also installed intel chipset drivers, From HP drivers i have drivers for JMicron SD card reader, Alcor smartcard reader, also HP wireless button drivers and HP hotkey driver. Rest of drivers are Windows 10 native ones. Except for accelerometer (part of 3D drive guard).
After install i noticed that version 5.2 of this driver windows 10 installs by default is ... disabled by windows itself with note that this driver can cause instability in Windows. I went searching on internet and found accelerometer driver version 7.3 on Microsoft's own update catalog. I was able to install but hpserv service which works with it was not updated obviously and fails to start.
I don't know where to get a proper version of 3D drive guard. Not sure does it affects boot but i noticed that it does hooks to boot device driver. HPs own page for my laptop model offers the same version 5.2 which has issues with Windows 10.
What else to mention... BIOS version for laptop is latest version i could find on support page for EliteBook 8470p.
05-24-2020 06:48 PM
You're very welcome.
If the version 7.3 of the 3D driveguard version installed and you don't have any ! mark next to the device, then that is as good as you can get..
You don't need it anyway since you have a SSD.
If there is a ! mark next to it, you can try the workaround that I posted for other forum members that have the same accelerometer hardware version as your model has...
You would have to uninstall the driver and bring it back to the unknown device status before trying this...
05-26-2020 02:07 AM - edited 05-26-2020 04:32 AM
It appears i was fighting windmills 😞
Culprit is 1TB Samsung QVO 860 itself:
Appears it does not play nice with laptop's SATA controller, i will try to use this remedy and let you know.
Cloning had the same issue and i blamed myself, while it appears drive was to blame. I could've just cloned the drive and used it.
UPDATE: i changed Windows SATA controller driver back to "Standard AHCI 1.0 Controller" which came with Windows and after one shutdown, laptop is able to successfully boot after restart.
From what i am reading on internet now, this drive does not play nicely with all controllers. My case is not the only one.
Regarding HP Accelerometer driver - i took driver from here:
to be precise. Version is 18.104.22.168
It has to be pushed to Device Manager via "Update Driver", "Browse my computer for driver software", "let me pick from a list of available drivers on my computer", "have disk", then pointing to the directory where .cab file is unpacked, to the .inf file specifically. Answering "Yes" to Windows worry that this driver is not meant for my laptop.
This removes "!" from the driver in Device Manager. HPservice which governs this sensor, can be disabled since obviously it is not updated along with driver and remains version 5.2
Unfortunately you can not disable this sensor in BIOS. That would save a lot of trouble.