|17 Aug 2012||#1|
| || |
Possible faulty HDD cables causing BSODs. Opinions?
I thought it was about time I looked for help on these forums directly, instead of just lurking around attempting to glean information off other peopleís issues for the last year and a bit. Sorry for the long post in advance, i just want to get as much information out there as possible.
Long story short, early last year i purchased a new computer from a custom builder for almost $4000. Ever since i received it, iíve been getting BSODís. The builders never found an issue with it (something i doubt) and because of their lack of interest in following through with my problems, the manufacturers warranty has run out. Iíve re-installed windows multiple times to no avail, updated drivers, run memtests, HDD tests, the lot.
The BSODís that i could pinpoint, i found fixes for, which didnt seem to help because the errors just came from somewhere else.
Excessive (30 gigs) data transfer used to cause BSODís, which was fixed by turning off USB3 support.Running Checkdisk scans on my hard drives would report hundreds of corrupted files and sectors, which were all fixable, but kept appearing after subsequent crashes corrupted new ones. The hard drives are perfectly healthy, with no bad sectors on multiple assessment programs. Iíve also had parts of windows corrupt that were active during a crash - notably the .NET 2.0 framework which was notorious to repair. Windows once bricked itself (i couldnt even use the Installation DVD to repair it) and i had to reformat the C:\ drive outside of the machine because it wouldnt even recognise the partition the OS was on.
Iíve also started having these odd issues with drive letters and paths - i run most of my music and video libraries off external drives, and windows seems to consistently change the paths from upper-alphabet letters (H:\, I:\, K:\, etc) to lower-alphabet ones (W:\, X:\, Y:\, Z:\, etc). Changing them back in Disk Management doesn't help - windows always switches them back on reboot.
My internal secondary hard drive often disappears from my computer too, prompting me to scan for hardware changes in order to re-find it. This has been recently happening to the local C:\ drive as well, but windows typically locks up and displays per-program file access errors before i can do anything about it.
Each BSOD (when they generate minidump files, which is now a rarity), traced through Bluescreen viewer, seems to point to a random array of drivers and files in the system folders. Iím beginning to think these have less to do with the causing the crash, and more to do with just being the files that were accessed when the error occurred.
Iíve tested my hardware for errors for going on a year and a half now, and they all still report fine. I ran a memtest pass post-boot for 15 hours, getting through 3 passes with no errors. My CPU and GPU are often put under strain and never seem to cause issues (oddly preventing them - rendering scenes for a short film took four days non-stop, and it didn't BSOD once). The HDDís have perfect health in short tests, longer tests don't seem to complete before a BSOD interrupts it, which recently made me think.
I ran a SMART test on both internal HDDs (via HDD scan), and the only issues it brought up were alert signs next to ďUltraDMA Cyclic Redundancy Check ErrorsĒ, which Google said represented ďThe count of errors in data transfer via the interface cableĒ.
Seeing as my PC is quite high-end, and and such all the cabling has been pleated and hidden away - would all these issues be pointing to damaged cables connecting the hard drives to the motherboard? I gather being stretched and tugged wouldn't have been good for them during the initial build.
Thoughts? Sorry if this is phrased wrong, doesnt have enough info, or posted in the wrong place, iím new
I've attached as much info as i could from the SF Diag tool, it couldn't find any minidumps for some reason, but i have a locked folder in my secondary hard drive filled with 139 megs of large .dmp files, if that would help.
|My System Specs|
|17 Aug 2012||#5|
| || |
Motherboard: ASUS Sabertooth Intel X58 DDR3 USB3 + SATA3 PCI-E
CPU: Intel Core i7 970 Bloomfield 3.20Ghz 12MB 1333Mhz LGA1366
RAM: Corsair CMZ12GX3M3A1600C9 12GB (3x4GB) DDR3-1600
Optical: LG CH10LS20 10X Blu-ray Reader Lightscribe Black SATA
HDD: Samsung Spinpoint F3 1TB 32MB 7200rpm SATAII (two)
GPU: ASUS nVidia Geforce GTX580 DirectCU II 1536MB GDDR5 PCI
PSU: Corsair HX750 750W Modular Power Supply
|My System Specs|
|17 Aug 2012||#6|
| || |
Sabertooth X58 1304 BIOS Improve stability on Marvell controller Download from here: ASUS - Motherboards- ASUS SABERTOOTH X58
Using EZ Flash 2:
EZ Flash 2 is a built-in function of BIOS. It is the safest way to update BIOS, because one is not dependent on the operating system, any application, internet connection, firewall settings, antivirus or anything else that can put the vital BIOS update at risk.
On a new build, BIOS can be updated to the latest version before installation of the OS, which may possibly make the installation go smoother and safer.
Note: All what's said below about loading BIOS defaults also applies to the other BIOS update methods (ASUS Update, AFUDOS and BUPDATER)!
The PC should not be overclocked during the BIOS update! Always load and save BIOS defaults before and after a BIOS update (press <F5>). By loading and saving BIOS defaults before the update, CPU frequency, memory frequency and voltages are set to default (Auto).
Memory timings are set to SPD values which ensure that a PC with high performance memory that need a higher voltage than 1.8V for DDR2 or 1.5V for DDR3 is able to boot on the standard Memory Voltage. Save the default settings (press <F10>) before starting the update.
|My System Specs|
|Similar help and support threads for2: Possible faulty HDD cables causing BSODs. Opinions?|
|Multiple BSODs on boot, Faulty RAM?||BSOD Help and Support|
|Suspect faulty BIOS and First-Boot BSODs||BSOD Help and Support|
|Faulty heatsink causing computer shut down within seconds of starting?||General Discussion|
|Netbook, faulty screen or screen cables. Second opinion needed.||Hardware & Devices|
|Random BSODs - faulty RAM?||BSOD Help and Support|
|Suspect new HDD causing BSODs, please help?||BSOD Help and Support|
|athrxusb.sys causing BSODs need help||Network & Sharing|
|Our Sites ||Site Links ||About Us ||Find Us |
© Designer Media Ltd
All times are GMT -5. The time now is 09:04 PM.