1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

BSOD when running SQL Server Management Studio

Discussion in 'Windows XP' started by smhouston, 2008/05/18.

  1. 2008/05/18
    smhouston

    smhouston Inactive Thread Starter

    Joined:
    2004/05/24
    Messages:
    77
    Likes Received:
    0
    Hello, I hope you can help me as this is driving me nuts!

    Whenever I'm running SQL Server Management Studio my PC seems to get BSOD! Sometimes it happens after using it for 5minutes, othertimes it can happen after an hour of use. I've got a copy of the dump file but I don't know how to read thems o wondeirng if someone could?


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

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000008E, {c0000005, bf8e5e91, b4909868, 0}

    Probably caused by : win32k.sys ( win32k!UserGetRedirectedWindowOrigin+28 )

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

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

    KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
    This is a very common bugcheck. Usually the exception address pinpoints
    the driver/function that caused the problem. Always note this address
    as well as the link date of the driver/image that contains this address.
    Some common problems are exception code 0x80000003. This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG. This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG. This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: c0000005, The exception code that was not handled
    Arg2: bf8e5e91, The address that the exception occurred at
    Arg3: b4909868, Trap Frame
    Arg4: 00000000

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


    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx ". The memory could not be "%s ".

    FAULTING_IP:
    win32k!UserGetRedirectedWindowOrigin+28
    bf8e5e91 8b5040 mov edx,dword ptr [eax+40h]

    TRAP_FRAME: b4909868 -- (.trap 0xffffffffb4909868)
    ErrCode = 00000000
    eax=00000000 ebx=00000001 ecx=00000b20 edx=0000000b esi=e4555de0 edi=00000005
    eip=bf8e5e91 esp=b49098dc ebp=b49098dc iopl=0 nv up ei pl zr na pe nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
    win32k!UserGetRedirectedWindowOrigin+0x28:
    bf8e5e91 8b5040 mov edx,dword ptr [eax+40h] ds:0023:00000040=????????
    Resetting default scope

    CUSTOMER_CRASH_COUNT: 2

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0x8E

    PROCESS_NAME: SqlWb.exe

    LAST_CONTROL_TRANSFER: from bf816709 to bf8e5e91

    STACK_TEXT:
    b49098dc bf816709 16010f26 b4909910 0012ea7c win32k!UserGetRedirectedWindowOrigin+0x28
    b4909920 8054086c 16010f26 e4555de0 00000004 win32k!GreGetRandomRgn+0xde
    b4909920 7c90eb94 16010f26 e4555de0 00000004 nt!KiFastCallEntry+0xfc
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    0012ea94 00000000 00000000 00000000 00000000 0x7c90eb94


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    win32k!UserGetRedirectedWindowOrigin+28
    bf8e5e91 8b5040 mov edx,dword ptr [eax+40h]

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: win32k!UserGetRedirectedWindowOrigin+28

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: win32k

    IMAGE_NAME: win32k.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 47e0e106

    FAILURE_BUCKET_ID: 0x8E_win32k!UserGetRedirectedWindowOrigin+28

    BUCKET_ID: 0x8E_win32k!UserGetRedirectedWindowOrigin+28

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




    Steven
     
  2. 2008/05/18
    Steve R Jones

    Steve R Jones SuperGeek Staff

    Joined:
    2001/12/30
    Messages:
    12,315
    Likes Received:
    252
    While you're waiting for a reply, Searching the MS Knowledgebase using the STOP: 0x00 error code could help find a solution.
     

  3. to hide this advert.

  4. 2008/05/19
    bdesmond

    bdesmond Inactive

    Joined:
    2008/05/19
    Messages:
    36
    Likes Received:
    0
    Without seeing the dump I couldn't say for certain, but I'd guess it's probably your video driver. Try getting the latest from whomever.
     

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.