SABnzbd Forums

I'm using SABnzbd-0.6.9-win32 on a Windows 7 system. I use SickBeard 489. My usenet server is SuperNews. I have Comcastic Business Class internet. I have a direct wired connection. Core i3-530 with 4GB RAM, separate OS drive.
Lately, every night, I get several "failed to unpack CRC errors". I never used to get these! It seems to happen most when I have a group of recordings in the queue. If I go to SickBeard and change the failed download from "snatched" to "wanted", SABnzbs will download the EXACT SAME file and process it properly! (same nzb, same post)

Any ideas please? Should I try to pause SAB between downloads?

Like I said above, this is happening every night...

PS, If I go to another computer and use NewsBin Pro, I can get the same download with no problems. So I figure it's got to have something to do with the "back to back" requests in the queue...

What happens if you just hit "Retry" in the History entry of the failed job?

shypike wrote:What happens if you just hit "Retry" in the History entry of the failed job?

I didn't see that there was a "retry" button in SAB. But it works when I requested the video again from SickBeard.

BTW, I checked the "Pause downloading during post-processing" box under "switches" and all went well last night! Crossing my fingers.

Thank you for the reply.

It may indicate memory issues.

I hope not.
G.SKILL Ripjaws Series 4GB (2 x 2GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800) Desktop Memory Model (F3-12800CL9D-4GBRL - Retail Item #: N82E16820231277)

I've never had a problem when I used to run Windows Media Center (and did multiple TV recordings). Guess I'll have to run memtest...

BTW, I found the retry/repair ... didn't work. But adding the (same) nzb again did work!

thewarm wrote: BTW, I found the retry/repair ... didn't work. But adding the (same) nzb again did work!

That would mean the files on disk are corrupted and not that par2 has trouble doing its work.
Cannot think of a reason why this would happen.
By default post processing and downloading is simultaneous.
It's this first time anyone complains about this specific scenario.

Ran memtest+, one bad memory module!
Also, the new HD I just got from Newegg sounds like a "Popcorn Popper"... it's going back.
bummer.

At least I have a pair of memory sticks I can steal from another system...

BTW, the repair option did work last night (just before a BSOD because of the bad memory!) I hope everything will get back to normal with new memory.

Thanks for all of the help!!!