I already posted in the hp8510 p available thread that hp put a new bios on their website, thats supposed to fix the graphical corruptions and system hangups.
New Bios is Version F.0C
My Hp 8510P did not have any Problems at all with VPu Recovers, BSODs or the green screen of death.
But anyway, i did flash the new Bios on my machine.
When i tried to oc my hd2600 with atitool i realized my card was working with 300 mhz for core and 400 mhz for for ram.
Ocing the card failed everytime i went for more than 50 mhz above stock speeds.
But with the new bios from HP ( Ver. F0C) i suddenly have these clocks displayed : 500mhz (core) 600mhz(ram) and the integrated atitool test renderer shows about 80 - 100 fps more
- before biosupdate : roughly 170 fps
- after biosupdate : between 250 and 280 fps
so this bios seems to unlock a lot of power, at least on my machine.
Will test some ocing tonight and see what else has changed.
please give some feedback if you updated your bios too !!
best
http://h20000.www2.hp.com/bizsuppor...&swLang=8&mode=2&taskId=135&swItem=ob-56616-1
__________________
-
Crimsonman Ex NBR member :cry:
That address doesn't exist... according to my computer
-
@ crimsonman
just edited the link - it should work now
already tried some ocing, and well what should i say
i was able to push the ram easily to 700 mhz ; - core was at 550 mhz.
so i guess the issue with the massively underclocked hd2600 is not present anymore.
And it looks like HP did not intend to downclock the card.
The low clocks seem to be just a bios- "bug", maybe it has something to do with a bad programming for the clockgenerator.
will do some further testing. but if this is stable and working we have already got some christmas present by hp.
-
When you o/c, you think you could run 3dmark 06?
-
i need to dl it first. but yes, i could do that
-
HOLY COW!
So underclocking was a bug and it's caused all these problems? OH MAN if that's true I'm so happy!
OC TIME BABY -
This is my first 3dmark06 result :
3439 points
@ stock speeds of 500mhz / 600mhz
//edit tested with a screen resolution of 1280 x 1024 //
Run on Xp Professional 32bit
edit // forgot to mention my driver is cat 7.11 //
Q : is this the correct resolution 3dmark needs to be run at ?
Anyway the tests i will run from now on will have this resolution. -
Crimsonman Ex NBR member :cry:
I got 3065
but I tested at 1280x1024...
-
That's so weird you guys, really :\ I tested at 1280x1024 in Vista and got 3312, 3308, 3312...I think I was (and still am) using Cats 7.09 though...
-
yeeehaw.....
so... first ocing result :
i set core to 526mhz and ram to 648mhz and i got
3625 points
thats an improvement i guess... looks promising
will go on testing and see how far i can go -
@ ackeron
i have some questions about your 3dmark results.
1. did you already flash your bios ?
2. were these results achieved with the new bios ?
3. what resolution did you use while benchmarking
// edit
and another step in sqeezeing performance out of the hd 2600 :
3696 points
core 540mhz - ram 657
// -
No these tests were pre-flash, done like...in September. I haven't had a chance to test post flash yet. They were at the standard 1280x1024. You can see the results in my review in the link in my sig.
-
oh well, in this case i´ll try the next run at the 1280x1024 resolution.
just completed another run at 1200x800 and i just broke the 3800 points
core 560mhz - ram 675mhz 3808 points
here´s the link at futuremarks result comparison
http://service.futuremark.com/orb/resultanalyzer.jsp?projectType=14&XLID=0&UID=12879359 -
Crimsonman Ex NBR member :cry:
Oh yeah!! I don't OC and I got 3225 with a 1280x1024 with 7.12 drivers and the new BIOS
http://service.futuremark.com/orb/resultanalyzer.jsp?projectType=14&XLID=0&UID=12880061 -
Boooyaaah....
just ran a test at 1280x1204 with these clocks
core : 574mhz
ram : 690mhz ( forgot the actual timing, but 690 (-1 or 2 )
and you won´t believe it my result was 3886
check it here : http://service.futuremark.com/orb/resultanalyzer.jsp?projectType=14&XLID=0&UID=12879850
for now i won´t go higher with the timings cause i can´t read the temps of my gpu. i really don´t wanna burn it right now.
but i guess the bios update has proven to be let´s say...... FANTASTIC
another positive thing seems to be the fan issue seems to be fixed.
the fan of course was running at full speed during the benchmarks, but already after 1 up to 2 minutes is slowed down.
it´s so gooood not to hear this thing........
-
Crimsonman Ex NBR member :cry:
That's awesome.
-
Very happy with the new bios. All I have to say is one problem down, one more to go. I feel like laughing at some of the people who said this problem wasn't fixable, but I will hold back until more time has passed. Now HP, go fix the fan!
-
The core should be able to go lots higher, mine went all the way to 775ish (no cooler, temps < 60C) but I back down to 750 if I need the power. Plus this thing loves having a high core speed since I got ~3800 at 1280x800 at 750/450 in 3D06. -
COD4 plays really well at WXGA resolution.
-
did you already check if this is still an issue ?
i just played crysis with a beamer ( extended display and switched primary and secondary display) so the 8510p not only had to display the game in 3d there still was the laptop lcd running in 2d mode.
the laptop got quite warm and the fan was running really fast, but about 5 minutes after i stopped playing the fan was slowing down. right now while i´m typing, about 10 minutes after i stopped playing the laptop still blows out warm air , but the fan is not very loud anymore.
i remember the fan running on full speed for 10-15 minutes without leveling down. That was mostly the time i could bare to stand , before restarting the laptop.
so i guess some improvements have been made concerning the fan issue.
i got to say thank you HP, you kinda made my day -
Oh I wasn't talking about that issue with the fan. I mean the low set points HP has for the fan to start up. The fan is supposed to turn on if the CPU >/+ 2%
Dang, even with the new bios, I can't play starcraft. It's funny I can play COD4, but not an old game like starcraft. -
hey guys i just ran it with the new bios and with 7.12 installed and i still get the same score
check it out.
http://service.futuremark.com/orb/resultanalyzer.jsp?projectType=14&XLID=0&UID=12884873
what could be the problem? -
it also doesnt even recognize my disk model and graphics card
-
// update //
i guess i have found the maximum of my card.
did do some testing to find out how far i can push the hd 2600.
last working setting for core/mem was 636mhz/686mhz.
i left the mem settings at 686. everytime i went above 640 for the core, 3dmark either got stuck or the whole system crashed. I guess i´m at the voltage limit now. Either the motherboard does not grant anymore power to the card, or the voltage settings for the card have to be changed.
Anyway, i´m quite happy with the results i have achieved.
All the test i ran today were in native resolution of 1650x1080, and it seems the screen resolution is not effecting the benchmark. 3dmark06 seems to set its own resolution.
here are my test results of today :
My specs again 8510P- c2d t7700 - hd2600 - 120gig / 7200 rpm - Xp Prof 32
All tests were run at 1650 x 1080, which did not have an effect to the results.
test 1
stockspeeds @ 1650x1080 temp : max 29°C 3434 points
http://service.futuremark.com/orb/resultanalyzer.jsp?projectType=14&XLID=0&UID=12892240
594 / 693 @ 1650x180 temp: max 32°C 3989 points
http://service.futuremark.com/orb/resultanalyzer.jsp?projectType=14&XLID=0&UID=12892528
636 / 687 @ 1650x180 max 33°C 4143 points
http://service.futuremark.com/orb/resultanalyzer.jsp?projectType=14&XLID=0&UID=12892807
well, i guess i´ve just broken the 4000 point barrier by far.
-
I suddenly don't regret buying the 8510p anymore. Lower CPU temperature, no more BSOD and a much faster GPU... that's what I call an awesome update!
Where can I see the speed that my GPU is running at? Couldn't find it anywhere in the CCC.
What tool do I need for overclocking my graphics card? Is it possible that the card gets damaged by OCing and will it void my warranty? -
Well you can be sure ocing will void the warranty. But if your notebook really does go up in smoke, Hp has to prove first that you did void the warranty.
Since this ocing is done software based at windows you probably will leave no traces.
So Hp will have to prove that you did void the warranty. Since this does cost time and money, your notebook will just be one of the countless "bad hardware cases "
fyi i did use the new AtiTool for overclocking.
temp monitoring is a little tricky. you can use amd gpu tool for temp monitoring. thanks at notyou for this tip. -
Is everyone using 7.12 now?
-
nope i guess not everybody. still on 7.11 and it´s working fine for me.
did you already do some ocing ?
i´m curious how far you guys can push it !!!
i have found the point of no return , when my hd2600 crashes. how about your cards , how far can you go ? -
wohoo, great news! Of course i instantly flashed my bios and ran 3DMark
But: I got the same result as i did with my old bios: 3350 @ 1280x1024
Then i oc'd my card to 575/675 and got 3771 @ 1280x1024! I'm trying to find the limit nowThank you HP for this update, waited so long for this!
(Using 7.11 with modtool and Vista 32)
Btw. with witch program do you guys monitor the temps?
edit: 3912 @ 600/700
edit #2: Ok, used AMD GPU Tool to monitor the temps. Run 3DMark again and at 600/700 i got a max temp of 47°C (avarage is around 43°C). Is this temp ok or too high? -
@ shambles.ch
the temp is way beyond what this card can endure. i guess we will not be able to push it to it´s actual limits.
i think the mobo won´t supply enough power.
i can easily push the core above 700 mhz when i don´t overclock the ram , and vice versa i can push the ram above 720 when leaving core clock at 500 mhz.
as you can read in my post above i am stuck at around 640mhz/690 mhz and i think there´s a voltage problem. i have not been able to push it further.
could you test if it´s the same for you ?
i am curious if it´s the voltage or my card thats preventing further overclocking. -
yeah, i think the card temps were too high...it crashed after playing CoD4 for 3mins
But why are your temps that low? -
oh, i meant your temps are within safe range. you could even go much higher.
about my temps .... hmmm, i actually don´t know why they are that low. i think they never went above 36 or 37 degrees.
maybe it has something to do with the os. since i see you are running vista 32, maybe the aero stuff is responsible for your higher temps ?? -
Crimsonman Ex NBR member :cry:
-
Are most of you guys using mobility modder? Would I actually get a difference in 3dmark06 by switching to ATI's 7.12 from HP's drivers?
-
@ jin07
don´t think the difference is that big.
i´ve installed the 7.12 and i´ve did a test run with maxed clocks ( 636/686) for my hd 2600 and received a similar result to the testrun i´ve done with catalyst 7.11
7.11 4143
7.12 4132
so i think this is within the typical range for measuring differences
i think there is no big difference between these two drivers, performancewise. -
I'm using 7.12, mobility modded:
1280x1024 3dmark06, stock clocks - 3347 - temps in the 60c range. ran the test 2 times, identical score. clocks confirmed at 500/600 though.
Ran the benchmarks from my own review again, got nearly identical scores (within 10fps).
I've come to the conclusion that the reason I never saw GPU errors is because my HD 2600 was working perfectly all along; that is, even though it always showed 300/400 as the clocks, they MUST have been 500/600 in high performance. Otherwise these scores make no sense.
Also, I think those OC'd temps in the 30s you guys are reporting must be from a different sensor. I'm guessing this because from talking to 8510p owners I've seen a temp increase across the board of about 5-10c, maybe because the fan runs less now (and the clocks are back to normal for most people). Thus the GPU temps under load should be 60+ like what I've seen.
I'd recommend trying Everest Ultimate (or whatever the uber edition is called), or loading SpeedFan 4.32 and watching the TEMP2 sensor, which is the GPU one.
Either way good stuff all around
I'll try OCing later today, for now gotta prep for xmas party -
With the new BIOS my HD 2600 overclocks to stable core: 675; memory: 837
-
did you do some testing with a 3d app, to see if it´s running stable in 3d ??
how is your 3dmark score with these settings ? i can only suppose, bit must be somewhere around 4500 points.
can you run a 3dmark bench and post the result here, maybe with a link to the result ? -
Counter Strike: Source: Video Stress Test:
Default: 96 FPS
Overclocked: 157 FPS
Half Life 2: Lost Coast: Video Stress Test:
Default: 57 FPS
Overclocked: 79 FPS.
I'm using moded Cat 7.12.
Nice overclock, eh? -
thats awesome !!!
how about the temps on your machine ?
how hot is the gpu ? could you measure the temps ?
and since this is the highest setting for the hd2600 i´ve seen yet, can you do the 3dmark06 test ? if you do, please post the result link also. thanks -
Will do as soon as I can.
I had an injury while skiing on Saturday (fell on the icy patch of snow) and broke some ribs on the left side and I can't move a lot without some serious pains :-(
Does the ATI Tool also record temps? -
Great, now that the ati2dvag BSOD are gone, I get a new kind of BSOD when using the benchmarks of Counter-Strike: Source and Half-Life 2 Lost Coast.
win32k.sys
blablabla
PAGE_FAULT_IN_NONPAGED_AREA
blablabla
STOP 0x00000050 (...)
I have the latest Catalyst driver via Modtool installed. I installed them without cleaning the HP provided drivers first. Could this be the problem? -
the error you described can have several reasons. The two i can offer you are pointing towards a memory problem or overclocking problem.
1.
The Stop 0x50 message indicates that requested data was not in memory. The system generates an exception error when using a reference to an invalid system memory address. Defective memory (including main memory, L2 RAM cache, video RAM) or incompatible software (including remote control and antivirus software) might cause Stop 0x50 messages.
2.
Due to overclocking ram can show the stop x00000050 error. Whenever ram is running with faster clocks than the specified ones these errors can occur.
maybe there are other reasons for it. but these are the ones i´ve heard quite often. -
I'm still on 3.2k 3dmark06 points, no improvement
-
let me guess , are you running vista?
looks like the vista results are mostly hitting the 3200 points while some xp users report about 3400 with stock clocks of 500/600 -
I deinstalled it and everything works fine now. I'm kinda glad it's not the laptop but on the other hand I'm pissed because Norton wasn't exactly cheap and now it's useless.
Well I will try to reinstall it and see if it helps and I'm definitely gonna call customer service.
I kinda liked Norton until now. It is unobtrusive and light on the resources, but it seems I'll have to look for something else. What kind of security software do you guys use? -
First thing i did was get rid of norton . avg or avast are good and free
-
Well, now that I'm able to OC, here's what I got so far in 3DMark06:
3275 points @ default speed
4135 points @ 654 Core 765 Memory
My system: WinXP Pro - Catalyst 7.12 - 2.2Ghz dual core - 2 GB Ram - 120GB HD 5400rpm
I guess the results are quite good. I'm not sure if some of the background processes like Quick buttons, Wireless assistant, etc are slowing things down.
I remember some people saying that the HD 2600 was underclocked. Is this still the case after the BIOS update?
@jerry66: Yeah I've used avast before and it's quite good. I bought Norton because I wanted a more comprehensive solution with firewall, anti-spam, etc. Norton is not the piece of bloatware that it used to be and I really hope I can fix the problem. -
Nice scores
I use AVG for my AV program. It's very lightweight; I see it auto-update every time I boot up and that's about it.
The HD 2600 is now clocked normally at 500/600 after the bios update.
I don't think background processes slow down a system like ours any significant amount, but I could be wrong
HP 8510P new Bios !!! improves HD 2600
Discussion in 'HP' started by schoko, Dec 22, 2007.