How Do I Interpret These "Hot CPU" Test Results?

[bostonkris34]

Hi everyone,

In relation to another thread I have about a busted new PC build, I ran a Hot CPU test and am not sure how to read the log. I started the program and went to sleep - it looks like it only ran for ~7 minutes if I'm reading it correctly. Do you think these results indicate a CPU and/or motherboard problem? THANK YOU!!!

Kris

000000| 0000 0000222c Mar, 09 - 20:37:06 | Startig Hot CPU Tester Pro 4.4.1
000001| 1012 0000222c Mar, 09 - 20:37:06 | Initializing DefectTrack Engine version 2.2.0
000002| 1010 0000222c Mar, 09 - 20:37:06 | Loading options...
000003| 1011 0000222c Mar, 09 - 20:37:06 | Reading system info...
000004| 0000 0000222c Mar, 09 - 20:37:09 | CPU: Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz
000005| 0000 0000222c Mar, 09 - 20:37:10 | Speed: 4199MHz
000006| 0005 0000222c Mar, 09 - 20:37:10 | -1
000007| 0005 0000222c Mar, 09 - 20:37:10 | -1
000008| 0005 0000222c Mar, 09 - 20:37:10 | -1
000009| 0000 0000222c Mar, 09 - 20:37:10 | L1 Cache Size: -2KB
000010| 0000 0000222c Mar, 09 - 20:37:10 | L2 Cache Size: -1KB
000011| 0000 0000222c Mar, 09 - 20:37:10 | L3 Cache Size: -1KB
000012| 0000 0000222c Mar, 09 - 20:37:10 | Hyper-Threading: FALSE
000013| 0000 0000222c Mar, 09 - 20:37:10 | SMP: TRUE
000014| 0000 0000222c Mar, 09 - 20:37:10 | Scanning SMBIOS...
000015| 0000 0000222c Mar, 09 - 20:37:10 | Could not read SMBIOS data
000016| 0000 0000222c Mar, 09 - 20:37:10 | Total Physical Memory: -1 bytes
000017| 0000 0000222c Mar, 09 - 20:37:10 | Availabe Physical Memory: -1 bytes
000018| 0000 0000222c Mar, 09 - 20:37:10 | Total Virtual Memory: -131072 bytes
000019| 0000 0000222c Mar, 09 - 20:37:10 | Availabe Virtual Memory: -154509312 bytes
000020| 0000 0000222c Mar, 09 - 20:37:10 | Operating System: Windows Server 2007 Home Premium
000021| 0156 0000222c Mar, 09 - 20:37:10 | Setting Process Priority...
000022| 1111 0000222c Mar, 09 - 20:37:17 | Diagnostic has started
000023| 1112 0000222c Mar, 09 - 20:37:17 | Test Duration: 06:00:00
000024| 1113 0000222c Mar, 09 - 20:37:17 | Diagnostic Method: Sequential
000025| 1114 0000222c Mar, 09 - 20:37:17 | Error Handling: Ignore and Continue
000026| 1115 0000222c Mar, 09 - 20:37:17 | Hyper-Threading: Disabled
000027| 0010 0000222c Mar, 09 - 20:37:17 | -Complex Matrix : Enabled
000028| 0011 0000222c Mar, 09 - 20:37:17 | --Thread Priority: THREAD_PRIORITY_NORMAL
000029| 0011 0000222c Mar, 09 - 20:37:17 | --Matrix Size: 3,000x3,000
000030| 0011 0000222c Mar, 09 - 20:37:17 | --Matrix Data Type: Double
000031| 0010 0000222c Mar, 09 - 20:37:17 | -Calculating Pi : Enabled
000032| 0011 0000222c Mar, 09 - 20:37:17 | --Thread Priority: THREAD_PRIORITY_NORMAL
000033| 0011 0000222c Mar, 09 - 20:37:17 | --Pi Iterations: 10,000
000034| 0010 0000222c Mar, 09 - 20:37:17 | -Sorting Algorithms : Enabled
000035| 0011 0000222c Mar, 09 - 20:37:17 | --Thread Priority: THREAD_PRIORITY_NORMAL
000036| 0011 0000222c Mar, 09 - 20:37:17 | --Insertion Sort: Enabled
000037| 0011 0000222c Mar, 09 - 20:37:17 | --Shell Sort: Enabled
000038| 0011 0000222c Mar, 09 - 20:37:17 | --Merge Sort: Enabled
000039| 0011 0000222c Mar, 09 - 20:37:17 | --Heap Sort: Enabled
000040| 0011 0000222c Mar, 09 - 20:37:17 | --Quick Sort: Enabled
000041| 0011 0000222c Mar, 09 - 20:37:17 | --CArray Quick Sort: Enabled
000042| 0011 0000222c Mar, 09 - 20:37:17 | Sorting Array Size: 100,000
000043| 0010 0000222c Mar, 09 - 20:37:17 | -Prime Test : Enabled
000044| 0011 0000222c Mar, 09 - 20:37:17 | --Thread Priority: THREAD_PRIORITY_NORMAL
000045| 0011 0000222c Mar, 09 - 20:37:17 | --Iterations: 100,000
000046| 0010 0000222c Mar, 09 - 20:37:17 | -Fast Fourier Transforms : Disabled
000047| 0011 0000222c Mar, 09 - 20:37:17 | --Thread Priority: THREAD_PRIORITY_NORMAL
000048| 0010 0000222c Mar, 09 - 20:37:17 | -Chipset : Disabled
000049| 0011 0000222c Mar, 09 - 20:37:17 | --Thread Priority: THREAD_PRIORITY_NORMAL
000050| 0010 0000222c Mar, 09 - 20:37:17 | -L1 Cache : Disabled
000051| 0011 0000222c Mar, 09 - 20:37:17 | --Thread Priority: THREAD_PRIORITY_NORMAL
000052| 0010 0000222c Mar, 09 - 20:37:17 | -L2 Cache : Disabled
000053| 0011 0000222c Mar, 09 - 20:37:17 | --Thread Priority: THREAD_PRIORITY_NORMAL
000054| 0010 0000222c Mar, 09 - 20:37:17 | -Memory : Enabled
000055| 0011 0000222c Mar, 09 - 20:37:17 | --Thread Priority: THREAD_PRIORITY_NORMAL
000056| 0010 0000222c Mar, 09 - 20:37:17 | -HD : Enabled
000057| 0011 0000222c Mar, 09 - 20:37:17 | --Thread Priority: THREAD_PRIORITY_NORMAL
000058| 0010 0000222c Mar, 09 - 20:37:17 | -MMX : Enabled
000059| 0011 0000222c Mar, 09 - 20:37:17 | --Thread Priority: THREAD_PRIORITY_NORMAL
000060| 0010 0000222c Mar, 09 - 20:37:18 | -SSE : Disabled
000061| 0011 0000222c Mar, 09 - 20:37:18 | --Thread Priority: THREAD_PRIORITY_NORMAL
000062| 0010 0000222c Mar, 09 - 20:37:18 | -SSE2/SSE3 : Disabled
000063| 0011 0000222c Mar, 09 - 20:37:18 | --Thread Priority: THREAD_PRIORITY_NORMAL
000064| 0010 0000222c Mar, 09 - 20:37:18 | -3DNow! : Disabled
000065| 0011 0000222c Mar, 09 - 20:37:18 | --Thread Priority: THREAD_PRIORITY_NORMAL
000066| 1024 00000b94 Mar, 09 - 20:37:18 | Starting Complex Matrix Module on CPU 0
000076| 1030 000014bc Mar, 09 - 20:37:18 | Starting Prime Test Module on CPU 1
000090| 1030 00001898 Mar, 09 - 20:37:18 | Starting Prime Test Module on CPU 3
000105| 1038 00001770 Mar, 09 - 20:37:18 | Starting Memory Mdoule on CPU 5
000119| 1038 000015a4 Mar, 09 - 20:37:18 | Starting Memory Mdoule on CPU 7
000122| 1009 0000222c Mar, 09 - 20:44:38 | Closing Hot CPU Tester Pro...
000123| 0000 0000222c Mar, 09 - 20:44:38 | ************ End of Session ************

 

[Rhinofart]

Yup. The test only lasted a few short minutes. I've not used that app before. Most times stress testing for CPUs is done with Prime95.

 

[bostonkris34]

Yup. The test only lasted a few short minutes. I've not used that app before. Most times stress testing for CPUs is done with Prime95.

Yeah, I was wondering perhaps if that in itself indicates a problem - it was supposed to go for 6 hours. Is there a reason it force quit that might provide insight into my PC problem? For instance it says it could not read my SMBIOS data, etc. I tried Prime95 and if I recall correctly, it crashed my computer haha - never a good sign. But I could be mixing that up in my head as I ran many tests last night. Basically, detailed in my other thread, I'm trying to figure out if I have a MOBO or CPU (or, less likely, PSU) problem. I'm leaning MOBO. Everything is brand new out of the box.

MOBO - Asus ROG Strix z270e gaming
CPU - i7-7700k

I will try running Prime95 again tonight!

 

[Rhinofart]

Reading the log it shows no indication of a forced exit of the test. It looks like everything completed "normally"