samsung series 7 seems to wake up with lid closed upon a light tap

it was never doing this before...

and I still can't access BIOS via f2- its giving me windows boot loader instead. only way I can access BIOS is taking computer apart and taking out the hard drive. how can I fix this? its got nothing to do with fastboot being on or off (although its set to on)

this laptop is giving me a hard time in some areas... still runs but becomes very glitch. R525 in comparison had no problems...

why is it turning on when closed?

 

Most likely the NVRAM used by your BIOS was corrupted. It is a common problem on some models and causes the symptoms you described here and in other threads. (Although I admit turning on by itself is a new one I haven't heard before, and could be something else).

Check the Samsung Forum Sticky List (on top of the Samsung forum) and look for a link called "F-keys don't work, cannot enter BIOS" (or something like that). Study that thread and follow the steps in the linked guide. That will clear the NVRAM and solve the problem.

It requires some work, including disconnecting the HDD (as you discovered), creating a WinPE USB stick (or any form of Windows that you can boot) and locating a BIOS update file for your model. If you are NOT already on the latest BIOS version, you just run the BIOS update file. If you ARE already on the latest, you need to extract the flashing utility from the BIOS update file and run it with parameters to clear the NVRAM.

It's all covered in that guide.

 

ok I found out what finally opened it-in device manager the mouse was set to wake up device. unchecked that its been much better since

I can enter bios if I take out the hard drive and boot without... why would NVRAM become corrupt?

I believe my particular 700z5b has 15A bios version... most recent. tiredto update and downgrade and I couldn't make out- I've been struggling with CMD commands lately

 

Yes, that makes sense being the mouse waking it up.

The reason I suggest looking into clearing NVRAM is because you said you are unable to get into BIOS with F2. That is usually a symptom of NVRAM having been corrupted, which tends to occur on certain generations of Samsung laptops when UEFI mode has been enabled and operating systems are installed or updated (processes which write the NVRAM).

I saw your earlier thread, linked below:

http://forum.notebookreview.com/threads/cannot-access-bios-on-series-7-after-dead-battery.799830/

Many users only notice long after the corruption first occurs, when they can't boot after updating or installing Windows or Linux. At that point it can be hard to fix, because you need Windows to run the BIOS updater and/or BIOS flashing utility. Indeed, some users effectively bricked their laptops this way because they were unable to boot anything, even though the machine was still technically alive.

So, if F2 isn't working to get into BIOS, AND you are still able to boot Windows, I would recommend clearing NVRAM while it is still relatively easy to do so.

Your particular model is the same generation as my NP700Z3A. The generation of Samsung laptops that is most prone to NVRAM corruption is later -- when Samsung first began delivering UEFI-installed Windows. But it is possible that this UEFI vulnerability was present already in earlier models, just not as common because UEFI was disabled by default. Indeed, we DO recommend keeping UEFI disabled on laptops that had it disabled from factory (generally laptops delivered with Win7).

I don't recall reports of members clearing NVRAM on your generation -- and I have not had a need to do so myself. It is entirely your call whether you want to pursue that. I suppose there is some risk, though I think it is minor. If I were unable to enter BIOS with F2, I would do it on my own on my NP700Z3A.

The topic is discussed in many threads here, but the main one that also contains the NVRAM clearing procedure is the one linked in the Samsung Forum Sticky list. For convenience, I also include it below. The link is to a guide in post #7, but the entire thread should be studied:

Unbrick when F-keys don't work at boot, cannot enter BIOS

Edit: Just to repeat: While updating/downgrading BIOS is the easiest way to clear NVRAM, you don't have to. Running the flashing utility with the right parameters will do it too. As described in that thread.

 

oh no...

so... the boot got corrupted again... F1 to continue F2 for set up, I pick f2 and I get boot menu... enable legecy bios and its good to go. but it never saved my boot.

then I pick f1 when it boots again... boot loop.

so I take the computer apart detach the SSD to get to the bios menu... now its not detecting my harddrive at all!

what happened? what can I do to fix?

welll thats scary.... I believe my sata cable is getting weak from all the pulling out. I found a used one on on ebay and was able to tweak the old one to boot up after taking out harddrive and switching legacy boot back on

strange how the computer crashed, giving me the black screen "F1 to continue F2 for set up" I'd have bios again when I got f2 and I would switch the boot back on... but it would never save. then in f1 it bootloops only for me to pull out the harddrive, get to BIOS, switch it and back to no BIOS on f2 and windows boot loader instead. btw my laptop won't boot properly unless if ufei boot is enabled

NVRAM you say? my cmd skills haven't been very good, is their an easier way?

 

Once again I recommend you clear your NVRAM while you can still boot Windows. If you find yourself in a situation where you are unable to boot Windows (from HDD or USB stick) your laptop will be a brick.

If you were NOT already on the latest BIOS version, simply updating to the latest will clear NVRAM. But you already said you are on the latest version.

In that case, the only procedures I know are the one I previously gave you -- and ones that are much harder and require programming of your BIOS chip using external hardware.

It DOES does require a command line AND strictly following several procedures linked in the guide. If you are not comfortable with that (which I can understand) then I recommend finding a friend or family member who is.

My previous disclaimer remains: Your model is not one that is normally prone to this UEFI triggered issue, and I suppose the problem could be something else in your case. But your symptoms are the well known ones of corrupted NVRAM, and you HAVE been running in UEFI mode (based on your posting). Once again, if this were on my NP700Z3A (same generation as yours) I would do it immediately.

 

I moved your question to the NVRAM clearing thread ( here) and posted my answer there.