JavaScript is required to use Bungie.net

幫助

請協助我們幫助你。
3/27/2024 8:24:14 AM
3

Error Code Marmot/BSOD with BEDaisy.sys

I was running into issues where the game would hard crash, resetting my entire PC during activities. No error code, just audio stutter into black screen, restart from scratch. I looked at the event log - Kernel error 41, which is represents that the machine had restarted unexpectedly. I went through the following steps: - Looked at disk and memory health, both in good order. - Used a utility to double check that the SSD wasn't fried - it's doing fine. - Reinstalled BattlEye, no change. - Uninstalled Helldivers 2 and nProtect Gameguard, fearing a collision between the two games' anticheats. - Turned off Restart on System Crash, to see if I could catch any error messages before I was whisked away to a black screen. - I made sure my display drivers and windows updates were up to date. At this point, the game was still technically functional, if only for short bursts before I would crash out. From this point, I reinstalled Destiny 2 and BattlEye, making sure to restart the entire machine. Now, I have one of two errors: Immediate BSOD with BEDaisy.sys throwing the error "Page Fault in Nonpaged Area". If the game manages to get past the splash screen, when I hit the character select menu it crashes with a Marmot error. Marmot Error states that the game files are corrupted, but the game has been freshly reinstalled and the disk is in perfect health (according to the hard drive manufacturer's tools). Other people have referred to BattlEye as being the culprit for Marmot errors (https://www.reddit.com/r/DestinyTheGame/comments/q6ylqu/marmot_error/) I'll keep trying things, but I would appreciate any suggestions.
English
#Help #Errorcodes

文章張貼語言:

 

以禮待人。發佈文章前請花點時間查看我們的行為準則 取消 編輯 創立火力戰隊 文章

  • From the Darktide FAQ regarding Oodle errors (https://support.fatshark.se/hc/en-us/articles/360021425793--PC-How-to-Resolve-Data-Corruption-Errors), I found a small thing that piqued my interest (as that game had been constantly crashing with decompression errors despite the game files being verified) "Intel i9 13900k/i7 13700k: Underclock 'Performance Core' Speed It has been noted that players with the Intel i9 13900k/i7 13700k CPU are prone to these crashes. Players have been able to work around this by underclocking the 'Performance Core' speed using Intel XTU, from x55 to x53." I have an i7 13700ku processor. Not that my CPU was overclocked, but I further underclocked it to x49 instead of x53, and it solved both the marmot and oodle errors, as far as I can tell.

    文章張貼語言:

     

    以禮待人。發佈文章前請花點時間查看我們的行為準則 取消 編輯 創立火力戰隊 文章

  • Came back about a week later (4/2/2024). No issues with any other games I'm running, nprotect and battleye both had updates since last time I ran D2. Immediate Marmot error upon entering into a strike. File integrity is fine - all 3016 files validated with no errors found. Still a collision between anticheats, and I don't know enough about either nProtect Gameguard or BattlEye to find a solution.

    文章張貼語言:

     

    以禮待人。發佈文章前請花點時間查看我們的行為準則 取消 編輯 創立火力戰隊 文章

    4 回覆
    • Double check your RAM; that looks a lot like a RAM stick has gone bad. Check your PSU too, it could be not performing optimally.

      文章張貼語言:

       

      以禮待人。發佈文章前請花點時間查看我們的行為準則 取消 編輯 創立火力戰隊 文章

      12 回覆
      你無權檢閱此內容
      ;
      preload icon
      preload icon
      preload icon