Attached logs from fresh FRST scan.
Once this fix has run could you post the fix log that will pop up as I want to see why the aswhid is not moving
CAUTION : This fix is only valid for this specific machine, using it on another may break your computer
Open notepad and copy/paste the text in the quotebox below into it:
R2 aswHwid; C:\Windows\system32\drivers\aswHwid.sys [29208 2014-07-02] () S4 aswSP; No ImagePath S3 aswEmHWID2; \??\C:\Users\THINKP~1\AppData\Local\Temp\aswEmHWID.sys [X] 2014-07-25 12:27 - 2014-07-25 12:27 - 00043152 _____ () C:\Windows\avastSS.scr 2014-07-25 12:23 - 2014-07-25 12:27 - 00307344 _____ () C:\Windows\system32\aswBoot.exe ShellIconOverlayIdentifiers: 00avast -> {472083B0-C522-11CF-8763-00608CC02F24} => No File REBOOT:
Save this as fixlist.txt, in the same location as FRST.exe
Run FRST and press Fix
On completion a log will be generated please post that
Same BSOD, no log.
See edit above, should I have already run aswclear?
Could you run that fix from safe mode please and see if it generates a log then
Yes try aswclear
OK aswclear ran success.
frst in normal mode gave same bsod.
frst log attached from fix (2nd one, shorter) run in safe mode (success).
That has now deleted the aswhid services
So the thought now is do you wish to try one further install
Sure. SUCCESS.
This has taken 5 days to solve overall…
THANK YOU.
So aswHwid.sys - could I have just done net delete aswHwid.sys, or whatever the service name is?
It looks as though there was an emergency update to the aswhid file but for some reason it was not being applied (or was corrupt)
Just deleting the file would have done no good as the service registry key needed to be removed as well. However, as an added embuggerance Avast was protecting that service from deletion in normal mode 
Still all is well that ends well
Yeh, joy of all joys but you knew what you were looking at and I didn’t. So I’m very very grateful.
Sorry to come back to the question about deleting the service, I don’t think I was clear (and since looking it up I definitely wasn’t). I meant in cmd, run the commands:
[net stop “SERVICENAME”]
followed by
[sc delete <service_name>]
Doesn’t that delete the registry key as well? If it had failed I’d have tried safe mode too… If I’d known it was a service to delete/uninstall, and I’d found out its name, I could actually have solved it in about an hour (it was the online installer taking the time on a 100k connection. Reboots etc. are no problem with SSD)…
BTW I did try renaming the file, and replacing with one from a working Avast installation, but that didn’t work. Should probably have guessed service as a next step, but oh well live and learn!
Yes that would do it but to save messing around with the command prompt a batch works just as well
Ya but it’s easier than running FRST with text file custom made by a forum advisor with proviso that it’s only for this one computer, meaning nobody else can use the solution…
Anyone can tell a user to go to safe mode, run cmd and type those 2 commands Earlier in this problem someone had me run sfc /scannow…
Might be a way forward for future posts, help get your job done faster :)
Over and out, I’m done here solution found issue resolved.
The problem is you are the only one so far with this specific problem