Update from Win-7 pro to Win-10 pro fails with 0x8007042B-0x2000D

[SomervilleTom]

Working on the above ...

 

[SomervilleTom]

I'm unable to remove the "marvell 91xx driver" because it's in use. I'm pretty sure that's the driver for the SATA controller needed for my 3 drives (E:, H:, I:)

 

[SomervilleTom]

I'm not sure how to check for updates for my chipset drivers. I've tried from the device manager, and it says all is up-to-date.

 

[Sysnative Windows Update]

Can the marvell device be disconnected temporarily? I've had issues with it before on a few systems as it is not natively supported in Win10.

 

[SomervilleTom]

Hmm. I'm not sure. The system runs from the C: drive, an internal SSD. The HDs are hot-swappable, so I can pull them out. I guess I can try that, but then how would I get the drives working again after the upgrade?

BTW, the upgrade just failed again in the same place.

 

[Sysnative Windows Update]

We would reconnect everything and search for the driver after the upgrade succeeds.

 

[SomervilleTom]

I'm removing everything attached to the SATA controller so that I can uninstall it. I might have to do this in "safe" mode, though. I'm not sure I can get the system to stop using it.

 

[Sysnative Windows Update]

Is it integrated or external (plugged into the motherboard as a separate device)?

 

[SomervilleTom]

@Integrated/external: I don't know. I think external, but I'm not sure.

 

[SomervilleTom]

When I try to uninstall it from "Programs and features", nothing happens (after a confirmation dialog).

 

[SomervilleTom]

If you like, I can power down the box and open it up. It might be integrated, though ... I think the power cables go to connectors on the motherboard. Hmm.

Might be time to retire the system, frankly.

 

[Sysnative Windows Update]

Please check. If not integrated, plug it out.

If it is integrated, this will kill its driver forcefully.


Step#1 - FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download the attached fixlist.txt and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.


I would recommend that you have a backup to restore to, just in case it decides to BSOD.

 

[SomervilleTom]

It is integrated. I opened up the case -- the motherboard is an "EVGA X58 SLI3". I haven't found any firmware or driver updates from either Marvell or EVGA.

I think I'll let this go until tomorrow, time for dinner and wine. :)

 

[Sysnative Windows Update]

Okay. Keep me posted and enjoy the dinner and the wine.

 

[SomervilleTom]

Based on the BIOS (see attachment), I think disabling the Marvell controller will block access to the C drive (the SSD).

I looked at the fixtext, are those new drivers? If so, then I'm game. If not, then it might be time for me to go shopping. Since my lovely wife is also the Secretary of Finance, I think I know where our dinner conversation will begin. :)

 

[Sysnative Windows Update]

No, the fixlist will kill the current driver. But yes, if the current boot drive is in the controller, this will likely result in a BSOD.