Didn't find what you were looking for?

New post
Bungie Answered

immediate broccoli error code on startup on AMD hardware. been going on for almost two months with no fix

anyone else with an amd gpu (7800xt 16gb, ryzen 9 5900x, 32gb ram, win11) getting immediate broccoli error on startup. this has been happening to me since the launch of season 2. and i genuinely have no idea what to even do at this point, i have tried literally everything. i've updated drivers, i've rolled them back multiple times, i've updated bios, i've disabled firewall, i've disabled all overlays and i still cant get this game to cooperate with me. extremely frustrating. And bungie before you give me the same automated response saying i need to ensure everything is up to date i have tried that multiple times already. your game just will not cooperate with my hardware, and im not the only person with this issue. the fact that this hasnt been listed as a known problem is absolutely absurd to me. please fix this shit. 

0

Comments

7 comments
  • Official comment

    Hi there,

    Thank you for reaching out.

    I'm sorry to hear that you are having issues launching the game.

    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.

  • 0
  • i can also provide the text file used to generate the pastebin link if necessary. hope this helps.

    0
  • Hi again,

    Based on your DxDiag, your PC appears to be running a Windows Insider / pre-release version of Windows 11 rather than a standard retail version of Windows. Marathon is only supported on retail Windows 10 or 11 builds, so this may be contributing to the BROCCOLI crashes you are seeing.

    Since you have already tried updating and rolling back your graphics drivers, the next steps we recommend are:

    • Move off of the Windows Insider build and update to a retail version of Windows 11.
    • Fully restart your PC and try launching the game with unnecessary background apps closed.
    • Run sfc / scannow in Windows to check for corrupted system files.
    • Send us Event Viewer error logs from the time of the crash, especially from Windows Logs > System and Windows Logs > Application. You can share this as a screenshot or use PasteBin again to share it.
    0
  • hello again, i confirmed via running winver that my os has no indication regarding it being a pre-release / insider version of windows. i did however discover corrupted files by running sfc /scannow. im also doing another fresh install of marathon to see if i can get it to work this way. if not, i will send event viewer error logs. ill respond in this thread again momentarily. 

    0
  • Faulting application name: Marathon.exe, version: 0.0.0.0, time stamp: 0x00000000
    Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
    Exception code: 0xc0000409
    Fault offset: 0x00007ff9fc05527e
    Faulting process id: 0x6860
    Faulting application start time: 0x1DD2373D659824E
    Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\Marathon\Marathon.exe
    Faulting module path: unknown
    Report Id: ddfba22c-03e2-469c-af3c-de5abf35e2d4
    Faulting package full name: 
    Faulting package-relative application ID: 

    0
  • this is what shows up in event viewer once i go to the specific error relating to the crash.

    0

Please sign in to leave a comment.