[EN] Windows 11 NVMe SSD Temporary Freezing Issue: “Reset to device, \Device\RaidPort0, was issued.”

On Windows 11 systems, especially on computers using NVMe SSDs, users may sometimes experience sudden and temporary system freezes. In this scenario, the computer may become completely unresponsive for 5 to 10 seconds. During this time, mouse movement may stop, applications may freeze, disk I/O operations may pause, and in some cases, the system may even crash with a Blue Screen of Death.

One of the most common indicators of this problem can be found in Windows Event Viewer. If you see a warning similar to the following under the System log, the issue may be related to the Windows storage stack, storage controller driver, NVMe power management, firmware, or disk timeout behavior.

Reset to device, \Device\RaidPort0, was issued.

This warning is commonly associated with Event ID 129 and may appear with sources such as storahci, storport, stornvme, or iaStorAC, depending on the storage driver and controller used by the system.

It is important to note that this error does not always mean that the SSD is faulty. It usually means that Windows sent an I/O request to the disk or storage controller but did not receive a response within the expected time. As a result, Windows attempts to reset the storage device or controller path in order to recover the connection.

Common Symptoms

This issue can appear in different ways depending on the system configuration and the severity of the storage delay.

The most common symptoms include temporary system freezing, applications becoming unresponsive, disk activity stopping for a few seconds, mouse and keyboard input not responding, sudden performance drops, game stuttering, virtual machine freezing, file copy operations hanging, or the system crashing with a blue screen.

In many cases, the system recovers automatically after a few seconds. However, if the timeout occurs repeatedly or the storage device fails to respond properly, Windows may become unstable and eventually crash.

When checking Event Viewer, you may see records similar to the following:

Warning
Source: storahci / storport / stornvme / iaStorAC
Event ID: 129
Reset to device, \Device\RaidPort0, was issued.

The RaidPort0 expression does not necessarily mean that the computer is using a RAID configuration. Windows may use this naming convention internally for storage ports and controllers, even on systems that do not have RAID enabled.

What Does This Error Mean?

The warning means that Windows detected a timeout while communicating with the disk or storage controller. When an I/O request takes too long to complete, the storage driver assumes that the device or controller may be stuck. To recover from this state, Windows issues a reset command to the related storage path.

This reset process is designed to prevent the system from remaining permanently stuck. However, while the reset is taking place, the operating system may appear frozen because disk operations cannot continue normally.

In simple terms, Windows is saying:

I sent a request to the storage device, but it did not respond in time. I am resetting the storage path to recover.

This can happen because of driver issues, firmware problems, aggressive power management, NVMe power state transitions, PCIe power saving settings, chipset driver incompatibility, BIOS settings, or actual SSD/controller faults.

Why Is This Commonly Seen on NVMe SSD Systems?

NVMe SSDs are very fast storage devices that communicate through the PCI Express bus. To reduce power consumption, especially on laptops, NVMe drives often use advanced power management mechanisms. One of these mechanisms is APST, also known as Autonomous Power State Transition.

APST allows the NVMe SSD to automatically move between different power states depending on workload. While this is useful for battery life and thermal efficiency, some SSDs, firmware versions, chipsets, or drivers may not handle these transitions smoothly.

If the SSD takes too long to wake up from a low-power state, Windows may interpret this delay as a storage timeout. As a result, the Event ID 129 warning may appear, and the system may freeze temporarily.

However, this issue is not limited to NVMe SSDs only. Similar behavior can also occur on SATA SSDs, AHCI controllers, Intel RST configurations, RAID controllers, or systems using third-party storage drivers.

Possible Causes

There is no single cause for this issue. In most cases, the problem is related to one or more of the following factors:

Outdated SSD firmware, outdated BIOS/UEFI version, incompatible chipset drivers, unstable Intel RST driver version, aggressive NVMe power management, APST-related wake-up delays, PCI Express Link State Power Management, StorAHCI Link Power Management, incorrect disk timeout behavior, faulty SSD, overheating NVMe drive, problematic M.2 slot, loose connection, storage filter drivers, antivirus or backup software interfering with disk I/O, or a Windows storage driver issue.

For this reason, the issue should be handled step by step instead of assuming that the SSD is immediately defective.

Important Warning Before Applying the Fix

The following steps include changes to the Windows Registry and power management settings. Before applying them, it is recommended to create a system restore point and back up important data.

In enterprise environments, production systems, servers, or critical workstations, these changes should be tested carefully before being applied widely.

These settings may reduce disk-related freezes in many cases, but they should not be considered a guaranteed fix for physical disk failure. If the SSD is faulty, overheating, or has firmware-level problems, these changes may only reduce the symptoms temporarily.

Step 1: Check Event Viewer

Before making any changes, confirm that the issue is related to the storage layer.

Open Event Viewer and go to:

Event Viewer > Windows Logs > System

Then filter the current log by the following Event IDs:

129, 153, 154, 157

Pay special attention to the following events:

Event ID 129 - Reset to device, \Device\RaidPort0, was issued.
Event ID 153 - The IO operation was retried.
Event ID 154 - The IO operation failed due to hardware error or timeout.
Event ID 157 - Disk has been surprise removed.

If Event ID 129 appears frequently and matches the exact time when the system freezes, the issue is most likely related to disk I/O timeout, storage controller delay, or power state transition problems.

Step 2: Update SSD Firmware, BIOS, and Chipset Drivers

Before changing registry or power settings, the first recommended step is to update the firmware and drivers.

Check the SSD manufacturer’s official tool for firmware updates. For example, depending on the SSD model, you can use tools such as Samsung Magician, Kingston SSD Manager, Crucial Storage Executive, Western Digital Dashboard, or the vendor’s official update utility.

You should also check the motherboard or laptop manufacturer’s support page and update the following components if newer versions are available:

Chipset driver, BIOS/UEFI firmware, Intel Management Engine, AMD chipset driver, Intel Rapid Storage Technology driver if used, NVMe driver, and storage controller driver.

This step is very important because many NVMe stability issues can be fixed by firmware updates.

Step 3: Disable StorAHCI Link Power Management

If the Event Viewer source is storahci, the issue may be related to SATA/AHCI Link Power Management. In this case, disabling LPM may help reduce temporary freezes and disk timeout warnings.

Open Command Prompt as Administrator and run the following command:

reg add "HKLM\SYSTEM\CurrentControlSet\Services\storahci\Parameters\Device" /v "NoLPM" /t REG_MULTI_SZ /d "*" /f

This command disables Link Power Management for the Microsoft StorAHCI driver.

This setting is mostly relevant for SATA/AHCI-based systems. If your system only uses an NVMe SSD and the Event Viewer source is stornvme, this setting may not directly affect the NVMe driver. Therefore, it is important to check the event source before applying changes.

Step 4: Increase Disk Timeout Value

Windows uses a disk timeout value to determine how long it should wait for a disk I/O operation to complete. If the disk or controller responds too late, Windows may reset the device.

Increasing the timeout value to 30 seconds can sometimes help systems that experience short storage delays.

Open Command Prompt as Administrator and run:

reg add "HKLM\SYSTEM\CurrentControlSet\Services\disk" /v "TimeOutValue" /t REG_DWORD /d 30 /f

This command sets the disk timeout value to 30 seconds.

This change may help Windows tolerate temporary delays caused by SSD wake-up time, controller latency, or short storage stalls. However, it does not fix a physically defective SSD or a serious hardware issue.

Step 5: Restrict NVMe Power State Transition Behavior

NVMe SSDs may enter low-power states when the system is idle. On some systems, the drive may not return from these low-power states quickly enough, causing disk I/O delays.

To reduce this behavior, you can modify the current power plan.

Run the following commands in Command Prompt as Administrator:

powercfg /setacvalueindex SCHEME_CURRENT SUB_DISK PACKET_TIMEOUT 0
powercfg /setactive SCHEME_CURRENT

This applies the setting to the currently active power plan while the system is connected to AC power.

For laptops, you may also want to apply the same setting for battery mode:

powercfg /setdcvalueindex SCHEME_CURRENT SUB_DISK PACKET_TIMEOUT 0
powercfg /setactive SCHEME_CURRENT

After applying these commands, restart the system.

Step 6: Disable PCI Express Link State Power Management

Because NVMe SSDs communicate over PCI Express, PCIe power saving settings can also affect stability.

To disable PCI Express Link State Power Management, follow these steps:

Control Panel > Power Options > Change plan settings > Change advanced power settings

Then navigate to:

PCI Express > Link State Power Management

Set both options to:

On battery: Off
Plugged in: Off

This prevents the PCIe link from entering aggressive low-power states. It may improve NVMe SSD stability, especially on laptops, but it may also slightly increase power consumption.

Step 7: Check SSD Health

If the problem continues, the SSD health should be checked carefully.

You can run the following command:

wmic diskdrive get model,status

You can also use PowerShell:

Get-PhysicalDisk | Select-Object FriendlyName, HealthStatus, OperationalStatus

To check the file system online, run:

chkdsk C: /scan

To verify Windows system files, run:

sfc /scannow

To repair the Windows component store, run:

DISM /Online /Cleanup-Image /RestoreHealth

In addition to these commands, check the SSD with the manufacturer’s official tool. Review SMART values, temperature, firmware version, unsafe shutdown count, media errors, and overall drive health.

Step 8: Review BIOS/UEFI Settings

If the issue is still not resolved, BIOS/UEFI settings should also be checked.

The following settings may be relevant:

M.2 slot configuration, PCIe generation mode, Intel RST or AHCI mode, RAID mode, ASPM settings, CPU C-State settings, NVMe configuration, and BIOS version.

On some systems, PCIe Gen4 or Gen5 may behave unstably with certain SSDs or motherboards. As a test, you can manually set the M.2 slot to a lower PCIe generation, such as Gen3 or Gen4, depending on the system. This should be used as a troubleshooting step, not necessarily as a permanent solution.

Recommended Command Set

The following commands can be used together on desktop and laptop systems. Run Command Prompt as Administrator:

reg add "HKLM\SYSTEM\CurrentControlSet\Services\storahci\Parameters\Device" /v "NoLPM" /t REG_MULTI_SZ /d "*" /f

reg add "HKLM\SYSTEM\CurrentControlSet\Services\disk" /v "TimeOutValue" /t REG_DWORD /d 30 /f

powercfg /setacvalueindex SCHEME_CURRENT SUB_DISK PACKET_TIMEOUT 0

powercfg /setactive SCHEME_CURRENT

For laptops, you can also apply the setting for battery mode:

powercfg /setdcvalueindex SCHEME_CURRENT SUB_DISK PACKET_TIMEOUT 0

powercfg /setactive SCHEME_CURRENT

After running the commands, restart the computer.

How to Revert the Changes

If you want to undo the registry changes, use the following commands.

To remove the NoLPM value:

reg delete "HKLM\SYSTEM\CurrentControlSet\Services\storahci\Parameters\Device" /v "NoLPM" /f

To remove the custom disk timeout value:

reg delete "HKLM\SYSTEM\CurrentControlSet\Services\disk" /v "TimeOutValue" /f

To restore all Windows power plans to their default settings:

powercfg -restoredefaultschemes

Be careful with this command because it resets all power plans and may remove custom power plan configurations.

What to Do If the Problem Continues

If the issue continues after applying these steps, the problem may be related to a deeper firmware, hardware, or driver-level incompatibility.

In that case, you should test the following:

Update the SSD firmware again if a newer version is available. Update BIOS/UEFI to the latest stable version. Reinstall chipset drivers. Try a different Intel RST version if Intel RST is being used. Test the Microsoft default NVMe driver instead of the vendor driver, or vice versa. Move the SSD to another M.2 slot if possible. Monitor SSD temperature under load. Test the SSD in another computer. Test the system with a different NVMe SSD.

If Event ID 129 appears together with Event ID 153, 154, or 157, there may be a more serious storage issue. In this case, the SSD, M.2 slot, motherboard, firmware, or storage controller should be investigated more carefully.

The “Reset to device, \Device\RaidPort0, was issued.” warning on Windows 11 is an important sign of a storage timeout or reset event. It often appears when Windows does not receive a timely response from the disk or storage controller.

Although this warning is commonly seen on NVMe SSD systems, it can also occur with SATA SSDs, AHCI controllers, Intel RST drivers, RAID controllers, or other storage configurations.

The root cause may be outdated firmware, aggressive power management, NVMe APST behavior, PCI Express power saving, StorAHCI Link Power Management, chipset driver issues, BIOS configuration, overheating, or actual hardware failure.

A proper troubleshooting process should start with Event Viewer analysis, followed by SSD firmware updates, BIOS and chipset driver updates, power management adjustments, disk timeout configuration, and SSD health checks.

When applied carefully, the recommended registry and power plan settings can reduce or eliminate temporary freezing caused by storage timeout behavior. However, if the underlying issue is physical disk failure or hardware instability, the affected component should be replaced or tested separately.