IRQL_NOT_LESS_OR_EQUAL BSOD ntkrnlmp.exe

[Kaelthas]

Hello, today I've been getting BSOD when I turned on a video game. I tried scanning for viruses, but it BSOD'd again. Idk what to do, can someone help me?
Specs:
Intel I5-4690k 3.50 gHz
8GB Dual-Channel DDR3 @ 799MHz Kingston HYPERX
Gigabyte Technology Co. Ltd. H97-D3H-CF
4095MB NVIDIA GeForce GTX 960
Chieftec A80
1 TB HDD

 

[Kaelthas]

Also, logs from Whocrashed:
On Tue 1/12/2016 11:04:47 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011316-29250-01.dmp
uptime: 00:21:51
This was probably caused by the following module: bedaisy.sys (BEDaisy+0x11A38)
Bugcheck code: 0xC4 (0xE2, 0xFFFFF9807F3589D0, 0x1E60040, 0x0)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
An IRP with Irp->RequestorMode set to KernelMode was found to have a user-mode address as one of its members. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: bedaisy.sys .
Google query: bedaisy.sys DRIVER_VERIFIER_DETECTED_VIOLATION



On Tue 1/12/2016 11:04:47 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
uptime: 00:21:51
This was probably caused by the following module: bedaisy.sys (BEDaisy+0x11A38)
Bugcheck code: 0xC4 (0xE2, 0xFFFFF9807F3589D0, 0x1E60040, 0x0)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
An IRP with Irp->RequestorMode set to KernelMode was found to have a user-mode address as one of its members. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: bedaisy.sys .
Google query: bedaisy.sys DRIVER_VERIFIER_DETECTED_VIOLATION



On Tue 1/12/2016 10:19:34 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011216-17456-01.dmp
uptime: 00:03:24
This was probably caused by the following module: bedaisy.sys (BEDaisy+0x11A38)
Bugcheck code: 0xC4 (0xE2, 0xFFFFF98043EB89D0, 0x1C90040, 0x0)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
An IRP with Irp->RequestorMode set to KernelMode was found to have a user-mode address as one of its members. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: bedaisy.sys .
Google query: bedaisy.sys DRIVER_VERIFIER_DETECTED_VIOLATION



On Tue 1/12/2016 6:38:45 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011216-19219-01.dmp
uptime: 01:04:46
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xC4 (0x62, 0xFFFFFA800D9E6948, 0xFFFFFA800D3AE500, 0x1)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
The driver is unloading without first freeing its pool allocations. A bug check with this parameter occurs only when the Pool Tracking option of Driver Verifier is active. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 1/12/2016 5:26:16 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011216-17269-01.dmp
uptime: 04:26:18
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0x48, 0x2, 0x1, 0xFFFFF800031846CF)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

[johnbl]

verifier found a driver (BattleEye anti-cheat driver) that was using a usermode file handle as a kernel mode file handle. This gets flagged because it only works most of the time. When the system comes under stress, the windows memory manager can page out the code to the pagefile.sys and when it is paged back into ram the handles can be invalid and the program will crash or the driver that used the handles will corrupt kernel memory.

you can tell verifier not to test this driver by using the verifier driver exclude option.
start cmd.exe as an admin
verifier.exe /standard /all /driver.exclude BEDaisy.sys
you can turn verifier off via
verifier.exe /reset

you might have to boot into safe mode if the system bugchecks before you can enter in the command

 

[Kaelthas]

The BattleEye anti-cheat driver is for the DayZ game, that only activates and updates before going into the game. Funny enough, the BSOD I got was when I tried to turn it on. The thing is, I didn't have the verifier on before that, and I just tried to play my game. I'll try to do what you just said, will report in a few minutes.

 

[Kaelthas]

The problem persists, I excluded bedaisy.sys like you said and rebooted my system, turned on the same game, and I got another BSOD
Logs:
On Wed 1/13/2016 12:06:54 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011316-24616-01.dmp
uptime: 00:03:09
This was probably caused by the following module: bedaisy.sys (BEDaisy+0x11A38)
Bugcheck code: 0xC4 (0xE2, 0xFFFFF9804558C9D0, 0x1A20040, 0x0)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
An IRP with Irp->RequestorMode set to KernelMode was found to have a user-mode address as one of its members. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: bedaisy.sys .
Google query: bedaisy.sys DRIVER_VERIFIER_DETECTED_VIOLATION

I highly doubt it's the game's fault, I've had a fresh install for a week or so, and I've played it all week. Everything worked properly. Will try to turn off the verifier now and try to run it again.

 

[Kaelthas]

Also, resetting verifier says that "No settings were changed." got another BSOD. I'm really desperate to fix this.
Logs:crash dump file: C:\Windows\Minidump\011316-18517-01.dmp
uptime: 00:05:44
This was probably caused by the following module: bedaisy.sys (BEDaisy+0x11A38)
Bugcheck code: 0xC4 (0xE2, 0xFFFFF980477429D0, 0x1BD0040, 0x0)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
An IRP with Irp->RequestorMode set to KernelMode was found to have a user-mode address as one of its members. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: bedaisy.sys .
Google query: bedaisy.sys DRIVER_VERIFIER_DETECTED_VIOLATION

 

[johnbl]

make sure you start cmd.exe and run it as an administrator
then run the veifier commands from the command prompt. Otherwise it will not save your changes.

Also, resetting verifier says that "No settings were changed." got another BSOD. I'm really desperate to fix this.
Logs:crash dump file: C:\Windows\Minidump\011316-18517-01.dmp
uptime: 00:05:44
This was probably caused by the following module: bedaisy.sys (BEDaisy+0x11A38)
Bugcheck code: 0xC4 (0xE2, 0xFFFFF980477429D0, 0x1BD0040, 0x0)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
An IRP with Irp->RequestorMode set to KernelMode was found to have a user-mode address as one of its members. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: bedaisy.sys .
Google query: bedaisy.sys DRIVER_VERIFIER_DETECTED_VIOLATION