Actions
Forum Thread Details
  • State Verified Answer
  • Locked Locked
  • Replies 13 replies
  • Subscribers 90 subscribers
  • Views 1611 views
  • Users 0 members are here
Related
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

CS Crashes on Library Access

larry_137

I cannot get CS to work. If I access a library, it crashes. If I view a 3D image of my circuit card, it crashes. If I try to do a 3D edit a footprint, it crashes. If I run a rules check and try to save the PCB file, it crashes. I just paid my "subscription" fee, but the program is useless.

 

Note that I completely designed a PCB (it is now in production) using the same libraries and CS worked flawlessly (well, good enough). At one point several months later, I went to check something in the design files, and the 3D view no longer worked and the Libraries window showed only a line outline with a clear center section. OK? When I tried to exit CS, all I could do was press the kill switch in Task Manager to get out. Task Manager said that DXP.exe was "unresponsive". No kidding.

 

The PCB was designed under Win7 (and as I said all worked fine) and this lock up happened under the same Win7 (who knows what Microsoft updates do). OK. I tried reloading the program. Crash. Because Win7 expired, I had to update to Win10. Before doing so, I uninstalled CS using Wise Program Uninstall. This kills everything in the program including Registry Keys. I then installed the new operating system (wasn't THAT fun!). With Window 10 on board, most everything seemed OK with minor exceptions. I then loaded CS using all of the defaults, just as the installer wants.  Started CS, and navigated the license activation routine. Great! Good to go. Started CS, and the home page came up. Blank Project Directory on the left, home page in the middle, and thin Library to the right. I checked that the two default integrated libraries were installed. Yes. On the task bar I pressed View and then Libraries. Crash! Could only kill CS using Task Manager. None of my files (which I checked by downloading a 3D viewer and they all looked good) were in use. As an experiment, I loaded CS on my laptop (also Win 10) and did the same sequence. The two integrated libraries came right up, and the footprints showed 3D views on all of the parts.

 

I have tried asking the forum with no results. Anybody have an idea of a way forward?

  • 0 in reply to spegs21

    Issue returned on 1909. I'm going to try DDU for a clean driver install.

  • 0

    Thank you everyone for your help. We circled the correct answer in thinking it was a video card driver issue. Normally, if the Direct X level is higher than the card can support, it is supposed to revert to the level that the card can handle. Apparently in this case, the Direct X 12 API either did not revert to the Direct X 11 level of my driver, or there was an error. To compound the problem, I went to Nvidia (the card is a Quadro K2200) and downloaded the latest driver listed and I still had the problem. Turns out the latest driver listed is NOT the latest driver. I (probably by accident) searched for the "latest K2200 driver" and ended up on a download page I had never seen before at Nvidia. It listed ALL versions of the drivers and and what they improved. Turns out the one I got first was WAY behind. In fact, there was a driver released only on Feb 24 of this year. One of the features: "added Direct X 12 support". After loading and restarting my computer, my PCB rendered and all of my parts had their 3D views. Again, thanks for the help. I got enough hints to know what to look for. Hopefully, this will help someone in the future.

  • 0

    One other bit of information. Right click the start icon (Win10), left click run and type "dxdiag" then enter. The Direct X diagnostic tool will come up. On the System tab it will tell you the Direct X version installed on your machine. Then go to the Display tab. Upper right is Direct3D DDI: xx. The xx on this line should match the version on the System page. If it does not, either lower your Direct X version to match the Direct3D DDI, or find a new driver that supports the Direct X version on the System page. In my case, what I thought was the latest driver was not. A new release had come out only a couple of days earlier, and that release said "...added Direct X 12 support>"