Bad SSD or Windows 7 Install?

G

Guest

Guest
I just installed Windows 7 on my new Samsung 840 Evo. Everything seemed to be fine, besides one little blurb where my network connection conked out right after the install. I restarted and it was fine. About an hour after the install random things started crashing though. Windows Media Service, Firefox, and random system processes just started failing. I'm guessing it's not my installation media cause it's a brand new Win 7 disc. Does anyone have any ideas why my system install is so messed up? I have an Asus P6T Deluxe v2 motherboard with the latest bios.
 
Solution


I know, it's weird, and I think Monster cables are a joke. But I think it's possible.
The SSDs transfer at a much faster rate, almost saturating the SATA interface, so it would be pushing the limits of the cable too, requiring cleaner signals at faster rate on the wires. Your old SATA cables could have been specified to work with older SATA2 devices but not SATA3. That's how mine was.

hp79

Distinguished
Feb 6, 2006
173
0
18,710
Are you using a good quality SATA cable? I had some random problems after about 6 months of normal use. I finally replaced the SATA cable to SATA3 labeled cable that came with my ASUS motherboard, and reimaged the SSD from a backup image. After that no more problems. So it was the cable in my case.
 
G

Guest

Guest
Yeah, it was a fresh install. I just mounted the drive in my tower, and installed Windows off the new disc. As for Sata cables, could that really be the problem? The cables are about 4 and a half years old now I guess; they're the ones that came with the motherboard. They seemed fine with my hdd though.
 

hp79

Distinguished
Feb 6, 2006
173
0
18,710


I know, it's weird, and I think Monster cables are a joke. But I think it's possible.
The SSDs transfer at a much faster rate, almost saturating the SATA interface, so it would be pushing the limits of the cable too, requiring cleaner signals at faster rate on the wires. Your old SATA cables could have been specified to work with older SATA2 devices but not SATA3. That's how mine was.
 
Solution