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.

    M17x-R2 BSOD a couple of times a day

    Discussion in 'Alienware 17 and M17x' started by TurbodTalon, Sep 16, 2011.

  1. TurbodTalon

    TurbodTalon Notebook Virtuoso

    Reputations:
    1,392
    Messages:
    3,147
    Likes Received:
    158
    Trophy Points:
    131
    I'm trying to figure out how to properly use the WinDbg to analyze the crash dumps from my several BSODs a day. When I load a dump, I get a bunch of crap about my debugger not using the proper symbols. It does, however, still tell me what the problem probably is. Will the information that it won't display because of the symbol issue actually pinpoint the driver that's causing my problems? I keep getting this:

    Probably caused by : ntoskrnl.exe ( nt+7cc40 )

    That doesn't tell me anything in a Google search. I would like to find the actual driver that's causing this so I can uninstall it, or update it. The BSODs have caused me to lose some pretty important work in Excel documents, etc.

    Here's the latest dump from this evening. Can someone please tell me how to get the correct symbols? I DL'd a 300+MB symbol package from the MS website, pointed the debugger to it, and still got the error message. Any help is much appreciated.
     
    TurbodTalon, Sep 16, 2011
    #1
  2. katalin_2003

    katalin_2003 NBR Spectre Super Moderator

    Reputations:
    14,963
    Messages:
    5,671
    Likes Received:
    1,521
    Trophy Points:
    331
    Hey, Turbod, download WhoCrashed see if you get better luck.
     
    katalin_2003, Sep 16, 2011
    #2
  3. TurbodTalon

    TurbodTalon Notebook Virtuoso

    Reputations:
    1,392
    Messages:
    3,147
    Likes Received:
    158
    Trophy Points:
    131
    WhoCrashed says the same thing, unfortunately. I have boiled it down to a driver problem though, because both programs say the same thing. No specific driver is mentioned though. If I get bored, I'll start uninstalling things to see if any improvements are made. Thank you for your help.
     
    TurbodTalon, Sep 17, 2011
    #3
  4. TurbodTalon

    TurbodTalon Notebook Virtuoso

    Reputations:
    1,392
    Messages:
    3,147
    Likes Received:
    158
    Trophy Points:
    131
    OK, I've had the 'opportunity' to analyze a few more BSOD dumps, including one that happened 15 seconds after I turned on my laptop this morning. Ntoskrnl.exe is the culprit 9 times out of 10. Does anyone have any other insight to this problem. I'm open to anything. Thanks guys.
     
    TurbodTalon, Sep 18, 2011
    #4
  5. almostinsane

    almostinsane Notebook Consultant

    Reputations:
    11
    Messages:
    132
    Likes Received:
    0
    Trophy Points:
    30
    More than likely its a hardware failure.
     
    almostinsane, Sep 18, 2011
    #5
  6. TurbodTalon

    TurbodTalon Notebook Virtuoso

    Reputations:
    1,392
    Messages:
    3,147
    Likes Received:
    158
    Trophy Points:
    131
    I've had this same issue since I bought the laptop, never cared to ask for anyone's advice before this though. I've run memtest on my RAM, as well as beat the living hell out of the GPU and CPU with FurMark and Prime95 respectively. Not real sure what's going on here. I believe it to be some sort of software failure/incompatibility.
     
    TurbodTalon, Sep 18, 2011
    #6