In after everyone spammed the same thing: CF is working alright, something is messing with the OS stuff that's usually used by Xtrap. Most likely it's either a virus, AV or just corrupted files. Perform both a thorough AV scan and, if possible, check for both disk errors and file consistency. Then see if your AV is the culprit by uninstalling it temporarily (yes, uninstalling it - some AVs have kernel-level stuff that can't be disabled).
If that fails (and you've done everything already mentioned in this thread), I would say you're pretty much left with no alternative than to go through every loaded driver and see what could be causing this. Either use Windows' native boot time logging or some external program, if you find that easier. I heard Process Monitor has got something decent
If that fails (and you've done everything already mentioned in this thread), I would say you're pretty much left with no alternative than to go through every loaded driver and see what could be causing this. Either use Windows' native boot time logging or some external program, if you find that easier. I heard Process Monitor has got something decent