Marathon Crashes PC when external audio interface is turned on
am experiencing reproducible full-system BSODs when playing Marathon with a Line 6 POD HD Pro X USB audio interface powered on.
The POD HD Pro X works normally with Windows and other games. I have tested Rainbow Six Siege with the POD powered on and it works perfectly without crashing. Marathon is the only game I have found that consistently triggers the BSOD.
Reproduction:
- Connect the Line 6 POD HD Pro X to the PC via USB.
- Leave the POD powered off.
- Launch Marathon and play normally. The game works without crashing.
- Power on the POD HD Pro X while Marathon is running.
- The PC eventually crashes with a BSOD.
- If the POD remains powered off, Marathon works normally.
I have also tested the following:
- POD powered on while using a different Windows audio device: Marathon still crashes.
- Marathon is configured to use a different audio device rather than the POD: still crashes.
- POD connected but powered off: Marathon works normally.
- POD powered on: Marathon crashes.
- Tested multiple USB ports: no difference.
- Updated the POD HD Pro X to the latest available firmware: no change.
- Updated the POD HD Pro X USB/audio drivers: no change.
- POD works normally in Windows and other games.
- Rainbow Six Siege works normally with the POD powered on.
This makes me suspect a compatibility issue involving Marathon, BattlEye, and/or the Line 6 POD HD Pro X USB driver. The fact that Marathon crashes even when it is using a completely different audio device suggests that simply having the POD's USB audio interface active may be enough to trigger the problem.
I have experienced two different BSODs:
Crash 1: 072226-8453-01.dmp
Bugcheck: 0x10D WDF_VIOLATION
Failure bucket:
0x10D_4_ucx01000!Urb_LegacyTransferUrbCompletion
The stack includes:
ucx01000.sys
USBXHCI.sys
USBXHCI!Isoch_Transfer_CompleteCancelable
USBXHCI!Isoch_CompleteStaleTransfers
USBXHCI!Isoch_ProcessTransferEventWithED1
This appears to involve the Windows USB stack while processing an isochronous USB transfer.
Crash 2: 072226-8718-01.dmp
Bugcheck: 0x139 KERNEL_SECURITY_CHECK_FAILURE
Parameter 1: 3
Failure:
CORRUPT_LIST_ENTRY
Failure bucket:
0x139_3_CORRUPT_LIST_ENTRY_BEDaisy!unknown_function
The dump identifies:
BEDaisy.sys
as the module on the stack at the point where the corruption was detected.
I understand that BEDaisy.sys may not necessarily be the original cause and could instead be where previously corrupted kernel state was detected.
I can provide both minidump files if needed.
The most reliable reproduction appears to be:
Marathon running + POD HD Pro X powered off = works
Marathon running + POD HD Pro X powered on = BSOD
I would appreciate it if the team could investigate a possible Marathon/BattlEye interaction with the Line 6 POD HD Pro X USB audio driver or USB audio subsystem.
Comments
Hi there,
Thank you for reaching out.
I'm sorry to hear that you are having issues with the game’s stability.
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. We would also like to see your Event Viewer logs from the crash as well. You can either paste that here or use PasteBin for both.
Here is my PasteBin for my DxDiag: https://pastebin.com/XG4PqMPL
Here is my PasteBin for my Event Viewer log from the most recent crash: https://pastebin.com/Da567Lvs
Hello there,
Thank you for the DxDiag and Event Viewer log.
We have taken note of your report and will investigate this on our end.
Thank you again for taking the time to alert us to this and for sharing such a detailed report.
Please sign in to leave a comment.