Sigh - this game is so random, played all year with a bug that crashes after launcher (BSOD) randomly seems to happen once PC has been on a couple of days. Now I have a new mobo CPU etc -even reinstalled onto new SSD - SAME BUG occurs randomly! However it got worse after last weekend - since then more often that not once in game it totally freezes my PC after 5-10mins Ran monitoring s/ware and at the point it creashed GPU = 61C and CPU 51C so I dont think it's that. Tried reverting GPU drivers back a few months... still same. Randomly it will sometimes let me play for hours no issue! Only PS2 causes it.... Gears 5, COD WM, Outerworlds all fine nothing else breaks my PC grrrrr. Read so many posts, but nothing helps
Just to clarify, you have a new computer? Are you reusing any of the old components? If so, power supply units can being to fail over time so be sure yours is sufficient for the power needs and not too old. Perhaps try submitting a detailed description of your hardware, OS, GPU drivers and any patterns observed during your BSOD or freezes to DBG support. Maybe they can help out.
Not experiencing this, I think it might be on your end. Check if any other components are old or if your connection is just fluctuating.
Games usually tax the system more. With that description it could be anything. So you need to pinpoint the problem, there are two possible routes: 1) Figure out more about the BSOD. Get a tool like this one: https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/debugger-download-tools After restarting it can be used to analyze the dump and figure out what is the possible reason. 2) Do the same using the Event Log. There is a window administrative component called "Event Viewer", fire it up and look at the 'System' group of events where crashes are recorded with timestamps and brief descriptions/error codes. Have a go at both ways and come back with your findings. What do you see?
Looks like BEDAISY.SYS is the culprit - battleye, seems I'm not the only person that has this and it's not the only game that has the issue - now to try and figure out what might be causing to flip out! Thanks for the debug advice, at least I'm closing in!
sigh... thought the issue had gone away... but no... it's back! Played yesterday no problems... this morning I can't play for more than 5 mins... same problem BEDAISY.SYS I guess it waited for me to buy the 7yr bundle before doing this.... hope I get my monies worth in support at least ************* Path validation summary ************** Response Time (ms) Location Deferred srv* Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 18362 MP (24 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Machine Name: Kernel base = 0xfffff802`37800000 PsLoadedModuleList = 0xfffff802`37c48170 Debug session time: Sun Dec 1 09:52:16.792 2019 (UTC + 0:00) System Uptime: 0 days 0:05:14.441 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ..................................... Loading User Symbols Loading unloaded module list ......... For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff802`379c14e0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff604`c126c0b0=0000000000000139 16: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KERNEL_SECURITY_CHECK_FAILURE (139) A kernel component has corrupted a critical data structure. The corruption could potentially allow a malicious user to gain control of this machine. Arguments: Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove). Arg2: fffff604c126c3d0, Address of the trap frame for the exception that caused the bugcheck Arg3: fffff604c126c328, Address of the exception record for the exception that caused the bugcheck Arg4: 0000000000000000, Reserved Debugging Details: ------------------ *** WARNING: Unable to verify timestamp for BEDaisy.sys KEY_VALUES_STRING: 1 Key : Analysis.CPU.Sec Value: 2 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on WIN10AMD Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.Sec Value: 2 Key : Analysis.Memory.CommitPeak.Mb Value: 71 Key : Analysis.System Value: CreateObject DUMP_FILE_ATTRIBUTES: 0x8 Kernel Generated Triage Dump BUGCHECK_CODE: 139 BUGCHECK_P1: 3 BUGCHECK_P2: fffff604c126c3d0 BUGCHECK_P3: fffff604c126c328 BUGCHECK_P4: 0 TRAP_FRAME: fffff604c126c3d0 -- (.trap 0xfffff604c126c3d0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=ffffa7839d2d1620 rbx=0000000000000000 rcx=0000000000000003 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80237848b10 rsp=fffff604c126c560 rbp=ffffa7839d25e040 r8=0000000000000001 r9=0000000000000002 r10=ffffa783848efa00 r11=ffff95007f18d180 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na pe cy nt!KiExitDispatcher+0x160: fffff802`37848b10 cd29 int 29h Resetting default scope EXCEPTION_RECORD: fffff604c126c328 -- (.exr 0xfffff604c126c328) ExceptionAddress: fffff80237848b10 (nt!KiExitDispatcher+0x0000000000000160) ExceptionCode: c0000409 (Security check failure or stack buffer overrun) ExceptionFlags: 00000001 NumberParameters: 1 Parameter[0]: 0000000000000003 Subcode: 0x3 FAST_FAIL_CORRUPT_LIST_ENTRY CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application. EXCEPTION_CODE_STR: c0000409 EXCEPTION_PARAMETER1: 0000000000000003 EXCEPTION_STR: 0xc0000409 STACK_TEXT: fffff604`c126c0a8 fffff802`379d32e9 : 00000000`00000139 00000000`00000003 fffff604`c126c3d0 fffff604`c126c328 : nt!KeBugCheckEx fffff604`c126c0b0 fffff802`379d3710 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69 fffff604`c126c1f0 fffff802`379d1aa5 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00ffffff : nt!KiFastFailDispatch+0xd0 fffff604`c126c3d0 fffff802`37848b10 : 00000000`00000000 fffff604`c126c601 ffff9500`7f18d180 00000000`00000000 : nt!KiRaiseSecurityCheckFailure+0x325 fffff604`c126c560 fffff802`378a597d : ffffa783`9d2d1618 00000000`00000200 ffff9500`7f18d101 fffff802`37b6f06d : nt!KiExitDispatcher+0x160 fffff604`c126c5c0 fffff802`878b07f8 : 00000000`00003600 ffffa783`9da42068 00000000`00000100 00000000`00000002 : nt!KeInsertQueueApc+0x14d fffff604`c126c660 00000000`00003600 : ffffa783`9da42068 00000000`00000100 00000000`00000002 00000000`00000000 : BEDaisy+0x2b07f8 fffff604`c126c668 ffffa783`9da42068 : 00000000`00000100 00000000`00000002 00000000`00000000 00000000`00000000 : 0x3600 fffff604`c126c670 00000000`00000100 : 00000000`00000002 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffffa783`9da42068 fffff604`c126c678 00000000`00000002 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x100 fffff604`c126c680 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x2 SYMBOL_NAME: BEDaisy+2b07f8 MODULE_NAME: BEDaisy IMAGE_NAME: BEDaisy.sys STACK_COMMAND: .thread ; .cxr ; kb BUCKET_ID_FUNC_OFFSET: 2b07f8 FAILURE_BUCKET_ID: 0x139_3_CORRUPT_LIST_ENTRY_BEDaisy!unknown_function OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {59d8eb10-b2e4-7df6-f6a5-49968226dbb8} Followup: MachineOwner ---------
I give up - anyone know how I get some support for this beyond 1st line support - I've done the drivers / reinstall stuff to death now
In my case the BSOD is caused by a conflict between BattleEye and Fanatec drivers. I don't know how to fix it. But I'm not searching for the problem anymore.
