Did anyone else experienced this problem in 2.3.20.1 version?
Laptop
aspire 8930g
Nvidia 9700GT
4GB or Ram
Win 7 64bit
Inter Centrino2 Quad Core
After 1 min of rendering default scene at 1280x720 final rendering my computer shuts down.
Out of 5 rendering only one finished.
Ram is at 1.5GB
processors are at 100%
temp is normal.
Any ideas? ???
Does it shut down on other versios too? How about other rendering apps? What kind of temps are you having while rendering?
Are you looking at the temps while rendering? I ask because the temperatures will go up and down rather rapidly between full CPU usage and near idle.
Try setting the minimum/maximum threads to 1/1 on the advanced render tab.
Agreed, especially on a laptop this sounds like a temperature issue. Reducing the number of cores used would reduce overall CPU usage and if it solves the problem then it's almost certainly heat-related.
- Oshyan
Ok, there is definately core number issue.
When i render with 3 cores temp is stable and rendering finishes.
When i swich to 4 cores temp is the same as if i'm running 3 cores but it shuts down after 30 sec.
I attached an screen shot showing temp of cores during 3 core rendering, when the rendering was done i swhiched to 4 cores and started rendering.
Temp remained the same but laptop has shut down after 30 sec.
BTW. Oshyan can i have a link to older version 2.2 i would like to see if the shut down occurs with previous versions.
Thank you.
How about this , right now i'm rendering with 4 cores but at 800x600 and it's not shutting down.
Could it be some memory alocation bug?
800x600 is ok but 1280x720 is not on 4 cores.
Ok i narrowed it down to 900x700 is ok and 900x800 and above shuts down with 4 cores.
Umm have you tried rendering heavier scenes, perhaps low resolution scenes just render fast enough to not have so much strain on the CPU?
Quote from: Derek Tokarzewski on January 03, 2012, 01:59:52 AM
Ok i narrowed it down to 900x700 is ok and 900x800 and above shuts down with 4 cores.
It still sounds like a temperature problem to me. The difference between 900x700 and 900x800 could be due to how much time is spent using all 4 cores. Perhaps at 900x700 it completed enough of the image in less than 30 seconds that the remaining buckets (tiles) were rendered without full utilization of the CPU. This always happens near the end of a render, but maybe 900x800 is the threshold where CPU usage became too high for too long. Of course it's not normal for a shutdown to occur. We should be able to fully load the CPU constantly.
Matt
If you're handy with a screwdriver, can you open the case to look at the fan atop the cpu? Check for excessive dust accumulated around the fan, cpu, heat sink and exhaust channel. If there is heavy dust accumulation it can be blown clear with a can of compressed air. This has worked for me in the past. Other possibilty is that too much voltage is being drawn at times, resulting in computer errors or total shutdown.
When it comes to dust i clean out the dust out of the chasis on the regular basis, actually i just finished the cleaning 2 weeks ago.
When it comes to overheating it is not becuase its steady at 60 celcius.
Also Vue can render for 8 hours on ultra 1280x720 and it's fine, but the second i turn on Terragen even when laptop was off all night 30 seconds of rendering 1280x720 it shuts down. Besides how hot can it get in 30 sec, also temp indicator shows cores at 50 to 60 celcius.
So the question is why would terragen draw so much voltage with 4 cores to the point that the whole system has to shut down to protect itself?
And the answer can't be because it is intensive process because Vue, Max and other programs are just as intensive and they work just fine.
I will try to find a voltage meter program and see what results i get.
Thanks for all the replys.
Derek T.
Can i get a link to older version of terragen 2
I wounder if its somekind of conflict with my system and the program code.
Quote from: Derek Tokarzewski on January 04, 2012, 07:17:27 AM
Can i get a link to older version of terragen 2
I wounder if its somekind of conflict with my system and the program code.
If there were true it should not be affected by resolution of rendering. From everything you've posted so far it seems very much to be a resource usage issue (i.e. pushing your CPU, which does imply temperatures). Terragen 2 does not do anything unusual - indeed it *cannot* - to stress your computer in an "incorrect" way. It is definitely strange that other rendering applications don't cause similar issues, but not necessarily conclusive. I suggest you try a stress test application like Prime95 and see if you get similar problems.
I will private message you a link to 2.2 licensed version.
- Oshyan
Thanks Oshyan.
Ok my problem is solved just finished rendering with 2.2 version with 4 cores at 1280x720.
So, at least for me there is some kind of code conflict in 2.3 between terragen and operating system.
OK i found a solution.
In Final Render
Under Advanced tab
Size of the Subdiv cache in Mb is set to 800
I changed it to 2400 Mb
I'm back in business.
Rendered it out without a glitch.
Thanks eveyone for participation, but like they say if you want it to get it done right you have to do it yourself. ;D
J/K thank you for support.
Derek T.
>:(
I guess i pulled out that victory cigar bit too early.
I placed simple obj. and again it crashed with a complimentary NTFS disk check.
If i keep this up my disk will go to hell.
Did you try Prime95 or a memory scan (Memtest86+ for example)? When it crashes, does it take down your entire computer (i.e. "hard" restart, freeze, or blue screen), or is it just TG2 that crashes? If it's just TG2 then it's possible it's some kind of odd code error (that is only manifesting in your particular configuration, which would indicate some kind of code conflict), but if it's taking down the entire OS it's very likely a hardware problem of some kind, or a deeper driver issue perhaps.
- Oshyan
I thought earlier it could be a ram problem but typically you would get a bluescreen and not a complete shutdown. Same with hard drive problems and other types. Motherboard overheating could trigger a shutdown tho and so would cpu. But yeah.. Odd problem indeed
The shutdown can be described as if plug was pulled from a TV, u just hear a click and it's down, no blue screens or warning just complet powerdown.
This should be enough of messing around, since 2.2 is working for me i'll stick with it untill new version comes out before my hard drives die on me.
Did you try the stress programs Oshyan suggested?
There's no guarantee the new version will fix the problem. It's frankly quite surprising that 2.2 works and 2.3 doesn't. I can't think of any reason that would be the case, given how you describe the problem. If we can't reproduce the problem (and so far we can't, nor even determine what the cause *might* be) then we can't fix any issues there might be to resolve on our end.
- Oshyan
I understand Oshyan, but meanwhile for my needs 2.2 should suffice or i might render in safe zone in 2.3 and upscale to 720p for video purposes. it might be enough for me.
I'll look into those strees programs and let you guys know.
Sounds good. Hopefully we can resolve this.
- Oshyan
PROBLEM SOLVED!!!!!!!!!!!!
Just upgraded memory from 4Gb to 6Gb and it renders out without a problem.
Happy Rendering to everyone. :)
Glad to hear it! Thanks for updating to let us know of the fix, hopefully it will help others. :) By the way, with your upgrade did you just *add* more memory, or did you completely replace your memory with new modules?
- Oshyan
Yeah, hello?? I would like to know the answer as well.
This is just speculation and reminiscing, but in my older days (PDP 11/45 - mid 70's), when we had problems with a certain program that we couldn't pin-point, we found loading programs in different order, hence forcing it to a different memory location (bank), sometimes help isolation. Yes, I did a lot of work with the US Navy and that was a "Navy sentence."
Many times we had to run memory diagnostics that were "relocatable". They would load in high memory and check low memory or the opposite (of course this is a simplified explanation, but I think it makes the point -- loading the diagnostic into the area where the memory problem was, doesn't work very well.) We had three types of memory on those old machines (core, Bipolar, and MOS) all with different timings, and we had to worry about crosstalk, timing, core heating (you could actually burn up a core memory board with a tight loop) and "memory boundaries." Never have figured out why we called those "the good old days", but we did.
Anyway, there are some good modern pc memory diagnostics that will check all your memory, including where your operating system would reside -- I think "Memtest86+" is one, but can't remember.
My advice is to try to isolate the problem without going into you computer. Of course you may have to if the problem is over-heating due to dust, etc. Do the low risk stuff first. Then try to check one thing at a time. We used to have a lot of "re-seating" problems, but if you swap, you are "re-seating" too, so which one was the real problem, the swap or the re-seat?
So, when you ask a question like "Computer Shuts down during rendering", you are going to get the heat, insufficient power, bad memory module, and many other responses that can cause the problem you encountered. Terragen has a large enough user base that you can pretty much figure that a lot of users would be reporting this problem consistently if it was a coding fault. The "stress" answer is the popular answer because heat is a common cause.
In an older machine I had regular shutdowns too, and did memtest, only to find out that one bank was faulty. Replaced it and troubles were over.