Fault tracing with a bootable USB stick

[John Marsh]

Thanks for the tech tips!

Crystal Disk Info 7.0.3 x64 gives: Health Status: Good. Temperature: 26°C.

All the listed parameters have blue dots by them.

In the Event Log, I found a couple of entries which may be relevant.

Log Name: Application
Source: Microsoft-Windows-WMI
Date: 19/09/2016 14:11:59
Event ID: 10
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: User-PC
Description:
Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-WMI" Guid="{1edeee53-0afe-4609-b846-d8c0b2075b1f}" EventSourceName="WinMgmt" />
<EventID Qualifiers="49152">10</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2016-09-19T13:11:59.000000000Z" />
<EventRecordID>6542</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>User-PC</Computer>
<Security />
</System>
<EventData>
<Data>//./root/CIMV2</Data>
<Data>SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage &gt; 99</Data>
<Data>0x80041003</Data>
</EventData>
</Event>


-----------------------------------------------------------------------------------------------------------------------

Log Name: System
Source: Service Control Manager
Date: 19/09/2016 14:11:51
Event ID: 7026
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: User-PC
Description:
The following boot-start or system-start driver(s) failed to load:
TPPWRIF
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
<EventID Qualifiers="49152">7026</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2016-09-19T13:11:51.956054600Z" />
<EventRecordID>26538</EventRecordID>
<Correlation />
<Execution ProcessID="728" ThreadID="732" />
<Channel>System</Channel>
<Computer>User-PC</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">
TPPWRIF</Data>
</EventData>
</Event>

-----------------------------------------------------------------------------------------------------------------------------

Who Crashed has found some entries; apparently not all the crash events get its attention.

On Mon 23/05/2016 11:41:27 GMT your computer crashed
crash dump file: CWindows\Minidump\052316-17468-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0x101 (0x30, 0x0, 0xFFFFF880009E9180, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: CWindows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time

----------------------------------------------------------------------------------------------------------------------------

On Thu 26/05/2016 11:05:22 GMT your computer crashed
crash dump file: CWindows\Minidump\052816-18890-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0x9F (0x3, 0xFFFFFA80078D6A10, 0xFFFFF8000405B518, 0xFFFFFA8008DCF200)
Error: DRIVER_POWER_STATE_FAILURE
file path: CWindows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

---------------------------------------------------------------------------------------------------------------------

I haven't tried a Safe Mode test; will give it a go.

Re. overheating: SpeedFan gives: HD0 25°C. Core0 40°C. Core1 40°C. Core2 38°C. Core3 38°C.

I'll clear out any dust if opening the machine becomes necessary. It was bought as new early this year and usage has been sporadic, due to its crashes and the Windows 10 Experience. It is never used on a carpet or tablecloth etc.

I have downloaded the Knoppix .iso and the program for making a bootable USB stick. The USB stick is in the post!

If it does turn out to be a software fault, Knoppix tests will run indefinitely without crashes, I guess.