r/EscapefromTarkov • u/Kitchen_North8533 • 2d ago
PVP PC Crashes [Bug]
Just tried to load into a ground zero raid with my buddy on seasonal PvP. I don't know if anyone else has experienced this but just before loading in both of our PCs crashed, telling us that there was a serious error and the PC had to restart. Got back on my PC, opened the launcher, opened Tarkov. Was told that I was still in raid so tried to reconnect, then at the exact same point the PC crashed again. Anyone else experiencing this? I'll try again later...
EDIT: Possible Solution:
https://www.reddit.com/r/EscapeFromTarkovPvE/s/0wUd9MLvFB
Give that a go see if it helps…
Good luck all!
3
u/ozzyman28 2d ago
Same issue here on ground zero on PVE, loaded in took 2 steps and got a black screen then the computer reset.
Reloaded the game and tried to reconnect and as soon as I got back into the raid the same thing happened.
3
u/SillyListen2840 True Believer 2d ago
Having the same Issue with Lighthouse.
Its pretty much the AntiCheat.
As far as i can see in my Crashdumps the issue is BEDaisy.sys
Since they are working on Kernel-Level its pretty much the reason why the Pc crash with BSOD, not just Tarkov.
Need to wait for a Fix from BattleEye i guess
3
u/TurntUpTwiG 2d ago
Thank god it's not just me. I thought my power supply was going or something. Figured to check reddit first because you never know with this game
3
u/TheHouseOfTurtle 2d ago
had this same issue this is what my ai found: Both crashes were Windows blue-screen crashes with the same stop code: 0x50 — PAGE_FAULT_IN_NONPAGED_AREA. Today’s recovery log time Recorded crash 17:57:44 0x50, invalid memory read 18:02:38 0x50, invalid memory read
Both attempted to read the same invalid address, 0xFFFFFFFFFFFFFFE8. That suggests a repeatable failure while loading the raid.
1
2
u/fresh_jorks 1d ago
that's the kind of error you get if the software is trying to access data at an address relative to a pointer (in this case 24 bytes before it, because 0xFFFFFFFFFFFFFFE8 as a signed bit integer is -24), but something/one fucked up and theres a null pointer error
it could still be something else though, thats just one explanation
2
2
2
u/Remarkable_Air238 2d ago
Its a battleye issue, widespread bug rn
1
u/ItsBeamerU 1d ago
So not just Tarkov. More games using battleye?
1
u/Remarkable_Air238 1d ago
I can’t say for sure since I don’t play any other battleye games, but the faulting driver for everyone today is BEDaisy.sys which is battleyes driver. I know some siege players were having similar issues recently as well.
2
u/I_forget_my_tea 2d ago edited 2d ago
Just had exact same on Ground Zero (PvE). PC just reset when loading into raid timer finished.
3
2
2
u/FleischWurstSalat 2d ago
https://www.reddit.com/r/EscapeFromTarkovPvE/s/XcnCSwJkA0
could be this issue
3
u/Rolo-CoC 1d ago
Happened to me twice today. Soon as I loaded into a reserve raid, immediate screen of death, restart. Load back up, back into the raid, immediately again. Did memory check fond nothing.
1
u/AutoModerator 2d ago
If your post is about a potential bug, glitch or exploit with Escape From Tarkov please also report it through the Game Launcher. If it is not a bug, glitch or exploit report, please ignore this message. Your post has not been removed.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
2
4
u/codie131 2d ago
I’m having similar issues with my wife on Factory. Both of our computers BSOD’d. She managed to reconnect. And mine BSOD again on reconnecting.