Avast install nightmare

[drummerman]

Did what you said, clicked 'take ownership' ...

when trying to upload still the same message; You don't have permission ...

This is fun 

regards

[essexboy]

OK I will let you do the analysis

Please download and install whocrashed from here http://www.resplendence.com/downloads
Run Whocrashed and press the analyse button

When it has completed scroll down where it states crash dump analysis and either screenshot or let me know what driver is responsible

[drummerman]

Ok, that worked.

Thanks for your help

regards


--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Fri 15/03/2013 17:43:23 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: aswsnx.sys (aswSnx+0x27803)
Bugcheck code: 0xA (0x10, 0x2, 0x0, 0xFFFFF80003CB7EE9)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\aswsnx.sys
product: avast! Antivirus
company: AVAST Software
description: avast! Virtualization Driver
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: aswsnx.sys (avast! Virtualization Driver, AVAST Software).
Google query: AVAST Software IRQL_NOT_LESS_OR_EQUAL




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

One crash dump has been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

aswsnx.sys (avast! Virtualization Driver, AVAST Software)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

[essexboy]

 aswsnx.sys  is the culprit .. Part of the sandbox I believe

Could you do a custom install on Avast and untick behaviour shield and sandbox
If that then appears to fix the problem then go to control panel > programs and features
Select Avast > change and then tick behaviour shield (a reboot may be required)
Does the problem return ?

[drummerman]

Will do.

Thanks for the fantastic guidance and I'll report back tomorrow

regards

[essexboy]

I have passed this thread to Avast as it may be what they are looking for

[drummerman]

Thanks

[hake]

With Windows XP at least, I have found that it is necessary to thoroughly clean out v7.  Doing an uninstall of v7 is insufficient.  It was necessary to run aswclear.exe in safe mode to banish v7 from the system.  Having done that, v8 runs like a dream.

[drummerman]

aswsnx.sys  is the culprit .. Part of the sandbox I believe

Could you do a custom install on Avast and untick behaviour shield and sandbox
If that then appears to fix the problem then go to control panel > programs and features
Select Avast > change and then tick behaviour shield (a reboot may be required)
Does the problem return ?

I switched both behaviour shield and auto sandbox off in existing installation and rebooted twice. No problems.

Turned behaviour shield on, rebooted twice. No problems.

Switched Auto Sandbox back on, rebooted. Crashed.

Hope this helps and many thanks for your time and help!

I look forward to the next update and leave Sandbox turned off for the time being.

regards

[drummerman]

Crashed again this morning on booting from cold, with the sandbox turned off.

Not sure what causes the conflict but it seems behaviour shield, as pointed out by you Essexboy, may has something to do with it though last night it booted ok with it on  . I've turned that off again and it booted fine just now.  I use Commodo FW in Chiron's configuration by the way.

Not quite sure what to do as protection is impaired with that shield off.

regards


--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sat 16/03/2013 07:56:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031613-25272-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0xA (0x10, 0x2, 0x0, 0xFFFFF80003C71EE9)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 16/03/2013 07:56:59 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x87752)
Bugcheck code: 0xA (0x10, 0x2, 0x0, 0xFFFFF80003C71EE9)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

[essexboy]

And the sandbox module was uninstalled ?

[drummerman]

It was 'un-ticked' under FileSsh.

Behaviour Shield on.

regards

[drummerman]

My Avast is the second clean install of this latest 8.0.1483. I have no other AV's or remnants. Old versions have been deleted both via uninstaller and the Avast tool.

Never had a problem until the 'fixes' to version 8 have been applied.

regards

[essexboy]

So non installation of sandbox cures the problem ?  Do you have any other sandbox type programmes installed ?

[drummerman]

Commodo FW

regards