Hi, I've got a very strange effect with the sensor for the
GPU temperature. Using the recent EVEREST Ultimate
I see four temperature symbols in the taskbar tray:
- HDD
- CPU
- GPU
- GPU neighborhood
Within the first refeshment cycle they all show normal.
However from the second refeshment cycle on (i.e. after
5 seconds) GPU and GPU neighborhood show a Zero.
The same happens in the EVEREST main window under
-> Computer -> Sensors. In the first cycle I see all four
temperatures, from the second cycle on the GPU related
entries vanish and never reappear.
What might be the reason for this rather strange behaviour?
It didn't use to happen. The only thing I changed is the
graphics driver, which I updated to a never version.
Could the graphics driver cause such an effect?
Since I have two identical notebooks and they both show
this odd behavior I do not think that it is a hardware
problem (sensor).
Should I provide more information? Which?
Page 1 of 1
GPU temperature vahishes (GeForce FX Go5700)
#2
Posted 02 November 2009 - 07:28 PM
1) Please let us know which version of EVEREST are you running, and what video adapter(s) do you have in your system.
2) Copy-paste the full results of the Computer / Sensor page of EVEREST into this topic. It would be best if you could do that before the GPU temperature vanishes.
3) Let me know the old and new video driver version. Changing driver can cause such weird issues on nVIDIA video cards, since on most nVIDIA video adapters EVEREST measures temperatures via a ForceWare driver interface.
Thanks,
Fiery
2) Copy-paste the full results of the Computer / Sensor page of EVEREST into this topic. It would be best if you could do that before the GPU temperature vanishes.
3) Let me know the old and new video driver version. Changing driver can cause such weird issues on nVIDIA video cards, since on most nVIDIA video adapters EVEREST measures temperatures via a ForceWare driver interface.
Thanks,
Fiery
#3
Posted 03 November 2009 - 09:35 PM
Fiery, on 02 November 2009 - 07:28 PM, said:
1) Please let us know which version of EVEREST are you running, and what video adapter(s) do you have in your system.
2) Copy-paste the full results of the Computer / Sensor page of EVEREST into this topic. It would be best if you could do that before the GPU temperature vanishes.
3) Let me know the old and new video driver version. Changing driver can cause such weird issues on nVIDIA video cards, since on most nVIDIA video adapters EVEREST measures temperatures via a ForceWare driver interface.
2) Copy-paste the full results of the Computer / Sensor page of EVEREST into this topic. It would be best if you could do that before the GPU temperature vanishes.
3) Let me know the old and new video driver version. Changing driver can cause such weird issues on nVIDIA video cards, since on most nVIDIA video adapters EVEREST measures temperatures via a ForceWare driver interface.
1) Everest Ultimate edition 5.30.1900
NVIDIA GeForce FX Go5700
3) New driver: nv4_mini.sys 6.14.11.7580
nv4_disp.dll 6.14.11.7580
nv4api.dll 6.14.11.7580
nv4cod.dll 1, 3, 0, 5
nv4codins.dll 1, 3, 0, 5
nv4cpl.dll 6.14.11.7580
nv4cuda.dll 6.14.11.7580
<more> 6.14.11.7580 (all)
Old driver: nv4_mini.sys 6.14.10.5351
nv4_disp.dll 6.14.10.5351
nv4cod.dll 1, 0, 0, 11
nv4cpl.dll 6.14.10.5351
<more> 6.14.10.5351 (all)
The old driver was digital signed, the new one is not. (I did not find a new signed one.)
The main reason to change the driver was a game (Crazy Machines 2) which did not render
properly with the old driver. After a long discussion with the game vendor's hotline I
did decide to try a new driver.
2) Today I am not able to copy the infomation before the temperatures vanishes.
However some days ago I could copy those values to clipboard before they vanished,
and I pasted the result to a text editor. Comparing this with the content of
the clipboard after vanishing I saw, that the only difference were two lines
with the temperature values. So there should not much information be missed today.
Sensor Eigenschaften
Sensortyp HDD, ACPI
GPU Sensortyp Maxim MAX6646 (NV-I2C 4Ch)
Temperaturen
CPU 63 °C (145 °F)
SAMSUNG SP2014N 50 °C (122 °F)
------[ Motherboard Info ]------
Motherboard ID : <DMI>
Motherboard Model : Acer Aspire 1710
Motherboard Chipset : Intel Springdale-G i865G
DMI MB Manufacturer : Acer
DMI MB Product : Aspire 1710
DMI MB Version :
DMI MB Serial : LXA1505080431003A5EF01
DMI SYS Manufacturer: Acer
DMI SYS Product : Aspire 1710
DMI SYS Version :
DMI SYS Serial : LXA1505080431003A5EF01
DMI BIOS Version :
------[ GPIO @ isa 1180 ]------
0000 80 F9 00 1A FF FF 00 03 00 00 00 00 00 00 3B 1B
0010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0020 00 00 00 00 00 00 00 00 00 00 00 00 00 20 00 00
0030 07 00 00 00 07 03 00 00 02 03 03 00 00 00 00 00
ITE 87xx HWMonitor Port = 0000h
ITE 87xx Device ID = 0000h
ITE 87xx Version = 00h
Winbond SuperIO HWMonitor Port = 0201h
Winbond SuperIO Device ID = EA11h
Fintek SuperIO HWMonitor Port = 0000h
Fintek SuperIO Device ID = 0000h
LPC47 SuperIO HWMonitor Port = 0000h
LPC47 SuperIO Device ID = EC11h
------[ ACPI Temperatures & Fans ]------
_TZ_.THM0._TMP :
_TZ_.THM1._TMP :
_TZ_.THR0._TMP :
_TZ_.THR1._TMP :
_TZ_.TZ00._TMP :
_TZ_.TZ01._TMP :
_TZ_.RFAN :
_TZ_.RFAN(0) :
_TZ_.RFAN(1) :
_SB_.ATKD.TMPR :
_SB_.PCI0.LPC0.EC0_.CCTV :
_SB_.PCI0.LPC0.EC0_.LRPM :
_SB_.PCI0.LPC0.EC0_.HRPM :
_SB_.PCI0.SBRG.EC0_.ECPU :
_SB_.PCI0.SBRG.EC0_.TACH(0):
_SB_.PCI0.SBRG.EC0_.TACH(1):
_SB_.PCI0.SBRG.EC0_.TAH0 :
_SB_.PCI0.SBRG.EC0_.TAH1 :
_SB_.PCI0.SBRG.EC0_.ST00 :
_SB_.PCI0.SBRG.EC0_.SC01 :
_SB_.PCI0.SBRG.EC0_.SC02 :
_SB_.PCI0.SBRG.EC0_.SC03 :
_SB_.PCI0.SBRG.EC0_.SC04 :
_SB_.PCI0.SBRG.EC0_.SC05 :
_SB_.PCI0.SBRG.EC0_.SC06 :
_SB_.PCI0.PIB_.EC0_.TCRT :
_SB_.PCI0.SBRG.EC0_.CTPM :
_SB_.PCI0.SBRG.EC__.CPUT :
_SB_.PCI0.SBRG.EC__.SYST :
_SB_.PCI0.LPC_.EC0_.CTMP :
_SB_.PCI0.LPCB.EC0_.CTMP :
_SB_.PCI0.LPC_.EC0_.TMP1 :
_SB_.PCI0.LPC_.EC0_.TMP2 :
_SB_.PCI0.LPC_.EC0_.TMPI :
_SB_.PCI0.LPC_.EC0_.TMPV :
==========================================================================
------[ 1 SMBus detected ]------
------[ SMBus #0 ]------
SMBus Type : Intel ICH
SMBus Port : 2040
Can Have SPD: Yes
Scan Type : Full
------[ SMBus Device B00-D44 ]------
0000 00 00 0F 04 00 00 00 00 00 00 00 00 00 00 00 00 ................
0010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0040 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0060 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0070 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0080 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0090 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00A0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00B0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00C0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00D0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00E0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00F0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
------[ SMBus Device B00-D44 ]------
0000 FF00 FF00 FF0F FF04 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00
0010 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00
0020 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00
0030 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00
0040 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00
0050 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00
0060 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00
0070 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00
0080 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00
0090 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00
00A0 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00
00B0 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00
00C0 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00
00D0 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00
00E0 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00
00F0 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00 FF00
------[ SMBus Device B00-D50 ]------
0000 80 08 07 0D 0A 02 40 00 04 60 70 00 82 08 00 01 ......@..`p.....
0010 0E 04 0C 01 02 20 00 75 70 00 00 48 30 48 2A 40 ..... .up..H0H*@
0020 75 75 45 45 00 00 00 00 00 3C 48 30 28 55 00 00 uuEE.....<H0(U..
0030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 3C ...............<
0040 7F 7F 7F 0B 00 00 00 00 08 4E 54 35 31 32 44 36 ......NT512D6
0050 34 53 38 48 42 31 47 2D 36 4B 20 00 00 04 18 08 4S8HB1G-6K .....
0060 58 22 06 00 00 00 00 00 00 00 00 00 00 00 00 00 X"..............
0070 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0080 00 00 00 00 00 00 00 4D 46 30 34 36 30 34 30 35 .......MF0460405
0090 42 00 00 00 00 00 00 31 35 34 36 39 38 36 00 00 B......1546986..
00A0 00 00 00 00 00 46 01 00 4E 53 54 55 00 32 2D 35 .....F..NSTU.2-5
00B0 32 00 00 00 00 00 00 00 00 00 00 00 00 00 80 00 2...............
00C0 00 00 00 00 00 00 00 00 00 00 00 80 00 00 00 00 ................
00D0 00 00 00 00 00 00 00 00 80 00 00 00 00 00 00 00 ................
00E0 00 00 00 00 00 80 00 00 00 00 00 00 00 00 00 00 ................
00F0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 88 ................
------[ SMBus Device B00-D51 ]------
0000 80 08 07 0D 0A 02 40 00 04 60 70 00 82 08 00 01 ......@..`p.....
0010 0E 04 0C 01 02 20 00 75 70 00 00 48 30 48 2A 40 ..... .up..H0H*@
0020 75 75 45 45 00 00 00 00 00 3C 48 30 28 55 00 00 uuEE.....<H0(U..
0030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 3C ...............<
0040 7F 7F 7F 0B 00 00 00 00 08 4E 54 35 31 32 44 36 ......NT512D6
0050 34 53 38 48 42 31 47 2D 36 4B 20 00 00 04 18 13 4S8HB1G-6K .....
0060 58 22 08 00 00 00 00 00 00 00 00 00 00 00 00 00 X"..............
0070 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0080 00 00 00 00 00 00 00 4D 46 30 34 36 30 34 30 35 .......MF0460405
0090 42 00 00 00 00 00 00 31 35 34 36 39 38 36 00 00 B......1546986..
00A0 00 00 00 00 00 3D 01 00 4E 53 54 55 00 32 2D 35 .....=..NSTU.2-5
00B0 32 00 00 00 00 00 00 00 00 00 00 00 00 00 80 00 2...............
00C0 00 00 00 00 00 00 00 00 00 00 00 80 00 00 00 00 ................
00D0 00 00 00 00 00 00 00 00 80 00 00 00 00 00 00 00 ................
00E0 00 00 00 00 00 80 00 00 00 00 00 00 00 00 00 00 ................
00F0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 88 ................
#4
Posted 03 November 2009 - 09:52 PM
Thank you for the data. After the GPU temperature vanishes, please right-click on the bottom status bar of EVEREST main window --> Video Debug --> nVIDIA SMBus Dump. Copy-paste the full results into this topic.
Also right-click on the bottom status bar of EVEREST main window --> Video Debug --> nVIDIA GPU Registers. Copy-paste the full results into this topic.
Thanks,
Fiery
Also right-click on the bottom status bar of EVEREST main window --> Video Debug --> nVIDIA GPU Registers. Copy-paste the full results into this topic.
Thanks,
Fiery
#5
Posted 03 November 2009 - 10:00 PM
Oops, here comes a PS.
I just read another thread in the forum
(http://www.lavalys.com/forum/index.php?showtopic=4442)
where you recommend to toggle the option
"nVIDIA GPU SMBus access through ForceWare".
I did try this, the option was not enabled.
After enabling it the missing GPU temperatures
do show up again.
So my problem seems to be solved. The only thing
I do not know is, what you would recommend under
normal circumstances, enabling the option or not.
Here is the new information from the
-> Computer -> Sensors site, but only as a kind of
diff dump:
Sensor Eigenschaften
Sensortyp HDD, ACPI
<through Forceware> GPU Sensortyp Driver (NV-DRV)
<not through Forceware> GPU Sensortyp Maxim MAX6646 (NV-I2C 4Ch)
Temperaturen
CPU 63 °C (145 °F)
<through Forceware> Grafikprozessor (GPU) 57 °C (135 °F)
<through Forceware> GPU Umgebung 52 °C (126 °F)
<through Forceware> SAMSUNG SP2014N 51 °C (124 °F)
<not through Forceware> SAMSUNG SP2014N 50 °C (122 °F)
<no more differences...>
I just read another thread in the forum
(http://www.lavalys.com/forum/index.php?showtopic=4442)
where you recommend to toggle the option
"nVIDIA GPU SMBus access through ForceWare".
I did try this, the option was not enabled.
After enabling it the missing GPU temperatures
do show up again.
So my problem seems to be solved. The only thing
I do not know is, what you would recommend under
normal circumstances, enabling the option or not.
Here is the new information from the
-> Computer -> Sensors site, but only as a kind of
diff dump:
Sensor Eigenschaften
Sensortyp HDD, ACPI
<through Forceware> GPU Sensortyp Driver (NV-DRV)
<not through Forceware> GPU Sensortyp Maxim MAX6646 (NV-I2C 4Ch)
Temperaturen
CPU 63 °C (145 °F)
<through Forceware> Grafikprozessor (GPU) 57 °C (135 °F)
<through Forceware> GPU Umgebung 52 °C (126 °F)
<through Forceware> SAMSUNG SP2014N 51 °C (124 °F)
<not through Forceware> SAMSUNG SP2014N 50 °C (122 °F)
<no more differences...>
#6
Posted 03 November 2009 - 10:03 PM
Thank you for the feedback. That option is fine at both settings. When the option is disabled, EVEREST accesses nVIDIA GPU SMBus via direct calls. But apparently direct calls do not work 100% reliably on your configuration. When you enable that option, EVEREST switches from direct calls to driver (ForceWare) calls, and that usually fixes such GPU temperature measurement issues.
Regards,
Fiery
Regards,
Fiery
#7
Posted 03 November 2009 - 10:25 PM
Our last messages must have crossed.
To avoid misunderstandings, I turned off the option
"nVIDIA GPU SMBus access through ForceWare" again
and restarted EVEREST.
Here is the dump from
-> main window -> Video Debug -> nVIDIA SMBus Dump:
------[ EVEREST v5.30.1900 ]------
------[ Microsoft Windows XP Home Edition 5.1.2600 (32-bit) ]------
------[ Video Adapters ]------
nVIDIA GeForce FX Go5700 [10DE-0348 / 1025-0045]
------[ Video Driver ]------
nvapi.dll: 6.14.11.7580
nv4_disp||6.14.11.7580 - nVIDIA ForceWare 175.80
nv4_disp||6.14.11.7580 - nVIDIA ForceWare 175.80
------[ nVIDIA Driver 1B0h / 24h ]------
35 3A 64 64 64 82 82 82 F002F8
------[ nVIDIA Driver 1B0h / 48h ]------
35 3A 64 64 64 82 82 82 F002F8
00 00 00 00 00 00 00 00 00
------[ nVIDIA Driver 1B0h / 90h ]------
35 3A 64 64 64 82 82 82 F002F8
00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00
------[ nVIDIA GPU #1 / B00-CR1F = 03 ]------
------[ nVIDIA GPU #1 / B00-CR49 = 00 ]------
------[ nVIDIA GPU #1 / B01-CR1F = 03 ]------
------[ nVIDIA GPU #1 / B01-CR49 = 00 ]------
------[ nVIDIA GPU #1 / B02-CR1F = 03 ]------
------[ nVIDIA GPU #1 / B02-CR49 = 00 ]------
------[ nVIDIA GPU #1 / B03-CR1F = 03 ]------
------[ nVIDIA GPU #1 / B03-CR49 = 00 ]------
And here is the dump from
-> main window -> Video Debug -> nVIDIA GPU Registers:
------[ EVEREST v5.30.1900 ]------
------[ Microsoft Windows XP Home Edition 5.1.2600 (32-bit) ]------
------[ Video Adapters ]------
nVIDIA GeForce FX Go5700 [10DE-0348 / 1025-0045]
------[ Video Driver ]------
nvapi.dll: 6.14.11.7580
nv4_disp||6.14.11.7580 - nVIDIA ForceWare 175.80
nv4_disp||6.14.11.7580 - nVIDIA ForceWare 175.80
------[ nVIDIA GPU #1 @ mem D1000000 ]------
GPU Clocks = 351 / 0 / 0 MHz
Memory Clock = 289 MHz
GPU Base Clock = 27000 kHz
Shader Base Clock = 27000 kHz
Memory Base Clock = 27000 kHz
nvidia-000000 = 436800A1
nvidia-0010F0 = 00007FFF
nvidia-001218 = 00010101
nvidia-001850 = 00000001
nvidia-100000 = 00000000
nvidia-100200 = 030F0705
nvidia-10020C = 08000000
nvidia-101000 = A160C187
nvidia-680500 = 00010601
nvidia-680504 = 10001E07
nvidia-680570 = 80000D03
nvidia-680574 = 80000501
------[ nVIDIA GPU #1 / ForceWare Properties ]------
VPE Count = 0
Shader Pipe Count = 0
Partition Count = 2
Physical Frame Buffer Size = 131072 KB
Virtual Frame Buffer Size = 131072 KB
------[ nVIDIA GPU #1 / ForceWare Clocks ]------
Perf. Levels = 3
Active Profile = 2
curr-core/shader/mem-0 = 100 MHz / 0 MHz / 350 MHz
curr-core/shader/mem-1 = 200 MHz / 0 MHz / 400 MHz
curr-core/shader/mem-2 = 350 MHz / 0 MHz / 580 MHz [Active]
orig-core/shader/mem-0 = 100 MHz / 0 MHz / 350 MHz
orig-core/shader/mem-1 = 200 MHz / 0 MHz / 400 MHz
orig-core/shader/mem-2 = 350 MHz / 0 MHz / 580 MHz [Active]
------[ nVIDIA GPU #1 / BIOS Info ]------
BIOS Version = 4.36.20.33
Signon Message = NV36 E183 Mobile Reference VGA BIOS
Bootup Core Clock = 200 MHz
Bootup Shader Clock = 0 MHz
Bootup Mem Clock = 200 MHz
Ref. Clock 4000 = 0 kHz = 0 MHz *4
Ref. Clock 4008 = 0 kHz = 0 MHz *4 [Memory]
Ref. Clock 4010 = 0 kHz = 0 MHz *4
Ref. Clock 4018 = 0 kHz = 0 MHz *4
Ref. Clock 4020 = 0 kHz = 0 MHz *4 [Shader]
Ref. Clock 4028 = 0 kHz = 0 MHz *4 [GPU]
Ref. Clock 4030 = 0 kHz = 0 MHz *4
Ref. Clock 4038 = 0 kHz = 0 MHz *4
Core Clock = 100 MHz
Shader Clock = 0 MHz
Mem Clock = 175 MHz
Geom. Delta = 0 MHz
Core Voltage = 0,00 V
Fan Speed = 100 %
Core Clock = 200 MHz
Shader Clock = 0 MHz
Mem Clock = 200 MHz
Geom. Delta = 0 MHz
Core Voltage = 0,00 V
Fan Speed = 100 %
Core Clock = 350 MHz
Shader Clock = 0 MHz
Mem Clock = 290 MHz
Geom. Delta = 0 MHz
Core Voltage = 0,00 V
Fan Speed = 100 %
Diode Gain Mul = 0
Diode Gain Div = 0
Diode Offset Mul = 0
Diode Offset Div = 0
Diode Offset Bin Mul = 0
Diode Offset Bin Div = 1
Temp Compensation Mul = 0
Temp Compensation Div = 1
Max Div = 0
Measured Temp Threshold (Raw) = 0
Measured Temp Threshold (Int) = 0 Celsius
Measured Temp Threshold (Float) = 0 Celsius
BIOS Temp Threshold = 125 Celsius
Measured Diode Temp (Raw) = 0
Measured Diode Temp (Int) = 0 Celsius
Measured Diode Temp (Float) = 0 Celsius
Diode Temp by ForceWare = 58 Celsius
------[ nVIDIA SLI ]------
00000200 00000000
------[ NVAPI GPU Handles ]------
GPU Count: 1
GPU #1: BB001000
------[ nVIDIA GPU #1 / Thermal Settings ]------
44 00 01 00 02 00 00 00 04 00 00 00 00 00 00 00
91 00 00 00 3A 00 00 00 01 00 00 00 04 00 00 00
00 00 00 00 91 00 00 00 34 00 00 00 08 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00
Taking this several times the last block varies
somtimes to
------[ nVIDIA GPU #1 / Thermal Settings ]------
44 00 01 00 02 00 00 00 04 00 00 00 00 00 00 00
91 00 00 00 3A 00 00 00 01 00 00 00 04 00 00 00
00 00 00 00 91 00 00 00 35 00 00 00 08 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00
I guess the 34 vs. 35 is a measured temperature?
To avoid misunderstandings, I turned off the option
"nVIDIA GPU SMBus access through ForceWare" again
and restarted EVEREST.
Here is the dump from
-> main window -> Video Debug -> nVIDIA SMBus Dump:
------[ EVEREST v5.30.1900 ]------
------[ Microsoft Windows XP Home Edition 5.1.2600 (32-bit) ]------
------[ Video Adapters ]------
nVIDIA GeForce FX Go5700 [10DE-0348 / 1025-0045]
------[ Video Driver ]------
nvapi.dll: 6.14.11.7580
nv4_disp||6.14.11.7580 - nVIDIA ForceWare 175.80
nv4_disp||6.14.11.7580 - nVIDIA ForceWare 175.80
------[ nVIDIA Driver 1B0h / 24h ]------
35 3A 64 64 64 82 82 82 F002F8
------[ nVIDIA Driver 1B0h / 48h ]------
35 3A 64 64 64 82 82 82 F002F8
00 00 00 00 00 00 00 00 00
------[ nVIDIA Driver 1B0h / 90h ]------
35 3A 64 64 64 82 82 82 F002F8
00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00
------[ nVIDIA GPU #1 / B00-CR1F = 03 ]------
------[ nVIDIA GPU #1 / B00-CR49 = 00 ]------
------[ nVIDIA GPU #1 / B01-CR1F = 03 ]------
------[ nVIDIA GPU #1 / B01-CR49 = 00 ]------
------[ nVIDIA GPU #1 / B02-CR1F = 03 ]------
------[ nVIDIA GPU #1 / B02-CR49 = 00 ]------
------[ nVIDIA GPU #1 / B03-CR1F = 03 ]------
------[ nVIDIA GPU #1 / B03-CR49 = 00 ]------
And here is the dump from
-> main window -> Video Debug -> nVIDIA GPU Registers:
------[ EVEREST v5.30.1900 ]------
------[ Microsoft Windows XP Home Edition 5.1.2600 (32-bit) ]------
------[ Video Adapters ]------
nVIDIA GeForce FX Go5700 [10DE-0348 / 1025-0045]
------[ Video Driver ]------
nvapi.dll: 6.14.11.7580
nv4_disp||6.14.11.7580 - nVIDIA ForceWare 175.80
nv4_disp||6.14.11.7580 - nVIDIA ForceWare 175.80
------[ nVIDIA GPU #1 @ mem D1000000 ]------
GPU Clocks = 351 / 0 / 0 MHz
Memory Clock = 289 MHz
GPU Base Clock = 27000 kHz
Shader Base Clock = 27000 kHz
Memory Base Clock = 27000 kHz
nvidia-000000 = 436800A1
nvidia-0010F0 = 00007FFF
nvidia-001218 = 00010101
nvidia-001850 = 00000001
nvidia-100000 = 00000000
nvidia-100200 = 030F0705
nvidia-10020C = 08000000
nvidia-101000 = A160C187
nvidia-680500 = 00010601
nvidia-680504 = 10001E07
nvidia-680570 = 80000D03
nvidia-680574 = 80000501
------[ nVIDIA GPU #1 / ForceWare Properties ]------
VPE Count = 0
Shader Pipe Count = 0
Partition Count = 2
Physical Frame Buffer Size = 131072 KB
Virtual Frame Buffer Size = 131072 KB
------[ nVIDIA GPU #1 / ForceWare Clocks ]------
Perf. Levels = 3
Active Profile = 2
curr-core/shader/mem-0 = 100 MHz / 0 MHz / 350 MHz
curr-core/shader/mem-1 = 200 MHz / 0 MHz / 400 MHz
curr-core/shader/mem-2 = 350 MHz / 0 MHz / 580 MHz [Active]
orig-core/shader/mem-0 = 100 MHz / 0 MHz / 350 MHz
orig-core/shader/mem-1 = 200 MHz / 0 MHz / 400 MHz
orig-core/shader/mem-2 = 350 MHz / 0 MHz / 580 MHz [Active]
------[ nVIDIA GPU #1 / BIOS Info ]------
BIOS Version = 4.36.20.33
Signon Message = NV36 E183 Mobile Reference VGA BIOS
Bootup Core Clock = 200 MHz
Bootup Shader Clock = 0 MHz
Bootup Mem Clock = 200 MHz
Ref. Clock 4000 = 0 kHz = 0 MHz *4
Ref. Clock 4008 = 0 kHz = 0 MHz *4 [Memory]
Ref. Clock 4010 = 0 kHz = 0 MHz *4
Ref. Clock 4018 = 0 kHz = 0 MHz *4
Ref. Clock 4020 = 0 kHz = 0 MHz *4 [Shader]
Ref. Clock 4028 = 0 kHz = 0 MHz *4 [GPU]
Ref. Clock 4030 = 0 kHz = 0 MHz *4
Ref. Clock 4038 = 0 kHz = 0 MHz *4
Core Clock = 100 MHz
Shader Clock = 0 MHz
Mem Clock = 175 MHz
Geom. Delta = 0 MHz
Core Voltage = 0,00 V
Fan Speed = 100 %
Core Clock = 200 MHz
Shader Clock = 0 MHz
Mem Clock = 200 MHz
Geom. Delta = 0 MHz
Core Voltage = 0,00 V
Fan Speed = 100 %
Core Clock = 350 MHz
Shader Clock = 0 MHz
Mem Clock = 290 MHz
Geom. Delta = 0 MHz
Core Voltage = 0,00 V
Fan Speed = 100 %
Diode Gain Mul = 0
Diode Gain Div = 0
Diode Offset Mul = 0
Diode Offset Div = 0
Diode Offset Bin Mul = 0
Diode Offset Bin Div = 1
Temp Compensation Mul = 0
Temp Compensation Div = 1
Max Div = 0
Measured Temp Threshold (Raw) = 0
Measured Temp Threshold (Int) = 0 Celsius
Measured Temp Threshold (Float) = 0 Celsius
BIOS Temp Threshold = 125 Celsius
Measured Diode Temp (Raw) = 0
Measured Diode Temp (Int) = 0 Celsius
Measured Diode Temp (Float) = 0 Celsius
Diode Temp by ForceWare = 58 Celsius
------[ nVIDIA SLI ]------
00000200 00000000
------[ NVAPI GPU Handles ]------
GPU Count: 1
GPU #1: BB001000
------[ nVIDIA GPU #1 / Thermal Settings ]------
44 00 01 00 02 00 00 00 04 00 00 00 00 00 00 00
91 00 00 00 3A 00 00 00 01 00 00 00 04 00 00 00
00 00 00 00 91 00 00 00 34 00 00 00 08 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00
Taking this several times the last block varies
somtimes to
------[ nVIDIA GPU #1 / Thermal Settings ]------
44 00 01 00 02 00 00 00 04 00 00 00 00 00 00 00
91 00 00 00 3A 00 00 00 01 00 00 00 04 00 00 00
00 00 00 00 91 00 00 00 35 00 00 00 08 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00
I guess the 34 vs. 35 is a measured temperature?
#8
Posted 03 November 2009 - 10:31 PM
Fiery, on 03 November 2009 - 10:03 PM, said:
Thank you for the feedback. That option is fine at both settings. When the option is disabled, EVEREST accesses nVIDIA GPU SMBus via direct calls. But apparently direct calls do not work 100% reliably on your configuration. When you enable that option, EVEREST switches from direct calls to driver (ForceWare) calls, and that usually fixes such GPU temperature measurement issues.
Thank you for your kind help :-)
Page 1 of 1

Sign In
Register
Help
MultiQuote