Again, the one constant here are your SSDs from your old laptop and now this one. Without swapping the SSD, you could run an instance of Linux off a USB stick, which will be running out of RAM. This isn't foolproof, given that maybe your issue is with Windows and Linux would solve the issue.
If this were my computer, I would take out both disks, set them aside and put in a 1Tb SSD, then install Windows. Use it like that for a week or more and see if the issue continues. Alternatively, update Chipset drivers if that exists (you should be able to use Lenovo Vantage to check for drivers). In fact, update all drivers that exist.
Further, I asked Copilot about this issue and this is what it had to say:
🧩 Why a 4TB NVMe
1.
Windows’ built‑in NVMe driver has been shown to cause:
- System deadlocks
- Kernel‑power crashes
- WHEA PCIe errors
- Total system freezes under sustained I/O
This was reproduced on multiple systems using high‑performance NVMe drives. Switching to the alternative Microsoft NVMe driver (nvmedisk.sys) eliminated the crashes entirely.
2.
Large‑capacity drives (2TB–4TB) often use:
- Newer controllers
- More aggressive power‑saving states
- More complex FTL (flash translation layer) mappings
These increase the chance of firmware edge‑case failures.
Examples:
- Samsung 990 Pro 4TB drives intermittently disconnecting, requiring full power‑cycle reboots. Firmware suspected.
- Western Digital / SanDisk 2TB+ models crashing Windows 11 24H2 under heavy I/O due to HMB‑related firmware issues.
3.
Windows 11 24H2 changed how it negotiates HMB with DRAM‑less NVMe SSDs.This caused:
- BSOD loops
- Kernel crashes
- System hangs during large transfers
Especially on higher‑capacity DRAM‑less drives that rely heavily on HMB. Firmware updates were required to fix this.
4.
On some systems, 4TB NVMe drives BSOD during boot when controlled by Intel RST.Switching to the Windows in‑box NVMe driver fixes the issue.
🧨 What symptoms match NVMe‑related kernel faults?
If you’re seeing any of these, the NVMe is a prime suspect:
- Kernel Data Inpage Error
- Critical Process Died
- WHEA PCIe errors
- System freezes with cursor still moving
- Drive disappears from BIOS until multiple reboots
- Crashes during large file transfers or game installs
These patterns match the documented NVMe failure modes above.
🧪 How to confirm it’s the NVMe (quick tests)
- Move Windows to another drive temporarily If crashes stop → the NVMe or its driver/firmware is the cause.
- Disable HMB (if DRAM‑less) Registry tweaks can stabilize affected drives (performance drops).This was a known workaround for 24H2 instability.
- Switch NVMe driver
- Try Microsoft’s nvmedisk.sys (25H2+ feature flag).
- Avoid Intel RST for standalone NVMe drives.
- Update firmware Samsung, WD, and SanDisk all issued firmware fixes for NVMe‑related BSODs.
- Check Event Viewer → WHEA‑Logger If you see PCIe Bus/Device errors → NVMe controller instability is likely.
🧠 Bottom line
A 4TB NVMe absolutely can cause intermittent kernel‑level crashes in Windows — not because it’s 4TB, but because large‑capacity NVMe drives often expose firmware, driver, and HMB‑related bugs that smaller drives don’t hit. Multiple real‑world cases and vendor advisories confirm this.
Yeah, so straight-up, I'd update the drivers and see what happens. But more than likely I'd try the smaller SSD and see if the problem disappears.
Again you mention in a previous thread that you had this issue on another PC with the same SSD. That seems to suggest a common cause.