Outpost 2.7 & BSOD

Hi All,

Sorry if this has been raised before.

I've been trialing out Outpost 2.7, and I was so far pretty impressed with it. Except for one major problem, BSOD. At least 3 times since install it, my system has locked up and died with a BSOD due to the firewall.

I've been forced to uninstall it. Anyone else had this problem? or have the slightest idea what causes it.

Thanks in advance,

Sync.

 

which antivirus do u use?

 

I found that
disabling XP's DEP
and Outposts - Plugin - DNS - Remove
Did the trick for me.

THe antiVirus used can also cause problems - I use F-secure Anti-Virus this has known problems but can work just fine.

 

I use NOD32,

I may try it again, disabling the DNS module and DEP.

 

i never had a bsod with DEP enabled and the dns plugin enabled. yet again every system is different and outpost is known for BSODs.

 

Did you have any other firewall software prior to installing Outpost? One thing I notice, it everytime I uninstall one and install the other software, there's still some file left over from the other firewall, like the driver file.......


Stick to one product and you be ok. Also Outpost could not the the reason why there is a Bluee Screen, could be a bad video driver........

I am a fan of Outpost and try so many like Tiny Firewall 2005, Norton, Zone Alarm......... and NONE will compare to what Outpost offer...

 

While I pretty much agree with what you are saying this kills the concept of trialing, which is recommended by many here to see what works best for them on their system. I prefer to do research and decide, while the concept of trialing is good it has it's draw backs.

 

Yes, BSODS have been reported by significant numbers of users and discussed eg here:

https://www.wilderssecurity.com/showthread.php?t=75148

Search Wilders for > outpost BSOD <


Try the same at Outpost forum

http://www.outpostfirewall.com/forum/


When it's clearly fixed I will give Outpost a try again.

 

What I have found indispensable here is to do a fresh reformat and reinstall of Windows, and then when you have everything installed except your firewall, do an image of your HD. I started doing this a month or two ago, and it's the best thing I've ever done. I can trial any firewall or software, and when I'm done, just restore my system from the image in 10 minutes, as if nothing ever changed or happened. It's truly great. Makes it easy to try various firewalls without wondering if something was left behind by the uninstall of one or another of them.

I use Drive Snapshot, as recommended some time back by P2k. Works very well. Here's a link: http://www.drivesnapshot.de/en/

 

same here except i use acronis true image. imaging ur hard drive is also handy for troubleshooting (if the probem is software specific) just install one at a time and image until u find the culprit.

 

Yep, it's great.. I only wish I had started doing this a year or so ago..

 

DEP issues with Outpost should have been fixed with version 2.5 so if you have a problem that is definitely DEP-related (i.e. following the steps in Windows XP SP2 and Outpost to disable DEP solves it and re-enabling DEP causes it to resurface) then please report this to Agnitum.

Conflicts with other firewalls or network-level software (e.g. port monitors, packet sniffers, VPN software or network diagnostic tools) are a more likely cause of BSODs with the current version (2.7) of Outpost. If applicable, try disabling such programs. Other firewalls need to be uninstalled - ZoneAlarm has been noted to require extra steps however, see Extended Zone Alarm Uninstall/Outpost Install Instructions.

 

Ah yes. I think that would work nicely. Good reply. I will check them out sometime soon.

 

Ok, well I've given it a second shot although I can't disable WEP. I've disabled the DNS Link and removed protowall (just in case).
I'll post back if it fails again.

Thanks for all the tips and advice.

Cheers,

Sync.

 

u mean DEP right? cuz WEP is for wireless networks. neways heres a thread on disabling DEP, however instead of changing the value to "/Execute" it should be "/NoExecute=AlwaysOff"). also have u tried just adding outpost.exe to teh DEP exclusion list?

 

This thread has most bases covered

DNS - DEP
http://outpostfirewall.com/forum/showthread.php?t=14419&page=2&pp=15



or

F-secure
http://outpostfirewall.com/forum/showthread.php?t=13074&highlight=starfish_001
http://outpostfirewall.com/forum/showthread.php?t=13185

 

Hi,

Yes DEP, not WEP as I said previously. I was replying to a post on wireless security on my local ISP forum and I'd got my wires crossed.

Well disabling the DNS plugin, and removing protowall seems to have done the trick, no BSOD so far. I'll have to try adding back protowall and see if it stays stable.

Thanks for all the help so far.

 

if its not stable with protowall, as an alternative also consider peerguardian or the blockpost plugin for outpost.