Nightdex

I managed to resolve my flashing problem. I've emulated the 780m, that didn't solve my over clocking problems. I have noticed that my core clock doesn't fire up straight after a system restart like it use to before taking the 340.43 update. Nvidia Inspector allows me to over clock again, the moment I fire up Nvidia Control Panel, which obviously, is kicking my core clock in at 993mhz. It seems that I'm having to use more voltage with minor over clock settings, since taking the 340.43 update. I've supplied you with my stock vbios in your request thread matey. I was hoping that we could work together, to come up with a solution. I'm willing to test any vbios for stability ext.. I will also donate to you again, for putting so much effort into this.

Tried if. I've tried to even emulate the 780m. It fixes my issue until I restart, I'm back to square 1. I isn't have this problem at all before I updated to the beta driver. That beta driver must have something to set a flag of some sort. Not just in the vbios, but somewhere else as a clean flash would resolve my problem if it was related to just the vbios.

I reverted back to stock. It appears I that I can still alter the core, memory and voltage, where as before, I couldn't at stock. With the latest driver, running +20 on the core clock in heaven. My driver crashes mid way through the test. My temps are at 73c (which is good), but I should be crashing at +20 on the core clock. I flashed the vbios from Slv and John, and yeah, let's not even go there. I don't think the vbios is broken in any way shape or form. I seriously think that Nvidia implemented something new in the latest beta driver. It's hammered my 880m, and the damn thing now acts worse than an Intel 4600HD.

Hi Slv, how you doing matey? I donated to you the day I downloaded the 880m vbios you came up with. I've since been having some odd problems with your vbios for the 880m. Nvidia Inspector, EVGA and MSI, all function as if my vbios is still stock after each computer restart. The only way I can get the over clocking functions working again, is to start Nvidia Control panel before opening Nvidia Inspector. I also have a few other problems, such as, driver crashes during Heaven Benchmarking. Plus, EVGA acts up with your current vbios for the 880m. I was wondering if you could take a look at my stock vbios and create me a more stable vbios for the latest beta driver if possible please matey? I've attached my stock 880m vbios link for you to take a look at. If you would like me to provide anything. I will be more than willing to do so, as I'm seriously reconsidering getting rid of my 880m at the moment. FileSwap.com : nightdex's stock 880m rom.rar download free

They don't have any problem as far as I know. I'm about to test it on Windows 7 now.

Well, before I updated to the latest beta driver, I had no problems over clocking my 880m. Now, since updating, I have nothing but problems over clocking. Here's just one of my problems. I restart my AW, instantly, I'm unable to over clock in any program. I have to start up Nvidia Control Panel to kick my vbios back in to action again. I'm in the middle of formatting to Windows 7, as I'm starting to think Windows 8.1 might be the issue. I'll post back with my findings. If it doesn't resolve my problem, that's it, I give up. I'm glad your 780m is functioning correctly matey.

Excuse me, what? I've been told that the 780m runs nicely regardless of whether you're running stock or modified. Shame that the same can't be said about the 880m. I'm in the process of downgrading to Windows 7, in hope that this fixed my problems. At this point, I'm thinking it could be Windows 8.1 at fault. It's not exactly renowned for being a very good OS.

Avoid the latest beta driver. It may kill Slv and John's vbios. It's crippled me left and right for the time being, along with a few other members here and over at NBR.

I don't see how would work since I have an AW with just 1 pin for the live.

What this Clevo convertor box you speak of matey?

No, I'll let you do the honours haha.

Cant, I have UEFI. I'll lose all my partition and what not. It's windows 8/8.1 or nothing for me.

If we can get someone on windows 7 to comment on the new driver. If those particular users still encounter the problem we face. I would say secure boot isn't causing the problem. Although, I would say without a shadow of a doubt, that Mr. Fox is indeed correct about the cancer that is "Secure Boot". At this point. I'm willing to try anything to bring my 880m back to life with Slv's and John's vbios. I don't care if I even have to try multiple vbios flashes and driver installs. I really don't care as long as I find a solution to my problem. Failing that, I'm done. I'll sell and get a 780m.

I hope you find a solution matey, I really do. I place my bet on it being #2. I really doubt it costs Nvidia a lot to manufacture these GPU's.. So I doubt they even care about fulfilling warranty replacements/repairs. Bad business practice if you ask me. Ive already joined in have my thoughts. I'll add more as I go along. I'm still attempting to resolve my problem. Sick of wasting my time on little problems like these, just because Nvdia or Dell/Alienware feel that need to toy with things that are already fine.

Personally, I wouldn't put much faith in the next mobile GPU from Nvidia. If this is the kind of practice they use these days, then I'm out. I've not spent over 3k to just get stuck with a throttled intel 4600HD. I will try anything at this point to resolve my problem.

I booted up today and I'm back to square one Mr. Fox. I've even reverted back to 337.88. As soon as I restart now. I lose the ability to over clock my memory and voltage. I'm done with all of this now. I'm getting rid of my AW 17. I'm going to put the money towards a 780ti SLI setup. I can't be doing with all of this messing around any more. I really don't understand how this latest driver could of killed my chances of over clocking. I've tried everything that's been suggested thus far. I think we're now at that brick wall. Thank you for all the help thus far brother Fox. I appreciate everything you have done for me. Edit: Ok, so I've come to realise that this is some sort of intermittent problem now. Nvidia Inspector will allow me to change the voltage and memory clock every now and again. I mean, before I loaded it up after a restart, It wouldn't let me change anything other than my core clock. I then closed the program and booted up 3D Mark 11. I opened up NI again at this point. This time, it allowed me to change all settings. I decided to then close NI again, just to reopen it to check if the settings are still enabled. Boom, back to the brick wall. I have no idea what the problem is. What's odd, is that the NI will allow me change my core clock all the way up to just over 500+. It will only allow me set the core clock above 100+ with my stock vbios. So NI does realise that I have a modified vbios still. I just don't know why NI won't let me change the memory clock and voltage. Slv, any thoughts matey? I've also got the same problem with MSI Afterburner. MSI doesn't even highlight the voltage settings, where as NI does sometimes. I've reflashed back to stock and then back to Slv's vbios around 6-7 times now.

Where to start.. Firstly, thank you very much for the 880m vbios Slv. I really appreciate it matey. Secondly, I've been running with the modified 880m vbios for the past week fine. Then last night, I decided to install the latest Nvidia beta driver. Boy was I an idiot for doing this. Somehow, I lost the ability to overclock my memory and voltage in EVGA and Nvidia Inspector. So anyway, I reverted back to my previous driver which worked fine alongside Slv's vbios for the 880m. This didn't fix my issue. So since then, I have flashed back to my stock vbios. This's where my problem begins. I've attempted to flash Slv's vbios back to my 880m. However, I'm now getting ID missmatch. I've tried the nvflash -6 filename.rom. My command is - nvflash -6 cus.rom. I typed YES in caps when prompted. However, Nvflash comes up with (ERROR I.D MISSMATCH) still. I never had this problem until now. Any help with this, would be highly appreciated. Sorry guys. I know this's not a good way to start off on a forum.