Razer Blade 2015 freezes

Hello everyone,

As they tried to fix my unit, replace it, replace the SECOND failed AC, this ****ing notebook is still experiencing troubles.

While playing, the notebook just freezes totally on the last frame, nothing works, no mouse or keyboard both internal and external, it just freezes.

It happens 1-2 times a day, altho I don't play more than 3-4 hours a day.

Once it also went "yellow-screen" (something like a BSOD, but yellow) which crashed too before going up to 100% data gathering.

No OC on the machine, happens both with TS running, tubo off and turbo on, it happened in Overwatch all the times, but that's probably cuase I'm only playing it as of now.

Has this happened to you too? Is is somehow common? Couldn't find any real fix yet on the net.

Note that it happened on two different Nvidia drivers versions too.

Thank you

 

Either overheating or defective motherboard.

 

@pbhenry3 may be able to help

 

Undervolting my 870m further then stable caused hughe stuterst but nothing like you are describing.

I mean, the intel onboard is there in case that the dedicated goes down the river.
that implys that something is fundamentaly wrong causing the system to fail in such a way.
Maybe temps, maybe voltages, maybe something else.

@pbhenry3 if you are on that side of the globe.
In the EU, maybe you let me have a look at it?

 

How are the temperatures? I doubt it would be overheating if it still does it with cpu turbo off, as you say, but still important to check. Other than that, It sounds more like it would be related to the cpu rather than the gpu. Usually any kind of gpu error on nvidia optimus would result in freezing for a few seconds and then a crash to desktop. A complete freeze up with error collecting and shutdown sounds more cpu related. Could be something like a bad cap on CPUVCORE or failing VRM? Although such an error should throw a "blue screen of death", havent heard of yellow screen.

Can you open the event viewer and take a look at the error codes from around the time it happened? Should give us a better idea as to whats going on with your system.

 

I could take this vid from one of said events:



Doesn't actually show much, but you can stop the vid while it shows the "yellow screen" I mentioned, it's impossible to read as it lasted less than a sec, but still..

Event viewer! Never used it; it says I got 4 critical errors during the past 7 days, literally "kernel-power" originated, from "system" register.
It's also showing 134 errors, 5 of which are 'kernel-EventTracing" originated.

The critical error details says it's power related and that it might be caused by a loss of energy supply, on a side note: my batttery died once, altho it still had 46% left the past week, upon relog it showed like it's health had gone down to 46% but a recalibration solved the issue. Could it be that the battery is dying (after 3 months of usage, 30-80% cycles, never down to 0, almost never up to 100.....).

I got no clue what it does mean 'cept for what I can google about it, so I'll simply STFU and post a SS, would you need any other information, let me know.

Spoiler

Note that all of the critical ones show the same descriptions in terms of "key word" (parola chiave: ) and "category" (categoria: ).

Also note that right before this post, the notebook actually BSOD'd but didn't turn completely off, it just semi hibernated, showing the white standby led but with keyboard still lighting up green.

XML details:

Spoiler

- <Event xmlns=" http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name=" Microsoft-Windows-Kernel-Power" Guid=" {331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
<EventID>41</EventID>
<Version>4</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000400000000002</Keywords>
<TimeCreated SystemTime=" 2017-02-18T22:08:10.916534300Z" />
<EventRecordID>12870</EventRecordID>
<Correlation />
<Execution ProcessID=" 4" ThreadID=" 8" />
<Channel>System</Channel>
<Computer>Blade</Computer>
<Security UserID=" S-1-5-18" />
</System>
- <EventData>
<Data Name=" BugcheckCode">0</Data>
<Data Name=" BugcheckParameter1">0x0</Data>
<Data Name=" BugcheckParameter2">0x0</Data>
<Data Name=" BugcheckParameter3">0x0</Data>
<Data Name=" BugcheckParameter4">0x0</Data>
<Data Name=" SleepInProgress">0</Data>
<Data Name=" PowerButtonTimestamp">0</Data>
<Data Name=" BootAppStatus">0</Data>
<Data Name=" Checkpoint">0</Data>
<Data Name=" ConnectedStandbyInProgress">false</Data>
<Data Name=" SystemSleepTransitionsToOn">0</Data>
<Data Name=" CsEntryScenarioInstanceId">0</Data>
</EventData>
</Event>

Next XML is from the "yellow screen" error:

Spoiler

- <Event xmlns=" http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name=" Microsoft-Windows-Kernel-Power" Guid=" {331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
<EventID>41</EventID>
<Version>4</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000400000000002</Keywords>
<TimeCreated SystemTime=" 2017-02-18T00:50:24.841981200Z" />
<EventRecordID>12586</EventRecordID>
<Correlation />
<Execution ProcessID=" 4" ThreadID=" 8" />
<Channel>System</Channel>
<Computer>Blade</Computer>
<Security UserID=" S-1-5-18" />
</System>
- <EventData>
<Data Name=" BugcheckCode">0</Data>
<Data Name=" BugcheckParameter1">0x0</Data>
<Data Name=" BugcheckParameter2">0x0</Data>
<Data Name=" BugcheckParameter3">0x0</Data>
<Data Name=" BugcheckParameter4">0x0</Data>
<Data Name=" SleepInProgress">0</Data>
<Data Name=" PowerButtonTimestamp">0</Data>
<Data Name=" BootAppStatus">0</Data>
<Data Name=" Checkpoint">0</Data>
<Data Name=" ConnectedStandbyInProgress">false</Data>
<Data Name=" SystemSleepTransitionsToOn">0</Data>
<Data Name=" CsEntryScenarioInstanceId">0</Data>
</EventData>
</Event>

 

Got it. Thats a generic Error message, but from what we do know I would say it is highly likely we are dealing with a problem on CPU MAIN CPU VCORE. I did have have a 2014 in before (same design) that had a failed resistor on the 12V Rail but that was causing no power up and 1 second fan spin. If I had to guess, I would say shorted diode or failing VRM, both of which are common. It could be a failing cap, but I haven't seen any failed caps on these before.

It is unlikely that it is the battery, if gaming and the battery became undetected briefly, it would just power limit throttle instantly and shouldn't shutdown.

Still that "yellow screen" is very strange and I'm not sure what to make of it. Let me ask you this, have you ever overclocked or undervolted this system in any way? I ask because sometimes changes can remain applied even after restarts and even if you arent running the utility anymore, or havent run it in some time. So if you have messed with the voltages significantly before, I would suggest taking the back plate off and disconnecting and reconnecting the CMOS BATTERY.

So before we automatically assume its a hardware issue, I would want to role out all other possible causes first. If you are certain there is no issue with windows itself, then please try the above. That will issue a complete reset.

Is this the early 2015 model with 8gb ram and green lit keyboard? or the late 2016 model?

 

I've OC'd the GPU a tiny bit for some time, but through Nvidia Inspector and it's now back at stock frequencies for a few weeks; absolutely never overvolted, CPU has been undervolted since the day it arrived to me (been one of the first things I did) but today shut down happened with TS closed.

I could probably reset the CMOS; I'm now also waiting on a Razer support reply as they had extended my warranty a bit as I complained since d1 about temps being too high (3 cores are ALWAYS under 90-92 C, while core n. 3 ALWAYS reaches a max temp of 98/99, if turbo isn't turned off...).

This is a 2015 model, 16 gb of RAM, GTX 970m, i7 4720HQ, QHD screen.

Thank you for your effort, I'll also add my previous post to the support ticket and will update the thread as soon as I get to know something, which might end up being in two days...

P.S.: here's the best I could do about that yellow screen:



It sadly was "cut" down, that black part is the screen plastic itself, looks like a "bugged YSOD", lol.




I had to reet and couldn't wait for a YSOD or sth alike at this time, as I was in hurry, but the issue looks clear.

 

That looks like a BSOD with a new coat of paint to me.

 

While getting out of a game the notebook just BSODd again, not turning off completely, in a semi hibernated manner:



It's not clearly seen (it was midnight, just wanted to go sleep, didn't put too much attention on the vid quality) but it turned on just after I pressed the power button.

I've been ping-ponged by their support already: from US (only one which you can directly contact regarding systems) support to EU support, which eventually just closed my ticket sayign they'd re-open and update my previous ticket, nice start tbh.

 

Yeah, Razer support is very bad. Look for 3rd party repair centres is the only real way to fix most issues.

 

I'm still under warranty as I said, not gonna spend money at all.

I'll just ask loud for a damn system swap to a newer model, I'm totally fed up of this **** with the 2015 version.

Hopefully they'll just give up and send me any 2016+ NB, even a FHD 128 gb, idm, just **** this, it's the third notebook in a row, wtf.

 

I have never heard of them giving system upgrades - literally hasn't happened AFAIK.

 

Here in germany, we have a law that states that after the third try, you have the right to get your money back. Full buy price of cause in return for the produckt.
Maybe thats similiar for you in your country.
Just in case they say **** you to your upgrade wish.

 

As they hosted my first (failed) repair process in Germany and sent me the first faulty unit from there, I'll try to enforce this right too, just in case...

Thank you for the tip!

 

Looks like they gave up trying to fix my unit, I'm gonna get a full reimbursment through a store credit code.

Not bad in the end, as it's basically a way to swap my unit with a new one, too bad the RB is unvailable as of now in Italy through their site and the credit needs to be used in there...

Waiting on an update from them regarding this problem.

Well, it finally doesn't look so bad, but I'm holding my last word on it.

 

I've never actually heard any reports on them fixing anyones unit. it always seems to come down to a replacement from what I am hearing. I would push for an actual refund rather than store credit personally.

 

My notebook over being 18 months old, wasn't bought directly from them (it's from B&H as it was the only store offering worldwide extended warranty), so I don't think I can push it more than I did, sadly.

At least 2017 version is muuuuch cooler, which probably will solve most of the problems previous refresh had.

Problem is that I'm not even sure I'll be able to get a 2017 yet, as their GB and GER stores state they only ship in Germany, UK and Austria, ffs.

Would I not be able to buy one and would be asked to spend aa 2399 credit in peripherals (which I don't even need tbh...) I'll probably keep pushing tho, yea.

 

If you can, do not accept store credit - it's a way of keeping you in the eco system. You should insist on a monetary refund. A guy on reddit had 5 or 6 defective units cause they refunded him through store credit and he couldn't get his money back at all.

 

Notebook will be sent back in monday, will get a credit store refund as they won't refund real money to people who haven't bought the notebook directly from them.

RB 2017 incoming, hopefully it's at least cold.

/praying the karma gods

 

Update on the issue:

I´ve been given the chance to upgrade to this 2017 unit and God, it´s awesome.

http://www.3dmark.com/3dm/18507726?

No OC at all, -120/0 mV downlvolt and 72-67° max temps, ALMOST similar to a same specced desktop.

Got almost no bleed (a small spot on top right, nothing I can notice in real life usage), 3° max temp difference between cores. PM961 with max read speed up to 3200 mb/s and write of 1800 mb/s.

At once, on the end, after a months long fight, I´m satisfied.

Reporting for the ones who might care.

 

Are the temps after 1 fire strike run or the 3DM stress test? Cause with one run you usually get 10-15*C lower. My GPU only goes to about 60*C with a single run.

 

Ran it two times and Temps hadn't changed at all, same values.

Is it on a 14inch?

This refresh seems to be a different story than, at least, my 2015 and its pretty close to the same class average, no obvious glitches or anything alike too (like they 2016 fans).

 

Well - can you run Unigine Heaven? That is a great way to test usually. It takes 15-20 minutes for temps to reach equilibrium.

 

Will do once I'm back at home.

BTW 2 hours on Ow max settings didn't let it go over ~75° C.

Anw, updating this ASAP.

 

Saved it like this as I thought I could upload a html file, which I can't, so no SS.

Used the free version, set it to extreme, I let the GPU heat up to 75° C than I benchmarked; max CPU temp has been 70° C, max GPU temp has been 77° C.

 

Not bad at all. Hopefully the temps remain low and no more issues follow.

 

Makyura, I wanted to compare with my skylake version, after undervolting, but I ran it at 1080p....any reason why you ran it 1600x900?
I let it warm up 70 degrees like don_svetlio suggested....and this is what I got....GPU temps didn´t go past 77 degrees and CPU 73 degrees, undervolted though.
I guess the temps are Ok for this kind of machine...hopefully nothing will give in the next year or so, which by then I plan I getting something else when the next gen Nvidias are out.

 

I see now, you ran yours at preset extreme...I will give it a try later.

 

this is what I got with extreme settings....temps are the same max. on GPU 77 degrees.
the scores are similar to yours expect that it chocked on some point and the min FPS came in at 8.8.

 

Yea that's why

Looks likes this how the notebook scores and that once tricked the Sky Lake scores as good as the Kaby