Author Topic: Freezing up 5.1.864  (Read 3695 times)

0 Members and 1 Guest are viewing this topic.

edlion

  • Guest
Freezing up 5.1.864
« on: January 04, 2011, 08:50:11 PM »
After updating avast computer would lock up and stop working when windows started.  Had to go into safe mode to uninstall avast and reinstall.

Second install seamed to be ok for a bit but now im getting freeze ups randomly from time to time.
This is the only thing thats changed on my system recently so likely due to the update.

XP pro 32bit
Intel core i7 930
free Avast 5.1.864
Definition just updated to 110104-1

anyone have any clues?

Offline igor

  • Avast team
  • Serious Graphoman
  • *
  • Posts: 11809
    • AVAST Software
Re: Freezing up 5.1.864
« Reply #1 on: January 04, 2011, 08:54:49 PM »
Would you be able and willing to generate a full memory dump at the moment the system is frozen (as described e.g. here - though the mentioned registry key is for PS/2 keyboards only, for USB keyboard a different one is needed) - and upload it to our FTP server?

edlion

  • Guest
Re: Freezing up 5.1.864
« Reply #2 on: January 04, 2011, 09:10:33 PM »
Would you be able and willing to generate a full memory dump at the moment the system is frozen (as described e.g. here - though the mentioned registry key is for PS/2 keyboards only, for USB keyboard a different one is needed) - and upload it to our FTP server?


Ok then, working on it :P
Forgot to mention if I open winamp (v2) the computer will freeze up there and then most of the time.

Offline DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 86130
  • No support PMs thanks
Re: Freezing up 5.1.864
« Reply #3 on: January 04, 2011, 09:37:32 PM »
<snip>
Forgot to mention if I open winamp (v2) the computer will freeze up there and then most of the time.

WinAmp v2, do you not think it is time to update that, the latest is 5.601. Not all of the version updates related to fixes and upgrades, some of them included security updates.
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 21.11.2500 (build 21.11.6809.528) UI 1.0.683/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security

edlion

  • Guest
Re: Freezing up 5.1.864
« Reply #4 on: January 04, 2011, 10:46:14 PM »
I have reasons for using the old version of winamp.

But lets not forget winamp is not the only trigger to the problem.

more testing, winamp doesn’t make the system freeze up if i turn the file system shield off.

Tenko: Winamp may not be the only trigger to the issue, however excluding the winamp folder in the file system shield didn’t solve the problem.


Offline DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 86130
  • No support PMs thanks
Re: Freezing up 5.1.864
« Reply #5 on: January 04, 2011, 11:08:24 PM »
I'm sure you do.
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 21.11.2500 (build 21.11.6809.528) UI 1.0.683/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security

edlion

  • Guest
Re: Freezing up 5.1.864
« Reply #6 on: January 04, 2011, 11:56:40 PM »
Would you be able and willing to generate a full memory dump at the moment the system is frozen (as described e.g. here - though the mentioned registry key is for PS/2 keyboards only, for USB keyboard a different one is needed) - and upload it to our FTP server?


After much fuss I was still unable to generate a "COMPLETE memory dump" as this option was not available even logged in as admin (safe mode).

Offline igor

  • Avast team
  • Serious Graphoman
  • *
  • Posts: 11809
    • AVAST Software
Re: Freezing up 5.1.864
« Reply #7 on: January 05, 2011, 12:02:30 AM »
Microsoft decided to hide that option on new OSes if the machine has more than 2GB RAM - for some reasons.
(note that the dump will be as big as the installed memory)

Here's some more info on that: http://support.microsoft.com/kb/254649/en-us
Basically, the complete dump can be enabled by putting the value 1 into CrashDumpEnabled in the registry key
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\CrashControl

However, there are some conditions (the page file must be at least as big as the size of RAM (or slightly bigger), and I believe it has to be on the system volume.