Windows 7 upgrade to 10 error 0x8007001F - 0x3000D

1) Open control panel > uninstall > post images into the thread

2) Uninstall spyware software

3) Open device manager > click view > click show hidden devices > look for any device displaying a yellow triangle with black exclamation mark or unknown device > post images into the thread
Device Manager - Finding Unknown Devices - Windows 7 Help Forums


4) also look for:

Code:

AODDriver4.01	ROOT\LEGACY_AODDRIVER4.01\0000	This device is not present, is not working properly, or does not have all its drivers installed.

5) The computer has been having BSOD with the last recorded one one yesterday 1/25/2020

6) Create a new restore point:
Restore Point - Add "Create Restore Point" to Context Menu in Windows - Windows 7 Help Forums

7) Read these links on windows driver verifier: (learn the reset and bootmode commands to turn off the tool)
Driver Verifier - Enable and Disable - Windows 7 Help Forums
Enable and Disable Driver Verifier in Windows 10
https://answers.microsoft.com/en-us/...3-c48669e4c983

8) For any BSOD:

a) run the DM log collector to collect new log files

b) search for: C:\Windows\memory.dmp
> if the file size is < 1.5 GB then zip > post a separate share link into the thread using one drive, drop box, or google drive

9) Check to see if the AMD chipset drivers are up to date > manually update as necessary

zbook said:

1) Open control panel > uninstall > post images into the thread

2) Uninstall spyware software

3) Open device manager > click view > click show hidden devices > look for any device displaying a yellow triangle with black exclamation mark or unknown device > post images into the thread
Device Manager - Finding Unknown Devices - Windows 7 Help Forums


4) also look for:

Code:

AODDriver4.01	ROOT\LEGACY_AODDRIVER4.01\0000	This device is not present, is not working properly, or does not have all its drivers installed.

5) The computer has been having BSOD with the last recorded one one yesterday 1/25/2020

6) Create a new restore point:
Restore Point - Add "Create Restore Point" to Context Menu in Windows - Windows 7 Help Forums

7) Read these links on windows driver verifier: (learn the reset and bootmode commands to turn off the tool)
Driver Verifier - Enable and Disable - Windows 7 Help Forums
Enable and Disable Driver Verifier in Windows 10
https://answers.microsoft.com/en-us/...3-c48669e4c983

8) For any BSOD:

a) run the DM log collector to collect new log files

b) search for: C:\Windows\memory.dmp
> if the file size is < 1.5 GB then zip > post a separate share link into the thread using one drive, drop box, or google drive

9) Check to see if the AMD chipset drivers are up to date > manually update as necessary

Thanks again for working on this. Here we go:

1)





2) Uninstalled SpywareBlaster 4.6 and Spybot - Search & Destroy (after taking the screencaps above)

3)


4) see 3) above

5) I have not seen an actual blue screen at any point during my many upgrade attempts--this must be happening in a way that is not displayed. Also see 8) below.

6&7) done

8)
a) here
b) no such file exists. The only .dmp file on the C: drive is this one.

9) I'm not sure I know how to do this correctly. Nothing I checked in device manager looked suspect, but I'm not sure I checked the right stuff, nor that I would recognize a problem if one existed.

Open administrative command prompt and type: shutdown /r /o /f /t 00
This should boot into windows recovery environment (RE)

Shift + restart is another method.
See this link: Safe Mode - Windows 7 Help Forums

When you are comfortable with Windows RE, how to turn off windows driver verifier using reset and bootmode commands you can start using the tool.

See these links:

How to Find Drivers for Unknown Devices in the Device Manager
How to easily find drivers for Unknown Devices in Windows | PCWorld


Download and install the chipset drivers > follow with windows updates
M4A79XTD EVO Driver & Tools | Motherboards | ASUS USA

Code:

Event[55942]:
  Log Name: System
  Source: volmgr
  Date: 2020-01-26T17:29:39.203
  Event ID: 46
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Threinen-PC
  Description: 
Crash dump initialization failed!

zbook said:

Open administrative command prompt and type: shutdown /r /o /f /t 00
This should boot into windows recovery environment (RE)

Shift + restart is another method.
See this link: Safe Mode - Windows 7 Help Forums

When you are comfortable with Windows RE, how to turn off windows driver verifier using reset and bootmode commands you can start using the tool.

See these links:

How to Find Drivers for Unknown Devices in the Device Manager
How to easily find drivers for Unknown Devices in Windows | PCWorld


Download and install the chipset drivers > follow with windows updates
M4A79XTD EVO Driver & Tools | Motherboards | ASUS USA

Code:

Event[55942]:
  Log Name: System
  Source: volmgr
  Date: 2020-01-26T17:29:39.203
  Event ID: 46
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Threinen-PC
  Description: 
Crash dump initialization failed!

I think I'd be comfortable booting in safe mode, and driver verifier seems pretty straightforward. Just to be sure before I do--is the idea to turn on driver verifier while in safe mode, then boot to normal mode and wait for BSOD/error logs to be generated regarding that driver?

I downloaded and installed the chipset drivers. AODDriver4.01 is still there with a yellow !. I can't use the approach in the articles you linked because 'Hardware IDs' is not an option on the list (see below).

Snooping around a bit online, I wonder if this driver is associated with the Radeon HD5760 graphics card that was initially installed in my machine (before I upgraded to my current NVIDIA card). Does this sound right? Do I need this driver?

Windows driver verifier is run when in normal boot.
It will stress drivers.
Misbehaving drivers should cause BSOD.
To turn off the tool and be able to return to the desktop use safe mode.
In safe mode run commands that can turn off the tool.
Run the DM log collector.
Look for C:\windows\memory.dmp
Upload results.
Restart Windows driver verifier to find the next misbehaving driver.


Run the Hardware and Devices troubleshooter.

See if any of these are useful:
Download Unknown Devices - MajorGeeks
Unknown Device Identifier - Freeware Download (make sure AV is installed and working)
Download DevManView - MajorGeeks


This was the closest finding but did not match:

Code:

AODDriver.sys	AMD Overdrive; also in EasyTune6 for Gigabyte motherboard
Known BSOD issues in Win7

Part of AMD Fuel

Location: C:\Program Files\ATI Technologies\ATI.ACE\Fuel\amd64\AODDriver2.sys	http://game.amd.com/us-en/drivers_overdrive.aspx

luke t said:

It wasn't incompatible for cloning--it was incompatible with my (ancient) motherboard, so I was unable even to install it. In particular, my board does not have an M.2 PCIe slot. I've got a SATA drive coming today, which should be compatible.

If it has SATA it isn't as ancient as my IDE only boards.
I have some combo boards that also have both and also only SATA and sometimes when the BIOS doesn't like your new larger drive a BIOS update flash is required. I had to do this when hard drives that came out were larger than when the board was made and this can also apply to CPU upgrades as well. If all else fails check your BIOS version and check for updates.
Oh and while we are at it consider swapping out your SATA cable from motherboard to hard drive as well. If you don't have a good spare swap from CD/DVD drives or check to make sure both ends are firmly seated in the board or hard drive.

zbook said:

Windows driver verifier is run when in normal boot.
It will stress drivers.
Misbehaving drivers should cause BSOD.
To turn off the tool and be able to return to the desktop use safe mode.
In safe mode run commands that can turn off the tool.
Run the DM log collector.
Look for C:\windows\memory.dmp
Upload results.
Restart Windows driver verifier to find the next misbehaving driver.


Run the Hardware and Devices troubleshooter.

See if any of these are useful:
Download Unknown Devices - MajorGeeks
Unknown Device Identifier - Freeware Download (make sure AV is installed and working)
Download DevManView - MajorGeeks


This was the closest finding but did not match:

Code:

AODDriver.sys	AMD Overdrive; also in EasyTune6 for Gigabyte motherboard
Known BSOD issues in Win7

Part of AMD Fuel

Location: C:\Program Files\ATI Technologies\ATI.ACE\Fuel\amd64\AODDriver2.sys	http://game.amd.com/us-en/drivers_overdrive.aspx

I finally had a chance to do this last night. No blue screens yet (roughly 12 hours in).

I am not entirely sure what useful output would have looked like for any of those three programs--their documentation is thin/nonexistent--but I didn't see anything that looked like a solution to that driver issue.

Since I do not have AMD Overdrive installed (at least not that I'm aware of), would it be useful to try uninstalling this driver? When I do a search for "do i need aoddriver", I see this suggestion made in various forums. Or am I asking for more trouble by doing this?

The driver was not in our database.

Make a new restore point.

If you can identify the driver it can be modified by adding .old for example abcdefg.sys > abcdedfg.sys.old

zbook said:

The driver was not in our database.

Make a new restore point.

If you can identify the driver it can be modified by adding .old for example abcdefg.sys > abcdedfg.sys.old

Wasn't able to identify the driver, so i just made a restore and uninstalled the driver. No evident impact from doing so.

Is this enough to make it worth retrying the Windows 10 upgrade?

For misbehaving driver testing plan to run the tool:
a) test all non-Microsoft drivers
b) use the customized test settings in the Microsoft link
c) run the tool for continuously for 48 hours without any unexpected shutdowns or restarts