there are two factors to consider. when increasing velocities, you
usually need to decrease the time step to be able to accurately
integrate the equations of motion. besides that, the specific error
can also be made less likely by increasing the communication cutoff.
depending on your system and setup, you may need to use a combination
of both factors to have a stable and reasonably accurate simulation.
In addition to Axel's answer, I'll forward Steve's general comment:
"As the error section of the manual explains, this is usually
due to bad dynamics, e.g. blowing atoms out of the box,
so that a bond cannot find its partner atom. Fix your simulation
and these kinds of problems go away."
http://lammps.sandia.gov/threads/msg20249.html
http://lammps.sandia.gov/threads/msg22394.html
http://lammps.sandia.gov/doc/Section_errors.html
For other people who run into this problem and are searching the
mailing list archives, these kinds of errors often occur early in a
simulation (due to overlapping atoms, singular dihedral angles,
etc.... For people having this problem, try visualizing the initial
configuration of your system. See:
http://lammps.sandia.gov/threads/msg47488.html)
However that was not happening in your case. But it makes sense
that these kinds of errors crop up under harsher conditions (high
strain, high temperature, high pressure, rapid driving forces,
etc...). Axel's suggestions are the first thing to try.
I haven't tried this but using a pair_style which supports RESPA
might help. If you have freedom to play with the force-field, then
switching from Lennard-Jones (1/r^12) to a pair_style with softer
repulsive forces can also help. You can also try use weaker harmonic
bonds, angles, etc.
Andrew
Although I don't think it will help, it can be fun to try visualizing
the trajectories of your simulation, saving often around the point
where the error occurs, and see if you can see where the explosion
occurred. (I suspect two atoms got too close together at some point.)
P.S. more pontification (suggestions for using minimization and fix nve):
http://lammps.sandia.gov/threads/msg33303.html