locked
BEX Event Error on Win7 x64 after installing AutoCAD LT 2007 RRS feed

  • Question

  • Receiving a BEX event error when trying to launch AutoCAD LT 2007 on Win7 Pro x64 system. Have already made changes to reflect Windows Compatibility Mode, user is local admin on machine, excluded AutoCAD LT from Microsoft's Data Execution Prevention, disabled AERO theme, Win7 Diagnostic Mode just sits and stalls out.

    Problem signature:
      Problem Event Name: BEX
      Application Name: acadlt.exe
      Application Version: 23.0.54.0
      Application Timestamp: 440adc1d
      Fault Module Name: StackHash_4c0d
      Fault Module Version: 0.0.0.0
      Fault Module Timestamp: 00000000
      Exception Offset: 00e619ec
      Exception Code: c0000005
      Exception Data: 00000008
      OS Version: 6.1.7600.2.0.0.256.48
      Locale ID: 1033
      Additional Information 1: 4c0d
      Additional Information 2: 4c0d4d78887f76d971d5d00f1f20a433
      Additional Information 3: 4c0d
      Additional Information 4: 4c0d4d78887f76d971d5d00f1f20a433

    The installation ran fine and was able to lauch and activate the software when logged in as a Domain Admin. I also was able to pull the setup.log the states: Failed installation aborted, Result=1601

    PC Built: Intel i7 970 Gulftown 3.2 GHz Six-Core Processor, Gigabyte GA-X58A-UD7, 24 GB of RAM, Windows 7 PRO x64 OS 

    Any suggestions, thank you!


    Mark E. Milller Systems Administrator Marshall Excelsior Company
    Tuesday, January 11, 2011 8:04 PM

Answers

  • The Longbow Software Converter worked with suppressing all the hidden security in Windows 7 and now AutoCAD LT 2007 works now on the PC.
    Mark E. Milller Systems Administrator Marshall Excelsior Company
    • Proposed as answer by Andre.Ziegler Thursday, January 20, 2011 8:25 PM
    • Marked as answer by Arthur Xie Tuesday, January 25, 2011 6:13 AM
    Thursday, January 20, 2011 2:57 PM

All replies

  • AutoCAD 2007 is very old and not compatible according to this list:

    http://www.microsoft.com/windows/compatibility/windows-7/en-us/Search.aspx?l=en-us&type=Software&s=AutoCAD%20LT%202007

    Install the XP Mode and run the old AutoCAD version there.


    André


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Tuesday, January 11, 2011 9:28 PM
  • Thanks for replying back Andre. I have already reviewed the compatible listing that Microsoft issued about AutoCAD LT 2007. I have the same software running on 2 other machines that have the same specs with Win 7 x64 and running fine without the XP mode. The one that is giving me the issue is running XP Mode and still will not launch the application.

    Any other work arounds or a converter software like Longbow Converter: http://www.longbowsoftware.com/ claims it can converter 16 bit and 32 bit to install and run on a 64 bit system.

    Mark 


    Mark E. Milller Systems Administrator Marshall Excelsior Company
    Wednesday, January 12, 2011 11:02 AM
  • I'm not an AutoCAD user so I can't tell you about this converter. You can run ProcessMonitor while starting AutoCAD to see if you can get the cause of the crash.

    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Wednesday, January 12, 2011 2:09 PM
  • Temporary disable antivirus and reinstall.

    You may refer the following thread which is from ACAD forum.

    re AutoCAD 2011 - 32 Bit Installation Fails with ... - Autodesk Discussion Groups
    http://forums.autodesk.com/t5/Installation-Licensing/AutoCAD-2011-32-Bit-Installation-Fails-with-install-of-Microsoft/m-p/2805844

    Important Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.

    Installation error 1603 is usually caused by permission issues.

    You receive an "error 1603: A fatal error occurred during installation" error message when you try to install a Windows Installer package
    http://support.microsoft.com/?scid=kb%3Ben-us%3B834484&x=11&y=7#appliesto


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
    Thursday, January 13, 2011 8:34 AM
  • Arthur, have you read the question? The tool is installed but crashes with a BEX issues (NX Bit).

    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Thursday, January 13, 2011 3:59 PM
  • The Longbow Software Converter worked with suppressing all the hidden security in Windows 7 and now AutoCAD LT 2007 works now on the PC.
    Mark E. Milller Systems Administrator Marshall Excelsior Company
    • Proposed as answer by Andre.Ziegler Thursday, January 20, 2011 8:25 PM
    • Marked as answer by Arthur Xie Tuesday, January 25, 2011 6:13 AM
    Thursday, January 20, 2011 2:57 PM
  • what do you mean with hidden security? UAC?

    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Thursday, January 20, 2011 8:25 PM
  • Remember that Win7 is built off from the security hound of Vista core. Many of the visible security that Vista displayed openly was suppressed under the surface for Win7 so you wouldn't get all the security prompts that you got in Vista even when you wanted to move a file from one location to another. Win7 will try to prevent at all cost the prevention of trying to run a 16bit or 32bit system even with WinXP Comp Mode. The Longbow Converter software worked. The AutoCAD LT 2007 is working fine now.
    Mark E. Milller Systems Administrator Marshall Excelsior Company
    Thursday, January 20, 2011 8:56 PM
  • Sorry I don't understand what you want to tell me. That a 16Bit app doesn't work under a 64Bit Windows is a CPU limitation, not a Windows limitation!

    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Thursday, January 20, 2011 9:49 PM
  • Longbow mention it on their website - their tools get all 32bit versions of AutoCAD >= 2008 working on 64bit, and all versions <= 2007 working too. But, it says that although AutoCAD R14 and AutoCAD 2000 are 32bit applications, they wont install on 64bit Windows because the installer program for those 2 are in 16bit and 16bit isn't supported on Windows 7 64, but it is supported on Windows 7 32bit.

    By the way Andre, it's not a CPU limitation, because you can install a 32bit version of Windows 7 on a 64bit machine no problem, and that gives you 16bit support. It's just that Microsoft decided to draw the line in how far back they will support older applications, so they didn't include a 16bit Windows on Windows (WOW) emulation layer, only 32bit WOW.

    Yeah, about the Longbow Converter, basically it totally fixed my company's AutoCAD LT BEX errors it seems by disabling DEP and by also turned down the Windows 7 security settings. I used the Old AutoCAD Reviver tool that comes with the Longbow Converter, this is what I used here... http://www.longbowsoftware.com/Tips_and_Tricks.php#Tip4

     


    Tommy
    Saturday, February 26, 2011 7:22 PM
  •  

    By the way Andre, it's not a CPU limitation, because you can install a 32bit version of Windows 7 on a 64bit machine no problem, and that gives you 16bit support. It's just that Microsoft decided to draw the line in how far back they will support older applications, so they didn't include a 16bit Windows on Windows (WOW) emulation layer, only 32bit WOW.

    IT IS. Running a 32Bit Windows turn the CPU into a different Mode compared to the 64Bit Long Mode which supports NO 16Bit! read the AMD Docs about Long Mdoe again.

    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Saturday, February 26, 2011 9:47 PM
    • Edited by lexingtonsteel Friday, July 12, 2013 11:44 PM forgot to mention the context!
    Friday, July 12, 2013 11:43 PM