I have installed the newer version of houdini 14.1. It is working quite well with the basic stuff like modelling .. etc. But when i try to work on particles and fluids it is getting crashed showing the error message Fatal error : Illegal instruction. The same is with render view and it shows mantra has stooped working . Is there anything that i have to fix in my hardware compnents . I"m using windows 7 64 bit with intel core I3 processor, 8 gb ram and NVIDIA GeForce GT 610 graphics card. I'm new to houdini.

8gb is kind of small for simulation work. If you have enabled OpenCL for acceleration, try your simulation with that option turned off (which is the default). I have found the current OpenCL implementation to be a bit buggy.

The default FLIP simulation is setup to use 5GB of your ram by default. Click the Cache TAB on the AutoDopNetwork and set the Cache Memory to something very low, like 128 or 256mb. This may get you farther down the road before you experience a crash.

Try simpler simulations or get more RAM. The i3 is kind of a low quality processor as well (i.e failed to meet i5 specifications).

Here is a link to a FLIP tutorial that worked on my 8Gb system.
https://www.youtube.com/watch?v=YsS6Gn0m1iI [youtube.com]

I have the same error.

When i try to open a file that has particles, houdini crash.

Someone knows how to fix this problem?


Thanks

I am getting fatal errors: illegal instruction with different numbers (depend on the effect - like 5784, 4680, 1068…)
Fresh houdini install (apprentiece) - PC windows 7, i7 3770, 32GB ram, nvidia GTX980TI. What can i do? I really wanted to learn houdini…

It happens for me every time - i start the app, adding cube, adding effect - like pyro fx flame etc.. And than it crashes.

Don't over clock your system. Return it to the Mghz that the CPU was designed for.

If you insist on overclocking your system make sure it passes the Prime95 test.
https://www.youtube.com/watch?v=5XXOsYSSYh0 [youtube.com]

i have the same problem fatal error : illegal instruction.
i have fix it by update window, maybe it is framework problem
after i update to window SP1 , the problem is fix.