[SOLVED] Constant BSOD after upgrading from win 7 to win 10. FIX: I removed condusiv software and ran the RAM at stock settings.

As suspected, this is why the Stop 0x7B bugchecks were getting thrown when you deleted those services, the drivers were registered to the filter manager and removing the associated service without modifying the UpperFilters value means that the system will throw Stop 0x7B:

Code: 
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e967-e325-11ce-bfc1-08002be10318}]
"UpperFilters"="tcesd
DKDFM
partmgr
fltsrv"

Please read here too: Deactivate the kernel mode filter driver - Windows Server

However, since you haven't had any issues so far then I would continue to use the system as normally would.
 
If I reinstalled diskeeper again then used the uninstall program woud this permentaly remove this ?
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e967-e325-11ce-bfc1-08002be10318}]
"UpperFilters"="tcesd
DKDFM
partmgr
fltsrv"
Thank-You
 
You could try it, it depends on how well written their uninstaller is, if they've provided one? Otherwise, you're going to have to disable the service, then modify that sub key value to ensure that the driver doesn't load.
 
Ok, found the entry but no value set, is this where to change value to 0x4 to deactivate the driver ?
 

Attachments

  • Reg Key.jpg
    Reg Key.jpg
    65.3 KB · Views: 11
No - you can just disable the service from the service management console (services.msc) or disable it from command prompt using:

Code: 
sc stop tcesd
sc config tcesd start= disabled

The UpperFilters value is set, I can see it in your screenshot. If you haven't had any crashes then I would suggest leaving it alone until you do.
 
Could you please do a FRST registry search for the problematic driver again? I would to check that the UpperFilters value has been modified correctly. Please also enter the following command from command prompt and then post the output:

Code: 
sc query tcesd
 
Just got back, here is the info. I didn't disable the prior
sc stop tcesd
sc config tcesd start= disabled yet ? was waiting as instructed until another crash.
Thank-You
 

Attachments

  • Report.png
    Report.png
    58 KB · Views: 3
  • FRST.txt
    FRST.txt
    119.6 KB · Views: 2
FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Download the attached fixlist.txt and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
2. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
3. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
4. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
 

Attachments

Thanks, please reboot the computer if you haven't done so already and then let us know if it crashes again.
 
One other thing, when I restarted the system an update to window was installed before the crash? The update KB 5023696
Thank-You
 
Please provide the dump files using the same collection tool as before, the one which you used in the posting instructions.
 
Let's remove the rest of the DiskKeeper drivers and prevent them from loading at boot.

FRST Registry Search
1. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
2. Copy and paste dkrtwrt;tcefs;dktlfsmf;DKDFM 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.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top