Memory management BSOD

Question

When ever I plug in my kingspec 2.5 “ 1 TB SSD to my computer it either freezes on the POST screen, lets me use windows like normal for 5-10 minuets then freezes, or gives me a memory management BSOD.

I am still able to access all my files on my ssd, but what use to take 5–10 seconds to load now takes 15-30 seconds, my pc was a bit dusty but even after dusting everything off and trying again the same thing happens.

I even changed the ports the sata cables are connected to for both the mother board, power supply, and ssd itself but nothing is working and I would really appreciate it if I could fix what ever is causing this since I put all my steam games and videos on there.

Answer 1

1

Please check to see if your PC is producing any minidump files, I will check those to see if they provide any insight into a potential cause of the system crashes.

Please do not upload a very large Memory.dmp file.

Open Windows File Explorer.

Navigate to C:\Windows\Minidump

Copy any minidump files onto your Desktop, then zip those up.

Upload the zip file to the Cloud (OneDrive... etc.), then choose to share those and get a share link.

Then post the link here to the zip file, so I can take a look for you.

2

You indicate you have no space on your C drive, that may be a contributing factor to the crashes.

Download the free TreeSize app from the Microsoft Store.

Very Important - to run TreeSize, you must right click its icon and choose Run as Administrator.

Please provide a screenshot of your C drive in that TreeSize utility, so I can see your hard drive and work out where that space is being used and if there is an underlying problem.

Please ensure the full TreeSize window is in the screenshot, there is information on the top and bottom bars I needs to see.

Answer 2

The symptoms point to a failing storage device or other hardware issue that is being exposed when the SSD is connected. The MEMORY_MANAGEMENT bug check (0x1A) specifically indicates a severe memory management error, and in several documented cases this is tied to hardware problems rather than Windows files or drivers.

Based on the context:

1. MEMORY_MANAGEMENT (0x1A) is commonly caused by hardware faults
   • The MEMORY_MANAGEMENT bug check indicates a severe memory management error and several parameter variants are explicitly described as “probably a hardware error.”
   • This includes corruption of page tables, PFNs, or relocation data, which can be triggered by bad RAM, a failing disk, or a faulty controller when Windows tries to page data in or out.
2. Storage-related errors can cause freezes and BSODs
   • When Windows encounters disk I/O problems (bad blocks, failing storage, cabling issues), it can freeze or bug check. For example, KERNEL_DATA_INPAGE_ERROR (0x7A) is documented as being caused by bad blocks on disk, cabling issues, or other storage hardware faults.
   • The guidance for 0x7A includes running chkdsk /f /r and checking cabling and hardware diagnostics, which is also applicable when a specific drive consistently causes freezes or BSODs.
3. Windows storage health monitoring
   • Windows 10 monitors NVMe SSD health and can raise critical warnings (low spare capacity, degraded reliability, or read‑only state). While this does not apply directly to SATA SSDs, the same underlying issues (media errors, internal device errors) can still exist and cause system instability.

Given that:

• The system only misbehaves when this specific SSD is attached.
• POST freezes, delayed file access, and system freezes/BSODs occur with that drive.
• Ports and cables have already been swapped.

The most likely causes are:

• The SSD itself is failing (internal media errors or controller faults).
• Less likely, a marginal power or SATA controller issue that only shows up under load from that drive.

Recommended steps, in order of priority:

1. Protect data immediately
   • Because the drive is already slow and causing freezes, treat it as at risk of imminent failure.
   • While the system is stable (for example, after booting without that SSD and then hot‑connecting it if supported by the system, or using another PC or USB–SATA adapter), copy critical data (documents, saves, irreplaceable files) off the SSD to another healthy drive.
2. Run disk checks on the SSD
   • When the system is stable enough to do so, run a full surface and file‑system check on that SSD using chkdsk /f /r.
   • If the system cannot stay stable long enough with the drive attached, avoid repeated attempts and focus on data recovery instead; repeated retries on a failing SSD can accelerate failure.
3. Run full hardware diagnostics
   • Run the PC/motherboard vendor’s hardware diagnostics, especially:
     • Memory tests (to rule out RAM issues that can also cause MEMORY_MANAGEMENT).
     • Storage diagnostics for the SATA controller and drives.
   • If any RAM or motherboard issues are reported, address those first, as they can also corrupt paging operations and trigger 0x1A.
4. Check for storage‑related events
   • In Event Viewer, examine System logs around the time of freezes/BSODs for disk, NTFS, or controller errors. Repeated disk or controller errors when that SSD is attached further confirm a hardware problem.
5. Replace the SSD if hardware faults are confirmed or strongly suspected
   • If diagnostics or chkdsk show bad sectors, repeated I/O errors, or if the system only crashes when this SSD is connected even after RAM and cabling are ruled out, treat the SSD as defective and replace it.
   • After replacement, reinstall or move Steam games and other data from backups.

If the problem persists even with the SSD disconnected, then the MEMORY_MANAGEMENT bug check should be investigated as a general hardware issue (RAM, motherboard, CPU) using the same memory‑focused guidance.

---

References:

• Bug Check 0x1A: MEMORY_MANAGEMENT
• Bug check 0x7A: KERNEL_DATA_INPAGE_ERROR
• Troubleshooting Windows unexpected restarts and stop code errors
• What to do about a critical warning for a storage device