If the error happens when using the battery then it is no way related to the AC adapter...
I assume he's referring to these events.
Code:
Event[497]:
Log Name: System
Source: Microsoft-Windows-Kernel-Processor-Power
Date: 2014-10-24T16:25:12.897
Event ID: 55
Task: N/A
Level: Information
Opcode: Info
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: HP
Description:
Processor 3 in group 0 exposes the following power management capabilities:
Idle state type: ACPI Idle (C) States (2 state(s))
Performance state type: [COLOR=#800080]ACPI Performance (P)[/COLOR] / [COLOR=#ff0000]Throttle (T) States[/COLOR]
Nominal Frequency (MHz): [COLOR=#008000]2401[/COLOR]
Maximum performance percentage: 100
Minimum performance percentage: 33
Minimum throttle percentage: 3
I've looked further into this, although I cannot find the exact reason for it. Have you modified some options within the BIOS, such as SpeedStep?
Due to the fact that I do not have a Kernel memory dump for one of your 0x124 crashes, I cannot find the temperatures for your computer. Do you crash when performing a particular activity? Can you monitor your temperatures with
Speccy or
HWmonitor.
T states are old throttle states which are largely undocumented as they are uncommon, they're also no longer used with modern processors, so these can be completely ignored.
P states are used by SpeedStep for Intel processors that consists of many power states, these lower the speeds and performance of a processor to generate less heat and use less power. This will change depending upon heat and power comsumption; although I don't see anything in your event log that shows the processor is being throttled at all.
There's a lot of information on this, including a calculation that explains how power consumption is indentified, as well as how SpeedStep uses this calculation to alter the processor accordingly.
You might want to try to reset the BIOS in case you have made any alterations, it might correct this problem. I still cannot see the AC adapter causing the problem, I have no idea where they're getting this information from.
Code:
Event[11065]:
Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 2014-12-11T17:08:22.281
Event ID: 109
Task: N/A
Level: Information
Opcode: Info
Keyword: N/A
User: N/A
User Name: N/A
Computer: Baere
Description:
The kernel power manager has initiated a shutdown transition.
Code:
Event[11041]:
Log Name: System
Source: Microsoft-Windows-Power-Troubleshooter
Date: 2014-12-11T15:38:42.273
Event ID: 1
Task: N/A
Level: Information
Opcode: Info
Keyword: N/A
User: S-1-5-19
User Name: NT AUTHORITY\LOCAL SERVICE
Computer: Baere
Description:
[COLOR=#800080]The system has returned from a low power state.[/COLOR]
[COLOR=#800080]Sleep Time[/COLOR]: ?2014?-?12?-?11T[COLOR=#800080]22:12:06[/COLOR].034347300Z
[COLOR=#800000]Wake Time[/COLOR]: ?2014?-?12?-?11T[COLOR=#800000]22:38:38[/COLOR].861094200Z
Wake Source: Unknown
Your laptop was in a low power sleep state for nearly half an hour, was this due to a timer with Windows or unknown? It could be temperature related.
Are these two events related to manual work which you have done purposely or are they automatic and therefore a problem; if the latter then we seem to be looking at a CPU problem, most likely temperature related.
Code:
Event[7580]:
Log Name: System
Source: User32
Date: 2014-11-23T12:47:50.557
Event ID: 1074
Task: N/A
Level: Information
Opcode: N/A
Keyword: Classic
User: S-1-5-21-1214943127-3233761971-4177106911-1002
User Name: BAERE\USER
Computer: Baere
Description:
The process Explorer.EXE has initiated the shutdown of computer BAERE on behalf of user BAERE\USER for the following reason: [COLOR=#ff8c00]Other[/COLOR] ([COLOR=#ff8c00]Planned[/COLOR])
Reason Code: [COLOR=#ff0000]0x80000000[/COLOR]
Shutdown Type: shutdown
Comment:
The reason code indicates the
SHTDN_REASON_FLAG_PLANNED flag was enabled for whatever reason. This event should create a System State Data file, although it's not generated unless Windows Error Reporting is enabled.
Double check that the WERS is ENABLED:
Start > Search > type services.msc > Under the name tab, find Windows Error Reporting Service > If the status of the service is not Started then right click it and select Start. Also ensure that under Startup Type it is set to Automatic rather than Manual. You can do this by right clicking it, selecting properties, and under General selecting startup type to 'Automatic', and then click Apply.
Slightly off topic.
I had a failing ASUS motherboard on my computer, in fact I still have it in this computer, I called ASUS and they said it was my RAM or HDD, I know for certain it isn't, but they refuse to do anything because they see BSODs being caused by RAM or failing drives... Meaning I'll have to buy a new motherboard at some point, one thing is for sure though; I'm not going with ASUS again.