- Joined
- Nov 10, 2006
- Messages
- 4,665 (0.73/day)
- Location
- Washington, US
System Name | Rainbow |
---|---|
Processor | Intel Core i7 8700k |
Motherboard | MSI MPG Z390M GAMING EDGE AC |
Cooling | Corsair H115i, 2x Noctua NF-A14 industrialPPC-3000 PWM |
Memory | G. Skill TridentZ RGB 4x8GB (F4-3600C16Q-32GTZR) |
Video Card(s) | ZOTAC GeForce RTX 3090 Trinity |
Storage | 2x Samsung 950 Pro 256GB | 2xHGST Deskstar 4TB 7.2K |
Display(s) | Samsung C27HG70 |
Case | Xigmatek Aquila |
Power Supply | Seasonic 760W SS-760XP |
Mouse | Razer Deathadder 2013 |
Keyboard | Corsair Vengeance K95 |
Software | Windows 10 Pro |
Benchmark Scores | 4 trillion points in GmailMark, over 144 FPS 2K Facebook Scrolling (Extreme Quality preset) |
In brief:
Installed Crucial M4 with the SATA controller in RAID mode, drive not in raid. No other SATA drives attached. Installed Windows 8 which ran without issue for quite a while until (no hardware or driver changes), it would occasionally crash and fail to identify itself in BIOS. Rebooting a few times would cause it to reappear, but it would try to load Windows, then BSOD. Clearing the BIOS and setting my old settings again changed nothing, but I HAVE managed to get it stable by setting the SATA controller to "Legacy IDE". Now my speeds are terrible (150 MB/s) and everything feels slow, but I don't have to worry about it not recognizing.
All Googling efforts have turned up something to the effect of "Flash the new 0009 firmware. It's much more stable!". The M4 came from Newegg with 040H firmware, which is currently the latest firmware available.
I've occasionally see people suggest "Do a secure wipe and reinstall", but I don't quite see how that would affect it being recognized in BIOS.
I'm wondering if simply re-flashing the same firmware will help. It seems like something's borked in that department.
Info:
DFI LanParty DK 790FXB-M3H5 (AMD 790FX, SB750)
Crucial M4-CT256M4SSD2, 040H Firmware
Windows 8 Pro 64-bit
Troubleshooting steps already taken:
Swap cable
Swap port
Prime95, Memtest, etc
Unplug drive for an hour
SMART short self test ("Completed without error.")
Installed Crucial M4 with the SATA controller in RAID mode, drive not in raid. No other SATA drives attached. Installed Windows 8 which ran without issue for quite a while until (no hardware or driver changes), it would occasionally crash and fail to identify itself in BIOS. Rebooting a few times would cause it to reappear, but it would try to load Windows, then BSOD. Clearing the BIOS and setting my old settings again changed nothing, but I HAVE managed to get it stable by setting the SATA controller to "Legacy IDE". Now my speeds are terrible (150 MB/s) and everything feels slow, but I don't have to worry about it not recognizing.
All Googling efforts have turned up something to the effect of "Flash the new 0009 firmware. It's much more stable!". The M4 came from Newegg with 040H firmware, which is currently the latest firmware available.
I've occasionally see people suggest "Do a secure wipe and reinstall", but I don't quite see how that would affect it being recognized in BIOS.
I'm wondering if simply re-flashing the same firmware will help. It seems like something's borked in that department.
Info:
DFI LanParty DK 790FXB-M3H5 (AMD 790FX, SB750)
Crucial M4-CT256M4SSD2, 040H Firmware
Windows 8 Pro 64-bit
Troubleshooting steps already taken:
Swap cable
Swap port
Prime95, Memtest, etc
Unplug drive for an hour
SMART short self test ("Completed without error.")