just installed a new mobo/RAM and because god hates me, it doesnt work.
after the bios, right before the windows logo is supposed to appear, it says "windows error blah 0xc00000e9 registry files are fucked up"
the strange part is - the first time i booted it up, it worked flawlessly until it crashed after a few minutes, then the error continued to happen.
things i have tried: messing with the bios, unplugging all usb devices, unplugging and plugging harddrive (apparently, the HD is the problem)
i dont have a windows vista x32 boot cd, so i cant boot from disk.
please dont reccomend i get a new HD/reformat, i dont want to lose everything i have.
please help :(
Well it's not too surprising it doesn't work, installing a new mobo generally requires a new windows install.
I know this has been said before.
Reinstall windows.
Do a checkdisk with a windows recovery cd before you reinstall windows.
srsly it works.
[QUOTE=Nilrus;26426476]Do a checkdisk with a windows recovery cd before you reinstall windows.
srsly it works.[/QUOTE]
Or just reinstall windows right away because he has the wrong drivers for his new hardware.
i dont have a windows install cdddddddddddddddddddddd
[QUOTE=skynrdfan2;26434051]i dont have a windows install cdddddddddddddddddddddd[/QUOTE]
then you're fuckeddddddddddddddddddddddddddd
Go buy a copy.
If you replace your motherboard, ALWAYS resinstall windows. Always.
Windows dedicates itself to the chipset of your motherboard. If you install a diffrent one, it goes berserk and crashes.
after 2 days i finally got this shit fixed.
yes, 2 days, dont judge me, it was a learning experience.
[QUOTE=Drumdevil;26439354]If you replace your motherboard, ALWAYS resinstall windows. Always.
Windows dedicates itself to the chipset of your motherboard. If you install a diffrent one, it goes berserk and crashes.[/QUOTE]
Not always, I've had several successful experiences of transplanting hard drives to other PCs, and in a few of the cases where it didn't work it was easily solvable with a recovery CD, no need to format.
Sorry, you need to Log In to post a reply to this thread.