Neo2-F Temps AGAIN!!!!!!!!!!!!!!

ok so this is supposed to be a forum right... people read your topics and then respond... Well Ive gotten no response on my last topic so Im gonna post it AGAIN! K8N Neo2-F Temps seem to be way high!. its giving idle readings on the CPU of about 55C WITH A THERMALTAKE BIG TYPHOON!! Not possible... no ow it also says the northbridge is runnin at about 29C. Is it possible that the board has the sensors backwards? I need help!!! I dont need to fry my Athlon64 3400+ now do I?

My Neo2 Plat does the same thing... since BIOS 1.5.
With a XP90/Artic S/ & running low V in a well ventilated case my CPU temps have always seemed warm. But they never exceed 52C @ full load according to SpeedFan, so I don't worry about it anymore.
As long as it's not smoking!
The weird thing is that my temps with my Dual Core Opty 165 are reported to be EXACTLY the same as my old Winnie 3000 at the same settings & voltages and everything else (H/S, case & etc) the same. Seems like with Dual Core it would be warmer, if anything under any circumstances....
A lot of mobo's temp sensors aren't all that accurate anyhow. My old ABIT NF7-S (NF2 chipset) board was widely known to report CPU temps 4C higher than actual, no matter what on a consistent basis.
I'm not sure if this condition exists on any other of Nvidia's chipsets or MSI's mobo's - it would be nice to know though.

Similar Messages

Neo2-V Temps and Timings

So I just got a Neo2-V.
CPU: P4 3.0c
Memory: OCZ Premier 3200, 2.5-3-3-7
HSF: Zalman 7000 ALCU + AS5
Temps:
The temps with the latest 610 bios idles at 41C.
With my p4p800, idle was at 28C. I know Asus is known to report 5C lower but 13C is quite a bit
On full load it jumps to 63C
Timings:
The timings are always at 2.5-4-4-8. The manual setting in the BIOS has no effect on it.
It worked with the original BIOS it came with, but being me I'd to go and get the latest drivers etc when I set this up.
Where can I get the older BIOS versions? I can't seem to find it on the MSI sites.

Quote
Temps:
The temps with the latest 610 bios idles at 41C.
With my p4p800, idle was at 28C. I know Asus is known to report 5C lower but 13C is quite a bit
On full load it jumps to 63C
Nobody knows how mobo makers calculate their temp measurement.
Every mobo maker have their own idle/load temp . So it's no need to compare them.
And I think there's no problem on yours, 41C idle is normal, 63C full load (assume you're using Prime95) is quite normal, it's around top fifty and low sixty.
Oops, it's if you're using stock HSF, but you're using 7000AlCU + AS5... so it's maybe BIOS problem (temp calculating problem) or you should try to reseat CPU, reapply thermal paste , and reseat HSF.
Are you using silent mode or full speed?

Temps Again!

Ok I got a p4 2.8E and a 865 Neo2-LS overclocked to 3400 Mhz at default voltage (rock stable!) running Seti@home for 1.5 hours now, everything is fne but my cpu temp is hitting 64-65 celsius under full load! case temp is 32 celsius.
At idle my cpu temp is 49-50 Celsius, I have read many threads in diffrent places about this being fine for the cpu (??) but will these load temps kill my motherboard? or will the board handle the higher temps?

Quote
Intel Aware of Pentium 4 Heat Problems
Heat is quickly becoming the issue with today’s processors especially Intel’s Pentium 4 processors. With the release of Pentium 4 Prescott version of the chip, Intel released a heat machine. Every credible industry analyst noted the Prescott for its heat problems.
Intel, at IDF in Taipei, Taiwan, admitted to the problems the company is having with heat, according to CoolTechZone sources at IDF. Intel needs to cut down on the heat processes if they want to be successful and competitive in the mobile market. AMD, concerned about heat, will announce its low-powered AMD Athlon64 2700+ processor later this year.
Steve Pawlowski, Director of Intel’s Microprocessor Lab, was discussing the issue with industry analysts at IDF, confirmed our close sources. According to Steve Pawlowski, it was always about performance, performance, and performance. Intel has always focused on producing the fastest chips possible in the given time. The heat never worried Intel before because it was not a concern.
The times are different now. Users, especially the enthusiast community wants the coolest chips possible due to overclocking purposes. Although Intel is against the overclocking practices, they can’t refuse the demands of their consumers.
Intel said, the problem is in the die of the processor where the memory and other chip circuitry are located. The chip giant also said it is working on improving case fans and heatsinks to dissipate heat in a more efficient way. "We can either limit the clock speeds or the frequency of the chips to reduce the amount of heat being produced," said company officials, confirmed by CoolTechZone sources. Ironically, limiting the clock speed and frequency will not cut it anymore. The company said its engineers are working hard on the equation.
Finally, Intel admits to having problems with heat. This is the first step to solving the heat issues the company is having with its Intel Pentium 4 Prescott processors. It will be interesting to see how Intel works with cooling manufacturers to try to improve fan and heatsink designs that can better deal with heat.

KT6 FISR CPU Temp (Again) !

My CPU has been operating at an average 55 degrees C for the past month and so I thought I would try to improve matters by using some Arctic Silver instead of the ShineEtsu thermal pad that I had originally installed the CPU with. So, I dismantled the PC, took-off the heatsink and fan, thoroughly cleaned the heatsink and CPU core of thermal pad debris and applied the "infamous" Arctic Silver Thermal compound in accordance with the Arctic Silver website instructions. Now, the CPU temperature is running about 2-3 degrees higher than before ! How annoying. The heatsink is mounted correctly and everything else is as before (except the additional 2-3 degrees in CPU temperature increase). The CPU is now operating at 57-58 degrees. Can I expect a significant improvement after the 200 hours Arctic Silver "burn-in" time or am I just destined to life with a HOT CPU ?
Cynically Yours
Technojunkie

I think that main problem with CPU and System temps. is the beliving that the fans (bad named as coolers) can get lower temps. than room one. The fans can only lower CPU and System temps almost and in the best case, at the limit of room temp. and not more, because they only move the air.- Water cooler systems are different as they can really can reach lower temps. than the existing surronunding temps. Those are really coolers. In the last 2 months the CPU in my PC has gone from 40 to 47 C. because in my country now is spring, with higher temps. and will shurelly reach more than 55 C. in summer with open case. As it don't reach over 65 C. think there is no problem. So, technojunkie, don't be bother with your temps. As Bas says, if PC works fine, leave it alone.
Cheers!

K8N neo2 plat Temp problem

Was wondering if anybody else has came across this problem or not. The Bios is reading cpu temp and sys temp at 44 and 43 C. While Temp monitors in windows such as pc alert is reading the the temps at 126 C. Bios Was just updated recently so its running 1.8. Probaly wouldn't have noticed but the pc started locking up during game play. So I started checking different areas and came across the temp difference.

Quote from: syar2003 on 23-May-05, 23:44:28
PcAlert isn't compatible with K8N Neo seies .
It screws up the corecell chip data (so don't ever use it).
Use SpeedFan , Motherboard Monitor (MBM5) , MSI corecenter , for readout through windows.
I thought I might add that in my personal experience corecenter is inaccurate with +12v rail, everything else seems to read the same between the 3 mentioned programs though.

Neo2 cpu temp sensor

I just flashed to bios 1.A4 and now when I use corecenter or speed fan it shows the cpu temp to be 123C which I know isn't correct. Any ideas what is up with that? Also when using mbm which board is closest on the config to this board?

The problem is most likely that corecenter is reading a false sensor. This can be caused by if you have recently run a different type of temp monitoring program such as motherboard monitor, which allows you to select which sensor you want to use. You might try installing that and selecting the correct sensor, this will put the correct sensor reading in MSI Core Center also. Since this post is older I'm not sure if you still have the problem, but either way hopefully this help...

MSI N560Ti Twin Frozr II OC Edition Temp to high

Hello svet, im from argentina too
Ive a problem with a MSI N560 GTX - TI Twin Frozr II / OC edition (1024 M )
Serial N: 602-v238-220b110905319
Like 4 months ago, one of the original fans from the cooler just broke up (stop working) so i got a Deepcool 4600 in replace
(this monster)
After installing in that moment the new cooler, temps went down like a champ (60ª full load temp)
A few days ago, i decided to recheck my temp again only to see how are the things going, and i found something weird
The GPU Temp was rising till 100º c in full load.
That was something imposible becouse in that case , the gpu will just stop working and the system will shutdown. So i decided to check the things , open up my V9 Black edition case, and check the thermal paste (artic silver 5) in the GPU. Nothing strange, i just reapply the tim and installed the vga again in place
Well , things went the same deal like before. Gpu hitting 100ª in like 8 - 9 seconds after opened a game, every time i just hit ALT TAB and drop to ws, the temp goes down to 35ª in like , i dunno, 3 seconds or less. Tab back in game, and after 5 - 6 seconds went up again
Just formated, installed clean drivers, same deal, but i managed to hit 80ª this time in cs:go (just to test) with vsync on tripple buffer , max settings and MAX_FPS 45
After a while (maybe less than a minute) temp hit again the 90º wall, and it was to late to keep testing.
Is it posible that a sensor is damaged? couse i didnt notice the heat that excesive inside the case, i mean i put my hand over the VGA (not touching, only hovering over) and the vga was hot but not at 100º def.
Is it posible for a card to cold that quickly? (from 100 to 30 in 5 seconds).
Can my bios be faulty?

btw this is the attachment
Code: [Select]
00, 04-06-2013 20:11:19, Hardware monitoring log v1.4
01, 04-06-2013 20:11:19, MSI N560GTX Ti Twin Frozr II
02, 04-06-2013 20:11:19, GPU temperature ,GPU usage ,Fan speed ,Fan tachometer ,Core clock ,Shader clock ,Memory clock ,Memory usage
03, 04-06-2013 20:11:19, 0 ,°C ,0.000 ,100.000 ,10
03, 04-06-2013 20:11:19, 1 ,% ,0.000 ,100.000 ,10
03, 04-06-2013 20:11:19, 2 ,% ,0.000 ,100.000 ,10
03, 04-06-2013 20:11:19, 3 ,RPM ,0.000 ,10000.000 ,10
03, 04-06-2013 20:11:19, 4 ,MHz ,0.000 ,1500.000 ,10
03, 04-06-2013 20:11:19, 5 ,MHz ,0.000 ,3000.000 ,10
03, 04-06-2013 20:11:19, 6 ,MHz ,0.000 ,5000.000 ,10
03, 04-06-2013 20:11:19, 7 ,MB ,0.000 ,3072.000 ,10
80, 04-06-2013 20:11:20, 32.000 ,0.000 ,100.000 ,0.000 ,50.625 ,101.250 ,135.000 ,78.965
80, 04-06-2013 20:11:21, 32.000 ,3.000 ,100.000 ,0.000 ,50.625 ,101.250 ,135.000 ,78.480
80, 04-06-2013 20:11:22, 32.000 ,2.000 ,100.000 ,0.000 ,50.625 ,101.250 ,135.000 ,78.480
80, 04-06-2013 20:11:23, 32.000 ,2.000 ,100.000 ,0.000 ,50.625 ,101.250 ,135.000 ,78.480
80, 04-06-2013 20:11:24, 32.000 ,0.000 ,100.000 ,0.000 ,50.625 ,101.250 ,135.000 ,78.480
80, 04-06-2013 20:11:25, 32.000 ,0.000 ,100.000 ,0.000 ,50.625 ,101.250 ,135.000 ,78.480
80, 04-06-2013 20:11:26, 32.000 ,0.000 ,100.000 ,0.000 ,50.625 ,101.250 ,135.000 ,78.598
80, 04-06-2013 20:11:27, 32.000 ,0.000 ,100.000 ,0.000 ,50.625 ,101.250 ,135.000 ,78.598
80, 04-06-2013 20:11:28, 34.000 ,0.000 ,100.000 ,0.000 ,882.321 ,1764.642 ,2097.900 ,80.098
80, 04-06-2013 20:11:29, 36.000 ,0.000 ,100.000 ,0.000 ,882.321 ,1764.642 ,2097.900 ,131.145
80, 04-06-2013 20:11:30, 60.000 ,99.000 ,100.000 ,0.000 ,882.321 ,1764.642 ,2097.900 ,167.520
80, 04-06-2013 20:11:31, 66.000 ,99.000 ,100.000 ,0.000 ,882.321 ,1764.642 ,2097.900 ,167.520
80, 04-06-2013 20:11:32, 73.000 ,99.000 ,100.000 ,0.000 ,882.321 ,1764.642 ,2097.900 ,167.520
80, 04-06-2013 20:11:33, 78.000 ,99.000 ,100.000 ,0.000 ,882.321 ,1764.642 ,2097.900 ,167.520
80, 04-06-2013 20:11:34, 83.000 ,99.000 ,100.000 ,0.000 ,882.321 ,1764.642 ,2097.900 ,167.520
80, 04-06-2013 20:11:35, 88.000 ,99.000 ,100.000 ,0.000 ,882.321 ,1764.642 ,2097.900 ,167.520
80, 04-06-2013 20:11:36, 91.000 ,99.000 ,100.000 ,0.000 ,882.321 ,1764.642 ,2097.900 ,167.520
80, 04-06-2013 20:11:37, 95.000 ,99.000 ,100.000 ,0.000 ,882.321 ,1764.642 ,2097.900 ,167.520
80, 04-06-2013 20:11:38, 99.000 ,99.000 ,100.000 ,0.000 ,882.321 ,1764.642 ,2097.900 ,167.520
80, 04-06-2013 20:11:39, 100.000 ,99.000 ,100.000 ,0.000 ,441.160 ,882.321 ,2097.900 ,167.520
80, 04-06-2013 20:11:40, 99.000 ,99.000 ,100.000 ,0.000 ,441.160 ,882.321 ,2097.900 ,167.520
80, 04-06-2013 20:11:41, 100.000 ,99.000 ,100.000 ,0.000 ,441.160 ,882.321 ,2097.900 ,167.520
80, 04-06-2013 20:11:42, 99.000 ,99.000 ,100.000 ,0.000 ,441.160 ,882.321 ,2097.900 ,167.520
80, 04-06-2013 20:11:43, 100.000 ,99.000 ,100.000 ,0.000 ,441.160 ,882.321 ,2097.900 ,167.520
80, 04-06-2013 20:11:44, 99.000 ,99.000 ,100.000 ,0.000 ,441.160 ,882.321 ,2097.900 ,167.520
80, 04-06-2013 20:11:45, 100.000 ,99.000 ,100.000 ,0.000 ,882.321 ,1764.642 ,2097.900 ,167.520
80, 04-06-2013 20:11:46, 100.000 ,99.000 ,100.000 ,0.000 ,441.160 ,882.321 ,2097.900 ,167.520
80, 04-06-2013 20:11:47, 100.000 ,99.000 ,100.000 ,0.000 ,441.160 ,882.321 ,2097.900 ,167.520
80, 04-06-2013 20:11:48, 100.000 ,99.000 ,100.000 ,0.000 ,441.160 ,882.321 ,2097.900 ,167.520
80, 04-06-2013 20:11:49, 100.000 ,99.000 ,100.000 ,0.000 ,441.160 ,882.321 ,2097.900 ,167.520
80, 04-06-2013 20:11:50, 99.000 ,99.000 ,100.000 ,0.000 ,441.160 ,882.321 ,2097.900 ,167.520
80, 04-06-2013 20:11:51, 100.000 ,99.000 ,100.000 ,0.000 ,882.321 ,1764.642 ,2097.900 ,167.520
80, 04-06-2013 20:11:52, 100.000 ,99.000 ,100.000 ,0.000 ,441.160 ,882.321 ,2097.900 ,167.520
80, 04-06-2013 20:11:53, 99.000 ,99.000 ,100.000 ,0.000 ,441.160 ,882.321 ,2097.900 ,167.520
80, 04-06-2013 20:11:54, 99.000 ,99.000 ,100.000 ,0.000 ,441.160 ,882.321 ,2097.900 ,167.520
80, 04-06-2013 20:11:55, 100.000 ,99.000 ,100.000 ,0.000 ,441.160 ,882.321 ,2097.900 ,167.520
80, 04-06-2013 20:11:56, 100.000 ,99.000 ,100.000 ,0.000 ,441.160 ,882.321 ,2097.900 ,167.520
80, 04-06-2013 20:11:57, 100.000 ,99.000 ,100.000 ,0.000 ,882.321 ,1764.642 ,2097.900 ,167.520
80, 04-06-2013 20:11:58, 100.000 ,99.000 ,100.000 ,0.000 ,441.160 ,882.321 ,2097.900 ,167.520
80, 04-06-2013 20:11:59, 100.000 ,99.000 ,100.000 ,0.000 ,441.160 ,882.321 ,2097.900 ,167.520
80, 04-06-2013 20:12:00, 100.000 ,99.000 ,100.000 ,0.000 ,441.160 ,882.321 ,2097.900 ,167.520
80, 04-06-2013 20:12:01, 100.000 ,99.000 ,100.000 ,0.000 ,441.160 ,882.321 ,2097.900 ,167.520
80, 04-06-2013 20:12:02, 100.000 ,99.000 ,100.000 ,0.000 ,441.160 ,882.321 ,2097.900 ,167.520
80, 04-06-2013 20:12:03, 100.000 ,99.000 ,100.000 ,0.000 ,441.160 ,882.321 ,2097.900 ,167.520
80, 04-06-2013 20:12:04, 100.000 ,99.000 ,100.000 ,0.000 ,441.160 ,882.321 ,2097.900 ,167.520
80, 04-06-2013 20:12:05, 100.000 ,99.000 ,100.000 ,0.000 ,441.160 ,882.321 ,2097.900 ,167.520
80, 04-06-2013 20:12:06, 100.000 ,99.000 ,100.000 ,0.000 ,441.160 ,882.321 ,2097.900 ,167.520
80, 04-06-2013 20:12:07, 100.000 ,99.000 ,100.000 ,0.000 ,441.160 ,882.321 ,2097.900 ,167.520
80, 04-06-2013 20:12:08, 101.000 ,99.000 ,100.000 ,0.000 ,441.160 ,882.321 ,2097.900 ,167.520
80, 04-06-2013 20:12:09, 101.000 ,99.000 ,100.000 ,0.000 ,441.160 ,882.321 ,2097.900 ,167.520
80, 04-06-2013 20:12:10, 101.000 ,99.000 ,100.000 ,0.000 ,441.160 ,882.321 ,2097.900 ,167.520
80, 04-06-2013 20:12:11, 84.000 ,0.000 ,100.000 ,0.000 ,882.321 ,1764.642 ,2097.900 ,78.598
80, 04-06-2013 20:12:12, 78.000 ,0.000 ,100.000 ,0.000 ,882.321 ,1764.642 ,2097.900 ,78.598
80, 04-06-2013 20:12:13, 74.000 ,0.000 ,100.000 ,0.000 ,882.321 ,1764.642 ,2097.900 ,78.598
80, 04-06-2013 20:12:14, 72.000 ,1.000 ,100.000 ,0.000 ,882.321 ,1764.642 ,2097.900 ,78.598
80, 04-06-2013 20:12:15, 70.000 ,0.000 ,100.000 ,0.000 ,882.321 ,1764.642 ,2097.900 ,78.598
80, 04-06-2013 20:12:16, 68.000 ,0.000 ,100.000 ,0.000 ,882.321 ,1764.642 ,2097.900 ,78.598
80, 04-06-2013 20:12:17, 66.000 ,0.000 ,100.000 ,0.000 ,882.321 ,1764.642 ,2097.900 ,78.031
80, 04-06-2013 20:12:18, 65.000 ,0.000 ,100.000 ,0.000 ,882.321 ,1764.642 ,2097.900 ,77.617
80, 04-06-2013 20:12:19, 61.000 ,0.000 ,100.000 ,0.000 ,405.000 ,810.000 ,324.000 ,77.617
80, 04-06-2013 20:12:20, 58.000 ,0.000 ,100.000 ,0.000 ,405.000 ,810.000 ,324.000 ,77.617
80, 04-06-2013 20:12:21, 55.000 ,0.000 ,100.000 ,0.000 ,405.000 ,810.000 ,324.000 ,77.617
80, 04-06-2013 20:12:22, 53.000 ,0.000 ,100.000 ,0.000 ,405.000 ,810.000 ,324.000 ,77.617
80, 04-06-2013 20:12:23, 52.000 ,0.000 ,100.000 ,0.000 ,405.000 ,810.000 ,324.000 ,77.617
80, 04-06-2013 20:12:24, 50.000 ,0.000 ,100.000 ,0.000 ,405.000 ,810.000 ,324.000 ,77.617
80, 04-06-2013 20:12:25, 49.000 ,0.000 ,100.000 ,0.000 ,405.000 ,810.000 ,324.000 ,77.617
80, 04-06-2013 20:12:26, 49.000 ,0.000 ,100.000 ,0.000 ,405.000 ,810.000 ,324.000 ,77.617
80, 04-06-2013 20:12:27, 47.000 ,0.000 ,100.000 ,0.000 ,50.625 ,101.250 ,135.000 ,77.617
80, 04-06-2013 20:12:28, 46.000 ,0.000 ,100.000 ,0.000 ,50.625 ,101.250 ,135.000 ,77.617
80, 04-06-2013 20:12:29, 46.000 ,0.000 ,100.000 ,0.000 ,50.625 ,101.250 ,135.000 ,77.617
80, 04-06-2013 20:12:30, 45.000 ,0.000 ,100.000 ,0.000 ,50.625 ,101.250 ,135.000 ,77.617
80, 04-06-2013 20:12:31, 44.000 ,0.000 ,100.000 ,0.000 ,50.625 ,101.250 ,135.000 ,77.617
80, 04-06-2013 20:12:32, 44.000 ,0.000 ,100.000 ,0.000 ,50.625 ,101.250 ,135.000 ,77.617
80, 04-06-2013 20:12:33, 43.000 ,0.000 ,100.000 ,0.000 ,50.625 ,101.250 ,135.000 ,77.617
80, 04-06-2013 20:12:34, 43.000 ,0.000 ,100.000 ,0.000 ,50.625 ,101.250 ,135.000 ,77.617
80, 04-06-2013 20:12:35, 42.000 ,0.000 ,100.000 ,0.000 ,50.625 ,101.250 ,135.000 ,77.617
80, 04-06-2013 20:12:36, 42.000 ,0.000 ,100.000 ,0.000 ,50.625 ,101.250 ,135.000 ,77.617
80, 04-06-2013 20:12:37, 42.000 ,0.000 ,100.000 ,0.000 ,50.625 ,101.250 ,135.000 ,77.617
80, 04-06-2013 20:12:38, 41.000 ,0.000 ,100.000 ,0.000 ,50.625 ,101.250 ,135.000 ,77.617
80, 04-06-2013 20:12:39, 41.000 ,0.000 ,100.000 ,0.000 ,50.625 ,101.250 ,135.000 ,77.617
80, 04-06-2013 20:12:40, 41.000 ,0.000 ,100.000 ,0.000 ,50.625 ,101.250 ,135.000 ,77.617
80, 04-06-2013 20:12:41, 40.000 ,0.000 ,100.000 ,0.000 ,50.625 ,101.250 ,135.000 ,77.617
80, 04-06-2013 20:12:42, 40.000 ,0.000 ,100.000 ,0.000 ,50.625 ,101.250 ,135.000 ,77.617
80, 04-06-2013 20:12:43, 40.000 ,0.000 ,100.000 ,0.000 ,50.625 ,101.250 ,135.000 ,77.617
80, 04-06-2013 20:12:44, 40.000 ,0.000 ,100.000 ,0.000 ,50.625 ,101.250 ,135.000 ,77.617
80, 04-06-2013 20:12:45, 40.000 ,3.000 ,100.000 ,0.000 ,50.625 ,101.250 ,135.000 ,77.617
80, 04-06-2013 20:12:46, 40.000 ,0.000 ,100.000 ,0.000 ,50.625 ,101.250 ,135.000 ,77.617
80, 04-06-2013 20:12:47, 40.000 ,0.000 ,100.000 ,0.000 ,50.625 ,101.250 ,135.000 ,77.617
80, 04-06-2013 20:12:48, 39.000 ,0.000 ,100.000 ,0.000 ,50.625 ,101.250 ,135.000 ,77.617
80, 04-06-2013 20:12:49, 39.000 ,0.000 ,100.000 ,0.000 ,50.625 ,101.250 ,135.000 ,77.617
80, 04-06-2013 20:12:50, 39.000 ,0.000 ,100.000 ,0.000 ,50.625 ,101.250 ,135.000 ,77.617
80, 04-06-2013 20:12:51, 39.000 ,1.000 ,100.000 ,0.000 ,50.625 ,101.250 ,135.000 ,77.617
80, 04-06-2013 20:12:52, 38.000 ,0.000 ,100.000 ,0.000 ,50.625 ,101.250 ,135.000 ,77.617
80, 04-06-2013 20:12:53, 38.000 ,0.000 ,100.000 ,0.000 ,50.625 ,101.250 ,135.000 ,77.617
80, 04-06-2013 20:12:54, 38.000 ,0.000 ,100.000 ,0.000 ,50.625 ,101.250 ,135.000 ,77.617
80, 04-06-2013 20:12:55, 38.000 ,0.000 ,100.000 ,0.000 ,50.625 ,101.250 ,135.000 ,77.617
80, 04-06-2013 20:12:56, 38.000 ,0.000 ,100.000 ,0.000 ,50.625 ,101.250 ,135.000 ,77.617
80, 04-06-2013 20:12:57, 38.000 ,0.000 ,100.000 ,0.000 ,50.625 ,101.250 ,135.000 ,77.617
80, 04-06-2013 20:12:58, 38.000 ,0.000 ,100.000 ,0.000 ,50.625 ,101.250 ,135.000 ,77.617

IMac (MB323LL/A) very hot to the touch. What are the normal temps?

I have a 20" iMac (MB323LL/A). When I feel the back of it (specifically the top-left corner, opposite of the DVD/CD drive), it feels extremely hot. The picture at http://tweetphoto.com/20424550 is a screen shot of the temperature readings. The program is iStat Menus.
Are the temperatures displayed in the screen shot normal?
I look forward to your responses. Thank you very much in advance.
- Ted

I am dead positive, those temps are just fine
*Now me, I'd not be so sure:)* One must use search intelligently & make their own assessment. My thoughts are here:
http://discussions.apple.com/thread.jspa?messageID=11627340
and elsewhere & I said I'd not post about iMac temps again, so sorry for this. It was too hard for me to let a statement like the above stand.
E.g. I'd occasionally seen *CPU temps like yours, 90°C*, prior to using 3rd party fan control. *Please note that even exceeds Intel's maximum storage temperature* of 85°C for Core Duos (lower if storing > 1 yr), from:
http://download.intel.com/design/mobile/datashts/30922106.pdf
but at least its below the recommended maximum junction temp of 100°C.
Your *PS temp of 83°C* is ever-so-slightly below it's capacitors' maximum operating temp of 85°C, "+For an *aluminium electrolyte capacitor at 85°C, an expected lifetime of 2000 hours is achieved* by selecting VR / VF = 0.8.+":
http://homepages.eee.strath.ac.uk/~bwwilliams/Book/Chapter%2016old.pdf
and elsewhere.
Your *HD bay temp of 54°C* is above the maximum even considered in the google HD failure rate study:
http://static.googleusercontent.com/externalcontent/untrusted_dlcp/labs.google.com/en/us/papers/diskfailures.pdf
see other refs in my post I linked to above.

Neo2 Platinum Temperature questions

hi,
2 questions i have to ask..
its useful to have them answered by somebody who knows somehting about a program called motherboard monitor...
question subject 1: Motherboard monitor shows 3 Temperature sensors. what are the correct settings for the sensors?
does anyone know of where there is a diagram of the locations of these sensors are situated on the board?
question subject 2: is 46-51'c (room temp 27'c) a good tempterature for a 3500+ A64 to be running at?
and if anyone else has an Akasa EVO 22 on their 3500+ a64 what are your temperatures? (please include room temperature, and typical RPM of fan)

Quote from: Kolian on 14-June-05, 07:01:35
I think I've some problems with temperature monitoring on my MoBo. For example, when I had ASUS A8V, my СPU (3000+) was running @2385MHz (1,6V) and max temperature with box cooler was 61'C (load). Now I've changed MoBo to MSI K8N Neo2, CPU is @2205MHz (1,52V) and its temperature with the same cooler is about 70'C ...
From what I understand different boards have their temp probes in slightly different locations, which will affect indicated temps.
I've also heard that the Neo2 reports temps 3-4C higher than actual (I'm not real sure about that though, if anybody has that scoop - lemme know).
Regardless, your temps are way high & I'd look into a more robust H/S than the boxed cooler. 70C is within meltdown range, 60C is toasty - 50's under load would be preferable.

How can you debug sudden freezes and restarts? Only overheating?

My iMac, under Win XP via Boot Camp, will freeze and restart unpredictably when playing games. I thought I had tracked it down to overheating, but it's not that simple. Is there any error logging at the BIOS level with Boot Camp or any record when it shuts itself off and restarts? I think it must be BIOS and/or hardware, since there are no Windows events that seem to be related. If it was a video or audio driver crash problem, wouldn't I get a BSOD and some sort of error log (since I have automatic restarting turned off in Windows)?
Does anyone know more about when the iMac hardware will trigger a restart due to heat issues? I thought I had solved this by using smcFanControl on the Mac side to bump up the fan speeds and then tracking it with SpeedFan on the Windows side. It worked great for 2 nights. Then the 3rd night, it crashed and restarted right away twice, and then played fine for an hour or more. The 4th night, it crashed and restarted 3 times in a row, within minutes, and we gave up, somehow restraining ourselves from tossing the Mac out the window onto the sidewalk.
According to SpeedFan, the first time it crashed, CPU temps were only at 16C, HD at 37C, and overall at 35C. The second time, CPU temps had gotten up to 25C. The last time, CPU temps again were only at 16C (i.e. it crashed so fast, we hadn't even started playing, so it was effectively idle). Other temps remained pretty constant the whole time.
Given all that, it's hard for me to believe it's a matter of overheating. Yet I have no idea what else it could be, or why upping the cooling seemed to fix the problem for 2 days, and then the next day we were back to square one.
I guess Boot Camp should come with a big sign, only for word processing. What a waste of time - everything else Windows I do in Fusion. The one thing I wanted to bother with Boot Camp for is almost impossible to do, play a simple, not even new or state of the art game. I'm at a total loss what's happening, now that my overheating theory seems to have blown away.

Hi. I just wanted to tell you that I have the exact same problem, only I've got a Mac Pro. Unfortunately, I don't have a solution for you, but I posted details about what I've found here: http://discussions.apple.com/message.jspa?messageID=7217936#7217936.

I need help with my for loop in this array

Ok well, I can't get my code to work. Also, please remember that this is just my draft so it isnt pretty. I will fix it up later so please look at it. The thing I want to do is look into the array for a time that matches what the user entered and return the toString() of that one. I know there is something wrong with my for loop but I cant figure how to fix it. please help. here is what i have so far:
import javax.swing.JOptionPane;
public class Runner
    public static void main (String[] args)
        String timeStr;
        int time, again, optiStr;
        Inbound[] in = new Inbound[25];
         in[0]=new Inbound ("",0,"On Time num0");
         in[1]=new Inbound ("",2,"On Time num1");
         in[2]=new Inbound ("",3,"Delayed num2");
         in[3]=new Inbound ("",4,"On Time");
         in[4]=new Inbound ("",5,"On Time");
         in[5]=new Inbound ("",6,"Canceled");
         in[6]=new Inbound ("",1,"Canceled num6");
         in[7]=new Inbound ("",8,"On Time");
         in[8]=new Inbound ("",9,"Delayed");
         in[9]=new Inbound ("",10,"On Time");
         in[10]=new Inbound ("",11,"Delayed");
         in[11]=new Inbound ("",12,"On Time");
         in[12]=new Inbound ("",13,"Delayed");
         in[13]=new Inbound ("",14,"On Time");
         in[14]=new Inbound ("",15,"On Time");
         in[15]=new Inbound ("",16,"On Time");
         in[16]=new Inbound ("",17,"Canceled");
         in[17]=new Inbound ("",18,"On Time");
         in[18]=new Inbound ("",19,"On Time");
         in[19]=new Inbound ("",20,"Canceled");
         in[20]=new Inbound ("",21,"On Time");
         in[21]=new Inbound ("",22,"Delayed");
         in[22]=new Inbound ("",23,"On Time");
         in[23]=new Inbound ("",24,"Cancled");
         in[24]=new Inbound ("",7,"On Time num24");
        do{
            timeStr = JOptionPane.showInputDialog ("In military time, what hour do you want?");
            time = Integer.parseInt(timeStr);
            if (time<=0 || time>24)
             JOptionPane.showMessageDialog (null, "Error");
             optiStr = JOptionPane.showConfirmDialog (null, "If you want Incoming flights click Yes, but if not click No");
            if (optiStr==JOptionPane.YES_OPTION)
//(ok this is the for loop i am talking about )
                for (int index = 0; index < in.length; index++)
                  if ( time == Inbound.getTime())
               JOptionPane.showMessageDialog (null, Inbound.tostring()); //return the time asked for
//               else JOptionPane.showMessageDialog (null, "else");
            }//temp return else if failed to find time asked for
//             else
//               if (optiStr==JOptionPane.CANCEL_OPTION)
//                 JOptionPane.showMessageDialog(null,"Canceled");
//              else
//                {Outbound.run();
//                JOptionPane.showMessageDialog (null, "outbound");}//temp
              again=JOptionPane.showConfirmDialog(null, "Try again?");
        while (again==JOptionPane.YES_OPTION);
}any help would be greatly appriciated.

rumble14 wrote:
Ok well, I can't get my code to work. Also, please remember that this is just my draft so it isnt pretty. I will fix it up later so please look at it. The thing I want to do is look into the array for a time that matches what the user entered and return the toString() of that one. I know there is something wrong with my for loop but I cant figure how to fix it. please help. here is what i have so far:
>//(ok this is the for loop i am talking about )
for (int index = 0; index < in.length; index++)
if ( time == Inbound.getTime())
JOptionPane.showMessageDialog (null, Inbound.tostring()); //return the time asked for
Inbound.getTime() is a static method of your Inbound class, that always returns the same value, I presume? As opposed to each of the 25 members of your array in, which have individual values?
Edited by: darb on Mar 26, 2008 11:12 AM

Stop Skype Automatic Update

I know there have already been threads for this, but I've looked, tried many solutions, and today skype once again downgraded itself to a newer version without my consent. Here are the steps I've taken to stop automatic updates:
- Disable automatic updates within skype options
- Disable Skype Updater services in services.msc
- Block 'download.skype.com' in my hosts file
- Delete any skype files in %temp%
After skype downgraded itself once again this morning (it does this every day now), the settings in skype options and services.msc had been reset, and there were more files in %temp% again. download.skype.com is still blocked in my hosts file, so I have no idea how it managed to downgrade itself this time. Did they change the download location since the old threads I've been reading were written?

Skype is now also updated by Windows Updates.
https://support.skype.com/en/faq/FA12050/how-can-i-update-skype-for-windows-desktop
To avoid this update to be pushed you need to hide the KB2876229 update in Windows Updates
https://support.microsoft.com/en-us/kb/2876229
http://blogmines.com/blog/how-to-hide-windows-updates-on-windows-8.1/

XP Pro fails at install with RAID 1 and 4GB RAM on P45 MB - help?

Hello all,
I am new to this forum so bear with me. Having read several threads I see that this forum is very helpful and responsive. Thanks in advance for all your help and please let me know if I could answer other questions that might help you diagnose this challenge.
System:
Antec 900 Case
MSI P45 Platinum MB
Intel Q9300 processor
4GB Corsair DDR2 800GHz
2 300GB VelociRaptors in RAID 1 configuration
Gigabyte HD3850 video card
Not sure if you need all of this, but am pretty sure you will need more. Please don't hesitate asking if you do.
My situation is that I can get the hard drives mirrored fine through BIOS using the JMicron controllers, but loading WinXP Pro 32 fails shortly after I insert the JMicron Additional Device floppy. I have tried several different versions of the device floppy files with the same result. The error I get is the blue screen Stop 0x0000007B notice that isn't helpful at all.
RAID is recognized perfectly when turned on. I just get the Stop 0x0000007B error that stops the installation. Not sure what to do. Although likely not relevent, I have some questions.
Will XP support 4GB RAM (2 x 2GB Corsair DDR2 800GHz)? If it only recognizes 3.2GB of it, will the additional memory cause such an issue as described above? If so, could I use just one 2GB module or do they need to be in pairs?
Should I scrap the JMicron controllers and uses the Intel controllers? I would like to think that this is not the remedy, as a neighbor of mine has installed several of these same systems but with Vista.
Thanks for all your help.
Kurt

Quote
It would appear the the last two core temperatures are too high, but I suspect that the sensors are bad for them. These temperatures were within a few minutes of powering the un-taxed computer.
Run some sort of CPU Stressing application (Prime95, Orthos or similar) to put all cores under full load and check your core temps again. See how the sensors respond.
Quote
Interestingly, when I powered the computer after Hibernation it took longer for Windows to resume than it does to completely boot up (resuming windows status bar at bottom of screen). However when I put the computer into Stand By mode it will resume really quickly.
That is normal: In Hibernation mode, all the data that is stored in system memory is copied to a file on your hard drive (basically an image of your system memory is created.) After that the system is completely shut down. When you restart the system, the RAM image is written back to the system memory.
In S3 Standby Mode, the system still supplies power to the memory. When you switch the system back on, nothing has to be written back to system memory, as everything is still there. That is why it is faster.
Quote
Is it Stand By that I should be more interested in because of the faster recovery?
Yes. For power saving, hibernation is the better alternative.
Quote
Two questions; one, what settings would I need to awaken the computer without the power switch,
Look in BIOS under "Wake Up Event Setup" and look at these settings:
- Wake Up Event By = [BIOS]/[OS]
- Resume From S3 By USB Device
- Resume From S3 By PS/2 Keyboard
- Hot Key
- Resume From S3 By PS/2 Mouse
Play around with these settings (I don't know what devices you use) and test what works best for your purposes. I am sure you will figure something out.

Best equivalent to Photoshop's Color Balance dialog

I'm trying to understand what's the most equivalent function to Photoshop's Color Balance dialog in Lightroom 2. e.g. suppose I move the Cyan/Red a bit toward the red to make the image more 'redish'. What LR2 action will produce similar results?
thanks!
David
PS: for reference, this is what the dialog looks like in CS2:

Photoshop does Color Balance with far more detail and multiple-input fine tuning options than LR, obviously. I mean look at the screen shot and all the options available there.
But in very general terms, and often, for many photographs and many shooters, this is all the Color Balance adjustment they need, moving LR's Develop>WB Temp to the right would have a similar effect to moving Cyan-Red to the right. Both should warm the shot. (Try moving these sliders while watching caucasian faces shot in outdoor light in the winter in the north... they'll go from pale to a slightly glowing tan to ruddy. Or white t-shirts or snow will go from a white or bluish-white to a pinkish-white in ordinary daylight.)
Just to keep you on your toes, moving the Tint slider to the left in LR's Develop>WB Tint will give a similar effect to moving Photoshop's Magenta-Green to the right. (YMMV of course, but personally, with a RAW shot taken with a Canon camera and no color profile sliders moved in the camera, I find moving the Tint slider in LR rarely helps a shot look better and so I usually leave that one untouched... but I often do warm shots to varying degrees using the Temp slider. I think some greyscale workers, or some color workers going for highly creative effects, like to use the Tint slider more than I do.)
Photoshop's Yellow-Blue would also, I believe, change the warming effect using different tones than Cyan-Red, similar to LR's Develop>WB Temp, again working in the opposite direction. The advantage of having two sliders that can warm or cool an image in Photoshop is that you can adjust the degree of yellow separate from red in warming, to give more or less of an orange tone to your warming as desired.
Amping up those Color Levels windows in Photoshop might give a similar effect to boosting Vibrance or Saturation in LR>Develop, though in Photoshop you can tinker with separate levels for separate primary tones, which in LR you could only try to approximate with Develop>Camera Calibration.
All these sliders may have unintended effects if your monitor and printer are not calibrated, or to the extent that you're using consumer-priced monitors or printers where color balance can be dicey at best.

Insane Preview memory leak?

Hello fellow mac users!
Wondering if anyone else has found a solution to this - have I missed something - is this currently normal?
(purchased mid 2014) Mac Mini Quad 2.3 Intel Core i7, 16GB 1600MHz (Crucial) ram
Mavericks 10.9.4 - Preview (7.0)
When opening up a photo or image in Preview everything seems fine until I attempt to edit it using 'Adjust Colour'... I just now tried opening an image 2000x1333pixels @ 72dpi file size 683kb... 10.7GB of my 16GB ram is free (only Safari and Preview running) ... I open 'Adjust Colour' and move the sharpening, saturation etc sliders up and down a bit .. bam system suddenly grinds to a slow treacle-like speed with only 7mb of ram free! As soon as I close Preview ram goes back to normal and all is well... now as the photo is only 683kb getting back to normal is just a bit slow as long as I don't try to do anything else - the other day I attempted to edit the colour on a 5.7mb photo... that took a long time to sort itself out with the system all but frozen solid for a few minutes.
This really is unacceptable - sure I have Photoshop etc but on my previous mac running Snow Leopard the only limitations editing in Preview were my system's specs and the frustratingly low 3GB ram it could use but still did a much better job than this... Preview was a surprisingly good, quick and easy editing tool for photos if you didn't need the in-depth tools of photoshop ... however like this almost useless for anything other than viewing.

Hi Barney,
Thanks for the reply despite being on the road ... yep grew up with jars of Molasses in the cupboard so ironically I would more readily associate with that than 'treacle' despite being pretty much the same thing (treacle is a little less thick than molasses... argh this is making me hungry remembering the rather tasty molasses flapjack I made back then!) ... ahem ok back on track!
Errrmm... image manipulation services .. like? um? ... I have Shades running to dim the screen a little but never had an issue with that on the old mac... lemme test turning that off to make sure ... nope exactly the same with Shades off.. hmm
Right now I have Mail, Safari, Skype & 685kb photo open in Preview... ram showing as 12.2GB free...
opening 'adjust colour' control panel.. 12.1GB...
open 'adjust size' and close it again without doing anything... now at 12.0GB...
move sharpness slider on 'adjust colour' to full... 8.03GB...
wait 7.99GB...
move temp slider to full .. 2.55GB left ...
saturation to full 302mb left ... sorry 275mb
...clicks 'reset all' button on 'adjust colour' control panel... 10.6GB left....
sharpness to full 7.05GB,
temp to full 5.25GB,
saturation to full 3.9GB,
reset 10.6GB....
temp to min 10.6GB,
Saturation to min 9.87GB,
sharpness to min 8.93GB,
reset 10.6GB... ok interesting! between resets I'm just adding each change to the last... lets try maxing these again...
ok sharpness max 9.75GB,
Temp max 8.89GB,
Saturation max 7.97GB...
ok... hmm reset10.5GB
right stress test - I will move up to full then down to min and back to almost full with every slider in here...
exposure 7.24GB,
contrast 2.09GB,
highlights 2mb!,
Shadows ok the mini didn't enjoy that - VERY slow but interestingly when it and finished doing what i asked of it (maxing,minimum, then back to almost max on that slider) it started climbing the free ram back up to 1.44GB...
saturation quite slow but then climbed back up to 1.36GB,
Temp again slow then climbed up to 1.51GB,
Tint down then climb to 1.56GB,
sepia again down to almost 0 then back up to 1.59GB
& last but not least sharpening semi-freezes with ram free down at almost 0 then back up to 1.40GB... assuming after 'highlights' 2mb low it would have eventually climbed back up?... ok nope...quick run through and got to shadows before it bottomed out and stays low around 8-12mb)
each ram amount I've given from my tests is the figure it stabilises at unless otherwise noted ...
ok closing Skype and Mail freed up another 120mb or so but then adjusted the shadows slider again to max,min then almost max.. bam free ram back to around 10mb... then gradually climbs back up to 300mb... right that is probably enough for now - and bear in mind I'm editing a small photo - reset and back to 12GB free now...
so conclusion for now - everything is pretty much ok unless you touch any of the 'adjust colour' sliders.. but once saved or reset sliders all is well again...

Neo2-F Temps AGAIN!!!!!!!!!!!!!!

Similar Messages

Maybe you are looking for