Adventures in Computing
Posted: 2004-01-02 09:35am
Or, another hour of "FUCK!"
So my CPUFAN connection is failing to return the RPMs on my heatsink fan, which it's supposed to do. Won't do it in MBM, won't do it in the BIOS. So after mucking about with MBM settings, I decide to flip a switch in the BIOS.
The CPU overheat protect.
Problem is, the thing'll shut down the computer if the CPUFAN is under 500 RPM...
And since the CPUFAN connection wasn't returning any speed reading at all, i.e. 0 RPM...
Yeah. So I went in and cleared the CMOS jumper. Shorted the jumper, put it back, turned it on.
Dr Voice: "Your memory may have a problem."
FUCK!
Flash-forward to now. After various and equally useless attempts to fix the problem by other means, including clearing the CMOS again...I decide "to hell with it" and remove the 512MB RAM chip in DIMM 1.
Computer boots.
Cost of my efforts: Fan speed still reading 0 RPM, RAM down 512 MB to 384.
And I still can't figure out what happened to the RAM.
So my CPUFAN connection is failing to return the RPMs on my heatsink fan, which it's supposed to do. Won't do it in MBM, won't do it in the BIOS. So after mucking about with MBM settings, I decide to flip a switch in the BIOS.
The CPU overheat protect.
Problem is, the thing'll shut down the computer if the CPUFAN is under 500 RPM...
And since the CPUFAN connection wasn't returning any speed reading at all, i.e. 0 RPM...
Yeah. So I went in and cleared the CMOS jumper. Shorted the jumper, put it back, turned it on.
Dr Voice: "Your memory may have a problem."
FUCK!
Flash-forward to now. After various and equally useless attempts to fix the problem by other means, including clearing the CMOS again...I decide "to hell with it" and remove the 512MB RAM chip in DIMM 1.
Computer boots.
Cost of my efforts: Fan speed still reading 0 RPM, RAM down 512 MB to 384.
And I still can't figure out what happened to the RAM.