Autodesk 360 Driver Issues

[Adam Young]

Hi all!

I'm Running AutoDesk Infraworks 360 (Up to date).

It keeps crashing my Graphics driver. It crashed on the 311.61 (I think it was this).
Updated yesterday to 347.25! Still crashing.

Do you know of any stable drivers? Or possible fixes?

The GPU is a 3Gb k4000
I have plenty of RAM available and CPU is not the issue!

Thanks for any input,

Adam

 

[Darkbreeze]

What is your windows version? Full system specs would be helpful.

http://www.tomshardware.com/faq/id-2299418/obtain-basic-advanced-system-information.html

 

[Darkbreeze]

I think it's at least possible you have the wrong driver installed, as there are about six different drivers, specific to the K4000 card and depending on what applications you are running, that are available for the card, per operating system version.

 

[Adam Young]

Xenon E5-2680 v3 @2.7Ghz (x2) Yes, Twin Xenon processors.
32Gb 2400Mhz RAM

I know it's not hardware.. Unless the Xenon's are bottlenecking the Quadro?

I downloaded the general Drivers as there were no AutoDesk boosted ones.
Any more info needed? I can get more system specs. But doubt it will have any impact on finding the solution. I am rather savy with computer hardware and software in general.

Thanks for any further ideas 😀

 

[Adam Young]

CPU Usage is between 3% and 85% is the absolute maximum.
GPU usualy sits about 15%-35% and about 90% at the most.
But the VRAM is about 2.3Gb used out of 3Gb. Constantly.

There is a fair amount of Graphics artifacting in my main models. All GPU clocks and settings are stock

 

[Darkbreeze]

Windows, Linux, version?

 

[Adam Young]

Win 7 64bit

 

[Darkbreeze]

This is a possibility:

http://knowledge.autodesk.com/support/infraworks-360/downloads/caas/downloads/content/hotfix-autodesk-infraworks360-20153-and-autodesk-infraworks-20153-closes-unexpectedly-start.html


And I guess I was wrong, there are not 6 different optimized drivers, there are about six hundred, possibly more. As you already know there does not seem to be a driver optimized for infraworks, but there are a slew of drivers optimized for other Autodesk applications:

http://www.nvidia.com/object/quadro-certified-drivers.html#partner_id=11&page=appSelected


What is the model number of your workstation, or is it a custom built machine? Have you checked to see if there are BIOS updates available for the board? Was this card working previously with this application and just begin having problems or did the problems begin with the addition of the card?

With enthusiast cards, which I know are somewhat different from workstation cards but share many similarities, the Nvidia drivers often will not function correctly when updated without full removal of the previous driver package. It might be worthwhile to run the Display driver uninstaller, choose the Nvidia option, reboot and reinstall the generic performance 347.25 drivers over again. The drivers section at the following link outlines the process. The DDU performs removal and registry cleansing routines not found with other driver uninstallers or during simple uninstallation processes.

http://www.tomshardware.com/faq/id-2492424/laymans-simple-guide-solving-graphics-card-issues.html


Lastly, if none of the above works, it may be worthwhile to contact both Nvidia and Autodesk, they may have a recommendation for using a specific driver listed as optimized for another Autodesk application, but that works well with your application.

 

[Adam Young]

I downloaded the HotFix, I'll give it a try on the pc I had issues with.

The workstation is a Fujitsu Celsius (Don't know the series numbers).

Problems have always been present since I've been on this machine. (Had a HP EliteBook 8560w before and it was fine, just not enough power in the hardware to run my big models).

If this fails I shall try your driver suggestions. Got a guy from Fujitsu coming to see me later.

Thanks for your help! I shall keep you posted

 

[Darkbreeze]

I'd also make sure your BIOS and other system drivers, including chipset drivers, are all up to date per the most recent drivers from the product pages of your unit's OEM. Often older or poorly optimized drivers can cause performance or compatibility issues with other drivers, making it seem like the problem is with one thing when it's actually with something entirely different and is simply causing the other item to throw the code.