Win7 Ultimate SP1 to Win10 upgrade "Error: 0x8007001F-0x20006", SURT shows missing KB2952664 MUMs

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.
 

Attachments

A quick one...

Code: 
Fix result of Farbar Recovery Scan Tool (x64) Version: 27-01-2020
Ran by Admin (27-01-2020 18:59:47) Run:3
Running from C:\_DATA\Downloads\FRST
Loaded Profiles: Admin (Available Profiles: Admin & Karen & Jon & Max)
Boot Mode: Normal
==============================================

fixlist content:
*****************
C:\Windows\System32\migration
*****************

C:\Windows\System32\migration => moved successfully

==== End of Fixlog 18:59:47 ====
[\code]
 
I just walked past it to check on progress (the Win10 applying updates stage takes soooo long) and just spotted the tail end of a BSOD before it rebooted (The win10 smiley BSOD with a QR code on screen? I only saw it from across the room for half a second, so no idea what info was displayed.)

It's recovering now, I'll post any codes shortly once I'm logged back in.
 
Confirmed it's the same reported error.

0xC1900101 - 0x30018
The installation failed in the FIRST_BOOT phase with an error during SYSPREP_SPECIALIZE operation.

I hadn't been sitting watching the entire upgrade but can watch one through (tomorrow evening) if needed. Last time I looked at the screen beforehand was showing the updates had reached 27%.

Does it store a dump from the BSOD during installation? I know how to configure windows "normally" to capture a full crash dump, and analyze it with windbg (although I'm more than 5 years out of practice) but wouldn't know how or whether the upgrade could be configured the same?



The below is speculation, apologies if it's just a distraction.

There are two bits of hardware that would be my hunch for crappy drivers causing a problem. One is the USB3 card I have installed. I could remove that for the time being, I only use it for running backups, and there's nothing currently plugged in to it. I'd be happy to do that and remove the drivers either to eliminate it or if there's any indication in the logs that this might be a problem.

The second would be the onboard RAID hardware in the motherboard. I have a pair of mirrored disks connected to this storing media files, so it's less easy to disable. It's a Marvell 61xx RAID controller.

C:\Windows\system32\DRIVERS\mv61xx.sys v1.2.0.69 on 11/05/2009
C:\Windows\system32\mvcoinst.dll v1.0.0.3 from 2008

It's a long time since I set this up but I think, from looking in Disk Management, that the mirroring is Windows RAID 1 mirroring, not hardware mirroring. The two disks are currently resynching, I assume because of the bsod.
 
Yes it was custom built, specs are on my 1st post. I was trying to ID the motherboard without doing having to, but have just opened the case to double check, it's an ASUS P5Q Deluxe MB.

Interestingly, the Asus website does not have Marvell drivers for RAID for this MB, and says the MB has Intel SATA on it. I'm wondering if the Marvell driver is present from a previous incarnation, and if it would be safe to remove the Marvell driver without risking leaving windows 7 unbootable? Potentially with a system restore point in place.

I checked in the bios, there are no raid controls, either to configure disks or partitions, nor to disable or enable raid.

I need to get to sleep now, will be availabel from 6pm UK time tomorrow.
 
Only just got to the machine tonight, I was looking for the rollback log, but spotted there IS a .dmp file. Also spotted that I already had the Win7 machine fully installed with WinDbg and the microsoft symbol files path set up (phew!)

Anyway the dump analysis confirms our suspicions. I'll look in to a system restore point and try without the driver.

Code: 
Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\$WINDOWS.~BT\Sources\Rollback\setupmem.dmp]
Kernel Bitmap Dump File: Only kernel address space is available

Symbol search path is: srv*C:\_DATA\localsymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 8 Kernel Version 18362 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff801`76400000 PsLoadedModuleList = 0xfffff801`76848150
Debug session time: Mon Jan 27 21:28:20.019 2020 (UTC + 0:00)
System Uptime: 0 days 0:05:32.077
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..........................
Loading User Symbols

Loading unloaded module list
...........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 133, {1, 1e00, fffff80176973358, 0}

*** ERROR: Module load completed but symbols could not be loaded for mv61xx.sys
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: TickPeriods                                   ***
***                                                                   ***
*************************************************************************
Probably caused by : mv61xx.sys ( mv61xx+1ba3d )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
    DISPATCH_LEVEL or above. The offending component can usually be
    identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: fffff80176973358
Arg4: 0000000000000000

Debugging Details:
------------------

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: TickPeriods                                   ***
***                                                                   ***
*************************************************************************

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x133

PROCESS_NAME:  System

CURRENT_IRQL:  d

LAST_CONTROL_TRANSFER:  from fffff801765eeac1 to fffff801765c14e0

STACK_TEXT:  
fffff801`7c275658 fffff801`765eeac1 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff801`76973358 : nt!KeBugCheckEx
fffff801`7c275660 fffff801`7641f61c : 000000d8`12ae24e2 fffff801`735c7180 00000000`00005304 00000000`00005304 : nt!KeAccumulateTicks+0x1cc061
fffff801`7c2756c0 fffff801`76eb74b2 : 00000000`00000000 fffff801`7c275b50 fffff801`7c275bd0 00000000`00000005 : nt!KeClockInterruptNotify+0x98c
fffff801`7c275a80 fffff801`76402a25 : 00000000`c605f396 fffff801`76f250e0 fffff801`76f25190 fffff801`76f250e0 : hal!HalpTimerClockInterrupt+0xf2
fffff801`7c275ab0 fffff801`765c2f7a : fffff801`7c275bd0 fffff801`76f250e0 00000000`00000001 fffff801`76eb92cb : nt!KiCallInterruptServiceRoutine+0xa5
fffff801`7c275b00 fffff801`765c34e7 : 000000d8`00000000 00000000`00000000 00000000`00000000 ffff8a8a`320974a8 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff801`7c275b50 fffff801`76efdefa : fffff801`76eb7727 00000000`c0700039 00000000`00000020 ffffb800`7c5fed00 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff801`7c275ce8 fffff801`76eb7727 : 00000000`c0700039 00000000`00000020 ffffb800`7c5fed00 00000000`00001388 : hal!HalpTscQueryCounter+0x1a
fffff801`7c275cf0 fffff801`7b08b8db : ffffb800`7c5fed00 ffff8a8a`32097678 00000000`00000004 00000000`00000001 : hal!KeStallExecutionProcessor+0x127
fffff801`7c275d70 fffff801`741dba3d : ffff8a8a`32097678 00000000`00000004 00000000`00000001 ffff8a8a`2eef2000 : SCSIPORT!ScsiPortStallExecution+0xb
fffff801`7c275da0 fffff801`741dc2e0 : fffff801`7c275f00 00000000`00000000 fffff801`00000003 ffff8a8a`320974a8 : mv61xx+0x1ba3d
fffff801`7c275e20 fffff801`741c1f4b : ffff8a8a`320974a8 ffffb800`7c1d4b40 fffff801`00100009 00000000`00100000 : mv61xx+0x1c2e0
fffff801`7c275ec0 fffff801`7b08566b : ffff8a8a`365311b0 ffff8a8a`33b0c4e0 ffffb800`7bd72970 00000000`00000002 : mv61xx+0x1f4b
fffff801`7c275ef0 fffff801`76402a25 : ffffb800`7bd728c0 ffffb800`7bd72970 fffff801`7c275fa8 00000000`00000008 : SCSIPORT!ScsiPortInterrupt+0x3b
fffff801`7c275f20 fffff801`765c2b4c : fffff801`7c2678d0 ffffb800`7c1d4b40 ffffb800`7bd728c0 ffffb800`7c1d4b40 : nt!KiCallInterruptServiceRoutine+0xa5
fffff801`7c275f70 fffff801`765c27a7 : ffff8a8a`308b58a0 00000000`000051b2 ffff8a8a`33771050 ffff8a8a`334a9620 : nt!KiScanInterruptObjectList+0x14c
fffff801`7c267850 fffff804`7889117b : 00000000`00000050 fffff804`7889163e 00000000`01000010 00000000`00000282 : nt!KiChainedDispatch+0x37
fffff801`7c2679e0 fffff801`7b881115 : ffff8a8a`337711a0 ffff8a8a`33771050 00000000`00000018 00000000`000000f8 : usbuhci!UhciPollController+0x4b
fffff801`7c267a40 fffff801`7646ba89 : 00000000`00000018 ffff8a8a`33771ac8 00000000`00000020 ffff8a8a`00000002 : USBPORT!USBPORT_DM_TimerDpc+0x105
fffff801`7c267a80 fffff801`7646a7e9 : 00000000`00000006 00000000`00989680 00000000`00001fe0 00000000`000000f8 : nt!KiProcessExpiredTimerList+0x169
fffff801`7c267b70 fffff801`765c5024 : 00000000`00000000 fffff801`735c7180 fffff801`76991400 ffff8a8a`3570a080 : nt!KiRetireDpcList+0x4e9
fffff801`7c267da0 00000000`00000000 : fffff801`7c268000 fffff801`7c262000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x84


STACK_COMMAND:  kb

FOLLOWUP_IP: 
mv61xx+1ba3d
fffff801`741dba3d 4c2bf6          sub     r14,rsi

SYMBOL_STACK_INDEX:  a

SYMBOL_NAME:  mv61xx+1ba3d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: mv61xx

IMAGE_NAME:  mv61xx.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d525e51

FAILURE_BUCKET_ID:  0x133_ISR_mv61xx+1ba3d

BUCKET_ID:  0x133_ISR_mv61xx+1ba3d

Followup: MachineOwner
---------
 
Marvel controller driver has crashed due to it being incompatible with Win10:

ERROR: Module load completed but symbols could not be loaded for mv61xx.sys
 
Yes I understand that. I really appreciate the help you have provided so far.

Given that a number of people over the years claim to be successfully running Windows 10 on the P5Q Deluxe motherboard, I was assuming that simply removing the windows 7 Marvell driver would let the upgrade get past that problem.

However, despite creating a system restore point just now prior to removing the Marvel driver from Windows, this has resulted in an unbootable Windows 7, even at last known good configuration. So I'm currently writing the correct Windows7 ISO to a bootable USB in order to properly restore the system. Sigh.

Please bear with me and help others while I get myself back to where I started.

If it comes to it I will have to pay for a Win10 license rather than upgrading for free, but I will still put in a donation to your site for the help you have provided, and your time you have given up.

I'll come back to you once I've fixed what i just broke!
 
Just a brief update - I recovered it with the original system restore point.

Then tried it another way, this time it got 60% into the Win10 upgrade download updates before a BSOD again.

On restore, Win7 still booted okay, but then within 2 mins, windows 7 update replaced the IDE drivers with newer ones form MS which don't work, and the system died again.

Win10 had deleted the restore points :(

So I had a fun few hours manually downgrading the drivers using boot disks.

...it's all good practice for me!

I've put in a donation for all your help to me and others.

I think for now, as I have other projects demanding my time, I'll have to put this on hold, as long as I can keep access to antivirus updates on Win7, It can live for a while until I can afford new hardware.
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top