As described above I find this very odd as it never used to happen in Win 7. (I upgrade to W10 Pro x64 from W7 SP1 x64).
Only if I power the external eSATA drive off during PC shut down (Total not standby or hibernate).
I get around it by simply waiting before I power off that drive.
It's disk 0 here:
Attachment 262165
Winver: 1909 (18363.535)
Hi Ex_Brit,
Please perform the following steps:
1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /scanhealth
4) dism /online /cleanup-image /restorehealth
5) sfc /scannow
6) chkdsk /scan
7) wmic recoveros set autoreboot = false
8) wmic recoveros set DebugInfoType = 7
10) wmic recoveros get autoreboot
11) wmic recoveros get DebugInfoType
12) bcdedit /enum {badmemory}
13) 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
14) Uninstall and reinstall this software:
Code:Diskeeper 18 20.0.1296.64 Condusiv Technologies 20190504
tcesd.sys
This driver was not in our database.
It appears related to condusiv technologies.
15) Uninstall and reinstall: Mcafee AV
https://service.mcafee.com/webcenter...%3Dg4tsxh9h7_9
Code:tcesd tcesd c:\windows\system32\drivers\tcesd.sys Kernel Driver Yes Boot Running OK Normal No YesCode:tcesd tcesd tcesd Kernel Boot Running OK TRUE FALSE 0 188,416 0 12-Sep-17 3:10:57 PM C:\Windows\system32\drivers\tcesd.sys 4,096Code:benefitspopup.exe c:\program files\condusiv technologies\diskeeper\benefitspopup.exe 6268 8 200 1380 06-Jan-20 10:06 AM 20.0.1296.0 674.20 KB (690,384 bytes) 09-Nov-18 11:33 AMCode:Diskeeper Diskeeper Running Auto Own Process "c:\program files\condusiv technologies\diskeeper\dkservice.exe" Normal LocalSystem 0Code:Start Menu\Programs\Condusiv Technologies Public:Start Menu\Programs\Condusiv Technologies PublicCode:tcesd.sys Tue Sep 12 12:10:57 2017 (59B83141)
Hello Peter,
As you have discovered the BSOD is caused by the external drive being turned off when the OS is still interacting with it. PDO means Portable Data Object. PnP means plug and play
Code:PNP_DETECTED_FATAL_ERROR (ca) PnP encountered a severe error, either as a result of a problem in a driver or a problem in PnP itself. The first argument describes the nature of the problem, the second argument is the address of the PDO. The other arguments vary depending on argument 1. Arguments: Arg1: 0000000000000002, Invalid PDO An API which requires a PDO has been called with either an FDO, a PDO which hasn't been initialized yet (returned to PnP in a QueryDeviceRelation/BusRelations), or some random piece of memory. Arg2: ffffd58a906c3060, Purported PDO. Arg3: 0000000000000000, Driver object. Arg4: 0000000000000000 7: kd> !devobj ffffd58a906c3060 f fffff8076b447ad0: Unable to get value of ObpRootDirectoryObject Device object (ffffd58a906c3060) is for: Cannot read info offset from nt!ObpInfoMaskToOffset \Driver\tcesdDriverObject ffffd58a86b86d20 Current Irp 00000000 RefCount 0 Type 00000007 Flags 00000050 Vpb ffffd58a909506c0 SecurityDescriptor ffff8c8404fdb620 DevExt ffffd58a906c31b0 DevObjExt ffffd58a906c3a68 ExtensionFlags (0x00000802) DOE_DELETE_PENDING, DOE_DEFAULT_SD_PRESENT Characteristics (0x00040100) FILE_DEVICE_SECURE_OPEN, FILE_PORTABLE_DEVICE AttachedDevice (Upper) ffffd58a9097c080ffffd58a9097c080: Could not read device object or _DEVICE_OBJECT not found
For some reason the driver for the PnP operation (tcsed.sys) is causing this. Try updating the driver if you can find a newer version.
Will uninstall/reinstall the software(s) shortly.Code:Microsoft Windows [Version 10.0.18363.535] (c) 2019 Microsoft Corporation. All rights reserved. C:\Windows\system32>sfc /scannow Beginning system scan. This process will take some time. Beginning verification phase of system scan. Verification 100% complete. Windows Resource Protection found corrupt files and successfully repaired them. For online repairs, details are included in the CBS log file located at windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline repairs, details are included in the log file provided by the /OFFLOGFILE flag. C:\Windows\system32>dism /online /cleanup-image /scanhealth Deployment Image Servicing and Management tool Version: 10.0.18362.1 Image Version: 10.0.18363.535 [==========================100.0%==========================] No component store corruption detected. The operation completed successfully. C:\Windows\system32>dism /online /cleanup-image /restorehealth Deployment Image Servicing and Management tool Version: 10.0.18362.1 Image Version: 10.0.18363.535 [==========================100.0%==========================] The restore operation completed successfully. The operation completed successfully. C:\Windows\system32>sfc /scannow Beginning system scan. This process will take some time. Beginning verification phase of system scan. Verification 100% complete. Windows Resource Protection did not find any integrity violations. C:\Windows\system32>chkdsk /scan The type of the file system is NTFS. Volume label is Win 10 Pro Main x64. Stage 1: Examining basic file system structure ... 859648 file records processed. File verification completed. 5379 large file records processed. 0 bad file records processed. Stage 2: Examining file name linkage ... 5292 reparse records processed. 1010638 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found. 5292 reparse records processed. Stage 3: Examining security descriptors ... Security descriptor verification completed. 75496 data files processed. CHKDSK is verifying Usn Journal... 35111128 USN bytes processed. Usn Journal verification completed. Windows has scanned the file system and found no problems. No further action is required. 487800926 KB total disk space. 206649004 KB in 563567 files. 319160 KB in 75497 indexes. 0 KB in bad sectors. 984686 KB in use by the system. 65536 KB occupied by the log file. 279848076 KB available on disk. 4096 bytes in each allocation unit. 121950231 total allocation units on disk. 69962019 allocation units available on disk. C:\Windows\system32>wmic recoveros set autoreboot = false Updating property(s) of '\\R2D2\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\Windows|\\Device\\Harddisk1\\Partition1"' Property(s) update successful. C:\Windows\system32>wmic recoveros set DebugInfoType = 7 Updating property(s) of '\\R2D2\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\Windows|\\Device\\Harddisk1\\Partition1"' Property(s) update successful. C:\Windows\system32>wmic recoveros get autoreboot AutoReboot FALSE C:\Windows\system32>wmic recoveros get DebugInfoType DebugInfoType 7 C:\Windows\system32>bcdedit /enum {badmemory} RAM Defects ----------- identifier {badmemory} C:\Windows\system32>
First scannow:
Second scannow:Code:Windows Resource Protection found corrupt files and successfully repaired them.
Code:Windows Resource Protection did not find any integrity violations.
For any BSOD:
a) run the V2 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
Quote