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.

    AW 13 R3 always BSOD after exiting games

    Discussion in '2015+ Alienware 13 / 15 / 17' started by ssj92, Jul 31, 2018.

  1. ssj92

    ssj92 Neutron Star

    Reputations:
    2,446
    Messages:
    4,446
    Likes Received:
    5,690
    Trophy Points:
    581
    So I have a weird issue with this laptop. Every single time you play a game, when you exit the game, the laptop BSODs. This happens with basically every game.

    Then upon restarting, the nVidia GPU is shown as "Microsoft Basic Display Adapter". The way to fix this issue is to do a shut down of the laptop and turn it back on (no restarting fixes it).

    Otherwise the laptop is fully stable and can game for hours perfectly fine.

    Any ideas what's causing this? Laptop is out of warranty since March.
     
  2. Reciever

    Reciever D! For Dragon!

    Reputations:
    1,525
    Messages:
    5,350
    Likes Received:
    4,359
    Trophy Points:
    431
    Sounds like it may be tied to optimus? having problems handing it back to the Intel HD?

    Is there a way to disable optimus and run the scenario again?
     
    ssj92 likes this.
  3. ssj92

    ssj92 Neutron Star

    Reputations:
    2,446
    Messages:
    4,446
    Likes Received:
    5,690
    Trophy Points:
    581
    Yes it's definitely an Optimus problem. But I never had it on my first AW 13 R3 (6700HQ). This model (7700HQ) has this issue. If I remember correctly, when using the graphics amp with my Titan X, exiting a game didn't have an issue.

    But I cannot disable Optimus, it's always enabled.
     
  4. pathfindercod

    pathfindercod Notebook Virtuoso

    Reputations:
    1,940
    Messages:
    2,344
    Likes Received:
    2,349
    Trophy Points:
    181
    Are you undervolting?
     
    c69k likes this.
  5. ssj92

    ssj92 Neutron Star

    Reputations:
    2,446
    Messages:
    4,446
    Likes Received:
    5,690
    Trophy Points:
    581
    No everything is completely stock. :(

    I'm going to try and flash the BIOS and reinstall windows once more. There should be a new BIOS by now since it's been running the same one since I bought from you lol
     
    c69k likes this.
  6. ThatOldGuy

    ThatOldGuy Notebook Virtuoso

    Reputations:
    1,310
    Messages:
    2,454
    Likes Received:
    2,588
    Trophy Points:
    181
    Try TrayPwrD3 as a temporary fix. Its a an executable that keeps Dgpu on when not used. Perhaps it will keep Dgpu from turning off on game exit (what may be causing BSOD)
    https://github.com/jobeid/TrayPwrD3

    Also, are you gaming on monitor + alienware AMP? And is monitor plugged into AMP or laptop if so?
     
    c69k likes this.
  7. ssj92

    ssj92 Neutron Star

    Reputations:
    2,446
    Messages:
    4,446
    Likes Received:
    5,690
    Trophy Points:
    581
    Okay sounds good I'll try this. Although I won't have the laptop back until Friday.

    Now my question is...if this works...what can I do to fix the issue? I know this would be a temporary fix but I am wondering what can be causing this then?

    Regarding the AMP, I ran it monthssssss ago when I first had the laptop with Titan X. I don't remember the specifics but I do remember using an external monitor and I believe I also tried the internal monitor. Both did not cause a BSOD after exiting the game I think.
     
  8. ThatOldGuy

    ThatOldGuy Notebook Virtuoso

    Reputations:
    1,310
    Messages:
    2,454
    Likes Received:
    2,588
    Trophy Points:
    181
    My number 1 guess without being able to replicate the issue is a registry error connected to the Intel and Nvidia drivers. In which case you can try a clean sweep of the drivers with an uninstaller that removes all traces. If that doesn't work, a full system wipe of windows