View Single Post
  #1 (permalink)  
Old 10-13-2006, 08:56 PM
Rod Speed
Guest
 
Posts: n/a
Default Re: Problem already solved but Iwant to learn what caused the problem. TIA

Joel <Joel@NoSpam.com> wrote:

> Sorry if the question was asked and answered, but I just joined this
> newsgroup right after having some weird system problem and have it
> solved (I hope for good) by luck. And I decided to join this newsgroup
> to learn a little more about computer problem for future use.


> Anyway, I am running WinXP SP2 (I don't think
> software has anything to do with this but who knows).


> AMD Athlon 3700+ 64
> 3GB memory
> (1) 100G (2) 250GB hard drives
> 1 DVD burner
> 256MB video card GeorgeForce something


> I usually have system running 24/7 and only reboot the system every
> few days when system starts slowing down, then back running again.
> And for about a week the system started acting up, first it locked up
> after 2 days, then 1 day, then 2-3 times a day.


> - Yesterday, the system reported that the booting device
> (not the correct word) or something was changed, and it
> gave the option to F1 = continue or DEL to go to CMOS
> setting. I pressed F1 and it continued to boot just fine.


That sounds like the cmos battery going bad.

> - Then around an hour later it locked up again. I tried to
> reboot and it gave the same report saying that the booting
> device/option was changed, but didn't give the option to
> press F1 to continue like last time.


> - I checked the CMOS setting to find out that


> - Drive C: became Slave (100GB)


> - Drive D: became Master (250GB)


> I checked the jumper, changed cable, disabled Drive D: and
> changed Drive C: to single drive etc. but it still won't boot and
> still getting the same error message "Verifying DMI Pool Data"


That isnt an error message. Its an information message that is
there every time you boot. The reason you see it is because
normally it flashes by so fast you dont notice it unless you look
for it. In this situation it isnt managing to do what comes next,
so that stays on the screen and you can see it.

> I have never seen this type of problem before so just can't figure out
> what caused the problem and why it changed the Master/Slave etc.
> and I was looking to get another system built while checking for the
> warrantee replacement (both CPU and Mboard are 5-6 months old)


> - While having the case opened I checked the FAN of video card which
> stopped working and I gave it some oil to make it spinned again (and
> also ordered a replacement fan). I found the fan stopped again, so I
> replaced the dead fan with a working one, and didn't have any hope of
> solving the booting problem but killing the time.


> ... and for whatever reason it has solved the booting problem
> (for good I hope), and I hope that the FAN was the problem
> (it just doesn't seem right?). There must be something else?


Yeah, it cant have been that.

> ....Hmmm.. I just did "Properties" on the 100GB (drive C:)
> which supposes to be 100GB, but the properties reports
> it's a 56GB hard drive and with 40GB avalable space.


> It seems like something eating 44GB and damaged the partition?????


Its more likely that whatever changed the drives around
also change the drive type setting. It should be AUTO.

> I have no problem replacing this with 500GB, but just
> want to learn what is causing all these problems, and
> it may be the best chance to learn something new.


I'd check for corrosion around the cmos battery. It shouldnt have
gone bad that quickly. If there is no obvious corrosion and the top
contact isnt lose, I'd try replacing it anyway, it may be a bad cell.



Reply With Quote