RTX 5070 discussion

:D:D · Wednesday at 12:40 PM

Just got a Palit GamerPro RTX 5070 12GB so sharing some findings.

It's the non OC model so 250W TGP max both VBIOS.

Can run Steel Nomad at around 3GHz @0.975V and 2125MHz mem for a score of 56 FPS, X99 mainboard and CPU are 10yrs+ now so a bit long in the tooth. PCIe 3 plus DDR4 2133MT/s RAM. See there are 60+ scores, don't know if that's with higher TGP (300W) or not.

Memory clock set to around 1653MHz results in artifacts / lockup requiring power button intervention, ugg. A few seldom times TDR to the rescue or even a bug check once with the nvidia driver. Thought it might be a driver issue but nobody else reporting this! Any thoughts @StViolenceDay ?

Voltage doesn't report dropping below 0.8V, well a drop to 0.795V sometimes, even in PState 8?

Seems very leaky, wouldn't like to try a HW volt mod with this one.

VRAM temps get a little high when loaded before fan kicks in, IIRC up to 96C if that temperature is correct.

Memory limits seem a bit restrictive, (-2000MT/s to +6000MT/s) wonder what the reason for that is.

So anyone else running one of these, what are your thoughts?

StViolenceDay · Wednesday at 12:56 PM

:D:D said:
Memory clock set to around 1653MHz results in artifacts / lockup requiring power button intervention, ugg. A few seldom times TDR to the rescue or even a bug check once with the nvidia driver. Thought it might be a driver issue but nobody else reporting this! Any thoughts @StViolenceDay ?

1653Mhz - do you mean underclocking VRAM? Or this value is offset? (i dont have a 5070, but I thought its default memory clock are 1750Mhz)

Actually since gddr7 has a lot of error detection mechanics including reporting the write errors to the GPU (so it can retry the write operation) - this is a first report about actually getting artifacts (instead of hangs/slowdowns) caused by GDDR7 memory tuning.

Please run the memtest_vulkan tool for 5 minutes (standard test):

on that 1653Mhz setting
on default frequencies

And it if would report any errors - attached its log file here, would be interesting to see the error details

Chrispy_ · Wednesday at 1:15 PM

Don't go on other people's scores in 3DMark. There will always be lots of high scores from people overclocking. Find a benchmark that shows a game you own, with the settings used, and check your card is within a few percent of that.

Your CPU will be a bottleneck at low-resolution/high-refresh, and your board's lack of ReBAR and PCIe 3.0 slot might be an issue if you are running AAA games at 4K with all the eye-candy turned on., because the 5070's 12GB isn't always enough, and it starts shuffling data over PCIe instead. At 1440p or below it shouldn't matter, just about every game still fits in 12GB at that resolution.

:D:D · Wednesday at 2:17 PM

StViolenceDay said:
1653Mhz - do you mean underclocking VRAM? Or this value is offset? (i dont have a 5070, but I thought its default memory clock are 1750Mhz)

Thank you for the reply. Yes, default 1750MHz and offset would be -97MHz at default PState 0.

StViolenceDay said:
Actually since gddr7 has a lot of error detection mechanics including reporting the write errors to the GPU (so it can retry the write operation) - this is a first report about actually getting artifacts (instead of hangs/slowdowns) caused by GDDR7 memory tuning.

StViolenceDay said:
Please run the memtest_vulkan tool for 5 minutes (standard test):

on that 1653Mhz setting

on default frequencies

And it if would report any errors - attached its log file here, would be interesting to see the error details

I can do default but not 1653MHz as it errors as soon as set.

Windows Event viewer after the fact. Example, not always the same.

Tried several driver versions plus latest for Windows, Linux driver 575 does the same. Can use nvidia-settings to replicate with a value of -1552MT/s (-97MHz) although it's shown in MHz for some reason.

I test BW but have to exclude that small ~8MHz band to avoid artifacts / system crash.

Test result at default 1750MHz

Code:

[alex@fedora memtest_vulkan-v0.5.0_DesktopLinux_X86_64]$ ./memtest_vulkan
https://github.com/GpuZelenograd/memtest_vulkan v0.5.0 by GpuZelenograd
To finish testing use Ctrl+C

1: Bus=0x03:00 DevId=0x2F04   12GB NVIDIA GeForce RTX 5070
2: Bus=0x00:00 DevId=0x0000   32GB llvmpipe (LLVM 20.1.6, 256 bits)
(first device will be autoselected in 0 seconds)   Override index to test:
    ...first device autoselected
Standard 5-minute test of 1: Bus=0x03:00 DevId=0x2F04   12GB NVIDIA GeForce RTX 5070
      1 iteration. Passed  0.0312 seconds  written:    7.2GB 570.7GB/sec        checked:   10.9GB 587.6GB/sec
     34 iteration. Passed  1.0303 seconds  written:  239.2GB 572.2GB/sec        checked:  358.9GB 586.2GB/sec
    195 iteration. Passed  5.0259 seconds  written: 1167.2GB 572.5GB/sec        checked: 1750.9GB 586.2GB/sec
   1156 iteration. Passed 30.0070 seconds  written: 6967.2GB 572.4GB/sec        checked:10450.9GB 586.0GB/sec
   2118 iteration. Passed 30.0244 seconds  written: 6974.5GB 572.7GB/sec        checked:10461.8GB 586.3GB/sec
   3080 iteration. Passed 30.0188 seconds  written: 6974.5GB 572.8GB/sec        checked:10461.8GB 586.3GB/sec
   4042 iteration. Passed 30.0271 seconds  written: 6974.5GB 572.6GB/sec        checked:10461.8GB 586.2GB/sec
   5004 iteration. Passed 30.0217 seconds  written: 6974.5GB 572.7GB/sec        checked:10461.8GB 586.3GB/sec
   5966 iteration. Passed 30.0229 seconds  written: 6974.5GB 572.7GB/sec        checked:10461.8GB 586.3GB/sec
   6928 iteration. Passed 30.0208 seconds  written: 6974.5GB 572.7GB/sec        checked:10461.8GB 586.3GB/sec
   7890 iteration. Passed 30.0275 seconds  written: 6974.5GB 572.5GB/sec        checked:10461.8GB 586.2GB/sec
   8851 iteration. Passed 30.0011 seconds  written: 6967.2GB 572.5GB/sec        checked:10450.9GB 586.1GB/sec
Standard 5-minute test PASSed! Just press Ctrl+C unless you plan long test run.
Extended endless test started; testing more than 2 hours is usually unneeded
use Ctrl+C to stop it when you decide it's enough
^C
memtest_vulkan: no any errors, testing PASSed.
  press any key to continue...
[alex@fedora memtest_vulkan-v0.5.0_DesktopLinux_X86_64]$

StViolenceDay · 2025-07-03T14:34:58+0100

BTW whats the VRAM vendor displayed in GPU-Z and exact VBIOS version?

Maybe VBIOS has timings/freq ranges table different from "most common". From the exoerience of 1660S I can say that thete can be as much as 10 timings updates during GPU production period, all with minor adjustments

:D:D · 2025-07-04T01:14:57+0100

Samsung config 0
VBIOS 98.05.36.00.4D and 98.05.36.00.4C

Tried running just console in Fedora (no GUI) and with some quick resets, ie setting fault clock then waiting 0 to some ms and setting back to default (same program) I was able to get control back. Started your program in another console during fault frequency doesn't get to selection and running it before hand and then setting fault frequency sees it stopping with

Runtime error: ERROR_DEVICE_LOST while getting () in context wait_for_fences

More often than not in console mode the display background changes color rapidly rather than block type artifacts which is quite disturbing ie probably epileptic inducing.

Code:

Jul 03 19:36:27 fedora kernel: NVRM: _kgspLogXid119: ********************************* GSP Timeout **********************************
Jul 03 19:36:27 fedora kernel: NVRM: _kgspLogXid119: Note: Please also check logs above.
Jul 03 19:36:27 fedora kernel: NVRM: GPU at PCI:0000:03:00: GPU-be9b4836-5a63-a9ef-5b03-721c54957016
Jul 03 19:36:27 fedora kernel: NVRM: GPU Board Serial Number: 0
Jul 03 19:36:27 fedora kernel: NVRM: Xid (PCI:0000:03:00): 119, pid=3182, name=memtest_vulkan, Timeout after 6s of waiting for RPC response from GPU0 GSP! Expected function 76 (GSP_RM_CONTROL) (0x2080012b 0x230).
Jul 03 19:36:27 fedora kernel: NVRM: GPU0 GSP RPC buffer contains function 76 (GSP_RM_CONTROL) and data 0x000000002080012b 0x0000000000000230.
Jul 03 19:36:27 fedora kernel: NVRM: GPU0 RPC history (CPU -> GSP):
Jul 03 19:36:27 fedora kernel: NVRM:     entry function                   data0              data1              ts_start           ts_end             duration actively_polling
Jul 03 19:36:27 fedora kernel: NVRM:      0    76   GSP_RM_CONTROL        0x000000002080012b 0x0000000000000230 0x000639059ff19625 0x0000000000000000          y
Jul 03 19:36:27 fedora kernel: NVRM:     -1    103  GSP_RM_ALLOC          0x0000000000009072 0x000000000000000c 0x000639059ff193a8 0x000639059ff19516    366us
Jul 03 19:36:27 fedora kernel: NVRM:     -2    76   GSP_RM_CONTROL        0x0000000020800a5d 0x0000000000000008 0x000639059ff192d6 0x000639059ff193a2    204us
Jul 03 19:36:27 fedora kernel: NVRM:     -3    103  GSP_RM_ALLOC          0x0000000000009072 0x000000000000000c 0x000639059ff19176 0x000639059ff192c8    338us
Jul 03 19:36:27 fedora kernel: NVRM:     -4    76   GSP_RM_CONTROL        0x0000000020800a5d 0x0000000000000008 0x000639059ff19090 0x000639059ff19170    224us
Jul 03 19:36:27 fedora kernel: NVRM:     -5    103  GSP_RM_ALLOC          0x0000000000009072 0x000000000000000c 0x000639059ff18f28 0x000639059ff19081    345us
Jul 03 19:36:27 fedora kernel: NVRM:     -6    76   GSP_RM_CONTROL        0x0000000020800a5d 0x0000000000000008 0x000639059ff18e42 0x000639059ff18f24    226us
Jul 03 19:36:27 fedora kernel: NVRM:     -7    103  GSP_RM_ALLOC          0x0000000000009072 0x000000000000000c 0x000639059ff18c5f 0x000639059ff18e34    469us
Jul 03 19:36:27 fedora kernel: NVRM: GPU0 RPC event history (CPU <- GSP):
Jul 03 19:36:27 fedora kernel: NVRM:     entry function                   data0              data1              ts_start           ts_end             duration during_incomplete_rpc
Jul 03 19:36:27 fedora kernel: NVRM:      0    4099 POST_EVENT            0x00000000000000a2 0x0000000000000000 0x000639055f5df98a 0x000639055f5df9a8     30us
Jul 03 19:36:27 fedora kernel: NVRM:     -1    4099 POST_EVENT            0x00000000000000a2 0x0000000000000000 0x000639055f4eb18c 0x000639055f4eb199     13us
Jul 03 19:36:27 fedora kernel: NVRM:     -2    4099 POST_EVENT            0x00000000000000a2 0x0000000000000000 0x000639055f3f699e 0x000639055f3f69a9     11us
Jul 03 19:36:27 fedora kernel: NVRM:     -3    4099 POST_EVENT            0x00000000000000a2 0x0000000000000000 0x000639055f3021ab 0x000639055f3021be     19us
Jul 03 19:36:27 fedora kernel: NVRM:     -4    4099 POST_EVENT            0x00000000000000a2 0x0000000000000000 0x000639055f20d9cb 0x000639055f20d9d8     13us
Jul 03 19:36:27 fedora kernel: NVRM:     -5    4099 POST_EVENT            0x00000000000000a2 0x0000000000000000 0x000639055f1191e4 0x000639055f1191f1     13us
Jul 03 19:36:27 fedora kernel: NVRM:     -6    4099 POST_EVENT            0x00000000000000a2 0x0000000000000000 0x000639055f0249e6 0x000639055f0249f3     13us
Jul 03 19:36:27 fedora kernel: NVRM:     -7    4099 POST_EVENT            0x00000000000000a2 0x0000000000000000 0x000639055ef301e9 0x000639055ef301f7     14us
Jul 03 19:36:27 fedora kernel: CPU: 31 UID: 1000 PID: 3182 Comm: memtest_vulkan Tainted: G S         OE       6.15.3-200.fc42.x86_64 #1 PREEMPT(lazy)
Jul 03 19:36:27 fedora kernel: Tainted: [S]=CPU_OUT_OF_SPEC, [O]=OOT_MODULE, [E]=UNSIGNED_MODULE
Jul 03 19:36:27 fedora kernel: Hardware name: Xioaxi                 X99-Special           /X99 Taichi, BIOS P1.80 04/06/2018
Jul 03 19:36:27 fedora kernel: Call Trace:
Jul 03 19:36:27 fedora kernel:  <TASK>
Jul 03 19:36:27 fedora kernel:  dump_stack_lvl+0x5d/0x80
Jul 03 19:36:27 fedora kernel:  _kgspRpcRecvPoll+0x593/0x760 [nvidia]
Jul 03 19:36:27 fedora kernel:  _issueRpcAndWait+0xd2/0x900 [nvidia]
Jul 03 19:36:27 fedora kernel:  ? osGetCurrentThread+0x26/0x60 [nvidia]
Jul 03 19:36:27 fedora kernel:  rpcRmApiControl_GSP+0x76f/0x940 [nvidia]
Jul 03 19:36:27 fedora kernel:  ? _tlsThreadEntryGet+0x82/0x90 [nvidia]
Jul 03 19:36:27 fedora kernel:  ? osGetCurrentThread+0x26/0x60 [nvidia]
Jul 03 19:36:27 fedora kernel:  rmresControl_Prologue_IMPL+0xd4/0x1e0 [nvidia]
Jul 03 19:36:27 fedora kernel:  resControl_IMPL+0xd6/0x1b0 [nvidia]
Jul 03 19:36:27 fedora kernel:  ? _tlsEntryAcquire+0x29/0xd0 [nvidia]
Jul 03 19:36:27 fedora kernel:  serverControl+0x47e/0x590 [nvidia]
Jul 03 19:36:27 fedora kernel:  _rmapiRmControl+0x544/0x820 [nvidia]
Jul 03 19:36:27 fedora kernel:  rmapiControlWithSecInfo+0x79/0x140 [nvidia]
Jul 03 19:36:27 fedora kernel:  rmapiControl+0x24/0x40 [nvidia]
Jul 03 19:36:27 fedora kernel:  kgrobjPromoteContext_IMPL+0x2e8/0x350 [nvidia]
Jul 03 19:36:27 fedora kernel:  kgrobjConstruct_IMPL+0x27a/0x480 [nvidia]
Jul 03 19:36:27 fedora kernel:  __nvoc_objCreate_KernelGraphicsObject+0x132/0x240 [nvidia]
Jul 03 19:36:27 fedora kernel:  __nvoc_objCreateDynamic+0x4a/0x70 [nvidia]
Jul 03 19:36:27 fedora kernel:  ? _portMemAllocNonPagedUntracked+0x2c/0x40 [nvidia]
Jul 03 19:36:27 fedora kernel:  ? os_alloc_mem+0x104/0x120 [nvidia]
Jul 03 19:36:27 fedora kernel:  resservResourceFactory+0xc5/0x240 [nvidia]
Jul 03 19:36:27 fedora kernel:  ? _tlsEntryAcquire+0x93/0xd0 [nvidia]
Jul 03 19:36:27 fedora kernel:  _clientAllocResourceHelper+0x2aa/0x660 [nvidia]
Jul 03 19:36:27 fedora kernel:  ? _tlsThreadEntryGet+0x82/0x90 [nvidia]
Jul 03 19:36:27 fedora kernel:  ? tlsEntryGet+0x31/0x70 [nvidia]
Jul 03 19:36:27 fedora kernel:  serverAllocResourceUnderLock+0x33b/0xa10 [nvidia]
Jul 03 19:36:27 fedora kernel:  ? portSyncSpinlockAcquire+0x18/0x30 [nvidia]
Jul 03 19:36:27 fedora kernel:  ? portThreadGetCurrentThreadId+0x1d/0x30 [nvidia]
Jul 03 19:36:27 fedora kernel:  ? os_acquire_rwlock_write+0x2b/0x40 [nvidia]
Jul 03 19:36:27 fedora kernel:  ? portThreadGetCurrentThreadId+0x1d/0x30 [nvidia]
Jul 03 19:36:27 fedora kernel:  ? rmclientValidateLocks_IMPL+0x21/0x90 [nvidia]
Jul 03 19:36:27 fedora kernel:  ? _serverLockClientWithLockInfo.constprop.0+0x106/0x260 [nvidia]
Jul 03 19:36:27 fedora kernel:  serverAllocResource+0x2b4/0x5c0 [nvidia]
Jul 03 19:36:27 fedora kernel:  rmapiAllocWithSecInfo+0x1f0/0x420 [nvidia]
Jul 03 19:36:27 fedora kernel:  rmapiAllocWithSecInfoTls+0x65/0x90 [nvidia]
Jul 03 19:36:27 fedora kernel:  Nv04AllocWithAccessSecInfo+0x6f/0x80 [nvidia]
Jul 03 19:36:27 fedora kernel:  ? security_capable+0x50/0x150
Jul 03 19:36:27 fedora kernel:  RmIoctl+0xac3/0xda0 [nvidia]
Jul 03 19:36:27 fedora kernel:  ? os_acquire_spinlock+0x12/0x30 [nvidia]
Jul 03 19:36:27 fedora kernel:  ? portSyncSpinlockAcquire+0x18/0x30 [nvidia]
Jul 03 19:36:27 fedora kernel:  rm_ioctl+0x66/0x4f0 [nvidia]
Jul 03 19:36:27 fedora kernel:  nvidia_ioctl.isra.0+0x450/0x810 [nvidia]
Jul 03 19:36:27 fedora kernel:  nvidia_unlocked_ioctl+0x1d/0x30 [nvidia]
Jul 03 19:36:27 fedora kernel:  __x64_sys_ioctl+0x97/0xc0
Jul 03 19:36:27 fedora kernel:  do_syscall_64+0x7b/0x160
Jul 03 19:36:27 fedora kernel:  ? do_syscall_64+0x87/0x160
Jul 03 19:36:27 fedora kernel:  ? nvidia_unlocked_ioctl+0x1d/0x30 [nvidia]
Jul 03 19:36:27 fedora kernel:  ? __x64_sys_ioctl+0x97/0xc0
Jul 03 19:36:27 fedora kernel:  ? syscall_exit_to_user_mode+0x10/0x210
Jul 03 19:36:27 fedora kernel:  ? do_syscall_64+0x87/0x160
Jul 03 19:36:27 fedora kernel:  ? nvidia_unlocked_ioctl+0x1d/0x30 [nvidia]
Jul 03 19:36:27 fedora kernel:  ? __x64_sys_ioctl+0x97/0xc0
Jul 03 19:36:27 fedora kernel:  ? syscall_exit_to_user_mode+0x10/0x210
Jul 03 19:36:27 fedora kernel:  ? do_syscall_64+0x87/0x160
Jul 03 19:36:27 fedora kernel:  ? filp_flush+0x5b/0x80
Jul 03 19:36:27 fedora kernel:  ? syscall_exit_to_user_mode+0x10/0x210
Jul 03 19:36:27 fedora kernel:  ? do_syscall_64+0x87/0x160
Jul 03 19:36:27 fedora kernel:  ? syscall_exit_to_user_mode+0x10/0x210
Jul 03 19:36:27 fedora kernel:  ? do_syscall_64+0x87/0x160
Jul 03 19:36:27 fedora kernel:  ? exc_page_fault+0x7e/0x1a0
Jul 03 19:36:27 fedora kernel:  entry_SYSCALL_64_after_hwframe+0x76/0x7e
Jul 03 19:36:27 fedora kernel: RIP: 0033:0x7fc2ec30eaad
Jul 03 19:36:27 fedora kernel: Code: 04 25 28 00 00 00 48 89 45 c8 31 c0 48 8d 45 10 c7 45 b0 10 00 00 00 48 89 45 b8 48 8d 45 d0 48 89 45 c0 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 1a 48 8b 45 c8 64 48 2b 04 25 28 00 00 00
Jul 03 19:36:27 fedora kernel: RSP: 002b:00007ffed0b757f0 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
Jul 03 19:36:27 fedora kernel: RAX: ffffffffffffffda RBX: 0000000000000030 RCX: 00007fc2ec30eaad
Jul 03 19:36:27 fedora kernel: RDX: 00007ffed0b75950 RSI: 00000000c030462b RDI: 000000000000000b
Jul 03 19:36:27 fedora kernel: RBP: 00007ffed0b75840 R08: 00007ffed0b75950 R09: 00007ffed0b75978
Jul 03 19:36:27 fedora kernel: R10: 00007fc2d5b17b54 R11: 0000000000000246 R12: 000000000000000b
Jul 03 19:36:27 fedora kernel: R13: 00000000c030462b R14: 000000000000002b R15: 00007ffed0b75850
Jul 03 19:36:27 fedora kernel:  </TASK>
Jul 03 19:36:27 fedora kernel: NVRM: _kgspLogXid119: ********************************************************************************
Jul 03 19:36:27 fedora kernel: NVRM: _issueRpcAndWait: rpcRecvPoll timedout for fn 76!
Jul 03 19:36:27 fedora kernel: NVRM: nvCheckOkFailedNoLog: Check failed: Call timed out [NV_ERR_TIMEOUT] (0x00000065) returned from kgrobjPromoteContext(pGpu, pKernelGraphicsObject, pKernelGraphics) @ kernel_graphics_object.c:223
Jul 03 19:36:33 fedora kernel: NVRM: Xid (PCI:0000:03:00): 119, pid=3182, name=memtest_vulkan, Timeout after 6s of waiting for RPC response from GPU0 GSP! Expected function 103 (GSP_RM_ALLOC) (0xcab5 0x8).
Jul 03 19:36:33 fedora kernel: NVRM: _issueRpcAndWait: rpcRecvPoll timedout for fn 103!
Jul 03 19:36:33 fedora kernel: NVRM: rpcRmApiAlloc_GSP: GspRmAlloc failed: hClient=0xc1d0005e; hParent=0xbeef0100; hObject=0xbeefa0b5; hClass=0x0000cab5; paramsSize=0x00000008; paramsStatus=0x00000000; status=0x00000065
Jul 03 19:36:39 fedora kernel: NVRM: Xid (PCI:0000:03:00): 119, pid=3182, name=memtest_vulkan, Timeout after 6s of waiting for RPC response from GPU0 GSP! Expected function 103 (GSP_RM_ALLOC) (0xcab5 0x8).
Jul 03 19:36:39 fedora kernel: NVRM: nvAssertFailedNoLog: Assertion failed: Back to back GSP RPC timeout detected! GPU marked for reset @ kernel_gsp.c:2314
Jul 03 19:36:39 fedora kernel: NVRM: _issueRpcAndWait: rpcRecvPoll timedout for fn 103!
Jul 03 19:36:39 fedora kernel: NVRM: rpcRmApiAlloc_GSP: GspRmAlloc failed: hClient=0xc1d0005e; hParent=0xbeef0101; hObject=0xbeef8500; hClass=0x0000cab5; paramsSize=0x00000008; paramsStatus=0x00000000; status=0x00000065
Jul 03 19:36:45 fedora kernel: NVRM: Rate limiting GSP RPC error prints for GPU at PCI:0000:03:00 (printing 1 of every 30).  The GPU likely needs to be reset.
Jul 03 19:36:51 fedora kernel: NVRM: nvCheckOkFailedNoLog: Check failed: Call timed out [NV_ERR_TIMEOUT] (0x00000065) returned from pRmApi->Control(pRmApi, pGpu->hInternalClient, pGpu->hInternalSubdevice, NV2080_CTRL_CMD_INTERNAL_LOG_OOB_XID, &params, sizeof(params)) @ gpu.c:6468
Jul 03 19:36:51 fedora kernel: NVRM: Xid (PCI:0000:03:00): 154, GPU recovery action changed from 0x0 (None) to 0x1 (GPU Reset Required)
Jul 03 19:36:57 fedora kernel: NVRM: nvCheckOkFailedNoLog: Check failed: Call timed out [NV_ERR_TIMEOUT] (0x00000065) returned from kgrobjPromoteContext(pGpu, pKernelGraphicsObject, pKernelGraphics) @ kernel_graphics_object.c:223
Jul 03 19:37:09 fedora kernel: NVRM: nvAssertFailedNoLog: Assertion failed: (status == NV_OK) || (status == NV_ERR_GPU_IN_FULLCHIP_RESET) @ rs_client.c:844
Jul 03 19:37:09 fedora kernel: NVRM: nvAssertFailedNoLog: Assertion failed: (status == NV_OK) || (status == NV_ERR_GPU_IN_FULLCHIP_RESET) @ rs_server.c:259
Jul 03 19:37:09 fedora kernel: NVRM: nvAssertFailedNoLog: Assertion failed: (status == NV_OK) || (status == NV_ERR_GPU_IN_FULLCHIP_RESET) @ rs_server.c:1375
Jul 03 19:37:21 fedora kernel: NVRM: nvAssertFailedNoLog: Assertion failed: (status == NV_OK) || (status == NV_ERR_GPU_IN_FULLCHIP_RESET) @ mem.c:179
Jul 03 19:37:27 fedora kernel: NVRM: nvAssertFailedNoLog: Assertion failed: (status == NV_OK) || (status == NV_ERR_GPU_IN_FULLCHIP_RESET) @ vaspace_api.c:538
Jul 03 19:37:45 fedora kernel: NVRM: nvAssertFailedNoLog: Assertion failed: (status == NV_OK) || (status == NV_ERR_GPU_IN_FULLCHIP_RESET) @ mem.c:179
Jul 03 19:37:51 fedora kernel: NVRM: nvAssertFailedNoLog: Assertion failed: (status == NV_OK) || (status == NV_ERR_GPU_IN_FULLCHIP_RESET) @ vaspace_api.c:538

Can still type in the console but reset doesn't happen and shutdown command doesn't complete if given or I didn't wait long enough for timeouts..

Otherwise the card seems to work okay, even at max memory clock. Seems Palit prefer to push for distributors handling problems which would probably mean giving the distributor the card and waiting 3 weeks for the same card or replacement.

PS your program seems familiar, cant help thinking we may have met on Overclock.net in the past.

System Name	Bragging Rights
Processor	Atom Z3735F 1.33GHz
Motherboard	It has no markings but it's green
Cooling	No, it's a 2.2W processor
Memory	2GB DDR3L-1333
Video Card(s)	Gen7 Intel HD (4EU @ 311MHz)
Storage	32GB eMMC and 128GB Sandisk Extreme U3
Display(s)	10" IPS 1280x800 60Hz
Case	Veddha T2
Audio Device(s)	Apparently, yes
Power Supply	Samsung 18W 5V fast-charger
Mouse	MX Anywhere 2
Keyboard	Logitech MX Keys (not Cherry MX at all)
VR HMD	Samsung Oddyssey, not that I'd plug it into this though....
Software	W10 21H1, barely
Benchmark Scores	I once clocked a Celeron-300A to 564MHz on an Abit BE6 and it scored over 9000.

RTX 5070 discussion

:D:D

StViolenceDay

Chrispy_

:D:D

StViolenceDay

:D:D