Yahoo Answers is shutting down on May 4th, 2021 (Eastern Time) and beginning April 20th, 2021 (Eastern Time) the Yahoo Answers website will be in read-only mode. There will be no changes to other Yahoo properties or services, or your Yahoo account. You can find more information about the Yahoo Answers shutdown and how to download your data on this help page.
Trending News
PC problem (have details)?
when i try to install windows on my old computer, there is always some windows error in mid installation, either he can't copy some random file or just BSOD, but then i installed the windows on my other computer (moved the hard drive there) and installed it and unhooked it right after the installation was completed
Trough system of elimination i have come to this conclusion:
Processor : Can't be the processor since it does boot up all the way to win xp screen and then restarts, same in safe mode
Graphics card : Can't be, i switched it with another and it still dies in boot screen
HDD: can't be, works fine on my other PC
RAM: can't be, unhooked them all and tried 2 sticks, one at the time
Conclusion is WTF MAAAANNN, main components required to run windows are all fine...does anyone have any hint?
2 Answers
- REXSLv 69 years agoFavorite Answer
You left no clue as to what this "old computer" was and only dropped one hint this was XP.
Did you let XP fully install to the hard drive when it was in the other computer? i.e. reboot several times until it loaded all drivers, etc? It may be hung between drivers.
Hints......
....If the computer is older than XP or newer than XP then it may be some nasty hanging driver. Disable onboard NIC, Audio, Modem, what ever you can in the BIOS. This can even happen if the board is made for XP.
....Reboots at an XP startup screen has always been a bad driver for me.
....Could be the motherboard is fried..... old computer could mean its in the era of the "capacitor plague" ----> http://en.wikipedia.org/wiki/Capacitor_plague ..... look at it... see if you see blown caps. A MB with blown caps will flake out all over the place. Or could be someone yanked a part while the comp was plugged into the wall...etc.
......RAM may still be the problem, could be both sticks are bad or someone yanked a stick while the comp was plugged into the wall, frying the ram BUS.
- 9 years ago
I think so that your "Windows has stopped this device because it has reported problems. (Code 43)". Details on Device Manager error codes like Code 43 are available in the your system.
