BSOD using Revit 2009: 0x00000050 win32k.sys

By Eibmoz
Mar 30, 2009
  1. Greetings all...

    Been doing a lot of digging around the web to try and figure out an issue ive been having.

    I have Revit 2009 installed on my home computer: Pentium 4 3.2, 2.5gigs PC3200 ram, NVIDIA Geforce 6200 (512 megs/AGP 8X), Windows XP Home Edition SP3. It's a Dell of which the RAM has been upgraded (2x1gig chips added) and a new video card (previous one was a Radeon 9800). SATA HDD, also, if thats relevant at all.

    I understand the hardware is a bit dated for use but I am only using it to learn and do exercises with it.

    Revit is able to start up but 98% of the time I try and start a new project or open a new one, it crashes w/ a Blue Screen error. It seems to load all the way but right as it is about to actually display the model, I get this:

    STOP 0x00000050 win32k.sys


    0X946A6407 0X00000001 0XBF8019CA 0X00000000

    address BF8019CA base at BF800000 datestamp 49900FC9

    Basically I am trying to discern if this is due to the hardware not being able to handle Revit or if this is actually a problem that can be remedied. I've already put 10 hours into trying to find people with similar issues on the web and I've seen so many different responses and solutions offered of which many I have tried, including:

    - Taking out some of the ram to verify if any of the chips are a problem

    - uninstalling & reinstalling both AutoCAD and Revit (i had noticed someone elsewhere facing similar issues resolved it by just reformatting his hard drive and reinstalling, clearing the issues all together. I'd rather avoid this path unless it was absolutely necessary). Registry values seemed to remain ,however, since the re-installation did not require any authentication.

    - updating my graphic card drivers
    and also updating Revit to Web Update 3

    - installing the "Open Save Close" hotfix (on Autodesk's site, unable to link due to being a new user) which at first seemed to resolve it in that I was able to start a new project and open an existing one. But after a reboot, Revit returned to its original behavior.

    - increasing the min and max page file size to 4095 MB , no effect

    - switching to 3GB mode (also advised from Autodesk's site) which sets the visible available VM to just over 3gigs, which had no effect

    I'd really appreciate if someone could at least point me in the right direction. Appreciate the help very much & hope someone can get me out of this hell.

    Currently am testing the system using Prime95 [no errors so far] and OCCT as advised by another user on another board. I am open to suggestions of other software to run tests with.

    Is this a computer that just can't hack it or my hardware not work well with revit? Or is there just a simple fix I've not managed to discover? Thanks so much in advance.
  2. Eibmoz

    Eibmoz TS Rookie Topic Starter

    Been doing some testing & updated to a newer version of DirectX 9.0c, just by chance if it would change my results. Nothing, basically, except that the error code is now a 0x0000008E win32k.sys error instead of a 50.
  3. Route44

    Route44 TechSpot Ambassador Posts: 11,966   +70

    Requested data was not in memory. An invalid system memory address was referenced. Defective memory (including main memory, L2 RAM cache, video RAM) or incompatible software (including remote control and antivirus software) might cause this Stop message, as may other hardware problems (e.g., incorrect SCSI termination or a flawed PCI card).

    0x8E errors can sometimes be due to drivers but almost always due to hardware issues, particularly RAM.

    win32k,sys is a Windows OS driver and is too general to be of much help.
  4. Eibmoz

    Eibmoz TS Rookie Topic Starter

    hm. I'll run a memtest86 on it tonight just to make sure.

    Ran a bugcheck analysis earlier. Heres the results:

    * *
    * Bugcheck Analysis *
    * *

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000008E, {c0000005, de4f0d79, ee8f3c1c, 0}

    Probably caused by : win32k.sys ( win32k!ThreadLockMenuAlwaysNoModify+8 )

    Followup: MachineOwner

    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: c0000005, The exception code that was not handled
    Arg2: de4f0d79, The address that the exception occurred at
    Arg3: ee8f3c1c, 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".

    de4f0d79 80481502 or byte ptr [eax+15h],2

    TRAP_FRAME: ee8f3c1c -- (.trap 0xffffffffee8f3c1c)
    ErrCode = 00000003
    eax=00c003d3 ebx=de4f126f ecx=e2044890 edx=ee8f3cd8 esi=00c003d3 edi=dd0fb6a8
    eip=de4f0d79 esp=ee8f3c90 ebp=ee8f3c90 iopl=0 nv up ei pl nz na po nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
    de4f0d79 80481502 or byte ptr [eax+15h],2 ds:0023:00c003e8=00
    Resetting default scope




    PROCESS_NAME: Revit.exe

    LAST_CONTROL_TRANSFER: from de4f11e4 to de4f0d79

    ee8f3c90 de4f11e4 00c003d3 ee8f3ca8 ee8f3d04 win32k!ThreadLockMenuAlwaysNoModify+0x8
    ee8f3cb4 de4f12d0 dd0fb6a8 1a011077 00000003 win32k!xxxPaintMenuBar+0x25
    ee8f3ce4 e0b8e99f 0007035c 1a011077 00000003 win32k!NtUserPaintMenuBar+0x68
    ee8f3ce4 7c90e4f4 0007035c 1a011077 00000003 nt!KiFastCallEntry+0xfc
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    0013e17c 00000000 00000000 00000000 00000000 0x7c90e4f4


    de4f0d79 80481502 or byte ptr [eax+15h],2


    SYMBOL_NAME: win32k!ThreadLockMenuAlwaysNoModify+8

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: win32k

    IMAGE_NAME: win32k.sys


    FAILURE_BUCKET_ID: 0x8E_win32k!ThreadLockMenuAlwaysNoModify+8

    BUCKET_ID: 0x8E_win32k!ThreadLockMenuAlwaysNoModify+8

    Followup: MachineOwner
Topic Status:
Not open for further replies.

Similar Topics

Add New Comment

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