[KERNEL_AUTO_BOOST_LOCK_ACQUISITION_WITH_RAISED_IRQL]

4 hours ago, BillPeavy said:

Dylion,

I've not seen this documented anywhere.  Can you point it out please?

Thanks,

 

 

In my case Window Server is in the requirements (Endpoint Security Quick Start Guide.pdf) :

[KERNEL_AUTO_BOOST_LOCK_ACQUISITION_WITH_RAISED_IRQL]

9 hours ago, DScherer said:

Vincent, did they get back to you with a solution?

Not yet. I removed Malwarebytes for the moment.

[KERNEL_AUTO_BOOST_LOCK_ACQUISITION_WITH_RAISED_IRQL]

 

Hi,

blue screen since one week on a server :

System Information (local)
--------------------------------------------------------------------------------

Computer name: SERVAGC
Windows version: Windows Server 2016 , 10.0, version 1607, build: 14393
Windows dir: C:\Windows
Hardware: PRIMERGY TX1310 M3, FUJITSU, D3521-A1
CPU: GenuineIntel Intel(R) Xeon(R) CPU E3-1225 v6 @ 3.30GHz Intel8664, level: 6
4 logical processors, active mask: 15
RAM: 16994754560 bytes (15,8GB)

--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dumps are enabled on your computer. 

Crash dump directories: 
C:\Windows
C:\Windows\Minidump

On Thu 06/06/2019 16:58:06 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\060619-22062-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x149F90) 
Bugcheck code: 0x192 (0xFFFFF8008CBD8940, 0xFFFF8A0A1AA2C2A8, 0x2, 0x0)
Error: KERNEL_AUTO_BOOST_LOCK_ACQUISITION_WITH_RAISED_IRQL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a lock tracked by AutoBoost was acquired while executing at DISPATCH_LEVEL or above. 
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 

On Thu 06/06/2019 16:58:06 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: farflt.sys (farflt+0x367B) 
Bugcheck code: 0x192 (0xFFFFF8008CBD8940, 0xFFFF8A0A1AA2C2A8, 0x2, 0x0)
Error: KERNEL_AUTO_BOOST_LOCK_ACQUISITION_WITH_RAISED_IRQL
file path: C:\Windows\system32\drivers\farflt.sys
product: Malwarebytes Anti-Ransomware Protection
company: Malwarebytes
description: Malwarebytes Anti-Ransomware Protection
Bug check description: This indicates that a lock tracked by AutoBoost was acquired while executing at DISPATCH_LEVEL or above. 
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out. 
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: farflt.sys (Malwarebytes Anti-Ransomware Protection, Malwarebytes). 
Google query: farflt.sys Malwarebytes KERNEL_AUTO_BOOST_LOCK_ACQUISITION_WITH_RAISED_IRQL

--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

2 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers: 

farflt.sys (Malwarebytes Anti-Ransomware Protection, Malwarebytes)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.

Read the topic general suggestions for troubleshooting system crashes for more information. 

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further. 

Thanks,

Vincent.