Forum Home
Press F1
Thread ID: 66613	2006-03-01 10:59:00	Internal Problem	norrol (2154)	Press F1

Post ID	Timestamp	Content	User
434801	2006-03-01 10:59:00	Is there any software one can use to check health of computer internals such as motherboard ,Memory video card,Cpu etc.I suspect I have some internals that are starting to break down with numerous freezes where computer just freezes and has to be rebooted. It isnt a software problem because i have reformated all 2 drives and reinstalled Windows Xp as a fresh install and have just loaded minimum of programs but still get freezing all the time in fact I spend more time rebooting than anything else and if I take the computer to a retail outlet they charge you the earth and then try and tell you you need to replace Cpu motherboard Memory etc and so on so any tests I can do my self will possible show me where the problem is. I do have software called Sandra but I believe this is for benchmarking not diagnostic problems	norrol (2154)
434802	2006-03-01 11:14:00	What type of computer do you have? An HP etc... Computer? How old is it? What are the system info?? Ie what type of CPU? Etc..?	stu161204 (123)
434803	2006-03-01 16:57:00	it could be overheating it could also have a dying motherboard/powersupply/ram........could be almost anything.........download the ultimate boot cd and run that to test your system.....	drcspy (146)
434804	2006-08-17 00:24:00	I am also having what I think is hardware problems. My computer also freezes about two times at least every day. I have three operating systems installed: Windows XP Pro, Mandrake Linux and Beos Phosb6. It seems to be problems mainly confined to Windows and Mandrake. They are both installed on a single Western Digital 80gb SATA So I suspect it is either the drive or drive controller. There are no bad sectors. There are a lot of Error number 11 and 51, in event viewer. It said on the microsoft website that Error 11 most likely means a bad SATA cable. I replaced the cable but no difference. So I am also going to try the Ultimate boot CD.The mainboard I am usinng is a Gigabyte 7n400 Pro2(Rev2). Ever since I bought it second hand three weeks ago I have had a lot of trouble in quite afew different areas and to think I replaced the Albatron KX600S Pro, thinking I would get better SATA detection and usability. Now I have already sold the Albatron. I don't no if there are some basic problems with the GA-7n400 Pro2(Rev) or it is because it was second hand. The SATA drive controller on the board is a Sil-3512. Does anyone else have any experiences with this board or fixed these types of problem?	procosm (6108)
434805	2006-08-17 01:43:00	The mainboard I am using is a Gigabyte 7n400 Pro2(Rev2). Ever since I bought it second hand three weeks ago I have had a lot of trouble in quite a few different areas and to think I replaced the Albatron KX600S Pro, thinking I would get better SATA detection and usability. Now I have already sold the Albatron. I don't no if there are some basic problems with the GA-7n400 Pro2(Rev) or it is because it was second hand. Being second hand is a good pointer. :groan: Ever ask yourself why the original owner sold it? Buying something as critical as a motherboard second-hand is an invitation for disaster because you have no idea what has been done to it by its previous owner. It may not be the cause of your problems, but if everything else remains the same it very well could be. One possible cause could be wrong MB drivers because unless you did a fresh installation from scratch, your HDD is still set up for the Albatron. If you didn't, one way around that is to delete all drivers under device manager (or its equivalent in the other two operating systems) then reboot into each OS in turn and allow them to locate and install drivers for all devices including the MB. I'd get Windows running first though, to prove whether the problems have been resolved before wasting time on the others. Cheers Billy 8-{)	Billy T (70)
434806	2006-08-17 03:54:00	Here is my little checklist: Motherboard: physically look for bad capacitors, burns marks and other stuff that shouldn't be there (e.g. rodents) CPU: rarely are they they the cause - check CPU fan is OK and not overheating (CPU temp monitoring app, while running something using 100% CPU) Hard Drive: Manufacturers diagnostic tools RAM: Memtest86 or Memtest++ (and swap out if needed). Be sure to test for a few cycles Power Supply: could check leads with multimeter (and see BIOS statistics) but I usually just grab a known good one and see what happens Also poke around relevant motherboard help forums and check for bios updates/mobo drivers. Quite a lot of it comes down to swapping one part out at a time (which is pretty tricky for home users), until you find the faulty part. It could take a very long time to isolate the problem....you just have to be methodical. It could have been caused by static charge damage to the motherboard (or just a buggy design). Ah the motherboard always gets the blame :)	gibler (49)
434807	2006-08-17 06:08:00	It may not be the cause of your problems, but if everything else remains the same it very well could be.[QUOTE=Billy T] Yes every other piece of hardware is the same as before. [QUOTE=Billy T]One possible cause could be wrong MB drivers because unless you did a fresh installation from scratch, your HDD is still set up for the Albatron.[QUOTE=Billy T] I did a fresh install of Windows XP. I initially tried to boot Mandriva from its previous driver state, because I read that it could handle a complete change of manboard but found it necessary to reinstall it. It functioned until last night when it refused to boot so I formated the / partition but not the /home partition reinstalled but it refused to load the driver for the realtek rtl8169 network chip and froze. [QUOTE=Billy T]I'd get Windows running first though, to prove whether the problems have been resolved before wasting time on the others.[QUOTE=Billy T] I have Windows installed and it goes fine except if I have done a quick switch to another user login (not logging out from previous user) that's when I seem to ger hit with random freeze ups. i look in the event log viewer and about the time these happen there is error 11, (The driver detected a controller error on \Device\Harddisk0\D.) error 51, (An error was detected on device \Device\Harddisk0\D during a paging operation.) [QUOTE=Billy T]Cheers Billy 8-{)	procosm (6108)
434808	2006-08-17 06:36:00	Here is my little checklist: Motherboard: physically look for bad capacitors, burns marks and other stuff that shouldn't be there (e.g. rodents) CPU: rarely are they they the cause - check CPU fan is OK and not overheating (CPU temp monitoring app, while running something using 100% CPU) Hard Drive: Manufacturers diagnostic tools RAM: Memtest86 or Memtest++ (and swap out if needed). Be sure to test for a few cycles Power Supply: could check leads with multimeter (and see BIOS statistics) but I usually just grab a known good one and see what happens G Also poke around relevant motherboard help forums and check for bios updates/mobo drivers. Quite a lot of it comes down to swapping one part out at a time (which is pretty tricky for home users), until you find the faulty part. It could take a very long time to isolate the problem....you just have to be methodical. It could have been caused by static charge damage to the motherboard (or just a buggy design). Ah the motherboard always gets the blame :) I am using Speedfan and when I am running the Community Grid application, that is helping with medical research, it runs the CPU at 100%. The temperature never goes past 54c. If it was the hottest time in summer it might go a lot higher. The mainboard might have higher power needs than the Albatron board because it also needs the extra ATX 4 pin plug from the powersupply, and I am using a 350W. The devices I have installed are: Gigabyte Nvidia Geforce FX5700 with it's own small fan. Seagate 40Gb ide drive. Seagate 80Gb SATA drive. LG DVD ROM combo drive 3.5 Floppy drive One 80mm case fan One 80mm fan on the CPU heatsink. I did upgrade to the latest BIOS available: FK 23-12-04 I have run memtest from the linux install CD and run it several times over, with no errors. I will look for bad capacitors and burn marks. Thanks for help from you all.	procosm (6108)
434809	2006-08-17 12:06:00	Here is my little checklist: Motherboard: physically look for bad capacitors, burns marks and other stuff that shouldn't be there (e.g. rodents) CPU: rarely are they they the cause - check CPU fan is OK and not overheating (CPU temp monitoring app, while running something using 100% CPU) Hard Drive: Manufacturers diagnostic tools RAM: Memtest86 or Memtest++ (and swap out if needed). Be sure to test for a few cycles Power Supply: could check leads with multimeter (and see BIOS statistics) but I usually just grab a known good one and see what happens Also poke around relevant motherboard help forums and check for bios updates/mobo drivers. Quite a lot of it comes down to swapping one part out at a time (which is pretty tricky for home users), until you find the faulty part. It could take a very long time to isolate the problem....you just have to be methodical. It could have been caused by static charge damage to the motherboard (or just a buggy design). Ah the motherboard always gets the blame :) I have downloaded the latest drive controller driver SIL3512 from Silicon Image and it seems to have solved the problems. The Gigabyte Sil3512 driver is from about December 2004 but the Silicon Image driver is from April this year.	procosm (6108)
434810	2006-08-17 12:57:00	didn't norrol start this thread, not procosom? where is norrol? procosm: i blame the motherboard, but try borrowing a hdd (possibly an ide one too - i know you have one but you never know) and see if that crashes. if it doesnt it was your hdd, but try an ide hdd just incase it was infact a sata issue which could be hdd/mobo/cable (yes, you can get 2 faulty cables in a row). also try putting your existing hdd in another pc etcetc do you have a mates computer you could borrow for the weekend? that way you could systematically (as others have said) swap 'n' see what the problem is. just take a component (like ram), swap, and see who crashes :) obviously check compatibility first be sure to accidentally mistake your 3000+ for their 4200+ and neglect to mention it ;) (i dont think there would be any reason to check cpu's unless you have plenty of spare thermal paste stick-it-btween-cpu-and-heatsink stuff)	motorbyclist (188)
1 2