Another Win 2000 Issue - Blue Screen

[Guest Nate]

Anyone,

 

Just when things started to go smooth once again, another encounter.

Windows 2000 at boot, POST okay, Win2K Welcome Screen Loading, then there it

is, Blue Screen. Error message saying, "A driver has corrupted the memory

management system ptes." I've tried Last Known Good, Safe Mode, and still

the quoted error message keeps happening after booting up. Has anyone

experienced this? Does anyone know how to resolve this problem?

 

Thanks,

Nate

[Guest philo]

Re: Another Win 2000 Issue - Blue Screen

 

 

"Nate" <n810s_email@hotmail.com> wrote in message

news:e0$UV8o6HHA.3940@TK2MSFTNGP05.phx.gbl...

> Anyone,

>

> Just when things started to go smooth once again, another encounter.

> Windows 2000 at boot, POST okay, Win2K Welcome Screen Loading, then there

it

> is, Blue Screen. Error message saying, "A driver has corrupted the memory

> management system ptes." I've tried Last Known Good, Safe Mode, and still

> the quoted error message keeps happening after booting up. Has anyone

> experienced this? Does anyone know how to resolve this problem?

>

> Thanks,

> Nate

>

>

 

 

Try a repair installtion

 

Google for help if you need it

[Guest Nate]

Re: Another Win 2000 Issue - Blue Screen

 

Anyone,

 

Have any other ideas? A repair installation did not work. Last Known Good

didn't work. Safe Mode didn't work. I've been up and down Google & Yahoo,

and still no solution found.

 

"Nate" <n810s_email@hotmail.com> wrote in message

news:e0$UV8o6HHA.3940@TK2MSFTNGP05.phx.gbl...

> Anyone,

>

> Just when things started to go smooth once again, another encounter.

> Windows 2000 at boot, POST okay, Win2K Welcome Screen Loading, then there

> it

> is, Blue Screen. Error message saying, "A driver has corrupted the memory

> management system ptes." I've tried Last Known Good, Safe Mode, and still

> the quoted error message keeps happening after booting up. Has anyone

> experienced this? Does anyone know how to resolve this problem?

>

> Thanks,

> Nate

>

>