Blue Screen and Memory Dump result in Constant Restart!

[DAunderpar]

I am running Win 2000 Pro with 64 MB or RAM and each time I start the machine a quick full screen flashes alerting me that physical memory is being dumped - and then the machine restarts. This occurs just after the machine has logged in and before the desktop is even prepared. Also, it happens everytime and the same result occurs in all modes of Safe Mode. I have tried swapping the RAM and also adding more RAM with the same result. Unfortunately the blue screen flashes so quickly that I cannot read the exact error or related drivers. Any suggestions?

 

[wolluf]

When did this start/what changed before this/any system crash before this/virus? You could try a repair installation - but best have an idea of what might have caused problem first.

 

[deskduty]

try a different video card

 

[thefourthwall]

You enabled the "Automatically Reboot" option under Startup and Recovery section of My Computer's properties. Not a good thing to do. Can you load last known good profile? Since you can't get into Windows this way, use a w2k cd and run recovery console under Repair Install. Your pc is loading a service or driver that is causing the STOP error. in recovery console there is a listsvc command and disable command you'll want to user (after listing them using HELP of course).

 

[Wirdo]

As said above your computer is set to reboot on errors. Right click my computer select properties and then advanced.
You should see a section that says startup and recovery click this and under system failure uncheck the box that say automaticly reboot. You should then be able to read what the error is saying.

 

[thefourthwall]

Wirdo,

I think the problem is that he cannot get that far into (past?) the boot process to make changes to Startup & Recovery, unfortunately.

 

[hashashin]

Have you altered any options in the Bios, Such as power savings, apm or plug and play? I had a simmiler problem until I reset to defaults.

Good luck

 

[Wirdo]

Sorry, misunderstood thought you could get to win2k. This may not be and option and may not help but if you know somone who will let you swap your drive into there comp you might be able to tell what the error is or if it is being caused by some device on your comp.

 

[pbxman]

Try pressing F8 when you get the "Starting Windows 2000" black screen, and choose "last known good".
See if that gets ya in. Then make the change there, or NTFSDOS from

http://www.sysinternals.com

would get you the ability to at least edit your boot.ini to get the /sos option in there to see what driver/device crashes it.
My guess is mup.sys or cdfs.sys since it occurs so late in the startup process.

You have a few options there - for the time it would take to repair it - just reinstall the OS. Note - 64MB RAM is the Bare-Bones for Win2K. It's laughable how slow it really is with 64MB compared to the identical system with 128MB+.

I dont think thats your problem unless you installed a bunch of programs after installing Win2K, and all of a sudden they're all trying to startup at the same time and you run out of pagefile and RAM..then boom - crash-ola.

so - this is what i'd do..
1) - try last known good
2) - try 64MB more RAM
3) - cry, cut my loses with all the wasted time, and reinstall the OS


Good luck. pbxman
Systems Administrator

Please let Tek-Tips members know their posts were helpful.