Jump to content
EwinRacing Flash Series Gaming Chairs
Guest

[BIOS/vBIOS - MODS] Prema Mod™ & Stock

Recommended Posts

Nice! BCLK OC was more trouble than it was worth anyway.

Sent from my SPH-L720 using Tapatalk

  • Thumbs Up 2

Share this post


Link to post
Share on other sites

sir, i found outsite for me firmware for 2012 model is 8.1.65.1586 for now...is that true? what is the diferent? is that ok to update?

is that already included in p37xem/em3 bios?

sorry for so many question

Share this post


Link to post
Share on other sites
Guest
sir, i found outsite for me firmware for 2012 model is 8.1.65.1586 for now...is that true? what is the diferent? is that ok to update?

is that already included in p37xem/em3 bios?

sorry for so many question

Here You go!

I see no reason for it not to work...

ME_8.1.65.1586_Win.rar

Share this post


Link to post
Share on other sites

Hi guys, I was trying to update vBios for my Batman (Clevo 751ZM), regular Bios from Prema updated just fine, but when I was trying to run the vBios .bat file I've got this as a result:

WARNING: Firmware image PCI Subsystem ID does not match adapter PCI Subsystem ID

I was doing this without the nvidia drivers, as I've read somwhere (prema site? not sure thou) that it should be done like that.. I've installed the drivers to check if I have the correct GPU installed and of course it is.. I've tried to to flash it afterwards, still the same error..

TLclear.png: DR should i flash the vbios with or without the nvidia drivers installed? Or it does not matter?

Share this post


Link to post
Share on other sites
Guest
Hi guys, I was trying to update vBios for my Batman (Clevo 751ZM), regular Bios from Prema updated just fine, but when I was trying to run the vBios .bat file I've got this as a result:

WARNING: Firmware image PCI Subsystem ID does not match adapter PCI Subsystem ID

I was doing this without the nvidia drivers, as I've read somwhere (prema site? not sure thou) that it should be done like that.. I've installed the drivers to check if I have the correct GPU installed and of course it is.. I've tried to to flash it afterwards, still the same error..

TLclear.png: DR should i flash the vbios with or without the nvidia drivers installed? Or it does not matter?

Don't worry, that's normal for Clevos even with stock vBIOS. Reason being the BIOS patching the system HWIDs on the fly and not showing the actual ones.

Share this post


Link to post
Share on other sites

Friend of mine had the WARNING: Firmware image PCI Subsystem ID does not match adapter PCI Subsystem ID message whilst updating vbios for his 980m G-Sync and he doesn't know what to do. He can either press "y" to confirm and update the driver firmware, or abort. Is he good to press Y?

Hi all,

Friend of mine tried to flash his 980m G Sync GPU with Premamod (see my post above, he pressed y if you couldn't guess already!) but something seems to have gone wrong and now his P750ZM doesn't seem to post at all. He's trying to blind flash but he needs the stock vbios for the 980m G Sync.

There is a stock 980m vbios on the premamod website, but I'm not sure if that works for G Sync 980m's too?

CLEVO_8GB_GTX980M_MXM_Stock

Oh, does anyone also know if there is a keyboard combination whilst booting a P750ZM which forces it to boot from USB?

EDIT - Can you even DOS flash a 980m g sync? If you can't then what options are available to my buddy? :(

Share this post


Link to post
Share on other sites

Hi Prema,

Sorry to trouble you, but I've found something quite odd with my P650SG and the PremaMod BIOS you have released. This morning I upgraded from v1 to v2 of your PremaMod BIOS, but noticed that I could not get into Windows 7 Safe Mode anymore, upon trying to load C:\Windows\system32\drivers\classpnp.sys, the Safe Mode login screen would appear and then immediately reboot the machine. Doing a quick Google search for this appears that is a common problem for some users, called the "classpnp.sys Safe Mode boot loop issue". Further research indicates that it is almost always a hardware issue.

I then reverted back to your v1 PremaMod BIOS, and disconnected all peripherals from my laptop, but I still cannot enter Safe Mode -- I keep getting this classpnp.sys issue. Normal booting into Windows 7 works fine with both v1 and v2, just Safe Mode doesn't work.

I have tried to get into Safe Mode with your Optimised Default BIOS settings for both v1 and v2, but neither work. I have tried disabling the dGPU, but that doesn't work either.

Am not sure why this could possibly be happening, but just thought I'd bring it to your attention. Have you by any chance encountered this issue before? Any possible fixes for it?

Share this post


Link to post
Share on other sites

Hi all,

Friend of mine tried to flash his 980m G Sync GPU with Premamod but something seems to have gone wrong and now his P750ZM doesn't seem to post at all. He's trying to blind flash but he needs the stock vbios for the 980m G Sync.

There is a stock 980m vbios on the premamod website, but I'm not sure if that works for G Sync 980m's too?

CLEVO_8GB_GTX980M_MXM_Stock

Oh, does anyone also know if there is a keyboard combination whilst booting a P750ZM which forces it to boot from USB?

Saw it posted elsewhere that you can't even DOS nvflash the 980m, if that's the case (not sure it is?), then are there any options available...

Share this post


Link to post
Share on other sites

Hey

Did your friend even flash the Bios? You really need to describe as accurately as possible what he did in what order. And it's true you don't to go in dos mode to flash vbios. Also if he did flash bios did he remove AC Power for 30s? Also did he change back UEFI settings if He used them before? Windows wont load if UEFI is turned off.

Share this post


Link to post
Share on other sites
Hi Prema,

Sorry to trouble you, but I've found something quite odd with my P650SG and the PremaMod BIOS you have released. This morning I upgraded from v1 to v2 of your PremaMod BIOS, but noticed that I could not get into Windows 7 Safe Mode anymore, upon trying to load C:\Windows\system32\drivers\classpnp.sys, the Safe Mode login screen would appear and then immediately reboot the machine. Doing a quick Google search for this appears that is a common problem for some users, called the "classpnp.sys Safe Mode boot loop issue". Further research indicates that it is almost always a hardware issue.

I then reverted back to your v1 PremaMod BIOS, and disconnected all peripherals from my laptop, but I still cannot enter Safe Mode -- I keep getting this classpnp.sys issue. Normal booting into Windows 7 works fine with both v1 and v2, just Safe Mode doesn't work.

I have tried to get into Safe Mode with your Optimised Default BIOS settings for both v1 and v2, but neither work. I have tried disabling the dGPU, but that doesn't work either.

Am not sure why this could possibly be happening, but just thought I'd bring it to your attention. Have you by any chance encountered this issue before? Any possible fixes for it?

Just an update to this, I noticed today that I also cannot run the scheduled disk check (chkdsk /F) on the C: drive which you can normally run prior to Windows starting up.

Both of these issues have to do with various boot/startup sequences, and I have a guess at what might be tying these issues together -- the offboard sata controller in the P650SG. I have my C: drive located on an M.2 PCIe SSD, the Samsung SM951, and I've read how the boot loader for this isn't on the SM951 itself, it's actually a string of BIOS hacks in the Clevo BIOS itself.

Prema, may I ask if during your exploration/hacking of the BIOS for the P650SG you see any bootloader or unlockable options for the offboard sata controller?

Share this post


Link to post
Share on other sites

Would anyone here be so kind as to upload a stock 980m G-Sync bios for me please? Can't seem to find it anywhere online..

A friend has an idea about putting the card into his Alienware and booting up with the integrated video then re-flashing in windows

Share this post


Link to post
Share on other sites
Guest
Friend of mine had the WARNING: Firmware image PCI Subsystem ID does not match adapter PCI Subsystem ID message whilst updating vbios for his 980m G-Sync and he doesn't know what to do. He can either press "y" to confirm and update the driver firmware, or abort. Is he good to press Y?

Hi all,

Friend of mine tried to flash his 980m G Sync GPU with Premamod (see my post above, he pressed y if you couldn't guess already!) but something seems to have gone wrong and now his P750ZM doesn't seem to post at all. He's trying to blind flash but he needs the stock vbios for the 980m G Sync.

There is a stock 980m vbios on the premamod website, but I'm not sure if that works for G Sync 980m's too?

CLEVO_8GB_GTX980M_MXM_Stock

Oh, does anyone also know if there is a keyboard combination whilst booting a P750ZM which forces it to boot from USB?

EDIT - Can you even DOS flash a 980m g sync? If you can't then what options are available to my buddy? :(

It is normal to through a HWID mismatch even when flashing stock vBIOS...a couple posts back I just gave the explanation...

He probably waited too long to answer the question with 'yes' and the nvflash lost control over the GPU resulting in a failed flash.

It is important to let the flash complete successfully and wait for the brief message to reboot. If a flash fails it needs to be repeated BEFORE rebooting.

Flashing in DOS is not supported for Maxwell cards by NVIDIA...

Would anyone here be so kind as to upload a stock 980m G-Sync bios for me please? Can't seem to find it anywhere online..

A friend has an idea about putting the card into his Alienware and booting up with the integrated video then re-flashing in windows

Stock vBIOS for GTX980M-G is in the OP and on the blog.

Re-flashing the GPU in a system with Optimus or as slave in an SLI will be no problem.

Hi Prema,

Sorry to trouble you, but I've found something quite odd with my P650SG and the PremaMod BIOS you have released. This morning I upgraded from v1 to v2 of your PremaMod BIOS, but noticed that I could not get into Windows 7 Safe Mode anymore, upon trying to load C:\Windows\system32\drivers\classpnp.sys, the Safe Mode login screen would appear and then immediately reboot the machine. Doing a quick Google search for this appears that is a common problem for some users, called the "classpnp.sys Safe Mode boot loop issue". Further research indicates that it is almost always a hardware issue.

I then reverted back to your v1 PremaMod BIOS, and disconnected all peripherals from my laptop, but I still cannot enter Safe Mode -- I keep getting this classpnp.sys issue. Normal booting into Windows 7 works fine with both v1 and v2, just Safe Mode doesn't work.

I have tried to get into Safe Mode with your Optimised Default BIOS settings for both v1 and v2, but neither work. I have tried disabling the dGPU, but that doesn't work either.

Am not sure why this could possibly be happening, but just thought I'd bring it to your attention. Have you by any chance encountered this issue before? Any possible fixes for it?

Just an update to this, I noticed today that I also cannot run the scheduled disk check (chkdsk /F) on the C: drive which you can normally run prior to Windows starting up.

Both of these issues have to do with various boot/startup sequences, and I have a guess at what might be tying these issues together -- the offboard sata controller in the P650SG. I have my C: drive located on an M.2 PCIe SSD, the Samsung SM951, and I've read how the boot loader for this isn't on the SM951 itself, it's actually a string of BIOS hacks in the Clevo BIOS itself.

Prema, may I ask if during your exploration/hacking of the BIOS for the P650SG you see any bootloader or unlockable options for the offboard sata controller?

Nope haven't heard of any such report...it may have already been corrupted...had the same problem with one of the W10 betas. The reason there was that it didn't forgive me booting in (mixed) Legacy mode once instead of pure UEFI.

Share this post


Link to post
Share on other sites
Nope haven't heard of any such report...it may have already been corrupted...had the same problem with one of the W10 betas. The reason there was that it didn't forgive me booting in (mixed) Legacy mode once instead of pure UEFI.

Sorry, can I ask you for a bit more detail about this? What do you mean by "it may have already been corrupted"? You mean the default Clevo offboard sata part of the BIOS may be corrupted at the source, from Clevo itself? What do you mean that the BIOS did not forgive you booting once in mixed Legacy mode versus pure UEFI? I have had my CSM configured to boot in Legacy since I did a fresh install of Windows 7, as I didn't want to install Windows 7 in pure UEFI. Does booting the system in Legacy mode possibly corrupt something?

Share this post


Link to post
Share on other sites
Guest
Sorry, can I ask you for a bit more detail about this? What do you mean by "it may have already been corrupted"? You mean the default Clevo offboard sata part of the BIOS may be corrupted at the source, from Clevo itself? What do you mean that the BIOS did not forgive you booting once in mixed Legacy mode versus pure UEFI? I have had my CSM configured to boot in Legacy since I did a fresh install of Windows 7, as I didn't want to install Windows 7 in pure UEFI. Does booting the system in Legacy mode possibly corrupt something?

Disabling UEFI and booting in Legacy while playing with CSM rendered the W10 beta FUBAR.

Share this post


Link to post
Share on other sites
Disabling UEFI and booting in Legacy while playing with CSM rendered the W10 beta FUBAR.

Did this fubar-corruption occur within the BIOS itself, or did playing with CSM in Legacy corrupt something in the OS which you were subsequently able to fix with a fresh OS install?

I'm considering trying out the stock BIOS for the P650SG posted on this site, to see if I still get this issue. Problem is, I am currently on v2 of your Prema BIOS which is based on Clevo version 37_39, but the stock BIOS you have posted are only 37_34. Is there a danger of bricking my laptop if I downgrade like this from 37_39 to 37_34?

Share this post


Link to post
Share on other sites
It is normal to through a HWID mismatch even when flashing stock vBIOS...a couple posts back I just gave the explanation...

He probably waited too long to answer the question with 'yes' and the nvflash lost control over the GPU resulting in a failed flash.

It is important to let the flash complete successfully and wait for the brief message to reboot. If a flash fails it needs to be repeated BEFORE rebooting.

Flashing in DOS is not supported for Maxwell cards by NVIDIA...

Stock vBIOS for GTX980M-G is in the OP and on the blog.

Re-flashing the GPU in a system with Optimus or as slave in an SLI will be no problem.

Hi Prema,

Yes, I think my friend waited at the option to press "y" to continue and it just did something anyway. I told him to wait as I wanted to check here if the message he got was normal :(

Thanks for uploading the stock 980m gsync vbios, couldn't see it earlier :)

Share this post


Link to post
Share on other sites
Guest
Did this fubar-corruption occur within the BIOS itself, or did playing with CSM in Legacy corrupt something in the OS which you were subsequently able to fix with a fresh OS install?

I'm considering trying out the stock BIOS for the P650SG posted on this site, to see if I still get this issue. Problem is, I am currently on v2 of your Prema BIOS which is based on Clevo version 37_39, but the stock BIOS you have posted are only 37_34. Is there a danger of bricking my laptop if I downgrade like this from 37_39 to 37_34?

It was not a BIOS but OS problem...though I had to reinstall it as nothing would fix it.

Share this post


Link to post
Share on other sites
It was not a BIOS but OS problem...though I had to reinstall it as nothing would fix it.

What was the OS problem? Was it the same issue I'm having, where everything worked fine except for Safe Mode?

Also, is there any danger in downgrading my BIOS from your v2 to 37_34 stock?

Share this post


Link to post
Share on other sites

According to anandtech, intel Skylake mobile processors are going to get 4core 4thread i5s, and has an unlocked i7 for the same price as regular i7s :D

Share this post


Link to post
Share on other sites
It is normal to through a HWID mismatch even when flashing stock vBIOS...a couple posts back I just gave the explanation...

He probably waited too long to answer the question with 'yes' and the nvflash lost control over the GPU resulting in a failed flash.

It is important to let the flash complete successfully and wait for the brief message to reboot. If a flash fails it needs to be repeated BEFORE rebooting.

Flashing in DOS is not supported for Maxwell cards by NVIDIA...

Stock vBIOS for GTX980M-G is in the OP and on the blog.

Re-flashing the GPU in a system with Optimus or as slave in an SLI will be no problem.

Nope haven't heard of any such report...it may have already been corrupted...had the same problem with one of the W10 betas. The reason there was that it didn't forgive me booting in (mixed) Legacy mode once instead of pure UEFI.

Hey Prema, we're trying to reflash the 980m gsync from my friends P750zm-G in another laptop (alienware) with an IGPU, but we're getting this error. Basically a board ID mismatch error.

post-35744-14495000689162_thumb.jpg

It's this board id mismatch error that we can't overcome, is it because we're trying to flash a clevo p750zm stock 980m g sync vbios whilst the card is in an alienware laptop? Is there some way we can correct this mismatch error or even bypass it if that won't cause any problems?

Really appreciate any help you can give!

Share this post


Link to post
Share on other sites
Guest

The stock version that I've uploaded for you maybe for a different board version. Try to flash the Mod version.

Share this post


Link to post
Share on other sites
The stock version that I've uploaded for you maybe for a different board version. Try to flash the Mod version.

We first tried to re-flash the modded g-sync vbios below and it went in fine with no mismatch ID errors, but with the same result as originally - black screen upon reboot

https://biosmods.wordpress.com/gtx9-g/

8GB MXM GTX980M-G:

Share this post


Link to post
Share on other sites
Guest
We first tried to re-flash the modded g-sync vbios below and it went in fine with no mismatch ID errors, but with the same result as originally - black screen upon reboot

https://biosmods.wordpress.com/gtx9-g/

8GB MXM GTX980M-G:

Are you 100% that he flashed the g-sync system BIOS and not the one for the regular model?

Usually if we cross-flash regular and g-sync versions it'll result in black screen on boot.

I am traveling atm and can't really access my files. Please drop me a mail (in your PM) so we can figure this out.

Share this post


Link to post
Share on other sites
Are you 100% that he flashed the g-sync system BIOS and not the one for the regular model?

Usually if we cross-flash regular and g-sync versions it'll result in black screen on boot.

I am traveling atm and can't really access my files. Please drop me a mail (in your PM) so we can figure this out.

Sent you an email Prema, Yes, he couldn't get the NEW stock bios to work (board ID mismatch) so he ended up trying the modded g-sync bios which went in ok but still resulted in black screen.

Here is the modded g-sync bios he tried - https://mega.nz/#!CNdkzDia!<wbr>q4q83PXLzw1lbp0IGlizOrbuTnKLLZ<wbr>iZfrRxnc5dH6Q

Here is the stock g-sync bios which resulted in the board ID mismatch - https://mega.nz/#!yMUlGaYR!FQH1nDXrkdLfYYisDPyDM_jxTFshLksEmvxRmcGVg8g

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.

  • Similar Content

    • By Anderitos135
      I have a iBuypower CZ-17 laptop, with a 2012 AMI BIOS that has E1762 as the version, which I believe means I have an MSI G70 motherboard. It has a 675MX GPU, but it's not useable in Windows 10 despite being "seen" in the device manager. I believe an updated, unlocked BIOS would fix my issue and have located the thread on this site with the BIOS I need.

      First of all, am I right? Will this fresh BIOS make my laptop that originally ran Windows 8 work with this old GPU?

      And second, I created this account, will wait 24 hours and made this post. Is that enough to allow me to download the file, or do I need to post elsewhere?

      Thanks!
    • By Radstark
      Title sums it up.
       
      TL;DR: we have a Clevo that runs a desktop CPU, one with those huge 82 Wh batteries. We remove the GPU and let it use the CPU's integrated graphics. How much time for the battery to go from 100 to 0? Is it comparable to an ultrabook's?
       
      I'm theorizing a mobile set with a static eGPU and an upgradable CPU. Given a hypothetical user that needs fast processing on the go and long battery life while retaining very high degrees of mobility, but at home wants a powerful machine to run most games, I guess that would be their best bet. It would surely be more convenient to keep everything in the same disk. And even though the thing would be quite heavy to carry around, changing CPU would be more cost-efficient than changing an entire laptop. (Not sure if I'm right here, and also I'm not sure whether the motherboard in a Clevo would be replaceable when the new CPU needs a different socket, which is another reason why I'm asking here.)
       
      If my above guesses aren't correct, then an ultrabook with Thunderbolt and without a dedicated GPU would be a better choice. If they are, then we would be carrying more weight in exchange of a more cost-efficient setup, which I think would be a fair tradeoff.
       
      Also I am aware of the heating problems that these laptops suffer from, at least compared to a desktop setup. Would they be solved by moving the GPU out of the chassis, and instead plugging it with an eGPU dock via Thunderbolt port?
       
      What do you think? Is it doable? If not, why?
    • By Zoarilamb
      A part of my BIOS got corrupted that controls my laptops backlights. Other methods like the Gary Key fix did not work for me because I do not get any light up during post. i followed this guide  that says I need to extract and use the 6MB portion of an 8MB bios dump, only AFUWIN tells me "Error, ROM file size does not match existing BIOS size which is because my laptop BIOS size is only 5.87MB.  I don't need to flash the whole BIOS, I only need to flash a portion of it. 
       
      I've searched everywhere online for a dump of my laptop model but non exist that I know of.
    • By Zoarilamb
      I fiddled around with modding my laptops BIOS to unlock XMP profiles and hopefully seeing if optimus could be disabled. After flashing my modded bios and trying it out, I noticed that my keyboards backlight no longer turns on. I was unaware it requires an official BIOS to function. They backlights wont turn on unless ASUS ATK package is installed but now it seems it also needs an official BIOS?
       
      The modded ROM and tool I used if anyone has any experience with this and doesn't mind telling me what to enable/disable, or anything else i can do to re-enable them 
        
    • By Binarious
      I installed an NVIDIA Quadro P4000 Max-Q in a Clevo P750DM-G.
       
      Device manager hardware ID shows:
      PCI\VEN_10DE&DEV_1BB7&SUBSYS_75021558&REV_A1
       
      I have done the standard inf file mod, then disabled driver enforcement as I have done successfully in the past, but it's not working this time. The install starts, then fails less than half way through. I have tried the DCH version, standard version, and studio versions and none of them will work. I am probably missing something. Could it be the result of the vBIOS?
       
      Below are screenshots starting with GPUz
       

       
       
       

       
       

       
       
       
       
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.