Jump to content
EwinRacing Flash Series Gaming Chairs


Registered User (Promoted)
  • Content Count

  • Joined

  • Last visited

Community Reputation

10 Semi Elite

About JChristian

  • Rank
    Junior Member
  • Birthday 02/20/1996
  1. My issue: one of the two 680M GPUs started displaying an "Windows has stopped this device because it has reported problems. (Code 43)". My hardware: Clevo P37EM / Sager NP9370 My OS: Windows 10 Enterprise 2016 LTSB x64 I keep the OS always up-to-date (Windows LTSB only ships security and fix updates). I also have very few softwares installed. Basically, my computer was working normally, but today I was playing Overwatch (which I always play) and after some hours, I suddenly heard a Windows beep, the game froze and the computer restarted. When I was back at the desktop, I noticed the resolution was not right and then I opened the Device Manager to see that one of the 680M was giving a Error Code 43. Both GPUs appear on my BIOS setup, the BIOS correctly identifies them as 680M. I found it strange, so I check my GPU VBIOS and noticed something odd, one of them was at and the other was at (I get these drivers here). I know for a fact that since some older NVIDIA Driver, the VBIOS must be or else I got some errors on this SAGER model, so I flash 33 on both a while back. I then proceeded to flash the correct version again. When I run DDU I notice it only detects the VBIOS version for one of the GPUs, the other one doesn't show the VBIOS version. My results are: NV Driver 398.36 ROM 33 PCI BUS 2 working PCI BUS 1 error code 43 ROM 67 PCI BUS 2 working PCI BUS 1 error code 43 NV Driver 391.35 ROM 33 PCI BUS 2 working PCI BUS 1 error code 43 ROM 67 PCI BUS 2 working PCI BUS 1 error code 43 Can a Nvidia update or Windows update brick a GPU? How can I know if it's a software or hardware issue? I'm afraid that one GPU died as I don't have the money to replace it now and it would be difficult to find a spare new 680M (which is now old hardware) where I live. I'm panicking a little...
  2. Yes, long time ago, I don't remember if there was a problem or not at that time. Which one do you recommend nowadays?
  3. Because the game is only using 3072MB of VRAM... It's not overhating, the temp is below 90 Celsius as always, it ranges from 82 - 89. But this card has 4GB
  4. Already did it, in fact, I was using this tweak while doing this "report", as you can see, didn't work!
  5. While I was playing GTA V my core clock of the GPU 2 was dropping to ridiculous speeds. Take a look: The core clock on the GPU 1 is ok, 719MHz all the time, but the GPU 2 is at 100~200MHz all the time, only when I pause the game it goes back to 719MHz. This cause serious fps drop, it's not even "drop" anymore, the game is always at 20fps -ish because of this thing. The game would run 10x better if the core clock of the GPU 2 was normal, a 680M SLi is enough to run on high 1080p/60fps. 680M SLi Driver 350.12 VBIOS NVIDIA Everything stock Help, please.
  6. Guys, where can I get the ORIGINAL/STOCK vbios for the NP9370 / P370EM 680M SLi? UPDATE: Found http://www.techpowerup.com/vgabios/index.php?architecture=NVIDIA&manufacturer=&model=GTX+680M&interface=&memType=&memSize= So, which one do you guys recommend? Clevo Nvidia They are all from 2012 The newset is from 2012-09-12 00:00:00. It's Clevo and Nvidia
  7. I'm using stock 680M SLi ROM ( in my NP9370 and the Voltage is 0.837 V, what would change if I use the custom Clevo 680m -'OCedition'_revised_01 - OV 1000v? What this higher Voltage would help me in? Would Performance in-game be better? Any chance of it harm my notebook?
  8. This problem only occurs with the Sager NP9370 models that have 680M GPU.
  9. The problem is that I can't even upgrade to 880M as the this model needs a update in BIOS to support it... Well, someone needs to fix this shit, I didn't pay high $$$ to get old drivers... My next GPU probably will be an AMD. The problem seems to be specifically in the Clevo model, so this is more a Clevo fault then Nvidia.
  10. I hope, but they talked that they don't have this model to test right away, so they are trying to contact Clevo and bla bla... -.- Maybe in the next WHQL they (Clevo + nVidia) fix this thing.
  11. Yeah, it seems to be a problem that occurs ONLY with the 680M in the Sager notebooks, I already talked to Clevo/Nvidia, but nothing resolved. -.- Stock and custom Clevo GTX 680M ( doesn't work with the 337.88, just 335.23 or anything below that...
  12. Yes, a little, anyway, I changed to the default ROM again. The problem is that this last WHQL Driver from Nvidia doesn't work with any BIOS, nor default, nor custom. So, I'm currently using 335.23.
  13. After I play like a hour of TF2 on Ultra, my notebook is shutting down, maybe is something related to the custom ROM? With the old normal ROM I didn't have this problem playing the same game for much more time.
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.