If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Re: Windows 7 BSOD

i've had the BSOD 7f on a brand new laptop running Zone Alarm Extreme Security since shortly after i got the laptop in Dec 09. sometimes it could happen several times a day, sometimes only 1 or 2 times a week. as per the error, i thought the memory was bad or mismatched but all tests show it's fine.

i reinstalled the OS (Win 7 Ultimate 64 bit) just to eliminate that variable. then i installed the current ZoneAlarm beta but the 7f BSOD still persisted. i HAVE contaced ZA tech support directly about this issue via the online beta form AND via FTP through ZA's diagnostic tool. Tech support has not gotten back to me in a week.

at first there wasn't much on the net about BSOD 0x0000007f online and i assumed something was wrong with my brand new laptop and scheduled it to go in for repair. in the time it took for all that to happen, more stuff cropped up on the net about the error and i found this article that explained people running Norton and Zone Alarm were having the same 0x7f issue i had.

The Fix:

the link above (which ultimately points to Norton's fix which then points to this microsoft page) suggested disabling NetBios on DHCP server (TCP/IPv4) as follows :

For Windows 7

Click Start, and then click Control Panel.

Under Network and Internet, click View network status and tasks.

Click Change adapter settings.

Right-click Local Area Connection, and then click Properties.

In the This connection uses the following items list, double-click Internet Protocol Version 4 (TCP/IPv4), click Advanced, and then click the WINS tab.

Click Disable NetBIOS over TCP/IP, and then click OK three times.

it's been 1 week since i disabled TCP/IPv4 and i haven't had a single 0x7f BSOD since (knock on wood.) so thus far, it would seem the articles i linked above are correct and ZoneAlarm Extreme Security does cause the BSOD 0x7f error.

anyone know the potential drawbacks or risks of disabling TCP/IPv4?? the drawback of leaving it enabled is more 7f errors, but i'd like to know what i disabled and why that matters. though obviously, the best solution would be for ZA to resolve this issue so TCP/IPv4 can be re-enabled.

~~ snip ~~

i mistakenly almost brought in a new laptop in for repair because of all this and hope this info helps someone else avoid the same mistake.

Re: Windows 7 BSOD

Originally Posted by pakled

i've had the BSOD 7f on a brand new laptop running Zone Alarm Extreme Security since shortly after i got the laptop in Dec 09. sometimes it could happen several times a day, sometimes only 1 or 2 times a week. as per the error, i thought the memory was bad or mismatched but all tests show it's fine.

I've had the exact same issue; six BSOD 7f in 10 days on new, clean installed Dell laptop with two clear memory/hardware diagnostic tests.

Thank you SO MUCH for sharing your problem and a detailed fix!

Going to give it a try or uninstall ZA and see how I fare. I really didn't fancy thrashing it out with Dell seeing they have trouble just delivering their products, but there's only so much you can do.

Re: Windows 7 BSOD

Please Contact ZA Tech Support If you have a Valid ZA License Key with Details of your Hardware, Software, Version of windows and what you were doing when the BSOD occured, and any Idea on how to Re-create the BSOD..

Re: Windows 7 BSOD

Originally Posted by farmerbeans

Going to give it a try or uninstall ZA and see how I fare.

I'm afraid the IPv4 NetBIOS disable work-around didn't work for me... had a BSOD 0x7F last night. Still not sure whether ZA is to blame, so I've replaced it with ** another Firewall to find out for sure... maybe ** the antivirus is the culprit

Still, it might work for some, and the more info the more options others will have. Here's hoping it's just a program causing this issue.

Last edited by fax; March 3rd, 2010 at 03:35 PM.
Reason: Reference to commercial products - Against forum rules