T TSTEWART Contributor Joined Jan 23, 2023 Posts 47 Mar 2, 2023 #1 Hi, Upgraded from win 7 to win 10 with the help of this forum. Since upgrading I have been getting BSOD regularly. Never had this problem with win 7. Have checked memory, cpu through stress testing and no issues which lead me to believe its a software or driver problem. Ran driver verifier and got BSOD quickly. Any help to solving this issue would be appreciated. Thank-You Attachments Speccy x64 portable.zip 2.7 MB · Views: 1 SysnativeFileCollectionApp.zip 2.8 MB · Views: 8 030123-15796-01.zip 347.2 KB · Views: 5
Hi, Upgraded from win 7 to win 10 with the help of this forum. Since upgrading I have been getting BSOD regularly. Never had this problem with win 7. Have checked memory, cpu through stress testing and no issues which lead me to believe its a software or driver problem. Ran driver verifier and got BSOD quickly. Any help to solving this issue would be appreciated. Thank-You
xilolee Moderator Staff member Joined Dec 31, 2013 Posts 3,680 Location World, Europe, Italy Mar 5, 2023 #2 Hi! You uploaded speccy, instead of posting the url to the snapshot. Did you check windows 10 updates and install all of them? Try these commands (from a command prompt - running as an administrator): Code: sc delete semav6msr64 sc delete cpuz132 sc stop mtsensor sc config mtsensor start= disabled If you are not using audials: Code: sc config tbhsd start= disabled And reboot. If it won't work, try to uninstall the following programs (I'm assuming you aren't using them and you can always reinstall them, if necessary... Otherwise say something if this is not the case!): - Acronis trueimage - Eset nod32 (in the meanwhile, use windows 10 defender antivirus and firewall) - Minitool partition wizard (there is a new version: 12.7) - MSI afterburner - Spyhunter Last edited: Mar 5, 2023
Hi! You uploaded speccy, instead of posting the url to the snapshot. Did you check windows 10 updates and install all of them? Try these commands (from a command prompt - running as an administrator): Code: sc delete semav6msr64 sc delete cpuz132 sc stop mtsensor sc config mtsensor start= disabled If you are not using audials: Code: sc config tbhsd start= disabled And reboot. If it won't work, try to uninstall the following programs (I'm assuming you aren't using them and you can always reinstall them, if necessary... Otherwise say something if this is not the case!): - Acronis trueimage - Eset nod32 (in the meanwhile, use windows 10 defender antivirus and firewall) - Minitool partition wizard (there is a new version: 12.7) - MSI afterburner - Spyhunter
Z zbook Member Joined Oct 2, 2015 Posts 919 Mar 5, 2023 #3 The BSOD bugchecks were 3B, 1E, D1, 3D, 139, FC The debugging displayed two misbehaving drivers. 1) Uninstall: tcesd.sys tcesd tcesd c:\windows\system32\drivers\tcesd.sys Condusiv Technologies Corporation 2) Unisntall: dktlfsmf.sys dktlfsmf Telemetry File System Mini Filter Driver c:\windows\system32\drivers\dktlfsmf.sys Help Center Last edited by a moderator: Mar 6, 2023
The BSOD bugchecks were 3B, 1E, D1, 3D, 139, FC The debugging displayed two misbehaving drivers. 1) Uninstall: tcesd.sys tcesd tcesd c:\windows\system32\drivers\tcesd.sys Condusiv Technologies Corporation 2) Unisntall: dktlfsmf.sys dktlfsmf Telemetry File System Mini Filter Driver c:\windows\system32\drivers\dktlfsmf.sys Help Center
T TSTEWART Contributor Joined Jan 23, 2023 Posts 47 Mar 6, 2023 #5 When you said uninstall, just delete the file I assume?
x BlueRobot Administrator Staff member Joined May 7, 2013 Posts 10,291 Location %systemroot% Mar 6, 2023 #6 You shouldn't just delete the files, you'll need to uninstall the associated software.
xilolee Moderator Staff member Joined Dec 31, 2013 Posts 3,680 Location World, Europe, Italy Mar 6, 2023 #7 TSTEWART said: When you said uninstall, just delete the file I assume? Click to expand... I think zbook suggests to uninstall also condusiv software (DymaxIO, diskkeper, etc).
TSTEWART said: When you said uninstall, just delete the file I assume? Click to expand... I think zbook suggests to uninstall also condusiv software (DymaxIO, diskkeper, etc).
T TSTEWART Contributor Joined Jan 23, 2023 Posts 47 Mar 7, 2023 #8 That's the problem, program no longer exists ? it was originally on win 7 and was uninstalled and these files must still be leftover?
That's the problem, program no longer exists ? it was originally on win 7 and was uninstalled and these files must still be leftover?
x BlueRobot Administrator Staff member Joined May 7, 2013 Posts 10,291 Location %systemroot% Mar 7, 2023 #9 I would check that those drivers aren't associated to any devices first of all, you shouldn't just delete files unless there is no other method to remove them. Code: pnputil /enum-devices /drivers
I would check that those drivers aren't associated to any devices first of all, you shouldn't just delete files unless there is no other method to remove them. Code: pnputil /enum-devices /drivers
xilolee Moderator Staff member Joined Dec 31, 2013 Posts 3,680 Location World, Europe, Italy Mar 7, 2023 #10 TSTEWART said: That's the problem, program no longer exists ? it was originally on win 7 and was uninstalled and these files must still be leftover? Click to expand... From a command prompt (admin): Code: sc stop tcesd sc delete tcesd sc stop tcefs sc delete tcefs sc stop dkrtwrt sc delete dkrtwrt sc stop dktlfsmf sc delete dktlfsmf sc stop dtultrascsibus sc delete dtultrascsibus Those four files (tcesd.sys, tcefs.sys, dkrtwrt.sys, dktlfsmf.sys) are part of condusiv software DymaxIO (Diskeeper, V-locity and SSDkeeper). The last one is from daemon tools. I included it because it seems you have uninstalled daemon tools too. Haven't you? Last edited: Mar 7, 2023
TSTEWART said: That's the problem, program no longer exists ? it was originally on win 7 and was uninstalled and these files must still be leftover? Click to expand... From a command prompt (admin): Code: sc stop tcesd sc delete tcesd sc stop tcefs sc delete tcefs sc stop dkrtwrt sc delete dkrtwrt sc stop dktlfsmf sc delete dktlfsmf sc stop dtultrascsibus sc delete dtultrascsibus Those four files (tcesd.sys, tcefs.sys, dkrtwrt.sys, dktlfsmf.sys) are part of condusiv software DymaxIO (Diskeeper, V-locity and SSDkeeper). The last one is from daemon tools. I included it because it seems you have uninstalled daemon tools too. Haven't you?
T TSTEWART Contributor Joined Jan 23, 2023 Posts 47 Mar 7, 2023 #11 Hi, after taking out the the files ( tcesd.sys and dktlsmf.sys) the first time i got the Stop code Inaccessible Boot Device and had to restore system with backup. same outcome with the fix. Thank-You for Helping
Hi, after taking out the the files ( tcesd.sys and dktlsmf.sys) the first time i got the Stop code Inaccessible Boot Device and had to restore system with backup. same outcome with the fix. Thank-You for Helping
xilolee Moderator Staff member Joined Dec 31, 2013 Posts 3,680 Location World, Europe, Italy Mar 7, 2023 #12 Did you include or exclude the daemon tools file from the previous commands? Please, run again the bsod collection app for fresh logs.
Did you include or exclude the daemon tools file from the previous commands? Please, run again the bsod collection app for fresh logs.
T TSTEWART Contributor Joined Jan 23, 2023 Posts 47 Mar 8, 2023 #13 The first time I just deleted the 2 files tcesd.sys and dktlfsmf.sys out of the system32 directory. The second time I ran the full cmd prompt with all you directed above. Both times the Inaccessible_Boot_Device and had to reinstall system with a backup? These files must be tied into the boot system somehow? Thank-You for your help. Attachments SysnativeFileCollectionApp.zip 2.8 MB · Views: 3
The first time I just deleted the 2 files tcesd.sys and dktlfsmf.sys out of the system32 directory. The second time I ran the full cmd prompt with all you directed above. Both times the Inaccessible_Boot_Device and had to reinstall system with a backup? These files must be tied into the boot system somehow? Thank-You for your help.
x BlueRobot Administrator Staff member Joined May 7, 2013 Posts 10,291 Location %systemroot% Mar 8, 2023 #14 I did mention this in my last post.
T TSTEWART Contributor Joined Jan 23, 2023 Posts 47 Mar 8, 2023 #15 What if I reinstalled diskeeper and tried to uninstall again?
xilolee Moderator Staff member Joined Dec 31, 2013 Posts 3,680 Location World, Europe, Italy Mar 8, 2023 #17 Ok, re-do the steps in the first reply. Then post fresh logs (bsodcollectionapp).
x BlueRobot Administrator Staff member Joined May 7, 2013 Posts 10,291 Location %systemroot% Mar 8, 2023 #18 If the driver is located in the Driver Store then you can remove it using pnputil, this is the safest method. There's two options for identifying its package within the store: use the command I mentioned previously or search the registry using FRST64 with the driver name.
If the driver is located in the Driver Store then you can remove it using pnputil, this is the safest method. There's two options for identifying its package within the store: use the command I mentioned previously or search the registry using FRST64 with the driver name.
T TSTEWART Contributor Joined Jan 23, 2023 Posts 47 Mar 8, 2023 #19 The files are listed but for the last 12 hrs no crashes? maybe something changed ? Attachments BSOD.jpg 134 KB · Views: 6
x BlueRobot Administrator Staff member Joined May 7, 2013 Posts 10,291 Location %systemroot% Mar 8, 2023 #20 I would see if the system remains stable for next 48 hours then, otherwise do a FRST registry search using these instructions: FRST Registry Search 1. Run FRST64 by Right-Clicking on the file and choosing Run as administrator. 2. Copy and paste tcesd into the Search box and click the Search Registry button. 3. When the scan is complete a notepad window will open with the results. Please attach this to your next reply. It is saved on your desktop named SearchReg.txt. You can do the same for the other drivers as well, I believe you use a semi-colon to search for multiple strings e.g. tcesd; dktlfsmf.
I would see if the system remains stable for next 48 hours then, otherwise do a FRST registry search using these instructions: FRST Registry Search 1. Run FRST64 by Right-Clicking on the file and choosing Run as administrator. 2. Copy and paste tcesd into the Search box and click the Search Registry button. 3. When the scan is complete a notepad window will open with the results. Please attach this to your next reply. It is saved on your desktop named SearchReg.txt. You can do the same for the other drivers as well, I believe you use a semi-colon to search for multiple strings e.g. tcesd; dktlfsmf.