newsbin.com

Since people aren't jumping up and down in here, this may be a settings thing. Newsbin is crashing for me on a few larger files. No matter what I have tried, I get to about 3/4 downloaded and Newsbin just closes. I updated to 6.82b7 to see if that was it, but the same thing is happening. 98% of files are fine, it is just some files over ~700 MB that take the app down. I am nowhere near CPU, Memory or disk usage maximums.

Where should I be looking to see if this is specific to me or does anyone have any suggestions for what I might try?

Thanks,
Tim

Tell me about your PC. What security software are you using?

hand-built Windows 10 PC, fully up to date. i7 4790, 16 GB RAM, SSD OS drive, 7200 RPM data drive where Newsbin download folders are. 250 Mbps download speeds.

Using Bitdefender with the latest updates.

This is something that has started happening in the last couple of months, and it seems to be happening in a single newsgroup, but only on the large files. Is there a log I should be looking for? I couldn't find anything relevant just poking about in the Newsbin folder.

Thank you!

I have more than one news service. Enabling only one at a time did not stop the crash.

BitDefender has been mistakenly marking Newsbin as having encryption trojan like tendencies. You might need to tell it to ignore newsbin or make Newsbin trusted. For one person it caused database corruption in some of newsbin's databases. It's worth trying anyway.

Quade,

Thanks for the help! This has turned into a false alarm. Either the driver updates I did at the suggestion of the Newsbin wiki did the trick or it was something else. I haven't crashed in a couple of days and I have downloaded all the problem files.

Shrug.

Thanks!

W*

It's still not done, couple of days ago I got the message that NBP manifests itself as ransomware (again) and got blocked, so crash.
Somehow my 'command' telling BitDefender that BNP should be whitelisted went overboard during an update.
.
BD thinks NBP is encrypting, probably has todo with building files from the (partial) headers or something ?
So beware people, although whitelisted, it CAN happen again, so I'm waiting a bit before upgrading to the 2020...