P157SM-A + Premamod Issues (FPS Drops)

Hi everyone,

I've been testing a Clevo P157SM-A with a GTX880M. With the stock BIOs that the machine came with, I was playing games comfortably at maximum settings at a locked 60fps.

However, I updated the BIOs with Premamod v2 and I've been noticing massive frame-rate drops at random times along with the GPU spiking at 99% before dropping down to 60%. It's always the same issue, holds 60fps for around 10 seconds, then the GPU spikes to 99% with a frame-rate drop to mid 30s then it goes back to normal before the cycle repeats itself.

I've tried going back to stock BIOs, same issue, updated to the latest vBIOs, same issue, re-installed Nvidia drivers, same issue. I'm honestly at a loss of what to do now.

For reference, here is the BIOs I flashed to, and currently using. Any help would be greatly appreciated.

https://biosmods.wordpress.com/p157sm-a/

EDIT: Also, is there anything to be done about the noise and heat output? It's ridiculous.

 

Don't blame the BIOS, your GPU always did that, that's simply what a stock GPU without Mod does...
A GTX880M will throttle like no tomorrow unless you also flash the vBIOS Mod for it:

https://www.techinferno.com/index.p...king-editions-modified-clocks-voltage-tweaks/

 

Thanks for the quick reply. What puzzles me is that it only started after I flashed my BIOs, so I was wondering if there was any tweaks that were required. I'll follow the link and report back.

 

Ok so I've updated the vBIOs from what you've linked me and I'm still experiencing the same issues. Randomly spikes to 99% then the FPS drops like a rock. Not sure on what I can do

 

Yep, stuttering issue is still occurring. Any idea on how to fix this?

EDIT: Uploaded a video, you can clearly see it happening. Help please

 

As we can't see the clocks I can't tell you for sure what the card does, but it'll 100% throttle on Furmark...the GTX880M is till today NVIDIAs highest rated TGP card except for the GTX980s.
Never use Furmark even with stock vBIOS, it'll kill your cards.

The svl7 vBIOS is set so that it doesn't throttle under normal use compared to stock.

 

Here is the log from GPUZ, you'll see that the core clock simply drops like a rock all the time. Any idea what could be causing it, because I can assure you with the stock everything that the system came with, I wasn't experiencing this at all. Appreciate the help.

 

Yes, that is Furmark power throttle, it protects your card.
If you want to burn it, you can use NVIDIA Inspector and raise the power slider all the way up and you will see the difference.

 

The log was from me playing. No matter what game I play, this stuttering always happens.

 

I'm at a loss of what to do now. I've reflashed the BIOs and vBIOs with the latest Prema and what you've linked me. Re-installed Windows, drivers etc. I've no clue what it could be. I've uploaded a short clip showing the FPS drops when playing, as well as the log from GPUZ. I hope this will be of some benefit. Thank you.

 

So I went ahead and flashed everything back to stock, issue is still occurring. All I can conclude is when I flashed to Premamod v2 something happened to my GPU. Going to try and acquire another GTX880M and report back. Any further help or tips would be greatly appreciated since I'm at my wits end.

 

I told you before that GPU performance has nothing to do with the system BIOS Mod.
The BIOS Mod does exactly change NOTHING related to the GPU.

Now you wanna waste your money on another GTX880M, just because you never noticed its problems before?
You will be very disappointed when you find out that they are all exactly like this right from the factory...
Instead simply use the tools properly that you have been given for free and raise the power target in Inspector and stay away from things like Furmark.
We make those Mods because things do not work right out of the box...

GTX880M & throttle have a long history:

http://forum.notebookreview.com/thr...-and-the-bs-that-there-doing-go-reply.755589/

http://forum.notebookreview.com/thr...ystem-or-hope-nvidia-fix-the-problems.757812/

http://forum.notebookreview.com/thr...maybe-not-what-youre-expecting-to-see.763931/

http://forum.notebookreview.com/threads/880m-gtx-throttling-issue.758228/

http://forum.notebookreview.com/threads/880m-throttling-with-low-temps-and-gpu-load.772908/

http://forum.notebookreview.com/threads/880m-sli-throttling.751772/

http://forum.notebookreview.com/alienware/746259-my-nvidia-gtx-880m-test-run-review.html

http://forum.notebookreview.com/alienware-18-m18x/750830-just-got-my-880m-twins.html

And here svl7 vBIOS and impact of driver version:

http://forum.notebookreview.com/threads/880m-sli-overclocking-with-svl7-vbios.757736/

Here directly @ NVIDIA Forums:

https://forums.geforce.com/default/...here-new-drivers-look-for-a-nvidia-response-/

 

Once again, I fully tested this machine before upgrading to Premamod BIOs and I never, ever experienced what I'm currently experiencing. Playing at 1080/60fps without a single frame-drop for hours on end, core/memory clocks were consistent and temperatures under load were hovering at around 70-80 degrees.

Getting another GTX880M to test with is not an issue, I have access to them. On Monday I'll be running the same test on another machine of the same make and model at stock BIOs/vBIOS and I'll demonstrate that there are no stuttering issues.

Before making this post, I yet again flashed to Premamod, and flashed my GPU to the link you posted on the first page, set the power and temperature target on nvidia inspector to the maximum and I'm still experiencing the same issue.

FYI I ran Furmark for barely 1 minute at the lowest setting, I only used it to see if every other program that utilizes the GPU is affected the same way, which it was.

 

Did you read the threads I linked above>>>driver

That's my last reply. Good Luck!

 

You're trying to use 361.43 driver? Are you nuts? Downgrade to 337.88, that's the driver I used with my 880Ms.

The behavior that you are experiencing is par for the course with 880Ms. I don't know why you're arguing with Prema, he's the LAST person who would give wrong information... You know, since he's an extremely skilled modder of both the BIOS and vBIOS...

Oh yeah and that svl7 vBIOS is fussy on Clevo systems......

 

Please don't argue with Prema, he is one of the smartest people the Clevo community has the pleasure of having. His knowledge and information as well as his abilities are an amazing asset and we are so lucky to have him. Definitely try downgrading your drivers and if you are going to do so then make sure to do a completely clean install with DDU.

 

So, I'm back, with tests that have been very, very interesting indeed.

Test Method #1

I acquired a brand new, unused GTX880M to test with. I installed it in the machine that I re-flashed with Premamod v2, the results were the same, i.e-stuttering, core clock dropping etc. I then flashed it back to stock BIOs, yet again the results were the same. Very disappointing but it proved that there was either a fault with the mainboard OR the GTX880M. I then installed a GTX870M card, yet AGAIN the results were the same. Another 800-series card 'acting' as it should or is there more to this issue?

Test Method #2

I then used another machine of the same make and model as the one above, that had not being flashed or otherwise tampered with in any shape or form (image attached below, stock1). I used the same SSD that was in the original system so EVERYTHING was identical which included 361.43 as the driver (image attached below, stock.gif). Well, the results speak for themselves. Not a single hitch, not a single frame drop, no throttling, no stuttering. It was performing exactly the same way as the original machine pre-flashing to Premamod v2. We ran SFV for hours on end and there was absolutely no issues whatsoever. I've attached the log which was quite lengthy so I cut off the top section which had the system on idle, plus attached a video which shows no visible frame drops whereas the original that was flashed with premamod would drop frames every few seconds (video in my previous posts)

Edit: I also tested the 880M from the older system in this new one and the results were exactly the same, no issues whatsoever.

Conclusion

Well, I dislike pointing fingers but it's been made abundantly clear that some inherent issue has arisen after the system was flashed with premamod. Even after flashing the system back to stock BIOs does the issue still exist. Will I risk flashing premamod on this new system to see if the issue persists or if it was a once off? **** no. But I will provide whatever files necessary so perhaps prema can look into this issue because frankly, one motherboard is rendered quite useless if it cannot allow the GPU to function as it should. I understand he has done fantastic work for the community with his custom BIOs and knowledge and for that I am grateful, so I do hope he doesn't take this post the wrong way and if I were disrespectful then I apologise.

Thank you.

 

Instead of blaming Prema, did you ever think to blame Clevo? You're running an ANCIENT stock system BIOS that was meant for the 8xx cards. 1.03.11 is optimized for 9xx cards. Glad that your issue is fixed but don't be so quick to jump to the conclusion that Prema broke it, Clevo probably is the one at fault here.

 

It still doesn't explain why the cards become crippled when using Premamod v2, which was my issue in the first place. If other folk have 8xx series cards and flash to Premamoa v2, wont they also experience the same issue? I do think it's worth investigating.

 

The Premamod vBIOS doesn't play well with NVIDIA's 361.43 drivers... Well more like the drivers don't play well with the vBIOS because NVIDIA has been messing up as usual... It has been said everywhere on this forum to stay away from them and yet you kept using them.. Don't blame Prema, blame NVIDIA and your stupidity for not listening to us..

Sent from my LG-H811 using Tapatalk

 

My stupidity? Are you listening to yourself? I DID rollback to older drivers, I DID put the power limiter up, I did EVERYTHING that Prema and others suggested and the issue still persisted. I tried absolutely everything and yet nothing changed. So please don't come here adding nothing to the conversation. It's hard getting a straight answer here without people jumping down your throat or resorting to insults. Grow up.

 

My guess is that anyone with 880Ms that flashes to stock Clevo 1.03.11 will have the same issues. I think that is worth investigating first. The fact is that flashing the stock Clevo BIOS on Prema's site removes any trace of Prema's mod. It's not like Prema is using a custom tool, he's using the official tools that Clevo does.

Most everyone who had the 880M cards has gotten rid of the trash by now.

 

That is something I would like to test when I have the chance but I'm honestly frightened of the outcome. What I will do however is flash the machine that's on 1.03.11 down to a lower BIOs if possible and report back. If 1.03.11 does prove to be the issue (which is looking likely) is there any way that Prema will be able to solve it, or just contact Clevo?

 

Clevo won't support any end of life machines at this point. You could ask your vendor if they have the old BIOS or you could ask Prema if he has it but just beware that downgrading the BIOS has caused bricks in the past... Although I've done it without issue. I think people who brick are forgetting to unplug the machine as soon as it turns off so the EC doesn't downgrade and results in a mismatch and a brick but the risk is always there. Replacement motherboards run a good 300-400 bucks if you have a bad flash so keep that in mind.

 

Holy hell, that's terrifying.

 

Did you reset the Bios profile? i mean some settings might be wrong.

Also i had a gtx880m and i keep it just a few weeks, the shi***** Gpu i ever own tested in both Aw&clevo. You can also try slv7 vbios. (even if i prefer Prema Vbios) And use a good thermal paste for this 'gpu'.

 

@ZeroX03 you have a PM. Please report back here when you have a chance to use it on your machine running 1.03.11, hopefully it fixes it.

 

Prema's BIOSes (stock or mod) overcome this by flashing the BIOS and EC at the same time. As long as you pull the power cord when the machine turns off after the flash like the instructions say to, you can successfully go between versions without any issue.

 

Oh, alright, that's good at least.

 

I still wouldn't do it unless I had to but the risk is definitely a lot lower using Prema's batch scripts. I've even flashed Sager over Clevo using his scripts despite the conventional wisdom around here saying that you can only flash Clevo over Sager, doing it the other way around will cause a brick. Since his scripts flash everything at once, the risk isn't any higher than a BIOS flash is normally. If anything, even flashing a newer stock the "right" way is more risky than Prema's way because there's a lot more room for human error in the "right" way.

 

That mod works PERFECTLY. Thank you so much!

 

Don't thank me, thank @Prema

I had a feeling it was due to the new BIOS base but its all Prema's work.

 

Yeah, after you told me to test the newer stock BIOS on another machine I had a gut feeling it may have been that. I actually did test it today and indeed the issue was the same. Many thanks to Prema for releasing this version.

 

Mate, I have exatly the same problem than the OP but with a 870m and a P15SM-A. Do you know what can i do? Thanks!

 

You can try contacting prema if it's identical.

 

My computer has the same problem than OP's, but its a bit different machine.

 

Yes but if you are using his modded bios then it's worth giving him a shout.

 

Thank you for the advice, but I dont know how to send hime a message lol.

 

You need to have 5 posts outside of the off-topic forum in order to send messages.

 

Through his site is probably best: https://biosmods.wordpress.com/

 

I've encountered near identical issues to the OP with my 880m GPU and upgrading from Prema's P150SM-A BIOS v01 to v02. Would it possible to know what the solution to this problem was i.e. in the PM Ethrem sent to ZeroX03?

The following are the steps I took in relation to this issue:

In short, I found the only solution was to downgrade back to Prema v01 BIOS for the P150SM-A. I kept the NVIDIA 880m svl7 modified vBIOS though.

I would very much appreciate any clear explanations behind why this stuttering occurs with Prema's v02 BIOS and not v01 in the above scenario, and any subsequent solution.

Many thanks!

 

Unfortunately you have to downgrade to v1. Clevo broke support for 880M in the new BIOS revision. You're not missing much of anything by using v1.

 

Thanks for the speedy reply Ethrem! Simple solution really.

From what I gather, Prema's v02 BIOS was to better enable 980m support. Is this correct?

From what I also understand, Prema would use the broken Clevo BIOS release as a base, and thus the broken support for the 880m is not easily fixable. Is this also correct?

It's also a potential shame shame for other P150SM-A 880m owners that the v01 BIOS is not longer offered on his blog, but I imagine a lot of those that cared would've installed it long ago.

Regardless, it seems like there were some interesting improvements with v02 of that BIOS from Prema's 22/07/15 blog post:

For my interest (and self-education) in particular, I tend to try overclocking/messing with my system when a new upgrade is a around the corner. So a greater array of options such as those mentioned by Prema above would have been useful. I also did notice that the keyboard LED was properly switching to the correct colours without intervention with the v02 BIOS, but I didn't test this at all.

Anyway, thanks for the info!

 

Any time!

Here's the problem... every flash has the potential to cause a brick... We both thought it was an isolated incident but I will be talking to Prema about maybe making a link to old releases with a disclaimer that you have to sign that he's not responsible so he has a record. The reason for this is because there are a lot of people who don't read the instructions and pull the power cord when the system shuts off. That's the only way to flash the EC. A mismatch between BIOS and EC *will* brick. Depending on the machine, you're looking between 200 and 500 for a new motherboard if you brick because Clevo does *not* have any back up system that reliably works. Downgrading has the largest risk of anything else you can do to the firmware in the machine if you don't do it right. If you want more evidence about this, go to the BIOS thread and ask what happens if you flash an old BIOS. Its serious business and while Prema has worked around the issue, its still a liability.

How many of those improvements actually affect you? I ask because traditional thought has *always* been that you don't flash the BIOS unless you have no choice because something is broken. Now that we have EFI... its anyone's guess what actually can mess up. Would you rather miss out on some features that likely either don't impact you or minimally do so, knowing the risk is you have to pay to have your machine fixed and that your entire warranty can be void depending on reseller policies?

Prema is offering a service. We are fortunate enough that he offers it for free, relying on people to make donations to make his time worthwhile. He's busy right now though and on top of that, he didn't make the 880M vbios, he just modified his code to make it actually work... and trust me, if I didn't own an M17xR1... I would have had to spend over 700 dollars for new 880Ms when svl7's vbios screwed up...

 

ROFL

 

Yes and they blame the people supplying the instructions. What makes things trickier is the EC is stored on a different chip.

 

It's unfortunate to hear about the unfair liability issues for community/service contributors such as Prema. Yes we are fortunate enough to have members such as him (gender assumption) and unclewebb (ThrottleStop), and for the record I have given donations to both in addition to the TechPowerUp website.

My suggestion about providing the old v01 and associated notes about the 880m where not from a position of a 'spoilt 15 year old forum troll spitting venom', but purely just a suggestion, with combined admission that "...a lot of those that cared would've installed it (v01) long ago". Particularly because I believe I am a good forum user and try to research my questions as much as possible before asking (some of the threads on these forums are enormous e.g. P150SM-A owner's lounge).

In regards to the "how many improvements actually affect you" and "traditional wisdom", these are all fair points. However I reiterate my point that I only overclock/mess with my system at the end of it's lifespan. For example I still have my old P150HM, and have messed with it's hardware/software/BIOS a fair bit for the reasons above, and it's luckily still running as my Media Centre. To put it another way, I don't resell my old laptops or care if I mess them up, so warranty/reseller policies are a non-issue for me.

I'm also just interested in technical questions such as, "Was Prema's primary goal with v02 BIOS to allow fo 980m support in the P150SM-A". Purely interest, nothing more. On this last point, I'm interested in your final comment: "...I would have had to spend over 700 dollars for new 880Ms when svl7's vbios screwed up...". As I said in my initial posts, I've installed svl7's vBIOs for the 880m, so I'll do some research around the forums about this comment and the history of this vBIOS.

Thanks again for the speedy answer's Ethrem, and if Prema is stalking around this thread, thanks for your efforts with the Clevo series over the years!

 

Sorry that this isn't as thorough as my last post but I'm on my phone right now.

I don't know what Clevo changed that broke 880M machines, especially considering that the 880M is just left over 780M silicon that tends to not work right yet I've heard no similar complaints from 780M users.

The SM-A series all support the 980M out of the box because Clevo finally implemented real MXM in the SM-A machines - the card shows as unknown but works just fine. As a matter of fact when I upgraded to 980Ms, Sager didn't even bother to flash the BIOS so my cards showed Unknown but worked fine.

If you have donated to Prema in the past, you have his email address, just send him a message asking for the v1 mod.

My comment about the svl7 vbios is that it doesn't work right on Clevo machines... I bricked twice and didn't realize it was because of legacy CSM running with EFI as well. Something about the vbios caused a black screen when I had the wrong the combination which required me to stick an 880M in my old Alienware to flash it with the stock vbios to get the system to POST again. This happened twice before I decided to run a self-modded stock vbios that was undervolted and set to 780M clocks to tame the fire those cards spewed out.

 

I origingally had Prema's V01 installed and still have a copy, hence my reversion in the steps I posted earlier when I was trying to diagnose these initial issues.. Again, was just a general comment for "the odd" P150SM-A 880m owner. I also like the idea of the 'forum' approach as opposed to emailing Prema, as other users can benefit from what I've learnt, as I have from others many times on these forums.

Sad that the 980M didn't have complete support from Clevo. However this absolutely pales in comparison to the trials I went through with the Alienware Area-51 m15x when Dell took-over (refer to my very early posts if interested!).

Good to know abou tthe svl7 vBIOS. With my P150SM-A and the svl7 880m vBIOS I have no issues, so I assume it's because I'm running legacy BIOS ...and don't have a dragon for a GFX card.

Cheers!

 

There are so many possible configurations, I'm glad you got one working