![]() I just need to start narrowing down possible causes because right now there are way to many variables. Any idea what I'm missing? Is Houdini using resources in a vastly different way? Anyone else ever had a similar problem? Any help is appreciated. Funnily enough, starting it up, quickly disconnecting and waiting a minute before reconnecting allows Houdini to operate normally. I know it sounds like a hardware issue but no other software has the problem. For some reason, my remote control program (Parsec) started causing Houdini to crash on startup. I've tried uninstalling Houdini, I've tried running different versions of Houdini, doesn't make a difference, still have the crash. I even exported an entire scene from houdini to C4D as alembic and so far it's rendering and working without an issue. I've been successfully using this PC without issue rendering thousands of 4k frames in C4D with redshift, compositing and exporting 8k raw footage from after effects, no problem at all. The thing is, it's only ever happened with Houdini. This happens frequently when GPU rendering with redshift but also happens when doing something simple like scrubbing through the timeline. Holding down the power button doesn't do anything switching off the PSU is the only way to restart. I recently built a new PC (my first build) and while using it for houdini the screens will suddenly go black, the fans go to full speed and the system will go completely unresponsive. I could use some help in finding the cause of a frequent system crash I'm having.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |