PerformanceTest - Startup Debugging
Last updated: 5/February/2007
Overview
We have had a number of reports of PerformanceTest not
starting correctly. The startup process seems to freeze either permanently
and in some cases it may crash. We have done extensive testing on 100's
of different computers, in various configurations. We have found that
the main reason for this is corrupt SMBIOS (System Management BIOS) in
the PC.
We have added two command line options to PerformanceTest to help with this startup problem.
DEBUGMODE: Creates a debug log file that can be sent to us for investigation;
SAFEMODE: Skips the loading of SMBIOS system information on startup.
This page describes the process needed to create a startup log file from PerformanceTest and starting PerformanceTest in Safe mode.
Downloading the debug version
If you do not have version 6.0 later, download this version of PerformanceTest
that has the debug option in it, using this
link.
Debug mode
Placing the "DEBUGMODE" text on the PerformanceTest command
line will result in a log file being created. You can edit the command
line by finding PerformanceTest in the start menu then right clicking
to edit the shortcut properties (see below).
Log file
The log file is created in the PerformanceTest executable directory or My Documents.
For PerformanceTest V6.0 (and earlier) this is,
C:\Program Files\PerformanceTest. For PerformanceTest V6.1 (and later) this is,
C:\Documents and Setting\<username>\My Documents\Passmark\Performance Test.
The name of the log file is "PerfTestLog.txt"
This is the file you should send us. Once you have created this file
you should mail it to us at
. A startup log file can help us locate the fault in the software.
Example PerfTestLog.txt file
| 0.016s - DEBUG: Starting... 0.016s - DEBUG: PerformanceTest V4.0 build 1010 0.016s - DEBUG OS: Windows XP 0.016s - DEBUG Path: C:\Software development\pt\pt___Win32_Unicode_Release 0.016s - DEBUG Command line: "C:\Software development\pt\pt___Win32_Unicode_Release\pt.exe" DEBUGMODE 0.031s - DEBUG: Init common controls 0.031s - DEBUG: Opening splash window 0.062s - DEBUG: Getting WMI info 0.109s - DEBUG: Get WMI CPU details 2.141s - DEBUG: Get WMI RAM details 2.156s - DEBUG: Get WMI BIOS details 2.156s - DEBUG: Getting CPU info 2.172s - DEBUG: GenuineIntel Pentium 4 2785.4 MHz 2.172s - DEBUG: Opening main window 2.172s - DEBUG: Opened main window 2.187s - DEBUG: Checking language and local 2.203s - DEBUG: Getting video driver information 2.219s - DEBUG VIDEO MFG: RADEON 7500 2.219s - DEBUG VIDEO DESC: RADEON 7500 2.219s - DEBUG VIDEO BIOS: BK6.0.0 VR000.000.000.109.000.001.001 wfreq 2.219s - DEBUG: Getting memory information 2.219s - DEBUG: Getting performance stats 2.219s - DEBUG PERF: Loading Perf DLL 2.234s - DEBUG PERF: Found perf functions in DLL 2.234s - DEBUG PERF: Loaded Perf DLL 2.266s - DEBUG PERF: Host "DAVIDXP", Index 238, Counter 6 2.547s - DEBUG PERF: Counter string "\Processor(_Total)\% Processor Time" 2.547s - DEBUG PERF: Got counter string DLL 2.547s - DEBUG PERF: Finished query 2.578s - DEBUG PERF: Added counter 2.578s - DEBUG: Got performance stats 2.578s - DEBUG: Display welcome window 4.672s - DEBUG: Building baseline list 4.703s - DEBUG: Checking command line 4.703s - DEBUG: Entering message loop 6.641s - DEBUG PERF: End perf startup 6.656s - DEBUG: Leaving message loop |
Safe mode
Placing the "SAFEMODE" text on the PerformanceTest command
line will result in PerformanceTest starting without trying to obtain
SMBIOS information. This may help with problems starting PerformanceTest,
due to corrupt SMBIOS or SMBIOS not configured by the OEM. This command
line parameter is only compatible with DEBUGMODE.
eg. PT.exe SAFEMODE