The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    Major problem with Samsung notebook and Win 8.1

    Discussion in 'Samsung' started by Lange, Dec 4, 2013.

  1. Lange

    Lange Newbie

    Reputations:
    0
    Messages:
    1
    Likes Received:
    0
    Trophy Points:
    5
    I work in a electroncs store and we have a lot of customers coming in and telling us that when they have tried upgrading to Windows 8.1 their computer breaks down.

    It starts up and before Windows starts a BSOD is shown shortly and then reboots. Again and again.

    The problem is ONLY on Samsung NP530U3C and I think we have received 15 in the last 2 months.

    The strange thing is that I cant even get into the BIOS and try to boot from USB to put a working image on the computer. F2 and F4 doesnt work. Sothe only thing to do for us is to send it to service to have it repaired.

    PLEASE give me advice on what to do as quickly as you can.

    Thanks
     
  2. John Ratsey

    John Ratsey Moderately inquisitive Super Moderator

    Reputations:
    7,197
    Messages:
    28,841
    Likes Received:
    2,165
    Trophy Points:
    581
    You probably need to send it to Samsung. We have various threads such as this with similar problems. I suspect that the bills and feedback from the service centres is the main motivation for Samsung to address these issues.

    Our bricking thread and BIOS Update thread have various suggestions about how to resurrect sulking computers but these have failed to come up with a fix for the 8.1-related problems.

    Samsung and Microsoft need to stop trying to push 8.1 on people until they have got everything debugged. People only find this thread after they have encountered problems. Microsoft have tinkered with things at a low level which then cause BIOS-related problems such as the one you have encountered.

    John
     
    Dannemand likes this.