baymavi - vevobahis - mobilbahis - https://guncelgirisi.com/. instagram takipçi satın al - instagram takipçi satın al mobil ödeme

Announcement

Collapse
No announcement yet.

Bios not recognize the "Phonix Pro"

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Bios not recognize the "Phonix Pro"

    i have the "Phonix Pro" - FM-25s2s-60gbp2 more then 6 months
    yesterday the computer froze,
    and i tried to restart,but then the bios didn't recognize the SSD,and course windows,
    it's caught me suddenly,and not ready,so i didn't backup my data,

    Is there any chance to save the data?
    what should i do at this point?

    plz help me,i am lost
    Tnx.

  • #2
    Try a different port and/or SATA cable to see if it can detect it.

    If not, send it in for RMA.

    http://www.gskill.com/rma.php

    Thank you
    GSKILL TECH

    Comment


    • #3
      Originally posted by GSKILL TECH View Post
      Try a different port and/or SATA cable to see if it can detect it.

      If not, send it in for RMA.

      http://www.gskill.com/rma.php

      Thank you
      GSKILL TECH
      I tried different cables and every ports on my mobo
      i even tried to connect the SSD with "stata to usb" adapter
      and windows show the name of the drive (FM-25s2s-60gbp2)
      but unfortunately i can't enter to my drive,

      i must say when the drive is connected to the computer,
      It's takes 10 seconds more to start the POST
      and it's looks like he thinks too much,

      Is there any chance?

      Comment


      • #4
        hi

        still can't get into windows and backup your data? usually people will using SSD for system drive,
        not data drive because once the SSD occurred problems, most of the time the data will not be able to recover. as you mentioned tried both SATA/USB, please also try it as the second drive to see if you can save the data and using other computer for one more test, if still not working, please following the sticky thread to erase all the drive and re-install firmware again.

        Comment

        Working...
        X