OK, I’ve booted with maxmem=1024, forced the bluescreen and recreated the memory.dmp.
I am currently uploading InstallHang.zip (399,040,911 bytes). Upload should be complete in about 4 hours. If that fails, I’ll upload it from work tomorrow, where I’ve got an insane amount of bandwidth 
Sorry for any inconvenience.
Phil
PhilR, I uninstalled my NOD32 using the Eset uninstall in the menu, and used the advice from Eset to go to Windows and Program files and delete 4 files if I remember right, and then deleted a few entrees from the registry. Then, satisfied that Eset was cleaned out of my computer I installed Avast!5. Avast is running fine. As stated before, simply deactivating Eset doesn’t cut it. I have seen folks in other instances in the past who were unable to install a particular app because they neglected to delete one file in the old app. If I’m wrong you can always reinstall your Eset later as long as you have your key. 
hi every one…am new here,but pls i need your help with my avasst, anytime i dowload the updates…it refuses to update…i am also using the new version 5.0.377…
the firewall on the office server prevents it from updating automatically, so with version 4.8 i was able to download and instal updates but with this new version i cant…please can any1 help me?
this is the error it shows
SI: 0x00000002
ST:0xFFFFFFFE
LE:0x00000000
This time it uploaded successfully ;D
The dump unpacks correctly this time… now let’s hope Vlk will find the problem inside.
Do you use MBAM real-time?
If so, uncheck the option to have it load at start-up.
Then reboot in safe mode, uninstall AVAST 5, reboot in normal mode and then reinstall it.
Does it work that time?
I had the same problem with build 377 and MBAM real-time was the “cause”.
I’m now waiting after a working build before trying AVAST 5 again…
Seems they,re doing the same mistake ESET did when they released NOD32 v3.
Released too early.
No, I just use the free version of MBAM for on-demand scans
Just on time… I’m gonna look at it shortly. Thanks.
I see the problem now. Interesting, but relatively easy to fix.
By the way, the same problem must have already occured with avast v4.8. Have you used avast (4.8) in the past?
Thanks
Vlk
Avast 4.8 always worked on my PC, as did earlier (pre-5.0.314) betas of 5.x which I’d tried. I didn’t test all builds, though…
I’m not going to try to tempt fate by reinstalling 4.8 to check
I’m glad you’ve found it, though.
What are you commenting? The MBAM incompatibility issue?
If so, I used Avast 4.8 without any problem with MBAM.
Sorry if it wasn’t the issue you were commenting.
No, vlk was commenting on the “hang at end of install” problem I was having, not any MBAM incompatibility.
Phil
Thanks, it was not obvious since he didn’t quote anything.
BTW, I never myself had any problem installing 4.8.
I had troubles with 5.0.377 as long as MBAM real-time was active.
I had the same kind of “hangs” you’ve had.
Sorry for off topic Vlk…my mistake
Try upgrade to 396 now. So we can see if they fixed your problem phil.
I’ve just installed AV 5.0.396 (after an uninstall and reboot) without any problems.
Fabulous!
Problem fixed!
Phil
That very a good new. You are very patient and my self i say thank you for help ALWIL by sending your mini dump to them. ;D
Alwil were also very patient. My first full dump upload failed, wasting some of their time. I’m glad I persisted and successfully uploaded a second full memory.dmp file.
Many thanks to Vlk for fixing it so promptly after receiving the dump file.
Phil