new build problems

Associate
Joined
19 Mar 2006
Posts
633
Location
Suffolk
I had major issues with my old rig recently (random crashes and power offs etc) so I bought some new components to build a new rig as I was getting no where fast with the old kit.

Old kit list

C2D E6850 with AC7 cooler
Asus P5K Premium
4x1GB OCZ 6400 DDR
XFX 8800GTX
WD250GB SATA HD
Corsair VX450
Emu0404 soundcard
Old Philips IDE DVD/CDRW unit
CM690 case
Vista 64

I tried changing the GFX, PSU, tested RAM and HD, cleared CMOS, re installed Vista etc with no luck.

So I decided to buy some new components as I was getting pretty narked after about a week of issues.

Purchased the following:

Corsair TX650 PSU
Asus P5Q (B Grade)
4 x 2GB Corsair 6400 DDR
WD 1T Green HD

Now I am trying to install Vista 64 and getting issues again!!

Tried installing to 2 diiferent HD and getting similar issues.

It did initially install but was flakey and would noly install drivers etc so I tried a new install and am now not getting through the installation.

I have just tried another optical drive just incase but no better.

It just went through an install then upon reboot gave a checksum error so I restarted and tried the memtest option in Vista install. It restarted and again gave the following error message.

Windows failed to start. A recent hardware or software change might be the cause. To fix the problem:

1. Insert install disk
2. Choose language settings then click next
3. Click "Repair your computer"

If you do not have disk contact sys admin or manufacturer for assistance.

File: \boot\memtest.exe

Status: 0xc0000221

Info: The file is possibly corrupt. Its header checksum does not match the computed checksum.


Any idead on what to do next please as my head is hurting now:confused:
 
I suppose it could possibly be the cmos battery but I need advice from someone with a better knowledge level than my own.

Anyway I have removed the power lead and battery and shorted the clear cmos pins and will try again.

Fingers crossed.
 
It might be the CMOS, a couple other threads recently had problems that were corrected by resetting it.

Btw, did you get the kit today?

Edit. 2 things. Firstly you said you got through an install the first time. Have you reformatted and totally wiped the drive since then? Might be an idea. Also, http://forums.overclockers.co.uk/showthread.php?t=17955761 dude here says he needed a SATA Optical drive to install Vista on his Asus board.
 
Last edited:
Yes tried a wipe etc and even another hard disk.

I installed Vista64 on my previous Asus mobo using an old ide drive with no problems.

Anyway I'm about to retry after clearing cmos etc.
 
Yes tried a wipe etc and even another hard disk.

I installed Vista64 on my previous Asus mobo using an old ide drive with no problems.

Anyway I'm about to retry after clearing cmos etc.

I'm sure someone else can give you some better insight.

But before you go...did you get your parts today? :cool:
 
OK it got about 98% of the way but then stopped with the following message:

"Windows cannot install required file. Make sure all files required for installation are available, and restart the installation. Error code: 0x80070714"

Any ideas...............
 
I am using the 8GB of Corsair RAM and not the OCZ sticks

I have just performed a cleam install using an old IDE hard disk and the IDE optical drive in a master slave setup on the one EIDE port on the mobo and it all appears to be working. I am halfway through the mobo driver installs.


Very strange, could it be a conflict between the IDE optical drive and the sata ports?
 
I spoke too soon, its still not happy.


It is now throwing up errors saying access violation at address 004101BC in module 'InstAll.exe'. Read of address 9E870F0C.

I think I'm going to go and buy a SATA optical to try as I am getting bored now.
 
Just stuck a Gigabyte GA P35C-DS3R in and its working fine now, the Asus is getting returned for a refund.

Just bad luck I suppose.
 
Last edited:
I spoke too soon. It started to power off again this morning whilst trying to install drivers etc.

The only item left unchanged is the CPU, could that be the problem.

Its not overheating according to the bios harware monitor screen.

I can't see any shorting issues such as cables frayed etc.

I suppose I will have to try a new CPU............:(

Any thoughts.
 
I am going to try one last build outside of the case with all the new components and my original E6850 CPU. If that still fails then it pretty much must be the CPU in my book.
 
It might be bad media, got the ability to try a new install disk from a friend? If not then try 1 stick of memory at a time, make sure voltages are set fine.

- Pea0n
 
Asus P5K premium (original mobo)
4x1GB OCZ (original)
XFX8800GTX (original)
Corsair VX450 (original)
WD 250GB SATA HD (original)
PATA combo drive (original)

Asus P5Q (new)
4x2GB Corsair (new)
WD Green 1TB (new) also tried WD250GB (original)
Corsair TX650 (new)
XFX8800GTX (original)
PATA combo drive (original)

Gigabyte GA EP35C-DS3R (new)
4x2GB Corsair (new)
WD Green 1TB (new) also tried WD250GB (original)
Corsair TX650 (new)
XFX8800GTX (original)
PATA combo drive (original)

All tried in a CM690 case installing Vista64 Home Premium

It never crashes out whilst in the bios and is solid through the install of Vista when it installs OK. When it gets into windows the power offs occur at random intervals.

As you can see, I have swapped all except the CPU so far.

If we go back to the original system with the P5K premium, this system had been rock solid for around 8 months prior to the power offs. I had installed no new components at all and am not aware of any power spikes or surges occuring locally. Windows update runs on auto and I had full AV and firewall running etc.

I tried swapping ram sticks, running memtest, new PSU, different gfx card, clr cmos, removing soundcard etc with no improvement.

The same issue has continued through the new builds with various components used. If we assume (and I know thats not clever) that all the new kit is OK, what is the common thread running through the builds. Possibly the CPU, case or OS software.

Is there something obvious that I am missing ?
 
Back
Top Bottom