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 Crashes - Can you interpret log?

    Discussion in 'Alienware 17 and M17x' started by Azeroth, Dec 4, 2011.

  1. Azeroth

    Azeroth Notebook Consultant

    Reputations:
    180
    Messages:
    160
    Likes Received:
    26
    Trophy Points:
    41
    Any thoughts based on this log what might be causing random blue screen/reboots on an m17x? The same entry is in the log over the last few day. The log below was taken from the program WhoCrashed which I read about on this forum.


    On Sun 12/4/2011 6:52:00 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\120411-10795-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
    Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80001EAAF00, 0x0, 0xFFFFFFFFFFFFFFFF)
    Error: KMODE_EXCEPTION_NOT_HANDLED
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
     
    Azeroth, Dec 4, 2011
    #1
  2. maxheap

    maxheap caparison horus :)

    Reputations:
    1,244
    Messages:
    3,294
    Likes Received:
    191
    Trophy Points:
    131
    wow I got a kmode_exception this morning too, what is your rig? (1866mhz? :))
     
    maxheap, Dec 4, 2011
    #2
  3. katalin_2003

    katalin_2003 NBR Spectre Super Moderator

    Reputations:
    14,963
    Messages:
    5,671
    Likes Received:
    1,521
    Trophy Points:
    331
    This could indicate a RAM sticks(s) that went bad. Which one(s) do you have inside?
    To make sure you can download memtest and check the ram sticks for errors. If no error is found we can go from there.
     
    katalin_2003, Dec 4, 2011
    #3
  4. maxheap

    maxheap caparison horus :)

    Reputations:
    1,244
    Messages:
    3,294
    Likes Received:
    191
    Trophy Points:
    131
    already did memtest for 11 hours, no error for me..
     
    maxheap, Dec 4, 2011
    #4
  5. katalin_2003

    katalin_2003 NBR Spectre Super Moderator

    Reputations:
    14,963
    Messages:
    5,671
    Likes Received:
    1,521
    Trophy Points:
    331
    Sorry, gratz, I replied to Azeroth.
    I also read your thread and from what I gathered since the release of the 1866Mhz ram sticks, many people pass the memtest checks but still have problems with them.
    Anyways it seems that 1600Mhz is the sweet spot for sandy bridge.
     
    katalin_2003, Dec 4, 2011
    #5
  6. maxheap

    maxheap caparison horus :)

    Reputations:
    1,244
    Messages:
    3,294
    Likes Received:
    191
    Trophy Points:
    131
    I guess, I will try my best to avoid this error, now trying some stuff with page file as one of the moderators suggested, we'll see :) thanks katalin!
     
    maxheap, Dec 4, 2011
    #6
  7. katalin_2003

    katalin_2003 NBR Spectre Super Moderator

    Reputations:
    14,963
    Messages:
    5,671
    Likes Received:
    1,521
    Trophy Points:
    331
    That's also a good idea if you messed with it or just got corrupted.
    Update us in your thread.

    Good luck
     
    katalin_2003, Dec 4, 2011
    #7
  8. maxheap

    maxheap caparison horus :)

    Reputations:
    1,244
    Messages:
    3,294
    Likes Received:
    191
    Trophy Points:
    131
    well, the final error got me sick of it and right now I am arranging a return... if something happens to my 580m I will destroy the ram for the good of all with an axe...
     
    maxheap, Dec 4, 2011
    #8