Bodo Thevissen

the problem vanished. I have no clue where it came from and where it went.

started the tests: [x] 10 mounts of the volume [x] 5 mounts with cpu stress via prime 85 [x] 5 mounts of stress on the RAM disk via crystal disk mark [x] 5 mounts with 2 lame threads writing on the RAM disk [x] 5 mounts with 4 lame threads writing on the RAM disk (cores still not 100% busy) [x] 5 mounts with 6 lame threads writing on the RAM disk All tests have been without any problem. The only "viarable" I didn't test yet was a java based tool that usually ran when the crashes occured. I updated...

started the tests: [x] 10 mounts of the volume [x] 5 mounts with cpu stress via prime 85 [x] 5 mounts of stress on the RAM disk via crystal disk mark [x] 5 mounts with 2 lame threads writing on the RAM disk [x] 5 mounts with 4 lame threads writing on the RAM disk (cores still not 100% busy) [ ] 5 mounts with 6 lame threads writing on the RAM disk

started the tests: [x] 10 mounts of the volume [x] 5 mounts with cpu stress via prime 85 [x] 5 mounts of stress on the RAM disk via crystal disk mark [x] 5 mounts with 2 lame threads writing on the RAM disk [x] 5 mounts with 4 lame threads writing on the RAM disk

started the tests: [x] 10 mounts of the volume [x] 5 mounts with cpu stress via prime 85 [x] 5 mounts of stress on the RAM disk via crystal disk mark [x] 5 mounts with 2 lame threads writing on the RAM disk [ ] 5 mounts with 4 lame threads writing on the RAM disk

started the tests: [x] 10 mounts of the volume [x] 5 mounts with cpu stress via prime 85 [x] 5 mounts of stress on the RAM disk via crystal disk mark [x] 5 mounts with 2 lame threads writing on the RAM disk

started the tests: [x] 10 mounts of the volume [x] 5 mounts with cpu stress via prime 85 [ ] 10 mounts of stress on the RAM disk

started the tests: [x] 10 mounts of the volume [ ] 10 mounts with cpu stress via prime 85 [ ] 10 mounts of stress on the RAM disk