Sign in with
Sign up | Sign in
Your question
Solved

Possible SATA port problems

Tags:
  • Motherboards
  • Seagate
Last response: in Motherboards
Share
June 18, 2014 10:27:22 AM

Specs:

MoBo: ASUS P8Z77-V LK
CPU: Intel i5-3570k 4.2 ghz 1.250 Vcore
RAM: Kingston HyperX Black 1600 MHz, 16GB total
Storage: Intel 240GB SSD
Seagate Barracuda 7200.14 2TB Hard Drive
Seagate SSHD 500 GB
GPU: EVGA Geforce GTX 760 4 GB Dual FTW
PSU: Seasonic 650W 80+ Gold

I have this weird intermittent issue where my PC will lock up for long periods of time, 5-10 seconds, before rebooting and losing my OS disk (Intel 240 GB SSD) in the bios. Reconnecting power or data solves issue temporarily. Any ideas as to the cause? I'm thinking it's either a SATA cable or SATA port on the motherboard acting weird. I've just swapped my SSHD and SSD ports to see if it fixes the issue with the SSD, if not, SATA cables are next.

It's thrown BSOD's before. The latest one was from system services terminating.

More about : sata port problems

a c 516 V Motherboard
June 18, 2014 10:53:25 AM

What do you mean by "losing" your OS disk? Does C: drive disappear in Win File Explorer?

Is the Win (7?) a clean install on the SSD or a clone from the HDD?
m
0
l
June 18, 2014 12:51:50 PM

It's a clean install on the SSD, I'm not dumb enough to clone it. By losing, I mean the BIOS won't see it.
m
0
l
Related resources
a c 516 V Motherboard
June 18, 2014 1:03:39 PM

I have cloned a SSD from my HDD before. I don't consider myself dumb. But, like any SSD/Win7 installation, you will want to do these tweaks to get the most performance from the SSD and keep it from writing itself to an early death: http://www.computing.net/howtos/show/solid-state-drive-...

Did you say you had a Hybrid SSD/HD too? If so, that is usually intended to be used as a boot drive. It contains non-volatile memory used at a persistent cache for booting the OS. That may be an issue... I'm not sure. Ive never used a persistent cache HDD with a separate SSD. Anyway...

So Win7 sees and boots to the SSD, but it doesn't show up in BIOS? How is that even possible? How did you manage to set the SSD as the boot drive in BIOS if it didn't show up?
m
0
l
June 18, 2014 1:08:48 PM

No, It's happening periodically. Like, I'm using the OS now on the SSD.

Sometimes my PC will lock up for 5-10 seconds at a time with short breaks in between with DPC's and interrupts consuming all of my CPU. Then it resets or BSODs and boots the SSHD because the BIOS can no longer see the SSD. I reconnect the data or the power to the SSD and presto, problem solved until it happens again.


SSD used to be on INTEL SATA 6.0 Gbps port 1. I'm seeing if that port is going bad, if it's the cable, that'll be the next thing I test. If it's my intel controller, I'm fucked as those are my only 2 6.0 Gbps ports. If it's my SSD I can RMA that to intel.

I've already done all that in the link and more. Intel recommends that write buffer caching be on, however.
m
0
l
a c 516 V Motherboard
June 18, 2014 1:12:54 PM

You didn't answer my question. Is that a hybrid HDD? How can it boot to the HDD if the OS and boot sector is on the SSD?
m
0
l
June 18, 2014 1:15:11 PM

Storage: Intel 240GB SSD
Seagate Barracuda 7200.14 2TB Hard Drive
Seagate SSHD 500 GB

The Seagate Solid State Hybrid Drive (in my case) has a 500 GB Platter and 8 GB of MLC Nand. It uses the NAND like a read cache. It's not as fast as the intel SSD I have. Not by any stretch of the means. I also have win 7 installed to the SSD, which i got recently. I have HAD the SSHD for a while now, and as such, it too has an OS on it.
m
0
l
a c 516 V Motherboard
June 18, 2014 2:10:36 PM

I see problems in the making with 2 boot drives. One in use as C: drive and the other used as a storage drive. Both drives have a boot sector. I presume you have the SSD enabled as the 1st hard drive in BIOS? And it is set as the first boot device in BIOS?
m
0
l
June 19, 2014 8:59:22 AM

Correct.
m
0
l
a c 516 V Motherboard
June 19, 2014 12:01:00 PM

If you unplug the SATA cable from the hard drive, does the SSD boot to Windows normally?
m
0
l
June 19, 2014 3:40:14 PM

Yes. It boots fine, except when the system has problems on the SSD when it's running and in windows, and then reboots and BSOD's. Then I have to reconnect the SSD and the BIOS will see it again, and everything works fine.

The issue I'm having is the SSD runs fine for x amount of time, but crashes and throws random BSOD errors. The other day it was STOP code 0xF4. It's been a different STOP Code every time. I think it's about to do it now.
m
0
l
a c 516 V Motherboard
June 19, 2014 5:26:57 PM

I presume both drives are in the grey SATA ports? Latest IRST driver? http://www.intel.com/p/en_US/support/highlights/sftwr-p...
- or - https://www.asus.com/Motherboards/P8Z77V_LK/HelpDesk_Do...
Have you gone through and optimized the SSD? http://www.computing.net/howtos/show/solid-state-drive-...
I suppose you should be sure you have the latest MB BIOS. I see there have been several updates to "Improve system stability".
m
0
l
June 19, 2014 6:21:29 PM

Yes, Yes, Yes, I don't update my BIOS because the last time I did that to a motherboard it resulted in a non-working board. Has BIOS Flashing stability improved at all, does it still run a risk of problems?
m
0
l

Best solution

a c 516 V Motherboard
June 19, 2014 6:37:47 PM

The first thing I do when I get a board is check if there are any BIOS updates. If there are, I do them. Never once in all my years had a problem. And now, you can do it right thru Windows. Page 3-34 starts the explanation of the various options Asus provides for updating the BIOS. I have always used Asus Update for my Asus boards. (in AI Suite II)
Share
June 21, 2014 5:49:36 AM

Is it possible that we skip updating BIOS?
m
0
l
a c 516 V Motherboard
June 21, 2014 11:58:18 AM

squish8294 said:
Is it possible that we skip updating BIOS?


Sure, your decision.
m
0
l
June 26, 2014 2:18:14 AM

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: f4
BCP1: 0000000000000003
BCP2: FFFFFA8010CE6B30
BCP3: FFFFFA8010CE6E10
BCP4: FFFFF800021CF270
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\062614-32744-01.dmp
C:\Users\Squish\AppData\Local\Temp\WER-32807-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0...

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt


There's the BSOD from it happening again - it's not the MoBo port, now we're checking the SATA data cable.

I'm downloading WinDbg now to debug the kernel dump.


Here's the stuff from the debugger:


  1. Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
  2. Copyright (c) Microsoft Corporation. All rights reserved.
  3.  
  4.  
  5. Loading Dump File [C:\Windows\Minidump\062614-32744-01.dmp]
  6. Mini Kernel Dump File: Only registers and stack trace are available
  7.  
  8. Symbol search path is: srv*
  9. Executable search path is: srv*
  10. Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
  11. Product: WinNt, suite: TerminalServer SingleUserTS
  12. Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
  13. Machine Name:
  14. Kernel base = 0xfffff800`01e54000 PsLoadedModuleList = 0xfffff800`02097890
  15. Debug session time: Thu Jun 26 03:55:59.023 2014 (UTC - 5:00)
  16. System Uptime: 1 days 13:20:26.538
  17. Loading Kernel Symbols
  18. ...............................................................
  19. ................................................................
  20. .........................................
  21. Loading User Symbols
  22. Loading unloaded module list
  23. ......
  24. *******************************************************************************
  25. * *
  26. * Bugcheck Analysis *
  27. * *
  28. *******************************************************************************
  29.  
  30. Use !analyze -v to get detailed debugging information.
  31.  
  32. BugCheck F4, {3, fffffa8010ce6b30, fffffa8010ce6e10, fffff800021cf270}
  33.  
  34. ----- ETW minidump data unavailable-----
  35. Probably caused by : csrss.exe
  36.  
  37. Followup: MachineOwner
  38. ---------
  39.  
  40. 3: kd> !analyze -v
  41. *******************************************************************************
  42. * *
  43. * Bugcheck Analysis *
  44. * *
  45. *******************************************************************************
  46.  
  47. CRITICAL_OBJECT_TERMINATION (f4)
  48. A process or thread crucial to system operation has unexpectedly exited or been
  49. terminated.
  50. Several processes and threads are necessary for the operation of the
  51. system; when they are terminated (for any reason), the system can no
  52. longer function.
  53. Arguments:
  54. Arg1: 0000000000000003, Process
  55. Arg2: fffffa8010ce6b30, Terminating object
  56. Arg3: fffffa8010ce6e10, Process image file name
  57. Arg4: fffff800021cf270, Explanatory message (ascii)
  58.  
  59. Debugging Details:
  60. ------------------
  61.  
  62. ----- ETW minidump data unavailable-----
  63.  
  64. KERNEL_LOG_FAILING_PROCESS: (null)
  65.  
  66. PROCESS_OBJECT: fffffa8010ce6b30
  67.  
  68. IMAGE_NAME: csrss.exe
  69.  
  70. DEBUG_FLR_IMAGE_TIMESTAMP: 0
  71.  
  72. MODULE_NAME: csrss
  73.  
  74. FAULTING_MODULE: 0000000000000000
  75.  
  76. PROCESS_NAME: csrss.exe
  77.  
  78. EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
  79.  
  80. BUGCHECK_STR: 0xF4_c0000005
  81.  
  82. CUSTOMER_CRASH_COUNT: 1
  83.  
  84. DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
  85.  
  86. CURRENT_IRQL: 0
  87.  
  88. STACK_TEXT:
  89. fffff880`03bf4e38 fffff800`02257ab2 : 00000000`000000f4 00000000`00000003 fffffa80`10ce6b30 fffffa80`10ce6e10 : nt!KeBugCheckEx
  90. fffff880`03bf4e40 fffff800`02202abb : ffffffff`ffffffff fffffa80`127d0b50 fffffa80`10ce6b30 fffffa80`10ce6b30 : nt!PspCatchCriticalBreak+0x92
  91. fffff880`03bf4e80 fffff800`02181f04 : ffffffff`ffffffff 00000000`00000001 fffffa80`10ce6b30 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x17486
  92. fffff880`03bf4ed0 fffff800`01ec8e53 : fffffa80`10ce6b30 fffff800`c0000005 fffffa80`127d0b50 00000000`001a0880 : nt!NtTerminateProcess+0xf4
  93. fffff880`03bf4f50 fffff800`01ec5410 : fffff800`01f1482f fffff880`03bf5a38 fffff880`03bf5790 fffff880`03bf5ae0 : nt!KiSystemServiceCopyEnd+0x13
  94. fffff880`03bf50e8 fffff800`01f1482f : fffff880`03bf5a38 fffff880`03bf5790 fffff880`03bf5ae0 00000000`001a2390 : nt!KiServiceLinkage
  95. fffff880`03bf50f0 fffff800`01ec9242 : fffff880`03bf5a38 00000000`0000d8f4 fffff880`03bf5ae0 00000000`001a1e68 : nt! ?? ::FNODOBFM::`string'+0x488e4
  96. fffff880`03bf5900 fffff800`01ec7dba : 00000000`00000001 00000000`001a0f98 00000000`00000001 00000000`0000d8f4 : nt!KiExceptionDispatch+0xc2
  97. fffff880`03bf5ae0 00000000`77b38e5d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
  98. 00000000`001a0fa0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77b38e5d
  99.  
  100.  
  101. STACK_COMMAND: kb
  102.  
  103. FOLLOWUP_NAME: MachineOwner
  104.  
  105. FAILURE_BUCKET_ID: X64_0xF4_c0000005_IMAGE_csrss.exe
  106.  
  107. BUCKET_ID: X64_0xF4_c0000005_IMAGE_csrss.exe
  108.  
  109. Followup: MachineOwner
  110. ---------
  111.  
  112. 3: kd> lmvm csrss
  113. start end module name



I know that my SSD is AT the root of the problem, I hope it isn't the cause. I don't remember if I've appended this to my post, but I've swapped ports in hopes of it not being a port issue. It was not the case as it BSOD'd again with stop code f4, I've now since changed cables to see if maybe the cable that came with the SSD was the cause. Fingers crossed...
m
0
l
!