Link to home
Create AccountLog in
Avatar of atf3doc
atf3doc

asked on

all but one user account corrupted in windows xp

I am working on an HP mini loaded with Windows XP Home SP3. One user account loads fine. The other after "loading personal settings" produces BSOD and immediately reboots so quickly that I can't read the error on the blue screen. I thought ir\t was a corrupted user account...so I created a new user account, but that also produces BSOD and reboot. I tried several new user accounts...all give same results.BSOD and reboot.
I copied data and went to do a repair install of Windows and ran into the next problem...F9,, boot options, shows both internal HDD and USB DVDROM. I select USB and start windows setup, but it tells me it can't find any mass storage device installed even though it saw it at boot selection.
If I can fix the user account I will be happy, but would also like to know why windows ssetup doesn't recognize any HDD. Thanks for any and all suggestions.
ASKER CERTIFIED SOLUTION
Avatar of Ian Pattison
Ian Pattison
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
SOLUTION
Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
SOLUTION
Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
Avatar of atf3doc
atf3doc

ASKER

HP didn't offer F6 drivers; they had other options, such as disabling SATA controller, which isn't shown in this setup menu. I'll cross that bridge later.

After I unchecked Auto Restart, I no longer received BSOD and can log in to all users. I ran Malwarebytes in Safe Mode and it came up with one, PUM.hijack.startmenu.All ws well until I engaged the SD card with pictures on it...back to BSOD. I took it back out and once again no problem logging on to any account. I was getting BSOD even wih it out before unchecking Auto Restart.
atf3doc
SOLUTION
Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
Or it could be a non-virus.  It could be some program X in conjunction with that particular configuration, happens to be misbehaving on your system, causing a BSOD.  Perhaps a program that is triggered whenever you insert an SD media.
Avatar of atf3doc

ASKER

Already have tried the SD card on the non BSOD user...works ok. Will run a root kit scan on the card.
atf3doc
Avatar of atf3doc

ASKER

I can boot into safe mode on the affected user account with no problem. As soon as I go to regular mode, I get Bad_Pool_Header blue screen ....only on the affected user.
Have you investigated what is triggered, what program runs when the SD card is inserted?  Usually the Windows autoplay comes up and gives a list of possible choices.  If that somehow got messed up that could blue screen.  Or, if a user chooses something on the autoplay list and always use this program for this type of media is checked on, (it has a different choice for blank CD versus audio versus pictures verus whatever autoplay decides the content type is) then the chosen program will get triggered always in future for that user for that type of media (such as what is on your SD card for example)

wait, what happened to all the users are affected except one?
Hmm, well when you use a virus anti-malware cleaning tool, if any of the users, lets say user B, have set in Control Panel, Users that their files are private, then the permissions are such that running the Malwarebytes or whatever tool cannot clean user B when logged in as user A.  So maybe something needs to be cleaned still under the affected user.
How long has this been going on?
Sometimes a BAD_POOL_HEADER is corrupt registry.  
Sometimes it is a bad driver and hardware issue.  Did you add any hardware or update or change any drivers recently at around the time of the problem?
If you did, try going to that device in Device Manager and try rolling the driver back.
Another way to solve BAD_POOL_HEADER involves figuring out which pool is bad, which can be quite technical and difficult.  One way is to try to make sure you have the most recent up-do-date BIOS and drivers for your motherboard and hardware devices, but not so recent that it is Beta or has known problems.  Sometimes putting on an updated driver creates a new problem where none existed before.
The old adage "if it ain't broke don't fix it" is kind of a golden rule among IT techs, much like Doctors' "first, do no harm".   However, in this case, it is broken.
Knowing what updates happened can be difficult to know if windows is set to automatically apply critical updates at 3am unattended.  You can go into Windows Updates, and then on the left is a view history so you can see what updates were attempted when, at least the ones through windows update, any hardware or software you added manually wouldn't be on that list.
If you know it has only been doing this for a few days or weeks, you could consider using System Restore to put the system registries back the way it was on a previous system restore checkpoint that are kept up to 30 days back.  User files on the disk are unaffected, but all programs installed, updates, and even anti-virus updates would have to be reapplied after the system restore to a previous point.  Sometimes some nasty viruses discard your checkpoints, so if you haven't any to restore from then be MORE worried.
If you go through the motions of going to do a System Restore, you can see in your checkpoint history, on each date that is bold, a rough description if the system decided to do a checkpoint because some major piece of software or hardware was installed, so you might get a clue as to what might have changed.
SOLUTION
Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
Avatar of atf3doc

ASKER

And now for the rest of the story. When I ran root kit revealer it came up with over 1076 discrepancies. I didn't do anything but close root kit revealer and then I couldn't boot at all, even in safe mode. Since I couldn't get the HDD recognized and HP didn't offer F6 drivers for that ( their only solution was to purchase recovery media) I slipstreamed AHCI drivers into a Windows XP install disk, and behold I could load windows Link to instructions:http://www.howtogeek.com/howto/windows/resolving-setup-did-not-find-any-hard-disk-drives-during-windows-xp-installation/
. After loading all drivers, I formatted the SD card and all worked well.
Avatar of atf3doc

ASKER

All comments were helpful in working toward a solution, but none actually resolved the problem. I included my own as a part of the solution, because that is what ended up reoslving the problem.