Specialty Forums
Security and Virus
General Hardware
CPUs/Overclocking
Networking
Digital Photo/Video
Office Software
PC Gaming
Console Gaming
Programming
Database
Web Development
Digital Home

General Forums
Windows XP
Windows Vista
Windows 95/98
Windows Me
Windows NT
Windows 2000
Win Server 2008
Win Server 2003
Windows 3.1
Linux
PDAs
BeOS
Novell Netware
OpenVMS
Solaris
Disk Op. System
Unix
Mac
OS/2

Drivers
Driver Scan
Driver Forum

Software
Automatic Updates

BIOS Updates

My Computing.Net

Solution Center

Free IT eBook

Howtos

Site Search

Message Find

RSS Feeds

Install Guides

Data Recovery

About

Home
Reply to Message Icon Go to Main Page Icon

Boot-up stuck in a continuous loop!

Original Message
Name: tonaso
Date: December 23, 2006 at 10:37:19 Pacific
Subject: Boot-up stuck in a continuous loop!
OS: Win 2000 Pro
CPU/Ram: PIII-1G/256k
Model/Manufacturer: Dell/Inspiron 8100 Laptop
Comment:
Hello:

I'm having trouble with booting up my PC. I hope some people more knowledgable than me can help with this puzzler;

The computer starts normally, nothing out of the ordinary that I can tell but after the Windows logo and the little blue progress bar saying 'starting up, please wait' it flashes up a blue screen with somekind of message on it.

Now the msg is only on screen for a fraction of a second, I only managed to catch the words 'corrupt' and phrase 'dump of physical memory'

Following this the PC restarts the bootup sequence again. and again. and again. Each time the same message flashes up.

I know somethings causing the memory dump but I can't get into Safe Mode at all nor can I restart with the last known good config.

So I'm lost at what to do next.

Anyone able to help?

Thanks & Kind Regards,
tonaso




Report Offensive Message For Removal


Response Number 1
Name: trvlr
Date: December 23, 2006 at 22:33:41 Pacific
Subject: Boot-up stuck in a continuous loop!
Reply: (edit)
Frequently, but not always..., bso/dump-screen can be due to less than purrfect RAM; one or more modules/sticks may be failing... A corrupt hard-drive can also cause same effect.

In the case of RAM if you have two or more sticks installed, typical advice is to reduce to a single stick (min 128Meg) and try each in turn... But as you have a laptop this may not be practical? If you can remove additional RAM (there is usually some permanently installed on the mobo and the rest in an expansion slot(?)) that may allow some RAM confirmation?

Personally I've not had much success with Memory check utils; although many have...

As for the drive... boot up with the W2K CD and run the recovery Console - specifically the checkdisk routine:

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

http://www.windowsnetworking.com/kb...

http://labmice.techtarget.com/troub...

http://www.computerhope.com/issues/...

discuss it all in reasonable depth.

And if that doesn't resolve it.. try a Repair routine; opt to check the system files; and if that doesn't work... do a repair instalation - in effect an overwrite of the current installation (i.e. re-install to same folder).

More on this at:

http://www.techspot.com/vb/topic835...

http://www.windowsreinstall.com -

specifically:

http://www.windows2000.windowsreins...

The Repair installation may be be easier option overall; will probably do all that's required in fell swooop?


Report Offensive Follow Up For Removal




Use following form to reply to current message:

   Name: From My Computing.Net Settings
 E-Mail: From My Computing.Net Settings

Subject: Boot-up stuck in a continuous loop!

Comments:

 
  Homepage URL (*): 
Homepage Title (*): 
         Image URL: 
 


Data Recovery Software




My PC has been hijacked!

Lexmark 2600 Printer Issues

btk1w1 infected start here post

Unwanted message remians on screen

Slow boot time


The information on Computing.Net is the opinions of its users. Such opinions may not be accurate and they are to be used at your own risk. Computing.Net cannot verify the validity of the statements made on this site. Computing.Net and Computing.Net, LLC hereby disclaim all responsibility and liability for the content of Computing.Net and its accuracy.
PLEASE READ THE FULL DISCLAIMER AND LEGAL TERMS BY CLICKING HERE

All content ©1996-2007 Computing.Net, LLC