INTERNAL_POWER_ERROR on my HP TX2500z tablet

[bmorris53]

Hey all,

I have been searching far and wide for an answer through google and I just can't find one that fits my problem.

I get a INTERNAL_POWER_ERROR on fresh boots randomly, the stop code is as follows:

0x000000A0 (0x0000000000000101,0x0000000000000007,
0xFFFFFA60021D4B20,0x0000000000000000)

I have no external hardware plugged. again this happens randomly I'll get the BSOD, shut down the computer, boot up and it works fine. Then some random number of startups later I get the BSOD again with no new hardware or anything.

System info:

HP pavilion tx2500z
Windows Vista Home Premium 64-bit SP1
BIOS version F.08
AMD Turion X2 Ultra Dual-Cor Mobile ZM-80
ATI HD3200 graphics

I just updated the BIOS today hoping it would work but nothing. The only updates I have installed recently are for Spybot S&D and the general Windows updates when they come. I have recently installed Virtual PC and VMware Player but this problem has been going on since before I did those installs. I've also tried removing the battery and running strictly off wall power with no luck.

Any help would be great because I am trying to find any excuse to stick with Windows so I don't lose my tablet funtionality cause Linux is looking really good right now.

Thanks

 

[dwellman]

Can you or have you installed the Windows Debugging Tools aka WinDbg.exe and used it to look at the dump?

This is generally a USB related issue, but it could be something else. 64-bit seems more susceptible. SP1 is supposed to fix these issues.

 

[bmorris53]

No I don't have the debugger installed, I'll do that now and post back.

 

[bmorris53]

Ok so I couldn't get debugger to work last night so i just decided to format and re-install windows. This time I installed 64bit business addition and gave it a shot. Installation went great. But this morning I got a new start up error, WINLOGON_FATAL_ERROR, I finally got debugger to work:

Here is the first analysis:

Use !analyze -v to get detailed debugging information.

BugCheck C000021A, {fffff880008b0b00, ffffffffc0000001, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt!ExpSystemErrorHandler2+5e9 )

The detailed analysis looks like this:

WINLOGON_FATAL_ERROR (c000021a)
The Winlogon process terminated unexpectedly.
Arguments:
Arg1: fffff880008b0b00, String that identifies the problem.
Arg2: ffffffffc0000001, Error Code.
Arg3: 0000000000000000
Arg4: 0000000000000000

Debugging Details:
------------------


ERROR_CODE: (NTSTATUS) 0xc000021a - {Fatal System Error} The %hs system process terminated unexpectedly with a status of 0x%08x (0x%08x 0x%08x). The system has been shut down.

BUGCHECK_STR: 0xc000021a_c0000001

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: smss.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80001f937dc to fffff80001c4d950

(Not including STACK_TEXT)

STACK_COMMAND: kb

FOLLOWUP_IP:
nt!ExpSystemErrorHandler2+5e9
fffff800`01e121c9 cc int 3

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nt!ExpSystemErrorHandler2+5e9

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 48d1ba12

FAILURE_BUCKET_ID: X64_0xc000021a_c0000001_nt!ExpSystemErrorHandler2+5e9

BUCKET_ID: X64_0xc000021a_c0000001_nt!ExpSystemErrorHandler2+5e9

So "ntkrnlmp.exe" caused my stop, but how do I fix it?

Thanks

 

[dwellman]

The first thing to do is try to replace the file ntkrnlmp.exe with one from the original DVD (or a known good one with the appropriate service pack) using the System Recovory Otions -> Command Prompt tool.

EDIT: On second thought, try the Startup Repair option, first.

Also, provided your install media is not corrupt, it's likely you have a memory or a motherboard issue if problems like this keep happening

 

[bmorris53]

Thanks, I will keep pluggin at it, I post if I find anything new or if I fix the problem.

EDIT: Thought I should throw out there that these problems only happen on fresh startups, once I get the computer running it runs smooth forever, I can hibernate it for hours and it starts right up, even restarting after update installs are fine. Just on fresh cold starts I get what seem to be driver conflicts.

Anyway I will post again if I fix the issue.

 

[dwellman]

That is weird. . .

 

[Sushant Shekhar]

this worked for me
http://www.onehackup.com/2015/08/01/internal-power-error-dell-laptop-error-solved/