physical dump of memory at boot

I started up my computer (xp) this morning, and after the XP title screen, a blue screen containing "physical dump of memory" and involving a file in "system32" (don't know which one) flashed for a second, and my computer restarted. It won't get past this blue screen, and the computer keeps restarting. Is there any way to bypass this other than re-formatting? It does this in safe mode and in normal startup. Any ideas?

 

Are you using SP2?

At advanced startup options, disable automatic restart.

We need to know what the error is to give effective advice.

The info you provided is too vague.

 

Seeing as you have XP, you may have a few options.

If it starts in Safe Mode, you could try System Restore, or System File Checker.

Reboot, press F8 repeatedly, and select "Last Known Good Configuration" may be another option.

You could also try a repair and use the Recovery Console.

If you have XP Pro, then you can use Automated System Recovery. (Not an option on Home version)

 

nope

 

Poster already said it doesn't boot into Safe Mode.

System File Checker does not function in Safe Mode.

If its a registry hive corruption, that will destroy the OS.

Only if an ASR backup was created and even then, it will destroy any data that was created from that point on.

 

Nope? Nope what!.. we can't help you until you answer all the questions asked.

 

Well, lets assume the worst then.
Try this:

http://support.microsoft.com/?kbid=307545

If it doesn't work, reverse the steps and try the repair that Insomniac suggested.

But try the registry replacement first.

 

it won't let me use "last good configuration" or safe mode. Only only can access my BIOS or to run my windows CD. I don't have Pro.

 

does it make a difference when it's OEM installed operating system (which is what I have)

 

I can't provide more info as the screen "critical error" screen only pops up for less than a second before the machine re-boots.

What would cause a problem like this? Driver installations? How can I avoid this from happening? I'm at work now, and will attempt all your suggestions tonight. Thank you.

 

Yes.


If thats a real XP CD, the only difference is when you go to copy the system hive backup from C:\windows\repair, it is named system.bak.

So, you have to not only copy that file, but rename it 'system'.

 

So what, if it fixes it, that is hardly an issue!

That cannot be used for OEM-installed operating system, and the Recovery Console should be tried first anyway.


cderaaf, what is the exact error message so you can get an exact answer?

 

Eh, it requires an ASR backup. Do you even know how to make one?

Secondly, the poster doesn't have pro.

Where exactly do you think that article takes you?

-The Recovery Console.

I've used it so far on every OEM system imagineable.

It most certainly can be used on OEM systems.

Pray tell, what exactly would stop an OEM user from being able to use that article other than the changes I already mentioned?

Poster already said they cannot.

 

I do as a matter of fact, not that that matters.

That's why I said "If you have XP Pro"! Notice the word "If" that I used?

How was I supposed to know that?

I'm on slow dial-up, and to quote and post, as well as having other pages open means I'm sometimes a few minutes behind. BIG DEAL!!!

I don't have the luxury of DSL and being able to refresh pages.

Taken from your link:

"Warning Do not use the procedure that is described in this article if your computer has an OEM-installed operating system."

You should at least read the links you use instead of just using Google.

Let me guess, you are right and MicroSoft is wrong (Again).

Anyway, I'm going to bed.


cderaaf, good luck and post back with your progress.

 

That settles it.

Insomniac is right, I am wrong. Best not follow my advice.

Look at the time, I got to get going.

My job working with Windows XP customers for MS is not forgiving when it comes to being late.