Overclock.net › Forums › Industry News › Hardware News › [MR] 2011 MacBook Pros Crashing Under Load
New Posts  All Forums:Forum Nav:

[MR] 2011 MacBook Pros Crashing Under Load - Page 15

post #141 of 161

What?
post #142 of 161
Quote:
Originally Posted by Farfnarkle View Post
So what you're saying is that a software update cant change:
-clock speeds
-voltage
-fan speeds

Please don't be so ignorant. I AM NOT SAYING THIS IS OR IS NOT A SOFTWARE ISSUE, I am simply stating that your argument/logic is flawed.
Yes, please don't. Both of you need to read again... Bad reading comprehension is bad...
The 10.6.7 update does not throttle the cards or alter voltages. It was a driver issue.
Edited by PoopaScoopa - 3/22/11 at 1:10am
post #143 of 161
Quote:
Originally Posted by PoopaScoopa View Post
Yes, please don't. Both of you need to read again... Bad reading comprehension is bad...
The 10.6.7 update does not throttle the cards or alter voltages. It was a driver issue.
So you've thoroughly disassembled the code and analyzed it, in detail, yah?
Why upgrade?
(14 items)
 
Why overclock?!
(15 items)
 
 
CPUMotherboardGraphicsRAM
Core i5 760 ASUS 55i Sabertooth EVGA 960 4GB 8gb 1600mhz Vengeance 
Hard DriveHard DriveOSMonitor
120gb Intel 320 (OS) 500gb Samsung 850 Evo Win 7 64 Viewsonic VX2250-Wm 
PowerCaseMouseAudio
Seasonic G 550w Gold Lancool PC-K9B Logitech G5 X-Fi Titanium/AT-H700 
CPUMotherboardGraphicsRAM
Core i5 4690k Asus Z97 Sabertooth mk2 EVGA 970 8gb Kingston 1833mhz 
Hard DriveHard DriveCoolingOS
128GB Samsung 830 500GB Samsung 840 Evo allota fans but quiet! Win 7 64 
MonitorKeyboardPowerCase
Dell U2311H Rev. A01 Mechanical w/ Cherry Blues NZXT Hale 650w NZXT Phantom - white 
MouseMouse PadAudio
Anker CG100 Steelseries 9HD Sennheiser HD555 
  hide details  
Reply
Why upgrade?
(14 items)
 
Why overclock?!
(15 items)
 
 
CPUMotherboardGraphicsRAM
Core i5 760 ASUS 55i Sabertooth EVGA 960 4GB 8gb 1600mhz Vengeance 
Hard DriveHard DriveOSMonitor
120gb Intel 320 (OS) 500gb Samsung 850 Evo Win 7 64 Viewsonic VX2250-Wm 
PowerCaseMouseAudio
Seasonic G 550w Gold Lancool PC-K9B Logitech G5 X-Fi Titanium/AT-H700 
CPUMotherboardGraphicsRAM
Core i5 4690k Asus Z97 Sabertooth mk2 EVGA 970 8gb Kingston 1833mhz 
Hard DriveHard DriveCoolingOS
128GB Samsung 830 500GB Samsung 840 Evo allota fans but quiet! Win 7 64 
MonitorKeyboardPowerCase
Dell U2311H Rev. A01 Mechanical w/ Cherry Blues NZXT Hale 650w NZXT Phantom - white 
MouseMouse PadAudio
Anker CG100 Steelseries 9HD Sennheiser HD555 
  hide details  
Reply
post #144 of 161
Quote:
Originally Posted by PoopaScoopa View Post
Yes, please don't. Both of you need to read again... Bad reading comprehension is bad...
Quote:
The 10.6.7 update does not throttle the cards or alter voltages. It was a driver issue.
First, you need to reread my post Ill try to be as clear as possible:

I am not commenting on whether or not this is a hardware or software issue. My only statement is that saying that software cannot affect hardware temperatures. You said "they fixed it with software, therefore it cannot have been hardware" this is NOT TRUE.

Quote:
The 10.6.7 update does not throttle the cards or alter voltages. It was a driver issue.
First off

Second, lets say you can back this up with real data proving the fans, voltages, clocks, etc were not touched. That's all fine and good, but you're original conclusion of "software fixed it so its not hardware" is called "unjustified true belief", (Google epistemology if you want more info) which means that although you may be CORRECT you would be correct for the WRONG REASONS. Do you see now that i'm not disagreeing (in fact, I would help you try to convince the people calling this issue hardware related if you proved it), I'm merely pointing out flaws in your reasoning.
post #145 of 161
Quote:
Originally Posted by Farfnarkle View Post
First, you need to reread my post Ill try to be as clear as possible:

I am not commenting on whether or not this is a hardware or software issue. My only statement is that saying that software cannot affect hardware temperatures. You said "they fixed it with software, therefore it cannot have been hardware" this is NOT TRUE.



First off

Second, lets say you can back this up with real data proving the fans, voltages, clocks, etc were not touched. That's all fine and good, but you're original conclusion of "software fixed it so its not hardware" is called "unjustified true belief", (Google epistemology if you want more info) which means that although you may be CORRECT you would be correct for the WRONG REASONS. Do you see now that i'm not disagreeing (in fact, I would help you try to convince the people calling this issue hardware related if you proved it), I'm merely pointing out flaws in your reasoning.
If you would just quit being lazy you could read the details of the update yourself in the release notes. You can also read the Ars Review showing the crash when switching from integrated to discreet.

My GPU/CPU Temps and clocks have not altered since the update.
Feel free to try and keep arguing about something you don't own or understand though.
post #146 of 161
Quote:
Originally Posted by PoopaScoopa View Post
If you would just quit being lazy you could read the details of the update yourself in the release notes. You can also read the Ars Review showing the crash when switching from integrated to discreet.

My GPU/CPU Temps and clocks have not altered since the update.
Feel free to try and keep arguing about something you don't own or understand though.


Got Intel Burn Test? Furmark?

You know what they did? Fan speed control. And Obviously, running something near its TJmax is very safe.
Edited by Kand - 3/23/11 at 1:34am
post #147 of 161
Quote:
Originally Posted by Kand View Post


Got Intel Burn Test? Furmark?

You know what they did? Fan speed control. And Obviously, running something near its TJmax is very safe.
lol, the update wasn't just to change some fan speeds... Most people use a separate app for controlling the fans like SMCFancontrol anyways so they wouldn't notice any changes.

You keep asking for proof but you fail to provide any proof that heat was an issue in the first place. I'm getting similar temperatures as before the update was applied so there goes that one. Coolbook shows the same voltages as well. 100% CPU and GPU load right now without any problems.

Why are you even arguing about something you have no proof of?
post #148 of 161
Quote:
Originally Posted by Kand View Post


Got Intel Burn Test? Furmark?

You know what they did? Fan speed control. And Obviously, running something near its TJmax is very safe.
You don't know that's it for sure. Considering the issue was "freezing" and not "restarting" it's very likely a driver issue and not heat related.

According to the wiki for the issue, 10.6.7 has completely fixed it even when running GPU intensive benchmarks like SmallLuxGpu.

EDIT: Out of curiosity, what is the TJmax for the i5/i7 Sandy Bridge CPUs in the MBPs?
Kasuf
(9 items)
 
  
CPUMotherboardGraphicsRAM
Core i5 6600K ASRock Z170 Pro4 ASUS Radeon RX 480 ROG Strix Corsair Vengeance LPX 32GB 3000MHz 
Hard DriveCoolingMonitorPower
Samsung 850 EVO Noctua NH-D15 LG 34" Ultrawide (LG34UC98) Corsair HX750i 
Case
Silverstone FT05B-W 
  hide details  
Reply
Kasuf
(9 items)
 
  
CPUMotherboardGraphicsRAM
Core i5 6600K ASRock Z170 Pro4 ASUS Radeon RX 480 ROG Strix Corsair Vengeance LPX 32GB 3000MHz 
Hard DriveCoolingMonitorPower
Samsung 850 EVO Noctua NH-D15 LG 34" Ultrawide (LG34UC98) Corsair HX750i 
Case
Silverstone FT05B-W 
  hide details  
Reply
post #149 of 161
Quote:
Originally Posted by PoopaScoopa View Post
lol, the update wasn't just to change some fan speeds... Most people use a separate app for controlling the fans like SMCFancontrol anyways so they wouldn't notice any changes.

You keep asking for proof but you fail to provide any proof that heat was an issue in the first place. I'm getting similar temperatures as before the update was applied so there goes that one. Coolbook shows the same voltages as well. 100% CPU and GPU load right now without any problems.

Why are you even arguing about something you have no proof of?
Yes?


Here's a guy who has had the issue, but resolved it by setting fan speed control thru SMC.

His issues disappeared PRE APPLE OFFICIAL UPDATE.

If it really were a driver issue, he wouldnt be able to play those games, use the GPU or any sort.

But he did. Now, I'm going to ask him if he can rollback, give us a sample video of his MBP locking up.

Quote:
Here's how I fixed the overheating problem on my 15" Macbook Pro:

I got my new 15" Macbook Pro this tuesday. And I saw some people reporting about overheating problems on the new Macbooks. I tried to run Portal, but my computer froze after about 2 minutes playing. I got another crash when I tried to export a short 720p video in iMovie.
And we all know running ~5c near TJmax is VERY safe.
Edited by Kand - 3/23/11 at 1:49am
post #150 of 161
Quote:
Originally Posted by Kand View Post
Yes?

http://www.youtube.com/watch?v=s7_3V...layer_embedded

Here's a guy who has had the issue, but resolved it by setting fan speed control thru SMC.

His issues disappeared PRE APPLE OFFICIAL UPDATE.

If it really were a driver issue, he wouldnt be able to play those games, use the GPU or any sort.

But he did. Now, I'm going to ask him if he can rollback, give us a sample video of his MBP locking up.
lol ok. Your ONE guy vs everyone elses MBP that has been fixed. I already had 100% fans with smcfancontrol and was still able to reproduce the crash prior to the update. Obviously heat wasn't the issue and since none of my clocks or voltages have changed after the update you're going to have to try again.
Apparently you know more than Apple's own devs who posted release notes along with the update that you have failed to read yet continue to keep embarrassing yourself by posting more.
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Hardware News
Overclock.net › Forums › Industry News › Hardware News › [MR] 2011 MacBook Pros Crashing Under Load