warvair / peerblock

Automatically exported from code.google.com/p/peerblock
Other
0 stars 1 forks source link

pbfilter.sys will not load #61

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
I have no idea how to reproduce the problem. All I did was exit PeerBlock
via right click on the tray icon. Win7 RC1 immediately blue screened. First
and only time I've seen Win7 get a bsod. I didn't record the error msg.
Uninstalled/reinstalled PB several times and pbfilter.sys simply will not load.

What is the expected output? What do you see instead?
PB runs fine, but the .sys file won't load according to the log file.

What version of the product are you using? On what operating system?
Win7 RC1 x64

Please provide any additional information below.
pbfilter.sys signed with dseo

Original issue reported on code.google.com by syntax...@gmail.com on 16 Aug 2009 at 5:46

Attachments:

GoogleCodeExporter commented 9 years ago
Forgot to add PB version. It's v0.9.2.r86

Original comment by syntax...@gmail.com on 16 Aug 2009 at 5:47

GoogleCodeExporter commented 9 years ago
Try restarting your computer and check if pbfilter.sys loads.

This might be due to some unclean shutdown code. Also, does this occurs with the
standard pbfilter.sys (not signed with dseo)?

Original comment by nightstalkerz on 16 Aug 2009 at 11:08

GoogleCodeExporter commented 9 years ago
Rebooting changes nothing. If I use an unsigned pbfilter.sys, I get an error 
window
as shown in the attachment.

I should also point out that while trying to get PB working again, I even 
resorted to
trying PeerGuardian 2.0 RC1 Test 2, with the exact same results.

I was using PG2 RC1 Test 2 successfully before I found PeerBlock, and it ran 
just fine.

I can only assume PeerBlock broke something in Win7 when it caused the bsod.

Original comment by syntax...@gmail.com on 16 Aug 2009 at 5:08

Attachments:

GoogleCodeExporter commented 9 years ago
Update. I've just discovered something very odd. I'm using 6 lists from 
IBlocklist,
level 1-3, edu, ads, and spyware. These are the Bluetack lists at the top of the
list. Plus a custom blocklist with 9 IP ranges.

With my custom list and those 6 blocklists loaded, PB reports 16953346 IPs 
blocked.
When I remove my custom list, it reports 0 IPs blocked. So I opened all 6 lists 
and
they show as empty.

I have deleted and re-downloaded those lists over and over with the same 
results.

Original comment by syntax...@gmail.com on 16 Aug 2009 at 5:27

GoogleCodeExporter commented 9 years ago
Ah, about the "the .sys file won't load according to the log file", are you 
talking
about the following two lines:

[2128] [driver] [load(3)]    driver not currently installed as service
[2128] [driver] [load(3)]    Driver-service NOT running!

If so, be aware that's actually a bad message, I need to clean that up to be 
less
alarming.  I've actually never NOT seen that message, even/especially when
PeerBlock's running just fine.  Try running the command "ping 3.0.0.0" from a
command-prompt: if it returns "General Failure" and you see the IP-address show 
up as
Blocked in PB's UI then PeerBlock's working fine, if it returns "Timeout" and 
you do
NOT see the IP show up as Blocked then PeerBlock is NOT working correctly.

Can't reproduce the other problem...  Setting up my config to have 6 active 
lists
(Level 1-3, Edu, Ads, and Spy; all from iBlocklist) I get 13+ billion IPs 
blocked. 
Can you upload your config, and a screenshot showing this problem?

Regarding the BSOD, don't suppose you got a system dump from that by any 
chance, did you?

Original comment by peerbloc...@gmail.com on 17 Aug 2009 at 12:51

GoogleCodeExporter commented 9 years ago
Yes, that 'bad message' is what shows in the log.

Tried ping 3.0.0.0 half a dozen times and each time it times out and nothing 
shows in
the PB window.

dump file, conf file and screenshots are in attached .zip file.

Original comment by syntax...@gmail.com on 17 Aug 2009 at 4:43

Attachments:

GoogleCodeExporter commented 9 years ago
Just to clarify, by "bad message" I meant the message is actually misleading, 
as it
doesn't necessarily indicate a problem.  I'll try tonight to repro the problem 
using
your config-file.  Could you also pass along your custom list, just for sake of
completeness?

The dump is a good one to get as not only does it appear to be another instance 
of a
different crash for which we got a dump, but it also includes some pbfilter.sys
routines in the stack (which the other dump did not) - this should hopefully 
help us
identify where in pbfilter.sys we were when we faulted.  Will hopefully be able 
to
make more progress on that one when I have a few hours to sit down and look at 
the
dump in more detail.

Original comment by peerbloc...@gmail.com on 17 Aug 2009 at 1:49

GoogleCodeExporter commented 9 years ago
Here's the text of my custom blocklist. Attached is the actual file I use, 
which was
made in PG2.

Description                 IP Range

moviex.info tracker                 89.248.162.134 
Fastserve Network Inc (MPAA)            66.172.0.0 - 66.172.63.255
Comcast Cable Comm. Holdings Inc (MPAA)     66.176.0.0 - 66.177.255.255
Cyberverse Online (MPAA)            66.180.192.0 - 66.180.207.255
Unknown Owner (MPAA)                85.139.184.134
PacificNet (MPAA)               209.204.0.0 - 209.204.63.255
Xeex (MPAA)                 216.151.128.0 - 216.151.159.255
Illegal 0.x.x.x Addresses           0.0.0.1 - 0.255.255.255
p2p.arenabg.com tracker             85.17.111.51

Original comment by syntax...@gmail.com on 17 Aug 2009 at 3:41

Attachments:

GoogleCodeExporter commented 9 years ago
I know this isn't the place for PG2 issues, but I've found something odd. Been
working in XP Pro SP3 tonight (dual boot with Win7), where I have PG2 beta 
installed
and it works fine. I switched it over from the original PG2 lists to the same 
lists
from iblocklist that I was using with PeerBlock, plus my custom list, and when 
the
PG2 window updated after downloading the new lists, it showed 16953346 IPs 
blocked.

When I remove the iblocklist lists, and switch back to the PG2 default lists 
minus
the .gov list, it shows 1000587928 IPs blocked as of 4:31am Eastern time 
(GMT-5),
August 21.

I'm not much of a programmer, but it seems to me like a bug in the PG2 code 
that's
been carried over into PeerBlock.

Original comment by syntax...@gmail.com on 21 Aug 2009 at 8:35

GoogleCodeExporter commented 9 years ago
New portable test release r132 fixed my issues. Ping 3.0.0.0 works as described 
now.
Thank you.

Original comment by syntax...@gmail.com on 7 Sep 2009 at 3:09

GoogleCodeExporter commented 9 years ago
Hmm, I guess this might have been fixed along with some other change we 
implemented.
 Alternatively this might have been due to having PeerBlock transfer over settings
from PG2 or something - I know that we have a few issues with that, still - 
such that
a clean install from the "Portable Edition" .zip files doesn't do whatever it 
was
that caused your problem.  I'll change this to Fixed for now, we can re-open it 
if
the problem reoccurs.  (We'll get notification if you update a "closed" bug, 
don't
worry.)

Sorry for the earlier difficulties, but I'm glad it's working now!  Not sure 
what we
did, but I'll take it as a win.  =;)

Original comment by peerbloc...@gmail.com on 8 Sep 2009 at 12:50