Hi guys,
Over the past few days, some of you may remember that I had encountered problems with my 880m after I installed the latest beta driver. I installed all known 880m drivers, plus emulated the 780m. None fixed my problem. So yesterday, I decided to perform a clean install of Windows 8.1. Upon running 3D Mark 11, I got through the entire test without any problems.
My stock score - 3D Mark 11
After testing with my stock vbios, I decided to go ahead and flash Slv's and John's vbios. Bare in mind, this vbios was released a few weeks prior to the beta driver. Anyway, as some of you maybe aware, Nvidia recently added the Sky Diver profile to it's latest driver. I've run 4 different benchmarks. Only 1 out of those 4 times I tried running 3D Mark 11, did I manage to get through the entire test without a problem. I'll tell you why now.
Settings in Nvidia Inspector - all tests performed with driver 337.88
Core/Memory/Voltage - Power set to 160% and Temperature set to 93c (Prioritize Temperature - Unticked)
1101/3000/1.050v
Failed within 5 seconds of the first test starting (submarine test).
Core/Memory/Voltage - Power and Temperature set same as above
1083/2900/1.050v
Failed within the exact time frame of the first test I performed (submarine test).
Core/Memory/Voltage - Power and Temperature set same as above
1063/2800/1.050v
Failed within the exact time frame of the first test I performed (submarine test).
Core/Memory/Voltage - Power and Temperature set same as above
1101/2600/1.062v
Score - 3D Mark 11
I've come to the conclusion that this may be memory related. It seems that I'm having to up the voltage to an outstanding 1.062 v in order to get through benchmark testing with just a slight +100 over clock on memory. If I just boost the clock, I get no problems what so ever. I should also mention, that I found out why I'm unable to over clock after restarting my AW 17. In HWINFO, my GPU is up and running, but the core clock isn't even firing up without opening a 3D program (game, nvidia control panel). As soon as I fire up a 3D program, my core clock fires up to 993mhz, and then I'm able to over clock once again. Bare in mind, that this doesn't happen on my stock vbios. My core clock fires straight up as soon as I boot back into Windows. This only happens with the modified vbios. Obviously that leads on to this being the vbios at fault. But where did this issue come from? I'm placing my money on the beta driver adding something. It's to do with the memory as far as I can tell. My temps never reached over 79c during testing, so I know it's not temp related. I also noticed that my core clock never boosts over 954mhz when running with my stock vbios. However, before this latest beta update. My core clock always boosted to 993mhz during benching. Suffice to say, I place my money on Nvida doing something to the 880m with this latest beta driver, which in turn, has completely crippled our chances over clocking the memory since no one here want's to run with a voltage sky high.
This is just 1 example of how my single 880m performed before installing the latest beta driver.
Core/Memory/Voltage - Power and Temperature set to 160% and 93c (Prioritize Temperature - Unticked)
1093/3000/0.050v
Score - 3D Mark 11
So from that score, I can 100% say that the beta driver did something.
Also, take a look at my Sky Diver scores (modified vbios but with default settings)
Driver 337.88 - Sky Diver
Driver 340.43 - Sky Diver
Notice that there's a slight drop in score with new the beta driver. That shouldn't be happening since driver 340.43 was suppose to be optimised for Sky Diver. Nvidia definitely cut corners, or implemented something with this latest beta driver.
I'm now done with testing until a solution comes our way. I've put so many hours into testing to come up with a solution these past 4-5 days. I'm so tired at this point brothers. It's time for me to start actually enjoying this AW 17. Until John or Slv come up with a solution, there is nothing more any of us can do, unless you specialise in that specific modding department. It a shame that it came to this. I was really enjoying number chasing, and comparing scores with brother Fox. I'm unable to do that now, but I do hope that some day soon, we can all start fully enjoying our 880m's once again.
My thanks go out to - Mr. Fox, Ethrem, members over at TechInferno, and most of all, John and Slv for giving me the pleasure of over clocking these past few weeks. It's been pleasure working by your sides guys. I hope to do it again sometime soon.
Over the past few days, some of you may remember that I had encountered problems with my 880m after I installed the latest beta driver. I installed all known 880m drivers, plus emulated the 780m. None fixed my problem. So yesterday, I decided to perform a clean install of Windows 8.1. Upon running 3D Mark 11, I got through the entire test without any problems.
My stock score - 3D Mark 11
After testing with my stock vbios, I decided to go ahead and flash Slv's and John's vbios. Bare in mind, this vbios was released a few weeks prior to the beta driver. Anyway, as some of you maybe aware, Nvidia recently added the Sky Diver profile to it's latest driver. I've run 4 different benchmarks. Only 1 out of those 4 times I tried running 3D Mark 11, did I manage to get through the entire test without a problem. I'll tell you why now.
Settings in Nvidia Inspector - all tests performed with driver 337.88
Core/Memory/Voltage - Power set to 160% and Temperature set to 93c (Prioritize Temperature - Unticked)
1101/3000/1.050v
Failed within 5 seconds of the first test starting (submarine test).
Core/Memory/Voltage - Power and Temperature set same as above
1083/2900/1.050v
Failed within the exact time frame of the first test I performed (submarine test).
Core/Memory/Voltage - Power and Temperature set same as above
1063/2800/1.050v
Failed within the exact time frame of the first test I performed (submarine test).
Core/Memory/Voltage - Power and Temperature set same as above
1101/2600/1.062v
Score - 3D Mark 11
I've come to the conclusion that this may be memory related. It seems that I'm having to up the voltage to an outstanding 1.062 v in order to get through benchmark testing with just a slight +100 over clock on memory. If I just boost the clock, I get no problems what so ever. I should also mention, that I found out why I'm unable to over clock after restarting my AW 17. In HWINFO, my GPU is up and running, but the core clock isn't even firing up without opening a 3D program (game, nvidia control panel). As soon as I fire up a 3D program, my core clock fires up to 993mhz, and then I'm able to over clock once again. Bare in mind, that this doesn't happen on my stock vbios. My core clock fires straight up as soon as I boot back into Windows. This only happens with the modified vbios. Obviously that leads on to this being the vbios at fault. But where did this issue come from? I'm placing my money on the beta driver adding something. It's to do with the memory as far as I can tell. My temps never reached over 79c during testing, so I know it's not temp related. I also noticed that my core clock never boosts over 954mhz when running with my stock vbios. However, before this latest beta update. My core clock always boosted to 993mhz during benching. Suffice to say, I place my money on Nvida doing something to the 880m with this latest beta driver, which in turn, has completely crippled our chances over clocking the memory since no one here want's to run with a voltage sky high.
This is just 1 example of how my single 880m performed before installing the latest beta driver.
Core/Memory/Voltage - Power and Temperature set to 160% and 93c (Prioritize Temperature - Unticked)
1093/3000/0.050v
Score - 3D Mark 11
So from that score, I can 100% say that the beta driver did something.
Also, take a look at my Sky Diver scores (modified vbios but with default settings)
Driver 337.88 - Sky Diver
Driver 340.43 - Sky Diver
Notice that there's a slight drop in score with new the beta driver. That shouldn't be happening since driver 340.43 was suppose to be optimised for Sky Diver. Nvidia definitely cut corners, or implemented something with this latest beta driver.
I'm now done with testing until a solution comes our way. I've put so many hours into testing to come up with a solution these past 4-5 days. I'm so tired at this point brothers. It's time for me to start actually enjoying this AW 17. Until John or Slv come up with a solution, there is nothing more any of us can do, unless you specialise in that specific modding department. It a shame that it came to this. I was really enjoying number chasing, and comparing scores with brother Fox. I'm unable to do that now, but I do hope that some day soon, we can all start fully enjoying our 880m's once again.
My thanks go out to - Mr. Fox, Ethrem, members over at TechInferno, and most of all, John and Slv for giving me the pleasure of over clocking these past few weeks. It's been pleasure working by your sides guys. I hope to do it again sometime soon.