Author Topic: GPU Caps Viewer 1.34.x.x released  (Read 5482 times)



0 Members and 1 Guest are viewing this topic.

JeGX

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1266
    • View Profile
    • Geeks3D.com
GPU Caps Viewer 1.34.x.x released
« on: March 27, 2017, 01:40:55 PM »
The new version of GPU Caps Viewer is available.

More information and dowmload links:
http://www.geeks3d.com/20170327/gpu-caps-viewer-1-34-0-released/

Stefan

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 4067
    • View Profile
Re: GPU Caps Viewer 1.34.x.x released
« Reply #1 on: March 28, 2017, 06:32:39 PM »
 NVIDIA Windows driver 377.14 breaks Vulkan demos again

Quote
>    plugin_gxc_vulkan_x32.dll!5dde239e()    Unbekannt
     [Unten angegebene Rahmen sind möglicherweise nicht korrekt und/oder fehlen, keine Symbole geladen für plugin_gxc_vulkan_x32.dll]   
     gxl_x32.dll!5ea6e1ce()    Unbekannt
     gxl_x32.dll!5eaa9a8f()    Unbekannt
     gxl_x32.dll!5eac5d69()    Unbekannt
     gxl_x32.dll!5eaa9bd0()    Unbekannt
     gxl_x32.dll!5ea9f43b()    Unbekannt
     gxl_x32.dll!5eaa93e3()    Unbekannt
     gxl_x32.dll!5eaaa032()    Unbekannt
     gxl_x32.dll!5ea359bb()    Unbekannt
     gxl_x32.dll!5ea019e4()    Unbekannt
     gxl_x32.dll!5ea014a6()    Unbekannt
     gxl_x32.dll!5ea0ae6e()    Unbekannt
     sgx_x32.dll!688e23e8()    Unbekannt
     GpuCapsViewer.exe!00ce94b8()    Unbekannt
     [Externer Code]   

PeterYS

  • Newbie
  • *
  • Posts: 8
    • View Profile
Re: GPU Caps Viewer 1.34.x.x released
« Reply #2 on: March 29, 2017, 07:00:43 PM »
The new version of GPU Caps Viewer is available.

More information and dowmload links:
http://www.geeks3d.com/20170327/gpu-caps-viewer-1-34-0-released/

When I run GPUCapsViewer v1.34.0 3D Demos the OpenCL demos on Win7, it would pop out error “OpenCL GPU not supported on the selected platform”. Then I switched to “OpenCL” sheet, its default setting is “1: Intel(R) OpenCL”. After changed manually to “2. AMD Accelerated Parallel Processing”, the OpenCL demos could run successfully.
But on Win10 OS, the GPUCapsViewer OpenCL demos didn’t need this manual setting, why?

PeterYS

  • Newbie
  • *
  • Posts: 8
    • View Profile
Re: GPU Caps Viewer 1.34.x.x released
« Reply #3 on: March 29, 2017, 07:03:47 PM »
The new version of GPU Caps Viewer is available.

More information and dowmload links:
http://www.geeks3d.com/20170327/gpu-caps-viewer-1-34-0-released/

GPU Caps Viewer 1.33.1.0 can not catch my AMD GPU on Win7, but Win10.
AMD GPU listed as below:
Radeon (TM) Pro WX 7100 Graphics.(PCI\VEN_1002&DEV_67C0&SUBSYS_07B11028&REV_00)
Radeon (TM) Pro WX 4150 Graphics.(PCI\VEN_1002&DEV_67E8&SUBSYS_07B01028&REV_00)
Radeon (TM) Pro WX 4130 Graphics.(PCI\VEN_1002&DEV_67E8&SUBSYS_07B01028&REV_01)

The V1.34.0 still didn’t show AMD Radeon Pro WX 7100, WX 4150 and WX 4130 on Win7, but Win10 is ok.
You can refer the link for compared screen captured pic.
https://drive.google.com/open?id=0B6gN-239wF0mOW9fUWw1d1cxR28
Or should I provide what the information to you? THX!!

PeterYS

  • Newbie
  • *
  • Posts: 8
    • View Profile
Re: GPU Caps Viewer 1.34.x.x released
« Reply #4 on: March 30, 2017, 05:44:12 AM »
The new version of GPU Caps Viewer is available.

More information and dowmload links:
http://www.geeks3d.com/20170327/gpu-caps-viewer-1-34-0-released/

GPU Caps Viewer 1.33.1.0 can not catch my AMD GPU on Win7, but Win10.
AMD GPU listed as below:
Radeon (TM) Pro WX 7100 Graphics.(PCI\VEN_1002&DEV_67C0&SUBSYS_07B11028&REV_00)
Radeon (TM) Pro WX 4150 Graphics.(PCI\VEN_1002&DEV_67E8&SUBSYS_07B01028&REV_00)
Radeon (TM) Pro WX 4130 Graphics.(PCI\VEN_1002&DEV_67E8&SUBSYS_07B01028&REV_01)

The V1.34.0 still didn’t show AMD Radeon Pro WX 7100, WX 4150 and WX 4130 on Win7, but Win10 is ok.
You can refer the link for compared screen captured pic.
https://drive.google.com/open?id=0B6gN-239wF0mOW9fUWw1d1cxR28
Or should I provide what the information to you? THX!!
Update Radeon Pro WX7100 gpu_caps_viewer_report.
link: https://drive.google.com/file/d/0B6gN-239wF0mM1Y5endpY2Q4V28/view?usp=sharing

JeGX

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1266
    • View Profile
    • Geeks3D.com
Re: GPU Caps Viewer 1.34.x.x released
« Reply #5 on: March 30, 2017, 03:59:00 PM »
Actually what I need is the log file of GPU Caps Viewer (_log.txt in GPU Caps folder). I need to know if the  WX 7100 is listed or not in Windows devices. On my system for example, the GTX 1060 is listed like that:
Quote
15:52:49 | 28 >> - DEV 0 - DeviceID: PCI\VEN_10DE&DEV_1C03&SUBSYS_61633842&REV_A1
15:52:49 | 29 >> - DEV 0 - DeviceName: \\.\DISPLAY1
15:52:49 | 30 >> - DEV 0 - DeviceString: NVIDIA GeForce GTX 1060 6GB
15:52:49 | 31 >> - DEV 0 - DeviceKey: \Registry\Machine\System\CurrentControlSet\Control\Video\{3FDB2FF5-A64B-4CA6-9A2B-0D133FF04B78}\0000

PeterYS

  • Newbie
  • *
  • Posts: 8
    • View Profile
Re: GPU Caps Viewer 1.34.x.x released
« Reply #6 on: March 31, 2017, 04:22:37 AM »
Actually what I need is the log file of GPU Caps Viewer (_log.txt in GPU Caps folder). I need to know if the  WX 7100 is listed or not in Windows devices. On my system for example, the GTX 1060 is listed like that:
Quote
15:52:49 | 28 >> - DEV 0 - DeviceID: PCI\VEN_10DE&DEV_1C03&SUBSYS_61633842&REV_A1
15:52:49 | 29 >> - DEV 0 - DeviceName: \\.\DISPLAY1
15:52:49 | 30 >> - DEV 0 - DeviceString: NVIDIA GeForce GTX 1060 6GB
15:52:49 | 31 >> - DEV 0 - DeviceKey: \Registry\Machine\System\CurrentControlSet\Control\Video\{3FDB2FF5-A64B-4CA6-9A2B-0D133FF04B78}\0000

Update log file of AMD WX 7100
=================================================================================================
01:16:53 | 0 >> GPU Caps Viewer 1.34.0.0 startup...
01:16:54 | 1 >> Vulkan - instance extensions: 3
01:16:54 | 2 >> Vulkan - 1/ VK_KHR_surface (spec version: 25)
01:16:54 | 3 >> Vulkan - 2/ VK_KHR_win32_surface (spec version: 5)
01:16:54 | 4 >> Vulkan - 3/ VK_EXT_debug_report (spec version: 4)
01:16:54 | 5 >> Vulkan - # devices: 1
01:16:54 | 6 >> Vulkan - [ Device 1 ]--------------------------------------
01:16:54 | 7 >> Vulkan -   device name: Radeon (TM) Pro WX 7100 Graphics
01:16:54 | 8 >> Vulkan -   deviceID: 1002-67C0
01:16:54 | 9 >> Vulkan -   driver version: 4210689
01:16:54 | 10 >> Vulkan -   API version: 1.0.37
01:16:54 | 11 >> Vulkan -   device type: DISCRETE_GPU
01:16:54 | 12 >> [SGX] - SGX 0.3.0.0 initialization in progress...
01:16:54 | 13 >> [SGX] - (C)2015-2017 Geeks3D - www.geeks3d.com/geexlab/
01:16:54 | 14 >> [SGX] - Plugin search path: C:\Users\SA\Desktop\GPU_Caps_Viewer1.34\plugins/
01:16:54 | 15 >> [SGX] - SGX initialized OK.
01:16:54 | 16 >> [SGX] - Plugin search path: C:\Users\SA\Desktop\GPU_Caps_Viewer1.34\gxcplugins/
01:16:54 | 17 >> [SGX] - [Plugin manager] unable to load the plugin: C:\Users\SA\Desktop\GPU_Caps_Viewer1.34\plugins/plugin_gxc_gpumon_x32.dll
01:16:54 | 18 >> [SGX] - [GpuMonitor] GPU monitoring plugin for NVIDIA and AMD GPUs
01:16:54 | 19 >> [SGX] - [GpuMonitor] Operating system detected: Windows 7 build 7601
01:16:54 | 20 >> [SGX] - [GpuMonitor] Num GPUs found: 1
01:16:54 | 21 >> [SGX] - [GpuMonitor] GPU0 - Intel(R) Iris(TM) Pro Graphics P580
01:16:54 | 22 >> [SGX] - [GpuMonitor] GPU0 - PCI codes: 0x8086-0x193D
01:16:54 | 23 >> [SGX] - [GpuMonitor] GPU0 - BIOS: Intel Video BIOS
01:16:54 | 24 >> [SGX] - [GpuMonitor] GPU0 - driver: Intel 21.20.16.4574 (12-23-2016) GL:atig6pxx.dll
01:16:54 | 25 >> [SGX] - Plugin plugin_gxc_gpumon_x32.dll successfully loaded
01:16:54 | 26 >> - DEV 0 - DeviceID: PCI\VEN_8086&DEV_193D&SUBSYS_07B11028&REV_09
01:16:54 | 27 >> - DEV 0 - DeviceName: \\.\DISPLAY1
01:16:54 | 28 >> - DEV 0 - DeviceString: Intel(R) Iris(TM) Pro Graphics P580
01:16:54 | 29 >> - DEV 0 - DeviceKey: \Registry\Machine\System\CurrentControlSet\Control\Video\{674CA461-FAB1-44C5-BB14-5ED2DFBA2C37}\0000
01:16:54 | 30 >> - DEV 1 - DeviceID: PCI\VEN_8086&DEV_193D&SUBSYS_07B11028&REV_09
01:16:54 | 31 >> - DEV 1 - DeviceName: \\.\DISPLAY2
01:16:54 | 32 >> - DEV 1 - DeviceString: Intel(R) Iris(TM) Pro Graphics P580
01:16:54 | 33 >> - DEV 1 - DeviceKey: \Registry\Machine\System\CurrentControlSet\Control\Video\{674CA461-FAB1-44C5-BB14-5ED2DFBA2C37}\0001
01:16:54 | 34 >> - DEV 2 - DeviceID: PCI\VEN_8086&DEV_193D&SUBSYS_07B11028&REV_09
01:16:54 | 35 >> - DEV 2 - DeviceName: \\.\DISPLAY3
01:16:54 | 36 >> - DEV 2 - DeviceString: Intel(R) Iris(TM) Pro Graphics P580
01:16:54 | 37 >> - DEV 2 - DeviceKey: \Registry\Machine\System\CurrentControlSet\Control\Video\{674CA461-FAB1-44C5-BB14-5ED2DFBA2C37}\0002
01:16:54 | 38 >> - DEV 3 - DeviceID: PCI\VEN_8086&DEV_193D&SUBSYS_07B11028&REV_09
01:16:54 | 39 >> - DEV 3 - DeviceName: \\.\DISPLAY4
01:16:54 | 40 >> - DEV 3 - DeviceString: Intel(R) Iris(TM) Pro Graphics P580
01:16:54 | 41 >> - DEV 3 - DeviceKey: \Registry\Machine\System\CurrentControlSet\Control\Video\{674CA461-FAB1-44C5-BB14-5ED2DFBA2C37}\0003
01:16:54 | 42 >> - DEV 4 - DeviceID: PCI\VEN_8086&DEV_193D&SUBSYS_07B11028&REV_09
01:16:54 | 43 >> - DEV 4 - DeviceName: \\.\DISPLAY5
01:16:54 | 44 >> - DEV 4 - DeviceString: Intel(R) Iris(TM) Pro Graphics P580
01:16:54 | 45 >> - DEV 4 - DeviceKey: \Registry\Machine\System\CurrentControlSet\Control\Video\{674CA461-FAB1-44C5-BB14-5ED2DFBA2C37}\0004
01:16:54 | 46 >> - DEV 5 - DeviceID: PCI\VEN_8086&DEV_193D&SUBSYS_07B11028&REV_09
01:16:54 | 47 >> - DEV 5 - DeviceName: \\.\DISPLAY6
01:16:54 | 48 >> - DEV 5 - DeviceString: Intel(R) Iris(TM) Pro Graphics P580
01:16:54 | 49 >> - DEV 5 - DeviceKey: \Registry\Machine\System\CurrentControlSet\Control\Video\{674CA461-FAB1-44C5-BB14-5ED2DFBA2C37}\0005
01:16:54 | 50 >> - DEV 6 - DeviceID: PCI\VEN_8086&DEV_193D&SUBSYS_07B11028&REV_09
01:16:54 | 51 >> - DEV 6 - DeviceName: \\.\DISPLAY7
01:16:54 | 52 >> - DEV 6 - DeviceString: Intel(R) Iris(TM) Pro Graphics P580
01:16:54 | 53 >> - DEV 6 - DeviceKey: \Registry\Machine\System\CurrentControlSet\Control\Video\{674CA461-FAB1-44C5-BB14-5ED2DFBA2C37}\0006
01:16:54 | 54 >> - DEV 7 - DeviceID:
01:16:54 | 55 >> - DEV 7 - DeviceName: \\.\DISPLAYV1
01:16:54 | 56 >> - DEV 7 - DeviceString: RDPDD Chained DD
01:16:54 | 57 >> - DEV 7 - DeviceKey: \Registry\Machine\System\CurrentControlSet\Control\Video\{DEB039CC-B704-4F53-B43E-9DD4432FA2E9}\0000
01:16:54 | 58 >> - DEV 8 - DeviceID:
01:16:54 | 59 >> - DEV 8 - DeviceName: \\.\DISPLAYV2
01:16:54 | 60 >> - DEV 8 - DeviceString: RDP Encoder Mirror Driver
01:16:54 | 61 >> - DEV 8 - DeviceKey: \Registry\Machine\System\CurrentControlSet\Control\Video\{42cf9257-1d96-4c9d-87f3-0d8e74595f78}\0000
01:16:54 | 62 >> - DEV 9 - DeviceID:
01:16:54 | 63 >> - DEV 9 - DeviceName: \\.\DISPLAYV3
01:16:54 | 64 >> - DEV 9 - DeviceString: RDP Reflector Display Driver
01:16:54 | 65 >> - DEV 9 - DeviceKey: \Registry\Machine\System\CurrentControlSet\Control\Video\{b043b95c-5670-4f10-b934-8ed0c8eb59a8}\0000
01:16:58 | 66 >> Found 2 OpenCL-capable platform.
01:16:58 | 67 >> Found 1 OpenCL-capable devices for platform Intel(R) OpenCL.
01:16:58 | 68 >> Found 2 OpenCL-capable devices for platform AMD Accelerated Parallel Processing.
01:17:00 | 69 >> - Device ID string (0): PCI\VEN_8086&DEV_193D&SUBSYS_07B11028&REV_09
01:17:00 | 70 >> - Display device string (0): Intel(R) Iris(TM) Pro Graphics P580
01:17:00 | 71 >> Detected graphics cards and GPUs:
01:17:00 | 72 >> - GPU 1: Intel(R) Iris(TM) Pro Graphics P580
01:17:00 | 73 >> ----> DeviceID: 8086-193D - SubdeviceID: 1028- 7B1 - RevisionID:  9
01:17:00 | 74 >> ----> Config: cores:72, TMUs:0, ROPs:0
01:17:00 | 75 >> ----> TDP: 0W
01:17:00 | 76 >> ----> Graphics driver: 21.20.16.4574
01:17:01 | 77 >> Could not find nvcuda.dll.
01:17:01 | 78 >> GPU Caps Viewer startup ok.
01:17:01 | 79 >> Checking for new version...
01:17:01 | 80 >> Unable to connect to www.oZone3D.Net. Check for update failed.
=================================================================================================

PeterYS

  • Newbie
  • *
  • Posts: 8
    • View Profile
Re: GPU Caps Viewer 1.34.x.x released
« Reply #7 on: March 31, 2017, 11:55:32 AM »
The new version of GPU Caps Viewer is available.

More information and dowmload links:
http://www.geeks3d.com/20170327/gpu-caps-viewer-1-34-0-released/

When I run GPUCapsViewer v1.34.0 3D Demos the OpenCL demos on Win7, it would pop out error “OpenCL GPU not supported on the selected platform”. Then I switched to “OpenCL” sheet, its default setting is “1: Intel(R) OpenCL”. After changed manually to “2. AMD Accelerated Parallel Processing”, the OpenCL demos could run successfully.
But on Win10 OS, the GPUCapsViewer OpenCL demos didn’t need this manual setting, why?

The OpenCL default setting is Intel(R) OpenCL like below pic.

When run 3D Demos the OpenCL demos on Win7, it would pop out error “OpenCL GPU not supported on the selected platform”.


Then switched to “OpenCL” sheet, changed manually to “2. AMD Accelerated Parallel Processing”.

OpenCL demos could run successfully.


But on Win10 OS, the GPUCapsViewer OpenCL demos didn’t need this manual setting, why?

Stefan

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 4067
    • View Profile
Re: GPU Caps Viewer 1.34.x.x released
« Reply #8 on: March 31, 2017, 09:36:02 PM »
Just a heads-up: Windows 10 Creators Update annoys you now with a popup


JeGX

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1266
    • View Profile
    • Geeks3D.com
Re: GPU Caps Viewer 1.34.x.x released
« Reply #9 on: April 01, 2017, 10:48:46 AM »
Update log file of AMD WX 7100
=================================================================================================
01:16:54 | 26 >> - DEV 0 - DeviceID: PCI\VEN_8086&DEV_193D&SUBSYS_07B11028&REV_09
01:16:54 | 27 >> - DEV 0 - DeviceName: \\.\DISPLAY1
01:16:54 | 28 >> - DEV 0 - DeviceString: Intel(R) Iris(TM) Pro Graphics P580
01:16:54 | 29 >> - DEV 0 - DeviceKey: \Registry\Machine\System\CurrentControlSet\Control\Video\{674CA461-FAB1-44C5-BB14-5ED2DFBA2C37}\0000
01:16:54 | 30 >> - DEV 1 - DeviceID: PCI\VEN_8086&DEV_193D&SUBSYS_07B11028&REV_09
01:16:54 | 31 >> - DEV 1 - DeviceName: \\.\DISPLAY2
01:16:54 | 32 >> - DEV 1 - DeviceString: Intel(R) Iris(TM) Pro Graphics P580
01:16:54 | 33 >> - DEV 1 - DeviceKey: \Registry\Machine\System\CurrentControlSet\Control\Video\{674CA461-FAB1-44C5-BB14-5ED2DFBA2C37}\0001
01:16:54 | 34 >> - DEV 2 - DeviceID: PCI\VEN_8086&DEV_193D&SUBSYS_07B11028&REV_09
01:16:54 | 35 >> - DEV 2 - DeviceName: \\.\DISPLAY3
01:16:54 | 36 >> - DEV 2 - DeviceString: Intel(R) Iris(TM) Pro Graphics P580
01:16:54 | 37 >> - DEV 2 - DeviceKey: \Registry\Machine\System\CurrentControlSet\Control\Video\{674CA461-FAB1-44C5-BB14-5ED2DFBA2C37}\0002
01:16:54 | 38 >> - DEV 3 - DeviceID: PCI\VEN_8086&DEV_193D&SUBSYS_07B11028&REV_09
01:16:54 | 39 >> - DEV 3 - DeviceName: \\.\DISPLAY4
01:16:54 | 40 >> - DEV 3 - DeviceString: Intel(R) Iris(TM) Pro Graphics P580
01:16:54 | 41 >> - DEV 3 - DeviceKey: \Registry\Machine\System\CurrentControlSet\Control\Video\{674CA461-FAB1-44C5-BB14-5ED2DFBA2C37}\0003
01:16:54 | 42 >> - DEV 4 - DeviceID: PCI\VEN_8086&DEV_193D&SUBSYS_07B11028&REV_09
01:16:54 | 43 >> - DEV 4 - DeviceName: \\.\DISPLAY5
01:16:54 | 44 >> - DEV 4 - DeviceString: Intel(R) Iris(TM) Pro Graphics P580
01:16:54 | 45 >> - DEV 4 - DeviceKey: \Registry\Machine\System\CurrentControlSet\Control\Video\{674CA461-FAB1-44C5-BB14-5ED2DFBA2C37}\0004
01:16:54 | 46 >> - DEV 5 - DeviceID: PCI\VEN_8086&DEV_193D&SUBSYS_07B11028&REV_09
01:16:54 | 47 >> - DEV 5 - DeviceName: \\.\DISPLAY6
01:16:54 | 48 >> - DEV 5 - DeviceString: Intel(R) Iris(TM) Pro Graphics P580
01:16:54 | 49 >> - DEV 5 - DeviceKey: \Registry\Machine\System\CurrentControlSet\Control\Video\{674CA461-FAB1-44C5-BB14-5ED2DFBA2C37}\0005
01:16:54 | 50 >> - DEV 6 - DeviceID: PCI\VEN_8086&DEV_193D&SUBSYS_07B11028&REV_09
01:16:54 | 51 >> - DEV 6 - DeviceName: \\.\DISPLAY7
01:16:54 | 52 >> - DEV 6 - DeviceString: Intel(R) Iris(TM) Pro Graphics P580
01:16:54 | 53 >> - DEV 6 - DeviceKey: \Registry\Machine\System\CurrentControlSet\Control\Video\{674CA461-FAB1-44C5-BB14-5ED2DFBA2C37}\0006
01:16:54 | 54 >> - DEV 7 - DeviceID:
01:16:54 | 55 >> - DEV 7 - DeviceName: \\.\DISPLAYV1
01:16:54 | 56 >> - DEV 7 - DeviceString: RDPDD Chained DD
01:16:54 | 57 >> - DEV 7 - DeviceKey: \Registry\Machine\System\CurrentControlSet\Control\Video\{DEB039CC-B704-4F53-B43E-9DD4432FA2E9}\0000
01:16:54 | 58 >> - DEV 8 - DeviceID:
01:16:54 | 59 >> - DEV 8 - DeviceName: \\.\DISPLAYV2
01:16:54 | 60 >> - DEV 8 - DeviceString: RDP Encoder Mirror Driver
01:16:54 | 61 >> - DEV 8 - DeviceKey: \Registry\Machine\System\CurrentControlSet\Control\Video\{42cf9257-1d96-4c9d-87f3-0d8e74595f78}\0000
01:16:54 | 62 >> - DEV 9 - DeviceID:
01:16:54 | 63 >> - DEV 9 - DeviceName: \\.\DISPLAYV3
01:16:54 | 64 >> - DEV 9 - DeviceString: RDP Reflector Display Driver
01:16:54 | 65 >> - DEV 9 - DeviceKey: \Registry\Machine\System\CurrentControlSet\Control\Video\{b043b95c-5670-4f10-b934-8ed0c8eb59a8}\0000

Thanks for the log. That's what I thought, the AMD GPU is not listed in the active Windows adapters. Actually I have the same problem with a notebook that has an Intel GPU + AMD GPU: GPU Caps Viewer shows the Intel GPU only. I'm investigating about this issue... I let you know asap.

JeGX

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1266
    • View Profile
    • Geeks3D.com
GPU Caps Viewer 1.34.1.x released
« Reply #10 on: April 01, 2017, 04:33:33 PM »
I think I fixed the bug with Radeon GPUs. Try the new version 1.34.1.0:

http://www.geeks3d.com/20170327/gpu-caps-viewer-1-34-0-released/#20170401

On my notebook (a Lenovo ThinkPad E460 with an Intel HD 520 + Radeom R7 M360), the R7 M360 is now properly detected by GPU Caps.

PeterYS

  • Newbie
  • *
  • Posts: 8
    • View Profile
Re: GPU Caps Viewer 1.34.x.x released
« Reply #11 on: April 02, 2017, 04:52:30 PM »
When I run GPUCapsViewer v1.34.0 3D Demos the OpenCL demos on Win7, it would pop out error “OpenCL GPU not supported on the selected platform”. Then I switched to “OpenCL” sheet, its default setting is “1: Intel(R) OpenCL”. After changed manually to “2. AMD Accelerated Parallel Processing”, the OpenCL demos could run successfully.
But on Win10 OS, the GPUCapsViewer OpenCL demos didn’t need this manual setting, why?

The OpenCL default setting is Intel(R) OpenCL like below pic.

When run 3D Demos the OpenCL demos on Win7, it would pop out error “OpenCL GPU not supported on the selected platform”.


Then switched to “OpenCL” sheet, changed manually to “2. AMD Accelerated Parallel Processing”.

OpenCL demos could run successfully.


But on Win10 OS, the GPUCapsViewer OpenCL demos didn’t need this manual setting, why?

PeterYS

  • Newbie
  • *
  • Posts: 8
    • View Profile
Re: GPU Caps Viewer 1.34.1.x released
« Reply #12 on: April 05, 2017, 12:20:51 PM »
I think I fixed the bug with Radeon GPUs. Try the new version 1.34.1.0:

http://www.geeks3d.com/20170327/gpu-caps-viewer-1-34-0-released/#20170401

On my notebook (a Lenovo ThinkPad E460 with an Intel HD 520 + Radeom R7 M360), the R7 M360 is now properly detected by GPU Caps.

Thanks JeGX. We also got PASS result with new version 1.34.1.0.

But still have another problem.

When I run GPUCapsViewer v1.34.0 3D Demos the OpenCL demos on Win7, it would pop out error “OpenCL GPU not supported on the selected platform”. Then I switched to “OpenCL” sheet, its default setting is “1: Intel(R) OpenCL”. After changed manually to “2. AMD Accelerated Parallel Processing”, the OpenCL demos could run successfully.
But on Win10 OS, the GPUCapsViewer OpenCL demos didn’t need this manual setting, why?

I posted the problem on reply 11#, need your help to check this issue.

Thanks,

JeGX

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1266
    • View Profile
    • Geeks3D.com
Re: GPU Caps Viewer 1.34.x.x released
« Reply #13 on: April 14, 2017, 04:42:16 PM »
To be honest, I have currently no idea  :(
All my test systems are now on Windows 10 and I can't quickly test on Win7.

All I can say is that if you have several OpenCL-capable GPUs, you have to select the current OpenCL GPU in the OpenCL tab before running an OpenCL test.

JeGX

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1266
    • View Profile
    • Geeks3D.com
GPU Caps Viewer 1.34.2.0 released
« Reply #14 on: April 14, 2017, 04:43:53 PM »
GPU Caps Viewer 1.34.2.0 released with TITAN Xp support:

http://www.geeks3d.com/20170327/gpu-caps-viewer-1-34-0-released/#20170414

JeGX

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1266
    • View Profile
    • Geeks3D.com
GPU Caps Viewer 1.34.2.1 released
« Reply #15 on: April 16, 2017, 01:20:25 PM »
GPU Caps Viewer 1.34.2.1 is available. More information and downloads:

http://www.geeks3d.com/20170327/gpu-caps-viewer-1-34-0-released/#20170416

Stefan

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 4067
    • View Profile
Re: GPU Caps Viewer 1.34.2.1 released
« Reply #16 on: April 17, 2017, 04:12:00 PM »
GPU Caps Viewer 1.34.2.1 is available.

VK-Z output is blanked now on my rig as mentioned on the frontpage by an other user.



JeGX

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1266
    • View Profile
    • Geeks3D.com
Re: GPU Caps Viewer 1.34.2.1 released
« Reply #17 on: April 18, 2017, 01:37:57 PM »

VK-Z output is blanked now on my rig as mentioned on the frontpage by an other user.


I see two possible explanations:

1/ the vkz.exe has been deleted by your antivirus

2/ vkz.exe is there but is not able to update the vkz.txt file. In that case, try to start GPU Caps Viewer with admin rights and let me know.

 

Stefan

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 4067
    • View Profile
Re: GPU Caps Viewer 1.34.2.1 released
« Reply #18 on: April 18, 2017, 04:47:54 PM »

VK-Z output is blanked now on my rig as mentioned on the frontpage by an other user.


I see two possible explanations:

1/ the vkz.exe has been deleted by your antivirus

2/ vkz.exe is there but is not able to update the vkz.txt file. In that case, try to start GPU Caps Viewer with admin rights and let me know.
VKZ works fine with Windows Defender. I always launch GPU Caps Viewer with admin rights.
Anyway i re-checked today and the output was there again without changing anything.I keep an eye on that...

JeGX

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1266
    • View Profile
    • Geeks3D.com
Re: GPU Caps Viewer 1.34.2.1 released
« Reply #19 on: April 18, 2017, 04:54:14 PM »
Anyway i re-checked today and the output was there again without changing anything.I keep an eye on that...

So probably a bug in GPU Caps Viewer...