Ce n’est pas ce que vous cherchez ?

Nouvelle publication
Bungie Answered

KERNEL_MODE_HEAP_CORRUPTION BSOD Crash

  • Bungie Account Name - AZNBeefcake#4522
  • Platform - Steam
  • Description of Issue - Since the most recent update I have been crashing every time I boot up the game. I tried verifying the game files, reinstalling Battle Eye, reinstalling marathon, reinstalling graphics drivers and doing a memtest and sfc /scannow.  I don't have this issue with any other games.
  • Rough Date and Time of issue - Started today. Last played on Monday 5/18 before the update.
  • Repro steps - Just booting the game on steam. 
0

Commentaires

4 commentaires
  • Commentaire officiel

    Hello there,
    Thanks for the report.

    We are aware of similar situations where the game on startup on Steam can cause these kinds of issues.
    We are currently looking into these situations and are focusing on bettering performance.

    I understand the frustration here, especially since you’ve already worked through the usual steps like verifying files, reinstalling BattlEye, reinstalling the game, reinstalling graphics drivers, and running system checks.

    If possible, please also include a DxDiag with the report. 

    Thank you for your patience.

  • Lol thank you for the AI response. Anyway, here is the dxdiag details not sure how much you need:

     

    System Information
    ------------------
          Time of this report: 5/21/2026, 18:28:16
                 Machine name: DESKTOP-9AKH99E
                   Machine Id: {8C4904B6-93E0-4AAE-9AED-8FE299E68673}
             Operating System: Windows 10 Home 64-bit (10.0, Build 19045) (19041.vb_release.191206-1406)
                     Language: English (Regional Setting: English)
          System Manufacturer: Gigabyte Technology Co., Ltd.
                 System Model: Z390 AORUS ELITE
                         BIOS: F12c (type: UEFI)
                    Processor: Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz (8 CPUs), ~3.6GHz
                       Memory: 16384MB RAM
          Available OS Memory: 16300MB RAM
                    Page File: 6383MB used, 10429MB available
                  Windows Dir: C:\WINDOWS
              DirectX Version: DirectX 12
          DX Setup Parameters: Not found
             User DPI Setting: 96 DPI (100 percent)
           System DPI Setting: 96 DPI (100 percent)
              DWM DPI Scaling: Disabled
                     Miracast: Available, no HDCP
    Microsoft Graphics Hybrid: Not Supported
     DirectX Database Version: 1.0.8
               DxDiag Version: 10.00.19041.5794 64bit Unicode
      DxDiag Previously: Crashed in Direct3D (stage 2). Re-running DxDiag with "dontskip" command line parameter or choosing not to bypass information gathering when prompted might result in DxDiag successfully obtaining this information

     

    ---------------
    Display Devices
    ---------------
               Card name: NVIDIA GeForce RTX 4080 SUPER
            Manufacturer: NVIDIA
               Chip type: NVIDIA GeForce RTX 4080 SUPER
                DAC type: Integrated RAMDAC
             Device Type: Full Device (POST)
              Device Key: Enum\PCI\VEN_10DE&DEV_2702&SUBSYS_89621043&REV_A1
           Device Status: 0180200A [DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER] 
     Device Problem Code: No Problem
     Driver Problem Code: Unknown
          Display Memory: Unknown
        Dedicated Memory: n/a
           Shared Memory: n/a
            Current Mode: 2560 x 1440 (32 bit) (144Hz)
             HDR Support: Not Supported
        Display Topology: Extend
     Display Color Space: Unknown
         Color Primaries: Unknown
       Display Luminance: Unknown
            Monitor Name: Generic PnP Monitor
           Monitor Model: 
              Monitor Id: 
             Native Mode: 
             Output Type: 
    Monitor Capabilities: HDR Not Supported
    Display Pixel Format: DISPLAYCONFIG_PIXELFORMAT_32BPP
          Advanced Color: Not Supported
             Driver Name: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_b7cca8360c0d57e9\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_b7cca8360c0d57e9\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_b7cca8360c0d57e9\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_b7cca8360c0d57e9\nvldumdx.dll
     Driver File Version: Unknown (Unknown)
          Driver Version: 32.0.15.9649
             DDI Version: Unknown
          Feature Levels: Unknown
            Driver Model: WDDM 2.7
     Hardware Scheduling: Supported:True Enabled:True 
     Graphics Preemption: Pixel
      Compute Preemption: Dispatch
                Miracast: Not Supported
          Detachable GPU: No
     Hybrid Graphics GPU: Not Supported
          Power P-states: Not Supported
          Virtualization: Paravirtualization 
              Block List: No Blocks
      Catalog Attributes: Universal:False Declarative:True 
       Driver Attributes: Final Retail
        Driver Date/Size: Unknown, 0 bytes
             WHQL Logo'd: n/a
         WHQL Date Stamp: n/a
       Device Identifier: Unknown
               Vendor ID: 0x10DE
               Device ID: 0x2702
               SubSys ID: 0x89621043
             Revision ID: 0x00A1
      Driver Strong Name: oem36.inf:0f066de3a1b855c6:Section030:32.0.15.9649:pci\ven_10de&dev_2702
          Rank Of Driver: 00CF2001
             Video Accel: Unknown
             DXVA2 Modes: Unknown
          Deinterlace Caps: n/a
            D3D9 Overlay: Unknown
                 DXVA-HD: Unknown
            DDraw Status: Disabled
              D3D Status: Not Available
              AGP Status: Not Available
           MPO MaxPlanes: Unknown
                MPO Caps: Unknown
             MPO Stretch: Unknown
         MPO Media Hints: Unknown
             MPO Formats: Unknown
        PanelFitter Caps: Unknown
     PanelFitter Stretch: Unknown

               Card name: NVIDIA GeForce RTX 4080 SUPER
            Manufacturer: NVIDIA
               Chip type: NVIDIA GeForce RTX 4080 SUPER
                DAC type: Integrated RAMDAC
             Device Type: Full Device (POST)
              Device Key: Enum\PCI\VEN_10DE&DEV_2702&SUBSYS_89621043&REV_A1
           Device Status: 0180200A [DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER] 
     Device Problem Code: No Problem
     Driver Problem Code: Unknown
          Display Memory: Unknown
        Dedicated Memory: n/a
           Shared Memory: n/a
            Current Mode: 1920 x 1080 (32 bit) (60Hz)
             HDR Support: Not Supported
        Display Topology: Extend
     Display Color Space: Unknown
         Color Primaries: Unknown
       Display Luminance: Unknown
            Monitor Name: Generic PnP Monitor
           Monitor Model: 
              Monitor Id: 
             Native Mode: 
             Output Type: 
    Monitor Capabilities: HDR Not Supported
    Display Pixel Format: DISPLAYCONFIG_PIXELFORMAT_32BPP
          Advanced Color: Not Supported
             Driver Name: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_b7cca8360c0d57e9\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_b7cca8360c0d57e9\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_b7cca8360c0d57e9\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_b7cca8360c0d57e9\nvldumdx.dll
     Driver File Version: Unknown (Unknown)
          Driver Version: 32.0.15.9649
             DDI Version: Unknown
          Feature Levels: Unknown
            Driver Model: WDDM 2.7
     Hardware Scheduling: Supported:True Enabled:True 
     Graphics Preemption: Pixel
      Compute Preemption: Dispatch
                Miracast: Not Supported
          Detachable GPU: No
     Hybrid Graphics GPU: Not Supported
          Power P-states: Not Supported
          Virtualization: Paravirtualization 
              Block List: No Blocks
      Catalog Attributes: Universal:False Declarative:True 
       Driver Attributes: Final Retail
        Driver Date/Size: Unknown, 0 bytes
             WHQL Logo'd: n/a
         WHQL Date Stamp: n/a
       Device Identifier: Unknown
               Vendor ID: 0x10DE
               Device ID: 0x2702
               SubSys ID: 0x89621043
             Revision ID: 0x00A1
      Driver Strong Name: oem36.inf:0f066de3a1b855c6:Section030:32.0.15.9649:pci\ven_10de&dev_2702
          Rank Of Driver: 00CF2001
             Video Accel: Unknown
             DXVA2 Modes: Unknown
          Deinterlace Caps: n/a
            D3D9 Overlay: Unknown
                 DXVA-HD: Unknown
            DDraw Status: Disabled
              D3D Status: Not Available
              AGP Status: Not Available
           MPO MaxPlanes: Unknown
                MPO Caps: Unknown
             MPO Stretch: Unknown
         MPO Media Hints: Unknown
             MPO Formats: Unknown
        PanelFitter Caps: Unknown
     PanelFitter Stretch: Unknown

    0
  • I also ran the dmp file from the blue screen through WinDbg and it definitely seems to be related to Battleye. Here is a portion of it.

    KERNEL_MODE_HEAP_CORRUPTION (13a)
    The kernel mode heap manager has detected corruption in a heap.
    Arguments:
    Arg1: 0000000000000011, The heap detected invalid internal state during the current operation. This can be the result of a double-free or heap corruption.
    Arg2: ffff928879802100, Address of the heap that reported the corruption
    Arg3: ffff92888e753b40, Address at which the corruption was detected
    Arg4: 0000000000000000
    
    Debugging Details:
    ------------------
    
    *** WARNING: Unable to verify timestamp for BEDaisy.sys
    fffff80743afb390: Unable to get MiVisibleState
    
    KEY_VALUES_STRING: 1
    
        Key  : Analysis.CPU.mSec
        Value: 1187
    
        Key  : Analysis.Elapsed.mSec
        Value: 1528
    
        Key  : Analysis.IO.Other.Mb
        Value: 0
    
        Key  : Analysis.IO.Read.Mb
        Value: 1
    
        Key  : Analysis.IO.Write.Mb
        Value: 0
    
        Key  : Analysis.Init.CPU.mSec
        Value: 500
    
        Key  : Analysis.Init.Elapsed.mSec
        Value: 5831
    
        Key  : Analysis.Memory.CommitPeak.Mb
        Value: 74
    
        Key  : Analysis.Version.DbgEng
        Value: 10.0.29547.1002
    
        Key  : Analysis.Version.Description
        Value: 10.2602.27.2 amd64fre
    
        Key  : Analysis.Version.Ext
        Value: 1.2602.27.2
    
        Key  : Bugcheck.Code.LegacyAPI
        Value: 0x13a
    
        Key  : Bugcheck.Code.TargetModel
        Value: 0x13a
    
        Key  : Dump.Attributes.AsUlong
        Value: 0x8
    
        Key  : Dump.Attributes.KernelGeneratedTriageDump
        Value: 1
    
        Key  : Failure.Bucket
        Value: 0x13a_11_BE___BEDaisy!unknown_function
    
        Key  : Failure.Hash
        Value: {6a85b8ad-f8a7-b71c-b9d1-e9d62252af2e}
    
        Key  : WER.System.BIOSRevision
        Value: 5.13.0.0
    
    
    BUGCHECK_CODE:  13a
    
    BUGCHECK_P1: 11
    
    BUGCHECK_P2: ffff928879802100
    
    BUGCHECK_P3: ffff92888e753b40
    
    BUGCHECK_P4: 0
    
    FILE_IN_CAB:  052026-7781-01.dmp
    
    DUMP_FILE_ATTRIBUTES: 0x8
      Kernel Generated Triage Dump
    
    FAULTING_THREAD:  ffff9288876e0080
    
    POOL_ADDRESS: fffff80743afb390: Unable to get MiVisibleState
     ffff92888e753b40 
    
    FREED_POOL_TAG:  BE__
    
    BLACKBOXBSD: 1 (!blackboxbsd)
    
    
    BLACKBOXNTFS: 1 (!blackboxntfs)
    
    
    BLACKBOXPNP: 1 (!blackboxpnp)
    
    
    BLACKBOXWINLOGON: 1 (!blackboxwinlogon) (!blackboxwinlogonnotify)
    
    
    CUSTOMER_CRASH_COUNT:  1
    
    PROCESS_NAME:  Marathon.exe
    
    STACK_TEXT:  
    fffffe85`88307468 fffff807`43393854     : 00000000`0000013a 00000000`00000011 ffff9288`79802100 ffff9288`8e753b40 : nt!KeBugCheckEx
    fffffe85`88307470 fffff807`433938b4     : 00000000`00000011 00000000`00000000 ffff9288`79802100 fffff807`4314217d : nt!RtlpHeapHandleError+0x40
    fffffe85`883074b0 fffff807`433934e1     : 00000000`00000030 ffff9288`8e753000 ffff9288`7b599980 01900030`79802000 : nt!RtlpHpHeapHandleError+0x58
    fffffe85`883074e0 fffff807`43277f9a     : 00000000`00000000 00000000`50737050 00000000`00000030 00000000`00000c75 : nt!RtlpLogHeapFailure+0x45
    fffffe85`88307510 fffff807`43142255     : ffff9288`79802340 ffffe306`49e001ff 00000000`00000000 ffffe306`00000000 : nt!RtlpHpLfhSubsegmentFreeBlock+0x1711fa
    fffffe85`883075c0 fffff807`4314217d     : ffff9288`79802000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!RtlpHpSegFree+0x65
    fffffe85`88307600 fffff807`43141ce9     : ffff9288`8c4a6080 ffff9288`79802000 ffff9288`8e753b50 fffff807`43065cf0 : nt!RtlpHpFreeHeap+0x8d
    fffffe85`88307650 fffff807`437b4019     : 00000000`00000000 ffff9288`8c4a6080 01000000`00100000 00000000`00000000 : nt!ExFreeHeapPool+0x239
    fffffe85`88307710 fffff807`c7de1927     : fffff807`c769c1e0 fffff807`00000000 00000000`00000000 00000000`00000000 : nt!ExFreePool+0x9
    fffffe85`88307740 fffff807`c769c1e0     : fffff807`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : BEDaisy+0x761927
    fffffe85`88307748 fffff807`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`0000000a : BEDaisy+0x1c1e0
    fffffe85`88307750 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`0000000a fffff807`43aec5c8 : 0xfffff807`00000000
    
    
    SYMBOL_NAME:  BEDaisy+761927
    
    MODULE_NAME: BEDaisy
    
    IMAGE_NAME:  BEDaisy.sys
    
    STACK_COMMAND: .process /r /p 0xffff92888c4a6080; .thread /r /p 0xffff9288876e0080 ; kb
    
    BUCKET_ID_FUNC_OFFSET:  761927
    
    FAILURE_BUCKET_ID:  0x13a_11_BE___BEDaisy!unknown_function
    
    OSPLATFORM_TYPE:  x64
    
    OSNAME:  Windows 10
    
    FAILURE_ID_HASH:  {6a85b8ad-f8a7-b71c-b9d1-e9d62252af2e}
    
    Followup:     MachineOwner
    ---------

     

    0
  • Okay sorry for the triple post, but I ended up fixing this (for now) by doing a system restore point from earlier this week. Clearly something went wrong with either my system files or registry, or drivers.

    0

Vous devez vous connecter pour laisser un commentaire.