Shut down

Nebie has a problem…

I start the interface, If I stop the memory scan the program will load.
If I let the memory scan go to the end, then I get the message that Ashsimpl has cause a problem and now will shut down.

Here are the details of the problem:

ASHSIMPL caused an invalid page fault in
module at 0000:1b10f38d.
Registers:
EAX=02beff88 CS=017f EIP=1b10f38d EFLGS=00010246
EBX=02beff88 SS=0187 ESP=02af0104 EBP=02af0124
ECX=02af01a8 DS=0187 ESI=8197b7c0 FS=635f
EDX=bff76855 ES=0187 EDI=02af01d0 GS=0000
Bytes at CS:EIP:

Stack dump:
bff76849 02af01d0 02beff88 02af01ec 02af01a8 02af02dc bff76855 02beff88 02af01b8 bff87fe9 02af01d0 02beff88 02af01ec 02af01a8 1b10f38d 02af0394

Any thoughts, Thanks

Oops, not good… :frowning:

Unfortunately, the dump you posted is not enough for me to give you any advice. We may try to simulate the problem, but I personally doubt that we will succeed…

Anyway, are you positive that it is connected to the memory scan? Is it always the case that if you skip the scan, everything is OK, and if you let it finish it crashes??

Tell us more about your computer - brand, OS, RAM size, etc… - anything you can think of… Thanks.

And besides these crashes - everything is working as expected? The resident protection is OK?

Sorry for this,
Vlk

Operating system is Win98SE, according to the kernel offsets, but otherwise… no idea what this 1b10… module could be.

westerneagle,

I just did a small research and found out that such a crash may (generally) be connected to the use of (corrupted or something) ODBC. Since avast itself uses ODBC, it may actually be the case (if you have no idea what ODBC is, don’t worry about it - you’re not alone ;)).

Try the following: open the file avast4.ini located in the \data folder, and replace the line

Database=ODBC

to

Database=XML

Then restart the computer and see if it helps. :wink:

Vlk

Yes, every time I let the memory scan go to the end, it would crash. Also, if I stopped the memory scan but then click on “Database” on the Automatic update line, it would crash too. :frowning:

I said “would” because it seems that the XML change in the ini file fixed the problem! :smiley:

Now about that corupted ODBC file??? How does one go about fixing that??? ::slight_smile:

Thanks for you help.

Oh,

Win 98
Compaa 800 mhz athalon
256 K

If your running Win 98/98Se you could try the System File Checker Utility that’s a part of Windows. It’s been a long time since I used Win 98 but if I remember correctly you can get to it by clicking on start/run then type “sfc” (with out the quotes) and then click run. Have your Win 98/98Se CD in the CD ROM. Ths will check all your system files for problems and replace them if needed. Use a little care though as it will ask you if you want to replace newer file versions, say from you doing a Windows Upate, with the original version. Doing this could cause your system to refuse to boot. As a general rule, always say “no” when asked by SFC if you want to replace a newer file with and older one, just replace if SFC says a file is currupted…

HTH,

Trev

Hi…

Sounds like similar problems to what I had…

See my post for “Ashsimpl invalid page faults - fixed” at
http://www.avast.com/forum/index.php?board=2;action=display;threadid=895

Hope it helps!