Chkdsk runs everytime I restart

Okay I tried it again with UtraISO and this time used F12 to select USB. (The ImgBrn/Universal route would have likely worked as well with F12)

Its now starting the install process..

Will post back results shortly...

I am still at full ram.... so the 2GB route is next if this does not work....

Okay,

BAD NEWS - The UltraISO usb based install generated the install load driver error message below.

GOOD NEWS - I pulled out that USB and put in the thee ( ImgBrn/Univeral) ... I bought two new ones this morning jsut for this reason). The ImgBrn/Univeral usb based install did not generate any error messages. Saw three partitions to choose from ( like a few doesn posts ago), ie
-100MB reserver
-350 GB Primary
-550 Gb Unallocated

I selected the 350GB, Foramtted it, and it is now proceeding with the install...

BAD NEWS - The orignal error code 0x80070570 message (of several posst ago returned). See below.

NEXT STEPS - Okay, now I will pull the memory next to do the following

NEW HD + IMGBRIN USB INSTALL + 2GB MEM

if that fails I will try:

NEW HD + DELL WIN7 OEM + 2GB MEM

if that fails I will try

NEW HD + SYS RECOVERY DVDS + 2GB MEM

if that fails , I will put everythuing back otghter and call DELL, Hopefuy tehy wont capmain about the extra meemry and new HD. I assupose I can remove both, put back the hITACHI, then call for help.... but perhas one of teh baove three last ditch attempt will work.

Didn't you successfully install with the Recovery Disks once before when the DVD failed?

I'd use them next if removing all but 2gb of RAM fails.

Remember to ground yourself by touching the case before touching the RAM. Don't force anything even if it takes too long.

gregrocker said:

Didn't you successfully install with the Recovery Disks once before when the DVD failed?

I'd use them next if removing all but 2gb of RAM fails.

Remember to ground yourself by touching the case before touching the RAM. Don't force anything even if it takes too long.

Yes, I did have success installing with the Recovery Disk,.. but then it could not do the Windows Updates....but that was with the old OEM HD.. and with full RAM.

I have never yet tried the Recovery Disks with the new drive, and certainly not with 2GB ram. We chatted about this earlier and decided used Ssytem Recovery DVDs should be last resort.

So are you are saying, of the choices below, try 1 and 3, but dont bother with 2??

1 NEW + IMGBURN USB INSTALL + 2GB MEM
2 NEW HD + DELL WIN7 OEM + 2GB MEM
3 NEW HD + SYS RECOVERY DVDS + 2GB MEM

Try all 3 now in that order. Report back exactly what happens.

RAM amount doesn't seem to affect Factory Recovery but memory may be causing the Update problems - or something in the factory image

This is why we should exhaust all steps to clean reinstall including applying a Win7 image made on another machine as a last resort - do you have either?

Ok, I removed all but 2GB, and proceeded with:
NEW + IMGBURN USB INSTALL + 2GB MEM

It successfuly completed with the full installation. HOWEVER, so did the
" OEM HD + SYS RECOVER DVD +FULL MEM" installation, which e know later failed and clobbered my machine on the Windwos Updates. .. but , taht was with a potentailly flayey drive and full RAM

OK, I will continue now with the true test - installing all windows updates, doing some restarts, and see it I get any of the isseud as per post 1 !

I will do all this with only the 2GB installed.

I will report back what happens.

(I may run into problems relating to drivers at some point ) - recall USB install does not quite have the same drivers as teh facotry install; the USB install has Windows only drivers)
.
NOTE - If successful, I still need to re-install the RAM. Once reseated, the next Windows update may clobber me again. I certainly do not want to remove memory each time there is a security patch. What is the game plan for that?? Is thrre a way, as a compromise, to lower thr available memory in thr BIOS? What is the common practice??? Do people really do this????

UPDATE

Still at 2GB. Generally very good so far in that many many updates and reboots were done without incident. In fact they did seem much faster ( but then again its a fresh install at new hard drive). but clearly low memory is good for updates!!

HOWEVER,

1) SP1 - Unlike previous version, is it not prompting me at all for Windows 7 SP1 update. I know this is not a known issue dicussed here : You do not have the option of downloading Windows 7 SP1 when you use Windows Update to check for updates , but I am curious why now?? All the other installs got passed this. Should I mannally intiiate it via this link ?

2) RAM - Per my note above, I still have my memory to put back Once reseated, the next big Windows update may clobber me again. I certainly do not want to remove memory each time there is a security patch. What is the game plan for that?? Is thrre a way, as a compromise, to lower thr available memory in thr BIOS? What is the common practice??? Do people really do this????

3) HOW MUCH IS TOO MUCH - Should I consder only putting back a max of 6GB... or 12GB .. or the full 18GB? At the time of purchase I did what I nomrally do, and that is I tend to buy (or plan to buy) the max memeory the unit can handle. This mnchine is for my home studio, so I was simply thinking ahead re recording software, control of studio equipment, music servers, streaming, videos, future home theatre use, etc But perhaps there is such a thing a too much memory. Nows a good time to downsize if thats the collective wisdom...

Windows Update will deliver many updates including Net Framework 4.0 and it's updates before delivering SP1. Just go with what it gives you, making sure to install the drivers delivered in optional Windows Updates promptly - in fact you can trust all optional WUD's. I wonder if lack of a driver caused your problem. I wouldn't rule out the excess RAM causing it although I've never heard of this before. I think it's good to leave it out until the updates are all installed.

I think you can reinstall all of the RAM but if problems crop up it should be suspect, tested with memtest86 for 5-6 passes or overnight, tried in different configurations, even taking some out systematically. I would consult our Hardware forum experts on this directly.

gregrocker said:

Windows Update will deliver many updates including Net Framework 4.0 and it's updates before delivering SP1. Just go with what it gives you.

Thats what I have been doing ; and I have 94 updates installed. I dont seem to have Net Framework : The.NET Framework 4 is available on Windows Update

gregrocker said:

...making sure to install the drivers delivered in optional Windows Updates promptly - in fact you can trust all optional WUD's. .

I think thats generral true. In one case for me, there is an optional upadate from a Realtex NIC driver whick renderws my NIC useless, so I now know not to downlaod that specific optional one.

gregrocker said:

. think it's good to leave it out until the updates are all installed.

[Re SP1] OK.. Will leave it alone and perhaps it will be offered up eventually.

gregrocker said:

I wouldn't rule out the excess RAM causing it....

Ya, me too. I am going to search the Dell forums as well to see if excess ram has come up. I can certainly put back 6GB and save the Kingston 12GB set for a future machine ( that will accept DDR3 SDRAM at 1333Mhhz)

Based on the history below, things do seem to point to execess memory

OEM HD + OEM DVD + FULL MEM = INSTALL SUCCESS BUT BUT CHKDSK ISSUES ON UPDATES
OEM HD + SYS RECOVER DVD +FULL MEM = INSTALL sucess BUT FAILS ON UPDATES
NEW HD + OEM DVD + FULL MEM = FAILS TO INSTALL
NEW HD + ULTRA ISO USB INSTALL + FULL MEM = FAILS TO START INSTALL
NEW HD + IMGBURN/UNIV USB INSTALL + FULL MEM = FAILS TO COMPLETE INSTALL
NEW HD + IMGBURN/UNIV USB INSTALL + 2GB RAM = INSTALL SUCCES INCL 94 WINDOWS UPDATES
-----
-----
Troubleshhoting Not tried (now not ncessary):
NEW HD + OEM DVD + 2GB MEM
NEW HD + SYS RECOVERY DVDS + 2GB MEM

NEXT STEPS
I will reseat remaining memory to either 6, 12 or 18GB levels and run some test on it as well

I will also test that Hitachi dirve if I can get the Ftiness test to recognize it ( maybe it will now), and if it fails, I will try to process a Dell warranty option claim for it. It if passes, fine , I pull put in 'stock'

STATUS
It would apprear I am back on track, (assuming my remaining Windwos update kick in and that CHKSDK cyckes does not return - if it does I will turn that 'feature' off per info in this thread. So I am hopefully will be on my way , I hope with without any future excitement.

THANK YOU
I want to sincerely thank you, and the other forum members who assisted, for the technical support, moral support and patience you have shown me here, getting things to a logcal conclusions A thousand thanks for sticking this out with me and giving me options I would have otherwise not tried. This was a long ordeal - I am certainly older now, but wiser now as well. Sincerely appreciate the effort extended.