theveritas
asked on
Windows98 and Memory Leaks
I recently upgraded to Win98 2nd edition. After doing so, I started to see a severe memory leak problem. Usually after heavy hard drive access. I use a system with a VIA chipset and 256 MB Ram. The memory will slowly leak down to 0....
Help!
UPDATE...Thank you for the Memturbo suggestion. However, I neglected to say that I did a clean install of just the OS and Free Mem Pro.. Same problem.. Even in Safe mode I get the leak..I think it has to do with the VIA Chipset, But their is no help from them.....Any other help would be appreciated
Help!
UPDATE...Thank you for the Memturbo suggestion. However, I neglected to say that I did a clean install of just the OS and Free Mem Pro.. Same problem.. Even in Safe mode I get the leak..I think it has to do with the VIA Chipset, But their is no help from them.....Any other help would be appreciated
ASKER
Edited text of question.
Theveritas, you are correct, the VIA chipset does create a large portion of the problem. Any program that calls the Win32 EnumObjects() API function may drop a memory sector during each call and eventually stop working, with the following error message:
<Program name> caused a General Protection Fault in module GDI.EXE.
The EnumObjects() function leaks a selector each time it is called. If enough calls are made during a particular session, the local descriptor table (LDT) can
become exhausted. The computer must then be rebooted to recover the correct memory core and restart the kernel.
Back in April Microsoft reported that the manufacturer was cooperating with them in developing a supported fix that would correct this problem and would be available from Microsoft. As of the 7/1/99 release of the MS Technet, the release is still in development and hos not even entered
full regression testing.
Dennis
<Program name> caused a General Protection Fault in module GDI.EXE.
The EnumObjects() function leaks a selector each time it is called. If enough calls are made during a particular session, the local descriptor table (LDT) can
become exhausted. The computer must then be rebooted to recover the correct memory core and restart the kernel.
Back in April Microsoft reported that the manufacturer was cooperating with them in developing a supported fix that would correct this problem and would be available from Microsoft. As of the 7/1/99 release of the MS Technet, the release is still in development and hos not even entered
full regression testing.
Dennis
I had the same problem on my system after I upgraded to SE, using a Mustang R534F MB (SiS chipset). I found that by manually setting my virtual memory settings in the Performance Section of the System Properties, the problem went away. I set mine to min 64meg, max 200meg. I have 64 meg RAM in my system, and this seems to work fine, with no real performance hit.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Ups! I accidentally checked answer instead of comment, sorry!
Sounds like you are having a problem with some software that you are running. Not a windows fix but a good program to take care of memory problems is mem turbo you can download it from this site.
http://www.memturbo.com/
get the free demo it recovers ram from programs that don't give it back to the operating system. It then does a defrag and there you go your ram will never hit zero again.
CShenberger