MB swap with a problem now

blackhawk · Post by **blackhawk** » Sat May 08, 2004 6:48 pm

Swapped out my kt400 mb for an nf2 one, both epox. Deleted the via stuff on the old hard drive, did the swap and powered up.

Some immediate issues with files etc and unable to run the 2800XP at default speeds with two sticks of crucial 2700(different pcb sticks) causing freezes and blue screens.

Problem I'm having now on bootup still is when logging on, I get a box saying

Generic Host Processes for Win32 Services has encountered an problem and needs to close, we will generate and error report...........................

Then when I cancel that, I get a window for

Windows File Protection

Files that are required to run windows properly have been replaced with unrecognized versions, please insert winXP sp1 disk and click..........

when I insert my disk, it doesn't see it nor does it see my standalone winXP service pack, after this I usually get the blue screen when I exit the update box.

Any ideas?

I ran spybot, adaware and tried to do a virus scan(its up to date) but unable to complete anything.

I have a hauppage pvr250 on it that doesn't load up right now since the swap.

If I cant sort this out, I can just reinstall the whole OS but I just re activated it over the phone today when I thought it was OK.

Some google hits for virii last year affecting generic host services but that usually is online.

b-man1 · Post by **b-man1** » Sat May 08, 2004 7:00 pm

did you try running a repair install of XP? that won't trash any existing programs...just critical system files, etc.

CaterpillarAssassin · Post by **CaterpillarAssassin** » Sat May 08, 2004 7:47 pm

Try first doing a "refresh" of XP or also called a repair installation. This will just replace critical system files. Also you can try putting in some known good ram, or try reseating the stuff you already have. Try setting BIOS settings to default. If all else fails try doing a clean install of XP. There is a way to save you activation data. But I dont remmber how. You have to copy a certain file to the system32 folder of windows. FP mentioned it in a previous thread. Let me try to find it. Meanwhile, get usy with these other suggestions!

blackhawk · Post by **blackhawk** » Sat May 08, 2004 8:02 pm

I did try the install to do the hard drive check disk but not the repair. I hate trying to find all my short cuts etc on a repair but may try it tomorrow, then the fresh install. Already spent 12 hours on it and the other computer that got that mb. The ram is good, it ran in the kt400 but of course not in dual mode. I put the two sticks in non dual mode right now.

My daughters computer, that got the old epox is running great on a fresh install and I can recover some of her stuff off the hard drive I ghosted.

Was hoping to 'test' the ability above stock on the setups by now

After all this is done have to pick linux off this system.

Post by **FlyingPenguin** » Sat May 08, 2004 8:58 pm

You HAVE TO do a repair when you change mobos. No getting around it. You will not have a stable system otherwise. Only time you can avoid this is if you change to a mobo with the same chipset.

You won't lose any shortcuts or programs. What it will do is change all the drivers back to generic (you'll need to install the updated drivers again later) and reset you back to the version of XP that is on the CD you use (I would recommend you use an XP SP1 CD to do the repair - if you have one - to save you the trouble of installing SP1 later). You'll also need to re-install all the critical updates.

Make damn sure you have the firewall on before connecting to the internet for the updates or you'll immediately get infected with MSBlaster and Sasser viruses.

blackhawk · Post by **blackhawk** » Sun May 09, 2004 5:34 am

So I escalated to doing the repair but it loads about 90% of the files then stops with a "corrupt file" try again box! Tried 3 times, different drives and down to one stick of ram and the barton running at 100fsb but no go.

Even tried another XP disk for my daughter's computer, same thing.

Next I escalated to full install with quick format, wont load again, tried full format, wont complete the format, says disk problems! 200gb seagate only a month old with an ntfs and a small fat32 partition for saves.
I guess I could try a dos format but cant pin down the problem to one area. Power supply is an antec 380w and it runs through a ups. )*

Willing to buy another mb or hd after work today but dont know where the problem lies.

Post by **FlyingPenguin** » Sun May 09, 2004 8:03 am

Eliminate the hard drive as the problem. Download Seagate's drive diagnostic from their web site and run the full factory certification test. I've certainly seen my fair share of bad drives new in the box.

It might also be a bad ribbon or controller. If the drive fails on the new mobo try it in another system. It's best to rplace ribbons when you upgrade a mobo. Old ribbons get brittle.

CaterpillarAssassin · Sun May 09, 2004 10:52 am

How hot is it in the room your working in? I know that I was working on a compaq a few weeks ago and had almost the same problem. Waited a day and it cooled down in the room and it worked fine.

If its normal temp I would say FP has you on the right track.

But I am willing to bet it is the controller on the new MB or the ribbon simply because you had this drive working with a different board. I would first try it in another machine.

blackhawk · Post by **blackhawk** » Sun May 09, 2004 7:06 pm

rooms cool, basement with good cooling, tried a different hd with cable and connector, same problem!

also tried single rams in different slots

blue screens are inconsistent in error and occurrance, sometimes freezes and boot screen scrolls rapidly

looking like the mb to me, got used off the boards(AT) so contacted the seller

also tried different vid card with same results, initial boot screen scrolls rapidly before going into start of XP load but generally freezes or blue screens quickly

seller willing to take back to test

I may try another psu although this antec is my newest and specs look good in bios