Windows loading fail

[Haroon92]

I'm trying to install windows 7 on a Hp DC7800, but everytime it fails to go any further and stuck at "windows is loading files". I've reinstalled the operating system several times on the flash drive. And i've use this bootimage to install windows before along with the same flash drive. I did change the flash drive also. I've changed RAMs, but still nothing. I've also used a different boot image, but this one wasn't even started to load. Not sure whats the problem, but my guess some reason is the images...But the reason I'm posting this message asking for help is because there mght be someone that has already experience this issue. Thanks.

 

[cypress]

What about the hard drive? What was the results on the diagnostics?

 

[Haroon92]

I haven't tested it separately as yet...going to do that now. By the way, I just installed a new image, but now it has passed the "windows loading", but went straight to a black screen and stuck there. Gonna test the hard drive separately now.

 

[cypress]

Yeah checking the hard drive first saves you all the hassle from the get go. Even "brand new" drives can still arrive DOA. Nothing is safe.

 

[Haroon92]

OK, so I attached the hard drive to another computer via sata cable, and now it's being installed just reach 15%

 

[Porthos]

and now it's being installed just reach 15%

It wont boot in the machine it came from with Win 7. If loading windows on the other machine.

We wanted to see drive tests not if it would load windows hooked up on another computer.

 

[Dogzilla]

As above, anything slow like this on installation, get the drive out of that machine, slaved to your workbench pc, and run some diagnostics.

 

[Haroon92]

It wont boot in the machine it came from with Win 7. If loading windows on the other machine.

We wanted to see drive tests not if it would load windows hooked up on another computer.

Chkdsk wasnt checking the hard drive that came from the faulty machine...If i entered "CD D:/" it would just go back to C:/.

 

[Haroon92]

Ok, so the problem was that it had another bad memory. I removed the bad memory and everything works fine now. I didn't know memory could have that sort of effect.

 

[Porthos]

Chkdsk wasnt checking the hard drive that came from the faulty machine...If i entered "CD D:/" it would just go back to C:/.

Chkdsk is NOT a drive diagnostic tool.

 

[mikeroq]

Ok, so the problem was that it had another bad memory. I removed the bad memory and everything works fine now. I didn't know memory could have that sort of effect.

"Windows is loading files" is WInPE being copied into memory. The installer uses WinPE which makes a ram disk and loads into memory. Thus a memory issue could cause issues.

 

[frase]

Use CrystalDiskInfo to check HDD

 

[Haroon92]

Chkdsk is NOT a drive diagnostic tool.

but it fixes drive issues...What you recommend?

 

[Porthos]

but it fixes drive issues...What you recommend?

Has a bigger chance to kill a drive if it is failing. Chkdisk is to fix file system issues NOT drive issues.
See the above post from frase.

 

[Haroon92]

Use ChrystalDiskInfo to check HDD

ok, thanks, man.

 

[Haroon92]

Has a bigger chance to kill a drive if it is failing. Chkdisk is to fix file system issues NOT drive issues.
See the above post from frase.

Yeah, yeah...I will certainly hold on to this.

 

[Markverhyden]

but it fixes drive issues...What you recommend?

Actually it does not fix drive issues. It fixes Windows operating system and file system issues.

 

[Haroon92]

Actually it does not fix drive issues. It fixes Windows operating system and file system issues.

Thanks. I always thought that it fixes drive problems. And remember, I'm still learning, and I thank God you all.

 

[Mick]

Regardless of whether or not running CHKDSK is a good idea (and it mostly isn't), you are using the wrong command syntax. You want: CHKDSK D: (followed by whatever switches etc you decide to use. 'CD' just changes the directory. CD doesn't stand for ChkDsk.