Thanks for your answer.
We actually have MCS 2.3.0.3. installed, and on the MiSeq there doesn't seem to be an update available. May I ask which version you're running?
Ever since the previous failed run with memory issues I had decided that we reboot the MiSeq before every run we start, because even at the time I found it suspicious that overclustering alone would cause a system crash. But appearantly, it did not prevent the crash this time.
We actually have MCS 2.3.0.3. installed, and on the MiSeq there doesn't seem to be an update available. May I ask which version you're running?
Ever since the previous failed run with memory issues I had decided that we reboot the MiSeq before every run we start, because even at the time I found it suspicious that overclustering alone would cause a system crash. But appearantly, it did not prevent the crash this time.
Comment