So far I have only noticed this in Windows. Some times the temprature displays incorrectly, just shoots up to 80-90 (not really the actual temp) (sometimes it does this at startup). Then the fans increase to 6200-6300 RPMs and then later on the temprature reads correctly. Without any change in physical temp after a few minutes the actual readings are typically 45-50c. This is showing in AIDA64. Any ideas what is causing this? I will double check OS X to make sure its not doing the same thing.
-
toyota_scion_tc Notebook Consultant
-
Try a different program maybe. I know in the gaming review in this forum he said the program he used caused the incorrect values, so it might be the same one you're using.
-
toyota_scion_tc Notebook Consultant
I have considered this but the only reason I did when the temps claim its running 80-90c the fan kicks up to 6200-6300 rpm like it really is warm but its at room temp or slightly colder.
-
Try Hwinfo32 to see what values it reports.
Also run lubbos fan control (1.0 should be the latest version).
Set it to ATI 1gpu 2 fans.
Also, check your system monitor to see what could be using a lot of your cpu
D. -
toyota_scion_tc Notebook Consultant
Also another issue I have been having under both OS-X and under Windows the clock magically sets itself to the wrong time. I have it set not to automatically update and have it locked. Any ideas what could cause this?
-
try the following fix:
(credits: prasys, apple discussion)
1. Boot Windows
2. Click Start --> Run and type regedit. Click OK
3. The Windows Registry Editor should pop up. Navigate within the explorer to:
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\TimeZoneInformation
4. Right click on the empty space right below ‘TimeZoneKeyName’ and create a new Dword (32-bit). On 32-bit versions of Windows 7/Vista , you will only see D-WORD .
5. Rename the new DWORD as “RealTimeIsUniversal” (without quotes and its case-sensitive) .
7. Double click on the new DWORD and change its value data “0″ (thats a zero) to “1″ (one) . Its in hexadecimal. Click Ok.
8. Reboot to MacOS X , set the time properly and now boot back to Windows. You should notice the time should be alrighty -
toyota_scion_tc Notebook Consultant
Let me clarify, the problem isn't OS X and Windows not matching (cause they do) its randomly changing the entire system time. I can use only OS X for a while and all of the sudden the time randomly changes without warning. I can use Windows under bootcamp and the system time will randomly change without warning without the auto update time button selected. Both OS X and Windows clocks match exact.
MBP Early 2011 15" i7 issues
Discussion in 'Apple and Mac OS X' started by toyota_scion_tc, May 8, 2011.