• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. PCB Design
  3. can't restart Capture after exiting

Stats

  • Locked Locked
  • Replies 5
  • Subscribers 165
  • Views 3418
  • Members are here 0
More Content
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

can't restart Capture after exiting

crabbyjacket
crabbyjacket over 14 years ago
I am using Capture CIS 16.5 w/ hotfix 2, with network licensing, under Windows 7x64SP1

I can run Capture once and exit with no problems or indications of a fault, but when I try to restart Capture again after exiting, 98% of the time it crashes almost immediately after displaying the splash screen.  The error message is "This application has quit unexpectedly.  To help Cadence detect and analyze the problem, archive the current project.  To submit the archived project, contact Cadence Customer Support."
Capture is checking with the license manager before the crash, as I get prompted to change licenses if the default is unavailable. The crash happens regardless of license availability.  lmutil diags show no LM issues.  SysInternals Process Explorer doesn't show any lingering Capture executable hanging around.

Rebooting the computer always resolves the problem.  Logging out/in does not solve the problem.  Waiting some length of time (which varies from minutes to overnight) before attempting again has always resulted in a successful restart.

Complete removal and re-installation of the Cadence suite & license manager also has not fixed this behavior.

Suggestions?
  • Cancel
  • crabbyjacket
    crabbyjacket over 14 years ago

    Gory details from Windows:

    Problem signature:
      Problem Event Name:    BEX
      Application Name:    Capture.exe
      Application Version:    1.0.0.1
      Application Timestamp:    4e292443
      Fault Module Name:    StackHash_e98d
      Fault Module Version:    0.0.0.0
      Fault Module Timestamp:    00000000
      Exception Offset:    ffffffff
      Exception Code:    c0000005
      Exception Data:    00000008
      OS Version:    6.1.7601.2.1.0.256.48
      Locale ID:    1033
      Additional Information 1:    e98d
      Additional Information 2:    e98dfca8bcf81bc1740adb135579ad53
      Additional Information 3:    6eab
      Additional Information 4:    6eabdd9e0dc94904be3b39a1c0583635


     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • oldmouldy
    oldmouldy over 14 years ago
    If you get a Capture crash, there will be a Capture<nnnnn>, Capture and "some number", directory in the TEMP location, use %TEMP% at the address bar for Windows Explorer. Find the latest timestamp version of this directory, zip the directory and send the resulting archive to Cadence support, or your Cadence Channel Partner. Whatever this issue is will only be resolved by the involvement of Cadence support.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • PCB George
    PCB George over 14 years ago
    Also, Capture sometimes does not release it’s process if it crashes.  If you open Task Manager (right-click the taskbar and select Task Manager) and look through the Processes list, you may see an instance of Capture.exe still running.  Right-click this line, select “End process tree”, and click “Yes” in the popup.

    ~~
    George
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • steve
    steve over 14 years ago

    I have been having a similar issue and Cadence fianlly managed to resolve my issue. It was related to the graphics card drivers. Make sure your machine is running the latest ones (mine were) but go to the device manager and then rmb the display driver and update the driver software. Not sure if this updates a registry setting but once I'd done this I no longer experienced any issues with Capture. Give it a try.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • crabbyjacket
    crabbyjacket over 14 years ago

     Updating the graphics card driver seems to have solved the problem.

    Coincidentally Cadence suggested this solution to me about a week after you did :-P

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Cadence Guidelines

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information