No, problem.
I'm going to implement a driver name change so no conflicts arise in the next version.
No, problem.
I'm going to implement a driver name change so no conflicts arise in the next version.
Quote:Originally Posted by billdavis
could you review this dump.txt to see if everything appears to be ok
Looks just fine.
thanks, when i ran it for the first time my computer shut down. but... it was at 3am and i forgot to set back 1 of the 500 settings i changed that night
NEW Question,
@2900mhz with my ihs removed and Ceramique
mbm5 was reporting:
idle40 load51
core temp beta
idle31 load51
@3000mhz ihs removed & Coollaboratory Liquid metal
mbm5 was reporting
idle37 load46
coretemp beta
idle31 load42
also my water temp after cpu,chipset,2x7800gt is about 31c
so would the idle of 31c be about right or the 37c?
it is hard to beleive i got a 10c improvement from this tim but im now still priming @3000mhz both cores are with in 1c of each other
________
212 EXPORT
in x64 Edition with 8M Super Pi running to load CPU
comparing CoreTemp, NextSensor, MBM5, and Everest 3.00
http://img158.imageshack.us/img158/4...rest4vv.th.jpg
http://img515.imageshack.us/img515/9...ces24vu.th.jpg
Is this supposed to be working on my Rev E CPU?
I have a 3800+ 0601 BH-E4 CPU and it appears to be working correctly for me.
It works on all A64 CPUs.
The Coolest, you might consider editing the thread title to avoid confusion.
This way it suggests CoreTemp is for Rev F owners exclusively.
lolQuote:
Originally Posted by Nedjo
nice work dude. Will try this 2nite
any chance for prescott support?
Update:
Version 0.9.0.91 - 5th July, 2006
- Logging feature added - Just copy into Excel for easy graphing.
- Fixed a bug where some programs would cause the program's driver to fail.
i get an error :(
after clicking ok, the icon is visible in the system tray, but the window never appears and eats 50% of my cpu resources
I get an error also. Previous version worked fine.
Im getting the exact same error:mad: :(Quote:
Originally Posted by Praz
Quote:
Originally Posted by Praz
same
________
SEX TUBE
same here 3 :(Quote:
Originally Posted by Praz
got the error as well
Everybody will get the error, its a bad compile. TC neglected to test his release build (although he doesn't even have an A64). He has gone to sleep or work so it'll be a bit before its fixed. Hang in there.
lol whoops...
damn, i catch on to this only when a bugged version gets released, lol.
Hmmm, I'm sorry. I guess compiling and 4am don't mix to well.
I think it should work now, try it out.
works now thanks :)
temps look about right, I knew my temps reported in smartguardian were off...I just couldn't believe i was at 44C full load at 1.6v and using the stock cooler.
One observation of mine: CoreTemp doesn't seems to refresh the CPU frequency reading, but does VID. IMHO this makes logging CPU freq pretty useless b/c the same freq is being reported all the time. It just writes down freq CoreTemp detected when it was started.
Oh damn, you're right. lol. I guess I'm not paying attention :|
Either way can you let it run for a while and see if it crashes after some time?
Ran it for half an hour - no problems. :)Quote:
Originally Posted by The Coolest
Works now, only thing is it reports the stock vid not the oc vid, but gives me the oc frequency and not the stock one. :)
Theres a good 7-10c difference between core1 and 2. Guess i might have a bad mount with the water block.