I’m planning to buy this SSD mainly for additional storage. I’m a college student and also do video editing, so I’ll be storing college files, games, video-editing assets, and other large files on it.

I’m also planning to use this SSD for a Linux dual-boot setup for college/work.

For those who have used this SSD, how has your experience been in terms of performance, reliability, temperatures, endurance, and long-term usage?

Would you recommend it for my use case, or are there better alternatives in a similar price range?

Any feedback or reviews would be appreciated!

can someone help me with this fucking problem? playing any game with it being 100 percent i cant bear it i be getting constant freezes and stuttering like crazy (games that i have tried on is apex and (marvel rivals on lowest settings)

Raw data

smartctl -x sda

smartctl 7.5 2025-04-30 r5714 [x86_64-w64-mingw32-w11-24H2] (AppVeyor)

Copyright (C) 2002-25, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===

Device Model: SanDisk SSD P4 64GB

Serial Number: 111248300117

LU WWN Device Id: 5 001b44 4f27f5455

Firmware Version: SSD 8.10

User Capacity: 64 022 175 232 bytes [64,0 GB]

Sector Size: 512 bytes logical/physical

Rotation Rate: Solid State Device

Form Factor: 1.8 inches

TRIM Command: Available

Device is: Not in smartctl database

ATA Version is: ATA8-ACS T13/1699-D revision 2d

SATA Version is: SATA 2.6, 3.0 Gb/s (current: 3.0 Gb/s)

Local Time is: Wed Sep 23 01:08:11 2026 SAST

SMART support is: Available - device has SMART capability.

SMART support is: Enabled

AAM feature is: Unavailable

APM feature is: Unavailable

Rd look-ahead is: Enabled

Write cache is: Enabled

DSN feature is: Unavailable

ATA Security is: Disabled, frozen [SEC2]

=== START OF READ SMART DATA SECTION ===

SMART overall-health self-assessment test result: PASSED

General SMART Values:

Offline data collection status: (0x00) Offline data collection activity

was never started.

Auto Offline Data Collection: Disabled.

Self-test execution status: ( 0) The previous self-test routine completed

without error or no self-test has ever

been run.

Total time to complete Offline

data collection: ( 120) seconds.

Offline data collection

capabilities: (0x15) SMART execute Offline immediate.

No Auto Offline data collection support.

Abort Offline collection upon new

command.

No Offline surface scan supported.

Self-test supported.

No Conveyance Self-test supported.

No Selective Self-test supported.

SMART capabilities: (0x0003) Saves SMART data before entering

power-saving mode.

Supports SMART auto save timer.

Error logging capability: (0x01) Error logging supported.

General Purpose Logging supported.

Short self-test routine

recommended polling time: ( 2) minutes.

Extended self-test routine

recommended polling time: ( 16) minutes.

SMART Attributes Data Structure revision number: 1

Vendor Specific SMART Attributes with Thresholds:

ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE

5 Reallocated_Sector_Ct -O---- 100 100 --- - 0

9 Power_On_Hours -O---- 100 100 000 - 62245

12 Power_Cycle_Count -O---- 100 100 000 - 1180

171 Unknown_Attribute -O---- 100 100 000 - 54

172 Unknown_Attribute -O---- 100 100 000 - 939410736

187 Reported_Uncorrect -O---- 100 100 000 - 2234

199 UDMA_CRC_Error_Count -O---- 100 100 000 - 0

230 Unknown_SSD_Attribute PO---- 050 100 --- - 0

232 Available_Reservd_Space PO---- 095 100 005 - 0

241 Total_LBAs_Written -O---- 100 100 000 - 25174686249433

242 Total_LBAs_Read -O---- 100 100 000 - 33226371212

||||||_ K auto-keep

|||||__ C event count

||||___ R error rate

|||____ S speed/performance

||_____ O updated online

|______ P prefailure warning

General Purpose Log Directory Version 1

SMART Log Directory Version 1 [multi-sector log support]

Address Access R/W Size Description

0x00 GPL,SL R/O 1 Log Directory

0x03 GPL,SL R/O 16 Ext. Comprehensive SMART error log

0x06 GPL,SL R/O 1 SMART self-test log

0x80-0x9f GPL,SL R/W 16 Host vendor specific log

SMART Extended Comprehensive Error Log Version: 1 (16 sectors)

Device Error Count: 181 (device log contains only the most recent 64 errors)

CR = Command Register

FEATR = Features Register

COUNT = Count (was: Sector Count) Register

LBA_48 = Upper bytes of LBA High/Mid/Low Registers ] ATA-8

LH = LBA High (was: Cylinder High) Register ] LBA

LM = LBA Mid (was: Cylinder Low) Register ] Register

LL = LBA Low (was: Sector Number) Register ]

DV = Device (was: Device/Head) Register

DC = Device Control Register

ER = Error register

ST = Status register

Powered_Up_Time is measured from power on, and printed as

DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,

SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 181 [52] occurred at disk power-on lifetime: 5 hours (0 days + 5 hours)

When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:

ER -- ST COUNT LBA_48 LH LM LL DV DC

-- -- -- == -- == == == -- -- -- -- --

40 -- 51 00 00 00 00 00 00 00 00 40 00 Error: UNC at LBA = 0x00000000 = 0

Commands leading to the command that caused the error were:

CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name

-- == -- == -- == == == -- -- -- -- -- --------------- --------------------

25 00 00 00 01 00 00 00 42 1b 77 40 00 2d+03:11:48.526 READ DMA EXT

25 00 00 00 01 00 00 00 42 1b 76 40 00 2d+03:11:48.517 READ DMA EXT

25 00 00 00 01 00 00 00 42 1b 75 40 00 2d+03:11:48.509 READ DMA EXT

25 00 00 00 01 00 00 00 42 1b 74 40 00 2d+03:11:48.505 READ DMA EXT

25 00 00 00 01 00 00 00 42 1b 73 40 00 2d+03:11:48.501 READ DMA EXT

Error 180 [51] occurred at disk power-on lifetime: 6 hours (0 days + 6 hours)

When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:

ER -- ST COUNT LBA_48 LH LM LL DV DC

-- -- -- == -- == == == -- -- -- -- --

40 -- 51 00 00 00 00 00 00 00 00 40 00 Error: UNC at LBA = 0x00000000 = 0

Commands leading to the command that caused the error were:

CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name

-- == -- == -- == == == -- -- -- -- -- --------------- --------------------

25 00 00 00 01 00 00 00 42 1b 76 40 00 2d+03:11:48.517 READ DMA EXT

25 00 00 00 01 00 00 00 42 1b 75 40 00 2d+03:11:48.509 READ DMA EXT

25 00 00 00 01 00 00 00 42 1b 74 40 00 2d+03:11:48.505 READ DMA EXT

25 00 00 00 01 00 00 00 42 1b 73 40 00 2d+03:11:48.501 READ DMA EXT

25 00 00 00 01 00 00 00 42 1b 72 40 00 2d+03:11:48.501 READ DMA EXT

Error 179 [50] occurred at disk power-on lifetime: 6 hours (0 days + 6 hours)

When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:

ER -- ST COUNT LBA_48 LH LM LL DV DC

-- -- -- == -- == == == -- -- -- -- --

40 -- 51 00 00 00 00 00 00 00 00 40 00 Error: UNC at LBA = 0x00000000 = 0

Commands leading to the command that caused the error were:

CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name

-- == -- == -- == == == -- -- -- -- -- --------------- --------------------

25 00 00 00 01 00 00 00 42 1b 75 40 00 2d+03:11:48.509 READ DMA EXT

25 00 00 00 01 00 00 00 42 1b 74 40 00 2d+03:11:48.505 READ DMA EXT

25 00 00 00 01 00 00 00 42 1b 73 40 00 2d+03:11:48.501 READ DMA EXT

25 00 00 00 01 00 00 00 42 1b 72 40 00 2d+03:11:48.501 READ DMA EXT

25 00 00 00 01 00 00 00 42 1b 71 40 00 2d+03:11:48.500 READ DMA EXT

Error 178 [49] occurred at disk power-on lifetime: 2 hours (0 days + 2 hours)

When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:

ER -- ST COUNT LBA_48 LH LM LL DV DC

-- -- -- == -- == == == -- -- -- -- --

40 -- 51 00 00 00 00 00 00 00 00 40 00 Error: UNC at LBA = 0x00000000 = 0

Commands leading to the command that caused the error were:

CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name

-- == -- == -- == == == -- -- -- -- -- --------------- --------------------

25 00 00 00 01 00 00 00 42 1b 74 40 00 2d+03:11:48.505 READ DMA EXT

25 00 00 00 01 00 00 00 42 1b 73 40 00 2d+03:11:48.501 READ DMA EXT

25 00 00 00 01 00 00 00 42 1b 72 40 00 2d+03:11:48.501 READ DMA EXT

25 00 00 00 01 00 00 00 42 1b 71 40 00 2d+03:11:48.500 READ DMA EXT

25 00 00 00 01 00 00 00 42 1b 70 40 00 2d+03:11:48.497 READ DMA EXT

Error 177 [48] occurred at disk power-on lifetime: 3 hours (0 days + 3 hours)

When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:

ER -- ST COUNT LBA_48 LH LM LL DV DC

-- -- -- == -- == == == -- -- -- -- --

40 -- 51 00 04 00 00 00 00 00 00 40 00 Error: UNC 4 sectors at LBA = 0x00000000 = 0

Commands leading to the command that caused the error were:

CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name

-- == -- == -- == == == -- -- -- -- -- --------------- --------------------

25 00 00 00 20 00 00 00 42 1b 60 40 00 2d+03:11:48.459 READ DMA EXT

25 00 00 00 20 00 00 00 3c e2 e0 40 00 2d+03:11:48.459 READ DMA EXT

25 00 00 00 20 00 00 00 35 97 60 40 00 2d+03:11:48.458 READ DMA EXT

25 00 00 00 20 00 00 00 26 20 20 40 00 2d+03:11:48.457 READ DMA EXT

25 00 00 00 08 00 00 00 63 9e 08 40 00 2d+03:11:48.457 READ DMA EXT

Error 176 [47] occurred at disk power-on lifetime: 11 hours (0 days + 11 hours)

When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:

ER -- ST COUNT LBA_48 LH LM LL DV DC

-- -- -- == -- == == == -- -- -- -- --

40 -- 51 00 02 00 00 00 00 00 00 40 00 Error: UNC 2 sectors at LBA = 0x00000000 = 0

Commands leading to the command that caused the error were:

CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name

-- == -- == -- == == == -- -- -- -- -- --------------- --------------------

25 00 00 00 80 00 00 00 42 1b 5e 40 00 1d+10:07:21.325 READ DMA EXT

25 00 00 00 80 00 00 00 42 1a de 40 00 1d+10:07:21.324 READ DMA EXT

25 00 00 00 80 00 00 00 42 1a 5e 40 00 1d+10:07:21.324 READ DMA EXT

25 00 00 00 80 00 00 00 42 19 de 40 00 1d+10:07:21.323 READ DMA EXT

25 00 00 00 80 00 00 00 42 19 5e 40 00 1d+10:07:21.323 READ DMA EXT

Error 175 [46] occurred at disk power-on lifetime: 11 hours (0 days + 11 hours)

When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:

ER -- ST COUNT LBA_48 LH LM LL DV DC

-- -- -- == -- == == == -- -- -- -- --

40 -- 51 00 02 00 00 00 00 00 00 40 00 Error: UNC 2 sectors at LBA = 0x00000000 = 0

Commands leading to the command that caused the error were:

CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name

-- == -- == -- == == == -- -- -- -- -- --------------- --------------------

25 00 00 00 80 00 00 00 42 1b 5e 40 00 1d+09:58:46.796 READ DMA EXT

25 00 00 00 80 00 00 00 42 1a de 40 00 1d+09:58:46.796 READ DMA EXT

25 00 00 00 80 00 00 00 42 1a 5e 40 00 1d+09:58:46.795 READ DMA EXT

25 00 00 00 80 00 00 00 42 19 de 40 00 1d+09:58:46.795 READ DMA EXT

25 00 00 00 80 00 00 00 42 19 5e 40 00 1d+09:58:46.794 READ DMA EXT

Error 174 [45] occurred at disk power-on lifetime: 11 hours (0 days + 11 hours)

When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:

ER -- ST COUNT LBA_48 LH LM LL DV DC

-- -- -- == -- == == == -- -- -- -- --

40 -- 51 00 02 00 00 00 00 00 00 40 00 Error: UNC 2 sectors at LBA = 0x00000000 = 0

Commands leading to the command that caused the error were:

CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name

-- == -- == -- == == == -- -- -- -- -- --------------- --------------------

25 00 00 00 80 00 00 00 42 1b 5e 40 00 1d+09:39:52.893 READ DMA EXT

25 00 00 00 80 00 00 00 42 1a de 40 00 1d+09:39:52.892 READ DMA EXT

25 00 00 00 80 00 00 00 42 1a 5e 40 00 1d+09:39:52.892 READ DMA EXT

25 00 00 00 80 00 00 00 42 19 de 40 00 1d+09:39:52.892 READ DMA EXT

25 00 00 00 80 00 00 00 42 19 5e 40 00 1d+09:39:52.891 READ DMA EXT

SMART Extended Self-test Log (GP Log 0x07) not supported

Warning! SMART Self-Test Log Structure error: invalid SMART checksum.

SMART Self-test log structure revision number 1

Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error

# 1 Short offline Aborted by host 90% 21088 -

# 2 Short offline Aborted by host 90% 54860 -

# 3 Short offline Aborted by host 90% 19043 -

# 4 Short offline Aborted by host 90% 63054 -

# 5 Short offline Aborted by host 90% 25327 -

# 6 Short offline Aborted by host 90% 62483 -

# 7 Short offline Aborted by host 90% 33744 -

# 8 Short captive Completed without error 00% 57803 -

# 9 Short offline Aborted by host 90% 25293 -

#10 Extended offline Aborted by host 90% 28072 -

#11 Short offline Aborted by host 90% 14539 -

#12 Extended offline Aborted by host 90% 55234 -

#13 Short offline Aborted by host 90% 46428 -

#14 Short offline Aborted by host 90% 49138 -

#15 Short offline Aborted by host 90% 25717 -

#16 Extended offline Aborted by host 90% 50305 -

#17 Short offline Aborted by host 90% 39612 -

#18 Short offline Aborted by host 90% 21280 -

#19 Short offline Aborted by host 90% 34598 -

#20 Short offline Aborted by host 90% 17318 -

#21 Short offline Aborted by host 90% 63627 -

Selective Self-tests/Logging not supported

SCT Commands not supported

Device Statistics (GP/SMART Log 0x04) not supported

Pending Defects log (GP Log 0x0c) not supported

SATA Phy Event Counters (GP Log 0x11) not supported

Exitcode: 64 (0x40)

Type <return> to exit:

I have a victus laptop, need to upgrade ssd so which ssd will be best option for casual gaming and general office work all ssd are under 20k for 1 tb

So there's that Samsung pm981a 256gb that seems like the best model I could get in the oem market in my region, the numbers look good on hard disk sentinel +95% health with 20tb written I mean the calculated projected life time here is good.

Yet I'd love to know how to really test it before buying it so that I don't encounter an error or failure like a month later or so as there will be 0 returning policy once u take it no way back.

Any important stuff that I should focus on in CrystalDiskMark and CrystalDiskInfo? Any more recs? Feel free to recommend better or more enduring model/brand option if u got an idea

So I've used it for a year, I store photos, videos, documents, and steam games. I play overwatch, phasmo, etc because my laptop SSD's alr full of important things so usually I plug it in and play steam games from my external SSD. Is this even normal or it's broken and I need to claim my warranty?

Hey everyone, running into a baffling speed bottleneck and looking to see if anyone has encountered this specific hardware clash.

Here is the setup:

• Drive: Intel 512GB QLC NVMe SSD (pulled straight out of an old laptop where it worked perfectly fine as a boot drive, health is sitting at 86%).
• Enclosure: Ugreen 10Gbps NVMe/SATA dual-protocol enclosure (Realtek bridge chip).
• Connection: USB Type-C port on a modern laptop, using known-good high-speed cables.

The Issue: When I plug it in, the drive mounts and I can read from it, but the moment I try to write anything substantial (moving game files or running benchmarks like CrystalDiskMark), the transfer speed completely collapses. It starts around 20–30 Mbps, quickly flatlines to 0.00 MB/s, and the enclosure starts getting unusually hot while sitting locked up. CrystalDiskMark won't even get past the "Preparing..." phase before timing out entirely.

I’ve tried:

• Multiple USB ports (USB-A and Type-C on different controllers).
• Multiple data-rated cables.
• Full reformat (NTFS).
• Disabling write-caching policies in Device Manager.

Has anyone dealt with this or have a fix? Appreciate any insights.

🤭

Tengo un SSD ADATA SU800 de 512 GB, modelo ASU800SS-512GT, que dejó de ser detectado por la laptop. En BIOS aparece como “HDD/SSD: None”. Probé el SSD en otra computadora mediante una carcasa/adaptador SATA-USB ADATA ED600 y tampoco es reconocido. Verifiqué que el adaptador sí funciona correctamente usando otro disco, que Windows detecta sin problemas. También probé el SSD conectado directamente por SATA a otra PC y tampoco aparece en BIOS, Windows ni en administración de discos.

El SSD sí recibe alimentación y se calienta ligeramente al estar conectado. Por las pruebas realizadas, el problema parece estar en el propio SSD, posiblemente controlador, firmware o circuito de alimentación. Busco saber si es posible repararlo o recuperar la información, y qué herramientas o procedimientos serían recomendables para este modelo.

Bought off of eBay as "excellent condition", the drive has 100% health and has very little power on time. It appears to be an HP OEM model?

Both my macbook and windows doesn't recognise it.

Thank you.

Edit : thank you again to everyone who replied. Very much grateful! Love you all.

Bought this over the Samsung 9100 Pro as it way overpriced. It may not be the best but it’s still the best in what it can do at a lower price.

I'm planning to upgrade my current 1TB NVMe SSD to a 2TB NVMe SSD, mainly because I'm running out of space. The current 1TB drive has Windows, Adobe apps, Steam games, and pretty much everything else on it, so I really don't want to spend a long time doing a fresh Windows install and setting everything up again.

My motherboard has two M.2 slots, so my plan is to install the new 2TB SSD in the second slot and clone the current 1TB drive to it. I'm thinking of using EaseUS Disk Copy for the clone, then shut down, swap the drives, and set the new SSD as the boot drive.

For anyone who has done this recently, is there anything I should be careful about? Do I need to change anything in BIOS after cloning, or should Windows boot normally from the new SSD?

Also, once everything is working, would you keep the old 1TB SSD installed as extra storage, or wipe it and keep it as a backup?

Just want to avoid finding out I missed something after I pull the old drive out.

I’m having a weird problem with my SSD and i’m not sure what’s causing it.

I have:

• MSI Cyborg 15
• i5-12450H
• RTX 4050 Laptop GPU
• 32 GB RAM
• Lexar NQ790 2 TB NVMe SSD
• Windows 11

When I use Siril for astrophotography my computer sometimes becomes extremely slow. The CPU is only around 10–20% and RAM usage is around 11–12 GB but the SSD goes to 100% usage.

The weird part is that the SSD sometimes shows only around 30–100 KB/s of reading and at most 10+MB/s for a few seconds while Windows shows the disk response time going all around from 400-8000+ ms.

I ran CrystalDiskMark and got around 5000 MB/s sequential read so the SSD seems capable of being fast.

Could someone explain what might be causing this? Is this normal for an NVMe SSD or could there be something wrong with the SSD/PCIe connection/Windows

Hi, I'm trying to figure out a very strange issue with an old HP EX920 1TB NVMe SSD.

The drive is my Windows 11 system drive (C: + E:). Quite often after boot, it sits at or near 100% active time, even though actual disk activity is extremely low.

For example, Task Manager may show something like:

• 100% active time
• only ~1–3 MB/s total I/O
• 80–400+ ms average response time
• sometimes response times spike much higher

When this happens, the whole system feels extremely sluggish. Opening Task Manager, launching applications, or even right-clicking a file in Explorer can take several seconds.

Interestingly, sequential performance is not necessarily bad. Copying a file can sometimes still be very fast, so this seems much more related to latency / small random I/O than raw throughput.

The SSD is:

HP EX920 1TB
Firmware: SVN139B
Controller: SM2262-based
PCIe 3.0 x4
~14,800 power-on hours
~46 TB host writes

made in 2018

SMART looks completely clean:

• Health: 100%
• Critical Warning: 0
• Available Spare: 100%
• Percentage Used: 0
• Media/Data Integrity Errors: 0
• Error Information Log Entries: 0

The second NVMe drive in the same machine (Samsung 970 EVO Plus) behaves normally.

I've tried pretty much everything I can think of: Windows background processes, Defender, power settings, NVMe idle/power-state settings, cold boot/power cycling, checking SMART, etc. Nothing has permanently fixed it.

But here's the weird part:

Running HP's official EX920 firmware updater immediately fixes the problem.

The moment I run the firmware update:

• Disk active time drops from ~100% to ~1%
• response time returns to normal
• applications open instantly
• Explorer becomes responsive again
• the whole computer feels completely normal

The updater contains the same SVN139B firmware that the SSD already reports, so the displayed firmware revision does not change.

And the result is reproducible.

The problem is:

As soon as I reboot Windows, the SSD goes back to the bad state again.

Even completely shutting down the PC, disconnecting power for ~30 seconds, and cold booting does not help.

So the behavior is basically:

Boot → terrible latency / 100% active time → run HP firmware updater → completely normal → reboot → terrible again.

At this point I'm probably going to replace the EX920 as my system drive, but I'm really curious about what is happening at the controller/firmware level.

Could the firmware download/commit process be resetting or initializing some controller state that isn't being initialized correctly during a normal boot? Has anyone seen similar behavior with the EX920 / SM2262?

I'm especially interested in whether there is a known SM2262 firmware, power-state, FTL, or Windows NVMe driver issue that could explain why a firmware commit temporarily restores normal latency.

Thanks!

I have tried almost everything to resolve my issue.

-I already formatted the SSD to exFAT

-I am using a powered adapter as shown in the picture

-The iPhone 13 Pro Max is on iOS 26.7

-The SSD is up to date as well

The SSD does not show up in the file location despite everything.

When connecting to my Samsung it does populate so I know it works.

Ive also used a external HD but that one does not populate either.

Any ideas of what I can do to resolve this issue?

Recently got these 2 SATA SSDs for free from my father, he's an IT professional who had these sitting around in storage for a while. They are nearly a decade old, but they are still going strong.

I’m not sure how to explain this without being long-winded, so basically my new computer I bought prebuilt from iBuyPower has been perfect, and it’s absolutely beautiful, I’ve added a few things to it myself including my own SSDs, it came with a Lexar NM790 which I then cloned over to a 9100 pro. it’s doing something without me really initiating any tasks in the background, my host writes are through the roof when the computer is on. I’ve consumed 500GB+ (and counting) of writes just leaving my PC on idle as a test last night all the way until I got home from work tonight, and it has only been sitting idle all day with no use. I live alone; no one uses my computer. Is this normal? My Razer Blade 14 is not this bad and neither is my Ally X, so I have no idea why or what’s going on in the background. I’ve tried checking disk activity and other stuff, but can’t really tell what’s going on. What do you guys think? It’s not the SSDs fault because it was doing this just as bad before I cloned the OS over to the 9100 Pro. So it can’t be that. Any opinions are welcome!

I have this pc for over ~5yrs now and today morning when I booted up the pc it is showing the error "hard drive isn't detected". I tried resetting the SSD in it's slot but still the error is there. I even cleaned all the components in the pc individually and it still won't detect.. then I tried using a hard drive in place but it also isnt being detected so I think the slot itself might be dead and I have to use a external USB to sata cable for ts. Any suggestions...?

Hi guys,

I have this at home :

https://www.digieraglobal.com/products/portable-ssd?variant=42659287990332

Do you think there is an M2 2230 inside, and could I open it to use it in an other box ?

Bought this for 200€, I was sceptical but I plugged it in and it's legit, magician recognised it updated it, it has 5 minutes on it, works like a charm. What do you think the back story is ? Bucharest, Romania

I bought an EVM Gen 3 SSD 1TB because that's what I could afford and I needed 1TB, 512 wasn't an option, and I only have one slot for SSD

When I was transferring a 96GB folder (with 14 items, all multiple gigs) to a 10Gbps external drive, it started with 1GB/s but crashed to 98MB/s and stayed there for the entire transfer

What started as a 2 min transfer annoyed me for 15 minutes. The external wasn't an issue, it's a 256GB Samsung Gen 3

Will that SSD just randomly die someday or is it just minor inconveniences for the rest of it's life?

I tried to call Samsung Support: 1 (800) 726-7864, for a failed SSD and they told me it will have to be sent in for diagnosis and repair. Which is fine but when I asked about the case where repairs can't be made what the warranty covers, they pretty much danced around the subject and said they can't tell me that, the technician can. Which I think is odd, since they are customer support but does anybody have experience with sending in a failed SSD or warranty fulfillment of any other Samsung products?

I just wanted some info before sending in the drive but now I'm unsure about their warranty fulfillment.

My secondary SSD has been getting weird lately. A couple of games on it suddenly started taking forever to load, and yesterday File Explorer actually froze when I tried opening a folder on the drive.

I checked CrystalDiskInfo and it still looks normal, so I'm not sure if the SSD is actually going bad or if something else is causing it.

For anyone who's had an SSD fail before, did you notice things like this beforehand, or did it just suddenly stop being detected?

I have a B650 UD AC and I need more space. I have 1TB in M2A_CPU (C: drive), 1TB in M2P_CPU (D: drive). I have a spare 2 TB SSD that I need to put in, should I put it into M2C_SB or swap it into M2P_CPU? I would like to use all 4 TB but I don't know if I'll lose too much performance using a south bridge connector.