lockup/reboot on touchsmart tx2

[csew]

I have a touchsmart tx2 with Windows 7 - 64 bit OS on it.  For some reason without warning it will

lockup on me.  The only way for me to get the system back is to reboot it.  Once I have rebooted the machine, it will then shutdown without warning.

Other times it will just reboot on me with out warning.

I have called support several times, but the problem continues to occur.  Sometime the system is able to stay up for a couple of hours other times it is up for only a couple of minutes.

The last unexpected reboot I got the following information when the system came back up:

******************************

Problem signature:

Problem Event Name: BlueScreen

OS Version: 6.1.7600.2.0.0.768.3

Locale ID: 1033

Additional information about the problem:

BCCode: 124

BCP1: 0000000000000000

BCP2: FFFFFA8006A988F8

BCP3: 0000000000000000

BCP4: 0000000000000000

OS Version: 6_1_7600

Service Pack: 0_0

Product: 768_1

Files that help describe the problem:

C:\Windows\Minidump\011011-26644-01.dmp

C:\Users\csewell\AppData\Local\Temp\WER-71308-0.sysdata.xml

Read our privacy statement online:

http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:

C:\Windows\system32\en-US\erofflps.txt

*******************

This has been going on intermittently for quite some time; any ideas as to what may be happening here?

[CharlesHP]

0x124 is a Machine Check error, typically it's the CPU that is reporting problem and system has to stop.

that said, Windows is reading someregister to get the CPU status, and if the machine is forced power off, Windows may not have time to do a "proper" shutdown and clear things and random bits might be set leading Windows to believe there was a CPU error, (especially on AMD CPU's they don't clear the bits on clean restart).

In short, 0x124 if happened on Intel CPU or AMD cpu during normal operation, then its' likely the CPU is defective, but if it's the result of a forced power down, and happen on reboot, probably not the cause of the first issue. That kind of explains the randomness of it.

We don't know however, what lead to the lock up to bigin with, I would suggest run memory and hard drive diagnose tests and run resource monitor to see if you can find any clue, system event log might help too. If not sure, always try update the bios and graphics driver, and maybe run HPSA to apply any critical updates.

[csew]

thanks I will do the updates & run the diagnostics and see if that clears up my problem

[csew]

My system has version F.26 of the bios on it, is there a later version?

[csew]

My machine has just restarted again.  It managed to stay up for about 1 1/2 hours before it went out.  The screen just went blank and then the system restarted.

This is what was displayed in the window recover screen:

Problem signature:

Problem Event Name: BlueScreen

OS Version: 6.1.7600.2.0.0.768.3

Locale ID: 1033

Additional information about the problem:

BCCode: 124

BCP1: 0000000000000000

BCP2: FFFFFA800662C548

BCP3: 0000000000000000

BCP4: 0000000000000000

OS Version: 6_1_7600

Service Pack: 0_0

Product: 768_1

Files that help describe the problem:

C:\Windows\Minidump\011111-32276-01.dmp

C:\Users\csewell\AppData\Local\Temp\WER-64194-0.sysdata.xml

Read our privacy statement online:

. . . . .

Where do I go from here?

[csew]

I also posted the dump file to http://www.mediafire.com/?houf61dyoydbcdh

Thanks

[csew]

I also uploaded the xml: http://www.mediafire.com/?kpmaj713ck3334r

[csew]

OK this is the 3rd time this has happened tonight All I was doing was using the touch pad to move the cursor

Problem signature:

Problem Event Name: BlueScreen

OS Version: 6.1.7600.2.0.0.768.3

Locale ID: 1033

Additional information about the problem:

BCCode: 124

BCP1: 0000000000000000

BCP2: FFFFFA8006A3D8F8

BCP3: 0000000000000000

BCP4: 0000000000000000

OS Version: 6_1_7600

Service Pack: 0_0

Product: 768_1

 DMP file http://www.mediafire.com/?s1bqqp5jr3vnsmt

XML file http://www.mediafire.com/?r8jao3ipig8dv40

[csew]

Does anyone have any suggestions of what I need to do to get this problem resolved?

[DJPianz]

Hi there, not sure what your problem is. But from my experience (I'm using TX2 too), this kind of BSOD usually happen when CPU voltage is lower than it should be or when the voltage is too low for the CPU P states, have you undervolt your processor? If not, try to raise your voltage up a notch, i.e. 0.0125v higher that its default, I'm not trying to say that this is a permanent solution, but you can try it and test for stability, use K10STAT to control your P states voltage. Please report here your finding.

P.s : Do it at your own risk, don't blame me if it's not working, I try to share what is working for me.