shawshanked me
Windows XP service pack 3 shawshanked me!
has this happened to anyone else?
winlogon.exe— Shell32.dll not valid.
I have tried everything, f8 and every possible option in there, and can’t get the old puppy to load up again, just shows the two errors (bad image) lasass.exe
and then virtual memory this and that and…shut down…
I can’t do a system restore cause I don’t have XP disk, I tried going back to previous time it loaded successfully, and it does nothing.
I’m thinkin’ my virtual memory card finally kicked the bucket, it had been acting weird and I kept getting “out of virtual memory” messages on a 512mg card.
I have seen so many error reports on the net about SP3 I should have read them before I clicked install…none of them are helpful tho, they all say to insert the XP disk as a solution.
Bubba, I read about your highway adventure and feel your pain.
keep shinin
jerm 
Tried booting to safe mode and running chkdsk?
Quote: (Bubbagump @ Mar. 23 2009, 4:03 PM)
Tried booting to safe mode and running chkdsk?
Yes I have, it goes to load in safe mode the same two errors come up, then the virtual memory pop up, SHUT DOWN!
It's like a shut down loop!
As I said I tried every option under F8, and nothing, just to error reports and shut down.
Since I told it to go back to the last successful boot up and it still crashed me tinks it is the virtual memory that took a crapper.
IT had all the signs, it was getting bad, when I used to open up Mozilla all my tabs would be dead, the back buttons didn't work, no URLS stayed in the browser.....
I might take the drive out and slave it into another machine.....cause I need some of the files off it.....
The other machine has more memory, so I am hoping I can get past the two .dll errors and it will boot up the drive.
OR I may try and get the dll files back into it, but don't really know how to do that without loading Windows.....
Service Pack 3, just say no!
keep shinin
jerm
I have SP3 on everything… at home and work. Nary a problem. You sure you haven’t picked up viri Jerm?
D
Quote: (Diogesneez @ Mar. 23 2009, 5:10 PM)
I have SP3 on everything... at home and work. Nary a problem. You sure you haven't picked up viri Jerm?
D
I have had AVG running since I got the machine, and it has nar missed a beat.
Like I said my virtual memory kept prompting, leading me to believe it was on the way out, then I installed SP3 and it was the straw that broke the camels back.
Me tinks SP3 requires a bit more RAM to load, I have seen those Dll errors before and windows or AVG usually fixes them, but alas der just taint enough memory to get over the hurdle anymore.
I even told the computer to ignore the errors at start up. (in F8)
I won't know until I either install the drive into a different system or get another stick o' memory.
keep shinin
jerm
I guess a bad memory chip would keep critical system files from loading and keep you from being able to boot. You just have 512M on the machine? I don’t know about ‘virtual memory’ but a memory chip failure might give some error message like that. Virtual memeory is ‘hard disk memory’ - What kind of shape is your hard disk in?
Quote: (sevenOfeleven @ Mar. 23 2009, 6:17 PM)
I guess a bad memory chip would keep critical system files from loading and keep you from being able to boot. You just have 512M on the machine? I don't know about 'virtual memory' but a memory chip failure might give some error message like that. Virtual memeory is 'hard disk memory' - What kind of shape is your hard disk in?
Not to good.
IT was getting loud and like said that virtual memory low prompt was coming up frequently in the last few weeks....
Yeah only 512 DDR I think....but there are only 2 slots on the board to begin with.
I have another maxtor drive I slaved to the one I am having problems with but it wouldn't load either (it has XP as well) a blue screen comes up on that one, but it goes by so quick I can't see what the error is.
I saw a fix to this Dll file online and wrote it down, but for the life of me I cannot remember how to get to the command prompt screen to put it in C:\(long line of instructions here)...
I tried to start in safe mode with the command prompt but all the commands just flew by and I couldn't get them to stop, or it to stop so I could put one in....
On an old WIN98 system I used to be able to Yes or no those things...
I thought I used to press control alt C to get to the C:\ command prompt...but it has been years
keep shinin
jerm
Let me guess, your system is AMD based? Is it an HP machine? Is it a laptop? If it’s a laptop you might be able to recover it. If it’s not a laptop you might be stuck with a format. Let me know.
PACO
Quote: (Paco572 @ Mar. 23 2009, 6:58 PM)
Let me guess, your system is AMD based? Is it an HP machine? Is it a laptop?
PACO
No I don't think it is Paco, but I know the error reports are all over the net for SP3 and the AMD.
It is intel4 2.2G and an Asus machine, although a blue HP screen does come up at start up.....it is a desktop.
I have found many solutions to these dll error's even for the intel but as I said cannot remember how to get tot he command prompt (and don't think I ever have had to with XP)
I tried simplifying the system to see if it would help, I took out the wireless mouse and keys, and used hardware ones, I took off the flatscreen and used an old tube...etc etc unplugged all the xtra USB devices....
keep shinin
jerm
Well try hitting ALT+ f10 on boot up. Do you know if the machine has a recovery image. Most Laptops have this built in so when you can’t boot up you can simply recover it. Maybe this machine has one?
From web page I found
"ACER BIOS screen, hold the “Alt†key and press the “F10†key simultaneously to start Acer eRecovery
3. Once eRecovery has loaded, click “Restore to Factory Default Settingsâ€
4. Click “OK†to continue"
Try hitting “f11” on boot as well to see if a recovery console comes up. Try all “f” keys on boot. Well f8 will bring up options, we know this and most laptops f2 brings you to the bios. Check bios as well for recovery console.
PACO
ok THANKS p,
I’m gonna go try that.
I will let you all know how this turns out regardless, perhaps if I find the solution it will benefit another scrawling the web one day,
keep shinin
jerm
I tried that,
holding ALT>F10 doesn’t do anything on this machine.
F10 is one of the prompts on the blue HP screen that says “system restore” next to it, but you need the XP disk to do that.
This Maxtor is formatted FAT32 so I was wondering…if I could slave it off another machine running windows98SE formatted FAT32 as well…
My main objective at this point is to retrieve whatever files I can off it before it takes the final dirt nap.
I though maybe if I can use it as a slave on a more stable system I can solve the problem.
Scan disk was able to run on the last start up and it said there was no problems, do I am hoping the drive is still ok and this is just a registry problem created by the SP3 wipe out of the old ones.
keep shinin
jerm
I noticed microsoft says to disable any virus programs before installing SP3.
It would make sense since that particular dll file (shell32.dll) always comes up in AVG as “fixed”, and now it is the same dll that is not matching the XP diskette, go figure.
AVG was running when SP3 was installing.
Pretty sure I know what caused the problem, just don’t know how to get my machine to the command prompt to fix it and type this in:
C:*reg add HTLM\System\CurrentControlSet\Services\Intelppm/vsart/d4/+REG_DWORD
keep shinin
jerm
Quote: (jeremysdemo @ Mar. 23 2009, 7:47 PM)
I noticed microsoft says to disable any virus programs before installing SP3.
It would make sense since that particular dll file (shell32.dll) always comes up in AVG as "fixed", and now it is the same dll that is not matching the XP diskette, go figure.
AVG was running when SP3 was installing.
Pretty sure I know what caused the problem, just don't know how to get my machine to the command prompt to fix it and type this in:
C:\*reg add HTLM\System\CurrentControlSet\Services\Intelppm/vsart/d4/+REG_DWORD
keep shinin
jerm
Yes they say that but what it really comes down to it, it's HP's image of XP. It's not a true copy and thats why the SP3 causes the "endless boot" factor. You can possibly use another hard drive thats fat 32 but you run the risk of a security block due to new hardware. I would try it. Set the old drive, the one thats failing to slave mode and run the new fat32 as the master and boot from it. Then run chkdsk on the old drive to fix any errors. Then put it back in your system as the master. and try to get to the safe mode. then you can edit the reg
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\intelppm and change the "Start" value from 1 to 4.
That should fix it. It should then boot on it's own.
PACO
THanx again P,
I will try that today, and let ya know.
keep shinin
jerm
Sounds like the hard drive is going to me.
I got the drive to light up on the other system as drive D:
I did try the command you gave above but it says there is no such file inside the drive.
It also says “chkdsk.exe” does not exist.
I’m gonna try and run a registry fixer on it, and possibly reload service pack 2 if need be.
keep shinin
jerm
Quote: (jeremysdemo @ Mar. 24 2009, 9:03 AM)
I got the drive to light up on the other system as drive D:
I did try the command you gave above but it says there is no such file inside the drive.
It also says "chkdsk.exe" does not exist.
I'm gonna try and run a registry fixer on it, and possibly reload service pack 2 if need be.
keep shinin
jerm
If it's windows xp it should be there. It's in the windows/system32 directory
So from the command prompt you would type in, that is if C is the boot drive and D is the bad drive
C:\WINDOWS\system32\chkdsk.exe d: /f (hit enter)
PACO
Perhaps the HD… You aren’t saying anything about POST errors which would point to memory or a bad mobo/processor/other little odd ball thing. I would seriously boot to something that can run chkdsk… either a WinXP install disc and go into the recovery console OR grab a later copy of Knoppix with ntfs-3g built in and use its version of chkdsk. (http://knopper.net/knoppix/index-en.html) This very same issue has popped up on a lot of machine I have run into over the years and it always turns out to be a fubar index or file descriptor on the disk. I would not bother with a registry repair at this point.