F5F Stay Refreshed Hardware Desktop The GEN 4 SSD in the second M.2 port of the ROG Strix x570-E is causing crashes for Games and Windows.

The GEN 4 SSD in the second M.2 port of the ROG Strix x570-E is causing crashes for Games and Windows.

The GEN 4 SSD in the second M.2 port of the ROG Strix x570-E is causing crashes for Games and Windows.

F
florian12pro
Member
144
08-25-2024, 06:04 PM
#1
I've encountered a problem with my new 980 Pro SSD (2TB) installed in the second M.2 slot of the x570E. It often causes games and Windows to crash, especially during gaming sessions like Apex Legends or Hunt: Showdown. Usually, this happens within 5 to 10 minutes.

Before this change, I had a different configuration: a 980 Pro (1TB) in the first M.2 slot and a 970 Evo Plus (500GB) in the second slot, which functioned well for more than two years. Recently, I swapped the 970 Evo Plus for the 980 Pro 2TB version in the second slot. After making this adjustment, my system has been crashing constantly. At first, I thought the new SSD was the culprit. So I removed it and returned the 1TB 980 Pro to the second slot, leaving the first empty. The issue persisted. This made me suspect a problem with the second slot. However, the 970 Evo Plus worked fine in that slot for over two years.

To troubleshoot, I followed these steps: updated drivers for CPU, GPU, and SSD; installed the latest BIOS; re-plugged all power cables; reinstalled the operating system. My PC specifications are: CPU 5800X3D, Mobo ROG Strix X570-E, RAM 32GB (8x4) @3200Mhz, GPU MSI 2070S, PSU Corsair RM1000x (1000W), case NZXT 710i, AIO NZXT Kraken X73, storage SSDs include 980 Pro 1TB/2TB and 970 Evo+ 500GB. HDDs are ST4000DM004, WD30EZRX, WD20EZRX.

If anyone has experienced this or knows what might be causing it, please assist. I've spent the last two weekends trying to resolve this. Also, the problem appears even when no OS or games are running on the second slot. It doesn't seem to happen after deleting the volume via Disk Management, but it starts right away once the volume is added. The error message displayed is "System Thread Exception Not Handled."
F
florian12pro
08-25-2024, 06:04 PM #1

I've encountered a problem with my new 980 Pro SSD (2TB) installed in the second M.2 slot of the x570E. It often causes games and Windows to crash, especially during gaming sessions like Apex Legends or Hunt: Showdown. Usually, this happens within 5 to 10 minutes.

Before this change, I had a different configuration: a 980 Pro (1TB) in the first M.2 slot and a 970 Evo Plus (500GB) in the second slot, which functioned well for more than two years. Recently, I swapped the 970 Evo Plus for the 980 Pro 2TB version in the second slot. After making this adjustment, my system has been crashing constantly. At first, I thought the new SSD was the culprit. So I removed it and returned the 1TB 980 Pro to the second slot, leaving the first empty. The issue persisted. This made me suspect a problem with the second slot. However, the 970 Evo Plus worked fine in that slot for over two years.

To troubleshoot, I followed these steps: updated drivers for CPU, GPU, and SSD; installed the latest BIOS; re-plugged all power cables; reinstalled the operating system. My PC specifications are: CPU 5800X3D, Mobo ROG Strix X570-E, RAM 32GB (8x4) @3200Mhz, GPU MSI 2070S, PSU Corsair RM1000x (1000W), case NZXT 710i, AIO NZXT Kraken X73, storage SSDs include 980 Pro 1TB/2TB and 970 Evo+ 500GB. HDDs are ST4000DM004, WD30EZRX, WD20EZRX.

If anyone has experienced this or knows what might be causing it, please assist. I've spent the last two weekends trying to resolve this. Also, the problem appears even when no OS or games are running on the second slot. It doesn't seem to happen after deleting the volume via Disk Management, but it starts right away once the volume is added. The error message displayed is "System Thread Exception Not Handled."

N
148
08-25-2024, 06:05 PM
#2
Considered an alternative approach, have you attempted updating the AMD chipset driver? Using Samsung Magician to update firmware and setting Microsoft as the device driver in Device Details might resolve the issue. It seems the incorrect driver is being applied, possibly due to using the wrong one. My setup relies on the Standard NVM Express Controller listed under Device Manager.
N
nicoandreassen
08-25-2024, 06:05 PM #2

Considered an alternative approach, have you attempted updating the AMD chipset driver? Using Samsung Magician to update firmware and setting Microsoft as the device driver in Device Details might resolve the issue. It seems the incorrect driver is being applied, possibly due to using the wrong one. My setup relies on the Standard NVM Express Controller listed under Device Manager.

E
57
08-25-2024, 06:05 PM
#3
I possessed this device. Verify the CMOS battery level. Provide an update.
E
endergirlsarah
08-25-2024, 06:05 PM #3

I possessed this device. Verify the CMOS battery level. Provide an update.

M
Minetoblend
Member
110
08-25-2024, 06:05 PM
#4
Both AMD Chipset Drivers and SSD Firmware are current, and Microsoft appears in both device driver lists. Still, oddly enough, the Device Manager lists two 1TB 980 Pros under Disk Drives, while one should actually be a 2TB drive.
M
Minetoblend
08-25-2024, 06:05 PM #4

Both AMD Chipset Drivers and SSD Firmware are current, and Microsoft appears in both device driver lists. Still, oddly enough, the Device Manager lists two 1TB 980 Pros under Disk Drives, while one should actually be a 2TB drive.

M
MrBogdanr5000
Member
148
08-25-2024, 06:05 PM
#5
Here are the current, minimum, maximum, and average values.
M
MrBogdanr5000
08-25-2024, 06:05 PM #5

Here are the current, minimum, maximum, and average values.

S
Splax67
Member
190
08-25-2024, 06:05 PM
#6
Software readings during operation aren't consistent. My device also displayed a normal reading, but its battery was only 2.3V. It's unclear why it functioned at that level since CR2032 cells are typically dead below 2.7V.
S
Splax67
08-25-2024, 06:05 PM #6

Software readings during operation aren't consistent. My device also displayed a normal reading, but its battery was only 2.3V. It's unclear why it functioned at that level since CR2032 cells are typically dead below 2.7V.

X
Xyers
Junior Member
1
08-25-2024, 06:05 PM
#7
You were correct. My readings turned out to be 2.4V. I swapped it for a fresh CR2032 battery. Thus far, everything is running smoothly. I'll share an update soon.
X
Xyers
08-25-2024, 06:05 PM #7

You were correct. My readings turned out to be 2.4V. I swapped it for a fresh CR2032 battery. Thus far, everything is running smoothly. I'll share an update soon.

S
227
08-25-2024, 06:05 PM
#8
Sure, I'm ready! What would you like me to do?
S
SenhorRoxinhas
08-25-2024, 06:05 PM #8

Sure, I'm ready! What would you like me to do?