BSOD on FILTNT.SYS

[kite]

Hi,

I'm evaluating the trial version of Outpost 2.7 and using it now for almost a week. Last night, while typing an email, suddenly a BSOD occured with some info about the virtual firewall driver (FILTNT.SYS) of Outpost being the cause.

Can anybody hint into a possible explanation for this event? Any know issues with other software?

Thanx for any effort,

Kite

Ps, my system is a Acer Aspire 1400XC notebook with 512 Mb RAM and a 80 Gb harddisk. It's running Windows XP Professional SP2 with all updates installed. The trial version of Outpost Pro is version 2.7.

[kite]

and filtnt.sys has versionnr: 2.7.416.5518

[kite]

and DEP is on in my Windows XP Professional.

i saw on the forum, that opinions are divided on this being a possible cause for the FILTNT.SYS BSOD.

[Shyly]

I'm no expert on this problem but I did find that somebody did a clean uninstall and then disabled about every service he could before he reinstalled Outpost and it seemed to help his BSOD. Might be worth a shot.

Uninstall/Reinstall Instructions

[kite]

Originally Posted by Shyly

I'm no expert on this problem but I did find that somebody did a clean uninstall and then disabled about every service he could before he reinstalled Outpost and it seemed to help his BSOD. Might be worth a shot.

Uninstall/Reinstall Instructions

i think i 'sinned' against everything mentioned in that install instruction, but i'm not sure if that could be the cause. bsod's usually are caused by a program-error.

[kite]

one week further without bsod and without reinstalling the poduct. i did however reactivate netbios for the virtual vmware network drivers. maybe that was the cause of the bsod?

[kite]

2 weeks further now without bsod. in the mean time i bought outpost firewall. it really is starting to look like prohibiting the netbios traffic generated by the virtual vmware drivers caused the bsod.

[Robert2]

As strange as it might sound, I solved this FILTNT.SYS BSOD problem by changing the "View | Font size" in the IE options from smallest to medium.

[Manny Carvalho]

Originally Posted by Robert2

As strange as it might sound, I solved this FILTNT.SYS BSOD problem by changing the "View | Font size" in the IE options from smallest to medium.

Amazing. Where you able to reproduce it?

[Robert2]

It happened each time I tried to retrieve email from my Hotmail account through Hotmail Popper (POP3 connection). I got messages saying "DRIVER_CORRUPTED_MMPOOL" and "FILTNT.SYS" is involved. Also it said "it might be helpful to look at your graphic card settings or driver".
I found the solution when I noticed thatsome of the IE pop-up dialogs were displaying almost unreadable captions. Font size was too small.

[Shark_M]

I am getting this Error with the latest build v 3.0 431

Why is that
it says
PAGE_FAULT_IN_NONPAGED_AREA

FILTNT.SYS
ADDRESS F2193CD2,F217C000,43311870

once the system is rebooted, outpost askes to send feedback, and i allow it, but this problem is recurring again and again

Any help?

[Perkabalo]

I also has this problem with v 3.0.
Outpost repeatedly tries sending error reports at startup, but I always get a could not send error message.

Any suggestions?

[Shark_M]

i dont know, but this version is buggy, i am using version 2.7 (493) for now

[SSK]

Shark M, did you run some memory tests to see if your memory has a problem? A good prog is memtest86+

[Fiano]

One workaround that just may be the ticket is to option the OS to automatically clear the paging file at shutdown. All that's needed is a simple reg edit; one which can easily be undone.

Upfront Caveats
- Works only with NT-kernel systems: XP, Win2000, NT
- Even on those, works only if you have enabled paging (Virtual Memory)
- Shutdown process will take longer (10-20secs ... or more)

The following directions are taken from cited MS K-base article [bracketed addition is mine]:

1. Start Registry Editor (Regedt32.exe [or Regedit.exe]).
2. Change the data value of the ClearPageFileAtShutdown value in the following registry key to a value of 1:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Session Manager\Memory Management

If the value does not exist, add the following value:
Value Name: ClearPageFileAtShutdown
Value Type: REG_DWORD
Value: 1

Source: How to Clear the Windows Paging File at Shutdown

A few things to keep in mind:
- To clear the paging file the first time, you'll need to reboot twice.
- You can end this "auto-clean" cycle by changing the Dword value to 0 (see above).
- The directions for doing/undoing this in XP, Win2000, and NT are identical.