XPS M1210 Will Not Stay On

new battery & mobo and still the same problem?

Only the OS is the same on the same harddisk ?

Is this a Dell adapter, or third party?  Before you changed the expensive parts (battery/mainboard) did you try a new Dell AC adapter?

LaptopNomad - I did switch out the hard drive with a new spare that I had and re-loaded Windows, but it continued to do the same thing.

ejn63 - I didn't replace the power adapter (it is the original Dell model) as the laptop works indefinitely with the cord plugged in.  I only have problems when I unplug the cord and the laptop switches over to battery power.  Do you think there is something with the cord that could cause it to do this?

I'm having the same issue. three month-old battery. no unusual use or damage.

reseated it a couple of times with cord unplugged.

It was working fine on battery or power and then one day it would start and shut down almost immediately. The screen just goes blank and it won't start on battery power, then it runs fine on  power.

Part 2

I tried adjusting power properties using the preloaded settings and nothing seems to make a difference. the M1210 boots up, XP starts and I even started task manager to see what was going on. Nothing odd. then it shut down abruptly with no warning. Took about two minutes.

I'm writing on it now on wall power and it works fine.

The only thing I've added recently is a cooling fan that works on USB because the M1210 gets so hot. It doesn't behave differently with the cooling fan unplugged.

I suppose it could be a bad battery, but when the battery was bad, I got a blinking organge light and that isn't happenning.

M1210 battery issue:

Laptop shuts down  with no warning after three minutes on battery. Battery is six months old, no unusual usage, shows as having 2+ hours life in  power meter.

I  found this commentary, which may be relevant, although I can't really say what it means:

Under certain circumstances with a Windows XP / 2003 operating system - intelppm.sys and processr.sys can cause a virtual machine running under Virtual PC / Virtual Server to crash (by default this will cause the Windows guest operating system to reboot automatically - but if you have changed this setting you will see a blue screen).  The reason for this crash is because these drivers are attempting to perform an unsupported operation inside of the virtual machine (like upgrading the physical processors microcode, changing power state on the physical processor).

Today this problem only occurs on Centrino and AMD K8 processors.  Most people see this problem when they move a virtual machine that was created on another type of processor to a computer running one of these types of processors (and then they usually see the problem when they attempt to shutdown their virtual machine for the first time).  Now you may be wondering why you have not heard about this problem more often - and the reason for that is that if these drivers fail once - they are smart enough to not attempt to perform the operation that failed again.

If you are seeing this problem repeatedly you can manually disable these drivers (with no negative side effect) by going to the following location in the registry:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Processor

Or

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Intelppm

And changing the 'Start' value to '4'.

In the mean time we have made some subtle changes to the way our hardware exposes the processor in Virtual Server R2 so that in future products these drivers should never get loaded inside of virtual machines.

Cheers,
Ben

Published Monday, October 24, 2005 9:25 PM by Virtual PC Guy Filed under: Virtual PC / Server Tips 'n' Tricks