Annoyances.org
Home » Windows XP Discussion Forum » Message 1218527922 Search | Help | Home
  
Tip: Run a free scan for common Windows errors ad

re: Question about 'Resolving Hardware Conflicts'
Tuesday, August 12, 2008 at 12:58 am
Windows XP Annoyances Discussion Forum
Posted by samreay (4 messages posted)


Hey guys...

Ive also been having a problem with the Win32k.sys 8E stop error, this time whenever 
I hit the "New" button in Revit 2009, this is the only time it happens and Im stumped. 
First off: It is NOT the ram... entire computer is brand new, hardware has all been 
checked, I believe its a driver fault.

Here's the minidump:

*******************************************************************************
*                                                                             *
*                        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: bf8ee860, The address that the exception occurred at
Arg3: ad3840ec, 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!ThreadLockMenuNoModify+8
bf8ee860 80481502        or      byte ptr [eax+15h],2

TRAP_FRAME:  ad3840ec -- (.trap 0xffffffffad3840ec)
ErrCode = 00000002
eax=000c0364 ebx=bf8eed56 ecx=e2dfbeb0 edx=ad3841a8 esi=000c0364 edi=bc6e15a8
eip=bf8ee860 esp=ad384160 ebp=ad384160 iopl=0         nv up ei pl nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010202
win32k!ThreadLockMenuNoModify+0x8:
bf8ee860 80481502        or      byte ptr [eax+15h],2       ds:0023:000c0379=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  3

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  Revit.exe

LAST_CONTROL_TRANSFER:  from bf8eeccb to bf8ee860

STACK_TEXT:  
ad384160 bf8eeccb 000c0364 ad384178 ad3841d4 win32k!ThreadLockMenuNoModify+0x8
ad384184 bf8eedb7 bc6e15a8 24010ece 00000003 win32k!xxxPaintMenuBar+0x25
ad3841b4 804dd98f 00060352 24010ece 00000003 win32k!NtUserPaintMenuBar+0x68
ad3841b4 7c90e4f4 00060352 24010ece 00000003 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012e21c 00000000 00000000 00000000 00000000 0x7c90e4f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!ThreadLockMenuNoModify+8
bf8ee860 80481502        or      byte ptr [eax+15h],2

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  win32k!ThreadLockMenuNoModify+8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  48025f2a

FAILURE_BUCKET_ID:  0x8E_win32k!ThreadLockMenuNoModify+8

BUCKET_ID:  0x8E_win32k!ThreadLockMenuNoModify+8

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



Written in response to:
re: Question about 'Resolving Hardware Conflicts' (Dakmar: Saturday, July 7, 2007 at 12:36 am)

Responses to this message:
*re: Question about 'Resolving Hardware Conflicts' (Spexx: Tuesday, August 12, 2008 at 3:31 am)

All messages in this thread [show all]
-Question about 'Resolving Hardware Conflicts' (Sam: Sat, Aug 9, 2003, 7:08 pm)
-re: Question about 'Resolving Hardware Conflicts' (Pappy: Sat, Aug 9, 2003, 7:37 pm)
-re: Question about 'Resolving Hardware Conflicts' (david cabrell: Sat, Dec 27, 2003, 12:55 pm)
-re: Question about 'Resolving Hardware Conflicts' (sheik: Sat, Apr 15, 2006, 2:07 am)
-re: Question about 'Resolving Hardware Conflicts' (Patrick Stowe: Sat, Nov 25, 2006, 2:31 am)
*re: Question about 'Resolving Hardware Conflicts' (CDM: Sat, Nov 25, 2006, 3:27 am)
-re: Question about 'Resolving Hardware Conflicts' (Paroxysm: Sat, Jan 27, 2007, 12:41 am)
-re: Question about 'Resolving Hardware Conflicts' (Dakmar: Sat, Jul 7, 2007, 12:36 am)
-re: Question about 'Resolving Hardware Conflicts' (samreay: Tue, Aug 12, 2008, 12:58 am)
-re: Question about 'Resolving Hardware Conflicts' (Spexx: Tue, Aug 12, 2008, 3:31 am)
-re: Question about 'Resolving Hardware Conflicts' (samreay: Wed, Aug 13, 2008, 12:29 am)
-re: Question about 'Resolving Hardware Conflicts' (Spexx: Wed, Aug 13, 2008, 9:09 am)
*re: Question about 'Resolving Hardware Conflicts' (samreay: Wed, Aug 13, 2008, 9:05 pm)
*re: Question about 'Resolving Hardware Conflicts' (Ram: Sat, Aug 9, 2003, 7:38 pm)
-re: Question about 'Resolving Hardware Conflicts' (Ken Hyer: Sat, Aug 9, 2003, 7:44 pm)
*re: Question about 'Resolving Hardware Conflicts' (Homer Simpson: Fri, Dec 10, 2004, 12:55 pm)
-re: Question about 'Resolving Hardware Conflicts' (tamburash: Tue, Sep 2, 2003, 6:33 am)
-re: Question about 'Resolving Hardware Conflicts' (interrupted: Tue, Nov 25, 2003, 1:00 am)
*re: Question about 'Resolving Hardware Conflicts' (tamburash: Tue, Nov 25, 2003, 5:51 am)
*re: Question about 'Resolving Hardware Conflicts' (JTMON: Tue, Nov 25, 2003, 10:28 pm)
*re: Question about 'Resolving Hardware Conflicts' (alex: Tue, Dec 30, 2003, 3:30 pm)
-re: Question about 'Resolving Hardware Conflicts' (Yanger: Wed, Feb 25, 2004, 7:57 am)
-re: Question about 'Resolving Hardware Conflicts' (EraseR: Thu, Mar 24, 2005, 5:00 am)
-Stop: 0000008E (C0000005,...) from dialup or 11b (Joel: Wed, Apr 20, 2005, 3:26 pm)
*Idiot seeks help (Dave Heil: Sat, Dec 3, 2005, 5:53 am)
-re: Stop: 0000008E (C0000005,0xFB6EAF0,0xF3A81060,)0x00000000...) from dialup or 11b (Lennall Harris: Fri, Mar 3, 2006, 10:17 pm)
*Stop: 0x0000008e (0xc0000005, 0xf82c8859, 0x8055e488, 0x00000000) (Carlene: Sun, May 14, 2006, 3:26 pm)
*re: Question about 'Resolving Hardware Conflicts' (sheik: Sat, Apr 15, 2006, 5:37 pm)
*re: Question about 'Resolving Hardware Conflicts' (cReepeR: Sat, Apr 17, 2004, 7:14 am)
-re: Question about 'Resolving Hardware Conflicts' (nm: Wed, Apr 26, 2006, 8:30 pm)
*re: Question about 'Resolving Hardware Conflicts' (Sven: Mon, May 15, 2006, 11:03 am)
*re: Question about 'Resolving Hardware Conflicts' (Heather: Wed, May 24, 2006, 9:09 am)
Return to the Windows XP Discussion Forum


All content at Annoyances.org is Copyright © 1995-2009 Creative Elementtm All rights reserved.
Please do not plagiarize; redistributing these pages without permission is strictly prohibited.