[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.
- Thread starter MingoMongo
- Start date
MingoMongo
Well-known member
Weeird, the command seemed to work and I also deleted the elbycdio.sys file from the system32/drivers folder. Trying it again says it does not exist as an installed service.
Search it with
Code:
dir c:\elbyc*.* /a /b /sMingoMongo
Well-known member
Says file not found. Forced another crash to get logs just in case I sent an older sysnativefilecollection last time.
Create a new restore point:
System Restore Point - Create - Windows 7 Help Forums (sevenforums.com)
Modify the WDV customized tests to include all customized tests except
(0x00000004) Randomized low resources simulation
Post a new verifier /querysettings
Download and Install: Everything
voidtools
Launch the application
For the upgrade attempt uninstall the software related to diginet.sys/ Avid Technology Pro Tools.
Tomorrow the Windows 10 iso will be updated.
Later in the week download and install on the desktop Windows 10 iso 20H2:
Download Windows 10
When WDV has completed, (36 hours after the last BSOD) plan an in place upgrade repair using the iso.
Upgrade to Windows 10 from Windows 7 for Free
(2) Upgrade to Windows 10 | Tutorials (tenforums.com)
System Restore Point - Create - Windows 7 Help Forums (sevenforums.com)
Modify the WDV customized tests to include all customized tests except
(0x00000004) Randomized low resources simulation
Post a new verifier /querysettings
Code:
SetupDiag was unable to match to any known failure signatures.Download and Install: Everything
voidtools
Launch the application
For the upgrade attempt uninstall the software related to diginet.sys/ Avid Technology Pro Tools.
Tomorrow the Windows 10 iso will be updated.
Later in the week download and install on the desktop Windows 10 iso 20H2:
Download Windows 10
When WDV has completed, (36 hours after the last BSOD) plan an in place upgrade repair using the iso.
Upgrade to Windows 10 from Windows 7 for Free
(2) Upgrade to Windows 10 | Tutorials (tenforums.com)
MingoMongo
Well-known member
Wait before I do that, do I still have diginet/avid stuff lying around? Their drivers were causing BSODs last time so I uninstalled them and deleted the drivers. Does anything get uninstalled properly? -_-
I'll have a hunt for that stuff tomorrow, if you have any ideas where to look in the meantime I'd appreciate it!
I'll have a hunt for that stuff tomorrow, if you have any ideas where to look in the meantime I'd appreciate it!
In msinfo32.nfo, components, problem devices:
Check if you can find it in device manager: if it's there, right-click on it and "uninstall device".
Download View attachment driverview-x64.zip, unzip the folder in the desktop, then run this command (from command prompt (admin):
Code:
powershell -executionpolicy unrestricted "%userprofile%\desktop\driverview-x64\Extdrivers.ps1"Post its content here (inside the quote tags, possibly).
MingoMongo
Well-known member
Alright, using Driver Store Explorer I got rid of the diginet drivers, saibus.sys which also caused BSODs in the past, and some I don't need anymore. Thank you for telling me about Everything, works sooo much better than explorer's search. Going to set up the WDV soon, gotta make sure my restore points are working because they've disappeared in the past.
The code didn't work but I'm pretty sure I've got what you were looking for by using the app:
The code didn't work but I'm pretty sure I've got what you were looking for by using the app:
MingoMongo
Well-known member
Restore seemed to save fine, thankfully didn't need it. Still got a blue screen when not in safe mode, can post dumps if needed.
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Jay>verifier /querysettings
Special pool: Enabled
Pool tracking: Enabled
Force IRQL checking: Enabled
I/O verification: Enabled
Deadlock detection: Enabled
DMA checking: Enabled
Security checks: Enabled
Force pending I/O requests: Enabled
Low resources simulation: Disabled
IRP Logging: Enabled
Miscellaneous checks: Enabled
Verified drivers:
jraid.sys
scsiport.sys
mvs91xx.sys
mvxxmm.sys
iastora.sys
amdxata.sys
tpkd.sys
iastorf.sys
hwinfo64a.sys
nvlddmkm.sys
igdkmd64.sys
hecix64.sys
e1c62x64.sys
ndis.sys
nusb3xhc.sys
mv91cons.sys
rt64win7.sys
focusriteusbswroot.sys
tapwindscribe0901.sys
btath_bus.sys
nvvad64v.sys
nvmoduletracker.sys
nvvhci.sys
vhhcd.sys
nusb3hub.sys
nvhda64v.sys
rtkvhd64.sys
vhhub.sys
dump_diskdump.sys
dump_iastora.sys
dump_dumpfve.sys
atmfd.dll
lvuvc64.sys
lvrs64.sys
focusriteusb.sys
btfilter.sys
focusriteusbaudio.sys
btath_rcp.sys
btath_a2dp.sys
btath_hcrp.sys
btath_flt.sys
btath_lwflt.sysIt could be there are some incompatibilities between powershell in Windows 7 and the Windows 10 version of it.
For any BSOD:
a) run the Sysnative log collector to collect new log files
b) open file explorer> this PC > C: > in the right upper corner 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
c) or use everything to 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
a) run the Sysnative log collector to collect new log files
b) open file explorer> this PC > C: > in the right upper corner 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
c) or use everything to 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
MingoMongo
Well-known member
Sorry Are you saying you need the Memory.dmp too or is it included in the sys file collection?
What devices are attached to your system?
Focusrite audio device, and?
Just guessing: hidclass.sys could indicate some device is not totally compatibile with your system (or we didn't update its driver).
If we remove the problematic device, maybe things will work.
Focusrite audio device, and?
Just guessing: hidclass.sys could indicate some device is not totally compatibile with your system (or we didn't update its driver).
If we remove the problematic device, maybe things will work.
Last edited:
MingoMongo
Well-known member
Ah sorry I didn't realise. Here's the memory dump.
MingoMongo
Well-known member
No dump files in LiveKernelReports, just an empty folder called WATCHDOG. Just tried using verifier with all devices besides mouse and keyboard disconnected, still blue screened. Besides the Scarlett 2i2, I have a Logitech webcam and an XBox wireless controller receiver plugged in. Ethernet too if that counts. I'm going to try and see if I can find the problem driver(s) by doing some process of elimination WDV since that worked for me last time.
Uninstall and reinstall:
rt64win7.sys
Realtek PCIe GbE Family Controller
Updating a driver.
Restart WDV.
rt64win7.sys
Realtek PCIe GbE Family Controller
Updating a driver.
Restart WDV.
Code:
rtl8167 Realtek 8167 NT Driver c:\windows\system32\drivers\rt64win7.sys Kernel Driver Yes Manual Running OK Normal No Yes
Code:
Name [00000014] Realtek PCIe GbE Family Controller
Adapter Type Ethernet 802.3
Product Type Realtek PCIe GbE Family Controller
Installed Yes
PNP Device ID PCI\VEN_10EC&DEV_8168&SUBSYS_84321043&REV_06\6&1831193F&0&004800E7
Last Reset 08/12/2020 14:18
Index 14
Service Name RTL8167
IP Address 192.168.68.112, fe80::ec06:4c63:510e:33f
IP Subnet 255.255.255.0, 64
Default IP Gateway 192.168.68.1
DHCP Enabled Yes
DHCP Server 192.168.68.1
DHCP Lease Expires 08/12/2020 16:18
DHCP Lease Obtained 08/12/2020 14:18
MAC Address C8:60:00:00:2A:1D
I/O Port 0x0000A000-0x0000AFFF
Memory Address 0xF2104000-0xF2104FFF
Memory Address 0xF2100000-0xF21FFFFF
IRQ Channel IRQ 4294967293
Driver c:\windows\system32\drivers\rt64win7.sys (7.136.928.2020, 1.08 MB (1,134,688 bytes), 07/12/2020 15:24)| Rt64win7.sys | Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC | http://www.realtek.com.tw/downloads...d=5&Level=5&Conn=4&DownTypeID=3&GetDown=false |
Code:
Rt64win7.sys Mon Sep 28 06:36:27 2020 (5F71E6DB)MingoMongo
Well-known member
Uninstalled from device manager, then uninstalled previous versions I apparently had lying around with Driver Store Explorer, then installed. Still gave me a BSOD. I'm not sure if this means anything but during my WDV tests, testing rt64win7 did not produce any BSODs. Still ongoing with those btw. Memory dump here.
MingoMongo
Well-known member
So by going through all the drivers in WDV through many tests, I can see that btath_rcp.sys is triggering my BSOD with HIDCLASS.SYS, and focusriteusb.sys is causing my message-less BSOD when shutting down. Again idk if this means they're the direct cause or a symptom of something else but that's what I found. Will try to reinstall these drivers starting with focusrite.
Has Sysnative Forums helped you? Please consider donating to help us support the site!