Clevo P150SM-A, Windows 8.1 update and no BIOS, etc

Hi

I have installed the last series of Win 8.1 x 64 updates on my Clevo P150SM-A (with Prema Mod BIOS - it was working OK for several month w/o any issues before this damned 8.1 update) and now when I switch the computer on I can't see Prema Bios Logo and it seems that LCD does not get any signal... tried to reboot pressing F2/F8 still can't get into BIOS... notebook itself seems to be switching on - fan is working, keyboard is illuminated with some blue light, LCD seems to get some light/switches on, I can see HDD light and hear it as it is working /primary is SSD, but 2nd is a regular HDD/ - but nothing comes on screen (and as I noted - no Prema Bios Logo)... any recommendations about what to do ?

 

OK. I removed mSATA drive - now I can go into Prema Mod bios at least... but what I do from there ? how to fix whatever is/went wrong with the Windows 8.1 on mSATA drive ?

 

the issue is when both the primary mSATA and HDD are in.. if I leave only the primary mSATA then everything is working (and HDD too if I put it into external mSATA to USB enclosure)... so both hard drives seems to be fin.. however once I move HDD back into its SATA slot inside notebook I am getting back to square one... WTF ?! when I put a different HDD in SATA slot, everything again works fine... the problem so is just when apparenlty fine original HDD is put back inside notebook when mSATA remains primary one to boot from (but as I can't get into BIOS in such configuration, I can't verify that)...

 

Installed Windows when both drives were present in the system? If so, then there's probably a boot section on the non-OS drive as well; make image, format drive and copy back data using the mounted image (so don't write back image itself).

 

How do you have things installed on these drives? I ran into a very similar issue when I tried having an install of Windows 7 on a SSD and Windows 8.1 on my M.2 SSD for my P650SG. I would not see the Sager BIOS splash and the monitor would act like it wasn't receiving any signal but the computer acted like it was turned on. If I removed the Windows 7 drive it would boot properly. So I ended up taking formatting the Windows 7 drive in a different PC and it worked.

 

no, not installed - Windows 8.1 was there already for several month booting just fine from primary mSATA - just installed a bunch of new M$ patches ... I fixed the issue...it involved several inserting/reinserting of the HDD and one time I was able to get into Prema BIOS and removed HDD from booting options altogether (even before that it was not the first drive in sequence)... so it is working now... but it was stressful.

 

I purchased Clevo from ProStar like this with 8.1 installed already on mSATA (primary) and HDD (second drive) - both drives were installed by ProStar... then I just installed 8.1 Pro on mSATA (fresh install - totally removed everything prev. - but if there were any hidden partions somewhere on the 2nd regular HDD they probably remained, I do not remember the details)... then I installed Prema Mod Bios to deal with fans (that Mod is working just beautiful by itself)... I am totally not an expert but I was under impression that somehow the thing tried to boot from HDD not from mSATA and not being able to find anything bootable on HDD it was also locking me out of regular BIOS access... how exactly did I fix this I even do not know - but it involved a lot of exchanges of HDDs (the original that was the issue and a different one) between inside notebook and outside enclosure and rebooting while trying to press Fn to get into the BIOS (note that no issues were when the right HDD was either in external enclosure or not present at all - but then I couldn't make it unavailable for any booting process in BIOS - I had to be able to get into BIOS when it was inside notebook as a native SATA drive visible to BIOS)... at some point in time it worked with the right HDD inside notebook and then I just removed it from any booting sequences in BIOS and also put an option to turn fast boot off (or how this is called in BIOS)...

 

You want to make sure they share the same boot partition of a drive, if you have two boot partitions that will cause issues.