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.
← Previous page

    *** Windows 10 + NVIDIA WHQL Drivers are Killing Alienware and Clevo LCD Panels ***

    Discussion in 'Alienware' started by Mr. Fox, Aug 1, 2015.

  1. RaSeven

    RaSeven Notebook Guru

    Reputations:
    11
    Messages:
    66
    Likes Received:
    35
    Trophy Points:
    26
    Status update: living with Win10 from release day until now, without PX, all is fine. Also bought an external monitor a few weeks ago, using it in DP without issues (just if someone thinking an external monitor triggering EDID corruption).

    P.S.
    New and updated profiles from v359.06:
    AC: Syndicate
    Fallout 4
    Just Cause 3
    Rainbow Six: Siege

    ;)
     
    Last edited: Dec 1, 2015
    RaSeven, Dec 1, 2015
    #3001
    GodlikeRU likes this.
  2. GodlikeRU

    GodlikeRU Notebook Deity

    Reputations:
    165
    Messages:
    1,254
    Likes Received:
    562
    Trophy Points:
    131
    GodlikeRU, Dec 1, 2015
    #3002
  3. thegh0sts

    thegh0sts Notebook Nobel Laureate

    Reputations:
    949
    Messages:
    7,700
    Likes Received:
    2,819
    Trophy Points:
    331
    funny, it's december and they're still posting the latest driver on the site....possible backlash from the community?
     
    thegh0sts, Dec 1, 2015
    #3003
  4. Assassin-SL

    Assassin-SL Newbie

    Reputations:
    0
    Messages:
    4
    Likes Received:
    0
    Trophy Points:
    5
    @thegh0sts I recently upgraded to Windows 10 to give it a try after following the display problem for awhile. I got an Alienware 17 R1 with a GTX 980m. I did a reset to factory setting before going to Windows 10. The reset took to me to Windows 8, then upgarded to Windows 8.1 and then to Windows 10. I tried installing the modded drivers with driver signature disabled and in the similar way I do with Windows 8.1. I ended up getting this error : "Nvidia Installer Cannot Continue. This Nvidia Graphic driver is not compatible with this version of Windows. This graphic driver could not find any compatible graphics hardware." Sorry I can't attach images yet I think because this is my first post. Any idea how to fix this issue? I would appreciate any help. For now i have reverted back to Windows 8.1 and the modded drivers installed without any issues.
     
    Assassin-SL, Dec 1, 2015
    #3004
  5. myx

    myx Notebook Deity

    Reputations:
    223
    Messages:
    1,017
    Likes Received:
    85
    Trophy Points:
    66
    You need to disable driver signature enforcement in order to install mod inf. Check advance startup options to disable driver signature.

    Sent from my Nexus 5 using Tapatalk
     
    myx, Dec 1, 2015
    #3005
  6. Assassin-SL

    Assassin-SL Newbie

    Reputations:
    0
    Messages:
    4
    Likes Received:
    0
    Trophy Points:
    5
    I tried that, doesn't work. That's why I find it confusing, works fine in Windows 8.1, not in Windows 10
     
    Assassin-SL, Dec 1, 2015
    #3006
  7. myx

    myx Notebook Deity

    Reputations:
    223
    Messages:
    1,017
    Likes Received:
    85
    Trophy Points:
    66
    If you disable the driver signature and still get the error that no compatible hardware is found, then you did not mod the inf correctly.

    Sent from my Nexus 5 using Tapatalk
     
    myx, Dec 1, 2015
    #3007
  8. Assassin-SL

    Assassin-SL Newbie

    Reputations:
    0
    Messages:
    4
    Likes Received:
    0
    Trophy Points:
    5
    I've been using j95's from TechInferno modded inf, works fine with Windows 8.1. I tried using modded drivers from eurocom v358.50 as well for Windows 10, still got the same error.
     
    Assassin-SL, Dec 1, 2015
    #3008
  9. myx

    myx Notebook Deity

    Reputations:
    223
    Messages:
    1,017
    Likes Received:
    85
    Trophy Points:
    66
    myx, Dec 1, 2015
    #3009
    Assassin-SL likes this.
  10. Assassin-SL

    Assassin-SL Newbie

    Reputations:
    0
    Messages:
    4
    Likes Received:
    0
    Trophy Points:
    5
    Do they have the modded drivers?

    Edit: I didn't read properly, I got what you meant. I'll give it a try later today, thanks
     
    Assassin-SL, Dec 1, 2015
    #3010
  11. myx

    myx Notebook Deity

    Reputations:
    223
    Messages:
    1,017
    Likes Received:
    85
    Trophy Points:
    66
    They have the modded inf file that you can use with the drivers from nvidia or the ones from their website.

    Take your time to read through the instructions if unclear how to use the modded inf.

    Sent from my Nexus 5 using Tapatalk
     
    myx, Dec 1, 2015
    #3011
  12. meteorstorm

    meteorstorm Newbie

    Reputations:
    0
    Messages:
    8
    Likes Received:
    1
    Trophy Points:
    6
    Ah jeez, I just ordered a new laptop that's susceptible to this problem D:
    Sager NP8658-S (Clevo 650RG), Windows 10, GTX 980m

    Woohoo... And if I've understood correctly, downgrading to Windows 8.1 won't help once Windows 10 has done its BIOS shenanigans?
     
    meteorstorm, Dec 1, 2015
    #3012
    Mr. Fox likes this.
  13. Jericho2015

    Jericho2015 Notebook Consultant

    Reputations:
    0
    Messages:
    132
    Likes Received:
    16
    Trophy Points:
    31
    I haven't heard of any of the new Skylake laptops having the issue.
     
    Jericho2015, Dec 1, 2015
    #3013
    meteorstorm likes this.
  14. Mr. Fox

    Mr. Fox BGA Filth-Hating Elitist®

    Reputations:
    37,255
    Messages:
    39,357
    Likes Received:
    70,784
    Trophy Points:
    931
    Mr. Fox, Dec 1, 2015
    #3014
    Spartan@HIDevolution, deadsmiley, RaSeven and 2 others like this.
  15. Mr. Fox

    Mr. Fox BGA Filth-Hating Elitist®

    Reputations:
    37,255
    Messages:
    39,357
    Likes Received:
    70,784
    Trophy Points:
    931
    Mr. Fox, Jan 2, 2016
    #3015
    Vasudev and TomJGX like this.
  16. Mr. Fox

    Mr. Fox BGA Filth-Hating Elitist®

    Reputations:
    37,255
    Messages:
    39,357
    Likes Received:
    70,784
    Trophy Points:
    931
    WINDOWS 10 UPGRADE WARNING

    You sre going to have to either boot with another screen attached to the LVDS port or manually reprogram the EEPROM EDID using a USB flash programming tool and another computer. The easiest solution is to get another screen to boot from, boot into Linux and hotswap the bricked LCD to flash it from the Linux desktop.

    Windows 10 is not safe to use, but it may not not be 100% the sole cause of this issue. It appears to be a contributor or creates the situation where it can occur, either directly or indirectly, through changes NVIDIA made to their drivers accommodating Windows 10.

    Anecdotally, I can tell you that all heck broke loose around Windows 10. Everything was just peachy, I installed Windows 10 RTM on my M18xR2 and that brought a screeching halt to the world I was happy in. To further confound my understanding, the simple act of installing Windows 10 on the Alienware 18 bricked the screen without EVGA Precision X being installed. EVGA Precision X being installed on the M18xR2 bricked the screen every day until I discovered it was contributing to, magnifying or exacerbating the issue. Removing it stopped the problem on the M18xR2.

    I still do not understand why the experts decided EVGA Precision X was the offending product since there are reports of the problem, including my own with the 18, where the LCD corruption has taken place without the help or involvement of EVGA Precision X. But, I am past trying to figure that out now. I doubt we will ever get to the bottom of it or hold the responsible party legally liable for the damage they have done to so many Alienware and Clevo owners, and perhaps the owners of machines brands we have not identified.

    Gabe Aul and Micro$haft ignored us as a group, and me personally as a customer. I sent several messages to Mr. Aul and found it pretty amazing that the dude did not have the courtesy to respond. He did not even have enough tact or diplomacy to delegate a one-time task to a flunky on his team to extend the common courtesy of a " we're sorry to hear of your situation, please have a nice life" sort of canned one-size-fits-all cameo response. I will never forget being treated this way by Micro$oft. They are incapable of and beyond any hope of regaining my trust or respect due to their lack of courtesy in relation to this issue. I know they don't care and don't need it.

    Dell/Alienware was very responsive and I definitely appreciate that.

    NVIDIA was responsive until I reported my findings with EVGA Precision X. Unfortunately, they were quick to blame EVGA and put them under the bus to deflect blame away from their brand.


    Since this is no longer just an "Alienware problem" and the thread is becoming a collector of off-topic posts, let's close this one and participate in the broader community thread covering the same problem...

    ***EVGA Precision X and Windows 7/8/8.1 and especially 10 bricking systems***.
     
    Mr. Fox, Apr 22, 2016
    #3016
    SharpHawk, Amdtaz, ajc9988 and 1 other person like this.
← Previous page