crash - 64bit

[11/28/2009] [13:26:15.203] [03900] [Main_OnVisible] < Leaving routine.
[11/29/2009] [04:00:43.703] [01044] [pbfilter_base] [thread_func] ERROR OPERATION_ABORTED


this happened in the middle of the night. it doesn't seem to be filtering anymore.

i have had an issue when i disable and then re_enable peerblock - i get a hard reboot. once ive posted this and save all my application data il give it a try.



Edited 1 time(s). Last edit at 11/29/2009 11:35AM by pawl.

yes. disable. re_enable. hard crash. no crashdump. no event logs. just straight out to bios.

no minidump either. no bluescreen.

im on win XP64. all service packs and patches applied.

im using the onboard lan on an asus m4a79t.

please let me know if there are any further details i can supply you.

P

PS. this is the only case of instability on the machine.

pawl Wrote:
-------------------------------------------------------

[11/29/2009] [04:00:43.703] [01044] [pbfilter_base] [thread_func] ERROR OPERATION_ABORTED

That looks familiar

> this happened in the middle of the night

Shortly after 0400 actually.
Are you on a LAN?

yes. disable. re_enable. hard crash. no crashdump. no event logs. just straight out to bios.

no minidump either. no bluescreen.

im on win XP64. all service packs and patches applied.

im using the onboard lan on an asus m4a79t.

i have tried all the versions of peerblock with similar effect. the last few days have been with the 223 beta.

please let me know if there are any further details i can supply you.

P

PS. this is the only case of instability on the machine.

yes - im on a lan - cisco 881 in charge.

maybe the dhcp refresh. let me look at those logs. nothing there.

oh - sorry bout the double post.

pawl Wrote:
-------------------------------------------------------

> im on a lan - cisco 881 in charge.
> maybe the dhcp refresh

The daily DHCP refresh in combination with misconfigured DNS settings can cause connections to be lost (which is what I think you and the poster in another thread are seeing).

There are also non-accidental possibilities: network admin policy and scheduling, for example.

Ok,

so we think that the loss of connection is causign x64 machines to reboot.

i guess i can manually renew my lease and see what happens to peerblock when the adress is released. il post the results of my testing tomorrow.

any pointers on DNS configuration to help ease this problem ?

P

Ok,

i did an ipconfig /release - checked the log.
then ipconfig /renew - checked again.

no entries. peerblock seemed quite happy.

I suppose i should add to this that i am using AVG antivirus + firewall and the scheduled daily scan starts at 4am - right when peerguardian logs its last entry.

With the r223 i can exit and restart peerguardian without anythign going wrong.

P

PS. if i disable and then enable after the antivirus has run i still get a hard crash.



Edited 1 time(s). Last edit at 01/12/2010 11:53AM by pawl.

I have done a number of updates to drivers over the last month to try to figure out why this crash occurs. My asus motherboards onboard LAN is a Realtek® 8112 - this part number only existed in the driver package supplied by asus. The part number still doesnt exist on the realtek website.

However - in the last 2 driver releases from realtek and microsoft update this part number is now acknowledged in the INF file.

;8168B
%RTL8168.DeviceDesc% = RTL8168.ndi, PCI\VEN_10EC&DEV_8168&REV_01
%RTL8168.DeviceDesc% = RTL8168.ndi, PCI\VEN_10EC&DEV_8168&SUBSYS_816810EC&REV_01
;8112
%RTL8112.DeviceDesc% = RTL8168.ndi, PCI\VEN_10EC&DEV_8168&SUBSYS_83851043&REV_01

quite why they created a one off part only they know.

the good news is that the behaviour of the driver has improved so that there is now a BSOD to show and not just a blackscreen. Ive attatched a copy of the BSOD screen. i hope this helps.

here is my log file.

most interesting are -

as the AV scheduled run starts
[1/12/2010] [04:00:44.437] [03748] [pbfilter_base] [thread_func] ERROR OPERATION_ABORTED

and when i shut it down cleanly after this AV related issue -
[1/12/2010] [11:22:02.453] [02500] [driver] [close] closing driver - name: [pbfilter]
[1/12/2010] [11:22:02.453] [02500] [driver] [close] Tried to close driver, but it wasn't loaded.
[1/12/2010] [11:22:02.453] [02500] [driver] [close] < Leaving routine (without doing anything).

more strange though is that no minidump was created. no idea why - the config is set to create one.

I recieved a program update for AVG 2 days ago, to program version 9.0.787 and the driver crashing has now stopped. I now have 24 hour + stability.

im using the r227 version of peerblock on windows xp64

P

Thank you for the revelation. So if I understood correctly, antivirus scheduling somehow interfered PeerBlock's process, right?

tippy - yes thats correct. although it is specific to AVG.

my AV is scheduled to run every night at 3am - and peerblock would die every night at 3am.

if i ran a manual scan with the AV then it would kill peerblock within seconds whenever i ran it.

the new version of AVG no longer does this. i am very pleased.