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-R3 Random Lockups and BSODs

    Discussion in 'Alienware 17 and M17x' started by Agent CoolBlue, Mar 18, 2012.

  1. Agent CoolBlue

    Agent CoolBlue Notebook Deity NBR Reviewer

    Reputations:
    619
    Messages:
    1,487
    Likes Received:
    5
    Trophy Points:
    56
    I love my R3 but little problems keep popping up that prevent me from fully enjoying it.

    1. My R3 randomly locks up out of nowhere and nothing brings it out (I.E. Ctrl+Alt+Delete doesn't work) and after about 60 seconds, it just comes back and everything I tried doing to bring it out pops up (such as Ctrl+Alt+Delete).

    2. Random BSODs; The blue screen says Driver_Power_State_Failure or something along the lines of that...

    Any idea what is happening and what I can do to fix it? The BSODs are occurring every 10-15 minutes...
     
    Agent CoolBlue, Mar 18, 2012
    #1
  2. The Revelator

    The Revelator Notebook Prophet

    Reputations:
    5,395
    Messages:
    4,571
    Likes Received:
    2
    Trophy Points:
    105
    Easiest approach is to restore settings to an earlier time when everything was working. Start>Control Panel>System & Security>Action Center>Restore your computer to an earlier time and then select an appropriate Restore Point from the list.

    It's very difficult for anyone to provide much help without more information about your components, when the issue(s) arose, what changes, additions and/or revisions had been made immediately preceding the problem, etc. You have to help us help you. Without more, restore is one of the few generic solutions available.
     
    The Revelator, Mar 18, 2012
    #2
  3. cleverpseudonym

    cleverpseudonym PG RATED

    Reputations:
    635
    Messages:
    1,402
    Likes Received:
    18
    Trophy Points:
    56
    it is a driver issue, likely with your GPU, but without the rest of the BSOD code it will be impossible to know.I would do a fresh in stall of windows 7 and install the drivers in the specific order required by the machine( i believe there is a guide by batboy in this section). I wouldn't use the Cd's that came with the machine ( i got mine last week and the driver disk is useless) or even the Windows disk that came with the machine. its best to use a clean OEM image to rule out software. Dell Recovery Cd;s are notorious for being corrupt & buggy

    I did experience something similar( wifi driver issue) during use of the OS that Dell installed, but since i did a fresh install that day i haven't had one issue.
     
    cleverpseudonym, Mar 18, 2012
    #3
  4. aznpos531

    aznpos531 Notebook Evangelist

    Reputations:
    457
    Messages:
    636
    Likes Received:
    1
    Trophy Points:
    31
    If you upload you dump files from C:/Windows/Minidump I can analyze it for you.
    As for the lock-ups, are you using an SSD by any chance?
     
    aznpos531, Mar 18, 2012
    #4
  5. Agent CoolBlue

    Agent CoolBlue Notebook Deity NBR Reviewer

    Reputations:
    619
    Messages:
    1,487
    Likes Received:
    5
    Trophy Points:
    56
    Yes I am using a Crucial C300 (64GB)

    I restored my computer all the way back to when I first got it, the restore basically left my computer bone stock. I don't get BSODs when on AC but when on battery and watching videos, I will BSOD. This leads me to believe that it is a Graphics/Optimus issue?

    Here is the message I get...

    "A problem has been detected and Windows has been shut down to prevent damage
    to your computer.

    The problem seems to be caused by the following file: ntoskrnl.exe

    DRIVER_POWER_STATE_FAILURE

    If this is the first time you've seen this stop error screen,
    restart your computer. If this screen appears again, follow
    these steps:

    Check to make sure any new hardware or software is properly installed.
    If this is a new installation, ask your hardware or software manufacturer
    for any Windows updates you might need.

    If problems continue, disable or remove any newly installed hardware
    or software. Disable BIOS memory options such as caching or shadowing.
    If you need to use safe mode to remove or disable components, restart
    your computer, press F8 to select Advanced Startup Options, and then
    select Safe Mode.

    Technical Information:

    *** STOP: 0x1000009f (0x0000000000000004, 0x0000000000000258, 0xfffffa800ca8a680,
    0xfffff80000b9c3d0)

    *** ntoskrnl.exe - Address 0xfffff800030924da base at 0xfffff80003013000 DateStamp
    0x4e02aaa3"

    Here is my dump file...

    [​IMG]
     
    Agent CoolBlue, Mar 18, 2012
    #5
  6. aznpos531

    aznpos531 Notebook Evangelist

    Reputations:
    457
    Messages:
    636
    Likes Received:
    1
    Trophy Points:
    31
    If it isn't already, try moving the SSD to Bay 1 (the middle one next to the GPU). See if that fixes the lockups. If not, try uninstalling IRST and run the SSD on the Microsoft AHCI drivers. I used to get the exact same thing and moving the drive to bay 1 and using MSAHCI fixed it.

    As for the dump file, some info is missing from the screen cap you posted. Please zip and upload the actual .dmp file. That will give me more info.
     
    aznpos531, Mar 18, 2012
    #6
  7. Agent CoolBlue

    Agent CoolBlue Notebook Deity NBR Reviewer

    Reputations:
    619
    Messages:
    1,487
    Likes Received:
    5
    Trophy Points:
    56
    So I...

    1. Reseated/swapped position of my RAM (2x4GB)
    2. Swapped position of my SSD/HDD
    3. Reformatted
    4. Re-installed drivers in proper order

    I am still getting BSODs when on battery and watching videos or anything that requires graphics processing but the BSOD screen just blinks for a microsecend and I cannot see what the error is. On top of that, there is no dump file. I use Bluescreenviewer which usually automatically detecs my dump files but it is now finding none.

    This is driving me crazy.

    EDIT: A search for *.dmp revealed a dump file...

    This time is says....

    [​IMG]
     
    Agent CoolBlue, Mar 19, 2012
    #7
  8. Agent CoolBlue

    Agent CoolBlue Notebook Deity NBR Reviewer

    Reputations:
    619
    Messages:
    1,487
    Likes Received:
    5
    Trophy Points:
    56
    Nevermind...

    getting normal Driver_State_Power_Failure BSODs again...


    DRIVER_POWER_STATE_FAILURE (9f)
    A driver is causing an inconsistent power state.
    Arguments:
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: fffffa800776ca10, Physical Device Object of the stack
    Arg3: fffff8000189a3d8, Functional Device Object of the stack
    Arg4: fffffa8009c82ab0, The blocked IRP
     
    Agent CoolBlue, Mar 19, 2012
    #8
  9. aznpos531

    aznpos531 Notebook Evangelist

    Reputations:
    457
    Messages:
    636
    Likes Received:
    1
    Trophy Points:
    31
    Oh...I know why the dump files are gone. You said you had done a system restore. That would've removed any dumps from the crashes that occurred after the date you restored to. :(
    The dump file you found is for a 0x0F4 which happens when an element needed to run the OS is closed or can't be read. Makes sense with the lockups (i.e. not able to read the SSD for the duration of the lockup).

    Without the dump files it'll be hard to determine the cause. You'll have to wait for another BSOD to happen then zip and upload the actual file (not just a bluescreenview screen cap).
     
    aznpos531, Mar 19, 2012
    #9
  10. Agent CoolBlue

    Agent CoolBlue Notebook Deity NBR Reviewer

    Reputations:
    619
    Messages:
    1,487
    Likes Received:
    5
    Trophy Points:
    56
    Agent CoolBlue, Mar 19, 2012
    #10
  11. aznpos531

    aznpos531 Notebook Evangelist

    Reputations:
    457
    Messages:
    636
    Likes Received:
    1
    Trophy Points:
    31
    Hmmm that dump file's wierd. It's much bigger than normal dumps (364MB v.s. the usual 300 to 600KB) and it's missing info as if it's corrupted.

    This is what your dump looks like:

    Code: 
    *******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa800776ca10, fffff8000189a3d8, fffffa8009c82ab0}

GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner
---------

GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
0: kd> !analyze -v
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get program counter
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa800776ca10, Physical Device Object of the stack
Arg3: fffff8000189a3d8, Functional Device Object of the stack
Arg4: fffffa8009c82ab0, The blocked IRP

Debugging Details:
------------------

GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147

DRVPOWERSTATE_SUBCODE:  3

IRP_ADDRESS:  fffffa8009c82ab0

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

CURRENT_IRQL:  0

STACK_TEXT: 
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147


STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

BUCKET_ID:  CORRUPT_MODULELIST

Followup: MachineOwner
---------

GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147

    and this is what a normal dump should look like:

    Code: 
    *******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa8007faaa10, fffff80000b9c3d8, fffffa800aef9900}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : pci.sys

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8007faaa10, Physical Device Object of the stack
Arg3: fffff80000b9c3d8, Functional Device Object of the stack
Arg4: fffffa800aef9900, The blocked IRP

Debugging Details:
------------------


DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  pci.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7928f

MODULE_NAME: pci

FAULTING_MODULE: fffff88000e00000 pci

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

STACK_TEXT: 
fffff800`00b9c388 fffff800`02d05cd2 : 00000000`0000009f 00000000`00000003 fffffa80`07faaa10 fffff800`00b9c3d8 : nt!KeBugCheckEx
fffff800`00b9c390 fffff800`02ca35fc : fffff800`00b9c4c0 fffff800`00b9c4c0 00000000`00000000 00000000`00000002 : nt! ?? ::FNODOBFM::`string'+0x34a90
fffff800`00b9c430 fffff800`02ca3496 : fffff880`00fc02b0 00000000`007423bf 00000000`00000000 fffff880`073a8c57 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00b9c4a0 fffff800`02ca337e : 00000114`750b9aca fffff800`00b9cb18 00000000`007423bf fffff800`02e11a68 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9caf0 fffff800`02ca3167 : 0000003b`330144c2 0000003b`007423bf 0000003b`330144f2 00000000`000000bf : nt!KiTimerExpiration+0x1be
fffff800`00b9cb90 fffff800`02c8f96a : fffff800`02e0de80 fffff800`02e1bcc0 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cc40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cc00 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_3_ACPI_IMAGE_pci.sys

BUCKET_ID:  X64_0x9F_3_ACPI_IMAGE_pci.sys

Followup: MachineOwner
---------

    See if you can recreate a BSOD and then upload the dump file from that.

    Edit: I have a few things in mind that may help to fix the issues you're having but I'd like to see a proper dump from a BSOD before I suggest anything. If you can't recreate a BSOD then the only thing to do is to wait for one to happen. If you don't get any...well I guess that's not a problem now is it? :D
     
    aznpos531, Mar 19, 2012
    #11
  12. R3G1m3nT4L

    R3G1m3nT4L Newbie

    Reputations:
    0
    Messages:
    7
    Likes Received:
    0
    Trophy Points:
    5
    Funny old thing got my r3 last week factryinstall updated all the drivers etc loaded wow bf3 fri, sat worked like adreamthen sunday bsod same error so im interested in this one as well will try and bang up a dump file tonight see if they are similar
     
    R3G1m3nT4L, Mar 19, 2012
    #12
  13. Agent CoolBlue

    Agent CoolBlue Notebook Deity NBR Reviewer

    Reputations:
    619
    Messages:
    1,487
    Likes Received:
    5
    Trophy Points:
    56
    Hey, so I disabled IGP with the modded A08 BIOs and I have not gotten a BSOD since (crossing fingers here). I isolated this issue by reenabling IGP and low and behold, BSODs again. I tried flashing back to stock A08 with no luck.

    Is it safe to assume it is an Optimus/video driver issue? If so...what can I do...?

    I'm happy that I have a way of using the laptop on battery power without BSODing but my battery life is hindered greatly without Optimus.
     
    Agent CoolBlue, Mar 20, 2012
    #13
  14. aznpos531

    aznpos531 Notebook Evangelist

    Reputations:
    457
    Messages:
    636
    Likes Received:
    1
    Trophy Points:
    31
    Try this:

    1. Go to Control Panel>Programs and Features
    2. Uninstall all nVidia drivers
    3. Restart into safe mode and use CCleaner or Driver Sweeper to clear out all registry entries for the nVidia driver.
    4. Restart normally and reinstall the latest drivers which are 260.10 I believe. During installation choose Custom Install>Clean Installation.

    If it's a driver issue this may fix it.
     
    aznpos531, Mar 20, 2012
    #14
  15. Agent CoolBlue

    Agent CoolBlue Notebook Deity NBR Reviewer

    Reputations:
    619
    Messages:
    1,487
    Likes Received:
    5
    Trophy Points:
    56
    Did all of that and same thing...BSODs...

    Here is something weird that might help solve our problem.

    I ran the Diagnostic Tool (F12 in BIOS) that comes with the M17x and everything checked out besides the RAM. I just installed 8GB of 1600mhz Crucial RAM and according to the diagnostic, there are integrity issues.

    This is weird...I just swapped back the 4GB of stock RAM that came with the laptop and am testing again now...will report my findings...

    EDIT: Stock RAM/My Ram still both result in BSODs. Driver Sweeper/CC Cleaner with a a fresh install of latest drivers still doesn't work. Only solution still seems to be to disable the IGP completely via modded A08 BIOS. This is really frustrating.
     
    Agent CoolBlue, Mar 20, 2012
    #15
  16. SlickDude80

    SlickDude80 Notebook Prophet

    Reputations:
    3,262
    Messages:
    4,997
    Likes Received:
    3
    Trophy Points:
    106
    Agent, have you run memtest86 on that new ram?

    You probably should leave the IGP disabled as optimus is great in theory but is often poorly executed
     
    SlickDude80, Mar 20, 2012
    #16
  17. SkylineLvr

    SkylineLvr Notebook Deity

    Reputations:
    446
    Messages:
    896
    Likes Received:
    203
    Trophy Points:
    56
    I can vouch for this. Optimus was giving me a headache for half a day. Hopefully I'll be able to turn it back on one day, as I would like to be able to give my 580M a rest at times.
     
    SkylineLvr, Mar 20, 2012
    #17
  18. The Revelator

    The Revelator Notebook Prophet

    Reputations:
    5,395
    Messages:
    4,571
    Likes Received:
    2
    Trophy Points:
    105
    Have you tried reinstalling the Intel Graphics drivers? If the problem is caused by a display driver, it's more likely the IGP drivers, not the Nvidia drivers.
     
    The Revelator, Mar 20, 2012
    #18
  19. aznpos531

    aznpos531 Notebook Evangelist

    Reputations:
    457
    Messages:
    636
    Likes Received:
    1
    Trophy Points:
    31
    That's a good point. Especially you don't get the problems with IGP disabled.
     
    aznpos531, Mar 21, 2012
    #19
  20. Agent CoolBlue

    Agent CoolBlue Notebook Deity NBR Reviewer

    Reputations:
    619
    Messages:
    1,487
    Likes Received:
    5
    Trophy Points:
    56
    Just uninstalled/reinstalled the latest IGP drivers straight from Intel, still BSODing. I think I may just give up on this issue and leave the IGP disabled. If it bothers me enough in the future, I will just give Dell a call and have them replace my motherboard or whatever else needs to be replaced as I have 3.5 years left of Complete Care.

    Surprisingly enough, even with IGP off, I am still getting around 2.5 hours of battery life w/ wifi on, screen brightness at about 40%-50%, and watching youtube/various other activities.

    Is there a way I can quickly downclock the 580m when on battery? I remember when I had my Sager 8690 w/ 5870m, there was a guide on how to make two buttons on the desktop. One button downclocked the 5870 when not gaming and another set it back to normal clocks when you wanted to game.
     
    Agent CoolBlue, Mar 21, 2012
    #20
  21. SkylineLvr

    SkylineLvr Notebook Deity

    Reputations:
    446
    Messages:
    896
    Likes Received:
    203
    Trophy Points:
    56
    You can use nVidia Inspector and create shortcuts on your desktop of the clocks you have. Currently I have a 10%, 15%, and 20% OC saved. I haven't gamed yet, so not sure which clocks I will play on (that's if the stock clocks aren't enough for me).
     
    SkylineLvr, Mar 21, 2012
    #21
  22. Agent CoolBlue

    Agent CoolBlue Notebook Deity NBR Reviewer

    Reputations:
    619
    Messages:
    1,487
    Likes Received:
    5
    Trophy Points:
    56
    Thanks for the advice Skyline. I just downloaded nvidiaInspector and created a couple shortchuts (50/100/100) but even after applying it, the 580M stays at it's idle clocks of (74/324/147). Perhaps this is the lowest it can go?

    EDIT: Nevermind, I just had to change the Default Power Level (P1) instead of P0 to be able to apply lower clocks. I made a shortcut for stock clocks but clicking on it doesn't apply for some reason?
     
    Agent CoolBlue, Mar 21, 2012
    #22
  23. GeoCake

    GeoCake http://ted.ph

    Reputations:
    1,491
    Messages:
    1,232
    Likes Received:
    2
    Trophy Points:
    56
    On battery life it automatically downclocks to the lowest possible clocks... 50.6/67.5/101Mhz
     
    GeoCake, Mar 21, 2012
    #23