Bad Checksum

LOL, Rockster! I can't picture myself operating a soldering gun with one paw! Even if I KNEW what I was doing!

I think I'll just build a new comp, bump this one down to the kids (if they lose CMOS now and then, who cares? At least I know how to correct it!)

I use 2 sticks of 512 MB PC 133 SDRAM. The CMOS problem was worse before I got these two identical sticks (was only running one 512 stick of DDR RAM a year ago)

From your link:

That would explain why there are less CMOS failures when I don't shut down very often!

Aida32 always tells me that "current AGP is less than max supported, may cause performance issues" Anything I can do about that?

I told you guys "Hardware" was one of my weaknesses. I appreciate any thoughts or suggestions.

Johanna

 

Thanks
Johanna and Rockster2U for the two MOBO links.
Have this board - The 3rd one was just installed, now waiting for new processor chip (it also fried along with PS in 17 months usage). This board has given me a long history of CMOS "lost settings" at cold boot start. Have changed batteries number of times... problem remains.. inconsistent, no rhyme or reason, CMOS settings lost. Will share this info with local builder.

 

Dennis, if you want a list of documentation of the CMOS problems of that board, send me an email. The only thing people agree on is that it is a known quirk of the board. But, though losing CMOS is a nuisance, it is not a disaster, and those boards do perform better than average by all benchmarks, and were quite reasonably priced.

To minimize freezing problems after several bad checksum boots, always cure by jumping the pins, to clear CMOS. To improve the behavior of this board, try fewer cold boots, reducing the system temp, eliminating power fluctuations, and praying to St. Jude. Well, that is what worked for me, anyway, to go from having the error often, to just occasionally. After all, it ran clean for 6 months...

Johanna

 

Thanks Johanna

The CMOS setting problem is as predictable as a politicians rhetoric... promise eveything, just don't say when it's going to happen (my question, who's paying for it. Darn, don't get me started). Oh well, will be concentrating on "good cooling and very timely cleaning" to extend life cycle. So far, builder has been picking up the bill. Have not picked up system from this rebuild, but I'm suspicious he'll try to hit me on the "data rescue ". One of them "rock and hard place" problems. Wish I had the fortitude (I was going to use a part of the male anatomy here, but don't want anyone to blush) to be my own builder... but Newt would have to add another server to keep up with all the questions -and- pestering all you fine folks would test the phrase "labor of love ".
Keep yours eye open for a PM and my email address for that CMOS documentation problems.
thanks

 

Same here. I've had a hand-me-down soldering iron for over ten years and haven't used it yet . I would grab the parts (a resistor), move all the cables away from that place on the motherboard, print out that picture and take them down to the local TV repair shop. Will probably do it on the spot.

Matt

 

Dennis L
I'll send the documentation when I get back from PT. Sadly, my computer gets as messy as the office, sometimes! But, that's what reinstalls are for!

Data Recovery
In all my trials and tribulations with this mobo, data recovery has NOT been an issue. A few bad dates in WE, lost History in IE, system time & proc speed, yes, but not data loss. When you lose CMOS, can you still run the comp, or does it have to go back in for repairs?

I was intimidated the first time I took the case apart, but the inside is not rocket science, and it's much easier to do "builds" than "repairs ". I am no hardware expert, and right now screwdrivers are giving me fits, but it is not scary to me anymore. Remember the old saying: "If you want domething done right, do it yourself! "

Cheers,
Johanna

 

Thanks Johanna

No rush, you take your time. Computer still in hospital.

CMOS issue
The first 6 months it was "multiply times per week ". He did a minor repair to the board (said he modified the battery holder unit) and reduce the problem to one or two times per 6 weeks. It never caused any other problems, just the annoyance of resetting the date / time / and chip multiplier.

Data recovery
There has been two re-occuring events with this computer...
CMOS .... High rate before "modify" then very infrequent.
Auto-Boots .. Very infrequent. But then "beginning of the end" would start. Frequency would increase. 1 per week to 1 per day to 1 per hour ".
When the 2nd MOBO / PS fried I posted asking (see thread) maintenance, heating issues... since this is what my builder says is causing the problem. Also, unlike previous MOBO / PS replacement, the HD was not reconized and required data rescue.
Needless to say, my patience / his patience has been tested on this issue. I keep asking why all the hardware failure, he sticks to his guns. Current type computers require very timely cleaning to prevent the heating. All of this has occured over a 17 month period.

 

Oh ye timid souls - this problem is very well documented and caused by both low or high temperatures on the SIS Mobo chip. You can pick up a decent soldering iron and this resistor at Radio Shack and its not a difficult repair. Think of it as the next progression from that once fearful task of opening your case - wasn't really so bad once you got past the phobia. And, as mattman suggests, if its too much for you, take it down to your local TV repair shop.

Sometimes one has no choice - I got past my fear when I broke a surface mount socket that held a BIOS chip (small one) - had 64 pins 4x16 in an area about 5/8" square - it was either solder on a new one or pitch the whole machine (modded I-Opener). Long story short - runs like a watch today. Never thought I could do it either.

Even one handed, you can do this if you can get past the fear factor.

 

Mattman & Zander
Just to let you know, the IE History is affected by the cmos date. I had been lazy the last few times, and set the clock from w/in Windows, but it must be done in BIOS to not lose the History.

I manually cleared CMOS this evening- I think the mobo is running too hot. It's about 10 degrees higher than normal (Thank you Motherboard Monitor!) and it has been freezing occasionally.

Over the winter, my neighbor cut down two huge oak trees that provided shade on the west side of the house, where the comp is. Now the afternoon sun is streaming in, even through closed blinds. I'm grasping at straws, I know, but other than that, nothing is any different than last week, month, year, other than some MS updates!

Dennis, did you get yours back yet? I didn't forget the documentation- gotta find it on an older cd from a couple of reinstalls ago! Not to worry, though, I learned a long time ago- back up back up back up, which is what I'm fixing to do right now.

Rockster Hey, YOU come over and fix this durned thing with your soldering gun and I will cook you the best lasagna you ever ate!! (You are exactly right about the "fear factor "!)

Johanna

 

Dennis, did you get yours back yet? I didn't forget the documentation

Have had it back about 10 days, remember the thread I started, XP - Home to PRO. No longer have that MOBO. Builder installed a Syntax - SV266AD board, with VIA VT8366A Apollo KT266A chipset, new AMD Athlon XP, 1800 MHz (6.75 x 267) 2200+ processor. Same 512 MB memory and HDD from old system.
Is a responsive system, with boot up, shut down both at either side of 45 seconds. But there seems to be a "history problem" with this MOBO...(?) Sensor readings have a +- 50% shift / drift. In simply english, their whacked. Have this readout problem with ADIA32 and have read similar threads/MOBO when using MBM 5.3.6.0. The current guess, it's a software glitch. If anyone has a sensor monitor suggestion to get a accurate read, would be thankful.

 

Hi Johanna,

I can't find anywhere you told us what bios you have (version and date).

If you haven't already, take a look at:
http://www.ecs.com.tw/download/k7s5a.htm

If the date on your BIOS is earlier than 2002/11/19, you may need to flash the bios for that date which fixes the "CMOS can't be saved issue ".