Faulting application name: SABnzbd.exe, version: 0.5.6.0, time stamp: 0x4917df95
Faulting module name: PYTHON25.DLL, version: 2.5.4150.1013, time stamp: 0x49820b43
Exception code: 0xc0000005
Fault offset: 0x00082317
Faulting process id: 0xf10
Faulting application start time: 0x01cbb11b3fda0060
Faulting application path: C:\Program Files\SABnzbd\SABnzbd.exe
Faulting module path: C:\Program Files\SABnzbd\PYTHON25.DLL
Report Id: c1f0d380-1d0e-11e0-bb8f-001e4ccc827b
any thoughts on this, it keeps happening and not sure why. i think it started when i made the completed directory a network drive, but not positive on that.
Faulting application name: SABnzbd.exe, python25.dll
Forum rules
Help us help you:
Help us help you:
- Are you using the latest stable version of SABnzbd? Downloads page.
- Tell us what system you run SABnzbd on.
- Adhere to the forum rules.
- Do you experience problems during downloading?
Check your connection in Status and Interface settings window.
Use Test Server in Config > Servers.
We will probably ask you to do a test using only basic settings. - Do you experience problems during repair or unpacking?
Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
-
prophetizer
- Newbie
- Posts: 20
- Joined: May 14th, 2010, 11:18 pm
Re: Faulting application name: SABnzbd.exe, python25.dll
Hard to tell.
Something upsets the Python runtime DLL.
It will probably require some experimenting on your side.
It's not a known issue and there's not starting point for me to start looking for issues.
Having the final folder on a network drive is not an issue,
unless perhaps you have an illegal path or weird access rights issues.
But even then I don't know what could make the DLL crash.
Something upsets the Python runtime DLL.
It will probably require some experimenting on your side.
It's not a known issue and there's not starting point for me to start looking for issues.
Having the final folder on a network drive is not an issue,
unless perhaps you have an illegal path or weird access rights issues.
But even then I don't know what could make the DLL crash.