Passmark performance test with 4 k Monitor

[marcinwednesbury]

Hi all i have a problem

Bought 4k monitor since this i cant test my gpu buring a test all freeze etc works on 2k monitor problem started since 4k

[David (PassMark)]

We have tested on a lot of 4K monitors without problem (assuming the video card supports 4K and has enough video RAM for 4K).

There isn't enough information to really make an informed comment.
What are the hardware specs?
Which one of the tests cause a problem?
Are you video card drivers up to date?

[marcinwednesbury]

my gpu gtx 970 cpu 3770k 16gb ram driver updated

When i start 3d test DX 9 no problem after that DX 10 freeze but computer it self works just need to close program but unable to finish test

[David (PassMark)]

What version of PerformanceTest are you using?

See,
https://www.passmark.com/products/pt_history.htm

There was a bug fix in the DirectX10 test for systems which had more than 500 permutations of display modes (resolutions and color depths).

If you are using the latest release, send us a debug log.
https://www.passmark.com/support/ptdebug.htm

[marcinwednesbury]

0.000s - DEBUG: Starting...
0.000s - DEBUG: Start time: 2018/11/22, 17:45:29.652
0.016s - DEBUG: PerformanceTest 9.0 build 1029 64-Bit
0.016s - DEBUG OS: Windows 8 build 9200 (64-bit)
0.016s - DEBUG Path: C:\Program Files\PerformanceTest
0.032s - DEBUG Command line: "C:\Program Files\PerformanceTest\PerformanceTest64.exe" DEBUGMODE
0.032s - Date: 11/22/18 17:45:29
0.047s - HORZRES - 3840 VERTRES - 2160
0.063s - LOGPIXELSY - 120 LOGPIXELSX - 120 DPIScale - 1.250000
0.063s - DEBUG: Opening splash window
1.532s - DEBUG: UTF8StringToWChar string truncated (FCBGA1224/FCPGA932nm -> FCBGA1224/FCPGA)
1.860s - DEBUG: Init CD Burner
2.078s - DEBUG: Retrieving Computer Name
2.078s - DEBUG: Retrieving OS Name
2.125s - Windows 8 build 9200 (64-bit)
2.125s - DEBUG: Retrieving Graphics Info
4.313s - Video adapters: iNumDD 14
4.313s - Video adapter 0: bDisplay: 1 szDeviceDescription: AMD Radeon R9 390 szDriverVersion: 24.20.13019.1008 : Memory: 8589934592
4.313s - Monitor 0:1 3840x2160x32 60Hz 120 DPI (Primary monitor)
4.328s - Video adapter 1: bDisplay: 0 szDeviceDescription: AMD Radeon R9 390 szDriverVersion: 24.20.13019.1008 : Memory: 8589934592
4.328s - Video adapter 2: bDisplay: 0 szDeviceDescription: AMD Radeon R9 390 szDriverVersion: 24.20.13019.1008 : Memory: 8589934592
4.328s - Video adapter 3: bDisplay: 0 szDeviceDescription: AMD Radeon R9 390 szDriverVersion: 24.20.13019.1008 : Memory: 8589934592
4.328s - Video adapter 4: bDisplay: 0 szDeviceDescription: AMD Radeon R9 390 szDriverVersion: 24.20.13019.1008 : Memory: 8589934592
4.344s - Video adapter 5: bDisplay: 0 szDeviceDescription: AMD Radeon R9 390 szDriverVersion: 24.20.13019.1008 : Memory: 8589934592
4.344s - Video adapter 6: bDisplay: 0 szDeviceDescription: AMD Radeon R9 390 szDriverVersion: 24.20.13019.1008 : Memory: 8589934592
4.344s - Video adapter 7: bDisplay: 0 szDeviceDescription: szDriverVersion: : Memory: 0
4.344s - Video adapter 8: bDisplay: 0 szDeviceDescription: szDriverVersion: : Memory: 0
4.360s - Video adapter 9: bDisplay: 0 szDeviceDescription: szDriverVersion: : Memory: 0
4.360s - Video adapter 10: bDisplay: 0 szDeviceDescription: szDriverVersion: : Memory: 0
4.360s - Video adapter 11: bDisplay: 0 szDeviceDescription: szDriverVersion: : Memory: 0
4.375s - Video adapter 12: bDisplay: 0 szDeviceDescription: szDriverVersion: : Memory: 0
4.375s - Video adapter 13: bDisplay: 0 szDeviceDescription: szDriverVersion: : Memory: 0
4.375s - DEBUG: Retrieving USB Info
4.875s - DEBUG: GetProcessList
4.875s - DEBUG: SysInfoDLL_Results::GetProcessList start
4.875s - DEBUG: SysInfoDLL_Results::GetProcessList finished
4.891s - DEBUG: Checking language and local
4.891s - DEBUG: Got language and local
4.891s - DEBUG: Creating main window
5.016s - DEBUG: Updating Baseline List
5.032s - Updating baseline: using OS:
5.032s - Windows 8 build 9200 (64-bit)
5.078s - DEBUG: Finished updating Baseline List
5.110s - CD3DApplication::BuildDeviceList start
5.125s - CD3DApplication::BuildDeviceList adapter 0 of 1
5.157s - CD3DApplication::BuildDeviceList finish
5.157s - DEBUG PERF: Initialize3DEnvironment
5.157s - DEBUG PERF: AdjustWindowForChange start
5.172s - DEBUG PERF: AdjustWindowForChange done
5.172s - DEBUG PERF: DX9 CreateDevice
5.235s - DEBUG PERF: DX9 CreateDevice OK
5.235s - DEBUG PERF: DX9 CreateDevice success
7.235s - g_D3D9ComplexDeviceUsed found (AMD Radeon (TM) R9 390 Series)
7.313s - DEBUG: Creating performance stats thread
7.328s - DEBUG: Performance stats thread created
7.344s - Initialize CD/DVD Burn
7.344s - DEBUG: Initialising bitmap resources
7.375s - DEBUG: Closing splash window
7.375s - DEBUG: RP 1
7.422s - DEBUG PERF: Loading Perf DLL
7.422s - DEBUG PERF: Found perf functions in DLL
7.438s - DEBUG PERF: Loaded Perf DLL
7.438s - DEBUG PERF: CPerformanceStats::GetLocalCounterString entry
7.532s - DEBUG: RP 2

[marcinwednesbury]

SORTED ther is a answer

https://www.reddit.com/r/pcmasterrac...es_my_gtx_970/

[David (PassMark)]

Yes 3rd party software that do frame capture and overlays are known to cause issues (and not just with our software)

See,
https://www.passmark.com/support/per...ite_screen.htm
https://www.passmark.com/support/per...r_messages.htm

But your problem description didn't exactly match the known misbehavior. Anyway, if it is fixed now, that's great.

[marcinwednesbury]

Thanks just wonder wyh r9 390 do not show dx 12 score not supported windows 10 ?!

[David (PassMark)]

Don't know what you mean. The R9-390 can do DirectX12 on Win10.
Maybe there are a few machines that have issues (e.g. bad video card drivers), but for the most part they should run DirectX12 OK.

[marcinwednesbury]

This is what it get

[David (PassMark)]

Log shows you are running Win8 and not Win10.

0.016s - DEBUG OS: Windows 8 build 9200 (64-bit)

DirectX12 was added in Win10.