Occasional BSOD (Kernel Security Check Failure), high CPU usage

Hi community,
usually I don't post in forums, but I'm afraid I'm stuck. Also, I have two issues that I believe are interrelated, so I hope I'm correct in this part of the forum:
1) Occasional BSODs (three since 27 June)
2) extremely high CPU usage that makes using my PC hard

A few days ago, while working on my Lenovo T520 notebook for about two hours already, I got a Kernel Security Check Failure BSOD. After restarting, the PC worked just fine, only Windows Defender showed a faulty driver. I manually updated it (I think it was for the memory card or so) and the PC worked fine for some hours before I got another BSOD (driver verifier detected violation). However, after restart, the driver manager did not show any problems, and manually updating some third party drivers did not help, all were supposedly new. Here is a .dmp from the, as I think, second BSOD: Dropbox - 062818-27953-01.dmp

What I did since then and what other complications occurred:
1) Make sure Windows 10 is up to date
2) Updating BIOS
3) Using third party software to update all drivers automatically (15 drivers updated)
However, after another BSOD (now Kernel Security Check Failure again), my computer is on constant high CPU usage (usually around 75%, often 100%, and it takes ages for programs to start) and I can hardly use it for work. However, there is no single process that is taking up the memory, often e.g. firefox is first with around 40 percent or so, but it seems to sum up in a weird way. (After fresh boot, not opening any programs, after some time the fan stops working and CPU is low. But that only works without opening any programs.) So I randomly did:
4) sfc /scannow (no errors)
5) chkdsk (no errors)
6) windows start up repair (because I was desperate - of course nothing changed)
7) boot in safe mode - the computer runs smooth again!
8) do a clean boot - same problems as before

When doing a clean boot, the services running are exactly the same as in safe mode, and still I have problems in the former but not in safe mode.
a) What can I do to get normal CPU usage?
b) How can I assure the BSOD does not return? I have lost some unsaved files because of this.

Hello Rhina,

The successful safe mode boot indicates that this is a driver issue rather than hardware, there are more drivers that operate with a clean boot since some services start in clean boot which do not start in safe mode, e.g. the network drivers.

When you obtained the driver verifier detected BSOD this only happens if you have Driver Verifier enabled. This is not normally enabled and as you did not tell me you enabled it I can only assume that it has always been running. This is not good for your PC and will considerably reduce its performance. Please turn Driver Verifier off for now. If you do not know how to do so then refer to this tutorial.

Your log_collector file uploaded does not have any data, please try again and use the beta Log_collector which is provided at the end of the BSOD posting instructions - this one may work better.

You mentioned you had used a 3rd Party Driver updater - these are notorious for introducing problems and should be avoided as they often add unwanted programs onto your system. Only update drivers from the PC manufacturer or website of the device. You need to roll back all drivers that were updated this way and try and get your device back to its earlier state. If you had a system image or backup this would be the way to do it. If not you might be able to use System Restore if it was turned on.

We will need to wait for some more BSODs and a successful upload of the files before we can provide further help. Filling in more details in your "My Computer" section would also be useful.

Thank you, philc43

I immediately disabled the Driver Verifier. I then restarted my PC. During shutdown, I got a new BSOD (Unexpected Kernel Mode Trap). I started and then restarted my PC again, without any BSOD. And now, it works like a charm! No high CPU usage any more. It's sometimes simple thinks like disabling the Driver Verifier that change everything. Must have overread that I need to disable it again after using it.

I attach the now working log_connector file using the beta.

*edit* At some point I must have started the Driver Verifier manually, forgot to mention that. As often, the problem sits in front of the PC, not inside.

That's good news. Run your PC for a few days and see how it goes - if you have any problems let us know.

After a few days of silence, I got the next BSOD just now, this time it's a DRIVER IRQL NOT LESS OR EQUAL and the cause is a file named BthA2DP.sys (according to the blue screen notification). I attach a new diagnostic file.

Any input? Is there an underlying problem that causes all the different kinds of BSODs?

My guess is that it is some type of Bluetooth driver. It looks like it is provided by Microsoft so I am not sure how you would update it except through Windows Update which is automatic.

Code:

0: kd> lmvm BthA2DP
Browse full module list
start             end                 module name
fffff800`8f010000 fffff800`8f048000   BthA2DP    (deferred)             
    Mapped memory image file: C:\ProgramData\Dbg\sym\BthA2DP.sys\6BCFA64038000\BthA2DP.sys
    Image path: \SystemRoot\system32\drivers\BthA2DP.sys
    Image name: BthA2DP.sys
    Browse all global symbols  functions  data
    Image was built with /Brepro flag.
    Timestamp:        6BCFA640 (This is a reproducible build file hash, not a timestamp)
    CheckSum:         00035D8C
    ImageSize:        00038000
    File version:     10.0.17134.111
    Product version:  10.0.17134.111
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        2.0 Dll
    File date:        00000000.00000000
    Translations:     0409.04b0
    Information from resource tables:
        CompanyName:      Microsoft Corporation
        ProductName:      Microsoft® Windows® Operating System
        InternalName:     btha2dp.sys
        OriginalFilename: btha2dp.sys
        ProductVersion:   10.0.17134.111
        FileVersion:      10.0.17134.111 (WinBuild.160101.0800)
        FileDescription:  Bluetooth A2DP Driver
        LegalCopyright:   © Microsoft Corporation. All rights reserved.

I would be temped to reinstall any Bluetooth devices to see if it makes a difference. What Bluetooth devices are you using?

I attached the blue tooth devices listed in the device manager. I tried to update the drivers but they were up to date already. I'm not sure which of these (except for the speakers) are safe to uninstall? Some seem to be part of the system?

Reflecting on it, I just recently got the UE Boom speakers, and I did not have problems without them. I might try not using them for two weeks or so and see where this takes me. There are several threads in forums with bluetooth devices causing problems, although mostly there is an instant BSOD as soon as people connect the device. In my case it would be a delayed BSOD, as I get only after a few hours, if at all.

The driver that caused the BSOD was associated with something identified as Bluetooth Stereo so I think that confirms it is due to the recent Boom speakers you added. See if there is any help from their website or via Google in case others have had problems.

Okay, not a single BSOD since I uninstalled the bluetooth speaker driver three weeks ago, that seems to have been the cause. I couldn't find any parallel cases on the web. Is there anything I could do in order to get around this problem? Any chance future windows version won't have this problem (i.e. waiting will help?)? It's not very urgent, but I would be nice anyway.