1. Marathon Help
  2. Community
  3. Bug Report: Systems, Settings, & Services

Didn't find what you were looking for?

New post
Bungie Answered

Repeated crashes (both DRIVER_IRQL full-system restarts and game-to-desktop) since Update 1.1.5

Avatar
audiovisualboy

Hi Support Team,

I'm reporting a mix of crashes — some full system restarts, some game crashes to desktop/Steam — that started immediately after Update 1.1.5 and have recurred multiple times since, including one that cost me a fully-geared Cryo Archive extraction run (my first ever, sadly).

System stability before vs. after the patch:
I've been playing Marathon for ~170 hours with zero crashes or performance issues of any kind. This problem began the night Update 1.1.5 deployed and has recurred consistently since — nothing else changed on my end. This is a new problem, not a pre-existing one.

Crash details:

  • At least 4 confirmed full-system restarts with bugcheck: 0x000000D1 (DRIVER_IRQL_NOT_LESS_OR_EQUAL), consistently pointing to Wdf01000.sys
  • Additional crashes that dropped straight to desktop/Steam rather than restarting the whole system
  • Occurrences of the full-restart crashes: 2026-07-21 11:08 PM, 2026-07-23 2:33 AM, 2026-07-24 6:15 AM, 2026-07-25 2:36 AM

What I was doing:
All crashes occurred during active combat encounters. This has happened across multiple zones — Cryo Archive, Dire Marsh, and Outpost — not isolated to one map. Most recently, mid looting in Cryo Archive with a great run in progress (gold-tier gear, lobby wiped).

Error codes/messages:
No in-game error code, but Windows Reliability Monitor and memory dump analysis confirm the bugcheck above for the full-restart crashes. I'm also noticing Marathon flags my AMD graphics driver as having "known issues" on every single launch.

Did it crash to desktop?
Both — some crashes were full system restarts, others dropped to desktop/Steam without restarting the whole machine.

Troubleshooting already completed:

  • Verified game file integrity
  • Reinstalled BattlEye
  • Full Marathon game uninstall, reboot, reinstall
  • Updated audio interface (Behringer UMC 204HD) drivers — did not resolve the issue
  • AMD graphics drivers confirmed current per Apple's Boot Camp driver channel

System specs:
16" MacBook Pro (2019), Boot Camp, AMD Radeon Pro 5300M, Windows 10

Possible pattern with other reports:
I noticed another report in this board ("Cryo crashing versus gunfight" by Land__Lord) describing a similar crash pattern during combat, but on a completely different AMD GPU (RX 7800 XT). Combined with the fact that I'm seeing this across multiple zones rather than one specific map, this may suggest a broader AMD driver interaction introduced by 1.1.5 rather than an isolated hardware/config or single-zone issue.

Lost loot:
I don't have video of the crash itself, but I do have a screenshot of the loadout I lost, and the two other players in my extraction (who did make it out) could potentially corroborate that I crashed. Happy to provide either if useful.

Thanks for looking into this — happy to provide any additional logs or details you need.

Best,

audiovisualboy#9008

0

Comments

2 comments
Sort by Date Votes
  • Official comment
    Avatar
    Bungie Support
    Marathon Support

    Hi there,

    Thank you for reaching out.

    I'm sorry to hear that you are having issues with the game’s stability when trying to play the game.

    To start out, please ensure that all of your drivers, windows, and your BIOS are all fully up-to-date. 

    If you still run into the same issue despite this, can you provide us with a copy of your DxDiag? You can copy and paste it over on PasteBin and provide us with the link.

  • Avatar
    audiovisualboy

    Hi, thanks for the response. Quick context: I played Marathon for ~150 hours with zero crashes or stability issues prior to Update 1.1.5 — this problem began immediately when that patch deployed and has recurred since.

    This is also a Boot Camp-partitioned MacBook Pro, so there's no traditional BIOS to update — Apple handles firmware through macOS, which is current. Windows and AMD drivers are both up to date (I did a full clean AMD driver reinstall via DDU as part of my own troubleshooting).

    Pastebin DxDiag Link: DxDiag - Pastebin.com

    For reference, my original post has the specific bugcheck details (0xD1, Wdf01000.sys) and crash timestamps — you'll also see multiple matching BlueScreen entries logged directly in the DxDiag's Windows Error Reporting section.

    0

Please sign in to leave a comment.