Boot time was not affected by the beta of avast.
I mean, the first one was. There is a slight curve today, but the boot time came to normal after the second boot.
I've uninstalled PeerBlock and testing.
I really don't want to uninstall K9. It's a pain because it does not have an option to export/import settings.
A long time ago, Vlk helped me to identify this following this:
I'd be very grateful if you could give it another test, but before doing so, do some preparations. Namely:
- enable PTE tracking by opening regedit and going to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management
and creating a new REG_DWORD value called "TrackPtes" and setting it to 1. You will have to reboot the computer for the change to become effective (note: on some systems, I have actually seen this setting to cause some stability problems (on its own).... I hope this won't be the case on your computer).
Then, when you install AIS (you can wait for the new build tonight), you will be monitoring the number of allocated PTEs by using the following program:
http://public.avast.com/~vlk/poolmon.exe
This is a program that you will run with the following parameter:
poolmon.exe -iMdl
it will display (in the Diff column) the number of currently allocated MDLs (which is equivalent to the number of PTEs). Normally, this number should be below 1000-2000. In your dump, it was visible that the number was like 350000 before the system crashed (that's a huge number!). I'd be interested in seeing how fast the number grows, and which applications (or actions) make it grow faster (e.g. running eMule etc)... This may help us to track down the issue and fix it.
Thanks much
-Ondrej
I've read that the PTEs method could be the reason itself for crashes, I mean, change the registry key could crash by itself.
I'll test this if necessary. What do you think pk?