Event ID 153 Causing PC Freeze While Playing Tarkov

Event ID 153 in Windows represents a critical storage stack failure where the operating system loses communication with a disk device, causing the entire system to freeze for approximately 40 seconds while it attempts recovery. This specific behavior is frequently observed by players of *Escape from Tarkov* due to the game’s intense and sustained read/write operations on storage drives, which can trigger timeouts in the storage controller or exhaust I/O queues. The solution involves adjusting power management settings for SATA links, disabling aggressive sleep states for NVMe drives, and ensuring that storage drivers are up to date to prevent these transient connectivity drops during high-load scenarios.

Understanding Event ID 153 and System Freezes

When Windows logs Event ID 153, it indicates that the computer has stopped communicating with a specific volume or disk device. Unlike a Blue Screen of Death (BSOD), this error often results in a temporary "hard freeze" where the mouse may still move but the screen does not update, audio loops, and input becomes unresponsive. The system typically recovers after about 30 to 60 seconds as the storage driver retries the connection or resets the port. For general users, this might manifest as occasional lag spikes, but for gamers running demanding titles like *Tarkov*, the impact is severe because the game engine expects continuous data streaming from the SSD or HDD. If the storage subsystem pauses, the game thread blocks, leading to the perceived freeze. It is important to distinguish this from network-related issues. While *Tarkov* is an online game, Event ID 153 is strictly a local hardware or driver issue related to your storage devices. It does not indicate packet loss or server-side problems. However, if you are experiencing other connectivity issues, such as loopback connections or Wi-Fi data loss, those are separate concerns that do not cause Event ID 153. You can refer to our guide on PC: Many Time-Wait Loopback Connections - Open? if you suspect network stack corruption, but for storage freezes, focus on the steps below.

Adjusting SATA and NVMe Power Management

The most common cause of Event ID 153 during gaming is the operating system attempting to put a storage port into a low-power state when it detects brief periods of inactivity, even if the game is actively reading assets. Modern Windows versions use Link Power Management (LPM) for SATA ports and ASPM (Active State Power Management) for PCIe/NVMe devices. When the transition from active to idle occurs too aggressively, the drive fails to wake up in time, resulting in a timeout. To resolve this, you must disable these power-saving features for your primary game drive. First, open the Control Panel and navigate to Hardware and Sound > Power Options. Click Change plan settings next to your active power plan, then select Change advanced power settings. In the dialog box, expand the PCI Express setting and locate Link Power Management. Set both On Battery and Plugged In options to Off. This prevents the system from cutting power to the PCIe bus connecting your NVMe drive. Next, expand the Hard disk section and set Turn off hard disk after to Never. While this is primarily for traditional HDDs, it ensures no aggressive timeouts are applied to any storage controller. Additionally, check the USB Root Hub settings in the same menu. Some older motherboards route certain M.2 slots or SATA controllers through internal USB-like buses; disabling selective suspend for USB devices can also help stabilize these connections during heavy I/O loads.

Updating Storage Controllers and Chipset Drivers

Outdated or generic storage drivers are a frequent culprit for Event ID 153. Windows Update often installs generic Microsoft drivers for SATA AHCI controllers, which may lack the specific optimizations required for high-performance NVMe drives. To fix this, identify your motherboard model and download the latest chipset and storage drivers directly from the manufacturer’s website, such as Intel, AMD, or your motherboard vendor. For Intel systems, ensure you have the Intel Rapid Storage Technology (RST) driver installed, even if you are using RAID mode or standard AHCI. For AMD systems, ensure the AMD Chipset Driver package is current, as it includes the necessary SMBus and storage controller utilities. After installing these drivers, restart your computer. If you are using a third-party SSD, check the manufacturer’s website (e.g., Samsung, Western Digital, Crucial) for their specific management software, which can sometimes update the drive’s firmware. An outdated firmware version can lead to stability issues under the heavy load of modern games.

Verifying Drive Health and File System Integrity

Before assuming a driver or power issue, rule out physical degradation or file system errors. A failing SSD or one with bad sectors can exhibit timeouts that look exactly like Event ID 153. Use the built-in Windows tool chkdsk to check for logical errors. Open Command Prompt as Administrator and run chkdsk C: /f /r, replacing C with your drive letter if different. This will schedule a scan at the next reboot. Additionally, use the manufacturer’s diagnostic tool to check the SMART status of your drive. Look for attributes like Media Wearout Indicator or Reallocated Sectors Count. If these values are critical, the drive itself is failing and needs replacement. Also, ensure you have adequate free space on your game drive. Running an SSD near full capacity can degrade performance and increase latency, making timeouts more likely during intensive asset loading.

Frequently Asked Questions

Does Event ID 153 cause data loss?

Typically, no. Event ID 153 is a communication timeout, meaning the OS temporarily lost contact with the drive. Since modern file systems like NTFS use journaling, minor interruptions rarely corrupt data. However, if the drive fails completely during a write operation, some recent data could be lost, so regular backups are essential.

Can I use a different antivirus to fix this?

No, antivirus software does not cause Event ID 153. This error is strictly related to the storage stack and hardware communication. While real-time scanning can add overhead to disk reads, it does not trigger the specific timeout error code associated with storage driver failures.

Why does this happen only in Tarkov and not other games?

*Escape from Tarkov* is known for its extremely high demand on storage bandwidth and random access patterns. Less demanding games may not push the storage controller hard enough to trigger the power management timeouts or driver limits that cause the freeze.

Should I reinstall Windows to fix Event ID 153?

A clean Windows install is rarely necessary and usually does not solve the problem, as the issue lies with drivers, BIOS settings, or hardware. Try updating drivers and changing power settings first, as these address the root cause in 90% of cases.

Is Event ID 153 the same as Event ID 129?

They are related but distinct. Event ID 129 indicates that the device has returned from a suspended state, while Event ID 153 indicates that the device was lost entirely. Both suggest instability in the storage link, but 153 is more severe as it implies a complete drop in communication before recovery.