p870dm vortex 1070 upgrade error code

I ve got my hands on a portion of Vortex 1070 mxm cards to upgrade p870dm-g

unfortunately after flashing them with 86.04.42.00.03 non-Gsync vbios - they all give error code 43, while they do work with original Vortex vbios perfectly but only on external screen.

any suggestions? maybe different non-G vbioses anyone can share?

@Prema ? @woodzstack ?

 

This is like the 10th error 43 I've had someone report to me in the last 2 weeks.
before that, I've not seen an error 43 reported to me in like...months/years ?

Almost seems like a thing. I wonder if it's a vbios thing, but the fact it's all around the same time has got to be more than just a coincidence, unless it's simply an error code windows started using only recently for certain issues.

Others reporting black screens too, and I've asked them to try external monitors. Not heard back from all of them though, and they never reported flashing a new bios - but maybe they just didn't want to admit it or something, hard to say without proof.

Also, every summer NVidia does crap to eliminate older cards, it's always an "accident' or bad drivers or something, and shared through partners , but its like always the same time every year for the last decade, at first I used to think it must just be summer and the extra heat is killing cards via temps, but I've learnt otherwise.

I'm not one for conspiracies, but i do think NVidia and INTEL want you to keep buying new products every year or so, and continue that trend so they plan things to expire unreasonably, or help it along it's way, with releasing bad code that makes use of exposed vulnerabilities. Always just a bug though that gets patched once the damage is done.

As for this specific error code I have no idea to be honest, can you try the card in a g-sync setting with the proper g-sync vbios and compatible panel ? Is it just a vbios thing (I assume it is) or you think the card is faulty too ? Maybe these cards are not identical electrically to the others.

 

it's definitely a vbios/driver thing. with older drivers they work with the non-G laptop vbios.

with newest driver they work with stock Vortex vbios

with new driver

 

I dealt with this in my 1070 SLI thread.

What worked for me:

Downloaded "latest" G65VR-6RE drivers (375.70)
INF modded nvmd.inf with:

[NVIDIA_Devices.NTamd64.10.0...14310]
%NVIDIA_DEV.1BA1.0371.1558% = Section058, PCI\VEN_10DE&DEV_1BA1&SUBSYS_03711558

[NVIDIA_Devices.NTamd64.10.0]
%NVIDIA_DEV.1BA1.0371.1558% = Section057, PCI\VEN_10DE&DEV_1BA1&SUBSYS_03711558

and a device text string at the bottom that was different to see I was installing using the added strings above
NVIDIA_DEV.1BA1.0371.1558 = "NVIDIA GeForce GTX 1070 SLI"

(you would use the P870DM subsys instead of 03711558)

It worked - internal (eDP) and external screens, HDMI and DP out (I didn't have DP out with stock vortex vBIOS)

Current vBIOS working: 86.04.42.00.03

Haven't tried anything newer or drilled deeper into the INF to which driver component or setting was stopping it working (or which of the above two edits were what made the difference) - by then I was sick of disassembling and flashing vBIOS with programmer and dozens of DDUs and driver install restarts and I just wanted to use the thing.

edit some more notes:
- I don't have brightness control with any of the registry hacks I could find (but can still reduce brightness/contrast to something acceptable through nv control panel colour settings)
- Intermittent blackscreen auto-reboot crashes in only GTA5; which were greatly reduced in frequency some time ago by reseating the master card and squashed SLI cable, and since, has not occurred a single time with a locked GPU clock/volt profile...
- In the driver INF mod I started with just copying the string for 1BA1.11C2.1462 (matching what my stock vbios reported its subsystem as) which didn't install so I just tried the next one down 11C3 which is what worked

 

interesting that you needed to add the SLI string...

 

I didn't *need* to do that, I did it only to make life easier to instantly see that my added device id was being detected

 

Exactly. You could have called it whatever you wanted to for testing...

e.g. NVIDIA_DEV.1BA1.0371.1558 = "NVIDIA GeForce GTX 1070 Radeon Killer"

 

I am not sure I completely understand what exactly different have you made with the inf?

does it work with the most recent driver?

 

Basically just a standard INF mod for installing aftermarket cards

Compare the two files in the zip to see the insertions
line ~443
line~547
line ~7773

The SectionXXX bit was what I had to trial and error to get a driver successfully installed. When I copied it from the 11C2 line and changed the device ID, code 43 on install. Copied from 11C3 line, installed.

Since the SectionXXX is only a pointer, there is something buried down in the section (further into the INF file) that is the real issue - settings, registry entries, etc. Search for [Section056] and [Section058] and compare what's there side by side.

I haven't tried with most recent driver.

 

so a specific section was required for the card to work, right?

so that section was intended for Vortex?

 

I added the two files in a zip to my post above and where the lines were added

My starting point was the signed driver package for the vortex 1070 sli. I added the device ID so it'd install on my laptop. The sections I pointed to were the same as the vortex uses.

However copying the line for 1462.11C2 led to a code 43 - strange, since that was what was in my cards stock vBIOS. Copying from the line below 11C3 with its different SectionXXX number is what worked.

 

MSI seems to be screwing with their site, many product support pages 404. I thought I got it from the G65VR-6RE SLI page, but that says the most recent is 361.75 so maybe I'm wrong and it was from GT83VR or GT73VR or GT62VR. I can't remember.

Anyway here is the link to the driver package I downloaded:
http://download.msi.com/nb_drivers/vga/Win10Win8.1Win8Win7_Combo_x64(375.70)-1014834-01.zip

 

I see you have managed to install 382 driver?

 

Yes and no.

If you read the first couple of pages of my thread I documented everything I did in the initial setup, what worked, what didn't...

TL;DR 382.33 worked with the stock vBIOS (i.e. installed fine, ran the GPUs at 100% fine, and was able to provide display output via a remote connection software over Wifi - Teamviewer) but gave no Displayport out, and didn't even run the backlight of the internal eDP panel once it came. 382.33 only ever gave display output via HDMI-out.

http://forum.notebookreview.com/thr...0em-an-adventure.806069/page-11#post-10570969
This post outlines my results with 382.33 and many, many different vBIOS versions... None, even if they installed successfully without error codes, gave me everything (eDP+DP+HDMI) - not even trying just about every vBIOS I could find.

 

You need 86.04.31.00.0C
Link:
https://pl.msi.com/Laptop/support/GT62VR-6RE-Dominator-Pro.html#down-firmware
For non G-Sync
I have reworked 2 clevos 870 dmg with 2 gtx 1070 from vortex . Only 1 compatible vbios for 1070 rev 02s (from vortex) working in p870 is from msi gt62vr.
I am using win 10 x64 with 384.94 driver.

 

When you say "rev 02s" what do you mean (printed on pcb top?)

I have rev 1.0 - the vbios that is in there now is gt62vr non gsync 1070 (a later version actually, 86.04.42.00.03)

Are you saying 384.94 installs and works? When you added the line in the INF, which device id did you use as a template?

 

rev 02 it means barcode sticker (small label) rev 1.0 it is pcb revision non vga card revision.
Just use posted vbios from my link.
here is moded 2 files :
https://ufile.io/unjur
I have gtx 1070 from gt62vr also and I don't remember which one is from vertex and which is from 62 vr :
%NVIDIA_DEV.1BA1.0870.1558% = Section090, PCI\VEN_10DE&DEV_1BA1&SUBSYS_08701558&REV_A1
%NVIDIA_DEV.1BE1.0870.1558% = Section090, PCI\VEN_10DE&DEV_1BE1&SUBSYS_08701558&REV_A1
...
NVIDIA_DEV.1BA1 = "NVIDIA GeForce GTX 1070"
NVIDIA_DEV.1BE1 = "NVIDIA GeForce GTX 1070"

Driver should be modified in 2 files :
nvami.inf and nv_dispi.inf

Yes 384.94 installs and works in driver whql disabled mode . Shift + reboot etc.

 

I got 5 cards from MSI Vortex and only 1 of them works with 86.04.42.00.03 without error.
Other 4 cards give me Error 43 after modding driver. I use mod from
bennyg with v375 from Vortex and its work. But its bad for me i want learn to do make any other drivers.
Also i try bios from Majster msi - 0C and use 2 files inf then i replace them to 384.94. Dont help me - i still got Error 43.
All 4 cards works fine in external display and forks fine if i try them to my MSI Vortex.

Idk why 1 card works. And my first 1070 from Msi vortex (i sold her) also works on MSI GT72.

 

Like I said I have 2 vortex card 02s and it works in 2 different p870dm-g. I don't know why yours gives error 43 .

 

Where i can check revision my card?

 

On sticker next to gpu.

Wys?ane z mojego SM-G950F przy u?yciu Tapatalka

 

Have you tried flashing a Gsync vbios with programmer?

 

I got all 02s and last card from 5 also 02s but it works. 1070 non sli g-sync - 03s.

 

Which driver are you using? Because the problem is with the newer driver, older drivers work perfectly.

 

Yes 384.94 it installs and works .


Wys?ane z mojego SM-G950F przy u?yciu Tapatalka

 

Which vbios are you running again?

And which system bios on p870dm?

 

Yep - black screen no image at all.
I am sitting on original clevo bios newest for p870dm-g from provided webpage:
1.05.07
P870DMG.07
Vbios - 86.04.31.00.0C
I found new bios from sager:
https://www.techinferno.com/index.php?/forums/topic/11352-latest-bios-p870dm-g/
Today I will try it.
I would like to test prema bios however it is not for all users...

 

Yes, all gsync (1BE1) vBIOS I tried gave no display

 

i tested on DMG.08 - Error 43. DM.08 - Error 43

 

windows 10?

 

@Prema: is it possible to mod stock Vortex bios to display on EDP?

 

Yep. On win 7 it will not work gtx 1070 gives image only on uefi as far as I know.

 

you can install win7 on uefi in Clevo laptops

 

can you confirm that the latest 384 drivers installs on your system after DDU cleanup?

 

Nope, I tried that. After a few hours of fight for run Windows 7 installer, installation hangs at disk.sys driver loading.

 

hm, weird, as I have managed to do that on ZM machine before. could be my false memory though, haha.

 

I've got a couple of those Vortex cards.
I can say that the first one shows error 43 with new drivers but works fine with older drivers (thanks to @woodzstack for pointing that out).
The second card doesn't show error 43 with new drivers but it has those infamous voltage related crashes.
Go figure.
My theory is that those cards didn't work as intended in their original Vortex machines (probably error 43 while in SLI or voltage crashes as well).
That's why they have been returned, stripped and since probably all those cards sort of worked separately - they have been resold separately through this refurbishing company.
That would explain the price, by the way. Maybe that was a sneaky way of MSI to sell problematic cards again. I wouldn't be surprised, honestly.

And seems like non G-sync cards do work in both UEFI and UEFI with CSM modes (at least mine do).
So I think it might be possible to test them in Windows 7 in UEFI with CSM mode.

 

That was my developing suspicion too. I've had intermittent crashes in GTA5, a couple of things I've done seemed to help, but not a single crash when locked to a fixed clock/volt profile (through MSI AB. I'm working upwards slowly but 1775mhz/0.85V is stable so far)

I'd be happy if the 8A vbios worked (the troubleshooting one from earlier this year that disabled TB3.0 - its a 1BE1 so it didn't work for me) - turboing higher when its not being used to its power limit seems rather pointless.

 

381 driver works on 870DM if modding as
bennyg (replace 11C3) then 382.33 install above with same mod, then 384 install with same mod and works nice.
But if driver unnisltall and install new 382 or highter will error 43

 

The best benchmark for those crashes is the Ghost Recon Wildlands. Sometimes it crashed even while trying to load that benchmark, haha.
GTA V crashed more randomly though, could be 10-15 mins of play until the crash, could be hours... and GTA V benchmark ran fine.

8A for non G-sync cards would be a nice solution. But I'd rather have a vbios with that customised clock/voltage curve. That would be perfect, I think.
I'm keeping mine somehwere at 1847-1860mhz/0.875V. Also stable.

Huh, interesting... I'll definitely try this.
Thanks for the information!

 

@RandomID @nk4261 @bennyg thanks for all the information. you guys should all finish your profiles and make it look like your a more permanent addition to NBR local folk, we could always use more people like you guys.
Been a few people with the error 43 recently, some of these people have had thier cards working fine until new/latest drivers, so clearly it's something new and maybe the cards are still good.(except where the cards are not good, but use your judgement I'm saying)

gonna spread some rep and likes. Cheers !

 

that seems unrelated, as they all perfectly work with the original Vortex vbios.

I wonder if any of non-G MSI gt laptop owners have this same problem going on...

 

Bingo about msi gtx 1070 , unfortunately I can`t tell nothing more in public. There is special vbios for msi gtx 1070 to workaround in vortex and in all revisions however we have here clevo machine and nobody cares @ msi to work it in p870dm-g. All I said in this topics earlier should work in p870dm-g if not ... sorry you don`t have full working vga card.
BTW currently there is around 8 revisions of gtx 1070.
@woodzstack
You should give some reply about heatsink that you get it but you just forgot ... Finaly your client is now ordering from me. Some punishment .
Just for later use:
to get it work in clevo p870dm:
- vbios should be from msi gt62vr non gsync
- should be installed win 10
- driver doesn`t mater which version with edited 2 files - posted earlier
-driver should be installed in "test mode"
-in bios you have to switch to UEFI mode.
Regards .

 

8 revisions ?

 

DO I have rev 02S cards from the "1W0V102S" on the barcode next to the core?

 

Damn... What kind of thermal pads are you using?

 

gt83vr vbios did not help either only made it worse!

 

Worse in what way?

 

makes the screen flicker and the error still stays.

 

Ask MSI? That was at unboxing, they got a good clean up of all the goop around the core too

And my question about rev 02S?