We have discontinued this forum and moved support tickets to the GitHub issue tracker. More info

0 values on Windows after a while (macbook pro/air)

Control fans on Apple hardware: iMacs, Macbooks, etc

Moderator: Steven

waikun
Posts: 11
Joined: 11 May 2013, 18:23

0 values on Windows after a while (macbook pro/air)

Post by waikun »

Hi,

I've noticed that, after some time playing games in windows, the program displays 0° temperature and 0 rpm on both fans of my rMBP 15". It only happens on Windows (8, don't know about other versions), not Mac OS X. After this effect emerges, any other hardware monitoring software fails to display correct values, as well. (In my case, CPUID Hardware Monitor, which doesn't even start up correctly and has to be killed.)

Since I always play in FullScreen-mode, I don't know what causes this to happen, but it seems to be fairly random and only after an extended period of play (>1-2h).

Not sure if this is the correct place for a bug report, but I thought I'd share.

Cheers,
waikun
User avatar
Steven
CrystalIDEA Developer
Posts: 2294
Joined: 21 Dec 2009, 11:48
Location: CrystalIDEA headquarters
Contact:

Re: nil values after running on windows for some time

Post by Steven »

waikun,

Thanks for the information! Maybe the problem lies in Boot Camp drivers for Windows.

1. Does the problem happen when you don't use Macs Fan Control?
2. Is the problem solved after reboot?
3. Screenshot of Macs Fan Control window when it displays 0

Thanks!
waikun
Posts: 11
Joined: 11 May 2013, 18:23

Re: nil values after running on windows for some time

Post by waikun »

Hi Steven,

Yes, the problem is solved after a reboot (at least when I reboot to Mac OS X, have never tried rebooting into Windows again since I only use it for gaming).
About whether it happens when MFC is not running - I'll do some testing, but I don't know when I'll get around to do it, I hope I have some time tonight!
User avatar
Steven
CrystalIDEA Developer
Posts: 2294
Joined: 21 Dec 2009, 11:48
Location: CrystalIDEA headquarters
Contact:

Re: nil values after running on windows for some time

Post by Steven »

Hi,

thanks in advance, take your time, I'll be waiting as much as needed :smile:
waikun
Posts: 11
Joined: 11 May 2013, 18:23

Re: nil values after running on windows for some time

Post by waikun »

Hi Steven,

sorry it took so long, I've been busy with university lately.
I've tried a few times, and it seems like the symptoms only appear when MFC is running... But contrary to what I've said before, it sometimes takes only a few minutes (if even) before all sensors show 0. Also, the fan speed doesn't reset until I reboot into Mac OS X and start MFC up (I guess anything that controls the fans would work); the operating systems won't return the fans to normal speed themselves.

Here is a screenshot:

ps: sorry for the huge screenshot size, the image seems really small on the rmbp...
Attachments
MFC_broken.PNG
MFC_broken.PNG (35.55 KiB) Viewed 49910 times
User avatar
Steven
CrystalIDEA Developer
Posts: 2294
Joined: 21 Dec 2009, 11:48
Location: CrystalIDEA headquarters
Contact:

Re: nil values after running on windows for some time

Post by Steven »

Looks like the problem is with SMC

1. What if you reboot in Windows back (not into mac). Does it happen again?
2. I'm not sure how MFC can do that. Do a clean reboot into Windows, don't run MFC for a couple of days in Windows. Then run it and see if displays zeros
3. Have you applied http://support.apple.com/kb/dl1559
User avatar
Steven
CrystalIDEA Developer
Posts: 2294
Joined: 21 Dec 2009, 11:48
Location: CrystalIDEA headquarters
Contact:

Re: nil values after running on windows for some time

Post by Steven »

I also have an idea that you might be running some other SMC program together with MFC
zk0sn1
Posts: 7
Joined: 10 Jul 2013, 18:02

Re: nil values after running on windows for some time

Post by zk0sn1 »

I have this exact same issue. Today running the latest. I have my fans set for fixed RPM. After an hour I'd say they show zero rpm. The temps were there, then I looked again and the temps all show 0 except for the SSD which seems to always register a temp.

I don't know what to look for in terms of conflicting programs (if any).

Machine:MacBookPro10,1
Fans:Left side-min{2151}curr{0}max{5917}mode{1,4002}Right side-min{1992}curr{0}max{5477}mode{1,4001}
TempSensors:TB0T,TB1T,TB2T,TC0E,TC0F,TC0P,TC1C,TC2C,TC3C,TC4C,TCGC,TCSA,TCTD,TCXC,TG0D,TG0P,TG1D,TG1F,TG1d,TH0A,TH0B,TH0V,TH0a,TH0b,TH0c,TH0x,TM0P,TM0S,TMBS,TP0P,TPCD,TS0D,TS0P,TS1D,TS1P,TW0P,Ta0P,TaSP,Th1H,Th2H,Ts0P,Ts0S,Ts1S
Values:Bottom Enclosure - 0,Battery Point 1 - 0,Battery Point 2 - 0,CPU Proximity - 0,CPU Core 1 - 0,GPU Diode - 0,DIMM Module 1 - 0,Airport Card - 0,Left Palm Rest - 0,APPLE SSD SM256E - 42,
User avatar
Steven
CrystalIDEA Developer
Posts: 2294
Joined: 21 Dec 2009, 11:48
Location: CrystalIDEA headquarters
Contact:

Re: 0 values on windows after a while (macbook pro retina)

Post by Steven »

It seems like the problem happens on MacBook Pro Retina (10,1) :(

I do recommend update SMC using
http://support.apple.com/kb/dl1559

Maybe it will help.
zk0sn1
Posts: 7
Joined: 10 Jul 2013, 18:02

Re: 0 values on windows after a while (macbook pro retina)

Post by zk0sn1 »

I checked my SMC in this KB. It's up to date.

Are there any alternative programs out there that read/monitor the same values?
User avatar
Steven
CrystalIDEA Developer
Posts: 2294
Joined: 21 Dec 2009, 11:48
Location: CrystalIDEA headquarters
Contact:

Re: 0 values on windows after a while (macbook pro retina)

Post by Steven »

Try closing BootCamp.exe on start-up and disable automatic startup of AppleOSSMgr.exe/AppleTimeSrv.exe services
zk0sn1
Posts: 7
Joined: 10 Jul 2013, 18:02

Re: 0 values on windows after a while (macbook pro retina)

Post by zk0sn1 »

I tried a few things.

Ending the bootcamp.exe process does allow Fan Control to run normally. If I start bootcamp.exe, Fan Control will eventually stop reading the values in under an hour. Only a reboot can get it back.

The two Apple services don't seem to matter.

If I leave bootcamp.exe running, and just periodically start and stop Fan Control there is no problem.

Something with bootcamp.exe and Fan Control is not compatible.

(backseat programmer suggestion. Make it so that fan control isn't polling the values so often? So they don't step on each other. I bet you'll have zero luck getting Apple to fix their buggy bootcamp.exe - It's always a crapshoot whether the fn buttons will work or not. I have had issues with both Macs I run in bootcamp mode)
waikun
Posts: 11
Joined: 11 May 2013, 18:23

Re: 0 values on windows after a while (macbook pro retina)

Post by waikun »

Hi,

thanks for the suggestions, I will try killing bootcamp.exe and see if it solves the problem. What exactly does it do, anyway?

By the way, I can confirm that the problem is not limited to rMBPs, a friend of mine had the same issue with a regular 13" 2012 MBP (Windows 7).

cheers
User avatar
Steven
CrystalIDEA Developer
Posts: 2294
Joined: 21 Dec 2009, 11:48
Location: CrystalIDEA headquarters
Contact:

Re: 0 values on windows after a while (macbook pro retina)

Post by Steven »

Thanks guys for letting know.

I cannot currently reproduce the issue on available hardware (iMac 2010, Macmini 2011). Thus cannot get it fixed :(

1. Try setting the fans to automatic mode and run MFC for a while together with BootCamp.exe. Does the problem happen?

2. When the issue happens, can you quit both MFC and BootCamp.exe, then restart MFC? Does it work?

3. BootCamp.exe file version?
User avatar
Steven
CrystalIDEA Developer
Posts: 2294
Joined: 21 Dec 2009, 11:48
Location: CrystalIDEA headquarters
Contact:

Re: 0 values on windows after a while (macbook pro 2012/retina)

Post by Steven »

4. Please test this. It will produce log.txt file, post it here when the problem appears.
zk0sn1
Posts: 7
Joined: 10 Jul 2013, 18:02

Re: 0 values on windows after a while (macbook pro 2012/retina)

Post by zk0sn1 »

1. Automatic seemed to be fine. Interestingly Sensor mode seemed to be fine too.

2. When I switched one fan to constant rpm, the values all went to zero after a few minutes. Closing mfc and bootcamp.exe and restarting mfc did not work. I observed that when mfc restarted it was very slow to populate the 0's.

3. I'm using 4.02, but I see there are newer versions.

4. I don't see a log.txt file. Where can I find it?
User avatar
Steven
CrystalIDEA Developer
Posts: 2294
Joined: 21 Dec 2009, 11:48
Location: CrystalIDEA headquarters
Contact:

Re: 0 values on windows after a while (macbook pro 2012/retina)

Post by Steven »

Sorry, this link, it must produce log.txt in its directory.

As far as I understand, the only current workaround is disabling BootCamp.exe from running together with MFC :(

What about updating BootCamp to 5.0 ?
zk0sn1
Posts: 7
Joined: 10 Jul 2013, 18:02

Re: 0 values on windows after a while (macbook pro 2012/retina)

Post by zk0sn1 »

I take back what I said about sensor based working. It also eventually fails.

Here's the log using fixed RPM

Code: Select all

 INFO 2013-07-19T16:28:53.739 "QMySysInfo::machineName ('')" 
 INFO 2013-07-19T16:28:53.739 "Starting on MacBookPro10,1" 
 INFO 2013-07-19T16:28:53.839 "QMySysInfo::machineName ('MacBookPro10,1')" 
 INFO 2013-07-19T16:28:53.839 "QFanControl::Init" 
 INFO 2013-07-19T16:28:53.839 "QFanControl::Init - LoadCachedFansAndTempSensors" 
 INFO 2013-07-19T16:28:53.839 "QFanControl::Init - FilterSupportedTempSensors" 
 INFO 2013-07-19T16:28:53.987 "QFanControl::Init - smc_get_fans_control_mode" 
 INFO 2013-07-19T16:28:54.003 "QFanControl::Init - QTempSensorSmart::LoadAvailableSensors" 
 INFO 2013-07-19T16:28:54.003 "Loading available SMART drives" 
 INFO 2013-07-19T16:28:54.003 "GetLogicalDrives returned 12" 
 INFO 2013-07-19T16:28:54.003 "Checking drive C:\" 
 INFO 2013-07-19T16:28:54.003 "Drive is fixed" 
 INFO 2013-07-19T16:28:54.003 "Phisical disk number: 0" 
 INFO 2013-07-19T16:28:54.008 "Adding drive \\.\PHYSICALDRIVE0" 
 INFO 2013-07-19T16:28:54.008 "Adding drive APPLE SSD SM256E" 
 INFO 2013-07-19T16:28:54.008 "Checking drive D:\" 
 INFO 2013-07-19T16:28:54.009 "Drive is fixed" 
 INFO 2013-07-19T16:28:54.009 "Phisical disk number: 0" 
 INFO 2013-07-19T16:28:54.009 "QFanControl::Init: number of supported SMC sensors: 9" 
 INFO 2013-07-19T16:28:54.009 "QFanControl::Init: number of supported SMART sensors: 1" 
 INFO 2013-07-19T16:28:54.042 "QFanControlMainWindow::FillFansTable: number of fans: 2" 
 INFO 2013-07-19T16:28:54.042 "QFanControlMainWindow::FillFansTable: adding fan Left side" 
 INFO 2013-07-19T16:28:54.042 "QFanControlMainWindow::FillFansTable: adding fan Right side" 
 INFO 2013-07-19T16:28:54.043 "QFanControlMainWindow::FillSensorsTable: number of supported sensors: 10" 
 INFO 2013-07-19T16:28:54.043 "QFanControlMainWindow::FillSensorsTable: adding sensor Bottom Enclosure (TB0T)" 
 INFO 2013-07-19T16:28:54.043 "QFanControlMainWindow::FillSensorsTable: adding sensor Battery Point 1 (TB1T)" 
 INFO 2013-07-19T16:28:54.043 "QFanControlMainWindow::FillSensorsTable: adding sensor Battery Point 2 (TB2T)" 
 INFO 2013-07-19T16:28:54.043 "QFanControlMainWindow::FillSensorsTable: adding sensor CPU Proximity (TC0P)" 
 INFO 2013-07-19T16:28:54.043 "QFanControlMainWindow::FillSensorsTable: adding sensor CPU Core 1 (TC1C)" 
 INFO 2013-07-19T16:28:54.043 "QFanControlMainWindow::FillSensorsTable: adding sensor GPU Diode (TG0D)" 
 INFO 2013-07-19T16:28:54.043 "QFanControlMainWindow::FillSensorsTable: adding sensor DIMM Module 1 (TM0S)" 
 INFO 2013-07-19T16:28:54.043 "QFanControlMainWindow::FillSensorsTable: adding sensor Airport Card (TW0P)" 
 INFO 2013-07-19T16:28:54.044 "QFanControlMainWindow::FillSensorsTable: adding sensor Left Palm Rest (Ts0P)" 
 INFO 2013-07-19T16:28:54.044 "QFanControlMainWindow::FillSensorsTable: adding sensor APPLE SSD SM256E (APPLE SSD SM256E)" 
ERROR 2013-07-19T16:43:39.378 "OS_WriteKey failed!" 
ERROR 2013-07-19T17:07:04.376 "OS_WriteKey failed!" 
ERROR 2013-07-19T17:09:34.382 "OS_ReadKey failed!" 
ERROR 2013-07-19T17:13:34.393 "OS_ReadKey failed!" 
....
TRUNCATED BY STEVEN.. hundreds of same ERROR entries
.....
ERROR 2013-07-19T18:12:35.367 "OS_WriteKey failed!" 
ERROR 2013-07-19T18:12:37.413 "OS_ReadKey failed!" 
ERROR 2013-07-19T18:12:39.459 "OS_WriteKey failed!" 
ERROR 2013-07-19T18:12:41.506 "OS_ReadKey failed!" 
 INFO 2013-07-19T18:12:42.340 "waitForThreadsFinished: m_ThreadUpdate = 1, m_ThreadInit = 0, m_ThreadControl = 1" 
 INFO 2013-07-19T18:12:42.540 "waitForThreadsFinished: m_ThreadUpdate = 1, m_ThreadInit = 0, m_ThreadControl = 1" 
 INFO 2013-07-19T18:12:42.740 "waitForThreadsFinished: m_ThreadUpdate = 1, m_ThreadInit = 0, m_ThreadControl = 1" 
 INFO 2013-07-19T18:12:42.940 "waitForThreadsFinished: m_ThreadUpdate = 1, m_ThreadInit = 0, m_ThreadControl = 1" 
 INFO 2013-07-19T18:12:43.140 "waitForThreadsFinished: m_ThreadUpdate = 1, m_ThreadInit = 0, m_ThreadControl = 1" 
 INFO 2013-07-19T18:12:43.340 "waitForThreadsFinished: m_ThreadUpdate = 1, m_ThreadInit = 0, m_ThreadControl = 1" 
 INFO 2013-07-19T18:12:43.540 "waitForThreadsFinished: m_ThreadUpdate = 1, m_ThreadInit = 0, m_ThreadControl = 1" 
ERROR 2013-07-19T18:12:43.552 "OS_WriteKey failed!" 
 INFO 2013-07-19T18:12:43.740 "waitForThreadsFinished: m_ThreadUpdate = 1, m_ThreadInit = 0, m_ThreadControl = 1" 
 INFO 2013-07-19T18:12:43.940 "waitForThreadsFinished: m_ThreadUpdate = 1, m_ThreadInit = 0, m_ThreadControl = 1" 
 INFO 2013-07-19T18:12:44.140 "waitForThreadsFinished: m_ThreadUpdate = 1, m_ThreadInit = 0, m_ThreadControl = 1" 
 INFO 2013-07-19T18:12:44.340 "waitForThreadsFinished: m_ThreadUpdate = 1, m_ThreadInit = 0, m_ThreadControl = 1" 
 INFO 2013-07-19T18:12:44.540 "waitForThreadsFinished: m_ThreadUpdate = 1, m_ThreadInit = 0, m_ThreadControl = 1" 
 INFO 2013-07-19T18:12:44.740 "waitForThreadsFinished: m_ThreadUpdate = 1, m_ThreadInit = 0, m_ThreadControl = 1" 
 INFO 2013-07-19T18:12:44.940 "waitForThreadsFinished: m_ThreadUpdate = 1, m_ThreadInit = 0, m_ThreadControl = 1" 
 INFO 2013-07-19T18:12:45.140 "waitForThreadsFinished: m_ThreadUpdate = 1, m_ThreadInit = 0, m_ThreadControl = 1" 
 INFO 2013-07-19T18:12:45.340 "waitForThreadsFinished: m_ThreadUpdate = 1, m_ThreadInit = 0, m_ThreadControl = 1" 
 INFO 2013-07-19T18:12:45.540 "waitForThreadsFinished: m_ThreadUpdate = 1, m_ThreadInit = 0, m_ThreadControl = 1" 
ERROR 2013-07-19T18:12:45.598 "OS_ReadKey failed!" 
 INFO 2013-07-19T18:12:45.740 "waitForThreadsFinished: m_ThreadUpdate = 0, m_ThreadInit = 0, m_ThreadControl = 1" 
 INFO 2013-07-19T18:12:45.940 "waitForThreadsFinished: m_ThreadUpdate = 0, m_ThreadInit = 0, m_ThreadControl = 1" 
 INFO 2013-07-19T18:12:46.140 "waitForThreadsFinished: m_ThreadUpdate = 0, m_ThreadInit = 0, m_ThreadControl = 1" 
 INFO 2013-07-19T18:12:46.340 "waitForThreadsFinished: m_ThreadUpdate = 0, m_ThreadInit = 0, m_ThreadControl = 1" 
 INFO 2013-07-19T18:12:46.540 "waitForThreadsFinished: m_ThreadUpdate = 0, m_ThreadInit = 0, m_ThreadControl = 1" 
 INFO 2013-07-19T18:12:46.740 "waitForThreadsFinished: m_ThreadUpdate = 0, m_ThreadInit = 0, m_ThreadControl = 1" 
 INFO 2013-07-19T18:12:46.940 "waitForThreadsFinished: m_ThreadUpdate = 0, m_ThreadInit = 0, m_ThreadControl = 1" 
 INFO 2013-07-19T18:12:47.140 "waitForThreadsFinished: m_ThreadUpdate = 0, m_ThreadInit = 0, m_ThreadControl = 1" 
 INFO 2013-07-19T18:12:47.340 "waitForThreadsFinished: m_ThreadUpdate = 0, m_ThreadInit = 0, m_ThreadControl = 1" 
 INFO 2013-07-19T18:12:47.540 "waitForThreadsFinished: m_ThreadUpdate = 0, m_ThreadInit = 0, m_ThreadControl = 1" 
ERROR 2013-07-19T18:12:47.644 "OS_WriteKey failed!" 
 INFO 2013-07-19T18:12:47.740 waitForThreadsFinished: Quit OK 
User avatar
Steven
CrystalIDEA Developer
Posts: 2294
Joined: 21 Dec 2009, 11:48
Location: CrystalIDEA headquarters
Contact:

Re: 0 values on windows after a while (macbook pro 2012/retina)

Post by Steven »

Ok, I have prepared new version with new implementation of OS_* layer. It really must work with BootCamp.exe without any problem!

Please test if it works for you (a reboot is required), a log is also welcome
User avatar
Steven
CrystalIDEA Developer
Posts: 2294
Joined: 21 Dec 2009, 11:48
Location: CrystalIDEA headquarters
Contact:

Re: 0 values on Windows after a while (macbook pro/air)

Post by Steven »

Changes are in 1.0.7 update
Post Reply