BSOD Kernel Auto Boost Lock Acquisition With Raised IRQL

zbook said:

Hi mudslag,

Welcome to the the Ten Forums BSOD forum.

Please perform the following steps:

1) Open file explorer > this PC > C: > in the right upper corner search for: C:\windows\memory.dmp > zip > post a share link into the thread using one drive, drop box, or google drive

[/CODE]

Hi:

Without OneDrive, DropBox, or GoogleDrive, the first step cannot be performed.

Nonetheless, there is STRONG empirical evidence that this BSOD is caused by MalwareBytes Anti-Ransomware for Business!

It is a repeatable event in that with this product installed, the BSOD will be triggered by Windows Backup. At least two other products: ("SQL Anywhere for Eaglesoft by Patterson Dental", and "Macrium Reflect Server Plus") have been reported as possible triggers.

In all responding cases noted so far, uninstalling MalwareBytes Anti-Ransomware for Business makes the issue go away.

AND in a MalwareBytes product forum, a staff member posted: "..., this is a bug with any Windows 1607 on 14393 build and ARW. For the moment, disable the Ransomware protection real-time. A fix to the engine will be coming shortly, targeted for the middle of next week. "

The detailed thread may be examined here: KERNEL_AUTO_BOOST_LOCK_ACQUISITION_WITH_RAISED_IRQL - Malwarebytes Anti-Ransomware for Business - Malwarebytes Forums

Best regards...

mudslag said:

Got 2 bsod in the last hour with the stop code: Kernel Auto Boost Lock Acquisition With Raised IRQL. Before this, I got this in the past but maybe 6 months ago. Im at a complete loss as to what is going on. It's happened when I had my work programs up and it happened when I had nothing running.

I googled the error and none of the issues related to this are something I have. I don't have a wireless adapter, bluethooth device or DNAS on the system. The BIOS is up to date and no external HD and nothing showed up with checking the disk for errors.

Iv uploaded the log collector and looking for advice. Thanks

Attachment 221203

I had this problem and found it was ultimately caused by the presence of Malwarebytes Anti-Ransomware on the server.
If you are running it on Windows Server, that's likely the cause. That was the problem for me.