I've tried everything: I've updated the BIOS, the CPU and GPU drivers, all the drivers that were out of date, etc., and it still doesn't work. I hope a solution is found soon, as I've never had anything like this happen to me before... The worst part is that it started after Tuesday's reboot, because yesterday I was playing at 3:00 a.m. without any problems, and when I went to play at 8:00 p.m., it wouldn't let me. Here is the DXDIAG data https://pastebin.com/zCb3KiFK

Why did you redact all that info? It's totally useless this way. Do you really want help or not?

Obviously, otherwise I wouldn't be on the forum asking for help. I simply responded to what Bungie support asked me to do, but if you have more information about what to do, please let me know.

Just link the Dxdiag report as it is created, without redaction (if you are really worried by your personal info, you can redact the computer's name, that's the only ever so slight info leak that you can be worried about).

Here is the complete dxdiag, I just deleted the computer name data. I hope this helps to see what the hell is going on with the game on my PC, because all the other games work perfectly. https://pastebin.com/XK6tw06g

Bug check 0x139: https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x139--kernel-security-check-failure Paramater 1 of 0x139: 3 = [quote]A LIST_ENTRY is corrupted (for example, a double remove). For more information, see the following Cause section.[/quote] Cause section: [quote]LIST_ENTRY corruption can be difficult to track down. This bug check indicates that an inconsistency was introduced into a doubly linked list (detected when an individual list entry element is added to or removed from the list). Unfortunately, the inconsistency is not necessarily detected at the time when the corruption occurred, so some detective work may be necessary to identify the root cause. Common causes of list entry corruption include: A driver corrupted a kernel synchronization object, such as a KEVENT (for example double initializing a KEVENT while a thread was still waiting on that same KEVENT, or allowing a stack-based KEVENT to go out of scope while another thread was using that KEVENT). This type of bug check typically occurs in nt!Ke* or nt!Ki* code. It can happen when a thread finishes waiting on a synchronization object or when code attempts to put a synchronization object in the signaled state. Usually, the synchronization object being signaled is the one that's corrupted. Sometimes, Driver Verifier with special pool can help track down the culprit (if the corrupted synchronization object is in a pool block that's already freed). A driver corrupted a periodic KTIMER. This type of bug check typically occurs in nt!Ke* or nt!Ki* code and involves signaling a timer, or inserting or removing a timer from a timer table. The timer being manipulated may be the corrupted one, but it might be necessary to inspect the timer table with !timer (or manually walking the timer list links) to identify which timer is corrupted. Sometimes, Driver Verifier with special pool can help track down the culprit (if the corrupted KTIMER is in a pool block that's already freed). A driver mismanaged an internal LIST_ENTRY-style linked list. A typical example would be calling RemoveEntryList twice on the same list entry without reinserting the list entry between the two RemoveEntryList calls. Other variations are possible, such as double inserting an entry into the same list. A driver freed a data structure that contains a LIST_ENTRY without removing the data structure from its corresponding list, causing corruption to be detected later when the list is examined after reusing the old pool block. A driver used a LIST_ENTRY-style list in a concurrent fashion without proper synchronization, resulting in a torn update to the list. In most cases, you can identify the corrupted data structure by walking the linked list both forward and backwards (the dl and dlb commands are useful for this purpose) and comparing the results. Where the list is inconsistent between a forward and backward walk is typically the location of the corruption. Since a linked list update operation can modify the list links of a neighboring element, you should look at the neighbors of a corrupted list entry closely, as they may be the underlying culprit. Because many system components internally utilize LIST_ENTRY lists, various types of resource mismanagement by a driver using system APIs might cause linked list corruption in a system-managed linked list.[/quote]

I have been searching for information about everything related to the error that appears, I have tried making all the changes, reinstalling, deleting and restoring files, and nothing works. Maybe I should do a complete reinstallation of Windows, but I don't want to lose everything I have installed and saved when at 3:00 a.m. I was playing quietly and at 8:00 p.m. on the same day the problems started.

There is also the possibility of RAM corruption; check your RAM too. PS you can also give the Epic version a try, and see whether it behaves the same or not.

Yes, I also ran a RAM test and it didn't show any errors. I had thought about installing it from Epic Games as well, or even from Windows, but aren't the versions the same? I mean, if it crashes on Steam, shouldn't it also crash on Epic Games or Windows? Besides, I have the DLCs on Steam, so I would lose them, right?

The goal is to see whether the Epic version really will crash the same way. You don't need to link your current Bungie profile to the Epic account you'll use if you don't want to, and yes, you just need to run the standard, free base game (no DLC needed, those will stay with your Steam account anyway).

I installed the game on Epic Games and the same thing keeps happening. It seems to start up, but when the game install Battleeye, the game crashes and my PC restarts. It looks like it's a Battleeye incompatibility issue. I don't know if they added an update with Tuesday's server restart, but I'm 200% sure it's a problem with Battleeye's anti-cheat and some update or code they added. Apart from the fact that I've been reading about other people experiencing the same thing... we'll have to wait for a hotfix to see if it gets fixed.

So it's something tied to your computer/OS installation. By any chance, does it have LED lights? Do you use a software or HW controller for them?

This is today's dxdiag at 21:10 GMT +1 (Madrid). I have the game installed on a 1TB M.2 drive. I tried installing it on the other two hard drives I have, an HDD and an SSD, and the same thing always happens. Nothing changes at all. The BattleEye installation starts, and when it finishes, I get a blue screen and the PC restarts. Maybe it's time to look at what's going on with BattleEye and stop focusing on what's happening to my PC, because there are other people having the same problem with the same result. I find it too strange that since Tuesday, several people have had the same problem... something has happened with Bungie or BattleEye that is blocking and resetting our PCs. Because I have other games that use BattleEye and absolutely nothing happens, and I can play normally. https://pastebin.com/v6jLcwZt

Hey! I have continued investigating the possible problem I am having with my PC crashing, and I may have found a solution. Looking through the Steam forums, I found someone who provided a solution to another problem, but it helped me find the file that was causing the game to crash when I started it. Pressing Win + R and typing “perfmon /rel” opens the reliability monitor, and on the days when I had forced reboots, I always got the same critical error “ps-service_launcher.exe” (streaming software for my Pico virtual reality glasses that I no longer use). It was always the same error, even on days when I simply turned on the computer to see if the problem had magically been solved. Perhaps the problem is still there, but I'm going to reinstall the game after uninstalling and deleting all the folders related to that software and see if I'm lucky this time and it stops crashing so I can play again. If not, at least I will have removed one of the problems that could cause my computer to restart.

Hi again, Just wanted to follow up on our earlier conversation and share what I’ve found after some more testing. What’s happening: Destiny 2 crashes every time right when BattlEye starts, causing a BSOD with: KERNEL_SECURITY_CHECK_FAILURE (0x139) System (for reference): CPU: Ryzen 9 5900X Motherboard: ASUS TUF Gaming B550M-Plus (BIOS 3621) GPU: NVIDIA RTX 3080 (10 GB) OS: Windows 11 25H2 (build 26200.7623) What I’ve done so far: Turned off automatic reboot so I could actually see the BSOD Collected crash dumps from multiple attempts Analyzed two different minidumps using WinDbg Preview Both dumps show the exact same result: IMAGE_NAME: BEDaisy.sys FAILURE_BUCKET_ID: 0x139_3_CORRUPT_LIST_ENTRY_BEDaisy Both crashes hit the same BEDaisy.sys offset, which looks like a consistent FAST_FAIL_CORRUPT_LIST_ENTRY Removed old leftover drivers (including some old VR/PICO stuff) Disabled virtualization features (SVM / IOMMU) Disabled VBS / Memory Integrity Double-checked Secure Boot and fTPM Tested RAM at stock settings (no XMP/DOCP) What I’m seeing: Everything else on the system runs fine The crash only happens when BattlEye loads Doesn’t look like random hardware or memory instability Takeaway: Given that the crash is identical across multiple dumps and setups, this really looks like a BattlEye (BEDaisy.sys) kernel issue rather than something wrong with the system itself. I hope this helps clarify the problem I am having and that you can provide a solution. In addition, I am leaving a pastebin of the minidumps analyzed so that you can better observe the results. https://pastebin.com/nNaqkwHs