BSOD after standby

Sorry, another BSOD happened..
I am trying to understand what is happening.

The BSOD/minidump file was created just this morning, after it was on tonight, just when I moved the mouse to turn on the monitor (not from standby mode).

I assume you will see this in the file, but I noticed it includes
STOP: 0X000000D1
psched.sys

Screen: http://img405.imageshack.us/img405/7926/img6788g.jpg

Thanks you

psched.sys is QoS Packet Scheduler in the windows network stack.

0xD1 error is generally caused by bad drivers (in same cases it occurs because of hardware).

Anyway, right now I would suggest you to uninstall your zonealarm again, because the actual culprit behind this bsod is vsdatant.sys (true vector device driver). Regards

-I am having internet problems (occasional disconnections) and a DHCP warning in Event Viewer:

Code:

Your computer was not able to renew its address from the network (from the DHCP Server) for the Network Card with network address 001D60AADDF7.  The following error occurred: 
The semaphore timeout period has expired. . Your computer will continue to try and obtain an address on its own from the network address (DHCP) server.

It seems its happening from time to time, but much more often with ZA on.
And having a message 'Closing Network Connection' for about a minute, whenever I restart my computer.
Could these be related to this BSOD error and give an idea how to solve it?

-I have updated drivers installed.
However I just found a virus on my computer (non windows file lsass.exe, and sysdrv32.sys) which I removed, could it had something to do with the error/BSOD?

-I can only think those viruses got to my system when I first connected to the internet with no firewall installed. Though the first thing I did was use windows update.
Are you sure that ZA is the cause for this BSOD? Or could the viruses cause this error?

I am also trying to figure out myself if it all leads to some problem...

I am positive about the id of ZA's True Vector Driver being cause of your last BSOD.

I think sometime earlier i suggested you to switch to Comodo or Online Armor. Both of these are excellent firewalls, infact IMHO they are far superior than ZA as well.

It's weird more problems are starting to appear one after the other (currently DHCP error message resulting in internet problems), as until it started, I used the same programs I use now, and all worked fine.

I wonder how can a firewall program cause a BSOD... it would be reported if there was a problem with it, or is it happening only on my system due to hardware/software installed?

I did try Comodo Firewall but found it too complicated. I guess I will just have to learn how to use it.

Will uninstall ZA and see regarding future problems/BSOD.

Currently I do have some problem with internet connection whether ZA was turned on/off. I have asked on other forums regarding it (including as much detail as possible) but still can't solve the problem.

What do you mean with internet problem (except that DHCP issue)? Also try stopping DHCP service in Services applet and see whether the error stops.

Also badly written softwares/drivers can cause all sorts of issues including BSODs. I agree Comodo needs a bit more steep learning curve; that is why I also proposed Online Armor, both of these firewalls carry roughly same ratings. So perhaps you may give the later one a try as well.

The internet problem... it might be related to issues I mentioned here, but I started this thread regarding a BSOD (which I believe was the faulty GPU) so I don't know if you could help me about it.

Funny it started a few days after I replaced the GPU... that and other issues.

Every hour or so (or every few minutes when ZA was on, like it was making the existing problem worse), the onboard ethernet controller (showing under Network Connections) is acting and there is no internet access, until it solves itself a minute later.
The related messages in event viewer are:

Code:

Your computer was not able to renew its address from the network (from the DHCP Server) for the Network Card with network address 001D60AADDF7.  The following error occurred: 
The semaphore timeout period has expired. . Your computer will continue to try and obtain an address on its own from the network address (DHCP) server.

Your computer has lost the lease to its IP address 172.x.x.x on the Network Card with network address 001D60AADDF7.

This never happened before I opened this thread. Internet worked fine and there were no disconnections. This is not normal behavior. I have tried to find out the cause for this. Have tried changing network card, cable and changing settings. It still happens.
Also under onboard Network Connection Details, 'Lease Expires' is always set to 5 minutes after the 'Lease Obtained'.


Anyway, regarding that BIOS, it just happened again.
Although it happened before I uninstalled ZoneAlarm, I did not have ZoneAlarm on while it happened.
It was very weird... computer was working fine four hours (since my last reply) until just a few minutes ago I turned off the monitor, and 5 minutes later I turned it on and saw the blue screen... Like it happened because I turned off/on the monitor!

I attached the minidump, it also contained info about psched.
Now I have ZA uninstalled, will see what will happen next :/

So many problems... like some faulty hardware is causing all of them or something. Frustrating.

Again 0xD1, with vsdatant.sys as the culprit (part of ZA); either it didn't installed correctly or left some stuff behind I guess.

Secondly, probability is your internet connection required DHCP enabled; however, if you stop DHCP service in services applet, and select its start up mode as manual, instead of auto ;then restart your computer; and try to connect your computer with internet again and see what happens.

Sorry I may be bit slow to respond in next couple of days due to couple of important meetings, which are scheduled to run well into evenings; but I will try to have a look in whenever possible to see whether things improve for you.

ZA is uninstalled so I will see if the psched BSOD is solved.
Do you think it would help the company solve it, if I let the them know about this BSOD and send them minidump?

DHCP Client Service is set to automatic (XP default setting), so I will set it to Manual and see if it will help.
Update: I changed it to Manual and restarted. Then LAC tried to acquire network address forever and there was no internet access, so I changed DHCP Client service back to to automatic. Any idea why this internet disconnection/DHCP errors are happening? Anything else to try? I'm lost as i've tried to change network card/cable/modem.

I don't know if it matters, but should IPSEC Services be set to manual/automatic? I also applied some the following reg fix 'DisableIPSEC.reg' according to ISP instructions:

Code:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RasMan\Parameters]
"ProhibitIpSec"=dword:00000001

Also, 2 other warnings in Event Viewer that might be related to internet disconnection issue, they happen occasionally, but not at the time of the disconnection and DHCP warning/error event viewer messages:

Code:

The server was unable to find a free connection 37 times in the last 60 seconds.  This indicates a spike in network traffic.  If this is happening frequently, you should consider increasing the minimum number of free connections to add headroom.  To do that, modify the MinFreeConnections and MaxFreeConnections for the LanmanServer in the registry.

TCP/IP has reached the security limit imposed on the number of concurrent TCP connect attempts.

In the past I did not have issues with ZA older version, and also did not have such a DHCP/ internet disconnection issue with the same ISP so its weird these problem start now.

I appreciate you helping me, take your time and reply when you have the time.

There is no harm in forwarding such information to ZA, perhaps they will act and fix their broken stuff improving the experience of all of their users. I will get back to you about network related issues asap.

Edit:
I think disabling IPSec service on the contrary may result in connectivity issues. Have they given any reason for asking you to disable this service?

Regarding the registry file, I am not sure what it does (can you know by its content seen above?)
but I know I needed to apply it since I am connected using L2TP and on windows XP.
Before I applied it the dialer gave an error and did not connect. Applying that registry fix from the ISP fixed it.
However I checked and IPSEC Services Service is still set to automatic (I think its the default XP setting), so the reg file might have done something else.

I mentioned, my machine worked fine and there were no DHCP errors and disconnections just until a few weeks ago, and back then I had the same ISP and applied that fix (which seems to be necessary), it just started all of a sudden.

I currently check with the ISP, maybe the DHCP error related to them, and not to something on my machine (and I already tried what I can on my machine).

As for that psched BSOD, so far (and since I uninstalled ZA) there haven't been any of them or any similar problems.

I haven't read through the thread so sorry if mentioned elsewhere.. but do you have your own router? If so, why don't assign your machine a static IP. See if that rids you of DHCP problem

Alright, thats nice; I hope it stays that way.

Regarding DHCP issues, I assumed (may be wrongly) that your ISP wants you to use DHCP to obtain IP, provided you are connecting directly to your ISP with that modem; however, if that is not the case LA's suggestion is very prudent.

ISP <---> Router <----> Local Computers

ISP would only care about DHCP to router. OP should be free to use either DHCP or static between their own router and their computers

I agree, but I was referring to slightly different situation where a user is not using any router, e.g. my pc is directly connecting to ISP via wireless modem, hence the need for DHCP. However, you are very right if he is using router, he can set static ip for his local network.

Ooops. Misread the intent of your post... So, yea, it hinges on whether or not the OP using a router or not

I don't really understand that stuff. I am connected directly to a modem. I don't really know what is DHCP but it seems I need it otherwise I can't connect to the internet.
I am using a dialer and every time I connect I get a different IP (the last octet at least).

Is 'Lease Expires' always set 5 minutes after the 'Lease Obtained' normal? I *think* that is the reason for the occasional disconnections and DHCP warnings. Shouldn't it be at least several hours forward?

I might as well try to assign a static IP if that might help. Where do I start?

No, I wouldn't set it to expire in 5 minutes; you should set it to maximum, and assigning static IP in your case may result in you being unable to connect to your isp at all (as that IP may be assigned to someone else at the moment in time).

Arg. How do I set it?
The information is there. I can't control it.
From what I understand, those disconnections (and DHCP warnings/error) happen because the Lease Expired is always set 5 minutes forward. I might be wrong.

Note I don't get a DHCP warning every 5 minutes, but every few hours.

My advise is to talk with your ISP; because they set out the policy for IP lease time, reason being as far as I can dig info on this issue, you can't set lease time on client end except with some registry hack, which is not advisable. Have you consulted you ISP for help on this particular issue?