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.

    Alienware m17x R3, AMD 6970m GPU Code 43 Please help!

    Discussion in 'Gaming (Software and Graphics Cards)' started by TbanksIV, Jun 26, 2014.

  1. TbanksIV

    TbanksIV Newbie

    Reputations:
    0
    Messages:
    1
    Likes Received:
    0
    Trophy Points:
    5
    Hey, I have an Alienware m17x R3, and my GPU is showing up in Device Manager with a Code 43: Windows has stopped the device because it has reported a problem, error.

    This error had showed up before, but it fixed itself somehow, I believe it's fixed itself twice now after reboots, and shut downs.

    Problem is this time it seems to be sticking. GPUZ shows "Unknown" as the BIOS for the GPU, and also shows reduced clock speed and shaders than what is normal. This is all with drivers installed, with no GPU drivers installed it shows Code 10: The device cannot start.

    This is driving me nuts, I've had this computer for 3 years now, and for only about 6 months had it operated correctly. I have no warranty left over with Alienware, so unfortunately that's not an option.

    I'll take any advice I can get here. Thanks guys.
     
    TbanksIV, Jun 26, 2014
    #1
  2. kuchiose

    kuchiose Notebook Enthusiast

    Reputations:
    0
    Messages:
    41
    Likes Received:
    2
    Trophy Points:
    16
    did you fiddle with the bios, or even overclock your gpu at some time ?
    i would've suggested to update the drivers but that doesn't seem to work...

    run cleaner to find registry errors maybe?
    worst you can do is reinstalling your Os (windows ?), it's either the driver's problem or from your OS
     
    kuchiose, Jul 3, 2014
    #2