bsod windows 10 not booting cmdhlp.sys failure

Windows 10 unbootable after fall creators update (solved)

Can you reproduce the problem & if so how reliably?:
no (I would not want to try to reproduce)

One or two sentences explaining what actually happened:

  1. windows 10 upgraded my desktop to the fall creators update
  2. the very first boot up was fine and it showed me the new features of the fall creators updates in a tab of the edge browser.
  3. But then i simply did a restart and that is when the bsod started. I initially could never get to a loaded system with a desktop (consistently got bsod only with access to the blue fix/recover windows screens).

One or two sentences explaining what you expected to happen:
normal windows 10 boot

If a software compatibility problem have you tried the advice to make programs work with CIS?:

Any software except CIS/OS involved? If so - name, & exact version:

Any other information, eg your guess at the cause, how you tried to fix it etc:

bsod said stop code: system service exception
what failed: cmdhlp.sys

  1. The ONLY thing that worked was i managed to go into the command line option in advanced recovery of bsod and type " bcdedit /set {default} safeboot minimal" without the quotes (not recommended unless you know what you are doing). This got me into safe mode.
  2. while in safe mode: edited registry to allow uninstalling programs (safe mode disallows windows installer).
  3. while still in safe mode: uninstalled comodo using ciscleanuptool because it otherwise failed uninstalling ( i forget the comodo error, revo gave the same comodo error)
  4. rebooted and got into windows desktop normal mode - i.e. problem fixed.

Exact CIS version & configuration:
lost all that info
i assume latest ver. (?) or at least very recent

Modules enabled & level. D+/HIPS, Autosandbox/BBlocker, Firewall, & AV:

Have you made any other changes to the default config? (egs here.):

Have you updated (without uninstall) from CIS 5, 6 or 7?:

Have you imported a config from a previous version of CIS:

OS version, SP, 32/64 bit, UAC setting, account type, V.Machine used:
windows 10 1709 build 16299.125

Other security/s’box software a) currently installed b) installed since OS, including initial trial security software included with system:
cryptoprevent with custom settings that prevent interfering with boot process.

We need to know CIS version. Possible to re-install latest CIS and check?
Also, can you please check if you can find any crash dumps?

Is there a remnant of that cis version info left on my windows 10 system somewhere ? do you know?

Lets see if you can find memory dump, that will help.

%SystemRoot%\memory.dmp neither?

Hi asdfg108,
Thank you for sharing crash dump, lets us look into it.


Excellent. :slight_smile:

Hello asdfg108.
We want to get more information ,please send email to me .
My email is[at] , thank you!

I can see your version of cis is 6468 ,so I modify the code based this version .
The fixed drvier bin file have comodo digital signature .I donot know if it can be loaded normal without microsoft signature, please repalce the dirver to c:\windows\system32\drivers\cmdhlp.sys for a try.
If need ,you have to disable system signature.

I have sent the bin file to email ,please check it.

Thank you .

Would windows try to load the test driver even if comodo is not currently installed?

Thank you.

Yes, you need to make sure comodo is installed.

btw two days ago after my recovery to normal booting (the initial problem of this thread), windows immediately updated from 1709 OS Build 16299.125 to 16299.192 so conditions have changed.


After you update to 16299.192 ,Can the bsod exist?

I do not currently get any bsod however I do not currently have comodo installed. Just to be clear, it was uninstalled during safe mode to fix the bsod probelm and has never been reinstalled.

One of my concerns is that i can only get a copy of comodo 6476 but the fixed drvier bin file was based on comodo 6468.

If i reinstall comodo i think i would want to install the latest comodo (6476) and wouldn’t i want to have a fixed driver bin file that was based on that version at my disposal ?
I could have it ready to switch out cmdhlp.sys if i ran into bsod problems and try that first before unistalling comodo as the fix. Or am i wrong about this ?

6468 is the driver file version that comes with 6476, drivers file versions don’t always match CIS version package. You need to install CIS to see if you still get bsod, if you do then you should replace the driver with the fixed driver you were provided with.

So if the comodo driver 6468 (dec.28 showing from minidump) is independently named, then i may well have already been running cis 6476 when the bsod occurred. Is that right?
Thank you

No 6476 was first available on Jan 9th.

Please install the bsod cis version and the replace my cmdhlp.sys file I have sent you.

Hi asdfg108,
Can you please install CIS, replace driver file as provided by “nasion”, re-boot and confirm if you still see BSOD?


Yes I am going to do my best to look into that today and report back.

Thank you, looking forward for it.