Hi,
I have an Inno3D Herculez X3 GTX 1070, which does not show any image. After ~30s, the monitor turns on and displays a black screen.
The card however is detected by the OS, GPU-Z shows 0 MB VRAM. The driver crashed during boot.
Visually the card is in very good condition. No visible signs of defects, all voltages are present and within reasonable range, but on the high side I think: Vcore = 0.9 V, Vmem = 1.5 V. Vcore measures ~250 mOhm according to my DMM.
This leads me to the assumption, that something VRAM-related is off. So the natural first step would be to run mats and check for errors.
Unfortunately, when I run mats (367) with two GPUs installed (monitor connected to the working one), I can run the test on the working card, but not on the 1070. It throws a warning that I should run
but when I do, the following error messages appears:
The 723 error codes are familiar to me, they also appear with other cards and I couldn't figure out what's the reason, but they never seem to actually matter... maybe the tools are not compatible with my mainboard/CPU?
Whatever, the lines highlighted in red seem to be related to the 1070 and don't look too good, right?
I cannot run mats even after running the above mods command and I'm kind of stuck.
Installing only the 1070 and running mats via the automated startup script yield no results. No logfile is created and the computer proceeds to the poweroff command.
Any suggestions are very much appreciated.
I have an Inno3D Herculez X3 GTX 1070, which does not show any image. After ~30s, the monitor turns on and displays a black screen.
The card however is detected by the OS, GPU-Z shows 0 MB VRAM. The driver crashed during boot.
Visually the card is in very good condition. No visible signs of defects, all voltages are present and within reasonable range, but on the high side I think: Vcore = 0.9 V, Vmem = 1.5 V. Vcore measures ~250 mOhm according to my DMM.
This leads me to the assumption, that something VRAM-related is off. So the natural first step would be to run mats and check for errors.
Unfortunately, when I run mats (367) with two GPUs installed (monitor connected to the working one), I can run the test on the working card, but not on the 1070. It throws a warning that I should run
Code:
mods gputest.js -skip_rm_state_init -mfg
Code:
CPU Foundry : AuthenticAMD Name : AMD Ryzen 5 1600X Six-Core Processor Family : 15 Model : 1 Stepping : 1 Version MODS : 367.38 OperatingSystem: Linux (x86_64) Kernel : 4.1.2-gentoo KernelDriver : 3.63 HostName : tinylinux Smbios version [0x208] is not supported gpu 0 dev.sub 0.0 --------------------------- PCI Location : 0x00, 0x27, 0x00, 0x00 DID : 0x1b81 Raw ECID : 0x005ff5800000004568470191 ECID : PHMX70-22_x-1_y02 Device Id : GP104 Revision : a1 NV Base : 0xf6000000 FB Base : 0xe0000000 IRQ : 11 ERROR: No responses on codec 0! Error 000000000723 : AzaliaController.InitExtDev Codec error detected Error 000000000723 : Global.CheckForAndInitAzalia Codec error detected Error 000000000723 : Global.InitPexAspm Codec error detected Error 000000000723 : Global.PerGpuInitializeCallback Codec error detected Error 000000000723 : Gpu.Initialize Codec error detected Error 000000000723 : Global.PrintGpuInitError Codec error detected Error 000000000723 : Global.InitializeGpuTests Codec error detected [COLOR="Red"]ERROR: Unable to determine current VGA mode, ax=0x4f03 ERROR: Unable to set VESA mode 0x3, ax=0x4f02 Error 000000000237 : Global.EnableUserInterface unable to set mode RmDestroyGpu failed[/COLOR] Error Code = 000000000723 (Codec error detected) ####### #### ######## ### ####### ###### ######## ### ## ## ## ## ### ## ## ## ## ### ####### ######## ## ### ####### ######## ## ### ## ## ## ## ### ## ## ## ######## ######## ## ## ## ######## ########
Whatever, the lines highlighted in red seem to be related to the 1070 and don't look too good, right?
I cannot run mats even after running the above mods command and I'm kind of stuck.
Installing only the 1070 and running mats via the automated startup script yield no results. No logfile is created and the computer proceeds to the poweroff command.
Any suggestions are very much appreciated.
Comment