Another things is that I tried rendering a simple scene with test render settings in 3dsmax and suddenly I'm warned about the cpu temp going 95 deg. Are you having the same problem with temp issues.
I have pretty much the same rig and I am having this exact problem. I have a P8Z68 - V Pro, 8gigs GSKILL 1600, i7 2600K. I went into BIOS EZ settings and set my machine to "ASUS Optimal" and every time I do a simple 3ds max render I get a temp warning. If I set my system back to the normal setting then CPU temp is fine, it doesn't go above 60 degrees C even for heavy renders. Can someone explain this behavior?
This sounds to me like the 3D Max render engine is not tasking properly all cores in a new(er) multi-threaded environment. Some types of render engines keep a single thread task across BOTH cores in a earlier dual core system alignment (as in the last time they reworked the threading model of the software, and a bit of a poor coding man's hack i'll say). In a Quad core arrangement, this really stresses/utilizes only 2 of the 4 cores. This is a well known issue with older builds of 3D rendering software. Instead of being pipelined for ALL individual cores, it mearly passes along a SINGLE thread on up to TWO cores each if 2 or more are detected/reported.
To get around this, I've had to resort to using multi-pass rendering as way to get overheating under control. I use Lightwave 3D 9.5 now (it's now properly multi-threaded) but my older LW3D v.8.0 had this issue, but only on certain renders of volumetric lighting w/ or w/o animated/displaced textures that were not "baked" in the lighting passes yet, (kept a 100% load on only 2 cores, while the other 2 cores were idle). I found if I did the lighting passes separately, the issue went away (I don't know about 3D'S Max threading though). Kind of a bum deal to make separate passes for pre-vis, but really I prefer it into final renders where I need more lighting control for exact photoreal scene matching.
I suggest you expieriment with your various render settings and find the tool most responsible for the 100% load, then do that function as a separate pass if you can, to keep the loading in check. At some point an update will then "render" the issue moot and no longer be plagued by the "hack-style" CPU loading.