Launching causes PC to crash
- Updated to include the provided template -
Bungie Account Name - Cent#0405
Platform - Steam
Description of Issue - When trying to launch the game, PC immediately crashes with a kernel_security_check_failure 0x139
I've done multiple things such as rolling back to a more stable nvidia driver (including a clean install with DDU) but still running into issues. Done sanity checks and confirmed other games and hardware are working just fine
OS: Win11
Card: 4080 Super
Ram: 32g
CPU: intel i9-14900k
1
Commentaires
Similar thing happens to me. For me, it only happens when I have my Focusrite Scarlett 18i20 audio interface (used for my microphone) plugged in via USB in the back of my PC.
If I don't have it turned on, the Server Slam will launch perfectly fine. But if it is on before starting, or is turned on after it successfully starts, the result is my PC crashing, with the error message "KERNEL_SECURITY_CHECK_FAILURE (0x139)" appearing at the bottom of my screen.
No way this is the issue - I am using an 18i20 too. That is insane thank you lol. Now i can play but gotta figure out audio
So i found a work around that will still let you use the interface. Go to Device Manager then to Sound, video and game controllers and disable the MIDI driver on your interface. Restart your PC and try to launch it again thats what fixed it for me.
Yup - I was able to launch with the device now while disabling midi. Man have always loved focusrite for audio flow but it sure does like to make something difficult in the weirdest ways.
I noticed digging around too (at least mine) was defaulting to an MSFT driver and not the actual focusrite driver so that could be a reason for the conflict since it's running so close to the kernel. Will investigate later but just happen to play finally after troubleshooting all morning. Thanks for the finds from both of ya
Thanks for the workaround Travis! I'm glad we were able to find this today. Hopefully we won't have to worry about a workaround in the main release.
I created a Bungie user account so I could pop in this thread and add some info. There is absolutely NO doubt you guys have figured it out. I also use a Focusrite 18i20 and never imagined that would be the issue with all my recent gaming problems. Marathon Server Slam hard resets my PC as soon as I launch it (after a super quick "Your device has run into a problem" screen). Crashed it over and over with at least 4 attempts. I turned off the audio interface and switched to my Bluetooth gaming headset (which I sometimes use because the game mic is built into it). Boom! Instant success. Disabling MIDI did not fix the problem for me, but I'm gonna tinker around with that some more.
This actually gets a little deeper for me. I will get similar behavior from playing Fortnite after the FIRST launch attempt. I could never figure that one out. System would hard reset on first launch, then work fine after that. 24 hours later? Same thing would happen after first launch. Super &#%ing weird! I was playing that with my stepdaughter and she quit playing, so I did as well. I didn't think about it anymore. Never had a single problem with tons of other games (and I play a wide range). However, the same thing started happening with Arc Raiders. I picked the game up late (last month) and have been playing a lot. About 50% of the time after the first launch of the day - BOOM - hard reset after the map loads. After that? Game works fine. Never had another reset for the rest of the evening after that. I have driven myself INSANE trying to figure this out. I've cleaned the PC (my own custom build) and even switched out power supply cables (as this feels like a power supply issue). No change. Just fired up Arc with the Focusrite turned off and using gaming headphones.....and no lockup. This is crazy. I was about to order a new Power Supply.
Long story short, this has gotta be a Focusrite issue. I'm going to check if there are driver updates available, but I doubt that will be the answer. It would probably help all of us in this thread to message and let them know about our experiences. There's no way this is some random thing, and it has to be an issue with the 18i20 current drivers. I'll bookmark this thread and add any info I gain from tinkering. Thanks for the post. You may have just solved a huge problem for me.
Vous devez vous connecter pour laisser un commentaire.