NOD32 crashes when trying to scan memory with 1GB+ memory installed

[Click Beetle DX]

Hello, everyone.

I've just upgraded my RAM from 832MB to 1.3GB. Of course, I already had the VCACHE fix patched into the SYSTEM.INI and SYSTEM.CB files, and patched VCACHE.VXD file, so everything in my Win98SE setup is working OK. Everything, that is, except NOD32 anti-virus (v2.7) which crashes with a KRNL386 error when trying to scan memory. Following the crash, just about every other program begins to crash in succession. I have quite a few programs installed on the machine and NOD32 is the only one causing a problem since the additional memory was installed.

Needless to say this is a bit disheartening so I'd like to get to the bottom of it and potentially fix the issue. I wager someone here may have already had the problem (though my search of the forum didn't reveal it), so any help is appreciated.

Thanks in advance.

[dencorso]

Are you using a MaxPhysPage? If so, modify it to exactly 1024 MiB, if not add one... does it make a difference?

Also, there's an unofficial fix for KRNL386.EXE at MDGx's... did you apply it? Does it make any difference?

BTW, I'm not at all sure that this other issue is really unrelated. It might be just another symptom...

[Click Beetle DX]

Are you using a MaxPhysPage? If so, modify it to exactly 1024 MiB, if not add one... does it make a difference?

It's currently set at 40000, which is the value I've seen recommended just about everywhere. Shouldn't that suffice?

Also, there's an unofficial fix for KRNL386.EXE at MDGx's... did you apply it? Does it make any difference?

Yes, I've had that fix applied for quite a while, now. Before I upgraded my RAM to 832MB last year, I made certain to apply all the patches recommended by this community. I knew I would be upgrading the memory again later and didn't want to overlook anything.

[dencorso]

MaxPhysPage=40000 is exactly 1024 MiB, all right.

Still, it might be a problem with KRNL386 or it might be related to vmm.vxd`s flaws...

Please submit your krnl386.exe to VirusTotal, just in case.

If nothing is detected, then try RLoew's RAM Limitation Patch Demo and let's see whether it fixes the problem or not.

[Click Beetle DX]

Please submit your krnl386.exe to VirusTotal, just in case.

It's fine.

If nothing is detected, then try RLoew's RAM Limitation Patch Demo and let's see whether it fixes the problem or not.

I already had the full version of his patch installed... or so I thought. When you mentioned this, I decided to open the patch's installer to make sure everything was OK. To my surprise, the installer reported "incomplete installation detected" (or something to that effect). Strange, as it reported success when I initially installed it. Well, no matter. I had it "complete" the installation and after a reboot, NOD32 seems to be working fine once again.

Great. Thanks for the suggestions.

[dencorso]

Glad your problem's solved!

But, if you're using the RAM Limitation Patch, now that it's fully operational, you can remove (or comment out) the MaxPhysPage=40000, and your system will see and use all the RAM onboard. Try it, please. To comment out a statement in SYSTEM.INI and SYSTEM.CB, just add a semi-colon as the 1st character in the line, before the statement you wish to comment out, and it'll be ignored.

[rloew]

If nothing is detected, then try RLoew's RAM Limitation Patch Demo and let's see whether it fixes the problem or not.

I already had the full version of his patch installed... or so I thought. When you mentioned this, I decided to open the patch's installer to make sure everything was OK. To my surprise, the installer reported "incomplete installation detected" (or something to that effect). Strange, as it reported success when I initially installed it. Well, no matter. I had it "complete" the installation and after a reboot, NOD32 seems to be working fine once again.

Great. Thanks for the suggestions.

My RAM Limitation Patch modifies VCACHE.VXD. If you added Xeno86's VCACHE.VXD, you overwrote my Patches. This is why the Installer complained.

What version of my Patch are you using?

[Click Beetle DX]

if you're using the RAM Limitation Patch, now that it's fully operational, you can remove (or comment out) the MaxPhysPage=40000, and your system will see and use all the RAM onboard.

Done -- and working fine.

What version of my Patch are you using?

7.0

Edited October 13, 2011 by Click Beetle DX