Windows XP: Reinstalled Windows XP, but I'm still getting BSODs and other troubles?!
- 8/14/09 11:40 AM
Check the RAM
by jjbrain - 8/15/09 12:40 AM In reply to: Reinstalled Windows XP, but I'm still getting BSODs by theonly1moonerAwhile back I started experiencing the dreaded BSOD, random crashes, and my screen image was flickering. I thought that I had picked up some sort of virus from hell. I tried running my security software and it came up clean. I tried a "system restore" and I could not get it to work. The situation was going from bad to worse and the panic I felt was overwhelming. I finally broke down and took my computer to Firedog (the late Circuit City's tech people) and a very nice young man checked my computer using a diagnostic software CD. The result? I had a bad stick of RAM. I had not even considered that I might have a hardware problem so I was surprised. Once the RAM was replaced my computer began to behave normally. I was now ready to format my hard drive and reinstall Windows but the tech at Firedog told me to try the system restore and to have patience because I might have to perform more than one system restore. It took three "system restores" and reinstalling several of my programs but eventually everything was back up and running and best of all XP had survived. I paid about $50.00 to have my computer diagnosed and it was money well spent. The tech replaced the RAM for me and with his advice I was able to do the rest. This experience made me realize that there are times when paying someone else figure out what is actually wrong with my computer is worth the cost.
Why would you reinstall first?
by pj-mckay - 8/15/09 2:29 AM In reply to: Reinstalled Windows XP, but I'm still getting BSODs by theonly1moonerYou've now lost all your settings, history, and quite possibly a lot of personal stuff. Without some analysis you're potentially just wasting your time too.
There is NO magic cure for BSOD. You MUST note the error code given as that explains EXACTLY what has occurred and should always be your starting point. As you've wiped the disk effectively, and wiped your software I'd say you can forget software problems. If it won't boot, I'd reduce your hardware by removing extra boards and run from 1 memory if you have the option. Also reset your BIOS to default and reboot. If it does boot, go to eventvwr and find an entry for the bsod event (most likely will be something logged) then google the code. Ther is NO point in progressing without analysing the error code... thats it's one purpose in life; to make problems easier to resolve.
You also need to consider running some diagnostics so consider downloading a memory checker etc. If you need to use professional services I would say the cost is potentially not worth the benefits, and consider putting the money towards a new PC. Might sound harsh but you could pay a large sum for little long term benefit.
re: BSOD
by ascii_pv - 8/8/09 8:51 AM In reply to: Reinstalled Windows XP, but I'm still getting BSODs and other troubles?! by Lee Koo (ADMIN)
by Experience:
1. See your video card, memory card if it is compatible with the motherboard.
2. Check your clock speed, you can do this (sometimes it dont correlate with the memory. Try narrowing down the clock speed, and check it if works.
Have a great day.
asciipv
Increasing BSODs
by Alain Martel1 - 8/8/09 8:52 AM In reply to: Reinstalled Windows XP, but I'm still getting BSODs and other troubles?! by Lee Koo (ADMIN)
First, for the grayed out Hybernate option.
It's a feature that can be turned on and off. In the start pannel, open the Configuration pannel.
Open the Power management, and select the hybernation tab. If the check mark is unmarked, click on it. It the chexk box is grayed out, you don't have enough free disk space. Close by clicking the "OK" button.
Note: you need at least as much free space on the drive where Windows is installed as the amount of RAM present on your system to be able to activate hybernation.
Quick verification:
Your computer may be slightly overheating. make sure that all fans are working properly and that all eat sinks are free of dust.
On Windows 2000, XP and Vista, BSODs are caused most of the time by faulty drivers OR faulty periferals.
I can assume that after you have reinstalled Windows, you also installed the drivers for all your periferals. Don't forget those for the motherboard and the CPU. (yes, there ARE drivers for those)
This leaves the hardware missfunction.
Try to install the most up to date drivers, including those for the motherboard itself and the CPU.
If the situation is cleared, you only had to invest some time.
If that don't improve your cituation, it's time to do some hardware troubleshooting.
Turn off the computer and unplug it.
VERY IMPORTENT!!!
Make sure that you discharge any static electricity by touching the metal of the case.
First, remove the sound card, or dissable it from the BIOS configuration if you have an onboard one.
Disconnect any extra hard drive and CD/DVD exept the one where windows is installed.
Also, remove any extra card and unplug any SCSI, USB or FireWhire device that may be connected. (exept the keyboard and mouse)
Check that your RAM is properly seated. Do the same with your video card.
Sometimes, removing and puting back is all that's needed.
Reconnect and restart the computer.
Does it work beter?
Yes? One of the component you removed is probably faulty, nearing the end of it's life, or had a faulty connection. You must find what component it is and replace it.
Replace your components one at the time, do some tests. It's brobably beter to start with your hard drives, then the CD/DVD. You may need to only reconnect one component per day and use your computer as intencely as possible for several hours.
If you get another BSOD after reconnecting a component, you've found the cause of your problem.
If you find that it's a hard drive that's faulty, it is URGENT that you get a replacement and copy ALL the content to the new drive, whipe out the old one and discard it.
If it's a problem with a drive, you may already have lost some datas.
No?
It's serious.
The possibilities are:
- The MAIN hard drive, the one where Windows is installed, is dying. Get a new one and reinstall.
- Your video card is dying. Try swaping it with another one. It can be an old PCI card or any one that you can install. Get a new video card.
- Your motherboard or the bios is about to die. You must change the motherboard. You'll also need to change the CPU as your current one won't fit on the new borad.
- Your CPU is failing. Need to change the CPU. It's very unprobable that you can find a new one that you can install on your current motherboard, so you'll need to change it as well.
If you need to change the motherboard/CPU, you'll also need to reinstall Windows.
Wipe - Reformatting is reshuffling chairs on the Titanic
by HomelessClarence - 8/8/09 8:54 AM In reply to: Reinstalled Windows XP, but I'm still getting BSODs and other troubles?! by Lee Koo (ADMIN)
The 3 most popular reasons for this is; Number 1. Reformatting a drive is like reshuffling chairs on the Titanic. Nothing really "disappears" but is merely re-tagged. When you re-install, the Installer "sees" the resident files and will either write-over them OR (in your case) will try to re-use them. If you've been diligent in Updating, these files look strange to your Installer since the registry is altered when you Update ... hence the BSOD or otherwise. Try wiping the drive and then Re-install. Number 2. The copy of Windows you are Re-Installing is corrupted. I've had this problem when I've left the Installer Disk on top of the Microwave waiting for my coffee to reheat. (I don't do this anymore.) I don't have an Office with a window (... sigh ...) but my boss has left disks on his desk where the sun beats down on it and ruined a few that way. Also, consider that your Original Hard Drive might be having a problem, which leads to Number 3. Number 3. Often there are "hardware" issues. I classify them as hardware issues, but it can be because of viruses (esp. boot and BIOS viruses) are residing in your computer. Sometimes, the Original drive might have a bad sector(s) and not write the files correctly there. Other times, a hardware change, like the BIOS chip, or if you've updated the BIOS, will not allow the Installer to recognize it (Or vice-versa). Remember that computers are not perfect and get age imperfections (like people). I hope these ideas help. If all else fails, Windows 7 is coming.
huh?
by porsche10x - 8/15/09 6:48 AM In reply to: Wipe - Reformatting is reshuffling chairs on the Titanic by HomelessClarenceWhat are you talking about? Reformatting most definitely completely deletes the contents of your harddrive. The installer doesn't "see" residual copies of old files after a reformat. Yes, it's true that formatting doesn't actually erase the contents of the drive by writing 0's or 1's into every bit, but that's irrelevant. You can't actually see the old files without special software, etc. Maybe you're thinking about doing a "repair" installation WITHOUT reformatting first?
Except for hardware issues I disagree
by BigGuns149 - 8/15/09 1:26 PM In reply to: Wipe - Reformatting is reshuffling chairs on the Titanic by HomelessClarenceWhile I have seen quite a few people with hardware issues causing BSODs I disagree with most of the rest of your post. Typically speaking provided one is using real legit OEM media that has clearly been damaged as opposed to some random pirated copy from a dubious source the media usually isn't at fault for bad installs.
If one really formats the drive than there is no reason that it would "reuse" any resident files because as far as the installer is concerned the HDD is empty. Sure, there are data recovery firms that can in some cases recover files that were formatted, but the installer will see an empty drive and will copy the known good versions of all the system files to the HDD.
BSOD
by taschan - 8/8/09 10:00 AM In reply to: Reinstalled Windows XP, but I'm still getting BSODs and other troubles?! by Lee Koo (ADMIN)
I have Vista and kept getting the BSOD. I ran AVS( from my computer and online versions). Sometimes it would make it through and other times it would become BSOD. I finally tried in a desperate attempt, a suggestion by my Tech guy to change the RAM. Even though it is extremely rare for RAM to go bad, mine apparently did. I have not seen the BSOD of death since then.
Quite possibly could be defective RAM MODULES.
by Brawly44 - 8/8/09 10:44 AM In reply to: Reinstalled Windows XP, but I'm still getting BSODs and other troubles?! by Lee Koo (ADMIN)
From what you describe, it appears to be a hardware related issue. In most cases this type of problem can be difficult to isolate, but with a little time and patience it can be resolved.
In my experience, this appears to be an issue with your ram modules. But lets touch quickly on the other 2 "might be" issues. An over-heating cpu or a bad power supply can cause havoc with your PC. In order to check your cpu (central processing unit), open the side of your computer case (always remove main power & ground yourself before handling the hardware inside your computer) and check to see if the cooling fan over the cpu is clean and free of dust and dirt, if not take steps to thoroughly clean this area, as a matter of fact, if the entire enclosure is dirty, take the time to clean all of it. A small vacuum is best for this type of cleanup, but the purchase of a can of air is helpful as well, if used very carefully. Once clean, check to see if the cooling fan is performing correctly. If the fan is performing poorly, or not at all; it is likely your cpu is overheating causing your problems.
Regarding the PSU (power supply unit), this can be tricky. Unless you have the skills of an electrician, and are quite adept with a voltmeter, your best bet is to switch out the PSU with another of equal voltage and attempt to boot your system with the replacement PSU to see if the problem goes away. The PSU is the one component most overlooked when dealing with these problems, and a PSU that is failing can cause detrimental issues with your PC.
Lastly, I suspect the problem is being caused by your ram modules. You did not indicate the age of your system, but this procedure is fairly standard across the board. If you have multiple ram modules (2 or more), power off your system and remove the main power cord from the PSU. Make sure you are well grounded before handling components in your system. Examine your ram modules and you will note on either end, a finger lever that if pushed will release either end of your ram module from the slots on the motherboard. After disengaging these levers the ram can be easily removed. If you have multiple modules, remove one and leave in the other (the idea is to test each module one-at-a-time). Re-attach your power, and boot the system back up, check to see if you continue to have problems. If so, replace the ram module with the other you removed and repeat the process. This procedure will help you to isolate which of the modules is faulty.
Lastly, there is a great utility that will test your ram modules to see if errors are being generated. It is called "MEMTEST86". The link is http://www.memtest.org. If you have a floppy drive, thumb drive, or CD/DVD drive, the site offers a download application for either medium. Use this application to test each module. If the ram is faulty this will definitely detect it. However, you will have to run Memtest for a few hours to get a full result. I hope this was helpful. The honest truth is that hardware issues are tedious and time consuming when trying to isolate. So much so, some PC users will opt to purchase a whole new PC rather than put themselves through the necessary time to fix the issue, that is if it is fixable. But if minimizing expense is a priority, take a little bit of time; maybe a weekend, to see if you can correct the problem.
Worth reading again...
by jakenewbie - 8/18/09 12:36 AM In reply to: Quite possibly could be defective RAM MODULES. by Brawly44Amidst all of this great advice, this might just be the best. Do yourself a favor and re-read it; then get to work...
Again, what does mem have to do with hib/sleep/suspend?
by Forgotten One - 8/18/09 3:02 PM In reply to: Worth reading again... by jakenewbieFor general BsoD tips, yes, but not this specific issue.
Good lord, 2/3 of this thread is the same posts and has nothing to do with the issue at hand.
READ THE ISSUE. IT IS NOT A GENERAL BsoD, IT IS CAUSED BY A SPECIFIC SYSTEM EVENT.
It's a BsoD caused by not being able to go in a hibernate/suspend/sleep/power down state. That has NOTHING to do with memory. If the memory is bad or questionable, it would be causing BsoD's in NORMAL OPERATION.
R-E-A-D
Again, click my username, and find the post I made on page 10/11 (probably on page 11 now). It's the REALLY BIG ONE THAT ELABORATELY EXPLAINS THE PROPER SOLUTIONS.
Last time I am mentioning this, go ahead and keep posting the same posts, with the same "solution" and watch the issue still be existant.
*sigh*
BSOD
by b_crystal - 8/8/09 10:46 AM In reply to: Reinstalled Windows XP, but I'm still getting BSODs and other troubles?! by Lee Koo (ADMIN)
Do a diagnostic on the hard drive, system ram and motherboard. Any of them could be giving random errors such as this.
Reinstalled Windows XP, but I'm still getting BSODs
by thomhart - 8/8/09 11:54 AM In reply to: Reinstalled Windows XP, but I'm still getting BSODs and other troubles?! by Lee Koo (ADMIN)
I would make sure that:
1. The motherboard battery is good, or just replace it, they are cheap. It may be powering the board in hibernate when it checks for keystrokes.
2. The CMOS is upgraded, or the current version complies with the current version of XP you are installing. The motherboard might be using legacy DLL's for an old BIOS that may not work with the version you are installing (it may not have the legacy DLL's that you started with). This more likely if your motherboard is older or has a non-standard BIOS.
3. You don't have some other software controlling those features. The only two I can think of right now would be RAID controller software that has power management built in, or if you have a UPS attached to your system and use monitoring software. Maybe a video card, though that seems wierd to me, but I have seen wierder.
Hope that helps.
Problems for windows xp
by Deba_Jyoti - 8/8/09 11:59 AM In reply to: Reinstalled Windows XP, but I'm still getting BSODs and other troubles?! by Lee Koo (ADMIN)
1. Boot from the Windows XP cd, go for a complete install after formatting the hard disk in NTFS partition (in full)
2. If still the problem persists, one of the RAM module might have said GOOOD Bye!!
Blue screens
by gramaticus - 8/8/09 12:01 PM In reply to: Reinstalled Windows XP, but I'm still getting BSODs and other troubles?! by Lee Koo (ADMIN)
Hello Bob T.
Have you installed all the latest updates from Microsoft ?
One of the causes of blue screens in my experience is a failure to (re) install all the appropriate updates and Service Packs
All the best
Paul
| Forum legend: | |
 |
Locked thread |
 |
Moderator |
 |
CNET staff |
 |
Samsung staff |
 |
Norton Authorized Support team |
 |
AVG staff |
 |
Windows Outreach team |
 |
Dell staff |
 |
Intel staff |
