bddci.sys permanently using 25-30% CPU


According to Sysinternals Process Explorer 64, [bddci.sys] is constantly consuming 12+% of CPU resources. This issue just began today after having BD Free up and running for the past 3 months. Normally BD uses minimal CPU time. It is now using 4 out of 8 of the i7 threads with each of the 4 threads averaging ~25% activity. Normally when idle, CPU averages around 98% free.


I do not believe BD is performing a scan as there is no drive activity detected.


12% usage is a major issue when trying to run processor intensive programs like x265.exe video conversion which can continuously use between 90-100% of all processor threads for an extended period of time without other running programs.


See attach for ProcExp results and system specs. (Yes, I have rebooted. Normally do not do this for 10+ days due to conscientious maintenance resulting in a clean computer. No virus, no malware, no nothing!)

Screenshot - 5_3_2019 , 10_50_02 AM.png


G180_Specs_(public).pdf

Comments


  • The same issue here. Uninstalling, installing the new Windows Update from today, rebooting and reinstalling did help up to the next reboot. Behaviour is the same again. Process Explorer Screenshot

  • Jyazen
    edited May 2019


    Yeah, having the same issue also after bddci.sys was updated yesterday (3 May 2019) at 5:28 pm GMT+8. It's taking up 25-30% CPU at all times.


    I do note that this thread is in the wrong section though, this is not for BD Mobile/Android but for BD Free, heh.


  • We started a thread in the wrong section. Since the update from yesterday, Bitdefender's bddci.sys consumes 25-30% CPU all the time, wasting power and making the fan run.


    -> 

    /index.php?/topic/80836-bddcisys-consuming-cpu-resources/&do=embed&embedDo=getNewComment" style="height:387px;max-width:502px;">


     


  • You're right. I started a new thread in the proper sub forum and put a link to this thread.


  • With the most recent up date like 10 minutes ago, it seems to be fixed.


  • Re-installed the software, rebooted - can confirm, works correct again!