SABnzbd Forums

Hello all, I hope I'm not reposting an existing issue - I did have a look around and couldn't see a topic which seemed to fit this issue exactly.

I'm having some problems with SABnzbd or namely the par2 component of it on my Windows server system.

Version: 0.5.4
OS: Windows Server 2008 R2 x64 Enterprise
CPU: AMD Athlon II X2 250
Install-type: Windows Installer
Skin: smpl Black v 1.3
Firewall Software: Windows Firewall (Enabled)
Are you using IPV6? no
Is the issue reproducible? Not exactly

Ever since I installed SABnzbd and began downloading my server intermittently crashes when SABnzbd is performing a PAR operation with par2.exe. I read on these forums that x64 versions of SABnzbd can have problems with the x64 par tools so I replaced them with the x86 ones - no change.

The reason I'm looking to par2.exe as the fault is due to the contents of the MEMORY.DMP crash dump created each time the server dies. It lists:
I was previously using Newsbin Pro x64 with it's inbuilt par mechanism (seems to be driven by par2dll64.dll in it's program files directory) and also QuickPar when needed; but I never had any problems with these utilities in regard to crashing my system.

The only other info I can think that might be helpful is that the par2.exe lives on a different drive to the files it is accessing; the download directory writes to a local RAID-5 array and the SABnzbd install folder is on the system drive. If anyone can shed some light as to what my issue is that would be greatly appreciated, look forward to hearing from you

Matt.

Applications do not blue-screen Server 2008, unless there is a problem
with the hardware or with drivers.
It says "A fatal hardware error has occurred".
Of course, par2 may very well trigger a hardware or software bug,
but it doesn't cause them.

The root cause of this blue screen error is a "Machine Check Exception".

A Machine check exception occurs when the CPU detects a hardware fault (e.g. an internal malfunction in the CPU, faulty RAM, etc.) Very occasionally, a machine check exception can occur due to a faulty driver (which causes a chip or add-on card to malfunction).

As this problem is almost always due to a hardware failure, you should check your computer hardware carefully first. If you are overclocking, return your system to default settings. Run appropriate memory (e.g. memtest86+) and CPU diagnostics (e.g. LinX). If your hardware checks out, then you should make sure that you have the latest stable drivers installed for all components in your system.

I resolved the issue by updating my BIOS in the end - it hasn't crashed since anyways. My guess would be that the reason par2.exe was the trigger was due to my motherboard not supporting the CPU until a new BIOS update...likely stressed the CPU in some way.