MSI Afterburner 4.1.1 is around the corner ;)

Discussion in 'MSI AfterBurner Application Development Forum' started by Unwinder, Apr 9, 2015.

  1. Rich_Guy

    Rich_Guy Ancient Guru

    Messages:
    12,705
    Likes Received:
    676
    GPU:
    MSI 2070S X-Trio
    Just updated, thanks Unwinder :)
     
  2. Unwinder

    Unwinder Moderator Staff Member

    Messages:
    15,663
    Likes Received:
    3,123
    It should be already supported.
     
  3. Unwinder

    Unwinder Moderator Staff Member

    Messages:
    15,663
    Likes Received:
    3,123
    Probably it has some point you simply don't see? Profiles allow you to override just _some_ of database settings, you cannot use them to perform full calibration of voltage controller for a specific card. Profiles not intended for redistribution and cannot be redistributed, they are tied to existing database settings and specific PC configuration. Databases are aimed to be redistributed and to work on any card.

    Nope, you haven't got it right.
    That doesn't work for your card exactly because of the things stated above. Just think a bit: you tried to map MVDDC and PEXVDD to exactly the same chip, how do you imagine voltage control core to guess which UP6262 output is MVDDC and which is PEXVDD. Your database is incomplete, it lacks this info.
    It also lack R1 resistor resistance, which is required to calibrate UP6262.
    Those settings need to be added to the database you've created:

    MVDDC_uP6262_R1 = 1000
    MVDDC_uP6262_Output = 0
    PEXVDD_uP6262_R1 = 1000
    PEXVDD_uP6262_Output = 1

    Nope, sorry. Direct access to registers on NV is obsolete and no longer required. NVAPI cover this functionality 100%. I keep it on AMD cards just because AMD ADL API is still terrible to direct access to AMD GPU is still required to access I2C devices.
     
    Last edited: May 29, 2015
  4. Unwinder

    Unwinder Moderator Staff Member

    Messages:
    15,663
    Likes Received:
    3,123
    If you mean regs info from NV15 BIOS sources then I have it. If it is something different then it would be interesting to look at it, thanks.
     

  5. Unwinder

    Unwinder Moderator Staff Member

    Messages:
    15,663
    Likes Received:
    3,123
    Here is early draft of hardware database format reference. I'm still working on it:

    Hardware database format reference v1.0

    1. HARDWARE DATABASE CONCEPTS 2
    2. HARDWARE DATABASE FORMAT 2
    2.1. [VEN_XXXX&DEV_XXXX&SUBSYS_XXXXXXXX&REV_XX] SECTION FORMAT 2
    2.1.1. CHL8214 voltage controller 3
    2.1.2. CHL8228 voltage controller 3
    2.1.3. CHL8266 voltage controller 4
    2.1.4. CHL8318 voltage controller 4
    2.1.5. IR3567B voltage controller 4
    2.1.6. L6788A voltage controller 4
    2.1.7. NCP4206 voltage controller 4
    2.1.8. NCP81022 voltage controller 4
    2.1.9. UP1637 voltage controller 4
    2.1.10. UP6204 voltage controller 5
    2.1.11. UP6208 voltage controller 5
    2.1.12. UP6218 voltage controller 5
    2.1.13. UP6262 voltage controller 5
    2.1.14. UP6266 voltage controller 5
    2.1.15. VT1165 voltage controller 5
    2.1.16. VT1556 voltage controller 6
    2.1.17. Generic voltage controller 6
    3. HELPER TOOLS 6
    3.1. I2C DUMP TOOL 6
    3.2. I2C READ/WRITE CONSOLE 6
    4. COMMON DATABASE CREATION HINTS AND TRICKS 7

    1. Hardware database concepts

    MSI Afterburner uses hardware databases concepts to implement voltage control support on a wide range of graphics cards and at the same time keep extremely fast and efficient application startup performance. Database concepts mean that each voltage control capable graphics card supported by MSI Afterburner is being uniquely identified inside the application by personal entry in hardware database. The database entry specific to each card define exact model of voltage controller, define controller’s unique hardware location address and provide full set of additional calibration information specific to the voltage controller model. So MSI Afterburner doesn’t need to perform full hardware scanning, it doesn’t need to perform heuristic detection of all possible controllers to select proper voltage control codepath. Such approach gives software voltage control layer the maximum safety, reduces the risk of incorrect detection of voltage controller model to zero and gives MSI Afterburner huge advantage in application startup performance comparing to tools performing full hardware scan at each startup. However, database approach doesn’t allow the application to control voltage on unknown cards with non-reference voltage control circuit.
    We ship MSI Afterburner with hardware databases providing voltage control support on 100% reference design AMD and NVIDIA graphics cards and on custom design MSI cards labeled with “Voltage control” logo. However, rich set of voltage controllers supported by MSI Afterburner core allows implementing voltage control support on many custom design cards from third party hardware vendors. For example, custom design ASUS GTX 980 STRIX or EGVA GTX 780 Classified series cards use the same voltage controllers as MSI Lightning series graphics cards, so it is possible to add such custom design ASUS and EVGA to the database and unlock voltage control for it. We don’t include such cards into official databases distributed with application, however we introduce original concepts of third party hardware database, which can be downloaded separately and attached to our application to extend voltage control functionality on third party custom design graphics cards. Third party hardware database format is open, so enthusiasts can add new cards to it and share the result with the community. Please follow this guide if you are going to edit third party hardware database.

    2. Hardware database format

    Third party hardware database is ASCII text file defining independent voltage control scenarios for different models of graphics cards. The database must have “;OEM” signature in the very beginning, otherwise the application won’t start and display error telling you that some components are missing or corrupted. The database format is derived from standard INI file format, so it is composed of multiple sections containing different fields. Each section inside the database identifies unique graphics card model or the set of similar models, if wildcards are used in the section name. Graphics card section names have the following format:

    [VEN_XXXX&DEV_XXXX&SUBSYS_XXXXXXXX&REV_XX]

    where VEN_XXXX part is graphics card vendor ID, DEV_XXXX part is graphics card device ID, SUBSYS_XXXXXXXX part is graphics card subsystem ID and REV_XX part is graphics card revision number.
    Vendor ID includes 4 hexadecimal digits, e.g. VEN_10DE for NVIDIA graphics card. Device ID includes 4 hexadecimal digits, e.g. DEV_1004 for NVIDIA GeForce GTX 780. Subsystem ID includes 8 hexadecimal digits and defines vendor specific submodel name, e.g. SUBSYS_17883842 for EVGA GTX 780 Classified. Revision number includes 2 hexadecimal digits, however different revisions of the same model normally use the same voltage controller, so it is recommended to avoid specifying revision directly in the section name and use wildcard symbol “?” instead to define one section for all possible revisions, e.g. REV_??. Wildcard symbol can be also used to define one section for a set of graphics cards models if necessary, for example [VEN_10DE&DEV_1004&SUBSYS_????3842&REV_??] section define settings for all possible submodels of EVGA GTX 780 series graphics cards. Use wildcards with caution and only when it is really necessary, for example [VEN_10DE&DEV_1004&SUBSYS_????????&REV_??] section define settings for all NVIDIA GeForce GTX 780 series cards, so specifying such section inside third party database will effectively redefine MSI Afterburner’s internal database settings for reference design NVIDIA GeForce GTX 780 series graphics cards.
    You may easily extract section name for your graphics card by clicking <i> button in MSI Afterburner, each GPU GUID displayed in MSI Afterburner information window is exactly what you are searching for.

    2.1. [VEN_XXXX&DEV_XXXX&SUBSYS_XXXXXXXX&REV_XX] section format

    This section defines settings for the graphics card model uniquely identified by section name or the set of graphics card models if the section name includes wildcard symbols. The settings include optional graphics card model name, voltage controller model, controller hardware location address and other helper settings specific to voltage controller model. For example:

    [VEN_1002&DEV_6798&SUBSYS_99991043&REV_??]

    Desc = ASUS ARES II
    VDDC_CHL8228_Detection = 6:30h
    VDDC_CHL8228_Defaults = C6 9F
    VDDC_CHL8228_VIDReadback = 1
    MVDDC_CHL8228_Detection = 6:30h
    MVDDC_CHL8228_Defaults = CD BF
    MVDDC_CHL8228_VIDReadback = 1

    Desc field is optional and it can be specified to display custom name for a graphics card in MSI Afterburner GUI, e.g. ASUS ARES II in this example. If this field is not specified, MSI Afterburner will display graphics card name as it is reported by Windows. Please keep in mind that graphics card name is displayed in limited space in some MSI Afterburner skins, so try to keep it as compact as it is possible and always test the result.
    VDDC_CHL8228_Detection field defines the first voltage controller detection information. Controller detection information includes voltage controller target, model and hardware location address. Voltage controller target in this example is VDDC, which means that we’re defining settings for core voltage controller. Voltage controller model is CHL8228, and voltage controller location is I2C bus 6, device address 30h.
    VDDC_CHL8228_Defaults field defines CHL8228 controller specific settings for core voltage controller, in this example we’re telling MSI Afterburner that core voltage is adjusted by CHL8228 voltage control loop 1 VID register C6 and default VID for this register is equal to 9F.
    VDDC_CHL8228_VIDReadback field defines additional CHL8228 controller specific settings for core voltage controller, we’re telling MSI Afterburner that we want to see VID readback (i.e. programmed target voltage) on core voltage monitoring graph instead of real voltage readback.
    MVDDC_CHL8228_Detection field defines the second voltage controller detection information. Controller detection information includes voltage controller target, model and hardware location address. Voltage controller target in this example is MVDDC, which means that we’re defining settings for memory voltage controller. Voltage controller model is CHL8228, and voltage controller location is I2C bus 6, device address 30h.
    MVDDC_CHL8228_Defaults field defines CHL8228 controller specific settings for memory voltage controller, in this example we’re telling MSI Afterburner that memory voltage is adjusted by CHL8228 voltage control loop 2 VID register CD and default VID for this register is equal to BF.
    MVDDC_CHL8228_VIDReadback field defines additional CHL8228 controller specific settings for core voltage controller, we’re telling MSI Afterburner that we want to see VID readback (i.e. programmed target voltage) on memory voltage monitoring graph instead of real voltage readback.

    Voltage controller detection fields are the only unified fields for all models of controllers. Detection fields have the following format:

    <target>_<model>_Detection = [<i2c_bus_filter>:]<i2c_device_filter>

    where <target> is voltage controller target, which can be set to VDDC (for core voltage controller detection), MVDDC (for memory voltage controller detection), VDDCI or PEXVDD (for auxiliary voltage controller detection). <model> is a model of voltage controller, which can be set to CHL8214, CHL8228, CHL8266, CHL8318, IR3567B, L6788A, NCP4206, NCP81022, UP1637, UP6204, UP6208, UP6218, UP6262, UP6266, VT1165, VT1556 or Generic. <i2c_bus_filter> specify the range of I2C buses where the controller can reside, for example it can be set to “3” if the controller can be located on I2C bus 3 only, “3-5” if it can be in bus 3 to 5 range or “3,5” if it can be on bus 3 or 5. <i2c_device_filter> specify the range of 7-bit I2C device addresses where the controller can reside. Similar to bus filter, you can specify exact device address, range of addresses or a few comma separated addresses. If you don’t specify bus filter and use device filter only, MSI Afterburner will search for the controller on all I2C buses available on this graphics card until matching I2C device is found. In most cases it is safe to specify device filter only, however, some controllers (e.g. UP6262) have no internal identification register and reside in the same address space as monitor DDC. So in this case it is absolutely necessary to specify both bus and device filters in order to detect the controller properly.
    It is allowed to specify a few voltage controller detection fields for the same voltage controller target (e.g. for VDDC) with different voltage controller models inside one section if some graphics card model can use different models of voltage controllers. For example reference design ATI RADEON 4870 series cards can use either VT1165 or L6788A to control core voltage. So database section for this graphics card contains both VDDC_VT1165_Detection and VDDC_L6788A_Defaults fields.
    The rest voltage controller related fields, such as VDDC_CHL8228_Defaults or VDDC_CHL8228_VIDReadback mentioned in this example are specific to model of voltage controller and will be discussed further in controller model specific chapters.

    2.1.1. CHL8214 voltage controller

    This controller can reside in full 7-bit I2C device address range. Controller is identified by register 9Ch (must be equal to 43h) and register 8Ch (must be equal to 16h). Model specific settings for CHL8214 include the following:

    <target>_CHL8214_Defaults = <vid_register_address> <default_vid>

    where <vid_register_address> is the address of VID register controlling voltage for 3D performance state, the address can be in 43h - 4Ah range for voltage loop 1 and in 4Bh - 4Eh range for voltage loop 2.
    <default_vid> specify default value for previously defined VID register.

    2.1.2. CHL8228 voltage controller

    This controller can reside in full 7-bit I2C device address range. Controller is identified by register 8Ch (can be equal to 03h, 04h or 0Eh). Model specific settings for CHL8228 include the following:

    <target>_CHL8214_Defaults = <vid_register_address> <default_vid>

    where <vid_register_address> is the address of VID register controlling voltage for 3D performance state, the address can be in C6h - C9h range for voltage loop 1 and in CAh - CDh range for voltage loop 2.
    <default_vid> specify default value for previously defined VID register.

    <target>_CHL8228_VIDReadback = <readback_mode>

    where <readback_mode> is controlling VID readback mode. When it is set to 1 VID readback mode is enabled and the voltage monitored by this controller is a target voltage programmed by VID. When it is set to 0 VID readback mode is disabled and real voltage is being monitored by this controller.

    2.1.3. CHL8266 voltage controller

    This controller can reside in fixed 46h device address only. The controller has no identification registers and no model specific settings.

    2.1.4. CHL8318 voltage controller

    This controller can reside in fixed 42h, 44h, 46h, 70h, 72h, 74h or 76h device addresses only. The controller has no identification registers. Model specific settings for CHL8318 include the following:

    <target>_CHL8318_Type = <control_type>

    where <control_type> can be set to 0 for fixed output voltage or 1 for applying offset to output voltage.

    2.1.5. IR3567B voltage controller

    This controller can reside in 28h - 46h device address range only. The controller is identified by register 92h (must be equal to 43h). Model specific settings for IR3567B include the following:

    <target>_IR3567B_Type = <control_type>

    where <control_type> can be set to 0 for fixed output voltage override or 1 for applying offset to output voltage.

    <target>_IR3567B_Output = <output_index>

    where <output_index> can be set to 0 to control the first voltage loop or 1 to control the second voltage loop. This setting is optional, MSI Afterburner defaults to the first loop if it is not specified.

    2.1.6. L6788A voltage controller

    This controller can reside in fixed 40h device address only. The controller is identified by register D0h (must be equal to 53h). Model specific settings for L6788A include the following:

    <target>_L6788A_Defaults = <vid_register_address> <default_vid>

    where <vid_register_address> is the address of VID register controlling voltage for 3D performance state, the address can be in D4h – D7h range.
    <default_vid> specify default value for previously defined VID register.

    2.1.7. NCP4206 voltage controller

    This controller can reside in fixed 20h device address only. The controller is identified by register 99h (must be equal to 41h). The controller has no model specific settings.

    2.1.8. NCP81022 voltage controller

    This controller can reside in 20h - 27h device address range only. The controller is identified by 2-byte register 99h (must be equal to 001Ah) and 2-byte register 9Ah (must be equal to 1022h). The controller has no model specific settings.

    2.1.9. UP1637 voltage controller

    This controller can reside in 46h - 47h device address range only. The controller is identified by register D0h (must be equal to 1Eh). Model specific settings for UP1637 include the following:

    <target>_UP1637_Defaults = <vid_register_address> <default_vid>

    where <vid_register_address> is the address of VID register controlling voltage for 3D performance state, the address can be in D4h – D7h range.
    <default_vid> specify default value for previously defined VID register.

    2.1.10. UP6204 voltage controller

    This controller can reside in fixed 40h device address only. The controller is identified by register D0h (must be equal to 11h). Model specific settings for UP6204 include the following:

    <target>_UP6204_Defaults = <vid_register_address> <default_vid>

    where <vid_register_address> is the address of VID register controlling voltage for 3D performance state, the address can be in D4h – D7h range.
    <default_vid> specify default value for previously defined VID register.

    2.1.11. UP6208 voltage controller

    This controller can reside in 45h - 47h device address range only. The controller is identified by register B2h (must be equal to 01h) and register 0Fh (must be equal to 11h). The controller has no model specific settings.

    2.1.12. UP6218 voltage controller

    This controller can reside in 45h - 47h device address range only. The controller is identified by register B2h (must be equal to 0Eh) and register 1Dh (lower 6 bits must be equal to 02h or 03h). The controller has no model specific settings.

    2.1.13. UP6262 voltage controller

    This controller can reside in fixed 30h device address only. The controller has no identification registers. Model specific settings for UP6262 include the following:

    <target>_UP6262_Output = <output_index>

    where <output_index> can be set to 0 to control the first voltage loop or 1 to control the second voltage loop. This setting is optional, MSI Afterburner defaults to the first loop if it is not specified.

    <target>_UP6262_R1 = <r1_resistance>

    where <r1_resistance> specify R1 resistor resistance (in Ohm) for voltage control loop. This value is set to zero by default and must be set to non-zero value in the database.

    2.1.14. UP6266 voltage controller

    This controller can reside in 51h - 53h device address range only. The controller is identified by register D0h (must be equal to 12h). Model specific settings for UP6266 include the following:

    <target>_UP6266_Defaults = <vid_register_address> <default_vid>

    where <vid_register_address> is the address of VID register controlling voltage for 3D performance state, the address can be in D4h – D7h range.
    <default_vid> specify default value for previously defined VID register.

    2.1.15. VT1165 voltage controller

    This controller can reside in 70h - 71h device address range only. The controller is identified by register 1Ah (must be equal to 0Ah). Model specific settings for VT1165 include the following:

    <target>_VT1165_Defaults = <vid_register_address> <default_vid>

    where <vid_register_address> is the address of VID register controlling voltage for 3D performance state, the address can be in 15h – 18h range.
    <default_vid> specify default value for previously defined VID register.

    2.1.16. VT1556 voltage controller

    This controller can reside in 70h - 73h device address range only. The controller is identified by register 1Ah (must be equal to 02h). Model specific settings for VT1556 include the following:

    <target>_VT1556_Defaults = <vid_register_address> <default_vid>

    where <vid_register_address> is the address of VID register controlling voltage for 3D performance state, the address can be in 94h – 9Bh range.
    <default_vid> specify default value for previously defined VID register.

    2.1.17. Generic voltage controller

    Generic is a special fake controller name allowing MSI Afterburner to use display driver’s VID based voltage control API instead of direct access to specific voltage controller. In this case voltage control range is seriously limited by display driver, but this mode is the only case for many reference design cards with cost down voltage controllers without I2C programming support. Voltage controller detection field for this controller supports only VDDC as the target and uses simple boolean variable to enable/disable it instead of I2C bus and device location info, e.g.

    VDDC_Generic_Detection = 1

    enables voltage control via display driver. Generic voltage control has the lowest priority, so when you specify generic and some other controller models for the same card MSI Afterburner first try to use direct access to other controllers and fall back to generic controller only if no other controllers found onboard.

    3. Helper tools

    MSI Afterburner contains built-in helper tools aimed to simplify the process of hardware database creation and allowing you to detect and diagnose voltage controller before adding it to hardware database. The next chapters discuss helper tools in details.

    3.1. I2C dump tool

    I2C dump tool is intended for automated scanning of all devices residing on all I2C buses of each GPU installed in the system. The first register of each scanned I2C device is being polled, if the device reply to polling then dump of 256 byte registers is saved into the dump. I2C dump tool is activated via the command line with the following switch:

    MSIAfterburner.exe /i2cd [<i2c_bus>[,<i2c_device>]]

    where <i2c_bus> is I2C bus number and <i2c_device> is 7-bit I2C device address. <i2c_bus> and <i2c_device> allow scanning required device address on all I2C buses or desired I2C bus only. When I2C bus and device address are not specified I2C dump tool is scanning all available I2C buses and 7-bit I2C address range starting from 00h up to 4Fh inclusive.

    3.2. I2C read/write console

    I2C read / write console is intended for reading registers from or writing registers to a specific I2C device. You can read data from a register of specific I2C device using the following command line switch:

    MSIAfterburner.exe /ri<i2c_bus>,<i2c_device>,<register>

    where <i2c_bus> is I2C bus number, <i2c_device> is 7-bit I2C device address and <register> is register address
    In addition to read operations you may also write data to a register of specific I2C device using the following command line switch:

    MSIAfterburner.exe /wi<i2c_bus>,<i2c_device>,<register>,<data>

    where <i2c_bus> is I2C bus number, <i2c_device> is 7-bit I2C device address, <register> is register address and <data> is a data to be written to the register
    Besides direct data write there a few additional operations, allowing you to read data from I2C device register, apply simple logical operations (AND, OR or XOR) to it and write it back to the register. The following command line switch read register form specific I2C device, apply bitwise AND operation to it using data you specify then write it back to the register:

    MSIAfterburner.exe /ai<i2c_bus>,<i2c_device>,<register>,<data>

    Similar to the previous command, the following commands do almost the same but use bitwise OR and XOR operations instead or AND operation:

    MSIAfterburner.exe /oi<i2c_bus>,<i2c_device>,<register>,<data>
    MSIAfterburner.exe /xi<i2c_bus>,<i2c_device>,<register>,<data>

    The commands in I2C read / write console can be queued, which mean that you can perform series of read / write operations in one command. Please take a note that all commands apply to GPU selected as a master GPU in MSI Afterburner properties, however you can use GPU selection command /sg<gpu_index> before I2C read and write commands to redirect them to desired GPU. <gpu_index> is zero based and it affects all read and write commands in the line until the next GPU selection command is met.
    Also take a note that all I2C read and write commands work with 1-byte I2C device registers by default. However, you may use access mode forcing command /fm2 to force 2-byte register access mode and /fm1 command to force 1-byte register access mode back if necessary. Similar to GPU selection commands, access mode forcing command also affects all read and write commands in the line until the next access mode forcing command is met.

    4. Common database creation hints and tricks


    1. The very first thing you have to do before trying to add new card MSI Afterburner third party hardware database is to determine exact model of voltage controller chip. Some graphics card reviewers pay attention to it, for example you may find info about voltage controller model in Techpowerup reviews, e.g. this review is telling you that custom design EVGA GTX 780 Ti Classified card uses CHL8318 controller.
    http://www.techpowerup.com/reviews/EVGA/GTX_780_Ti_Classified/4.html

    2. If you cannot find info about voltage controller model in any online reviews, try to examine PCB and visually identify model of controller chip.

    3. If you identified voltage controller model and it is listed as supported by MSI afterburner in chapters 2.1.x, proceed with the next steps. If you identified voltage controller model but it is not listed as supported by MSI afterburner in chapters 2.1.x, then sadly currently you are out of luck. Some voltage controller models (e.g. RT8802A or NCP81174) are cost down controller models with no I2C support, so there are absolutely no chances to see support for such controllers in future versions of MSI Afterburner. Support for programmable controllers can be added to MSI Afterburner in future versions, but we prioritize development only for the controllers used on custom design MSI graphics cards.

    4. Use I2C dump tool to scan all I2C devices installed on your card. If you already know voltage controller model, you may use the dump to find the controller location address. Otherwise you’ll need to analyze all devices and compare it with each possible model identification info. For example, let’s assume that you know that your controller is CHL8228. Peek into the chapter about this controller. You’ll see there that CHL8228 controller may reside in any address and that it can be identified by values 03h, 04h or 0Eh in register 8Ch. Now examine all I2C devices in the dump and select device matching with our address selection (can be any in our case) and identification criterias. In our example there is only one device inside the dump located on bus 6 deivce 30h and it is our victim, because register 8Ch is indeed equal to 0Eh (row 9 contain registers 80h – 8Fh, column 13 in this row in register 8Ch):

    Scanning GPU VEN_1002&DEV_6798&SUBSYS_99991043&REV_00&BUS_3&DEV _0&FN_0...
    ...
    Scanning I2C bus 6...
    Probing device 00...
    Invalid device
    ...
    Probing device 30...
    25 CA 78 61 DB 5B 01 30 A0 08 80 00 87 7F CF 96
    A0 03 AA 06 A0 00 00 00 00 A4 89 9A 28 00 E8 A1
    28 4B DB DD 30 55 00 00 B9 B9 99 05 05 11 AA 22
    44 33 C5 00 AA 38 39 90 53 2D 00 00 00 3A 01 80
    9F CF 00 00 4B 3E 3F 3F 3F 3E 3E 3F 71 F0 F1 80
    D9 7F D9 81 D9 8B 02 1E D8 00 D0 97 BA 03 B8 20
    F0 30 F0 29 19 00 00 00 00 00 00 F8 7B 00 00 00
    00 03 00 03 51 00 CF FF 00 00 A0 EA FF 00 00 68
    D9 00 D0 4B D9 04 D0 D7 B9 FF BB 56 0E 00 01 FF
    02 07 00 00 C0 00 00 BB 00 00 12 1F 1F AD 50 00
    00 00 00 00 00 00 00 00 00 03 00 00 03 FF 9F 00
    00 00 0F 00 00 00 00 FF FF 88 88 01 0A 0A FF 88
    01 01 01 00 00 C0 9F 9F 9F 9F BF BF BF BF 01 80
    00 00 00 00 80 33 00 00 08 00 01 00 00 00 00 00
    00 00 00 15 15 00 00 00 01 00 00 00 00 01 00 00
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

    5. Keep in mind that in some cases default I2C dump may contain no data required for voltage controller identification. It can be the case if voltage controller reside in upper I2C addresses (5Fh and higher), which are not scanned by default I2C dump scanner. For example if we’re searching for CHL8318 controller and know that it can reside in fixed 70h, 72h, 74h and 76h addresses, we can scan those addresses directly with the following commands:

    MSIAfterburner.exe /i2cd,70
    MSIAfterburner.exe /i2cd,72
    MSIAfterburner.exe /i2cd,74
    MSIAfterburner.exe /i2cd,76

    In some cases I2C devices can be completely invisible to I2C dump tool because their first registers polled by the scanner of I2C dump tool can be unreadable due to their architecture specifics. For example it applies to NCP4206 voltage controllers. In this case we need to poll the controller directly via I2C read / write console. For example the following commands poll identification register 99h of NCP4206 device address 20h. We’re expecting to see 41h for NCP4206 according to info from the chapter about NCP4206 voltage controller. So, let’s assume that we poll this register and address on 2 neighbor I2C buses:

    MSIAfterburner.exe /ri3,20,99 /ri4,20,99

    And the output result is:

    I2C 03 20 99 : 41
    I2C 04 20 99 : invalid

    which means that our NCP4206 is indeed located on I2C bus 3, device address 20h
     
    Last edited: May 30, 2015
  6. Mooshan

    Mooshan Master Guru

    Messages:
    470
    Likes Received:
    0
    GPU:
    MSI Armor 1080
    Hi Alex

    Not sure if this is any help for the database, but I have a Galax 970 GTX EX OC card and here is the I2C scan, not sure if anything else is needed, can anything be added from this and can the voltage be changed?

    Scanning GPU VEN_10DE&DEV_13C2&SUBSYS_111610DE&REV_A1&BUS_1&DEV_0&FN_0...
    Scanning I2C bus 0...
    Probing device 00...
    Invalid device
    Probing device 01...
    Invalid device
    Probing device 02...
    Invalid device
    Probing device 03...
    Invalid device
    Probing device 04...
    Invalid device
    Probing device 05...
    Invalid device
    Probing device 06...
    Invalid device
    Probing device 07...
    Invalid device
    Probing device 08...
    Invalid device
    Probing device 09...
    Invalid device
    Probing device 0a...
    Invalid device
    Probing device 0b...
    Invalid device
    Probing device 0c...
    Invalid device
    Probing device 0d...
    Invalid device
    Probing device 0e...
    Invalid device
    Probing device 0f...
    Invalid device
    Probing device 10...
    Invalid device
    Probing device 11...
    Invalid device
    Probing device 12...
    Invalid device
    Probing device 13...
    Invalid device
    Probing device 14...
    Invalid device
    Probing device 15...
    Invalid device
    Probing device 16...
    Invalid device
    Probing device 17...
    Invalid device
    Probing device 18...
    Invalid device
    Probing device 19...
    Invalid device
    Probing device 1a...
    Invalid device
    Probing device 1b...
    Invalid device
    Probing device 1c...
    Invalid device
    Probing device 1d...
    Invalid device
    Probing device 1e...
    Invalid device
    Probing device 1f...
    Invalid device
    Probing device 20...
    Invalid device
    Probing device 21...
    Invalid device
    Probing device 22...
    Invalid device
    Probing device 23...
    Invalid device
    Probing device 24...
    Invalid device
    Probing device 25...
    Invalid device
    Probing device 26...
    Invalid device
    Probing device 27...
    Invalid device
    Probing device 28...
    Invalid device
    Probing device 29...
    Invalid device
    Probing device 2a...
    Invalid device
    Probing device 2b...
    Invalid device
    Probing device 2c...
    Invalid device
    Probing device 2d...
    Invalid device
    Probing device 2e...
    Invalid device
    Probing device 2f...
    Invalid device
    Probing device 30...
    00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
    10 11 12 13 14 15 16 17 18 19 1A 1B 1C 1D 1E 1F
    20 21 22 23 24 25 26 27 28 29 2A 2B 2C 2D 2E 2F
    30 31 32 33 34 35 36 37 38 39 3A 3B 3C 3D 3E 3F
    40 41 42 43 44 45 46 47 48 49 4A 4B 4C 4D 4E 4F
    50 51 52 53 54 55 56 57 58 59 5A 5B 5C 5D 5E 5F
    60 61 62 63 64 65 66 67 68 69 6A 6B 6C 6D 6E 6F
    70 71 72 73 74 75 76 77 78 79 7A 7B 7C 7D 7E 7F
    80 81 82 83 84 85 86 87 88 89 8A 8B 8C 8D 8E 8F
    90 91 92 93 94 95 96 97 98 99 9A 9B 9C 9D 9E 9F
    A0 A1 A2 A3 A4 A5 A6 A7 A8 A9 AA AB AC AD AE AF
    B0 B1 B2 B3 B4 B5 B6 B7 B8 B9 BA BB BC BD BE BF
    C0 C1 C2 C3 C4 C5 C6 C7 C8 C9 CA CB CC CD CE CF
    D0 D1 D2 D3 D4 D5 D6 D7 D8 D9 DA DB DC DD DE DF
    E0 E1 E2 E3 E4 E5 E6 E7 E8 E9 EA EB EC ED EE EF
    F0 F1 F2 F3 F4 F5 F6 F7 F8 F9 FA FB FC FD FE FF
    Probing device 31...
    Invalid device
    Probing device 32...
    Invalid device
    Probing device 33...
    Invalid device
    Probing device 34...
    Invalid device
    Probing device 35...
    Invalid device
    Probing device 36...
    Invalid device
    Probing device 37...
    98 A3 01 89 58 9A EC 77 78 54 98 0C 15 6F 79 A9
    00 00 00 00 00 98 00 00 98 00 00 00 98 00 00 00
    98 00 00 98 00 00 00 98 00 00 00 00 98 00 00 98
    00 00 00 00 00 00 00 98 00 00 00 98 00 00 00 00
    00 98 00 00 00 00 98 00 98 00 00 98 00 00 00 98
    00 00 98 00 00 00 98 00 00 00 98 00 00 98 00 00
    00 98 00 00 00 00 00 00 00 00 00 00 00 00 00 98
    00 00 00 98 00 00 98 00 00 00 98 00 00 00 98 00
    00 00 98 00 00 00 00 98 00 00 98 00 00 00 00 98
    A3 00 00 00 00 00 00 00 00 00 00 00 98 00 00 00
    00 00 00 00 00 00 00 00 98 00 00 98 00 00 00 00
    00 00 98 00 00 00 00 00 98 00 00 00 98 00 00 00
    00 00 98 00 00 00 00 00 00 00 00 00 00 00 00 98
    00 00 00 98 00 98 00 00 00 00 00 00 00 00 00 00
    98 00 00 98 00 00 00 00 98 00 00 98 00 00 00 00
    00 98 00 00 00 98 00 00 00 00 00 98 00 00 98 00
    Probing device 38...
    Invalid device
    Probing device 39...
    Invalid device
    Probing device 3a...
    2F F3 8C D2 24 00 00 00 00 00 00 00 00 00 00 00
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    93 00 10 00 00 00 00 00 00 00 00 00 00 00 00 00
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    Probing device 3b...
    Invalid device
    Probing device 3c...
    Invalid device
    Probing device 3d...
    Invalid device
    Probing device 3e...
    Invalid device
    Probing device 3f...
    Invalid device
    Probing device 40...
    Invalid device
    Probing device 41...
    Invalid device
    Probing device 42...
    Invalid device
    Probing device 43...
    Invalid device
    Probing device 44...
    Invalid device
    Probing device 45...
    Invalid device
    Probing device 46...
    Invalid device
    Probing device 47...
    Invalid device
    Probing device 48...
    Invalid device
    Probing device 49...
    Invalid device
    Probing device 4a...
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    Probing device 4b...
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    Probing device 4c...
    Invalid device
    Probing device 4d...
    Invalid device
    Probing device 4e...
    Invalid device
    Probing device 4f...
    Invalid device
    Scanning I2C bus 1...
    Probing device 00...
    Invalid device
    Probing device 01...
    Invalid device
    Probing device 02...
    Invalid device
    Probing device 03...
    Invalid device
    Probing device 04...
    Invalid device
    Probing device 05...
    Invalid device
    Probing device 06...
    Invalid device
    Probing device 07...
    Invalid device
    Probing device 08...
    Invalid device
    Probing device 09...
    Invalid device
    Probing device 0a...
    Invalid device
    Probing device 0b...
    Invalid device
    Probing device 0c...
    Invalid device
    Probing device 0d...
    Invalid device
    Probing device 0e...
    Invalid device
    Probing device 0f...
    Invalid device
    Probing device 10...
    Invalid device
    Probing device 11...
    Invalid device
    Probing device 12...
    Invalid device
    Probing device 13...
    Invalid device
    Probing device 14...
    Invalid device
    Probing device 15...
    Invalid device
    Probing device 16...
    Invalid device
    Probing device 17...
    Invalid device
    Probing device 18...
    Invalid device
    Probing device 19...
    Invalid device
    Probing device 1a...
    Invalid device
    Probing device 1b...
    Invalid device
    Probing device 1c...
    Invalid device
    Probing device 1d...
    Invalid device
    Probing device 1e...
    Invalid device
    Probing device 1f...
    Invalid device
    Probing device 20...
    Invalid device
    Probing device 21...
    Invalid device
    Probing device 22...
    Invalid device
    Probing device 23...
    Invalid device
    Probing device 24...
    Invalid device
    Probing device 25...
    Invalid device
    Probing device 26...
    Invalid device
    Probing device 27...
    Invalid device
    Probing device 28...
    Invalid device
    Probing device 29...
    Invalid device
    Probing device 2a...
    Invalid device
    Probing device 2b...
    Invalid device
    Probing device 2c...
    Invalid device
    Probing device 2d...
    Invalid device
    Probing device 2e...
    Invalid device
    Probing device 2f...
    Invalid device
    Probing device 30...
    Invalid device
    Probing device 31...
    Invalid device
    Probing device 32...
    Invalid device
    Probing device 33...
    Invalid device
    Probing device 34...
    Invalid device
    Probing device 35...
    Invalid device
    Probing device 36...
    Invalid device
    Probing device 37...
    Invalid device
    Probing device 38...
    Invalid device
    Probing device 39...
    Invalid device
    Probing device 3a...
    Invalid device
    Probing device 3b...
    Invalid device
    Probing device 3c...
    Invalid device
    Probing device 3d...
    Invalid device
    Probing device 3e...
    Invalid device
    Probing device 3f...
    Invalid device
    Probing device 40...
    Invalid device
    Probing device 41...
    Invalid device
    Probing device 42...
    Invalid device
    Probing device 43...
    Invalid device
    Probing device 44...
    Invalid device
    Probing device 45...
    Invalid device
    Probing device 46...
    Invalid device
    Probing device 47...
    Invalid device
    Probing device 48...
    Invalid device
    Probing device 49...
    Invalid device
    Probing device 4a...
    Invalid device
    Probing device 4b...
    Invalid device
    Probing device 4c...
    Invalid device
    Probing device 4d...
    Invalid device
    Probing device 4e...
    Invalid device
    Probing device 4f...
    Invalid device
    Scanning I2C bus 2...
    Probing device 00...
    Invalid device
    Probing device 01...
    Invalid device
    Probing device 02...
    Invalid device
    Probing device 03...
    Invalid device
    Probing device 04...
    Invalid device
    Probing device 05...
    Invalid device
    Probing device 06...
    Invalid device
    Probing device 07...
    Invalid device
    Probing device 08...
    Invalid device
    Probing device 09...
    Invalid device
    Probing device 0a...
    Invalid device
    Probing device 0b...
    Invalid device
    Probing device 0c...
    Invalid device
    Probing device 0d...
    Invalid device
    Probing device 0e...
    Invalid device
    Probing device 0f...
    Invalid device
    Probing device 10...
    Invalid device
    Probing device 11...
    Invalid device
    Probing device 12...
    Invalid device
    Probing device 13...
    Invalid device
    Probing device 14...
    Invalid device
    Probing device 15...
    Invalid device
    Probing device 16...
    Invalid device
    Probing device 17...
    Invalid device
    Probing device 18...
    Invalid device
    Probing device 19...
    Invalid device
    Probing device 1a...
    Invalid device
    Probing device 1b...
    Invalid device
    Probing device 1c...
    Invalid device
    Probing device 1d...
    Invalid device
    Probing device 1e...
    Invalid device
    Probing device 1f...
    Invalid device
    Probing device 20...
    Invalid device
    Probing device 21...
    Invalid device
    Probing device 22...
    Invalid device
    Probing device 23...
    Invalid device
    Probing device 24...
    Invalid device
    Probing device 25...
    Invalid device
    Probing device 26...
    Invalid device
    Probing device 27...
    Invalid device
    Probing device 28...
    Invalid device
    Probing device 29...
    Invalid device
    Probing device 2a...
    Invalid device
    Probing device 2b...
    Invalid device
    Probing device 2c...
    Invalid device
    Probing device 2d...
    Invalid device
    Probing device 2e...
    Invalid device
    Probing device 2f...
    Invalid device
    Probing device 30...
    Invalid device
    Probing device 31...
    Invalid device
    Probing device 32...
    Invalid device
    Probing device 33...
    Invalid device
    Probing device 34...
    Invalid device
    Probing device 35...
    Invalid device
    Probing device 36...
    Invalid device
    Probing device 37...
    Invalid device
    Probing device 38...
    Invalid device
    Probing device 39...
    Invalid device
    Probing device 3a...
    Invalid device
    Probing device 3b...
    Invalid device
    Probing device 3c...
    Invalid device
    Probing device 3d...
    Invalid device
    Probing device 3e...
    Invalid device
    Probing device 3f...
    Invalid device
    Probing device 40...
    Invalid device
    Probing device 41...
    Invalid device
    Probing device 42...
    Invalid device
    Probing device 43...
    Invalid device
    Probing device 44...
    Invalid device
    Probing device 45...
    Invalid device
    Probing device 46...
    Invalid device
    Probing device 47...
    Invalid device
    Probing device 48...
    Invalid device
    Probing device 49...
    Invalid device
    Probing device 4a...
    Invalid device
    Probing device 4b...
    Invalid device
    Probing device 4c...
    Invalid device
    Probing device 4d...
    Invalid device
    Probing device 4e...
    Invalid device
    Probing device 4f...
    Invalid device
    Scanning I2C bus 3...
    Probing device 00...
    Invalid device
    Probing device 01...
    Invalid device
    Probing device 02...
    Invalid device
    Probing device 03...
    Invalid device
    Probing device 04...
    Invalid device
    Probing device 05...
    Invalid device
    Probing device 06...
    Invalid device
    Probing device 07...
    Invalid device
    Probing device 08...
    Invalid device
    Probing device 09...
    Invalid device
    Probing device 0a...
    Invalid device
    Probing device 0b...
    Invalid device
    Probing device 0c...
    Invalid device
    Probing device 0d...
    Invalid device
    Probing device 0e...
    Invalid device
    Probing device 0f...
    Invalid device
    Probing device 10...
    Invalid device
    Probing device 11...
    Invalid device
    Probing device 12...
    Invalid device
    Probing device 13...
    Invalid device
    Probing device 14...
    Invalid device
    Probing device 15...
    Invalid device
    Probing device 16...
    Invalid device
    Probing device 17...
    Invalid device
    Probing device 18...
    Invalid device
    Probing device 19...
    Invalid device
    Probing device 1a...
    Invalid device
    Probing device 1b...
    Invalid device
    Probing device 1c...
    Invalid device
    Probing device 1d...
    Invalid device
    Probing device 1e...
    Invalid device
    Probing device 1f...
    Invalid device
    Probing device 20...
    Invalid device
    Probing device 21...
    Invalid device
    Probing device 22...
    Invalid device
    Probing device 23...
    Invalid device
    Probing device 24...
    Invalid device
    Probing device 25...
    Invalid device
    Probing device 26...
    Invalid device
    Probing device 27...
    Invalid device
    Probing device 28...
    Invalid device
    Probing device 29...
    Invalid device
    Probing device 2a...
    Invalid device
    Probing device 2b...
    Invalid device
    Probing device 2c...
    Invalid device
    Probing device 2d...
    Invalid device
    Probing device 2e...
    Invalid device
    Probing device 2f...
    Invalid device
    Probing device 30...
    Invalid device
    Probing device 31...
    Invalid device
    Probing device 32...
    Invalid device
    Probing device 33...
    Invalid device
    Probing device 34...
    Invalid device
    Probing device 35...
    Invalid device
    Probing device 36...
    Invalid device
    Probing device 37...
    Invalid device
    Probing device 38...
    Invalid device
    Probing device 39...
    Invalid device
    Probing device 3a...
    Invalid device
    Probing device 3b...
    Invalid device
    Probing device 3c...
    Invalid device
    Probing device 3d...
    Invalid device
    Probing device 3e...
    Invalid device
    Probing device 3f...
    Invalid device
    Probing device 40...
    78 02 2F 02 2F 01 2F 7F 7F 44 7F 44 7F 00 7F 00
    27 23 FF FF FF FF FF FF FF FF -- 00 FF FF 54 32
    78 02 2F 02 2F 01 2F 7F 7F 44 7F 44 7F 00 7F 00
    27 23 FF FF FF FF FF FF FF FF -- 00 FF FF 54 32
    78 02 2F 02 2F 01 2F 7F 7F 44 7F 44 7F 00 7F 00
    27 23 FF FF FF FF FF FF FF FF -- 00 FF FF 54 32
    78 03 2F 02 2F 01 2F 7F 7F 44 7F 44 7F 00 7F 00
    27 23 FF FF FF FF FF FF FF FF -- 00 FF FF 54 32
    78 02 2F 02 2F 01 2F 7F 7F 44 7F 44 7F 00 7F 00
    27 23 FF FF FF FF FF FF FF FF -- 00 FF FF 54 32
    78 02 2F 02 2F 01 2F 7F 7F 44 7F 44 7F 00 7F 00
    27 23 FF FF FF FF FF FF FF FF -- 00 FF FF 54 32
    78 02 2F 02 2F 01 2F 7F 7F 44 7F 44 7F 00 7F 00
    27 23 FF FF FF FF FF FF FF FF -- 00 FF FF 54 32
    78 02 2F 02 2F 01 2F 7F 7F 44 7F 44 7F 00 7F 00
    27 23 FF FF FF FF FF FF FF FF -- 00 FF FF 54 32
    Probing device 41...
    Invalid device
    Probing device 42...
    Invalid device
    Probing device 43...
    Invalid device
    Probing device 44...
    Invalid device
    Probing device 45...
    Invalid device
    Probing device 46...
    Invalid device
    Probing device 47...
    Invalid device
    Probing device 48...
    Invalid device
    Probing device 49...
    Invalid device
    Probing device 4a...
    Invalid device
    Probing device 4b...
    Invalid device
    Probing device 4c...
    Invalid device
    Probing device 4d...
    Invalid device
    Probing device 4e...
    Invalid device
    Probing device 4f...
    Invalid device
    Scanning I2C bus 4...
    Probing device 00...
    Invalid device
    Probing device 01...
    Invalid device
    Probing device 02...
    Invalid device
    Probing device 03...
    Invalid device
    Probing device 04...
    Invalid device
    Probing device 05...
    Invalid device
    Probing device 06...
    Invalid device
    Probing device 07...
    Invalid device
    Probing device 08...
    Invalid device
    Probing device 09...
    Invalid device
    Probing device 0a...
    Invalid device
    Probing device 0b...
    Invalid device
    Probing device 0c...
    Invalid device
    Probing device 0d...
    Invalid device
    Probing device 0e...
    Invalid device
    Probing device 0f...
    Invalid device
    Probing device 10...
    Invalid device
    Probing device 11...
    Invalid device
    Probing device 12...
    Invalid device
    Probing device 13...
    Invalid device
    Probing device 14...
    Invalid device
    Probing device 15...
    Invalid device
    Probing device 16...
    Invalid device
    Probing device 17...
    Invalid device
    Probing device 18...
    Invalid device
    Probing device 19...
    Invalid device
    Probing device 1a...
    Invalid device
    Probing device 1b...
    Invalid device
    Probing device 1c...
    Invalid device
    Probing device 1d...
    Invalid device
    Probing device 1e...
    Invalid device
    Probing device 1f...
    Invalid device
    Probing device 20...
    Invalid device
    Probing device 21...
    Invalid device
    Probing device 22...
    Invalid device
    Probing device 23...
    Invalid device
    Probing device 24...
    Invalid device
    Probing device 25...
    Invalid device
    Probing device 26...
    Invalid device
    Probing device 27...
    Invalid device
    Probing device 28...
    Invalid device
    Probing device 29...
    Invalid device
    Probing device 2a...
    Invalid device
    Probing device 2b...
    Invalid device
    Probing device 2c...
    Invalid device
    Probing device 2d...
    Invalid device
    Probing device 2e...
    Invalid device
    Probing device 2f...
    Invalid device
    Probing device 30...
    Invalid device
    Probing device 31...
    Invalid device
    Probing device 32...
    Invalid device
    Probing device 33...
    Invalid device
    Probing device 34...
    Invalid device
    Probing device 35...
    Invalid device
    Probing device 36...
    Invalid device
    Probing device 37...
    Invalid device
    Probing device 38...
    Invalid device
    Probing device 39...
    Invalid device
    Probing device 3a...
    Invalid device
    Probing device 3b...
    Invalid device
    Probing device 3c...
    Invalid device
    Probing device 3d...
    Invalid device
    Probing device 3e...
    Invalid device
    Probing device 3f...
    Invalid device
    Probing device 40...
    Invalid device
    Probing device 41...
    Invalid device
    Probing device 42...
    Invalid device
    Probing device 43...
    Invalid device
    Probing device 44...
    Invalid device
    Probing device 45...
    Invalid device
    Probing device 46...
    Invalid device
    Probing device 47...
    Invalid device
    Probing device 48...
    Invalid device
    Probing device 49...
    Invalid device
    Probing device 4a...
    Invalid device
    Probing device 4b...
    Invalid device
    Probing device 4c...
    Invalid device
    Probing device 4d...
    Invalid device
    Probing device 4e...
    Invalid device
    Probing device 4f...
    Invalid device

    thanks
     
  7. Unwinder

    Unwinder Moderator Staff Member

    Messages:
    15,663
    Likes Received:
    3,123
    I'm afraid I see no supported controller in the dump, sorry.
     
  8. Unwinder

    Unwinder Moderator Staff Member

    Messages:
    15,663
    Likes Received:
    3,123
    Nice, glad that you've got it working.

    I've received it, thanks!

    Direct access to NV regs is obsolete for MSI Afterburner's functionality only. NV designed this API in order to eliminate the need to access hw directly in tools like RT. But there is no unified way to access NV reg space via NVAPI. It is rather high level API.
     
  9. antonyfrn

    antonyfrn Maha Guru

    Messages:
    1,268
    Likes Received:
    7
    GPU:
    EVGA GTX 1070 FTW
    Is this any use for the database?

    Code:
    Scanning GPU VEN_10DE&DEV_13C2&SUBSYS_29783842&REV_A1&BUS_1&DEV_0&FN_0...
    Scanning I2C bus 0...
    Probing device 00...
    Invalid device
    Probing device 01...
    Invalid device
    Probing device 02...
    Invalid device
    Probing device 03...
    Invalid device
    Probing device 04...
    Invalid device
    Probing device 05...
    Invalid device
    Probing device 06...
    Invalid device
    Probing device 07...
    Invalid device
    Probing device 08...
    Invalid device
    Probing device 09...
    Invalid device
    Probing device 0a...
    Invalid device
    Probing device 0b...
    Invalid device
    Probing device 0c...
    Invalid device
    Probing device 0d...
    Invalid device
    Probing device 0e...
    Invalid device
    Probing device 0f...
    Invalid device
    Probing device 10...
    Invalid device
    Probing device 11...
    Invalid device
    Probing device 12...
    Invalid device
    Probing device 13...
    Invalid device
    Probing device 14...
    Invalid device
    Probing device 15...
    Invalid device
    Probing device 16...
    Invalid device
    Probing device 17...
    Invalid device
    Probing device 18...
    Invalid device
    Probing device 19...
    Invalid device
    Probing device 1a...
    Invalid device
    Probing device 1b...
    Invalid device
    Probing device 1c...
    Invalid device
    Probing device 1d...
    Invalid device
    Probing device 1e...
    Invalid device
    Probing device 1f...
    Invalid device
    Probing device 20...
    Invalid device
    Probing device 21...
    Invalid device
    Probing device 22...
    Invalid device
    Probing device 23...
    Invalid device
    Probing device 24...
    Invalid device
    Probing device 25...
    Invalid device
    Probing device 26...
    Invalid device
    Probing device 27...
    Invalid device
    Probing device 28...
    Invalid device
    Probing device 29...
    Invalid device
    Probing device 2a...
    Invalid device
    Probing device 2b...
    Invalid device
    Probing device 2c...
    Invalid device
    Probing device 2d...
    Invalid device
    Probing device 2e...
    Invalid device
    Probing device 2f...
    Invalid device
    Probing device 30...
    Invalid device
    Probing device 31...
    Invalid device
    Probing device 32...
    Invalid device
    Probing device 33...
    Invalid device
    Probing device 34...
    Invalid device
    Probing device 35...
    Invalid device
    Probing device 36...
    Invalid device
    Probing device 37...
    Invalid device
    Probing device 38...
    Invalid device
    Probing device 39...
    Invalid device
    Probing device 3a...
    Invalid device
    Probing device 3b...
    Invalid device
    Probing device 3c...
    Invalid device
    Probing device 3d...
    Invalid device
    Probing device 3e...
    Invalid device
    Probing device 3f...
    Invalid device
    Probing device 40...
    Invalid device
    Probing device 41...
    Invalid device
    Probing device 42...
    Invalid device
    Probing device 43...
    Invalid device
    Probing device 44...
    Invalid device
    Probing device 45...
    Invalid device
    Probing device 46...
    Invalid device
    Probing device 47...
    Invalid device
    Probing device 48...
    Invalid device
    Probing device 49...
    Invalid device
    Probing device 4a...
    Invalid device
    Probing device 4b...
    Invalid device
    Probing device 4c...
    Invalid device
    Probing device 4d...
    Invalid device
    Probing device 4e...
    Invalid device
    Probing device 4f...
    Invalid device
    Scanning I2C bus 1...
    Probing device 00...
    Invalid device
    Probing device 01...
    Invalid device
    Probing device 02...
    Invalid device
    Probing device 03...
    Invalid device
    Probing device 04...
    Invalid device
    Probing device 05...
    Invalid device
    Probing device 06...
    Invalid device
    Probing device 07...
    Invalid device
    Probing device 08...
    Invalid device
    Probing device 09...
    Invalid device
    Probing device 0a...
    Invalid device
    Probing device 0b...
    Invalid device
    Probing device 0c...
    Invalid device
    Probing device 0d...
    Invalid device
    Probing device 0e...
    Invalid device
    Probing device 0f...
    Invalid device
    Probing device 10...
    Invalid device
    Probing device 11...
    Invalid device
    Probing device 12...
    Invalid device
    Probing device 13...
    Invalid device
    Probing device 14...
    Invalid device
    Probing device 15...
    Invalid device
    Probing device 16...
    Invalid device
    Probing device 17...
    Invalid device
    Probing device 18...
    Invalid device
    Probing device 19...
    Invalid device
    Probing device 1a...
    Invalid device
    Probing device 1b...
    Invalid device
    Probing device 1c...
    Invalid device
    Probing device 1d...
    Invalid device
    Probing device 1e...
    Invalid device
    Probing device 1f...
    Invalid device
    Probing device 20...
    Invalid device
    Probing device 21...
    Invalid device
    Probing device 22...
    Invalid device
    Probing device 23...
    Invalid device
    Probing device 24...
    Invalid device
    Probing device 25...
    Invalid device
    Probing device 26...
    Invalid device
    Probing device 27...
    Invalid device
    Probing device 28...
    Invalid device
    Probing device 29...
    Invalid device
    Probing device 2a...
    Invalid device
    Probing device 2b...
    Invalid device
    Probing device 2c...
    Invalid device
    Probing device 2d...
    Invalid device
    Probing device 2e...
    Invalid device
    Probing device 2f...
    Invalid device
    Probing device 30...
    Invalid device
    Probing device 31...
    Invalid device
    Probing device 32...
    Invalid device
    Probing device 33...
    Invalid device
    Probing device 34...
    Invalid device
    Probing device 35...
    Invalid device
    Probing device 36...
    Invalid device
    Probing device 37...
    Invalid device
    Probing device 38...
    Invalid device
    Probing device 39...
    Invalid device
    Probing device 3a...
    Invalid device
    Probing device 3b...
    Invalid device
    Probing device 3c...
    Invalid device
    Probing device 3d...
    Invalid device
    Probing device 3e...
    Invalid device
    Probing device 3f...
    Invalid device
    Probing device 40...
    Invalid device
    Probing device 41...
    Invalid device
    Probing device 42...
    Invalid device
    Probing device 43...
    Invalid device
    Probing device 44...
    Invalid device
    Probing device 45...
    Invalid device
    Probing device 46...
    Invalid device
    Probing device 47...
    Invalid device
    Probing device 48...
    Invalid device
    Probing device 49...
    Invalid device
    Probing device 4a...
    Invalid device
    Probing device 4b...
    Invalid device
    Probing device 4c...
    Invalid device
    Probing device 4d...
    Invalid device
    Probing device 4e...
    Invalid device
    Probing device 4f...
    Invalid device
    Scanning I2C bus 2...
    Probing device 00...
    Invalid device
    Probing device 01...
    Invalid device
    Probing device 02...
    Invalid device
    Probing device 03...
    Invalid device
    Probing device 04...
    Invalid device
    Probing device 05...
    Invalid device
    Probing device 06...
    Invalid device
    Probing device 07...
    Invalid device
    Probing device 08...
    Invalid device
    Probing device 09...
    Invalid device
    Probing device 0a...
    Invalid device
    Probing device 0b...
    Invalid device
    Probing device 0c...
    Invalid device
    Probing device 0d...
    Invalid device
    Probing device 0e...
    Invalid device
    Probing device 0f...
    Invalid device
    Probing device 10...
    Invalid device
    Probing device 11...
    Invalid device
    Probing device 12...
    Invalid device
    Probing device 13...
    Invalid device
    Probing device 14...
    Invalid device
    Probing device 15...
    Invalid device
    Probing device 16...
    Invalid device
    Probing device 17...
    Invalid device
    Probing device 18...
    Invalid device
    Probing device 19...
    Invalid device
    Probing device 1a...
    Invalid device
    Probing device 1b...
    Invalid device
    Probing device 1c...
    Invalid device
    Probing device 1d...
    Invalid device
    Probing device 1e...
    Invalid device
    Probing device 1f...
    Invalid device
    Probing device 20...
    Invalid device
    Probing device 21...
    Invalid device
    Probing device 22...
    Invalid device
    Probing device 23...
    Invalid device
    Probing device 24...
    Invalid device
    Probing device 25...
    Invalid device
    Probing device 26...
    Invalid device
    Probing device 27...
    Invalid device
    Probing device 28...
    Invalid device
    Probing device 29...
    Invalid device
    Probing device 2a...
    Invalid device
    Probing device 2b...
    Invalid device
    Probing device 2c...
    Invalid device
    Probing device 2d...
    Invalid device
    Probing device 2e...
    Invalid device
    Probing device 2f...
    Invalid device
    Probing device 30...
    Invalid device
    Probing device 31...
    Invalid device
    Probing device 32...
    Invalid device
    Probing device 33...
    Invalid device
    Probing device 34...
    Invalid device
    Probing device 35...
    Invalid device
    Probing device 36...
    Invalid device
    Probing device 37...
    Invalid device
    Probing device 38...
    Invalid device
    Probing device 39...
    Invalid device
    Probing device 3a...
    Invalid device
    Probing device 3b...
    Invalid device
    Probing device 3c...
    Invalid device
    Probing device 3d...
    Invalid device
    Probing device 3e...
    Invalid device
    Probing device 3f...
    Invalid device
    Probing device 40...
    Invalid device
    Probing device 41...
    Invalid device
    Probing device 42...
    Invalid device
    Probing device 43...
    Invalid device
    Probing device 44...
    Invalid device
    Probing device 45...
    Invalid device
    Probing device 46...
    Invalid device
    Probing device 47...
    Invalid device
    Probing device 48...
    Invalid device
    Probing device 49...
    Invalid device
    Probing device 4a...
    Invalid device
    Probing device 4b...
    Invalid device
    Probing device 4c...
    Invalid device
    Probing device 4d...
    Invalid device
    Probing device 4e...
    Invalid device
    Probing device 4f...
    Invalid device
    Scanning I2C bus 3...
    Probing device 00...
    Invalid device
    Probing device 01...
    Invalid device
    Probing device 02...
    Invalid device
    Probing device 03...
    Invalid device
    Probing device 04...
    Invalid device
    Probing device 05...
    Invalid device
    Probing device 06...
    Invalid device
    Probing device 07...
    Invalid device
    Probing device 08...
    Invalid device
    Probing device 09...
    Invalid device
    Probing device 0a...
    Invalid device
    Probing device 0b...
    Invalid device
    Probing device 0c...
    Invalid device
    Probing device 0d...
    Invalid device
    Probing device 0e...
    Invalid device
    Probing device 0f...
    Invalid device
    Probing device 10...
    Invalid device
    Probing device 11...
    Invalid device
    Probing device 12...
    Invalid device
    Probing device 13...
    Invalid device
    Probing device 14...
    Invalid device
    Probing device 15...
    Invalid device
    Probing device 16...
    Invalid device
    Probing device 17...
    Invalid device
    Probing device 18...
    Invalid device
    Probing device 19...
    Invalid device
    Probing device 1a...
    Invalid device
    Probing device 1b...
    Invalid device
    Probing device 1c...
    Invalid device
    Probing device 1d...
    Invalid device
    Probing device 1e...
    Invalid device
    Probing device 1f...
    Invalid device
    Probing device 20...
    Invalid device
    Probing device 21...
    Invalid device
    Probing device 22...
    Invalid device
    Probing device 23...
    Invalid device
    Probing device 24...
    Invalid device
    Probing device 25...
    Invalid device
    Probing device 26...
    Invalid device
    Probing device 27...
    Invalid device
    Probing device 28...
    Invalid device
    Probing device 29...
    Invalid device
    Probing device 2a...
    Invalid device
    Probing device 2b...
    Invalid device
    Probing device 2c...
    Invalid device
    Probing device 2d...
    Invalid device
    Probing device 2e...
    Invalid device
    Probing device 2f...
    Invalid device
    Probing device 30...
    Invalid device
    Probing device 31...
    Invalid device
    Probing device 32...
    Invalid device
    Probing device 33...
    Invalid device
    Probing device 34...
    Invalid device
    Probing device 35...
    Invalid device
    Probing device 36...
    Invalid device
    Probing device 37...
    Invalid device
    Probing device 38...
    Invalid device
    Probing device 39...
    Invalid device
    Probing device 3a...
    Invalid device
    Probing device 3b...
    Invalid device
    Probing device 3c...
    Invalid device
    Probing device 3d...
    Invalid device
    Probing device 3e...
    Invalid device
    Probing device 3f...
    Invalid device
    Probing device 40...
    78 01 2F 02 2F 00 2F 7F 7F 44 7F 44 7F 00 7F 00 
    27 23 FF FF FF FF FF FF FF FF -- F8 FF FF 54 32 
    78 01 2F 02 2F 00 2F 7F 7F 44 7F 44 7F 00 7F 00 
    27 23 FF FF FF FF FF FF FF FF -- F8 FF FF 54 32 
    78 01 2F 02 2F 00 2F 7F 7F 44 7F 44 7F 00 7F 00 
    27 23 FF FF FF FF FF FF FF FF -- F8 FF FF 54 32 
    78 01 2F 02 2F 00 2F 7F 7F 44 7F 44 7F 00 7F 00 
    27 23 FF FF FF FF FF FF FF FF -- F8 FF FF 54 32 
    78 01 2F 02 2F 00 2F 7F 7F 44 7F 44 7F 00 7F 00 
    27 23 FF FF FF FF FF FF FF FF -- F8 FF FF 54 32 
    78 01 2F 02 2F 00 2F 7F 7F 44 7F 44 7F 00 7F 00 
    27 23 FF FF FF FF FF FF FF FF -- F8 FF FF 54 32 
    78 01 2F 02 2F 00 2F 7F 7F 44 7F 44 7F 00 7F 00 
    27 23 FF FF FF FF FF FF FF FF -- F8 FF FF 54 32 
    78 01 2F 02 2F 00 2F 7F 7F 44 7F 44 7F 00 7F 00 
    27 23 FF FF FF FF FF FF FF FF -- F8 FF FF 54 32 
    Probing device 41...
    Invalid device
    Probing device 42...
    Invalid device
    Probing device 43...
    Invalid device
    Probing device 44...
    Invalid device
    Probing device 45...
    Invalid device
    Probing device 46...
    Invalid device
    Probing device 47...
    Invalid device
    Probing device 48...
    Invalid device
    Probing device 49...
    Invalid device
    Probing device 4a...
    Invalid device
    Probing device 4b...
    Invalid device
    Probing device 4c...
    Invalid device
    Probing device 4d...
    Invalid device
    Probing device 4e...
    Invalid device
    Probing device 4f...
    Invalid device
    Scanning I2C bus 4...
    Probing device 00...
    Invalid device
    Probing device 01...
    Invalid device
    Probing device 02...
    Invalid device
    Probing device 03...
    Invalid device
    Probing device 04...
    Invalid device
    Probing device 05...
    Invalid device
    Probing device 06...
    Invalid device
    Probing device 07...
    Invalid device
    Probing device 08...
    Invalid device
    Probing device 09...
    Invalid device
    Probing device 0a...
    Invalid device
    Probing device 0b...
    Invalid device
    Probing device 0c...
    Invalid device
    Probing device 0d...
    Invalid device
    Probing device 0e...
    Invalid device
    Probing device 0f...
    Invalid device
    Probing device 10...
    Invalid device
    Probing device 11...
    Invalid device
    Probing device 12...
    Invalid device
    Probing device 13...
    Invalid device
    Probing device 14...
    Invalid device
    Probing device 15...
    Invalid device
    Probing device 16...
    Invalid device
    Probing device 17...
    Invalid device
    Probing device 18...
    Invalid device
    Probing device 19...
    Invalid device
    Probing device 1a...
    Invalid device
    Probing device 1b...
    Invalid device
    Probing device 1c...
    Invalid device
    Probing device 1d...
    Invalid device
    Probing device 1e...
    Invalid device
    Probing device 1f...
    Invalid device
    Probing device 20...
    Invalid device
    Probing device 21...
    Invalid device
    Probing device 22...
    Invalid device
    Probing device 23...
    Invalid device
    Probing device 24...
    Invalid device
    Probing device 25...
    Invalid device
    Probing device 26...
    Invalid device
    Probing device 27...
    Invalid device
    Probing device 28...
    Invalid device
    Probing device 29...
    Invalid device
    Probing device 2a...
    Invalid device
    Probing device 2b...
    Invalid device
    Probing device 2c...
    Invalid device
    Probing device 2d...
    Invalid device
    Probing device 2e...
    Invalid device
    Probing device 2f...
    Invalid device
    Probing device 30...
    Invalid device
    Probing device 31...
    Invalid device
    Probing device 32...
    Invalid device
    Probing device 33...
    Invalid device
    Probing device 34...
    Invalid device
    Probing device 35...
    Invalid device
    Probing device 36...
    Invalid device
    Probing device 37...
    Invalid device
    Probing device 38...
    Invalid device
    Probing device 39...
    Invalid device
    Probing device 3a...
    Invalid device
    Probing device 3b...
    Invalid device
    Probing device 3c...
    Invalid device
    Probing device 3d...
    Invalid device
    Probing device 3e...
    Invalid device
    Probing device 3f...
    Invalid device
    Probing device 40...
    Invalid device
    Probing device 41...
    Invalid device
    Probing device 42...
    Invalid device
    Probing device 43...
    Invalid device
    Probing device 44...
    Invalid device
    Probing device 45...
    Invalid device
    Probing device 46...
    Invalid device
    Probing device 47...
    Invalid device
    Probing device 48...
    Invalid device
    Probing device 49...
    Invalid device
    Probing device 4a...
    Invalid device
    Probing device 4b...
    Invalid device
    Probing device 4c...
    Invalid device
    Probing device 4d...
    Invalid device
    Probing device 4e...
    Invalid device
    Probing device 4f...
    Invalid device
    
     
  10. Cryengine

    Cryengine Member Guru

    Messages:
    172
    Likes Received:
    3
    GPU:
    Strix 1080 Ti oc
    No core voltage control here (Asus GTX 780 DcuII o/c bios : 80.80.21.00.3B )
    Any idea thanks in advance.
     

  11. Unwinder

    Unwinder Moderator Staff Member

    Messages:
    15,663
    Likes Received:
    3,123
    May I ask why it is supposed to be there? Seriously, try to read the thread.
     
  12. Unwinder

    Unwinder Moderator Staff Member

    Messages:
    15,663
    Likes Received:
    3,123
    Nope, sorry, seem to be regular reference design card with no extra controller.
     
  13. Unwinder

    Unwinder Moderator Staff Member

    Messages:
    15,663
    Likes Received:
    3,123
    Hardware database format document is ready, so I've created sticky thread for third party hardware database. All documentation and the most recent version of third party database will be stored there:

    http://forums.guru3d.com/showthread.php?t=399542

    Please post everything related to third party database in that thread.
     
  14. Unwinder

    Unwinder Moderator Staff Member

    Messages:
    15,663
    Likes Received:
    3,123
    Guys, I'd like to see some feedback from AMD CPU owners who unlock experimental AMD CPU temperature monitoring in 4.1.1.
     
  15. Tomatone

    Tomatone Member Guru

    Messages:
    151
    Likes Received:
    42
    GPU:
    Nitro+ 580 8GB
    Readings are accurate for Phenom II X4 955BE :)
     

  16. Unwinder

    Unwinder Moderator Staff Member

    Messages:
    15,663
    Likes Received:
    3,123
    Thanks. If I collect more feedback on this feature, it will be unlocked by default in the next version.
     
  17. Unwinder

    Unwinder Moderator Staff Member

    Messages:
    15,663
    Likes Received:
    3,123
    Good news, recently leaked beta version of 353.17 drivers fixes videomemory usage monitoring under Windows 10:

    http://forums.guru3d.com/showpost.php?p=5093011&postcount=34
     
  18. Extraordinary

    Extraordinary Ancient Guru

    Messages:
    19,562
    Likes Received:
    1,629
    GPU:
    ROG Strix 1080 OC
    What sort of feedback can I give?

    I'm not sure about accuracy because nothing seems to be able to monitor FX chips correctly under 40c to compare the results from Afterburner
     
  19. Unwinder

    Unwinder Moderator Staff Member

    Messages:
    15,663
    Likes Received:
    3,123
    Even simple feedback in "able to unlock" or "unable to unlock" forms from different AMD CPUs would be useful.
     
  20. Extraordinary

    Extraordinary Ancient Guru

    Messages:
    19,562
    Likes Received:
    1,629
    GPU:
    ROG Strix 1080 OC
    Ah ok, well I mentioned a couple weeks back that it unlocked and works great on my FX-8350, temps seem to look around about what I would expect judging from CPU usage in game too

    Seems to be pretty close to Coretemps results too

    [​IMG]
     
    Last edited: Jun 10, 2015

Share This Page