[SOLVED] BSOD on W7 upgrade to W10 & in driver verifier, no dumps. FIX: FEW drivers (and devices) removed; TPKD was the last one which blocked the upgrade.

xilolee · Dec 18, 2020

Are you using windscribe or did you uninstall it? And logmein?
Are you using any hardware by AMD (graphics cards, usually) or creative (sound cards, usually)?

And I still didn't understand if you have a system image (it's different from a system restore point)...

MingoMongo · Dec 18, 2020

I've still got Windscribe and Logmein Hamachi, I had a Creative SoundBlaster but I removed it and (tried) to remove the drivers.
I have a system image, that's what was failing to restore. I make restore points but they seem to disappear after a few restarts, or maybe after an upgrade attempt.

xilolee · Dec 18, 2020

What program are you using for the system image?

From a command prompt (admin):

Code:

sc stop amdxata
sc config amdxata start= disabled
sc delete amdxata
sc delete amdsata
sc delete amdsbs
sc delete focusriteusb
sc delete focusriteusbswroot
sc delete focusriteusb_audio
sc delete ossrv
sc delete _hid_0738_1705
sc delete _usb_0738_1705
sc delete ct20xut
sc delete ct20xut.sys
sc delete ctac32k
sc delete ctaud2k
sc delete ctexfifx
sc delete ctexfifx.sys
sc delete cthwiut
sc delete cthwiut.sys
sc delete ctprxy2k
sc delete ctsfm2k
sc delete emupia
sc delete ha20x22k
sc delete ha20x2k

Report their results.

Then install:
Download NVM Update Utility for Intel® 82579V Gigabit Ethernet PHY Network Connection
https://dlcdnets.asus.com/pub/ASUS/lan/Inte_LAN_V17300_XPWin7_8.zip

Reboot and post the new logs (driverview, devmanview, regseeker).

zbook · Dec 18, 2020

Imaging with free Macrium - Windows 7 Help Forums

MingoMongo · Dec 18, 2020

I was maybe foolishly using the Windows system image save, now using Macrium.

I was trying to do the virtual Windows 10 Trial zbook linked, but found an error when I was using the "bcdboot D:Windows" command (yes D: is the right drive) which gave me the error:

BFSVC Error: Could not open the BCD template store. Status = [c000000f]

I also moved the VHD to a different drive but the same error appeared.
So I'm now suspecting boot issues which I will attempt to repair as explained here. But knowing how dangerous boot stuff can be I'm definitely making a backup image and maybe a repair disc first. I don't know if this will help/is the reason I'm in this mess, but I think it's worth looking at since nothing's working right now.

Xilolee everything succeeded in being deleted, will update ethernet and post logs tomorrow or day after.

zbook · Dec 18, 2020

Malwarebytes and or Microsoft Security Essentials can be installed before downloads: Download Microsoft Security Essentials from Official Microsoft Download Center

1) Open disk management > by default some columns are compressed > widen each Status and Volume > make sure the contents within the parenthesis are in full view and that none of the characters are cutoff > view disk 0 > widen this row as needed so that all of the characters are in full view > post an image into the thread
Disk Management - How to Post a Screenshot of

2) Download and install Minitool Partition Wizard > click launch > post an image of the results into this thread
MiniTool Partition Wizard Free Edition
MiniTool Portable Partition Magic Brings Easier Disk Management

3) Run: DiskParInfo.bat - Click here to go to the BSOD batch repository to download and run this batch file. (it was not yet tested on Windows 7)

MingoMongo · Dec 19, 2020

Attached. BIOS mode is BIOS, not UEFI if that makes a difference.

This computer has the above fixed storage device(s) in total.
=======================================================================

Microsoft DiskPart version 6.1.7601
Copyright (C) 1999-2008 Microsoft Corporation.
On computer: JAY-PC

Disk ### Status Size Free Dyn Gpt
-------- ------------- ------- ------- --- ---
Disk 0 Online 465 GB 0 B
Disk 1 Online 1863 GB 1024 KB * *
Disk 2 Online 931 GB 0 B

Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
Volume 0 H Personal NTFS Simple 638 GB Healthy
Volume 1 E Big Files NTFS Simple 1224 GB Healthy
Volume 2 C NTFS Partition 465 GB Healthy System
Volume 3 D Old Drive NTFS Partition 931 GB Healthy

===============================================================================

Extended configuration for the Recovery Environment

Windows RE enabled: 1
Windows RE staged: 0
Setup enabled: 0
Custom Recovery Tool: 0
WinRE.WIM directory:
Recovery Environment:
BCD Id: 4e384007-793f-11e1-85b2-db8ffeee976c
Setup Files:
Recovery Operation: 4
Operation Parameter:
Boot Key Scan Code 0x0
REAGENTC.EXE: Operation successful
===============================================================================

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=C:
description Windows Boot Manager
locale en-us
inherit {globalsettings}
default {current}
resumeobject {e66661de-0f08-11eb-9078-00268337b4dc}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 30

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7
locale en-us
inherit {bootloadersettings}
osdevice partition=C:
systemroot \Windows
resumeobject {e66661de-0f08-11eb-9078-00268337b4dc}
nx OptIn
bootstatuspolicy IgnoreAllFailures
detecthal Yes

Resume from Hibernate
---------------------
identifier {e66661de-0f08-11eb-9078-00268337b4dc}
device partition=C:
path \Windows\system32\winresume.exe
description Windows Resume Application
locale en-us
inherit {resumeloadersettings}
filedevice partition=C:
filepath \hiberfil.sys
debugoptionenabled No

Windows Memory Tester
---------------------
identifier {memdiag}
device partition=C:
path \boot\memtest.exe
description Windows Memory Diagnostic
locale en-us
inherit {globalsettings}
badmemoryaccess Yes

EMS Settings
------------
identifier {emssettings}
bootems Yes

Debugger Settings
-----------------
identifier {dbgsettings}
debugtype Serial
debugport 1
baudrate 115200

RAM Defects
-----------
identifier {badmemory}

Global Settings
---------------
identifier {globalsettings}
inherit {dbgsettings}
{emssettings}
{badmemory}

Boot Loader Settings
--------------------
identifier {bootloadersettings}
inherit {globalsettings}
{hypervisorsettings}

Hypervisor Settings
-------------------
identifier {hypervisorsettings}
hypervisordebugtype Serial
hypervisordebugport 1
hypervisorbaudrate 115200

Resume Loader Settings
----------------------
identifier {resumeloadersettings}
inherit {globalsettings}

xilolee · Dec 19, 2020

The amdxata driver was enabled at boot.

You don't have any amd chip, chipset or graphics card, to justify any amd drivers enabled on your system.
They are available on windows maybe because it installs them by default, like it does for intel drivers on an amd build like mine: I removed them all, and even intel services, and I haven't got any issues, even if they were marked as boot.
I had intelpep.sys (Intel Power Engine Plugin) and intelta.sys (Intel(R) Telemetry Service): both services were enabled and running!

I don't know if now the upgrade is going to work, but that one was a possible culprit.

zbook · Dec 19, 2020

When performing Windows upgrades make sure that only one drive is attached (disk 0).

Open administrative command prompt and type or copy and paste: (all at one time)

Code:

bcdedit /enum
reagentc /info
diskpart
lis dis
lis vol
sel dis 0
det dis
lis par
sel par 1
det par
sel par 2
det par
sel par 3
det par
sel dis 1
det dis
lis par
sel par 1
det par
sel par 2
det par
sel par 3
det par
sel par 4
det par
sel par 5
det par
sel par 6
det par
sel dis 2
det dis
lis par
sel par 1
det par
sel par 2
det par
sel par 3
det par

When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

MingoMongo · Dec 19, 2020

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Jay>bcdedit /enum

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=C:
description Windows Boot Manager
locale en-us
inherit {globalsettings}
default {current}
resumeobject {e66661de-0f08-11eb-9078-00268337b4dc}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 30

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7
locale en-us
inherit {bootloadersettings}
osdevice partition=C:
systemroot \Windows
resumeobject {e66661de-0f08-11eb-9078-00268337b4dc}
nx OptIn
bootstatuspolicy IgnoreAllFailures
detecthal Yes

C:\Users\Jay>reagentc /info
Extended configuration for the Recovery Environment

Windows RE enabled: 1
Windows RE staged: 0
Setup enabled: 0
Custom Recovery Tool: 0
WinRE.WIM directory:
Recovery Environment: \\?\GLOBALROOT\device\harddisk0\partition1\Recovery\4e
384007-793f-11e1-85b2-db8ffeee976c
BCD Id: 4e384007-793f-11e1-85b2-db8ffeee976c
Setup Files:
Recovery Operation: 4
Operation Parameter:
Boot Key Scan Code 0x0
REAGENTC.EXE: Operation successful

C:\Users\Jay>diskpart

Microsoft DiskPart version 6.1.7601
Copyright (C) 1999-2008 Microsoft Corporation.
On computer: JAY-PC

DISKPART> lis dis

Disk ### Status Size Free Dyn Gpt
-------- ------------- ------- ------- --- ---
Disk 0 Online 465 GB 0 B

DISKPART> lis vol

Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
Volume 0 C NTFS Partition 465 GB Healthy System

DISKPART> sel dis 0

Disk 0 is now the selected disk.

DISKPART> det dis

Samsung SSD 860 EVO 500G
Disk ID: B16DD13D
Type : ATA
Status : Online
Path : 0
Target : 0
LUN ID : 0
Location Path : PCIROOT(0)#ATA(C00T00L00)
Current Read-only State : No
Read-only : No
Boot Disk : Yes
Pagefile Disk : Yes
Hibernation File Disk : No
Crashdump Disk : Yes
Clustered Disk : No

Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
Volume 0 C NTFS Partition 465 GB Healthy System

DISKPART> lis par

Partition ### Type Size Offset
------------- ---------------- ------- -------
Partition 1 Primary 465 GB 1024 KB

DISKPART> sel par 1

Partition 1 is now the selected partition.

DISKPART> det par

Partition 1
Type : 07
Hidden: No
Active: Yes
Offset in Bytes: 1048576

Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
* Volume 0 C NTFS Partition 465 GB Healthy System

DISKPART> sel par 2

The specified partition is not valid.
Please select a valid partition.

There is no partition selected.

DISKPART> det par

There is no partition selected.
Please select a partition and try again.

DISKPART> sel par 3

The specified partition is not valid.
Please select a valid partition.

There is no partition selected.

DISKPART> det par

There is no partition selected.
Please select a partition and try again.

DISKPART> sel dis 1

The disk you specified is not valid.

There is no disk selected.

DISKPART> det dis

There is no disk selected to list details for.
Please select a disk and try again.

Displays the properties of the selected disk and the list of volumes on
the disk.

Syntax: DETAIL DISK

A disk must be selected for this operation to succeed.

Example:

DETAIL DISK

DISKPART> lis par

There is no disk selected to list partitions.
Select a disk and try again.

DISKPART> sel par 1

There is no disk selected to set the partition.
Select a disk and try again.

DISKPART> det par

There is no disk selected.
Please select a disk and try again.

DISKPART> sel par 2

There is no disk selected to set the partition.
Select a disk and try again.

DISKPART> det par

There is no disk selected.
Please select a disk and try again.

DISKPART> sel par 3

There is no disk selected to set the partition.
Select a disk and try again.

DISKPART> det par

There is no disk selected.
Please select a disk and try again.

DISKPART> sel par 4

There is no disk selected to set the partition.
Select a disk and try again.

DISKPART> det par

There is no disk selected.
Please select a disk and try again.

DISKPART> sel par 5

There is no disk selected to set the partition.
Select a disk and try again.

DISKPART> det par

There is no disk selected.
Please select a disk and try again.

DISKPART> sel par 6

There is no disk selected to set the partition.
Select a disk and try again.

DISKPART> det par

There is no disk selected.
Please select a disk and try again.

DISKPART> sel dis 2

The disk you specified is not valid.

There is no disk selected.

DISKPART> det dis

There is no disk selected to list details for.
Please select a disk and try again.

Displays the properties of the selected disk and the list of volumes on
the disk.

Syntax: DETAIL DISK

A disk must be selected for this operation to succeed.

Example:

DETAIL DISK

DISKPART> lis par

There is no disk selected to list partitions.
Select a disk and try again.

DISKPART> sel par 1

There is no disk selected to set the partition.
Select a disk and try again.

DISKPART> det par

There is no disk selected.
Please select a disk and try again.

DISKPART> sel par 2

There is no disk selected to set the partition.
Select a disk and try again.

DISKPART> det par

There is no disk selected.
Please select a disk and try again.

DISKPART> sel par 3

There is no disk selected to set the partition.
Select a disk and try again.

DISKPART> det par

There is no disk selected to set the partition.
Select a disk and try again.

MingoMongo · Dec 20, 2020

Well double fail this time. BSOD on upgrade and rebuilding the BCD still didn't make the Windows.vhd bootable. I did however make a recovery disk and it apparently repaired my Windows Boot Manager and added "Windows Recovery Environment (recovered)". I tried to repair my BCD (which may not have been the problem anyway) so renamed it then rebuilt it, but nothing changed. The BCD template store is not part of the BCD anyway so if sfc /scannow isn't fixing it idk what to do. I'm gonna leave the Windows 10 test for now since I can't figure out what's wrong. That 2016 guide is the only guide I can find and I have no clue if it even still works. It may not work because I saw that Windows 7s that have been upgraded (or maybe tried to in this case) can be missing their boot partition and have boot stuff on the main partition, maybe that gets in the way of Windows 10 UEFI. Don't know what I'm talking about really.

I've just bumped up my page file size to try and get a crash dump. Maybe I should try selecting small memory dump if that doesn't work? Also I've just found C/Windows/Panther/NewOs/Panther, is that useful? It may just be copied to the Windows~BT from what I can tell.

Panther

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Jay>bcdedit /enum

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=C:
path \bootmgr
description Windows Boot Manager
locale en-US
default {current}
displayorder {current}
timeout 30

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7 Home Premium
locale en-US
osdevice partition=C:
systemroot \Windows
resumeobject {019413d0-425f-11eb-8efd-806e6f6e6963}

C:\Users\Jay>reagentc /info
Extended configuration for the Recovery Environment

Windows RE enabled: 1
Windows RE staged: 0
Setup enabled: 0
Custom Recovery Tool: 0
WinRE.WIM directory:
Recovery Environment: \\?\GLOBALROOT\device\harddisk0\partition1\Recovery\4e
384007-793f-11e1-85b2-db8ffeee976c
BCD Id: 4e384007-793f-11e1-85b2-db8ffeee976c
Setup Files:
Recovery Operation: 4
Operation Parameter:
Boot Key Scan Code 0x0
REAGENTC.EXE: Operation successful

C:\Users\Jay>diskpart

Microsoft DiskPart version 6.1.7601
Copyright (C) 1999-2008 Microsoft Corporation.
On computer: JAY-PC

DISKPART> lis dis

Disk ### Status Size Free Dyn Gpt
-------- ------------- ------- ------- --- ---
Disk 0 Online 465 GB 0 B

DISKPART> lis vol

Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
Volume 0 D DVD-ROM 0 B No Media
Volume 1 C NTFS Partition 465 GB Healthy System

DISKPART> sel dis 0

Disk 0 is now the selected disk.

DISKPART> det dis

Samsung SSD 860 EVO 500G
Disk ID: B16DD13D
Type : ATA
Status : Online
Path : 0
Target : 0
LUN ID : 0
Location Path : PCIROOT(0)#ATA(C00T00L00)
Current Read-only State : No
Read-only : No
Boot Disk : Yes
Pagefile Disk : Yes
Hibernation File Disk : No
Crashdump Disk : Yes
Clustered Disk : No

Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
Volume 1 C NTFS Partition 465 GB Healthy System

DISKPART> lis par

Partition ### Type Size Offset
------------- ---------------- ------- -------
Partition 1 Primary 465 GB 1024 KB

DISKPART> sel par 1

Partition 1 is now the selected partition.

DISKPART> det par

Partition 1
Type : 07
Hidden: No
Active: Yes
Offset in Bytes: 1048576

Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
* Volume 1 C NTFS Partition 465 GB Healthy System

MingoMongo · Dec 20, 2020

Page file size didn't produce any crash logs. Sorry Xilo, forgot you wanted my driver lists (startup entries are same as last time)

MingoMongo · Dec 20, 2020

It's possible! I tried a different trial iso and a different guide for using VirtualBox and managed to get Windows 10 running virtually, so at least I know that I can run it on my hardware. This doesn't solve my problem since I'm trying to upgrade for stability not just a Windows 10 exclusive feature/program, but hey it's nice to have something work for once.

zbook · Dec 20, 2020

See post #219.

How long was the computer in safe mode?

Indicate whether there were BSOD while in safe mode.

And indicate the Sysnative log collector post while in safe mode.

MingoMongo · Dec 20, 2020

Sorry z I didn't have my PC in safe mode. I forgot about doing it getting distracted with the other posts.

EDIT: Also, looking back at older posts I said I had Logmein Hamachi installed when I wasn't at my computer, turns out I did try to get rid of it so I'll get rid of the associated drivers/reg entries

zbook · Dec 20, 2020

At some time all of the typical MBR default partitions were merged into one partition.

So there is one partition on disk 0: C:.

The bcdboot command in post #225 was incorrect.

If the BIOS has UEFI options and you prefer it then it may be able to be accomplished with MBR2GPT or with a clean install.
(1) Convert Windows 10 from Legacy BIOS to UEFI without Data Loss | Tutorials (tenforums.com)
(1) Convert MBR Disk to GPT Disk in Windows 10 | Tutorials (tenforums.com)

Does the computer boot properly or improperly?

If it boots properly please place the computer into safe mode for several days.
Safe Mode - Windows 7 Help Forums (sevenforums.com)
Boot into Safe Mode on Windows 10

Post new Sysnative log collector results for any BSOD.

As xilolee commented in post #168 you can work in the windows update thread.

MingoMongo · Dec 20, 2020

I only used that command because it was in the guide you sent

The computer boots fine, I was just looking at this as a possible cause of upgrade issues because I thought I need to have a partition. I'm not too fussed about the BIOS/EFI.

I can put Safe Mode on, but unless I'm trying to upgrade I don't think I'm going to run into any BSODs since I don't get them randomly. Also I'm trying to use the Windows Update thread but no one's replied

zbook · Dec 20, 2020

Switching from MBR to UEFI is easy during a clean install as the data is already backed up.

UEFI has a secure boot option that adds an extra layer of protection from malware.
(2) Enable or Disable Secure Boot on Windows 10 PC | Tutorials (tenforums.com)

As drives become larger the UEFI option is used for drives > 2 TB.

There are BSOD that are specific to upgrades however these were not seen in the log files: setupmem.dmp

Safe mode can be used with networking.

This allows Ethernet.

Some computers can use wifi while in safe mode.

The longer the computer is in safe mode the better the testing conditions.

For the other thread(s) consider closing them.

Then open a new thread with a new title and new data (scannow, surt, sfcfix, cbs, farbar, etc)

xilolee · Dec 20, 2020

Is everything working, now?
Do you have a system image done with macrium and a (macrium) recovery media that works?

Did you use a broadcom wifi card?
And wacom device?

Uninstall minitool p.w., windscribe, virtualbox.
Open iobit driver booster and clean unplugged device data.
Then: cleanmgr /sagerun:1
Run the usual checks (sigverif, sfc, windows update).
And send the usual logs (driverview, devmanview, regseeker screenshots).

zbook · Dec 20, 2020

If malwarebytes or security essentials were installed in post #226 then uninstall them too.

[SOLVED] BSOD on W7 upgrade to W10 & in driver verifier, no dumps. FIX: FEW drivers (and devices) removed; TPKD was the last one which blocked the upgrade.

Moderator

Well-known member

Moderator

Member

Well-known member

Member

Well-known member

Attachments

Moderator

Member

Well-known member

Well-known member

Well-known member

Attachments

Well-known member

Member

Well-known member

Member

Well-known member

Member

Moderator

Member