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.

    MX7122 BSOD Errors

    Discussion in 'Gateway and eMachines' started by Tidalious, Mar 31, 2009.

  1. Tidalious

    Tidalious Newbie

    Reputations:
    0
    Messages:
    1
    Likes Received:
    0
    Trophy Points:
    5
    Hi, I decided to update my ati Xpress 200M series drivers and got the newest IGP/motherboard driver along with their catalyst control center. Once I did this I noticed I was starting to get more BSODs.
    I decided to reformat and install only things like firefox and the drivers listed on the Gateway site for my model, however I am still receiving BSODs when I try and install World of Warcraft or transfer the whole folder from another computer to this one.
    This is from one of the Minidumps using WinDBG, and I'll attach the minidumps for any more knowledgeable people out there.

    Thanks in advance!


    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high. This is usually
    caused by drivers using improper addresses.
    If kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: 0050017a, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000008, value 0 = read operation, 1 = write operation
    Arg4: 0050017a, address which referenced memory

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


    READ_ADDRESS: 0050017a

    CURRENT_IRQL: 2

    FAULTING_IP:
    +f8
    0050017a ?? ???

    PROCESS_NAME: Steam.exe

    CUSTOMER_CRASH_COUNT: 3

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0xD1

    LAST_CONTROL_TRANSFER: from 88c99940 to 0050017a

    FAILED_INSTRUCTION_ADDRESS:
    +f8
    0050017a ?? ???

    STACK_TEXT:
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    b9f8dc3c 88c99940 88c998d0 804f99be 000025ff 0x50017a
    b9f8dc6c bf802ec4 00000001 0000000d 00000001 0x88c99940
    b9f8dca8 bf801aa8 000025ff 00000000 00000001 win32k!xxxSleepThread+0x192
    b9f8dcec bf80f106 b9f8dd18 000025ff 00000000 win32k!xxxRealInternalGetMessage+0x418
    b9f8dd4c 8053c808 0012e1d8 00000000 00000000 win32k!NtUserGetMessage+0x27
    b9f8dd4c 7c90eb94 0012e1d8 00000000 00000000 nt!KiFastCallEntry+0xf8
    0012e1b4 00000000 00000000 00000000 00000000 0x7c90eb94


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    win32k!xxxSleepThread+192
    bf802ec4 8945fc mov dword ptr [ebp-4],eax

    SYMBOL_STACK_INDEX: 2

    SYMBOL_NAME: win32k!xxxSleepThread+192

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: win32k

    IMAGE_NAME: win32k.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 41107f7a

    FAILURE_BUCKET_ID: 0xD1_CODE_AV_BAD_IP_win32k!xxxSleepThread+192

    BUCKET_ID: 0xD1_CODE_AV_BAD_IP_win32k!xxxSleepThread+192

    Followup: MachineOwner
     

    Attached Files:

    Tidalious, Mar 31, 2009
    #1