My pc is ryzen 5-6600H with rtx3060 win11pro. I've noticed that every game using BattleEye anti-cheat causes a Blue Screen of Death. There is something written about core heap corruption. Any ideas for fixing it? i like ps2 but now i cant play
Generic stuff: Drivers, drivers, drivers. Make sure they're up to date across the board. BSOD is a kernel level failure where driver code runs. BattleEye by it's nature would have some component in kernel mode with the rest in user mode. Be sure it's up to date (remove/reinstall if needed). It may also bump heads with other security software. More specific stuff: Need info. Find your system eventlog look for an event ID 1001 in there. Paste it here. (omit your computername)
Did you receive any error involving BEdaisy.sys by chance? If you get this again, could you snap a photo of the screen that reveals any code or file error message? This would be very helpful. Thanks!
there are 2 errors , cant post screnshot for unknown reason. - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> - <System> <Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{abce23e7-de45-4366-8631-84fa6c525952}" /> <EventID>1001</EventID> <Version>1</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x8000000000000000</Keywords> <TimeCreated SystemTime="2023-04-05T23:07:20.2884585Z" /> <EventRecordID>3029</EventRecordID> <Correlation /> <Execution ProcessID="1296" ThreadID="1300" /> <Channel>System</Channel> <Computer>A-Nitro-5</Computer> <Security UserID="S-1-5-18" /> </System> - <EventData> <Data Name="param1">0x0000013a (0x0000000000000011, 0xffffb28b2a002140, 0xffffb28b4c755440, 0x0000000000000000)</Data> <Data Name="param2">C:\Windows\Minidump\040623-12906-01.dmp</Data> <Data Name="param3">2ec37f6e-1a79-4069-af73-51505fa80fe3</Data> </EventData> </Event> and -<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> - <System> <Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{abce23e7-de45-4366-8631-84fa6c525952}" /> <EventID>1001</EventID> <Version>1</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x8000000000000000</Keywords> <TimeCreated SystemTime="2023-04-05T23:11:11.7472187Z" /> <EventRecordID>3162</EventRecordID> <Correlation /> <Execution ProcessID="1300" ThreadID="1304" /> <Channel>System</Channel> <Computer>A-Nitro-5</Computer> <Security UserID="S-1-5-18" /> </System> - <EventData> <Data Name="param1">0x0000013a (0x0000000000000011, 0xffff9a08ea002140, 0xffff9a0909905120, 0x0000000000000000)</Data> <Data Name="param2">C:\Windows\Minidump\040623-11359-01.dmp</Data> <Data Name="param3">3d461e35-100e-4571-8aff-bffef5b0f8c3</Data> </EventData> </Event>
this is your stop code. 0x0000013a (0x0000000000000011, 0xffffb28b2a002140, 0xffffb28b4c755440, 0x0000000000000000) That's kernel heap corruption.. Bug check 0x13A KERNEL_MODE_HEAP_CORRUPTION - Windows drivers | Microsoft Learn Specifically..0x11 : The heap detected invalid internal state during the current operation. This is usually the result of a buffer overflow. These can be a bit of a ***** to debug as the corruption happens sometime well prior to the crash. The driver (typically) causing this crash can just as easily be a victim rather than the offender. But this is what you do: go in the microsoft store on your PC download WinDbgX (aka WinDbg Preview) In File | Settings | debug settings, add the following to your symbols path: SRV*https://msdl.microsoft.com/download/symbols file open (or drag and drop) that C:\windows\memory.dmp file (or this one: C:\Windows\Minidump\040623-11359-01.dmp ) into the debugger. Once loaded run this command: !analyze -v More info: Stop error or blue screen error troubleshooting - Windows Client | Microsoft Learn Microsoft public symbol server - Windows drivers | Microsoft Learn
You can find a good list of recent application crashes with: Start | Run | MsInfo32 In the left tree expand Software Environment Click on Windows Error Reporting at the bottom. It will take a moment to load. It's sorted by "alphabetical date" which is just wrong, so pay close attention