CPU overheating problem in MB

#1

I’ve an AMD 2500+ 1.8GHz (1280MB RAM, GF5500FX DVI) system at home. Since I mostly work with small to medium sized graphics in Photoshop/Illustrator and my Maya renders are normally rare and small the CPU has suited me very well for a long time.

It normally works around 35C, hits 50C when watching movies or a little higher when rendering in Maya. Apart from the time when my previous cooler broke down, the CPU temperature has never climbed higher than 55C. I also recently cleaned the current cooler and changed the heatsink.

However, when I work in Motion Builder CPU temperature climbs up to 60 degrees in 10-20 minutes with the application being merely opened. If I then don’t minimize it for at least 5 minutes my PC just crashes. Obviously, this is quite annoying and not very helpful in my work.

I haven’t planned to upgrade my system for at least half a year from now since it performs any other tasks pretty much up to my needs. I also want my next upgrade to be a very serious one and I can’t afford a serious upgrade right now.

Anybody knows a way to temporarly fix this problem?

Currently I’m using Motion Builder only for self-study purposes.

Thanks in advance for any help from whoever it might come!

#2

I don’t know if it is documented anywhere, but it seems MB and AMD don’t play together Perfectly. On our team a member with an older AMD CPU’s is not able to work with files that a old Intel PIII can manage. New dual core users need a patch to spped things up.
I would guess that the software is somehow INTEL optimized as it seems to run on various Intel CPUs fine. :shrug:

#3

Thanks for the info. I sure hope this is just a coincidence. :confused:

#4

Hey xsenos,

There are a few things here that I think will help you with this issue - First off, MotionBuilder is more like a video game-engine than other 3D applications (read: Maya, 3dsmax, etc.), in that it’s core is a real-time engine, running full out at all times. This means that just having the application open, it will take up as many CPU cycles and RAM as it can - this is normal behaviour for MotionBuilder. The more CPUs that you have, the more MotionBuilder will utilize. The other unique aspect of MotionBuilder is it’s aggressive memory handling - which it needs to provide its speed and performance.

As of this time, there are no differences between the use of AMD CPUs over Intel based CPUs, in the use of MotionBuilder. Customers should feel free to use either hardware solution.

I hope this sheds some light on the issue you are experiencing.

Cheers,

Curtis Garton

#5

Thanks for the info. For some time I’ve been looking forward to upgrading my RAM by one more gig. If this takes some pressure off of the CPU, I’ll let you know. Last time I upgraded RAM it really did.

#6

This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.