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.

    OCing GPU then BSOD then 555M went missing

    Discussion in 'Alienware 14 and M14x' started by tassadar898, Dec 1, 2011.

  1. tassadar898

    tassadar898 Notebook Evangelist

    Reputations:
    101
    Messages:
    592
    Likes Received:
    24
    Trophy Points:
    31
    I was OCing the GPU after flashing the increase GPU voltage modded a05 bios and I BSOD during 3dmark11. Upon restart my computer could not detect the 555M. It went completely missing. It was not in device manager and GPU-Z showed no 555M. Only the Intel GPU was present. I reflashed the modded a05 bios and it came back. Has anyone else experienced this?

    Everything seems back to normal and after running 10 more 3dmark11 benchmarks at 10mhz below when I BSOD and it seems stable with temps below 75C.
     
  2. tyler27

    tyler27 Notebook Consultant

    Reputations:
    25
    Messages:
    222
    Likes Received:
    0
    Trophy Points:
    30
    i did once but i was testing an untested bios where the gt 555 voltage was set at 1v and didnt show up, but that wasa the only time for me, how high did you OC it?
     
  3. tassadar898

    tassadar898 Notebook Evangelist

    Reputations:
    101
    Messages:
    592
    Likes Received:
    24
    Trophy Points:
    31
    820/1640/1080. How could a BSOD cause the vbios to get corrupted?
     
  4. CGSDR

    CGSDR Alien Master Race

    Reputations:
    285
    Messages:
    1,477
    Likes Received:
    10
    Trophy Points:
    56
    That happen to me as well, but dont worry, there's a temporary fix, all you need to do is uninstall the NVIDIA Control Panel and reinstall it back, after you reinstall and restart you will see the GT555M working as it should.

    My first time causing it was when I OC it to 850/1700/1080, and play a few chapter in Portal 2. And I also found out that you can only OC up to 800/1600/1080 which is the safe point for me I guess because it doesnt seem to OC if I OC at that clock rate.

    The BSOD doesnt cause the GPU to corrupt, in fact it is programmed to show at the point of overheat or near hardware damage, you will only see a BSOD if Windows think that a hardware is going to be damage, it is to prevent more damage cause to the hardware. For example, If you CPU reach the 100C point, most likely Windows will initiate a BSOD saying thing like Kernel error or a program has cause Windows to shut down or something similar.
     
  5. tassadar898

    tassadar898 Notebook Evangelist

    Reputations:
    101
    Messages:
    592
    Likes Received:
    24
    Trophy Points:
    31
    Gotcha thanks! I figured it was corrupting the vbios cause when I reflashed the bios it came back.
     
  6. thewind21

    thewind21 Notebook Enthusiast

    Reputations:
    0
    Messages:
    41
    Likes Received:
    0
    Trophy Points:
    15
    Happened to me before but I didn't OC my GPU, it just disappear and wasn't listed in BIOS.

    Did a reflash and it came back
     
  7. bigtonyman

    bigtonyman Desktop Powa!!!

    Reputations:
    2,377
    Messages:
    5,040
    Likes Received:
    277
    Trophy Points:
    251
    could have been a heat issue who knows :confused: if you didn't mess with it, it shouldn't have disappeared(in theory).