Bluescreen after newest update

[TwentyOne]

Hi guys,

so I got a weird problem. I just downloaded the newest update and everytime the game starts I get a bluescen with the bugcode 0x0000007f (according to microsoft this is an UNEXPECTED_KERNEL_MODE_TRAP).

The bluescreen appears sight as the actual game starts, and this bluescreen only appeared after this update. I was able to play this game a few hours earlier too with no problems, apart from some microstutters I had since Para Bellum launched.

Any idea what this might have caused it?

[ayylmaoski]

try to verify game integrity

[TwentyOne]

Originally posted by real nibba:

try to verify game integrity

Did, and there was no issue there, all files were verified successfully.

[TwentyOne]

So, I reinstalled my entire PC, and now a new Bluescreen appears with the Bugcheck code 0x50, and explicitly states in the memory dump that it's a driver error. The cause of it seems to be Battleye. Any ideas on how to fix this?

[MOB bubsdoge]

dude why'd you reinstall your intire computer
i'd just deal with it and be happy because r6 is a bad game

[TwentyOne]

Originally posted by DingotheDog:

dude why'd you reinstall your intire computer
i'd just deal with it and be happy because r6 is a bad game

because a) I want to solve this problem and b) I like this game

[MOB bubsdoge]

well i cant help you with this, i have had this simular problem before but instead of bluescreening I legit just couldn't launch it

i contacted ubisoft support and they told me my ♥♥♥♥♥♥ gt 610 couldn't run the game

[TwentyOne]

I figured it out now. It seems that sometimes Uplay will download a bad version od Battleye when rolling out a patch, which doesn't get detected by Uplay when validating the game files. Deleting Battleye and thus enforcing Uplay to download Battleye again resolves this issue.

[PFC Demigo [29th ID]]

The Bluescreen is NOT related to Ubisoft and its Game. -.-
Its your own Hardware and Software.
Its easy to find the solution if you had google the code

[Th0tJuice]

if ur comp blue screens its not an issue with r6 lol just google ur error code

[TwentyOne]

Originally posted by ♋️LunarCainEX🐶:

The Bluescreen is NOT related to Ubisoft and its Game. -.-
Its your own Hardware and Software.

As I said, it was highly likely that Battleye was the sole cause for it. The BSOD said it was a driver issue, and the driver being BEDaisy.sys, which is a component of battleye, and after removing Battleye to force uplay to reinstall it, the BSOD went away.

[TwentyOne]

Originally posted by Thot Juice:

if ur comp blue screens its not an issue with r6 lol just google ur error code

I did. Bugcheck 0x50 refers to a missing page in a cache, which is commonly triggered by faulty drivers. Luckily, Windows was able to catch the name of the faulty driver, namely BEDaisy.sys. I can provide the memory dump if you want some proof.

[TwentyOne]

It still hasn't stopped. Apparently, when I first launch the game (and therefor Battleye) everything works fine, but any launch after that will result in a crash. The only option for me to play now at the moment would be to remove Battleye everytime I want to play, which isn't really a viable one, to be honest.

Considering it seems very unlikely to be a hardware failure (SSD doesn't cause any errors, BSOD referencing bad drivers), it could be that either
a) Something on my PC stops Battleye from functioning correctly after the Patch
b) I can only download faulty versions of Battleye for some unknown reason

EDIT: So apparently it wasn't Battleye that was faulty, but something with the graphics drivers.I have no idea why this was the case, and there seeems to be no indication of this getting targeted by the makers of NVidia itself, as the newest "Game Ready" driver isn't a patch, but just a way to optimize some certain games.

[Considera Core]

Originally posted by ♋️LunarCainEX🐶:

The Bluescreen is NOT related to Ubisoft and its Game. -.-
Its your own Hardware and Software.
Its easy to find the solution if you had google the code

later post but honestly i wish there was common sense here, the error is PAGE_FAULT_IN_NONPAGED_AREA and is caused by BEDaisy.sys which is a driver for R6. The driver causes the blue screen but i've tried following https://www.online-tech-tips.com/computer-tips/page-fault-in-non-paged-area-error/ and 2 others but nothing helped.

So no, it's not our own software, it's the drivers from the battleye anti-cheat.

[Considera Core]

Originally posted by TwentyOne:

It still hasn't stopped. Apparently, when I first launch the game (and therefor Battleye) everything works fine, but any launch after that will result in a crash. The only option for me to play now at the moment would be to remove Battleye everytime I want to play, which isn't really a viable one, to be honest.

Considering it seems very unlikely to be a hardware failure (SSD doesn't cause any errors, BSOD referencing bad drivers), it could be that either
a) Something on my PC stops Battleye from functioning correctly after the Patch
b) I can only download faulty versions of Battleye for some unknown reason

EDIT: So apparently it wasn't Battleye that was faulty, but something with the graphics drivers.I have no idea why this was the case, and there seeems to be no indication of this getting targeted by the makers of NVidia itself, as the newest "Game Ready" driver isn't a patch, but just a way to optimize some certain games.

huh odd, i get a different error and i updated my drivers and nothing fixed it. the one i got was PAGE_FAULT_IN_NONPAGED_AREA which is related to memory or the driver trying to access memory, gpu, cpu, ssd, hd, etc info but can't find it or something like that. i also refer to this quote i found about it

"Sorry to post on a dead thread, but the reason this happens is because H1Z1 is pointing to a BattlEye that isn't owned by the game (e.g DayZ BattlEye,) but it doesn't load into memory until you start the game. When you join a server, it starts. Invalid BattlEye drivers and DLLs are loaded in whilst the actual H1Z1 BattlEye stays non-paged. H1Z1 basically says "Hey, this isn't my BattlEye! This is a page fault (Error in used memory)" and it returns a page fault with the location of the H1Z1 BattlEye, but Windows knows that it isn't paged memory. So it's a PAGE_FAULT_IN_NONPAGED_AREA (of memory) BSOD. Uninstall games that use BattlEye, check to see if H1Z1 works, slowly install them back one by one until you find the culprit is my best guess to fix. This happened to me, I just wanted to clear it up for people having this problem." <-- assuming this is the same situation for me in r6

[TwentyOne]

Originally posted by bruh:

Originally posted by TwentyOne:

It still hasn't stopped. Apparently, when I first launch the game (and therefor Battleye) everything works fine, but any launch after that will result in a crash. The only option for me to play now at the moment would be to remove Battleye everytime I want to play, which isn't really a viable one, to be honest.

Considering it seems very unlikely to be a hardware failure (SSD doesn't cause any errors, BSOD referencing bad drivers), it could be that either
a) Something on my PC stops Battleye from functioning correctly after the Patch
b) I can only download faulty versions of Battleye for some unknown reason

EDIT: So apparently it wasn't Battleye that was faulty, but something with the graphics drivers.I have no idea why this was the case, and there seeems to be no indication of this getting targeted by the makers of NVidia itself, as the newest "Game Ready" driver isn't a patch, but just a way to optimize some certain games.

huh odd, i get a different error and i updated my drivers and nothing fixed it. the one i got was PAGE_FAULT_IN_NONPAGED_AREA which is related to memory or the driver trying to access memory, gpu, cpu, ssd, hd, etc info but can't find it or something like that. i also refer to this quote i found about it

"Sorry to post on a dead thread, but the reason this happens is because H1Z1 is pointing to a BattlEye that isn't owned by the game (e.g DayZ BattlEye,) but it doesn't load into memory until you start the game. When you join a server, it starts. Invalid BattlEye drivers and DLLs are loaded in whilst the actual H1Z1 BattlEye stays non-paged. H1Z1 basically says "Hey, this isn't my BattlEye! This is a page fault (Error in used memory)" and it returns a page fault with the location of the H1Z1 BattlEye, but Windows knows that it isn't paged memory. So it's a PAGE_FAULT_IN_NONPAGED_AREA (of memory) BSOD. Uninstall games that use BattlEye, check to see if H1Z1 works, slowly install them back one by one until you find the culprit is my best guess to fix. This happened to me, I just wanted to clear it up for people having this problem." <-- assuming this is the same situation for me in r6

I kind of forgot about this thread. However I did discover the root of the problem, namely a bug that's bugging R6:S for a long time, namely the card reader problem.

For those who are unaware of this age old bug: You get an error message saying to insert a disk when you have a card reader plugged into your PC's mainboard. This error is pretty much skippable, but it seems it does have some relevancy to BattlEye, because once I tried plugging out the card reader from my mainboard the bluescreens disappeared entirely, and never came back.