Activity for Bodo Thevissen
-
Bodo Thevissen posted a comment on discussion Technical Topics
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
-
Have you had a look at memory usage when the issue occurs? Maybe you are running low on memory because the RAM disk blocks too much memory, which is needed for other processes? There is no memory shortage. It happens with a lot of GB of free RAM. Have you tried your workflow without using VeraCrypt at the same time? Yes, it really only happens when mounting a Veracrypt volume. Have you tried your workflow without using a RAM disk? not yet, but will very soon.
-
Hi again, To give you slightly more insight: with 4 cores and 8 threads (thanks to multithreading) I am running 6 "lame mp3" conversions at the same time. So the CPU is kept 100% busy with: - conversion of many rather small wavs to mp3 files - Windows defender checking the lame mp3 executable with every start of it (eating about 10-30% of the cpu power) - and then I dare to mount a veracrypt device consuming even more cpu cycles. The only other rather special thing about my setup is that the newly...
-
Hi again, To give you slightly more insight: with 4 cores and 8 threads (thanks to multithreading) I am running 6 "lame mp3" conversions at the same time. So the CPU is kept 100% busy with: - conversion of many rather small wavs to mp3 files - Windows defender checking the lame mp3 executable with every start of it (eating about 10-30% of the cpu power) - and then I dare to mount a veracrypt device consuming even more cpu cycles. The only other rather special thing about my setup is that the newly...
-
Thanks, method 5 is refering to the Windows internal memory test. I did this about 2 weeks ago (when the crashes occured several times) but this memory test didn't show any problems. The crashes only occur when mounting the veracrypt volume and especially when there is stress on the CPU. Close to this time I created this specific truecrypt volume. Perhaps something is wrong with the volume? Will try to rule out all other reasons. Edit: I ran 5 passes of complete memory tests with Memtest64 without...
-
Thanks, method 5 is refering to the Windows internal memory test. I did this about 2 weeks ago (when the crashes occured several times) but this memory test didn't show any problems. The crashes only occur when mounting the veracrypt volume and especially when there is stress on the CPU. Close to this time I created this specific truecrypt volume. Perhaps something is wrong with the volume? Will try to rule out all other reasons.
-
Thanks, method 5 is refering to the Windows internal memory test. I did this about 2 weeks ago (when the crashes occured several times) but this memory test didn't show any problems. btw. the crashes only occur when mounting the veracrypt volume and especially when there is stress on the CPU. Will try to rule out all other reasons.
-
Hi @RealThereal, Will try to do the memtest test. The next time I tried to mount my volume while putting stress on the CPU it crashed so I have a screenshot. Thanks for your help. Cheers, Bodo
-
Hi @RealThereal, Will try to do the memtest test. The next time I tried to mount my volume while putting stress on the CPU it crashed so I have a screenshot:
-
Hi, during about 30% of the times mounting a non-boot disc fully encrypted my machine fires a blue screen (memory issue). This happens with the current version but started about 1-2 weeks before the current version was released. It seems that this does happen more likely when the cores are close to being 100% busy (6 threads of 8 on a 4 core+multithreading). This is my machine: Win10 H2 64 bit (all current updates) i7 6800k 16 GB DDR4 RAM (the RAM has been tested via the Win10 tool and is fine)....
-
Hi Igor, I have read that 7-zip now usually first reserves file space. Doesn't this lead to twice as much drive writing? This may still be a wanted behaviours for normal HDDs but with SSDs this leads to twice as much wear of the SSD. As I assume that there won't be any disadvantages of fragemntation on an SSD I'd like to propose to deactivate this behaviour when writing to SSDs. Thanks for this really impressive piece of software.
-
I have read that 7-zip now usually first reserves file space. Doesn't this lead to twice as much drive writing? This may still be a wanted behaviours for normal HDDs but with SSDs this leads to twice as much wear of the SSD. As I assume that there won't be any disadvantages of fragemntation on an SSD I'd like to propose to deactivate this behaviour when writing to SSDs.
-
thanks for your quick answer and sorry for my unprecise knowledge. Though the core...
-
thanks for your quick answer and sorry for my unprecise knowledge. Though the core...
-
Hi Igor, 7-zip is really a great piece of software and I am using it very regularly....
1