This may explain it…
Printing and Display are very closely coupled.
Adobe Acrobat has an atrocious track record with respect to being “fault tolerant” of problems with display drivers.
If your drivers are perfect, the the Acrobat authoring tools seem to work fine.
If your display drivers are a little glitchy (and most are), then Acrobat will crash or cause other problems.
CutePDF, PDF995, BullZip, and other PDF authoring tools seem to be far more fault tolerant than Acrobat.
It’s also possible, your Rhino file has problems that are gumming up the translation.
What happens if you run SelBadObjects?