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.

    MSI GX640 BSoDs

    Discussion in 'MSI' started by SpiXe, Jan 14, 2011.

  1. SpiXe

    SpiXe Notebook Enthusiast

    Reputations:
    0
    Messages:
    11
    Likes Received:
    0
    Trophy Points:
    5
    Hey.

    So I decided to make a new thread, since this problem just won't go away.

    I keep getting blue screen of deaths with my new GX640. It happens after a while, when the laptop has been running. I don't think it has anything to do with how much I'm running on it anymore..

    One of the weird things - All the dumps are different:
    0x00000021
    0x0000005C
    0x0000007E

    The three dumps I've noticed so far.

    It's not connected to the temp, since it also happens when it's idling. I've already run a memtest - no errors.


    Someone help me please :(
     
  2. kizwan

    kizwan Lord Pringles

    Reputations:
    1,502
    Messages:
    3,229
    Likes Received:
    10
    Trophy Points:
    106
  3. SpiXe

    SpiXe Notebook Enthusiast

    Reputations:
    0
    Messages:
    11
    Likes Received:
    0
    Trophy Points:
    5
    Hm. It is already a total fresh install, so.. And I've never RMA'd anything, but one time's gotta be the first I guess. Should it be sent to MSI or the website I bought it off?
     
  4. kizwan

    kizwan Lord Pringles

    Reputations:
    1,502
    Messages:
    3,229
    Likes Received:
    10
    Trophy Points:
    106
    Usually better RMA'd back to MSI but if you bought it online, for example from Newegg, better RAM'd to them instead. I'm also have no experience RMA'd anything. :) Contact them to know what option you have.
     
  5. SpiXe

    SpiXe Notebook Enthusiast

    Reputations:
    0
    Messages:
    11
    Likes Received:
    0
    Trophy Points:
    5
    As far as I know, there is no MSI "department" in Denmark, so I'd have to send it to Germany or somewhere.. But I'll try mail the site I bought it off and hear what they say :) Thanks.
     
  6. saturnotaku

    saturnotaku Notebook Nobel Laureate

    Reputations:
    4,879
    Messages:
    8,926
    Likes Received:
    4,707
    Trophy Points:
    431
    Random BSODs are usually caused by bad RAM. Pull out one of the sticks and use your computer. If you still get errors, swap one for the other. If that doesn't work, then you probably have a larger problem that may require sending the whole machine back.
     
  7. Molius

    Molius Notebook Consultant

    Reputations:
    23
    Messages:
    275
    Likes Received:
    0
    Trophy Points:
    30
    Hey, there is a MSI certified service center in Denmark:

    Denmark
    Address: Telegrafvej 4-6, 2750 Ballerup
    Product repair status query:+45 7012 4400
    Technical support hotline:+45 7022 3909
    InfoCare fullstory.aspx?m=133&amid=414

    Found that on the official site.
     
  8. Dakins

    Dakins Notebook Evangelist

    Reputations:
    24
    Messages:
    330
    Likes Received:
    0
    Trophy Points:
    30
    Lol what kind of advice is this.

    OP, do a memtest. Go to Memtest86+ - Advanced Memory Diagnostic Tool, download the version of your choice (CD or USB) and create a bootable memtest CD or USB drive. Then reboot the computer, at the MSI logo, bring up the boot menu (F11 I think) and select either the DVD drive or your USB key. Let memtest run for an hour and check back to see if your RAM is bad.

    If it's the case, you won't have to deal with the pain of RMA. You can just buy a new RAM stick and replace the bad one. If memtest doesn't give you any errors, well, it's RMA time I guess.
     
  9. Ayle

    Ayle Trailblazer

    Reputations:
    877
    Messages:
    3,707
    Likes Received:
    7
    Trophy Points:
    106
  10. saturnotaku

    saturnotaku Notebook Nobel Laureate

    Reputations:
    4,879
    Messages:
    8,926
    Likes Received:
    4,707
    Trophy Points:
    431
    Memtest isn't always a reliable barometer. I've had more than one stick of RAM report no errors in memtest but still cause problems. The only way to stop them was to remove a stick outright and test.
     
  11. Dakins

    Dakins Notebook Evangelist

    Reputations:
    24
    Messages:
    330
    Likes Received:
    0
    Trophy Points:
    30
    By doing that, you induce another factor of possible failure by touching the ram sticks with your bare hands. If the RAM is causing error within Windows, it will cause errors within memtest, you just gotta let it run long enough.
     
  12. saturnotaku

    saturnotaku Notebook Nobel Laureate

    Reputations:
    4,879
    Messages:
    8,926
    Likes Received:
    4,707
    Trophy Points:
    431
    If you're careful about handling sensitive electronics by keeping yourself grounded, the risk of damage is minimal at worst.
     
  13. DrewN

    DrewN Notebook Evangelist

    Reputations:
    106
    Messages:
    503
    Likes Received:
    24
    Trophy Points:
    31
    Another tool you can use is NirSoft BlueScreen View ( link), after you install it , just run the software after the initial boot after the BSOD. It reads the dmp file and identifies the bad driver, it's pretty straightforward.

    On a side note I've been experiencing some serious BSODs from a bad atikdmag.sys file after instaling Catalyst 10.12. I was having a ridiculously hard time installing the 10.12 Catalyst drivers correctly, between mistakenly installing the desktop drivers to not uninstalling the old drivers cleanly. My latest attempt to fix my BSODs was to remove the hardware completely from Device Manager, install MSI reference drivers, then completely uninstall reference and install 10.12, whilst updating the BIOS and VBIOS to the latest and cleaning the registry. I'm realy hoping I've solved my BSOD issues for good *knocks on serious wood*.
     
  14. Ayle

    Ayle Trailblazer

    Reputations:
    877
    Messages:
    3,707
    Likes Received:
    7
    Trophy Points:
    106
    I had to go back to the msi drivers for the same reason. 10.12 is broken. It works well in most games, but I had to deal with missing textures in gta4, bsods and also the fact that they have not included the new control center in the mobile drivers...
     
  15. DrewN

    DrewN Notebook Evangelist

    Reputations:
    106
    Messages:
    503
    Likes Received:
    24
    Trophy Points:
    31
    Well, whaddya know, I just recovered from another BSOD caused by the ATI drivers. Thanks for commenting, or I would have felt like I was the only one. I guess it's back to the MSI drivers.