Re: SqlWB BSOD on Table Data Edit 1000008e

The guess is based on the function call to
UserGetRedirectedWindowOrigin
Did you check for updated video drivers?
Did you apply SP 2 for SQL Server on your PC?

I'm not sure why would you have to use Access and linked
tables instead. Writing insert, update, delete statements
is generally a better to edit data in a table.

-Sue

On Sun, 29 Jul 2007 16:44:02 -0700, Andrew Hollamon
<AndrewHollamon@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

So for at least a month now I've been able to reproduce, pretty much at will,
a blue-screen bugcheck from within the sql workbench.

This happens when I'm editing the data within a table, and seems to happen
when I'm tabbing or shift+tabbing between cells. This is consistent and
reproducible.

Windows XP SP2 Tablet PC Edition 2005 (fully patched)
Gateway M-285E Laptop/Convertible
Core 2 Duo 2.00 GHz
2GB memory
ATI Mobility Radeo X1400

SQL Server 2005 Enterprise (from MSDN), fully patched, used as development
environment

I used WinDbg to analyze the crash-dump, which I've included after my
comments. Unfortunately, I cannot determine where to go from here, as the
problem seems to be a kernel mode exception coming from win32k.sys through a
function call from sqlwb.exe. At least as I read it, this is not an area I'm
an expert at.

On another thread, 5/10/2007, a gentleman named Srini posted exactly the
same issue, and Andrew J Kelley came back with a thought that it might be
video driver related. I have no idea how he gets that evaluation, but then
again, this is not my area of expertise.

Any thoughts would be appreciated, maybe a pointer to a QFE for this, or
assistance on determining the cause. This is nearly a show-stopper for some
work ... I'll have to resort to linking access to these tables to get some of
this data in for now.

Thanks,

Andrew Hollamon


Microsoft (R) Windows Debugger Version 6.7.0005.1
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini060307-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is:
srv*C:\WINDOWS\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: C:\WINDOWS\Minidump
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86
compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_qfe.070227-2300
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Sun Jun 3 19:02:47.343 2007 (GMT-7)
System Uptime: 2 days 9:17:34.948
Loading Kernel Symbols
...............................................................................................................................................................................................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, bf8e5f91, a686e868, 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: bf8e5f91, The address that the exception occurred at
Arg3: a686e868, 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
bf8e5f91 8b5040 mov edx,dword ptr [eax+40h]

TRAP_FRAME: a686e868 -- (.trap 0xffffffffa686e868)
ErrCode = 00000000
eax=00000000 ebx=00000001 ecx=00000b20 edx=0000000b esi=e1a31c20 edi=00000005
eip=bf8e5f91 esp=a686e8dc ebp=a686e8dc 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:
bf8e5f91 8b5040 mov edx,dword ptr [eax+40h]
ds:0023:00000040=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: SqlWb.exe

LAST_CONTROL_TRANSFER: from bf816719 to bf8e5f91

STACK_TEXT:
a686e8dc bf816719 c1011043 a686e910 0012ea7c
win32k!UserGetRedirectedWindowOrigin+0x28
a686e920 804dd99f c1011043 e1a31c20 00000004 win32k!GreGetRandomRgn+0xde
a686e920 7c90eb94 c1011043 e1a31c20 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
bf8e5f91 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: 45f013f6

FAILURE_BUCKET_ID: 0x8E_win32k!UserGetRedirectedWindowOrigin+28

BUCKET_ID: 0x8E_win32k!UserGetRedirectedWindowOrigin+28

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


.

Relevant Pages
Loading