I've been doing alot of advanced node work, and I've noticed that if you have a HELL of ALOT of nodes, poser just stops rendering the image. I was wondering if 1 has anyone else had thing problem, and 2 does anyone know of a limit?

what nodes are you using? Some nodes require more computation than others, most prominently the raytracing ones. How many is a hell alot anyway? 100? 1000?

well, on V3 each skin material has 36 nodes so ALOT

I've had no problems with 39. Are you using a Mac?

NO, I'm on a PC, reducing the bucket size from 32 to 16 fixes the problem. I'm thinking theres just too much to calculate per bucket... but I don't know

That's almost certainly the case. Which, oddly enough, is why the bucket size is able to be changed...

I think someone posted a while ago suggesting bucket size be lowered even more - like to 2! I tried it and I liked the fact that I was able to cancel a render and have it cancel almost immediately instead of waiting and waiting.

As stated above, imo it has less to do with nodes but everything to do with the "weight" of the scene and how much the renderer has to do in each bucket (a single hi-res head with hair closeup can max you out fast). Generally, if the render stops somewhere and you can X and clear it, it's a bucket size issue and reducing it will eventually get your render. If it locks up during a render and the only way out is the task manager then, it is one of many other problems...usually an overburdon on the memory (mine at least), or the poser/devil who says Hah! You did not save first....