Was it on the power brick every time it locked up? Does it lock up when you are only on battery?

On 7/6/2017 2:49 PM, Bino Gopal wrote:
Doubt it's heat-while it has a 1060 in it I wasn't using it for gaming *any* of 
those times, and there were plenty of times I was running Mad Max at 1080p, and 
a couple times at 4k even and I could hear the fans spin up and it def get hot, 
but it never had problems then...in fact, when I had the two issues in quick 
succession on 6/22 it was in my lap on a tray and I had a fan blowing on it and 
I thought it was b/c I got it too cold or something like that actually...!

Power...it's been plugged into the same third party power block that Xoticpc 
sold me with the laptop (thing is massive) and it was on my desk the other 
times...I just leave it plugged in and on so it stays fully charged...are you 
thinking surges?  It's plugged into a strip...

Any other ideas anyone? :P
                                                        BINO


-----Original Message-----
From: Hardware [mailto:hardware-boun...@lists.hardwaregroup.com] On Behalf Of 
Joe User
Sent: Thursday, July 6, 2017 4:45 AM
To: hardw...@lists.hardwaregroup.com
Subject: Re: [H] Help! Bino MSI Win10 Pro laptop random lockup issues

Heat or Power?


On 7/5/2017 7:39 PM, Bino Gopal wrote:
Hey guys, really hoping someone has the trick to solve this here...

Got a new latest and greatest MSI gaming laptop (GS73VR 7RF) with Win10 Pro a 
couple months ago from XoticPC who did a couple customizations for me-received 
3/15/17.  I thought last month that it started locking up on me-no response 
except if I hold the power button down and shut it off and then power it up.

It started happening more frequently a couple weeks ago when it did this 4x in 
the same week!  I contacted XoticPC, who said to just restore the OS-but I 
haven't really installed that much and would rather figure out the problem (if 
I can) before I reinstall and run into it again.
Interestingly after the second lockup on 6/22 which happened only 3 mins after 
the first one that day, the second one on 6/26 happened only 6 seconds after 
boot if I'm reading these timestamps right...though I didn't notice until the 
next day, which is when I rebooted.

Anyway, any ideas?  Anyone seen this before?  Any help or suggestions much 
appreciated!

                                                                                
                                  BINO


Reply via email to