Wiruz
01-27-2001, 09:13 AM
It has been almost a year since my last reinstalling of windows, and even though i've nursed it, i think it's beginning to show signs of "old age"
I have 192 megs of Apacer PC-100 SD's installed currently clocked at 112 MHz. (CPU: 112x4 = 448)
Sometimes when i push my 'puter to the limit, it freezes, and when i reboot it only finds 64 Megs or 128 Megs - 90% of the time it finds 64 megz.
The first time this happened, i got a little scared, fearing that i had fried 128 megs worth of Apacer PC100 SD's. I turned off the power for 10-20 seconds, and then booted up again - this time with all my 192 megs.
I then later found a program called "RamBooster" which helped a lot (freeing up memory when there's only a few megs left). I'm now sure, that the 'puter only freezes when all the memory is used up, and one or more programs are accesing it (WinRAR).
Then it struck me that it could be clock of the memory which screwed everything up, so i quickly clocked it to 450 - 4.5 x 100.... which didn't help. I ran it at this speed for a day or so to make sure that it wasn't a one time freeze only.
Now i'm running @ 112x4 again, and curious about what is causing this error.
My own guess is that my windows needs a reinstall, which bothers me. (never had a windows running better than this one)
Here is a run-down of my system:
AMD Sharptooth (K6-III) 450@448 - 112x4
192 PC100 Apacer SD's (1x64, 1x128)
Epox G2 motherboard
Matrox Marvel G400
Adaptec 2910 SCSI
Realtek 10/100 NIC
25 gig IBM HD
6 gig Seagate
Plextor 12/4
Pioneer 6x/32 (doesn't work http://sysopt.earthweb.com/forum/frown.gif)
Soundblaster AWE 64
My os is Windows 98v2
I Have been fiddling with the timings in the BIOS - didn't help, neither does default settings.
Is this just signs of my windows getting old?
~Wiruz, The Digital Hippie
[This message has been edited by Wiruz (edited 01-28-2001).]
I have 192 megs of Apacer PC-100 SD's installed currently clocked at 112 MHz. (CPU: 112x4 = 448)
Sometimes when i push my 'puter to the limit, it freezes, and when i reboot it only finds 64 Megs or 128 Megs - 90% of the time it finds 64 megz.
The first time this happened, i got a little scared, fearing that i had fried 128 megs worth of Apacer PC100 SD's. I turned off the power for 10-20 seconds, and then booted up again - this time with all my 192 megs.
I then later found a program called "RamBooster" which helped a lot (freeing up memory when there's only a few megs left). I'm now sure, that the 'puter only freezes when all the memory is used up, and one or more programs are accesing it (WinRAR).
Then it struck me that it could be clock of the memory which screwed everything up, so i quickly clocked it to 450 - 4.5 x 100.... which didn't help. I ran it at this speed for a day or so to make sure that it wasn't a one time freeze only.
Now i'm running @ 112x4 again, and curious about what is causing this error.
My own guess is that my windows needs a reinstall, which bothers me. (never had a windows running better than this one)
Here is a run-down of my system:
AMD Sharptooth (K6-III) 450@448 - 112x4
192 PC100 Apacer SD's (1x64, 1x128)
Epox G2 motherboard
Matrox Marvel G400
Adaptec 2910 SCSI
Realtek 10/100 NIC
25 gig IBM HD
6 gig Seagate
Plextor 12/4
Pioneer 6x/32 (doesn't work http://sysopt.earthweb.com/forum/frown.gif)
Soundblaster AWE 64
My os is Windows 98v2
I Have been fiddling with the timings in the BIOS - didn't help, neither does default settings.
Is this just signs of my windows getting old?
~Wiruz, The Digital Hippie
[This message has been edited by Wiruz (edited 01-28-2001).]