CRC errors in jdownloader 2
August 6th, 2016
It could be that your hard disk is broken.
using different disk and same problem, checksums work fine if I d/l using firefox so problem must be in jdownloader
Go to the settings, applications, click the jdownloader application, in options tab, change the content filtering to disabled for that app.
There are two things that come to mind.
The easiest to try is the program you are using to decompress the files – try Bandizip (it includes the newest winrar format). Sometimes when you try to open new version winrar file with a program that hasn’t been updated for it, it will say you have a CRC error (but not all of the time).
For the downloader part, try to download a file with only one segment rather than multiples. If it is good then you know it is how the JD is splitting the download into segments and then putting them back together. For this, I would first try to lower the number of segments – it could be (but doubtful) that your HD isn’t keeping up with the multiple writes. Then I would try to set the temp folder JD uses to a different drive if that is an option for you.
Having same problem with single and multi part files and also on different drives.
Go to the settings, applications, click the jdownloader application, in options tab, change the content filtering to disabled for that app.
I am not sure what program you are referring to. I have removed security essentials and disabled malware bytes, still getting same errors.
Please don't double-post, use the edit button instead. Members are allowed to double or triple post only if their previous post has exceeded the maximum characters limit.
Kindly visit our rules:
www..org/rules
Single part files – that isn’t what I was speaking of when I mentioned segments.
JD or other downloaders download a single file in ‘chunks’ or segments. So one file is downloaded say in 5 chunks and then is assembled to create the one file.
If something is wrong with how the chunks are put back together, then your one file is corrupt. So change the number of segments to 1 rather than whatever JD is using right now – probably 5.
This way one file = one chunk and there is no reassembly. If the file is still corrupted, it is the file and not the downloader.
trying that now, thanks
what says , is to set “max connections per file” to 1 , and jdownloader have a different algroithm that deals with segments at the start of the download not at the end , like IDM. if files are not corrupt after failed crc check , there should be no problem , and u can disable crc checks through , advanced options . just untick “sfv/crc check when possible” . i wrote these according to jdownloader 1 , not jd2 beta , so menus could be different
edit : also someone mentioned above about it could be a harddrive problem , it can be true also because crc checks in jd pushes harddrive at the edge , the bigger file size the longer time for checking. u told u tried at different drives, did u try at different partitions of same harddrive like C D E etc.. or actually totally different physical harddrive ? to get the real answer i suggest you to do second
I changed actual physical drive.
I changed actual physical drive.
then there shouldnt be any hardware problem, the important thing is , can you extract the file after it gives crc check error ? if u can , u shouldnt be worry about it , i never used jd2 beta but at jd1 there were only a few popular hosts uses crc checks , uploaded and filefactory as i remember. if there is no problem and u dont wanna see the error , u can disable crc check as i mentioned above post. also it is better to disable auto extract on jdownloader through extensions which is called jd unrar. i cant think anything else , maybe it is just a plugin problem will be fixed later , or it may be related to the java version u installed , try to update it to latest. if files doesnt get corrupt , let it give crc errors , it doesnt matter
Try a fresh install of it. With recent updates a few people have had issues with crc. For some a re-install worked, for others they tried different hosts and had better luck. Keep trying what you can to narrow it down. If you don’t have ECC ram it is also a possibility of RAM going bad. Not likely but covering all your bases will help.