The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    Weird Freezes on Load after Upgrading

    Discussion in 'Alienware M15x' started by Taxifare, May 20, 2018.

  1. Taxifare

    Taxifare Notebook Enthusiast

    Reputations:
    0
    Messages:
    23
    Likes Received:
    1
    Trophy Points:
    6
    Hi Gurus,

    Thanks for reading my lengthy post, but I need some help on my rig. :(
    Recently I upgraded my M15X from the following specs:


    Before upgrade:
    I7-740QM
    8GB DDR3 RAM
    120GB SSD
    Nvidia Geforce GTX460M
    150W PSU
    Windows 7

    to

    I7-740QM
    8GB DDR3 RAM
    120GB SSD
    1TB SSHD FireCuda (Replaced CD Rom)
    Nvidia Geforce GTX860M (Replaced 460M)
    150W PSU
    Windows 10 (Upgraded from Windows 7)

    After successfully performing the hardware upgrade and reinstallation of windows, drivers & monitoring temperatures to be below 70'c, it is currently having an issue.

    Issues
    Whenever I run a game/benchmark (UniEngine) software, the machine freezes and proceed to auto-restart within 2 minutes. However, after it auto-restarts, it is running smoothly for hours.

    However, when I switch off the rig for the night (for at least 6 hours with both state "tested with both power brick switch on and switch off"), and boot it up again. It freezes and proceed to auto-restart within 2 minutes again. And when it restarts, it is running smoothly for hours as usual without booting.

    Workaround
    I do not know what is causing the error and the current workaround is, I would let the rig to crash on first boot and restarts itself, then use it as if it was healthy after it reboots.

    Errors in Event Viewer
    Kernel Power-41 (Obvious reasons)
    Constraint to a periodic tick.

    Early thanks to anyone who would share an advice or suggestion. :)
     
    Last edited: May 20, 2018
    Taxifare, May 20, 2018
    #1
  2. Papusan

    Papusan Jokebook's Sucks! Dont waste your $$$ on Filthy

    Reputations:
    42,732
    Messages:
    29,855
    Likes Received:
    59,692
    Trophy Points:
    931
    Papusan, May 20, 2018
    #2
    Ashtrix likes this.
  3. Taxifare

    Taxifare Notebook Enthusiast

    Reputations:
    0
    Messages:
    23
    Likes Received:
    1
    Trophy Points:
    6
    Taxifare, May 20, 2018
    #3
  4. Mastermind5200

    Mastermind5200 Notebook Virtuoso

    Reputations:
    372
    Messages:
    2,152
    Likes Received:
    826
    Trophy Points:
    131
    Hmm had a similar issue with my 765M in my M17 R1, its probably GPU driver related (thats what it was for me)
     
    Mastermind5200, May 21, 2018
    #4
  5. Taxifare

    Taxifare Notebook Enthusiast

    Reputations:
    0
    Messages:
    23
    Likes Received:
    1
    Trophy Points:
    6
    Hey Grant,

    Hmm... What did you do to solve it? Reinstall the driver?

    What was the last stable driver for 860M for M15X?
     
    Last edited: May 21, 2018
    Taxifare, May 21, 2018
    #5
  6. Mastermind5200

    Mastermind5200 Notebook Virtuoso

    Reputations:
    372
    Messages:
    2,152
    Likes Received:
    826
    Trophy Points:
    131
    Well, I never truly fixed the issue, and I don't know any drivers for the M15X (sorry!) But try another driver, if not I honestly have no clue.....
     
    Mastermind5200, May 21, 2018
    #6
  7. Taxifare

    Taxifare Notebook Enthusiast

    Reputations:
    0
    Messages:
    23
    Likes Received:
    1
    Trophy Points:
    6
    Solved!

    I'm gonna share the solution if anyone happen to run in to similar problem.
    Apparently there was something wrong with the vbios of the card upon purchase. Seller said it was new but after few days (weeks) of diagnosting, realized that the memory clocks had been tripping into weird numbers.

    Solution: Reflashed vbios. Works sweet now!
     
    Taxifare, Jun 13, 2018
    #7