Probably caused by : win32k.sys (win32k!HmgDecrementShareReferenceCount+b)

By BHensley
Jun 3, 2009
  1. Hello,

    I've been researching this recent Blue Screen dump but have not been able to determine what exactly is causing this repeating blue screen. It seems to happen sporadically perhaps 1-3 times a month. I've seen suggestions pointing to Video Card Drivers / Mouse Drivers but I'd like to confirm this. I've confirmed I'm running the latest NVidia Drivers, however from 2006.

    OS: Windows Vista Business (32-bit) SP2

    0: kd> !analyze -v
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    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
    Arg1: 80000004, The exception code that was not handled
    Arg2: 9614a001, The address that the exception occurred at
    Arg3: caeecbd0, Trap Frame
    Arg4: 00000000
    Debugging Details:
    Page 901cc not present in the dump file. Type ".hh dbgerr004" for details
    Page 901cc not present in the dump file. Type ".hh dbgerr004" for details
    PEB is paged out (Peb.Ldr = 7ffdf00c).  Type ".hh dbgerr001" for details
    PEB is paged out (Peb.Ldr = 7ffdf00c).  Type ".hh dbgerr001" for details
    EXCEPTION_CODE: (HRESULT) 0x80000004 (2147483652) - No such interface supported
    9614a001 8b06            mov     eax,dword ptr [esi]
    TRAP_FRAME:  caeecbd0 -- (.trap 0xffffffffcaeecbd0)
    ErrCode = 00000000
    eax=ff9d1670 ebx=d404194c ecx=86c8add0 edx=00000000 esi=ffaa18b8 edi=caeeccd8
    eip=9614a001 esp=caeecc44 ebp=caeecc4c iopl=0         ov up ei ng nz na pe nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00000a86
    9614a001 8b06            mov     eax,dword ptr [esi]  ds:0023:ffaa18b8=00000000
    Resetting default scope
    PROCESS_NAME:  sidebar.exe
    LAST_CONTROL_TRANSFER:  from 81a3b918 to 81ae1b0d
    caeec790 81a3b918 0000008e 80000004 9614a001 nt!KeBugCheckEx+0x1e
    caeecb60 81a5f83a caeecb7c 00000000 caeecbd0 nt!KiDispatchException+0x1a9
    caeecbc8 81a5f7d6 caeecc4c 9614a001 badb0d00 nt!CommonDispatchException+0x4a
    caeecbe4 81a5bf38 849772a8 86ef8810 849772a8 nt!Kei386EoiHelper+0x16e
    caeecc4c 9613862c ffaa18b8 caeeccd8 fe8307b0 nt!KeWaitForSingleObject+0x492
    caeecc84 9613af97 fe8307b0 d404194c 00010080 win32k!_GetDCEx+0x1c
    caeecca8 9613f661 00000000 caeeccd8 5c99dcf7 win32k!xxxBeginPaint+0x17f
    caeecd34 81a5ec7a 0002032e 02c7f1a0 02c7f22c win32k!NtUserBeginPaint+0x4b
    caeecd34 77765e74 0002032e 02c7f1a0 02c7f22c nt!KiFastCallEntry+0x12a
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    02c7f22c 00000000 00000000 00000000 00000000 0x77765e74
    9614a001 8b06            mov     eax,dword ptr [esi]
    SYMBOL_NAME:  win32k!HmgDecrementShareReferenceCount+b
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: win32k
    IMAGE_NAME:  win32k.sys
    FAILURE_BUCKET_ID:  0x8E_win32k!HmgDecrementShareReferenceCount+b
    BUCKET_ID:  0x8E_win32k!HmgDecrementShareReferenceCount+b
    Followup: MachineOwner
  2. Route44

    Route44 TechSpot Ambassador Posts: 11,984   +72

    0x8E errors are almost always caused by hardware issues and are a strong indicator of of corrupted memory (though sometimes these errors can be due to faulty drivers).

    Because your dump cites a Windows driver as the probable cause this isn't much help because they are too general. Taking your error code and coupling it with the randomness of crashes you should run Memtest on your RAM.

    See this link and follow direstions:

    Let it run for a LONG time. The rule is a minimum of 7 Passes. There are 8 individual tests per Pass. Many people will start this test before going to bed and check it the next day.

    If you have errors you have corrupted memory and it needs to be replaced.

    Also, with errors you need to run this test per stick of RAM. Take out one and run the test. Then take that one out and put the other in and run the test. If you start getting errors before 7 Passes you know that stick is corrupted and you don’t need to run the test any further on that stick.

    * Get back to us with your results.
Topic Status:
Not open for further replies.

Similar Topics

Add your comment to this article

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...