TDI.sys with BSOD occurs updating from 1809 to 1909

%3CLINGO-SUB%20id%3D%22lingo-sub-1371742%22%20slang%3D%22en-US%22%3ETDI.sys%20with%20BSOD%20occurs%20updating%20from%201809%20to%201909%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1371742%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSTRONG%3ESummary%20of%20Problem%3A%26nbsp%3B%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3EI%20have%20three%20identical%20hp%208440p%20laptop%20production%20systems%20and%20another%204th%20identical%20spare%20laptop%20that%20I%20have%20the%20luxury%20of%20using%20as%20a%20troubleshooting%20tool%20.%26nbsp%3B%20All%20are%20running%20Win10%20with%20no%20operational%20issues%2C%20and%20the%20troubleshooting%20laptop%20has%20only%20a%20single%20internal%20OS%2FApp%20SSD%20and%20an%20external%20USB%20mouse.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20issue%20involves%20only%20failed%20attempts%20to%20update%20from%20WIN10%20revision%201809%20to%201909.%26nbsp%3B%20Please%20make%20a%20mental%20note%20that%20the%20systems%20implement%20%3CSTRONG%3EIDENTICAL%3C%2FSTRONG%3E%20hardware%20configurations%2C%20device%20drivers%2C%20and%20application%20software.%26nbsp%3B%20In%20addition%2C%20one%20of%20the%208440p%20production%20laptops%20has%20successfully%20updated%20to%201909%20courtesy%20of%20the%20Windows%20Updater.%26nbsp%3B%20The%20other%20three%20refuse%20to%20upgrade.%20%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20spent%20hours%20on%20problem%20isolation%20using%20the%20trouble%20shooting%20laptop%20which%20has%20a%20mirrored%20image%20of%20the%20OS%20and%20application%20software%20that%20the%20other%20three%20laptops%20are%20using.%26nbsp%3B%20For%20the%20purpose%20of%20this%20discussion%2C%20I%20have%20eliminated%20hardware%20as%20the%20cause%20of%20this%20failure%20by%20using%20recommended%20techniques%20and%20tools.%26nbsp%3B%20Additionally%2C%20the%20BSOD%20and%20failure%20modes%20of%20all%20systems%20are%20%3CSTRONG%3EIDENTICAL%3C%2FSTRONG%3E%2C%20including%20attempts%20to%20update%20using%20the%20Windows%20updater%2C%20update%20assistant%2C%20or%20windows%20ISO%20download%20created%20from%20the%20Microsoft%20Nov%202019%20update%20site.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3EDetails%20of%20the%20failure%3A%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3EBegin%20update%20from%20OS%20source%20of%20choice.%26nbsp%3B%20Update%20completes%20interactive%20dialog%20and%20creation%20of%20updated%20OS%20code%20proceeds.%26nbsp%3B%20Once%20completed%2C%20the%20system%20reboots%20and%20begins%20installation.%26nbsp%3B%20At%20approximately%2030%20percent%2C%20the%20system%20display%20goes%20black%20and%20another%20reboot%20occurs.%26nbsp%3B%20When%20the%20system%20reboot%20completes%2C%20the%20system%20restarts%20the%20installation%20and%20hangs%20at%2030%25%20for%20a%20short%20time.%26nbsp%3B%20After%20a%20few%20seconds%2C%20the%20BSOD%20is%20displayed%20with%20the%20TDI.SYS%20driver%20reported%20as%20the%20offending%20piece%20of%20code.%3C%2FP%3E%3CP%3EUnfortunately%2C%20I%20do%20not%20have%20the%20documentation%20to%20decode%20the%20four%20SP%20codes%20reported%20in%20the%20roll%20back%20file.%26nbsp%3B%20Neither%20do%20I%20have%20another%20TDI.sys%20driver%20to%20replace%20the%201809%20revision.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20suspect%20that%20there%20are%20other%20individuals%20that%20have%20encountered%20this%20failure%20and%20perhaps%20a%20solution%20has%20already%20been%20provided%20by%20Microsoft.%26nbsp%3B%20I%20would%20appreciate%20greatly%20information%20that%20would%20assist%20in%20the%20successful%20resolution%20of%20this%20issue.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20submit%20the%20following%20data%20from%20the%20%3CSTRONG%3ESETUPLOG%3C%2FSTRONG%3E%20analyzer.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3ESETUPDIAG.logs%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3ESetupDiag%20version%3A%201.6.0.0%3CBR%20%2F%3ESystem%20Information%3A%3CBR%20%2F%3EMachine%20Name%20%3D%20COTTONMOUTH2%3CBR%20%2F%3EManufacturer%20%3D%20Hewlett-Packard%3CBR%20%2F%3EModel%20%3D%20HP%20EliteBook%208440p%3CBR%20%2F%3EHostOSArchitecture%20%3D%201033%3CBR%20%2F%3EFirmwareType%20%3D%20PCAT%3CBR%20%2F%3EBiosReleaseDate%20%3D%2020151111000000.000000%2B000%3CBR%20%2F%3EBiosVendor%20%3D%20Default%20System%20BIOS%3CBR%20%2F%3EBiosVersion%20%3D%2068CCU%20Ver.%20F.60%3CBR%20%2F%3EHostOSVersion%20%3D%2010.0.17763%3CBR%20%2F%3EHostOSBuildString%20%3D%2017763.1.x86fre.rs5_release.180914-1434%3CBR%20%2F%3ETargetOSBuildString%20%3D%2010.0.18362.770%20(19h1_release_svc_prod1.200309-1836)%3CBR%20%2F%3EHostOSLanguageId%20%3D%3CBR%20%2F%3EHostOSEdition%20%3D%20Professional%3CBR%20%2F%3ERegisteredAV%20%3D%20Norton%20360%3CBR%20%2F%3EFilterDrivers%20%3D%20FileInfo%3CBR%20%2F%3EUpgradeStartTime%20%3D%205%2F6%2F2020%206%3A48%3A55%20PM%3CBR%20%2F%3EUpgradeEndTime%20%3D%205%2F6%2F2020%208%3A21%3A51%20PM%3CBR%20%2F%3EUpgradeElapsedTime%20%3D%2001%3A32%3A56%3CBR%20%2F%3ECV%20%3D%20kHVIkDfaRUKLbXt3%3CBR%20%2F%3EReportId%20%3D%2088DCF397-6380-41CA-B38B-67FCEE3C7669%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EError%3A%20Found%20crash%20information%20in%20rollback%20log.%3CBR%20%2F%3EBugCheck%20Code%3A%200x0000007E%3CBR%20%2F%3EDriver%3A%20TDI.sys%3CBR%20%2F%3ESetupPhase%3A%20FirstBoot%2CStart%3C%2FP%3E%3CP%3ERefer%20to%20%22%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-hardware%2Fdrivers%2Fdebugger%2Fbug-check-code-reference2%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-hardware%2Fdrivers%2Fdebugger%2Fbug-check-code-reference2%3C%2FA%3E%22%20for%20error%20information.%3CBR%20%2F%3ERecommend%20you%20update%20the%20driver%20package%20or%20remove%20the%20device%20and%20drivers%20if%20possible%2C%20and%20try%20again.%3C%2FP%3E%3CP%3ELast%20Setup%20Phase%3A%3CBR%20%2F%3EPhase%20Name%3A%20Pre%20First%20Boot%3CBR%20%2F%3EPhase%20Started%3A%205%2F6%2F2020%208%3A21%3A51%20PM%3CBR%20%2F%3EPhase%20Ended%3A%201%2F1%2F0001%2012%3A00%3A00%20AM%3CBR%20%2F%3EPhase%20Time%20Delta%3A%2000%3A00%3A00%3CBR%20%2F%3ECompleted%20Successfully%3F%20False%3C%2FP%3E%3CP%3E%3CBR%20%2F%3ELast%20Setup%20Operation%3A%3CBR%20%2F%3EOperation%20Name%3A%20Setup%20the%20recovery%20partition%3CBR%20%2F%3EOperation%20Started%3A%205%2F6%2F2020%208%3A21%3A51%20PM%3CBR%20%2F%3EOperation%20Ended%3A%201%2F1%2F0001%2012%3A00%3A00%20AM%3CBR%20%2F%3EOperation%20Time%20Delta%3A%200%3A00%3A00%3A00.0000000%3CBR%20%2F%3ECompleted%20Successfully%3F%20False%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3ESetupact_rollback%3A%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E2020-05-06%2020%3A22%3A51%2C%20Info%20%3CSTRONG%3ECheckCrashInfo%3A%20Crash%20detected%2C%20exiting.%3C%2FSTRONG%3E%3CBR%20%2F%3E2020-05-06%2020%3A22%3A52%2C%20Info%20%3CSTRONG%3ESP%20Crash%200x0000007E%3C%2FSTRONG%3E%20detected%3CBR%20%2F%3E2020-05-06%2020%3A22%3A52%2C%20Info%20%3CSTRONG%3ESP%20Parameter%201%20%3A%200xFFFFFFFFC0000005%3C%2FSTRONG%3E%3CBR%20%2F%3E2020-05-06%2020%3A22%3A52%2C%20Info%20%3CSTRONG%3ESP%20Parameter%202%20%3A%200xFFFFFFFF93031B1C%3C%2FSTRONG%3E%3CBR%20%2F%3E2020-05-06%2020%3A22%3A52%2C%20Info%20%3CSTRONG%3ESP%20Parameter%203%20%3A%200xFFFFFFFF890CBB48%3C%2FSTRONG%3E%3CBR%20%2F%3E2020-05-06%2020%3A22%3A52%2C%20Info%20%3CSTRONG%3ESP%20Parameter%204%20%3A%200xFFFFFFFF890CB700%3C%2FSTRONG%3E%3CBR%20%2F%3E2020-05-06%2020%3A22%3A52%2C%20Info%20SP%20Param%20module%20name%3A%20%3CSTRONG%3ETDI.sys%3C%2FSTRONG%3E%3CBR%20%2F%3E2020-05-06%2020%3A22%3A52%2C%20Info%20SP%20Frame%200%2C%20module%3A%20nt%3CBR%20%2F%3E2020-05-06%2020%3A22%3A52%2C%20Info%20SP%20Frame%201%2C%20module%3A%20nt%3CBR%20%2F%3E2020-05-06%2020%3A22%3A52%2C%20Info%20SP%20Frame%202%2C%20module%3A%20nt%3CBR%20%2F%3E2020-05-06%2020%3A22%3A52%2C%20Info%20SP%20Frame%203%2C%20module%3A%20nt%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E-----%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Visitor

Summary of Problem: 

I have three identical hp 8440p laptop production systems and another 4th identical spare laptop that I have the luxury of using as a troubleshooting tool .  All are running Win10 with no operational issues, and the troubleshooting laptop has only a single internal OS/App SSD and an external USB mouse. 

 

This issue involves only failed attempts to update from WIN10 revision 1809 to 1909.  Please make a mental note that the systems implement IDENTICAL hardware configurations, device drivers, and application software.  In addition, one of the 8440p production laptops has successfully updated to 1909 courtesy of the Windows Updater.  The other three refuse to upgrade.  

 

I've spent hours on problem isolation using the trouble shooting laptop which has a mirrored image of the OS and application software that the other three laptops are using.  For the purpose of this discussion, I have eliminated hardware as the cause of this failure by using recommended techniques and tools.  Additionally, the BSOD and failure modes of all systems are IDENTICAL, including attempts to update using the Windows updater, update assistant, or windows ISO download created from the Microsoft Nov 2019 update site.

 

Details of the failure:

Begin update from OS source of choice.  Update completes interactive dialog and creation of updated OS code proceeds.  Once completed, the system reboots and begins installation.  At approximately 30 percent, the system display goes black and another reboot occurs.  When the system reboot completes, the system restarts the installation and hangs at 30% for a short time.  After a few seconds, the BSOD is displayed with the TDI.SYS driver reported as the offending piece of code.

Unfortunately, I do not have the documentation to decode the four SP codes reported in the roll back file.  Neither do I have another TDI.sys driver to replace the 1809 revision.

 

I suspect that there are other individuals that have encountered this failure and perhaps a solution has already been provided by Microsoft.  I would appreciate greatly information that would assist in the successful resolution of this issue. 

 

I submit the following data from the SETUPLOG analyzer.

 

SETUPDIAG.logs

SetupDiag version: 1.6.0.0
System Information:
Machine Name = COTTONMOUTH2
Manufacturer = Hewlett-Packard
Model = HP EliteBook 8440p
HostOSArchitecture = 1033
FirmwareType = PCAT
BiosReleaseDate = 20151111000000.000000+000
BiosVendor = Default System BIOS
BiosVersion = 68CCU Ver. F.60
HostOSVersion = 10.0.17763
HostOSBuildString = 17763.1.x86fre.rs5_release.180914-1434
TargetOSBuildString = 10.0.18362.770 (19h1_release_svc_prod1.200309-1836)
HostOSLanguageId =
HostOSEdition = Professional
RegisteredAV = Norton 360
FilterDrivers = FileInfo
UpgradeStartTime = 5/6/2020 6:48:55 PM
UpgradeEndTime = 5/6/2020 8:21:51 PM
UpgradeElapsedTime = 01:32:56
CV = kHVIkDfaRUKLbXt3
ReportId = 88DCF397-6380-41CA-B38B-67FCEE3C7669


Error: Found crash information in rollback log.
BugCheck Code: 0x0000007E
Driver: TDI.sys
SetupPhase: FirstBoot,Start

Refer to "https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-code-reference2" for error information.
Recommend you update the driver package or remove the device and drivers if possible, and try again.

Last Setup Phase:
Phase Name: Pre First Boot
Phase Started: 5/6/2020 8:21:51 PM
Phase Ended: 1/1/0001 12:00:00 AM
Phase Time Delta: 00:00:00
Completed Successfully? False


Last Setup Operation:
Operation Name: Setup the recovery partition
Operation Started: 5/6/2020 8:21:51 PM
Operation Ended: 1/1/0001 12:00:00 AM
Operation Time Delta: 0:00:00:00.0000000
Completed Successfully? False

 

Setupact_rollback:

2020-05-06 20:22:51, Info CheckCrashInfo: Crash detected, exiting.
2020-05-06 20:22:52, Info SP Crash 0x0000007E detected
2020-05-06 20:22:52, Info SP Parameter 1 : 0xFFFFFFFFC0000005
2020-05-06 20:22:52, Info SP Parameter 2 : 0xFFFFFFFF93031B1C
2020-05-06 20:22:52, Info SP Parameter 3 : 0xFFFFFFFF890CBB48
2020-05-06 20:22:52, Info SP Parameter 4 : 0xFFFFFFFF890CB700
2020-05-06 20:22:52, Info SP Param module name: TDI.sys
2020-05-06 20:22:52, Info SP Frame 0, module: nt
2020-05-06 20:22:52, Info SP Frame 1, module: nt
2020-05-06 20:22:52, Info SP Frame 2, module: nt
2020-05-06 20:22:52, Info SP Frame 3, module: nt

 

-----

 

 

 

0 Replies