Hardware strangeness

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



Brand new motherboard Gigabyte GA-VM900M with Socket 775 CPU in it P4 3.0Ghz. and 512megs ram. Oddities happening all over this installation made me doubt the thing is working right.

So, I decided to get out a brand new hard drive that has never been used before, install XP fresh on it and install the motherboard drivers thereafter. All APPEARS OK but when you do something requiring a lot of mucking about, it sometimes dies. This is EXACTLY what happened with the computer before under its own CPU and motherboard and older XP installation. I thought the case may be busted because some fool who put the computer together used the "case open" warning attachment on the motherboard to shove the leads that show only power is on and the motherboard original in it had slowly degraded to the point where it started throwing up errors that didn't make any sense.

Therefore, there I am with brand new case, brand new motherboard, brand new CPU, brand new HD and brand new ram and I install XP fresh. When it finishes, all seems OK but the one thing that would kill the old machine reliably was to do a chkdsk /r and command and reboot and let it do that. It would get all the way through to test 5 of 5 and do that 100% and just when it was supposed to reboot, wouldn't. It would, instead, blue screen with an IRCL error "not equal to" or something along that sort of wording. So I did that chkdsk /r with what is basically all new machinery and sure enough, same problem. I figured the motherboard was probably wrecked because I put it in the old case in the first place so put a new motherboard in a new case and put new ram in it again and installed XP fresh all over again and did the chkdsk /r on it again and same problem. However, boot off the XP CD and go to the first repair prompt and do chkdsk /r there and it completes with no errors and doesn't blue screen.

So has anyone any ideas why this is going on please? I think my eyes are crossed and I cant see an answer because of that now because I cant see any sense in it.

Any help appreciated.

.



Relevant Pages

  • Re: building a new DIY PC
    ... I will install the Zalman CNPS9700 LED cooler now before bringing into the ... I can go buy a bunch of other parts so I could tell myself if it's the CPU ... chip, motherboard, RAM sticks, which the RAM stick are brand new also, ... shouldn't be a problem now with the CPU chip and motherboard. ...
    (microsoft.public.windowsxp.hardware)
  • Re: Power management lappies
    ... major problem could be solved just with potatoes, ... What I'd suggest is download and install System Mechanic (not the ... your hardware type and see if you can upgrade the RAM. ... Once installed and ran, go into Motherboard, then go into SPD. ...
    (alt.2600)
  • KERNEL_DATA_INPAGE_ERROR installing XP Pro on new hardware
    ... I just got a new ASUS P5Q-EM Motherboard, ... and the install screen says 39 minutes left for completion. ... I removed the RAM and got the expected beep code for no memory detected ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: RAM Issues
    ... > up the ram voltage, ... > check a forum that has users of your motherboard - they may have good ... If you do replace a stick, I would try a different brand ... > system file is now bad on disk. ...
    (microsoft.public.windowsxp.general)
  • Re: Clean Install Fails
    ... I found it to be an issue with the motherboard auto-detect of the ... Usually it is the video card that causes this kind of failure in ... There is a known issue with installing x64 when 4GB of ram is installed. ... Reduce it to 2GB, install Vista, then reinsert the other 2GB of memory. ...
    (microsoft.public.windows.vista.installation_setup)