SABnzbd Forums

Hey guys,

First post here, so firstly hello! Also I have done some searching but cannot find anything thats relative to this problem.

The issue I'm having has only started since I installed Sab and only happens when it is running.

Completely randomly and without warning the computer will turn off. I dont mean it shuts down, its as if someone pulled the plug out.

The only thing to note is that I had a job that failed due to not enough parts for repair, I clicked retry and now the computer turns off part way through verification/repair. I cannot remove the job as every time I open Sab the job automatically starts from the beginning.

Sometimes when I start sab after I turn off I get an error to check the log, here is what's in it:
Edit: I set sab to auto start when I run windows, its possible the above has nothing to do with the error I'm having and may just be because the network hasn't connected yet, but I thought I would include it anyway.


This is really serious and means I cant run sab Any ideas?

Thanks,

Dk

I would run memtest86 (google it) to make sure your memory is correct. Reason: SABnzbd loves to use memory, and if your memory is corrupt, it can crash your system.

HTH

I'll give it a shot, thanks.

Well memtest was running for almost 24 hours and showing no errors. Any other ideas?

Max

First, it looks like the Windows networking software is slow to start.
Don't autostart SABnzbd, or otherwise use a delayed scheduled task tied to login.
Look for "Scheduled Tasks" in Windows.
Some systems have problems with the heavy load of par2.
If you have a consistently bad item in the queue,
just remove the item from the "temporary download folder" and restart SABnzbd.

Hi,

Thank you for your reply. I have created the task for sab. I've been running newsleecher on this machine without a problem for more than a year (since I got the machine, it's a fairly good i5, it should be good enough).
Removing the item solves the problem for now, but this isn't a fix, any ideas for solving this?
Thanks,

Max

NL doesn't have an internal webserver, so it's not hindered by a slow network startup.
Some downloads are so corrupt that par2 hangs on it, nothing much we can do about that.

I understand but the shutdown issue continued even after I turned off the auto start.

I'm sorry, replying from my phone and it won't let me edit. I was going to say that even though it hangs, it shouldn't cause my computer power to cut out?!

If a computer shuts of like you describe, it's a hardware, operating system or driver issue.
There is no way a user-level application can cause this.
It may trigger a problem hiding in the system, but it cannot be the root cause.

This is what I feared. Thank you for your help, looks like I'm reinstalling windows!

Hi again,

I have now run memtest for 24 hours, and prime 95 for 24 hours without a single problem. The issue has completely stopped since I cleared that one item from the queue and has never happened before now. The issue only happened when I clicked repair...doesnt that seem a bit coincidental?

It can be that it was the par2-tool that crashed on an especially badly damaged par2 file.
Or possibly SABnzbd crashing on the same.
It's still a puzzle why either situation would crash the system.

I've been working with computers for years and I'm very puzzled. I have tried to re-create the problem using torture tools and cannot, it was the most bizarre situation. I hope it doesn't happen again.

We did get some reports about badly behaving par2 and unrar commands.
Some 64bit systems have trouble running the 64bit versions of unrar and some also the multi-core version of par2.
You can disable two options and try again:
Config->Switches: Enable MultiCore Par2
Config->Special: allow_64bit_tools