Sign in with
Sign up | Sign in
Your question
Closed

Marvell port failure....is there a workaround?

Last response: in Motherboards
Share
August 19, 2012 9:36:39 PM

Hello,

My Asus laptop (specs below) performed beautifully using AHCI for a year and a half. Yesterday when I press the power button to cold boot, the BIOS screen shows up, then I get a black screen with a blinking horizontal cursor in the upper left. That's it.

I went into the BIOS and changed the SATA Configuration to IDE, reboot. It booted into Windows 7x64, no problem.

I tried booting to USB flash drive and doing Windows startup repair, no go. It won't even recognize the SDD unless I go back and switch the BIOS to IDE.

There are two HD bays in my laptop: when it used to work, only one of the two bays would work with the SDD using AHCI. I'm guessing this is the Marvell port?

So besides seeing if Asus will replace the mobo, is there anything else I can try that might solve this problem?

BTW this is a great forum!

Asus G73-JW
Intel i7 740 1.73 GHz
Crucial C300 128GB SSD w/ firmware v7
Seagate HDD 500GB
August 19, 2012 9:36:39 PM

Hello,

My Asus laptop (specs below) performed beautifully using AHCI for a year and a half. Yesterday when I press the power button to cold boot, the BIOS screen shows up, then I get a black screen with a blinking horizontal cursor in the upper left. That's it.

I went into the BIOS and changed the SATA Configuration to IDE, reboot. It booted into Windows 7x64, no problem.

I tried booting to USB flash drive and doing Windows startup repair, no go. It won't even recognize the SDD unless I go back and switch the BIOS to IDE.

There are two HD bays in my laptop: when it used to work, only one of the two bays would work with the SDD using AHCI. I'm guessing this is the Marvell port?

So besides seeing if Asus will replace the mobo, is there anything else I can try that might solve this problem?

BTW this is a great forum!

Asus G73-JW
Intel i7 740 1.73 GHz
Crucial C300 128GB SSD w/ firmware v7
Seagate HDD 500GB
Score
0

Best solution

a b Ĉ ASUS
a b V Motherboard
August 19, 2012 10:12:59 PM

it would be using the Intel SATA ports i have never seen a laptop with an extra controller for additional SATA ports just to chew more power and leave the chipset SATA ports unused etc

i would focus on the windows not booting correctly in the mode you requested - run all hardware tests test everything, in IDE mode boot into windows do chkdsk (chkdsk %systemdrive% /r) and sfc (sfc /scannow), also perhaps look into this:

http://communities.intel.com/thread/30411

1) Run the Registry Editor (regedit.exe)
2) Navigate to Registry Key: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Msahci
3) Set the "Start" value to 0 (zero)
4) Navigate to Registry Key: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Pciide
5) Set the "Start" value to 0 (zero)

I use this all the time to re-configure poor user built systems to allow AHCI post-install for any NT6 machine (VISTA/7 and even 8 since they all use the same core aka 99% the same OS).

Also make sure your SSD firmware is up to date.

best of luck.
Share
Related resources
a b Ĉ ASUS
a c 168 V Motherboard
August 19, 2012 10:39:03 PM

It's pretty rare for laptops to use add-in storage controllers because the Intel chipsets provide more than enough SATA ports. The HM55 chipset provides up to 4 SATA ports and I don't see any mention of an add-in controller on the Asus webpage.

If it suddenly bit the dust this could point to either a PCH failure (chipset) or a drive failure. Use a process of elimination to find the fault and RMA the relevant component.
Score
0
August 19, 2012 11:02:18 PM

Thank you!

I ran chkdsk, no problems there. But sfc found some corrupt files that it could not repair. Here is one of the areas of the CBS Log file that describes the corrupt files found:



2012-08-19 17:47:00, Info CSI 0000029c [SR] Verify complete
2012-08-19 17:47:00, Info CSI 0000029d [SR] Verifying 100 (0x0000000000000064) components
2012-08-19 17:47:00, Info CSI 0000029e [SR] Beginning Verify and Repair transaction
2012-08-19 17:47:01, Info CSI 0000029f Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-n..ce_iassdo.resources_31bf3856ad364e35_6.1.7600.16385_en-us_e86c80b89a3f77b7\iassdo.dll.mui do not match actual file [l:28{14}]"iassdo.dll.mui" :
Found: {l:32 b:tfmxBgEeHYSqU0nOhrdrRtqL98a1xYC32if7l90WiOg=} Expected: {l:32 b:hLMYgoYEaSd6WHNAcMpQlj3ndwYSJanHCJ0EaEjgsTg=}
2012-08-19 17:47:01, Info CSI 000002a0 [SR] Cannot repair member file [l:28{14}]"iassdo.dll.mui" of Microsoft-Windows-Networking-Internet_Authentication_Service_Iassdo.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2012-08-19 17:47:01, Info CSI 000002a1 Ignoring duplicate ownership for directory [l:58{29}]"\??\C:\Windows\SysWOW64\uk-UA" in component Microsoft-Windows-mlang.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"uk-UA", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral

2012-08-19 17:47:01, Info CSI 000002a2 Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-n..ce_iassdo.resources_31bf3856ad364e35_6.1.7600.16385_en-us_e86c80b89a3f77b7\iassdo.dll.mui do not match actual file [l:28{14}]"iassdo.dll.mui" :
Found: {l:32 b:tfmxBgEeHYSqU0nOhrdrRtqL98a1xYC32if7l90WiOg=} Expected: {l:32 b:hLMYgoYEaSd6WHNAcMpQlj3ndwYSJanHCJ0EaEjgsTg=}
2012-08-19 17:47:01, Info CSI 000002a3 [SR] Cannot repair member file [l:28{14}]"iassdo.dll.mui" of Microsoft-Windows-Networking-Internet_Authentication_Service_Iassdo.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2012-08-19 17:47:01, Info CSI 000002a4 [SR] This component was referenced by [l:266{133}]"Microsoft-Windows-WindowsFoundation-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~6.1.7600.16385.Windows Foundation Language Pack"
2012-08-19 17:47:01, Info CSI 000002a5 Hashes for file member \??\C:\Windows\SysWOW64\en-US\iassdo.dll.mui do not match actual file [l:28{14}]"iassdo.dll.mui" :
Found: {l:32 b:tfmxBgEeHYSqU0nOhrdrRtqL98a1xYC32if7l90WiOg=} Expected: {l:32 b:hLMYgoYEaSd6WHNAcMpQlj3ndwYSJanHCJ0EaEjgsTg=}
2012-08-19 17:47:01, Info CSI 000002a6 Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-n..ce_iassdo.resources_31bf3856ad364e35_6.1.7600.16385_en-us_e86c80b89a3f77b7\iassdo.dll.mui do not match actual file [l:28{14}]"iassdo.dll.mui" :
Found: {l:32 b:tfmxBgEeHYSqU0nOhrdrRtqL98a1xYC32if7l90WiOg=} Expected: {l:32 b:hLMYgoYEaSd6WHNAcMpQlj3ndwYSJanHCJ0EaEjgsTg=}


So how do I get my drive straightened out?
Score
0
August 19, 2012 11:40:07 PM

Best answer selected by jkrump.
Score
0
August 19, 2012 11:41:17 PM

After doing the above, I tried rebooting in AHCI and guess what....success! So apparently SFC found something and fixed it...thanks for the explanation and help!
Score
0
August 19, 2012 11:43:30 PM

Thanks! I had accidentally double-posted this thread, and thanks to your info and a user's info from the other thread, I found that running "sfc" fixed something that was messed up on my SSD. I rebooted with AHCI setting in bios, and voila.
Score
0
a b Ĉ ASUS
a c 168 V Motherboard
August 20, 2012 1:08:21 AM

Quote:
Thanks! I had accidentally double-posted this thread, and thanks to your info and a user's info from the other thread, I found that running "sfc" fixed something that was messed up on my SSD. I rebooted with AHCI setting in bios, and voila.


terrific
Score
0
August 20, 2012 2:27:36 AM

Best answer selected by jkrump.
Score
0
a b Ĉ ASUS
a c 328 V Motherboard
August 20, 2012 2:54:44 AM

This topic has been closed by Nikorr
Score
0
a b Ĉ ASUS
a c 328 V Motherboard
August 20, 2012 2:57:42 AM

This topic has been closed by Nikorr
Score
0
a c 262 Ĉ ASUS
a c 990 V Motherboard
August 21, 2012 3:27:36 AM

This next topics has been merged by Area51reopened
  • Marvell port failure....is there a workaround?
    Score
    0
    !