So, I love Malibal's build quality, and their customer support, always been helpful (just saying, I don't think this is on their end). After recently starting to play Borderlands 2 and Mass Effect 3 (No other games as far as I can tell at the moment do this to my screen), maybe an hour into playing, maybe two (granted only a week ago, after 20+ hours of playing the entire week, this never happened), the screen will start to flicker white. Sometimes the entire screen, sometimes only a little bar of white. There is no FPS drop (I checked using the FPS counter in-game), and the temperature still stays at 75C (according to Speccy). Lastly, my drivers are up-to-date.
Any help and/or suggestions are GREATLY appreciated.
Computer Specs:
CPU: Intel i7-2820QM @ 2.3 (I need to OC this, haven't messed with it, haven't OC'd in a while. Any help with that would be great as well).
Memory: 8 Gigs DDR3
GPU: NVidia 485M
Trying to type all this out while finishing up some homework (decided to post here after not being able to solve the problem myself). Let me know if there is any other info you will need (most likely).
Thanks again!
-
Did you contact Malibal? And why do you have a 485M with a P170EM? P170EM was the first 17" with Ivey, by then at the minimum, you should have a GTX 580M/570M, not a 485M. And even a GTX 670M should beat your 485M.
-
At the time of ordering, the best mobile GPU they offered for the Satori (what Malibal calls the P170EM), was a 485M. This was maybe at the start of last year's Summer? I've had it for almost a year and a half.
-
Hi, I think you have the previous gen's P170HM like mine.
With regards to your problem, do you experience any of these issues if you connect it to an external monitor? -
Not sure, I'm at college right now, so I'll try the next time I am home. It's just that I don't want to spend that much money on a nice external, and the whole point of a laptop is unless I'm bringing along a 120hz monitor, is to not need an external.
-
I would highly suggest you contact malibal. You should have received a warranty and if you have some of your warranty remaining then you could utilize it in fixing your laptop in this case the p170em. Contact them first and foremost. If they cannot resolve it, then pm me and i will try to assist you further if need be.
-
I'll see. It's just it only does it for these two games (at the moment, as far as I know). I thought it could be DirectX doesn't like my drivers, something or other. I'll do some more tests and post back here hopefully by the end of the weekend. Thanks guys, hope to get some more help soon!
-
haha yeah the 485m got faster due to driver enhancements, its basically a 7% lower clocked 580m/675m. so no the 670m is not faster, well maybe compared to when it was released. and for the record originally the em series came with sandybridge, while they were waiting for ivybridge, although i find it very unlikely that they shipped a 485m with an em series, as the 675m was already available, which is the same as the 580m.
-
Unless they changed the Clevo model they use with the Satori (under customization), I have an EM with a 485M. My processor is a Sandy Bridge as well.....meep.
-
You have a p170hm. Malibal just kept their same names (Satori and Lotus) when Clevo released the P170em and p150em chassis.
If you aren't convinced then check if your keyboard lights up. Next check, you probably don't have an msata slot. Also, check the serial number on the bottom of your laptop. There should be a number that states it is a p170hm. Lastly, the P170em chassis were not released until.this year, and since you got yours last summer, it is a p170hm.
Hope you get your issues resolved however. Starting a ticket with mailbal will be first step for you.
Sent from my EVO using Tapatalk 2 -
Ah, well I'll check tonight. I had been out of town these past couple of days, so I wasn't able to check anything on the laptop.
I have the P170HM then.
I might contact them, depending on what I find. Thanks.
P170EM (Malibal) with NVidia 485M problems...
Discussion in 'Sager and Clevo' started by thrwbck, Oct 2, 2012.