Recent content by keek

I've actually been working through the RMA on the Zotac, and we'll see what comes from that. My coworker is working with me on it and said that if we get a refurb he's just giving it to me (what a saint). So I guess I'll have his 4090 AND a 5070 Ti to sell in a few months, assuming it goes through.

Just as a final post, the 6750 XT is stable on the X870 platform with DDR5-6000 RAM. Not sure which component fixed it. I bought and installed a 5070Ti to upgrade since the rest of my build is new, and it's smooth as well. Nail in the coffin for that 4090. Sad.

The thing that was puzzling me before was that the 6750 XT was (on the prior platform: B650, old RAM) throwing the same watchdog violation, but in low-power/idle states. I'll have to give this plenty of time to see if that re-emerges. Thanks for all your help in troubleshooting, gentlemen.

I put the 6750 XT back in, and played ARC Raiders for an hour. The 4090 would reliably crash in less than 10 minutes, usually less than 5. I cranked everything back up to "normals" for me as well -- refresh rate on both monitors at 144Hz, Adaptive Sync on and FSR3 working just fine.

Does YCruncher work better/different than OCCT? OCCT tests pass.

I have been running things through ChatGPT for several weeks now, and I just had it analyze a PresentMon log along with an Aftermath bundle. Thought you all might be interested in its take: https://chatgpt.com/s/t_6960639264d081918933bfa1a173cd33

This is getting out of my wheelhouse, but I'll try to answer as best I can. HWInfo shows CPU VDDCR_SOC Voltage (SVI3 TFN) [V] at 0.896 at the time of the crash. The CPU VCORE SoC [V] was 0.924, and the GPU Core Voltage (VDDCR_GFX) [V] was pinned at 0.725.

Okay, did that--no difference. Same DPC_WATCHDOG_VIOLATION 0X133 black screen crash and reboot.

I added the file in Drivers as El_Capitan mentioned, and got a fresh minidump.

Decent thought, and I've actually done that aside from using integrated graphics. The main problem with that is, the only reliable crash avenue is the 4090 in a game with the settings turned up. For the AMD cards, it happens at random, exacerbated by low-power states like display off. I never...

Sorry to be thick, but do you mean C:\Windows\System32\Drivers\nvlddmkm.sys or C:\Windows\System32\Drivers\FileRepository\nv_dispi.inf_amd64_7840b4313191ae17\nvlddmkm.sys ?

I have one buried down in DriverStore: C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_7840b4313191ae17\nvlddmkm.sys, but nothing in Drivers. Is there a path it belongs there?

I tried 2 different M.2 drives in 2 different slots and one SATA SSD, all in isolation. Can't be cables or drives. I did fall down the rabbit hole of an NVMe issue caused by a Windows update on Phison storage controllers back around the right time frame, but the SATA SSD ruled that out.

Mostly nvlddmkm reporting error 14, but I also see 153 from the same source and 162 from volmgr. That last one is usually what writes the minidump which boils down to the Nvidia driver in the stack.

Yeah I tried that one at one point as well. Took longer to to crash, but still did.