I just got an checksum error while creating a PAR2 recovery file with MultiPar software 1.3.2 #120
-
|
Windows memory diagnostic reports no error, as I am suspecting RAM issues. What could this be? It has happened only once. I should have taken a screenshot. @Yutaka-Sawada I found the log file. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
|
18-Feb-24 2:04:28 PM Base Directory : "..." Input File count : 12 0.0% : Creating recovery slice |
Beta Was this translation helpful? Give feedback.
-
|
Because it would be a hardware problem, I cannot help mostly. Some users reported this error on old PCs. Windows OS's memory diagnostic may not detect Row hammer problem. You may need MemTest86 to check Row hammer. But, Row hammer should not happen on recent PCs normally. I could not solve this problem in software side. You may change PC setting to be stable, such like over-clock or memory access speed. You may use the latest version MultiPar. If you enable GPU acceleration, just disable it. At MultiPar options, decrease CPU usage or disable CPU feature like AVX2. Though it becomes slow, slower calculation may avoid hardware error. |
Beta Was this translation helpful? Give feedback.
Because it would be a hardware problem, I cannot help mostly. Some users reported this error on old PCs. Windows OS's memory diagnostic may not detect Row hammer problem. You may need MemTest86 to check Row hammer. But, Row hammer should not happen on recent PCs normally. I could not solve this problem in software side.
You may change PC setting to be stable, such like over-clock or memory access speed. You may use the latest version MultiPar. If you enable GPU acceleration, just disable it. At MultiPar options, decrease CPU usage or disable CPU feature like AVX2. Though it becomes slow, slower calculation may avoid hardware error.