Blue Screens on Vista SP2 (Greek) and Bitdefender Internet Security 2012

I have a system with Vista SP2 32-bit and Bitdefender Internet Security 2012. I had Windows Live Safety installed, but I saw that one of the Norton features was the capability to specify a total time quota on Internet Usage (say XX hours per week), without having to configure specific allowed Internet schedules.

 

So I uninstalled Windows Live Safety which worked ok (as did the integrated Vista parental controls before that) and installed some days ago the latest Norton Safety minder, configured the accounts and tried to check how it behaves. Upon trying a number of URLs I received the first blue screen I've ever seen on this system, with a reference to TDI. This happened again and again, even on admin accounts that were not configured to be supervised by Norton.

 

Important note: Bitdefender does have parental controls, but they were/are disabled, since I did the supervision via other products (live safety and now norton).

 

To cut a long story short, I had the exact issue as in http://community.norton.com/t5/Norton-Online-Family/have-Windows-Vista-Home-Premium-SP2-and-getting-blue-screen/m-p/194994/highlight/true (for some reason the "reply" button was greyed out, prolly because I am a new member here). Same operating system that is.

 

I did open a ticket with Bitdefender, but I am afraid this is a Norton issue. Can someone have a look at this issue? I have kept the minidumps from the BSODs if that helps...

Hello Katie,

 

my apologies for the late reply. I hoped that I would have to avoid that path: the bitdefender installation/configuration might take some time unfortunately, which is a luxury that I do not have. That is why I preferred to uninstall the Norton Online Family product instead...

 

Would you please consider installing the Bitdefender Internet Security 2012 (trial version would be just fine) on a Vista SP2 system and try to confirm the existence of this issue?

Hi carmik,

 

Thanks for the update.  Sure,  I'll pass the issue to the QA team so they can check into this.

 

 

Thanks,

Katie

Much appreciated! I hope I'll be hearing from you soon, windows live safety is missing a lot of features compared to your implementation...

 

Off-topic: all of the forum notifications end up in my spam folder in Gmail for some reason. Just something else you might check with your web techs...

carmik,

 

Sure.  Our QA will check into this.

 

As for the forum notifications, the software that creates the forum is not a product of Norton, so I can't  check the details on why the emails have been filtered to the spam folder.  But maybe you can add them to the Gmail whitelist.  Please check out the link below for details or you can find lots of information on the topic online.

 

http://howto.cnet.com/8301-11310_39-20126788-285/how-to-add-a-whitelist-to-gmail/

 

 

Thanks,

Katie


KatieQ wrote:

As for the forum notifications, the software that creates the forum is not a product of Norton, so I can't  check the details on why the emails have been filtered to the spam folder. 


I've found one of the reasons: the automated emails are sent with a From: mail header of nortoncommunity@symantec.com. These mails are sent from the SMTP server smtp.lithium.com (208.74.204.5). However the Sender Policy Framework (SPF) of domain symantec.com does not designate smtp.lithium.com as an allowed originating SMTP mail server for the domain, resulting soft fails (and higher probabilities of being marked as spam) by receiving mail servers. See the Received-SPF line below, in the transcript taken from the automated mail sent to my account:

 

 

 

Received: from smtp.lithium.com (smtp.lithium.com. [208.74.204.5])
        by mx.google.com with ESMTP id t9si17459957pbj.252.2012.04.23.12.12.45;
        Mon, 23 Apr 2012 12:12:45 -0700 (PDT)
Received-SPF: softfail (google.com: domain of transitioning nortoncommunity@symantec.com does not designate 208.74.204.5 as permitted sender) client-ip=208.74.204.5;
Authentication-Results: mx.google.com; spf=softfail (google.com: domain of transitioning nortoncommunity@symantec.com does not designate 208.74.204.5 as permitted sender) smtp.mail=nortoncommunity@symantec.com
Received: from app-c3-5.sj.lithium.com (app-c3-5.sj.lithium.com [10.20.110.40])
	by smtp.lithium.com (Postfix) with ESMTP id 521B3F023B
	for <XXXXXXXXXXX@gmail.com>; Mon, 23 Apr 2012 12:12:45 -0700 (PDT)
X-DomainKeys: Sendmail DomainKeys Filter v1.0.2 smtp.lithium.com 521B3F023B
From: Norton Community Mailer <nortoncommunity@symantec.com>

 

Possible solutions:

(a) Have email sent from symantec.com SMTP servers (does not seem possible here)

(b) Add 208.74.204.5 to the symantec.com SPF record (also not very clean)

(c) Create a subdomain say community.symantec.com and have a different SPF for that domain, that shall include 208.74.204.5

I have a system with Vista SP2 32-bit and Bitdefender Internet Security 2012. I had Windows Live Safety installed, but I saw that one of the Norton features was the capability to specify a total time quota on Internet Usage (say XX hours per week), without having to configure specific allowed Internet schedules.

 

So I uninstalled Windows Live Safety which worked ok (as did the integrated Vista parental controls before that) and installed some days ago the latest Norton Safety minder, configured the accounts and tried to check how it behaves. Upon trying a number of URLs I received the first blue screen I've ever seen on this system, with a reference to TDI. This happened again and again, even on admin accounts that were not configured to be supervised by Norton.

 

Important note: Bitdefender does have parental controls, but they were/are disabled, since I did the supervision via other products (live safety and now norton).

 

To cut a long story short, I had the exact issue as in http://community.norton.com/t5/Norton-Online-Family/have-Windows-Vista-Home-Premium-SP2-and-getting-blue-screen/m-p/194994/highlight/true (for some reason the "reply" button was greyed out, prolly because I am a new member here). Same operating system that is.

 

I did open a ticket with Bitdefender, but I am afraid this is a Norton issue. Can someone have a look at this issue? I have kept the minidumps from the BSODs if that helps...