|Did you find anything when you examined the capacitors ? |
If you didn't, then there is no certainly the mboard is damaged.
"2) I am writing clearly that I am getting BLUE SCREENS while the system loads the WIN XP PRO kernel!!! "
"DIFFERENT CODE each time I am trying!!! The only reason I did not post a code of blue screen issue is that every time I retry, it gives a different code!!!"
The same problem can cause different STOP error codes. However, eventually, usually, you see the same group of STOP error codes again.
"Or when I tried to REINSTALL Win XP PRO, it starts the hardware detection, starts to load the files from Installation CD and suddenly crashes and appears A BLUE SCREEN reporting a hardware issue!!! "
You should NOT get ANY errors reading the files from that XP CD.
If you DO get errors reading files from the CD,
See Response 7 in in this,
"Errors reading from the CD can be caused by....."
If the second stage of Setup DOES NOT complete, you DO have a hardware problem .
See response 7 and response 9 in this:
"RAM: (Dual channel) 2 X DDR 256MB, 333 MHz, but I tried too 2 X 1 GB Kingston 400 MHz adjusted once @ 333 (166 MHz) and once @ 400 (200 MHz) timing!"
There is usually nothing wrong with the ram that worked fine when it was installed in the mboard previously.
Ram that works in another mboard , or any ram you buy or have lying around, may not work properly, or sometimes, not at all - even if it physically fits and is the right overall type (e.g. SDram, DDR, DDR2, etc.; PCxxxx, xxx mhz) for your mboard. In the worst cases of incompatibilty your mboard WILL NOT BOOT all the way with it installed, and the mboard may not even beep - the ram has to be compatible with the mboard's main chipset, or in the case of recent mboards, compatible with the memory controller built into the cpu.
If you still have the ram that was installed when the system worked fine, and you know which modules they were, try installing just that ram.
Some ram manufacturer's modules do not strictly adhere to the JEDEC standards that most mboards bioses use to determine ram settings.
In that case, the ram settings in the bios Setup that the bios has automatically chosen may not be correct.
Check the ram settings in your bios - the ram voltage, and the ram timing numbers - those should be the same as for the specs for the modules themselves. Often the ram voltage and timing numbers are printed on the label on the modules.
If the voltage setting or timings settings in the bios are different from the specs for the ram, change them in the bios. The timing numbers must be as close as you can get to the same, or slower timings (higher numbers = slower) - you won't notice the difference the slower settings make.
If you have a mix of different modules
- don't mix ram that different voltages are specified for - the bios will force the ram to use the lowest voltage, if "by spd" or similar is used (default settings) - ram that a higher voltage is specified for is more likely to not work properly in that situation.
- the bios settings must be those for the slowest timing settings of all the modules, or slower (higher numbers = slower).
NOTE that I have seen some cases in Topics on this web site where the ram passes a diagnostics test, yet there are errors produced in Windows when the settings the bios is using for the ram don't match the specified settings the ram is supposed to use. E.g. when one or more of the ram timing numbers the bios is using is LOWER than that specified on / for the module (that being higher than specified causes no problems).
"CPU: Intel 4 @ 2.8GHz Northwood (the same that was working always) but I tried also another P4 @ 3.0 GHz Northwood!!!"
Apparently there are P4V88, P4V88+, and P4V88-M+ models.
If you have the P4V88
According to this:
The only 3.0 ghz Northwood cpus you can use are one of these: