Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: Yamaki on September 04, 2005, 05:23:14 PM
-
Alright, I just installed Avast Home on my desktop, since I heard it was so great. It's also installed on the laptop I'm using right now, and working smoothly. When I first installed it on my desktop, I rebooted because there was a virus in memory. Now windows boots to my BootSkins screen and then just goes black. I don't know what's happening. I'm using windows 2000 Professional on my desktop. Is it a possibility that BootSkins is messing it up?
I can't get into safemode because a stupid virus has messed it up.
Also, I currently have Norton Antivirus 2004 and Avast home installed.
Anything that can fix this?
Thanks!
-Yamaki
-
One of the problems is that Avast and Norton are not working together.
Choose which one you want to keep and remove the other.
Things like bootskin often messes with Windows system files and can cause all kind of problems.
-
Having two resident scanners is a recipe for conflict and may well causing this problem. However I haven't used either w2k or bootskins.
How/what has a virus messed up to stop you getting into safe mode?
-
I'm not sure what virus it is, but whenever I try to go into safemode I get an IRQ_NOT_LESS_OR_EQUAL stop screen, so...yeah.
Would there be any way to bypass my problems or uninstall through cmd or something?
Thanks for all of your help so far!
-Yamaki
-
Okay, I got into command prompt, but it won't let me access my program files directory! It says access denied even if I try cd PROGRA~1.
Help! D:
-Yamaki
-
Yamaki, problem is not on BootScreens but, God, why did you install NAV and avast at the same time in your computer??? :(
You can't uninstall avast! by command line (dos mode). You'll need to get access to the Registry, NTFS read/write for DOS program,, etc.
But, strange, safe mode give you a BSOD (IRQ_NOT_LESS_OR_EQUAL stop screen)...
Can you go to C:\WINNT\CONFIG.NT file and list the contents?
Can you edit this file (or at least, copy to a floppy, edit it and put them back there?
If so, try to see at the bottom, after the comments the 'active' lines such these ones:
dos=high, umb
device=%SystemRoot%\system32\himem.sys
files=40
device=x:\short_path_to_avast4\aswmonds.sys
If you add a REM before the line:
REM device=x:\short_path_to_avast4\aswmonds.sys
Boot, will it solve the incompatibility?
-
WINNT/CONFIG.NT... Hmm...
I don't have that file! O_O
EDIT: Even so, for some reason I can't copy the file onto a floppy (access denied) OR edit it in the RC. Gah!
-Yamaki
-
I'm not sure what virus it is, but whenever I try to go into safemode I get an IRQ_NOT_LESS_OR_EQUAL stop screen, so...yeah.
No this is more associated with a bad driver or hardware issue. I had this only a couple of days ago, I will ignore it unless it becomes habit forming.
If this is happening every time you boot, it may be hardware, have you installed any new hardware or drivers recently?
-
I'm not sure what virus it is, but whenever I try to go into safemode I get an IRQ_NOT_LESS_OR_EQUAL stop screen, so...yeah.
No this is more associated with a bad driver or hardware issue. I had this only a couple of days ago, I will ignore it unless it becomes habit forming.
If this is happening every time you boot, it may be hardware, have you installed any new hardware or drivers recently?
Nope. Nothing new.
-Yamaki
-
These Stop error screens like the one you got also have a code and this one is usually 0x0000000A, a google search for this returns lots of hits, but it is extremely difficult to resolve/track them as even the information on the MS site is very hard to understand.
So finding the exact fault is very difficult hence why I tend to ignore them as one off blips.
When I got the same error I had nothing new either, so the only other thing brought out in the MS info is a driver either righting or reading from a memory address that isn't there. The trouble is there is nothing to help identify which driver or what to do even if you do find it.
Sorry I'm out of ideas.
-
WINNT/CONFIG.NT... Hmm... I don't have that file! O_O
Sorry, my fault:
C:\Windows\System32\Config.nt in Windows XP
C:\Winnt\System32\Config.nt in Windows 2k (I suppose)
-
WINNT/CONFIG.NT... Hmm... I don't have that file! O_O
Sorry, my fault:
C:\Windows\System32\Config.nt in Windows XP
C:\Winnt\System32\Config.nt in Windows 2k (I suppose)
Nope. Nothing. x.x;;
Still not resolved!
-Yamaki
-
I'm not sure what virus it is, but whenever I try to go into safemode I get an IRQ_NOT_LESS_OR_EQUAL stop screen, so...yeah.
Would there be any way to bypass my problems or uninstall through cmd or something?
Thanks for all of your help so far!
Hi this is what exactly the above means it might help you with your problem.
A kernal-mode process or driver attempted to access a memory location without authorization. This STOP error is typically caused by faulty or incompatible hardware or software. The name of the offending device driver often appears in the STOP error and can provide an important clue to solving the problem.
If the error message points to a specific device or category of devices, try removing or replacing devices in that category.
If this STOP error appears during Setup, suspect an incompatible driver, system service, virus scanner, or backup program.
Hope this helps you.
-
I'm not sure what virus it is, but whenever I try to go into safemode I get an IRQ_NOT_LESS_OR_EQUAL stop screen, so...yeah.
Would there be any way to bypass my problems or uninstall through cmd or something?
Thanks for all of your help so far!
Hi this is what exactly the above means it might help you with your problem.
A kernal-mode process or driver attempted to access a memory location without authorization. This STOP error is typically caused by faulty or incompatible hardware or software. The name of the offending device driver often appears in the STOP error and can provide an important clue to solving the problem.
If the error message points to a specific device or category of devices, try removing or replacing devices in that category.
If this STOP error appears during Setup, suspect an incompatible driver, system service, virus scanner, or backup program.
Hope this helps you.
Oi. Unfortunately, it doesn't list the cause of the STOP error in the error itself.
Problem still unresolved.
-Yamaki
-
Bumpage x.x.
*Still not resolved*
-Yamaki
-
Well, it won't be easy (if possible) to solve your problem.
You installed two antivirus at the same time into Windows 2k. Obviously, it will crash.
You need to get acess through DOS to registry files (BART CD from Alwil provides it, or boot into DOS and use NTFS for DOS application, then a registry editor for DOS).
Do you have any Registry backup (with ERUNT tool, for instance)?
Do you have an image of your system?
If not... maybe you'll have to consider reformat :'(
-
Hi is it xp or 2000 you are having trouble with also any other error message would help, we are trying to help you but need time and more info.
-
Right I tried my friend Google and found something along the same lines, someone who installed AVG when they already had McAfee and got the DRIVER_IRQL_NOT_LESS_OR_EQUAL error. There is a lot on that forum thread, I haven't read it all I will leave that up to you to see if there is a solution there.
http://www.wilderssecurity.com/showthread.php?t=13042
Let us know if this is the way to go.
-
I've recently been getting the IRQL_NOT_LESS_OR_EQUAL Stop: 0x0000000A message myself. Maybe within the last month or so. What's even stranger is that I've seen it on 3 different computers here at home. Two desktops and 1 laptop. None of them have any additional virus programs or firewalls. All three are WinXP SP2 with latest updates and patches.
The laptop showed the message about 30 minutes after I had updated from version 4.6.623 to version 4.6.691. It's a friend's laptop, and I'm pretty sure they would have told me if they saw BSODs while using 623. The other two desktops have version 4.6.691, and it seems they started showing the STOP 0x0000000A message around the time they were updated to 691.
Ever since I've uninstalled Avast from one desktop, and downgraded to version 623 on the other, the BSODs have subsided.
When I started getting the errors on the first desktop I thought maybe something was failing like memory. Then I found it odd it was happening on another desktop around the same time. Now I get a laptop I'm working on which isn't mine and all I do is update from 623 to 691 and I get the same exact 0x0000000A message, now I know it ain't no hardware failing. Anyone know what's going on here? I see these errors have been haunting some since the version 4.5 days.
-
STOP 0x0000000A or IRQL_NOT_LESS_OR_EQUAL
A kernel-mode process or driver attempted to access a memory location without authorization. This STOP error is typically caused by faulty or incompatible hardware or software. The name of the offending device driver often appears in the STOP error and can provide an important clue to solving the problem.
If the error message points to a specific device or category of devices, try removing or replacing devices in that category. If this STOP error appears during Setup, suspect an incompatible driver, system service, virus scanner, or backup program.
You can find more information if you go to to help and support and type the above number in.
-
Can i suggest if anyone is getting crashes that they set their windows to generate minidump files for Avast to analyse. :) Those that have them already should send them to VLK along with a brief explanation .
-
Can i suggest if anyone is getting crashes that they set their windows to generate minidump files for Avast to analyse. :) Those that have them already should send them to VLK along with a brief explanation .
If so, please, go to folder \windows\minidump and send the newest (recent) .mdmp files for analysis.
Better if you can compress (zip) them and add some information about the BSOD and the link for this thread. ;)
Send an email to any of these addresses:
vlk (at) avast.com
rypacek (at) asw.cz
Or upload to the any of these anonymous ftp servers:
ftp://ftp.asw.cz/incoming
ftp://www2.asw.cz/incoming
Eddy's links for minidump issues:
http://www.jsiinc.com/SUBJ/tip4900/rh4981.htm
http://www.microsoft.com/whdc/devtools/debugging/default.mspx