STOP error

**amyb** · April 29th, 2009, 09:05 AM

When trying to login, the error “The instruction at 0x7c90c..memory cannot be written. Click ok to terminate (which shuts down the computer) or hit Cancel to debug. This brings the BSOD and the error STOP c00021A appears. I selected “last known configuration” which doesn’t help. For now, the user can log in if he doesn’t select the options to the first error message. Would doing a repair installation help?

**CCT** · April 29th, 2009, 09:33 AM

I'd be more inclined to boot into Safe Mode, run msconfig, uncjeck everything in Startup and every non-Windows service in Services, then try a normal boot.

If that succeeds, then start restoring a few of each and rebooting to detect which is causing the problem.

Or, analyze the dump files.

**amyb** · April 29th, 2009, 09:37 AM

the password to get into safe mode doesn't work...

**CCT** · April 29th, 2009, 10:13 AM

Then, boot into Normal Mode, run msconfig, uncheck everything in Startup and every non-Windows service in Services, then try a normal boot.

ps: I have never heard of a password for Safe Mode - something learned every day.

**amyb** · April 29th, 2009, 10:16 AM

I know..I was shocked too (re:safemode pw)

**CCT** · April 29th, 2009, 10:21 AM

http://www.wikihow.com/Password-Prot...-in-Windows-XP

http://support.microsoft.com/kb/321305

Doesn't do much good when people forget them!

**amyb** · April 29th, 2009, 10:23 AM

thank you

**slgrieb** · April 29th, 2009, 11:22 AM

I must sound like a broken record, anymore, but... there are bits of malware that will change both the user and administrative passwords, and you are getting a memory error, so I'd think about scanning the drive connected to another computer running the malware tools of you choice before you do anything else.

In so far as resetting the password goes, there are many, many ways to do it. Doing a repair installation with the SHIFT-F10 method is one. The only caveat is that I've had some of the reset tools fail when the password change actually is malware related.

**NooNoo** · April 30th, 2009, 03:18 AM

I had this the other day, there was a fibre trapped in the ram...

A similar problem was malware related - malwarebot I think was the culprit... but last known good config worked to get me in and remove it.

If ram isn't the problem, boot with a live cd and go on a search destroy misson, or pull the drive and scan it in another machine.

**slgrieb** · April 30th, 2009, 08:23 AM

Originally Posted by NooNoo

I had this the other day, there was a fibre trapped in the ram...

A bit of wool, perhaps?

**Platypus** · April 30th, 2009, 08:29 AM

Ram... wool...

Groan!

**slgrieb** · April 30th, 2009, 03:05 PM

It behooves me to ask the question: "Is there no pun so baaaad I don't enjoy it?" I guess I'd sheepishly have to admit that the answer is "Naaaah!"

**Platypus** · April 30th, 2009, 05:37 PM

No buts about it, that's a flock of bad buns! You have maaaa'd skilz!

(Sorry amyb, no more punning thread hijacks from me...

)

**slgrieb** · April 30th, 2009, 06:09 PM

Originally Posted by Platypus

No buts about it, that's a flock of bad buns! You have maaaa'd skilz!

(Sorry amyb, no more punning thread hijacks from me...

)

I'm surprised forum members aren't flocking to this thread with their posts. What's the matter? Are you all woolly-headed and fresh out of ideas?

AmyB. You can help end the madness. Just mark the thread as "solved" or post a response so we can give you some help that might be more ewesful. Don't let the mutton heads drive you off. I've herd your pain and want to help resolve this just out of shear good will.