Nxt crashing

Replies to This Discussion

Permalink Reply by Roy Hirshkowitz on February 18, 2013 at 9:36am

Haven't seen this before (at least not that I can recall.)  Microsoft appears to a have a hotfix for it.  You'll need to contact them using the link below.  This sort of thing tends to happen when the configuration on a machine is screwy-- perhaps due to viruses or malware.  The render hanging problem, of course, tends to suggest that something else is wrong as well.

http://support.microsoft.com/kb/2643995

• ▶ Reply

Permalink Reply by Peter Hoffmann on March 6, 2013 at 9:29am

At this point I have done the following:

We have reinstalled Autocad both on the machine discussed above and on my own machine (intel 3770k  CPU)

Have reinstalled NXT on both.

Both machines are virtually new and free of viruses.

I have tested files that ran fine under Autocad 2012

Keep getting same problem, either Autocad crashes or whole machine locks up between 30 minutes and 7 hours into renderings.  Have tried batches as well as just letting one rendering run overnight.

So at this juncture it seems that the problem lies with Acad2013 and Accurender combo.

Not sure how to proceed.  Attached is picture of this mornings lockup showing running time of 2 hrs plus before it died.

Attachments:

• crash.JPG, 427 KB

• ▶ Reply

Permalink Reply by Roy Hirshkowitz on March 6, 2013 at 10:32am

There isn't much I can do here unless I get something reproducible.  The problem isn't happening generally, we would be hearing about this a lot if it were.

You are rendering at an exceptionally high resolution.  While this should not cause a crash, 21 MPixels are almost always overkill.  Try seeing if some low-res renderings survive the night to see if the problem lies there.  It would be a start anyway.  Display driver software, heat management, are all remote possibilities.

• ▶ Reply

Permalink Reply by Peter Milner on March 7, 2013 at 4:32am

Most new computers have power management settings which sometimes conflict with the graphics card requirements. In other words, the computer doesn't supply enough power to the graphics card. This happened on my machine as it kept crashing after a certain amount of rendering time.

• ▶ Reply

Permalink Reply by Peter Hoffmann on March 7, 2013 at 8:31am

We are investigating.  is the processing all done on the CPU or is the GPU involved as well?  We are using Quadro 2000D.

• ▶ Reply

Permalink Reply by Roy Hirshkowitz on March 7, 2013 at 8:38am

No GPU processing per se-- but the video card will always be a (small) part of it since it manages the display.  I'm somewhat concerned here since it's happening on multiple (different) systems.  If they have the same GPU then perhaps updating drivers may help.  I would still try a low-res overnight test to see if it makes a difference.

• ▶ Reply

Permalink Reply by Peter Hoffmann on March 8, 2013 at 7:48am

made a simple model file and ran it at low res last night.  same results.  attached are pics of the two monitors as they were when machine froze.  was running task manager and the performance graphs.

Attachments:

• c2.JPG, 444 KB
• c1.JPG, 585 KB
• c3.JPG, 121 KB

• ▶ Reply

Permalink Reply by Roy Hirshkowitz on March 8, 2013 at 8:36am

3000 x 1500 is not low-res (!!)-- run one at 640 x 480, for example, if you want to exclude memory from the problem.  (12,000 faces, BTW, is not a simple model either).

There are usually some heat management settings you can toy with-- setting the processors to run at 97% capacity, for example, usually solves any excess heat minimal performance degredation.  However, I don't really think it's heat-- that normally brings the whole machine down and causes a reboot or shutdown.

Best guess at the moment is the display driver or some hardware management setting as Peter described.  Only a guess, though.

• ▶ Reply

Permalink Reply by Peter Hoffmann on March 29, 2013 at 11:30am

Roy,

 

Ran the small render last night.  Crashed 4:44 in.  Also trying to run next on 2012.  NXT loads fine, but as soon as I try to attach a material it crashes.

Attachments:

• photo nxt.JPG, 487 KB

• ▶ Reply

Permalink Reply by Roy Hirshkowitz on March 29, 2013 at 12:02pm

Bizarre.  Just for grins give me the exact steps you use to produce the error in 2012.  64 bit I assume?  If a drawing is required to reproduce please send it.

Permalink Reply by Ian Foster Griffith on March 6, 2013 at 9:45pm

Have issue with NTX crashing with one of my computers. You are running 64bit system right?

Found my problem was - Relationship between motherboard, cpu and RAM.

When running at 100% some RAM requires a high voltage than the standard bois settings.

I changed my power settings from 1.8v to 2.1v (setting for my MB only) and changed ram chips to lower Mhz, resolving my issues.

But I post this because in my online reseach it is clear that some motherboards don't like some types of ram.

Not just a NXT issue, any high cpu/ram program brings the issue when ram is push to it's limits.

But I would look first at the Microsoft OS problems first look fishy.

• ▶ Reply

Permalink Reply by Ian Foster Griffith on March 6, 2013 at 9:49pm

All so check motherboard chipset drivers for update, that can sometime help...........

• ▶ Reply

• ‹ Previous
• 1
• 2
• Next ›
• Page