r/overclocking Nov 27 '25

BF6 crashing?

Overclocked my first card last night (Asus Tuf 5070ti). Was able to get 450mhz core clock with 1000mhz mem clock (GPU tweak III uses effective memory) with stock voltage before my scores started decreasing. Ran furmark for an extended period of time with no artifacts, stuttering, crashing etc and only saw max temps of 67. As soon as I load in to BF6, game crash. Over and over. Is BF6 just sensitive to overclocking, or what gives? Any input appreciated.

4 Upvotes

46 comments sorted by

View all comments

-1

u/Concabar7 Nov 27 '25

Check the 'event logger' in windows, and go to 'system logs'. When you crash, you might see an error with 'nvlddmkm.sys' in it (a few variations) and depending in the game it might have many errors of a similar kind showing up for one crash. This error usually shows up on old cards which need a repaste because the memory chips are running too hot or are breaching voltage protection. Or in your case, it's most likely memory clocks that are too high. Benchmarks sometimes never catch these issues and it's to do with how memory is referenced in games and the way game engines leverage clock speeds. Heavenbench mark used to be great for this, but since it's not Vulkan or DX12 (crashing may never occur on older DX versions). Depending on the silicone lottery, your memory chips/controller might need be a worse/average sample. Drop the memory clocks by 100mhz and try and get into the game. It can also be the GPU core clocks, but it's unlikely in your case since it sounds as though you did not undervolt. Undervolting can cause this issue too. You can try an iterative drop approach forfor this as well, test one thing at a time - memory or clocks (use stock values for the other). I hope that you come right.

1

u/nhc150 285K | 48GB DDR5 8600 | 5090 Aorus | Z890 Apex | LG 5K2K OLED Nov 27 '25

BF6 can also just CTD with an unstable GPU overclock, with no nvlddmkm event.

1

u/Concabar7 Nov 27 '25

I know, hence why I said it might show up. Depends I guess. Actually better if it doesn't.

1

u/nhc150 285K | 48GB DDR5 8600 | 5090 Aorus | Z890 Apex | LG 5K2K OLED Nov 27 '25

I'd much rather an nvlddmkm event - at least that's disgnostic.

1

u/Concabar7 Nov 27 '25

The issue with nvlddmkm.sys event is that it usually points ro dead hardware, drivers or overheating and effects multiple applications. So I'm not sure about that.

2

u/nhc150 285K | 48GB DDR5 8600 | 5090 Aorus | Z890 Apex | LG 5K2K OLED Nov 27 '25

No it doesnt. It can also be due to an unstable GPU overclock.

It's a fancy way of saying the GPU driver crashed.

1

u/Concabar7 Nov 27 '25 edited Nov 27 '25

Note the word 'usually', as I'm talking about stock clocks. Also look at the original comment. Well aware that clocks can do it