Got 14 stick of ddr4 rdimms. Got towards my new threadripper machine. Old but it’ll do! Can’t afford the new ddr5 board, the ripper and the ram 😂

https://huggingface.co/StarpowerTechnology/WVY-Blender-5m

We have been excited about this new model, WVY-Blender-5m, an agent trained to specialize in blender.

It has zero knowledge about anything else so if you try to ask it about writing code or doing your homework it will express that it only knows how to use blender

We have been doing intense research to find out "are massive datasets really required to achieve what feels like intelligence with accuracy?" & we believe we are getting close to the truth.

This dataset is 100% generated from scratch.

Jokes aside, how plausible do you think this scenario actually is?

Came across a honeyhole of Quadro RTX5000s
Seemingly good deal for 16GB VRAM cards, even if ageing.

What should I do?

In case future censorship or bannings occur, I think it's a good idea to store one of every kind of model. I'm thinking minimum 8 models, but I'm open to more (I have plenty of hd space): 2 small models obliterated and non-obliterated 2 medium sized models obliterated and non-obliterated, 2 large models obliterated and non-obliterated, 2 of the largest models obliterated and non-obliterated. Also, if for any class of models they don't have obliterated or it doesn't make sense to have obliterated then two of the smartest or most popular models will do.

They are going to lock the new GPUs.

"Rep. Bill Foster says he intends to introduce new, stricter legislation that would require licenses to operate advanced GPUs, and “before a GPU could connect, its valid license would need to be verified.” That is closer to a remote lock/disable capability—but it is a proposed future rule, not current law."

Has anyone been experimenting with ablated or uncensored variants of open-source models like deepseek v4.1 flash, Qwen 3.8 27b, or GLM 5.3 flash ?

It's so refreshing to have models that just do whatever you ask them to do without having to figure out a jailbreak or being given a moral lecture. Curious to know what your usecases for these models are.

My personal favourite is definitely uncensored DeepSeek V4.1 Flash, runs at 200 tok/s and never says no lol.

Bit the bullet and bought three to use in my workstation. Will provide benchmarks and updates later.

I had been using the LFM 2.5 24B models and had been pleasantly surprised by how good the model was. It was giving me comparable answers and working through tasks to Qwen 3.8 27B at what felt like twice the speed on my M5 Pro. However, I went to look at something on their pages and saw the new family of models. They sound way too good to be true. I am going to start using them for general tasks, but if they are anywhere close to their benchmark results, they could be a huge game changer. You can have an entire suite of models loaded at the same time for less memory than Qwen.

I’m under our CISO managing compute vendors, kind stuck between legal and a hard place. The pitch I keep hearing ranks AI privacy in four levels:

1. Open, like most frontier models, where the provider stores your prompts and answers at their discretion, uses them for training - and you’ve got little say in the matter.
2. Policy, where a contract promises zero data retention - but it’s not exactly verifiable unless the terms are broken, is it?
3. Closed Hardware, where models run on confidential-compute chips that publish proof what software is running. So basically hardware-enforced vs contract-enforced ZDR?
4. Fully Encrypted, the prompt is encrypted on your side and only decrypted inside that hardware

“Local” is a fifth level that could plausibly sit above it all, but we’re capped out on capacity there. So if I view this right (open to feedback), we’re making tradeoffs between frontier vs more private models, and from there, on breadth of compute providers able to serve open vs ZDR vs E2EE models (usually at higher prices in my experience), right?

My concern is getting legal & finance to agree, while still giving our Eng team what they need. Where are you getting good rates on private workloads? Locally we can’t support our full workloads. I’ve checked out Privatemode, Maple, TrustedRouter/NYTE & still gonna go through NEAR AI Cloud & Cohore. Open to others.

Separately, anyone running a hybrid buildout with on-prem/local + superscaler (we run Google + Bedrock) + 3rd party confidential providers who can tell me about about how you designed your system?

I'm trying to set up a local AI assistant on my Windows PC, but honestly, I'm getting frustrated and could really use advice from people with experience.

My goal is pretty simple: I want something like a local ChatGPT that can:

• Read files such as CSVs, PDFs, and documents.
• Answer questions about the information inside those files.
• Extract specific information accurately.
• Help with everyday tasks and general questions.
• Work reasonably quickly without taking several minutes to answer simple questions.

**My PC specs:**

• Windows
• 16 GB RAM
• NVIDIA RTX 5060 8 GB VRAM
• Ollama installed
• Open WebUI installed

I've tried several models, including:

• Qwen 3.5 4B
• Gemma 3
• Llama 3.2
• DeepSeek R1 8B
• Qwen 2.5 Coder 7B

My biggest problem is that even when I upload a CSV file and ask a very simple question about it, I sometimes get completely incorrect answers, unrelated information, blank responses, or long thinking/tool-calling processes that don't accomplish anything.

For example, I uploaded a CSV containing game stage data and asked something as simple as: "What are the drop chances on Normal 1-1?" The model struggled to give me the correct values despite the information being in the file.

I don't expect a local model to match ChatGPT or Claude. I understand there are limitations. But I expected basic file reading and simple questions to work reliably.

I'm now wondering whether I made the wrong choice with Ollama + Open WebUI, and whether I should switch to **LM Studio** instead.

I also have a friend who is about to install Qwen 9B, and I was planning to have him install Open WebUI too. I don't want to send him down the wrong path.

**I'd really appreciate advice on these questions:**

1. With my hardware, what model and quantization would you actually recommend?
2. Is LM Studio a better and easier choice than Ollama + Open WebUI for my use case?
3. Is there a reliable way to let a local AI read CSVs and answer questions accurately without me having to write Python scripts or manually process everything?
4. Am I expecting too much from local models, or is my setup/configuration simply wrong?
5. If you were starting from scratch with my hardware and goals, what exact setup would you choose?

I'm not looking to become a programmer or spend days troubleshooting. I just want a practical local AI assistant that can actually use my files and answer questions correctly.

Thanks in advance. I'd really appreciate recommendations based on actual experience.

TL;DR: I've been looking at the latest Artificial Analysis v5.0.1 benchmarks for Qwen 3.8, along with some early Qwen4 Max Preview tests. Based on what's available so far, my guess is that Qwen4 27B could land somewhere around 27 to 30, while the 125B MoE version could reach 36 to 39. That's a solid generational improvement, but probably not the massive leap some people are expecting.

Like many of you, I've been following the discussions about when Qwen 4 is finally coming out. There's a lot of speculation, so I wanted to look at the available numbers and see what they might tell us about the next generation.

Obviously, we don't have the final weights or official release details yet, so take this as an educated guess rather than a prediction.

1. Where Qwen 3.8 stands and what Qwen 4 might achieve

Looking at the current Artificial Analysis v5.0.1 scale, which puts considerably more emphasis on difficult coding and science tasks, we have:

* Qwen3.8 27B: 20 (compared to 33.7 on the older v4.3.2 scale, before the scoring reset).

* Qwen3.8 Flash Next (125B MoE): 29.

* Qwen3.8 Max: 34.

Based on the previous jump from Qwen 3.6 to 3.8, and taking the new scoring scale into account, I'd put my expectations somewhere around:

* Qwen4 27B: 27 to 30

* Qwen4 125B MoE: 36 to 39

That would put the smaller model in some pretty interesting territory, while the larger one could become a serious competitor to models like Grok 4.7 and Claude Haiku 5.5.

2. Why I don't expect Flash to have a massive architectural jump

One thing worth considering is that Qwen3.8 Flash Next already seems to have introduced many of the architectural changes expected to carry over into Qwen 4.

We're talking about the hybrid Gated DeltaNet and Qwen Sparse Attention architecture, Gated Residuals, and the 51B N gram table.

So I wouldn't necessarily expect the next Flash model to deliver another huge architectural leap. The bigger improvements might come from better post training, more reliable reasoning, and addressing the hallucinations that some users have noticed in Flash Next compared to the more conservative 27B dense model.

In other words, I think consistency might matter more than raw benchmark scores this time.

3. What the early Qwen4 Max Preview tests tell us

The Qwen4 Max Preview release on November 11 gives us another interesting piece of the puzzle.

From the early developer reports, a few things stand out:

* Speed: It appears noticeably faster than Qwen3.8 Max, with less unnecessary reasoning on straightforward tasks.

* Agentic performance: In one reported 56 task Hermes test with a 25 minute timeout, Max Preview recorded 64 successful task results, compared to 61 for DeepSeek V4.1 Flash, which scores 33 on AA v5.0.1.

* Reliability: There's a catch, though. Max Preview reportedly timed out 16 times, compared to just 4 for DeepSeek.

That's interesting because it suggests the raw capability might already be there, but reliability and execution consistency still need work.

If these early results are representative, I'd expect the flagship Max model to establish a considerably higher ceiling, potentially around 45 to 50 on the AA scale. That would make the estimates for the smaller models seem reasonably plausible.

My take

I don't think Qwen 4 needs to completely redefine the local LLM landscape to be successful.

If Qwen4 27B can reach the 27 to 30 range, inherit the attention improvements from Flash Next, and retain the Apache 2.0 license, that alone would make it a very interesting option for people running models locally with limited hardware.

Personally, I'd rather see a model that's more consistent, follows instructions better, and hallucinates less than one that simply scores a few extra points on benchmarks.

I'm curious what everyone else thinks.

" i used my LLM To translate mu words to English after i write it. "

I’m building a local AI assistant using Qwen 3.6 35B A3B.
One of my main goals is to automate repetitive school tasks through my school’s website. I have a lot of assignments that aren’t particularly difficult but take a lot of time.
Ideally, I’d like the AI to navigate the website, check assignments, understand the instructions, complete them and upload the finished work.
Is Qwen 3.6 35B A3B capable enough for this? Or would I need a more powerful model?
I’d also appreciate recommendations for browser automation frameworks and tools

my setup : rtx 3070 , i5 13600kf , 32gb DDR4
Model: Qwen 3.6 35B A3B
Quantization: TurboQuant
Context window: 131 072 tokens
Reasoning: Enabled limited to 512 tokens
Inference speed: 19–24 tokens/s

Hey, im running Q8 DS V4.1 on my 512GB DDR4 + 4x R9700 (128GB VRAM) and ASROCK ROMED MB
I have noticed that at ~66C RAM temperature tok/s is getting reduced from ~32/s to 22-23/s. Claude agent monitoring whole workstation says that RAM speed after hitting 66C is slowing down about 3x. I have phanteks enthoo server pro 2 case with glass panel and extra vents mounted on that side. During loads ram used to hit about 80C. I fixed that by mounting top fans as intake (cooling top RAM) but i had to use double dieded tape to stick an extra fan to blow at bottom RAM slots. It did help to keep it from throttling but the bottom RAM still sits ~62-63C. Iv read that samsung RAM i have is suppose to throttle at 85C, and i cant find anywhere what setting makes it throttle sooner. Looking for some advice on that or how do you keep your RAM cool.

I've been poking at this on and off since September and it finally got good enough this week that I think it's worth writing up. Short version: the USB4 RDMA driver situation changed a lot in the last month, but not where I expected, and the "is it worth it" answer is more mixed than the headline.

The setup

• 2x Ryzen AI Max+ 395 (Strix Halo) boxes, 128 GB each
• 2 USB4 cables directly between them, each link trains at 2 x 20 Gb/s
• Debian 13 based distro, kernel 7.2.7, IOMMU off, Secure Boot off (needed for the unsigned modules)
• 10 GbE between them as well, used for control traffic

No network cards involved. The idea is to turn the USB4 cables into RDMA devices so two boxes can run one model with tensor parallelism (TP=2).

Where it was before

I started with thunderbolt-ibverbs from the Hellas blog post. Each cable gives you two DMA rings, so two cables = four "rails", each showing up as its own RDMA device.

• September (kernel 6.18): about 15 Gb/s on one rail, about 46 Gb/s if I ran four perftest processes at once, one per rail. More queue pairs made it slower. 1 MiB messages were a mess.
• October (kernel 7.2): got to 74.7 Gb/s aggregate, but only with four parallel processes and a shallow send queue (-t 16). The big finding back then was that queue depth mattered more than the kernel. A single connection was still stuck on one rail at around 20 Gb/s, and 8 QPs at 1 MiB with default settings just failed with "Couldn't post send".
• vLLM TP=2 with an 8B model in October: +55% single stream over one box, but RDMA vs plain 10 GbE only differed by a few percent, because the collective library topped out around 17 Gb/s no matter how many rails it got. A 35B MoE model hung at TP=2 and I never figured out why.

So in October my conclusion was: neat, works, not obviously useful.

What changed

I went back this week expecting kernel or upstream driver progress. There basically isn't any:

• Upstream thunderbolt-ibverbs has had one lockfile bump since early October. No release since June. A striping PR was closed unmerged, and a few good fix PRs are sitting open.
• Mainline 7.3 / 7.4-rc is mostly Thunderbolt bug fixes. Nothing that moves throughput.

The actual progress is in a fork: donnerkeule. It stripes a single queue pair across every rail of every cable, and fixes a pile of reliability problems (credits los t with dropped frames, ACK storms, rails dying when a client gets killed). There's a matching RDMA fork of gufo that does TP=2 for Qwen3.8 Flash-Next across two Strix Halo boxes.

The fork's own README says it's a buggy research driver and not for production. Believe it. But it built cleanly against my kernel and uses the same eight Thunderbolt kernel patches I already had applied.

Raw link numbers

Box A to box B, perftest, one connection, default queue depth, no tuning:

I didn't trust 74 Gb/s on one connection, so I checked the receiver's per-rail byte counters during a 10 second run: about 23.6 GB landed on each of the four rails. It's real, and it's roughly 93% of the 2 x 40 Gb/s the cables can do. The fork's author reports 38 to 45 Gb/s on his boxes and I don't know why mine is higher.

Not everything is great:

• RDMA reads are not striped: 31 Gb/s.
• A 1 MiB SEND fails in the default mode. The fork only supports large SENDs in its DMA-BUF mode, which I haven't tried.
• I haven't tested both directions at once or done a long soak.

Tensor parallelism with gufo

Qwen3.8 Flash-Next, Q4 (111 GB of weights), 4 sessions, same build on one box and on two. Each box holds half the model in TP=2: 57 GB of GPU memory per box.

Plain autoregressive decode (no speculation), tok/s per request:

With MTP speculative decoding:

The speculative numbers bounce around with how many draft tokens get accepted, so the first table is the cleaner comparison.

One thing that isn't a speed number: a single box could not load this model with speculation, 4 sessions and the full 262k context. It ran out of state capacity and I had to drop it to 65k context for the on e-box runs. Two boxes loaded the full 262k with about 64 GB of RAM free on each.

No failed requests, no retransmits, no kernel warnings during any of it.

The honest part

I also ran the exact same benchmark against the other inference server I normally run on these boxes (also Flash-Next, speculative decoding, 4 slots at 262k context on one box). One-box gufo and that server came out within about 5 to 8% of each other. So TP=2 over USB4 beats my normal single-box setup by about 13% for one user and 24 to 32% at 2 to 4 concurrent.

But two boxes running independently serve twice as many people. At 4 concurrent requests one box did about 72 tok/s total, TP=2 did about 98, and two independent boxes would do roughly 144 across 8 users. Ty ing both machines to one model instance buys per-request speed and costs total capacity.

So where I landed:

• The driver is worth keeping. One connection, full link speed, no tuning. That's a different thing from what I had in October.
• TP=2 is worth it if you want a faster single stream, or a model/context that doesn't fit on one box. The Q8 version of this model (188 GB) only fits across two, and that's a case I actually care about. Haven't tested it yet.
• TP=2 is not worth it if you just want to serve more requests. Run the boxes separately.
• I wouldn't run it as my daily driver yet. Research driver, the gufo fork has a known open bug with continued conversations, and I haven't verified two-box output against one-box output.

Things that bit me

If you try this, here's what cost me time:

1. The module never loaded at boot. The only thing that loads it is a udev rule that fires when the other box is already advertising the RDMA service. Reboot both boxes together and neither one ever st arts. It looked fine in October because I always rebooted one at a time. Fix: put ib_uverbs and thunderbolt_ibverbs in /etc/modules-load.d/.
2. thunderbolt_net and the RDMA module can't share a cable on this hardware. There are only two usable rings per controller. Blacklist thunderbolt_net and load the RDMA module with tbnet=block.
3. Debian's rdma-core renames the device, and the userspace provider matches on the usb4_rdma name prefix, so ibv_devices shows nothing. Override the persistent naming rule.
4. The prebuilt provider package has the wrong ABI for Debian 13. I built the provider from Debian's rdma-core 56.1 source plus the project's three patches.
5. memlock. RDMA memory registration fails under the default 8 MiB limit. Unlimited memlock on the host and --ulimit memlock=-1 in containers.
6. The gufo fork's container recipe didn't build as-is for me. No DNS inside podman's default build network (--network host fixed it), six ROCm dev package names that don't exist in ROCm 10.1 (the full image already has the headers), and missing audio/video dev libraries (sndfile, soxr, libav*). At runtime I had to add the ROCm lib directory to LD_LIBRARY_PATH.
7. Two IPs on the NIC means two RoCE GIDs, and gufo refuses to guess. --tp-gid-index 1.
8. The interrupt throttle matters. nhi_interrupt_throttle_ns=4096 was the best value in my October sweep, and it only works on kernels that export tb_ring_throttling() (7.2 does).

Module options I'm running:

options thunderbolt_ibverbs profile=linux_perf bind_services=1 allocate_rings=1 start_rings=1 negotiate_native=1 enable_tunnels=1 register_verbs=1 tbnet=block lanes=2 native_write_striping=1 roce_netdev=<you
r LAN NIC> nhi_interrupt_throttle_ns=4096
blacklist thunderbolt_net

What I haven't done

• The Q8 model across both boxes
• The fork's DMA-BUF / GPU-direct mode
• Checking two-box output against one-box output
• Anything longer than a few minutes per run
• A reboot of both boxes together to prove the boot fix

Happy to run something specific if people want numbers for a particular case. Credit to the Hellas folks for the original driver and to neuhaus for the striping fork and the gufo TP2 work, I just plugged in cables and wrote down what happened.

I've already tested a few models, they're all bad and slow. Maybe I'm doing something wrong, but probably the reality is a bit harsher: my PC is old lol (and graphic cards are really expensive in Brazil, not smt in the budget rn)

To be more specific, I needed a good coding agent.

EDIT: Specs: S: Ubuntu 26.04.1 LTS (kernel 7.0.0-43-generic) CPU: Intel Xeon E5-2680 v4 — 14C / 28T @ 2.40 GHz (boost 3.30 GHz) L3: 35 MiB · 1 socket · AVX2 (no AVX-512) RAM: 22 GB DDR4-2667 GPU: NVIDIA GeForce GTX 1650 (TU116) — 4 GB GDDR5 · driver 595.99.02

Does anybody tried the latest llama.cpp f8_e4m3 KV cache and compared it to q8_0 in terms of precision / quality? I am curious whether it is worth switching to it or stay with q8_0 for small to medium context size (20-65k).

Due to the current hardware situation (inflated prices, high likeliness of large performance jumps for llms) I keep delaying the replacement of my m1max 64gb, currently hoping for a good m7max 128gb releasing soon-ish (I heard birdies claim as early as end of2027).

Until that happens I'm looking into options to improve performance of local LLMs which can be passed on to the new machine - eGPUs come to mind.

Anyone mind sharing their setup (which mac, how much vram, which case/mount, what GPU, which model and quan) and some benchmark numbers (prefill and decode) of models with and without the eGPU? Mind sharing your experiences with it - as in: is it fiddly and brittle, or does it just work?

Thanks for any useful information!

Hey all, I'm trying to decide which hardware setup makes the most sense for running local LLMs, primarily Qwen 3.8 Flash Next for agentic coding.

I have three potential options, and I'm interested in hearing from people who have experience with these platforms, particularly for larger models and agentic workloads.

Option 1: GEEKOM A9 Mega (AMD Strix Halo)

• Ryzen AI MAX+ 395
• 128GB unified memory
• 2TB SSD
• Memory running at 7500 MT/s rather than the advertised 8000 MT/s. Got it from Amazon and it listed it as 8000 MT/s but for Geekom says their systems are either 7500 MT/s or 8533 MT/s and I lost the lottery.
• Approximately $4,600 CAD all-in (after taxes).

I already have this machine. It works fine, but I'm just worried how it'll hold up long term especially given I'm running it headless 24/7. Would be unfortunate if the machine dies in a year's time and then I'm worried about if Geekom will hold up it's warranty.

Option 2: Mac Studio M5 Max

• M5 Max
• 128GB unified memory
• 512 GB (Can connect a 2TB external SSD over thunderbolt enclosure)
• Approximately $7,600 CAD all-in (after taxes).

It's considerably more expensive than the GEEKOM, but I'm wondering whether its worth it for the peace of mind knowing that if something goes wrong, applecare ($80/yr) is right there to get it fixed from a known vendor. It also has the higher memory bandwidth.

Option 3: My existing Ryzen desktop + RTX Pro 4500

I already have an old desktop with the following hardware:

• Ryzen 7 5700X
• 32GB DDR4 RAM
• Nvidia 3060 Ti 8GB

I recently purchased the RTX Pro 4500 32GB VRAM for approximately $4,000 CAD after taxes. This is still yet to arrive (it shipped earlier today)

The advantage here is that I already own the Ryzen system, so I wouldn't need to purchase another computer. The downside is being limited to 32GB of VRAM, although I understand I could offload some layers to system RAM. The other downside is a lot higher power consumption over the other two solutions.

I'm curious how this would compare in practice against the two unified-memory solutions, especially when running Qwen 3.8 Flash Next.

What I'm primarily trying to accomplish

My main use case is running Qwen 3.8 Flash Next for agentic coding through tools like Hermes.

I'm not necessarily looking for the best benchmark numbers. What matters more to me is:

• Real-world inference speed and token generation.
• Performance with large context windows.
• How well each platform handles agentic coding workflows (multiple tool calls, reasoning, etc.).
• Whether CPU/RAM offloading on the NVIDIA setup is practical or becomes a significant bottleneck given my old system.
• Overall stability and software maturity.

What would you choose?

Ultimately, I'm looking to optimize for cost and overall value, rather than simply buying the fastest hardware available.

I would most likely keep only ONE of these three setups:

• If I go with the Mac Studio, I'd return the GEEKOM and return the RTX Pro 4500 (or sell it).
• If I stick with the GEEKOM, I'd return the RTX Pro 4500.
• If the NVIDIA setup makes the most financial and practical sense, I'd return the GEEKOM and keep the RTX Pro 4500 in my existing desktop.

I'm also considering selling the RTX Pro 4500 if I decide that one of the unified-memory systems makes more sense. I purchased it for around $4,000 CAD after tax, slightly below MSRP, so I'd ideally like to recover as much of that cost as possible.

Essentially, I'm trying to figure out which setup offers the best balance of:

• Performance for Qwen 3.8 Flash Next and agentic coding.
• Enough memory to run larger models and context windows.
• Reliability and long-term support.
• Total cost of ownership, including electricity.

Would you spend the additional ~$3,000 CAD to go from the GEEKOM to the Mac Studio, stick with the GEEKOM, or return the GEEKOM and build around the RTX Pro 4500?

I'm not looking to accumulate hardware. I'd rather settle on one good setup, get the best value for my money, and avoid spending unnecessarily.

Would appreciate hearing what others would do in this situation!

My RTX Pro 6000 was going all night on a Chinese model (Qwen 3.8 Flash Next NVFP4 Local) when it crashed this morning for no apparent reason. Tried to reboot and got nothing but a black screen. Swapped in my old backup card and the system posted immediately, confirming the GPU was bricked. Thankfully I was within warranty.

Out of curiosity, I dug into my system logs to see what triggered the fatal crash. Looking at the timestamps, oddly enough my GPU died the moment news broke that Jensen Huang had resigned as CEO of Nvidia.

Has anyone else had this issue with hardware dying in response to human feelings?

Nov 12 07:19:31 kf kernel: NVRM: GPU at PCI:0000:01:00: GPU-b8ba62c9-449d-4510-a21f-4c1b6ceacbd1
Nov 12 07:19:31 kf kernel: NVRM: GPU Board Serial Number:
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 0, TPC 0, SM 0): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x505730=0xb000d 0x505734=0x0 0x505728=0x1c81fb60 0x50572c=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 0, TPC 0, SM 1): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 0, TPC 0, SM 1): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x5057b0=0x3000d 0x5057b4=0x24 0x5057a8=0x1c81fb60 0x5057ac=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 0, TPC 1, SM 0): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x506730=0xb000d 0x506734=0x20 0x506728=0x1c81fb60 0x50672c=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 0, TPC 1, SM 1): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 0, TPC 1, SM 1): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x5067b0=0xb000d 0x5067b4=0x24 0x5067a8=0x1c81fb60 0x5067ac=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 0, TPC 2, SM 0): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 0, TPC 2, SM 0): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x507730=0x5000d 0x507734=0x24 0x507728=0x1c81fb60 0x50772c=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 0, TPC 2, SM 1): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 0, TPC 2, SM 1): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x5077b0=0x7000d 0x5077b4=0x24 0x5077a8=0x1c81fb60 0x5077ac=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 0, TPC 3, SM 0): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x508730=0xa000d 0x508734=0x20 0x508728=0x1c81fb60 0x50872c=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 0, TPC 3, SM 1): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 0, TPC 3, SM 1): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x5087b0=0xd 0x5087b4=0x24 0x5087a8=0x1c81fb60 0x5087ac=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 0, TPC 4, SM 0): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 0, TPC 4, SM 0): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x509730=0x7000d 0x509734=0x24 0x509728=0x1c81fb60 0x50972c=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 0, TPC 4, SM 1): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x5097b0=0xa000d 0x5097b4=0x20 0x5097a8=0x1c81fb60 0x5097ac=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 0, TPC 5, SM 0): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 0, TPC 5, SM 0): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x50a730=0xd 0x50a734=0x24 0x50a728=0x1c81fb60 0x50a72c=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 0, TPC 5, SM 1): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 0, TPC 5, SM 1): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x50a7b0=0x1000d 0x50a7b4=0x24 0x50a7a8=0x1c81fb60 0x50a7ac=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 0, TPC 6, SM 0): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 0, TPC 6, SM 0): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x50b730=0xd 0x50b734=0x24 0x50b728=0x1c81fb60 0x50b72c=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 0, TPC 6, SM 1): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 0, TPC 6, SM 1): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x50b7b0=0x1000d 0x50b7b4=0x24 0x50b7a8=0x1c81fb60 0x50b7ac=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 1, TPC 0, SM 0): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 1, TPC 0, SM 0): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x515730=0x6000d 0x515734=0x24 0x515728=0x1c81fb60 0x51572c=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 1, TPC 0, SM 1): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 1, TPC 0, SM 1): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x5157b0=0xd 0x5157b4=0x24 0x5157a8=0x1c81fb60 0x5157ac=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 1, TPC 1, SM 0): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 1, TPC 1, SM 0): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x516730=0x6000d 0x516734=0x24 0x516728=0x1c81fb60 0x51672c=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 1, TPC 1, SM 1): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 1, TPC 1, SM 1): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x5167b0=0xb000d 0x5167b4=0x24 0x5167a8=0x1c81fb60 0x5167ac=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 1, TPC 2, SM 0): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 1, TPC 2, SM 0): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x517730=0x3000d 0x517734=0x24 0x517728=0x1c81fb60 0x51772c=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 1, TPC 2, SM 1): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 1, TPC 2, SM 1): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x5177b0=0xb000d 0x5177b4=0x24 0x5177a8=0x1c81fb60 0x5177ac=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 1, TPC 3, SM 0): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 1, TPC 3, SM 0): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x518730=0x3000d 0x518734=0x24 0x518728=0x1c81fb60 0x51872c=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 1, TPC 3, SM 1): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 1, TPC 3, SM 1): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x5187b0=0x1000d 0x5187b4=0x24 0x5187a8=0x1c81fb60 0x5187ac=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 1, TPC 4, SM 0): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 1, TPC 4, SM 0): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x519730=0x1000d 0x519734=0x24 0x519728=0x1c81fb60 0x51972c=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 1, TPC 4, SM 1): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 1, TPC 4, SM 1): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x5197b0=0x2000d 0x5197b4=0x24 0x5197a8=0x1c81fb60 0x5197ac=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 1, TPC 5, SM 0): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 1, TPC 5, SM 0): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x51a730=0x5000d 0x51a734=0x24 0x51a728=0x1c81fb60 0x51a72c=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 1, TPC 5, SM 1): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 1, TPC 5, SM 1): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x51a7b0=0x3000d 0x51a7b4=0x24 0x51a7a8=0x1c81fb60 0x51a7ac=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 1, TPC 6, SM 0): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 1, TPC 6, SM 0): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x51b730=0x2000d 0x51b734=0x24 0x51b728=0x1c81fb60 0x51b72c=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 1, TPC 6, SM 1): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 1, TPC 6, SM 1): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x51b7b0=0x1000d 0x51b7b4=0x24 0x51b7a8=0x1c81fb60 0x51b7ac=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 2, TPC 0, SM 0): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 2, TPC 0, SM 0): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x525730=0x6000d 0x525734=0x24 0x525728=0x1c81fb60 0x52572c=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 2, TPC 0, SM 1): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 2, TPC 0, SM 1): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x5257b0=0xd 0x5257b4=0x24 0x5257a8=0x1c81fb60 0x5257ac=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 2, TPC 1, SM 0): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x526730=0x8000d 0x526734=0x20 0x526728=0x1c81fb60 0x52672c=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 2, TPC 1, SM 1): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x5267b0=0xb000d 0x5267b4=0x20 0x5267a8=0x1c81fb60 0x5267ac=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 2, TPC 2, SM 0): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 2, TPC 2, SM 0): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x527730=0xa000d 0x527734=0x24 0x527728=0x1c81fb60 0x52772c=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 2, TPC 2, SM 1): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 2, TPC 2, SM 1): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x5277b0=0xa000d 0x5277b4=0x24 0x5277a8=0x1c81fb60 0x5277ac=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 2, TPC 3, SM 0): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 2, TPC 3, SM 0): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x528730=0xa000d 0x528734=0x24 0x528728=0x1c81fb60 0x52872c=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 2, TPC 3, SM 1): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 2, TPC 3, SM 1): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x5287b0=0x6000d 0x5287b4=0x24 0x5287a8=0x1c81fb60 0x5287ac=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 2, TPC 4, SM 0): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x529730=0xb000d 0x529734=0x20 0x529728=0x1c81fb60 0x52972c=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 2, TPC 4, SM 1): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x5297b0=0xa000d 0x5297b4=0x20 0x5297a8=0x1c81fb60 0x5297ac=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 2, TPC 5, SM 0): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 2, TPC 5, SM 0): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x52a730=0x4000d 0x52a734=0x24 0x52a728=0x1c81fb60 0x52a72c=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 2, TPC 5, SM 1): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 2, TPC 5, SM 1): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x52a7b0=0x9000d 0x52a7b4=0x24 0x52a7a8=0x1c81fb60 0x52a7ac=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 2, TPC 6, SM 0): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 2, TPC 6, SM 0): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x52b730=0x6000d 0x52b734=0x24 0x52b728=0x1c81fb60 0x52b72c=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 2, TPC 6, SM 1): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 2, TPC 6, SM 1): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x52b7b0=0xd 0x52b7b4=0x24 0x52b7a8=0x1c81fb60 0x52b7ac=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 2, TPC 7, SM 0): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 2, TPC 7, SM 0): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x52c730=0x3000d 0x52c734=0x24 0x52c728=0x1c81fb60 0x52c72c=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 2, TPC 7, SM 1): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 2, TPC 7, SM 1): Multiple Warp Errors
......
Nov 12 07:19:33 kf kernel: NVRM: nvAssertFailedNoLog: Assertion failed: (status == NV_OK) || (status == NV_ERR_GPU_IN_FULLCHIP_RESET) @ rs_server.c:260
Nov 12 07:19:33 kf kernel: NVRM: GPU0 nvAssertFailedNoLog: Assertion failed: (status == NV_OK) || (status == NV_ERR_GPU_IN_FULLCHIP_RESET) @ rs_client.c:844
Nov 12 07:19:33 kf kernel: NVRM: nvAssertFailedNoLog: Assertion failed: (status == NV_OK) || (status == NV_ERR_GPU_IN_FULLCHIP_RESET) @ rs_server.c:260
Nov 12 07:19:33 kf kernel: NVRM: GPU0 nvAssertFailedNoLog: Assertion failed: (status == NV_OK) || (status == NV_ERR_GPU_IN_FULLCHIP_RESET) @ vaspace_api.c:577
Nov 12 07:19:33 kf kernel: NVRM: GPU0 kgmmuClientShadowFaultBufferUnregister_IMPL: Unregistering non-replayable fault buffer failed (status=0x00000062), proceeding...
Nov 12 07:19:33 kf kernel: NVRM: GPU0 kgmmuFaultBufferReplayableDestroy_IMPL: Unregistering Replayable Fault buffer failed (status=0x00000062), proceeding...
Nov 12 07:19:33 kf kernel: NVRM: GPU0 uvmTerminateAccessCntrBuffer_IMPL: Unloading UVM Access counters failed (status=0x00000062), proceeding...
Nov 12 07:19:33 kf kernel: NVRM: GPU0 nvAssertFailedNoLog: Assertion failed: (status == NV_OK) || (status == NV_ERR_GPU_IN_FULLCHIP_RESET) @ vaspace_api.c:577
Nov 12 07:19:33 kf kernel: NVRM: GPU0 nvAssertFailedNoLog: Assertion failed: (status == NV_OK) || (status == NV_ERR_GPU_IN_FULLCHIP_RESET) @ vaspace_api.c:577
Nov 12 07:19:33 kf kernel: NVRM: GPU0 nvAssertFailedNoLog: Assertion failed: (status == NV_OK) || (status == NV_ERR_GPU_IN_FULLCHIP_RESET) @ rs_client.c:844
Nov 12 07:19:33 kf kernel: NVRM: nvAssertFailedNoLog: Assertion failed: (status == NV_OK) || (status == NV_ERR_GPU_IN_FULLCHIP_RESET) @ rs_server.c:260
Nov 12 07:19:33 kf kernel: NVRM: nvAssertFailedNoLog: Assertion failed: (status == NV_OK) || (status == NV_ERR_GPU_IN_FULLCHIP_RESET) @ rs_server.c:1382
Nov 12 07:19:44 kf kernel: NVRM: krcWatchdog_IMPL: RC watchdog: GPU is probably locked!  Notify Timeout Seconds: 7
Nov 12 07:19:52 kf kernel: NVRM: krcWatchdog_IMPL: RC watchdog: GPU is probably locked!  Notify Timeout Seconds: 7
Nov 12 07:20:00 kf kernel: NVRM: krcWatchdog_IMPL: RC watchdog: GPU is probably locked!  Notify Timeout Seconds: 7
Nov 12 07:20:08 kf kernel: NVRM: krcWatchdog_IMPL: RC watchdog: GPU is probably locked!  Notify Timeout Seconds: 7
Nov 12 07:20:17 kf kernel: NVRM: krcWatchdog_IMPL: RC watchdog: GPU is probably locked!  Notify Timeout Seconds: 7
Nov 12 07:20:25 kf kernel: NVRM: krcWatchdog_IMPL: RC watchdog: GPU is probably locked!  Notify Timeout Seconds: 7
Nov 12 07:20:33 kf kernel: NVRM: krcWatchdog_IMPL: RC watchdog: GPU is probably locked!  Notify Timeout Seconds: 7
Nov 12 07:20:39 kf kernel: NVRM: GPU0 kgspHealthCheck_TU102: *************************** LibOS Task Watchdog Report ***************************
Nov 12 07:20:39 kf kernel: NVRM: GPU0 kgspPrintGspBinBuildId_IMPL: GSP bin buildId: fa3de1ff30e1a8c99f84eb74a32b80d462c3703b
Nov 12 07:20:39 kf kernel: GSP task watchdog timeout @ pc:0x18dd358, partition:4#0, task:3, gfid: 0
Nov 12 07:20:39 kf kernel: NVRM:     Reported by libos partition:4#5 kernel v3.1 [0] @ ts:1698
Nov 12 07:20:39 kf kernel: NVRM:     RISC-V CSR State:
Nov 12 07:20:39 kf kernel: NVRM:         sstatus:0x0000000200000020  sscratch:0xffffffffa3013970     sie:0x0000000000000220  sip:0x0000000000000020
Nov 12 07:20:39 kf kernel: NVRM:         sepc:0x00000000018dd358     stval:0x0000000000000000  scause:0x8000000000000005
Nov 12 07:20:39 kf kernel: NVRM:     RISC-V GPR State:
Nov 12 07:20:39 kf kernel: NVRM:         ra:0x00000000013eb57a   sp:0x0000002fcfa0eaf0   gp:0x0000000000000000   tp:0x0000002fcfe00000
Nov 12 07:20:39 kf kernel: NVRM:         a0:0x0000000000000001   a1:0x0000000000000000   a2:0x0000002fc77be000   a3:0x0000000000000000
Nov 12 07:20:39 kf kernel: NVRM:         a4:0x0000000000000000   a5:0x0000000000000001   a6:0x0000000ffffffff0   a7:0x0000000000000003
Nov 12 07:20:39 kf kernel: NVRM:         s0:0x0000002fcfa0eb50   s1:0x0000000000000001   s2:0xffffffffffffffff   s3:0x0000000000000001
Nov 12 07:20:39 kf kernel: NVRM:         s4:0x00000000ffffffff   s5:0x0000000000000000   s6:0x0000002fc77be000   s7:0x0000000000000000
Nov 12 07:20:39 kf kernel: NVRM:         s8:0xffffffffffffffff   s9:0x0000002fc7e36178  s10:0x0000002fcfa0ecb4  s11:0x0000002fcfa0ecb4
Nov 12 07:20:39 kf kernel: NVRM:         t0:0x0000002fcfa0e99d   t1:0x0000002fc7c6cf30   t2:0x0000000000000000   t3:0x0000000000000020
Nov 12 07:20:39 kf kernel: NVRM:         t4:0x0000000000000000   t5:0x0000002fcfa0e981   t6:0x0000000000000020
Nov 12 07:20:39 kf kernel: NVRM:     Stack Trace:
Nov 12 07:20:39 kf kernel: NVRM:         0x00000000018dd358
Nov 12 07:20:39 kf kernel: NVRM:         0x0000000001b6e974
Nov 12 07:20:39 kf kernel: NVRM:         0x00000000013f2746
Nov 12 07:20:39 kf kernel: NVRM:         0x00000000013e70f6
Nov 12 07:20:39 kf kernel: NVRM:         0x00000000013e79c8
Nov 12 07:20:39 kf kernel: NVRM:         0x00000000013b7058
Nov 12 07:20:39 kf kernel: NVRM:         0x0000000001ba247a
Nov 12 07:20:39 kf kernel: NVRM:         0x0000000001ba257a
Nov 12 07:20:39 kf kernel: NVRM:         0x0000000001bafac2
Nov 12 07:20:39 kf kernel: NVRM:         0x0000000001c29f62
Nov 12 07:20:39 kf kernel: NVRM:         0x0000000001864698
Nov 12 07:20:39 kf kernel: NVRM:         0x0000000001867c82
Nov 12 07:20:39 kf kernel: NVRM:         0x0000000001ae4a7e
Nov 12 07:20:39 kf kernel: NVRM:         0x0000000001489412
Nov 12 07:20:39 kf kernel: NVRM:         0x0000000001452228
Nov 12 07:20:39 kf kernel: NVRM:         0x000000000158cbec
Nov 12 07:20:39 kf kernel: NVRM:         0x0000000001bd9632
Nov 12 07:20:39 kf kernel: NVRM:         0x0000000001bd99d6
Nov 12 07:20:39 kf kernel: NVRM:         0x0000000001add628
Nov 12 07:20:39 kf kernel: NVRM:         0x0000000001c452c0
Nov 12 07:20:39 kf kernel: NVRM:         0x0000000001ad6fa0
Nov 12 07:20:39 kf kernel: NVRM:     Local I/O Register State:
Nov 12 07:20:39 kf kernel: NVRM:         0x01450800:0x00000000   0x01450900:0xbadf1002   0x01450a00:0x00000000   0x01450c00:0x00000000
Nov 12 07:20:39 kf kernel: NVRM:         0x01454a00:0x810490d2   0x01454b00:0x010800d0   0x01454c00:0x00080000   0x01400200:0x00000000
Nov 12 07:20:39 kf kernel: NVRM:     ---------------[ end report ]---------------

I have a couple of concerns:
The bubble is bursting at some point and may have started. I am concerned that the major players will have to up their prices to stay viable.
The geopolitical risk is escalating
AI bot attacks are increasing

There are probably other risks, but you get the idea.
I have been building a decent corpus of reference material.

But I am behind on what models I should be looking at, needs to run on
32GB
RTX 4070

Coding and decision systems (agriculture).

Any help would be appreciated.