RAM Leaking
This is a discussion about RAM Leaking in the Windows Hardware category; Hi there, I have 512MB Samsung PC2100 DDR RAM (CAS2. 5) and after W2K startup I end up with around 438 MB free. That's all nice and dandy, but last night I noticed that after installing some dodgy ASPI drivers and Fireburner 2.
Hi there,
I have 512MB Samsung PC2100 DDR RAM (CAS2.5) and after W2K startup I end up with around 438 MB free. That's all nice and dandy, but last night I noticed that after installing some dodgy ASPI drivers and Fireburner 2.1 (i think latest version), I ended up with 218 MB free. After rebooting, I fired up my DSL connection, started an FTP client, and I had again around 220 MB free...something is eating up my resources, and I can't figure out what.
Any bright ideas, anyone?
I have 512MB Samsung PC2100 DDR RAM (CAS2.5) and after W2K startup I end up with around 438 MB free. That's all nice and dandy, but last night I noticed that after installing some dodgy ASPI drivers and Fireburner 2.1 (i think latest version), I ended up with 218 MB free. After rebooting, I fired up my DSL connection, started an FTP client, and I had again around 220 MB free...something is eating up my resources, and I can't figure out what.
Any bright ideas, anyone?
Participate in our website and join the conversation
This subject has been archived. New comments and votes cannot be submitted.
Responses to this topic
Bring up the task manager and you can sort your processes by memory usage. That should help to clear things up as to what is hogging up all the memory.
OP
Yea, duhh, that was the first thing i did...there is no app or service reporting the missing RAM.
OP
Thanks man but it doesn't do it anymore...I guess it was caused by the new version of Fireburner, that generates an error upon exit (sum runtime error bug). So everybuddy out there be careful with it!
At least I'm inclined to think this...however I cannot explain why it did the same thing even after I rebooted and did not run the program.
Hmm...
At least I'm inclined to think this...however I cannot explain why it did the same thing even after I rebooted and did not run the program.
Hmm...
