*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C9, {23e, fffffa80081c32c0, fffff9800eed0e10, 0}
*** WARNING: Unable to verify timestamp for PxHlpa64.sys
*** ERROR: Module load completed but symbols could not be loaded for PxHlpa64.sys
Probably caused by : PxHlpa64.sys ( PxHlpa64+35dd )
Followup: MachineOwner
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C9, {23e, fffffa80081c32c0, fffff9800eed0e10, 0}
*** WARNING: Unable to verify timestamp for PxHlpa64.sys
*** ERROR: Module load completed but symbols could not be loaded for PxHlpa64.sys
Probably caused by : PxHlpa64.sys ( PxHlpa64+35dd )
Followup: MachineOwner
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, fffff8039aeb19c5, 0, 41}
Probably caused by : win32k.sys ( win32k!UserProcessDwmInput+168 )
Followup: MachineOwner
File Description
UPDATE BIOS Update Utility
Release Date 7/19/2012
Version R1013H5File Size 5.69 MB
This utility updates the BIOS to version R1013H5 to resolve the following issues:
- A critical battery dialog box appears after restarting the computer that forces the computer to enter hibernation mode
- The computer intermittently does not charge the battery
- The computer may randomly shutdown
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, fffff8039aeb19c5, 0, 41}
Probably caused by : win32k.sys ( win32k!UserProcessDwmInput+168 )
Followup: MachineOwner
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, fffff8039aeb19c5, 0, 41}
Probably caused by : win32k.sys ( win32k!UserProcessDwmInput+168 )
Followup: MachineOwner
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, fffff8039aeb19c5, 0, 41}
Probably caused by : win32k.sys ( win32k!UserProcessDwmInput+168 )
Followup: MachineOwner