Saved Bookmarks
| 1. |
Solve : Computer keeps getting blue screen errors when reinstalling Windows XP.? |
|
Answer» ONE of my spare computers has been having PROBLEMS lately. I usually leave it running right next to me and I noticed that it would randomly restart, get BSOD's, and even sometimes it would give an error that Windows Explorer had to be shut down. I immediately diagnosed it as some kind of software problem and decided to reinstall Windows on it(since it had nothing on it and I didn't really want to fix Windows). But now every time I try to install Windows it crashes. It seems to occur 3 or 4 minutes after I input the network settings. Here's part of the blue screen error it gave: If you can't read it says: ***STOP: 0X0000001A (0X0004128B, 0X09185201, 0X00000000, 0XC0883000) Also, I have also gotten an error that said: ***STOP: 0x0000007F (I think all these sequences were 0X00000000 4 times. ) Anyway, I'm thinking it's a RAM problem I've got here. I did check both RAM cards and reseated them after I got the 0x0000007F error, and after reseating them is when I got the 0x0000001A error. Any help? Try one stick of ram at a time and see what happensI've seen this kind of error a number of times. It is either the RAM, the cache on the MOTHERBOARD or the harddisk. You need to eliminate the RAM first, then the Harddisk. If both turn up clean, it's time for a new mobo. 1) To check the RAM... > Use a single stick from your set, then run any ram stress tester program for 24 hours. If you don't get any crashes, it's your memory, replace the sticks. If you still get a crash, try another stick until you've tried all the sticks you have. If they all crash, it's unlikely to be the ram. On to step two. 2) The harddisk is the next thing to check. The only decent way to check it is to simply swap it with another computer that has windows installed. Windows will automatically detect all the hardware and allow you a few days of free time (if it asks to validate). Leave the PC running for a few days, see if you get any crashes. If you don't have another disk to try, try running a full SECTOR scan, it may turn up bad sectors but it's not a conclusive test. Working? Replace Disk. Still crashing? Step three. 3) Sadly, this usually means the problem is the motherboard cache. The error is caused by corruption in the registry and if you've already eliminated the ram and the disk, it has to be the board. Theres no easy fix here, you'll have to sack the board and get a new one . Cleaned up some irrelevant posts.Thanks guys. I found out that one of the RAM slots was the problem. So, after shifting my RAM around it's all working fine. |
|
