Solved BSOD in games after last Nvidia update

[axe0]

The focus is to stabilize your system, on an unstable system any overclocking could make the system more unstable.

 

[Layback Bear]

A little information that might be helpful.

I have over clocked my systems for years.
On one of my older system (i7-960) the over clock had to be reduced to keep away from BSOD.
Your (860) is a lot like my (960). They run hotter that most cpu even when they are not over clocked, and the memory controller is located in the cpu. Time and temps lower the ability it once had.

I think what happens is do to time and use the hardware is no longer able to handle the over clock. Hardware does wears in small percentages without breaking. All electronics loose their efficiency and abilities over time and use.
I just kept lowering the cpu and ram over clock until the system was happy.

What cpu cooler do you use?


You state on post #60

Processor had been overclocked since 2008 when i first installed windows 7

 

[Lunideth]

Antec khuler 650

I understand about overclocking and stuffs, but im really sure that its cause of graphics.
BSOD's only occur in dx10/11 games. Graphics dont matter. i can play on lowest or on max and still get random crashes or bsod's.

In same time i can play any dx9 game on max for several hours without any crashes. Best example is Lost planet 2. you can play either dx9 or dx10 version. And on dx10 i get crashes. dx9 again works fine.

Also in normal everyday use i dont have any crashes. I have 30 tabs open in opera, winamp, steam, origin, etc. I have dozen programs open at same time and dont get any crashes or anything.

But as soon as i try to play dx10/11 game i crash / get BSOD.

 

[Lunideth]

Don't forget memory corruption can be GFX ram or HDD pagefile as well as actual RAM.
Have you checked your temps while playing ? in particular gfx temps to see if they are going to high
You could try furmark to stress your card while monitoring temperatures

Thanx for reminding me about other memories besides RAM. Because i remembered one thing.

My cooler has colors. It changes colors: white -> light blue -> blue -> pink -> violet -> red depending on temperature.

And about 2 months ago (when i started to have crashes) it turned to pink during idle. It is supposed to be white / light blue. I didnt pay any attention to that. Today i remembered your post and though: RAM cannot be bad because i tested it, SSD cannot be bad, because its new ssd and health software is monitoring it which leaves cpu and then i remembered that my cpu is running too hot.

I forgot that idle temperature is not supposed to be 55-60. So today i changed thermal paste and TADAA idle temp is around 35-40 and MAX temperature i got by playing games for several hours straight was 78c

So today i played several hours different games and didnt get single crash or BSOD.

Its strange though that i was able to play dx9 games on mx graphics and dx10 crashed even on lowest settings, i guess those games just use more cpu.

So ill test bit more, but i think that BSOD is solved.

 

[Layback Bear]

I'm surprise a over heating problem didn't show up in your post #13

Added system specs.
Run 3dmark. - No problems / no crashes
Run OCCT tests: PSU, CPU, GPU. Run each test for several hours - No errors / no crashes
Run memtest86 - No errors

I recommend not depending on the little colored lights to monitor your temps.
I recommend using Realtemp to monitor the temps. Works quite well with Intel cpu's.

I'm back to watching.

 

[Lunideth]

Also is strange that dx9 games and normal using wasnt causing anything. Best example is Lost Planet 2. I launch dx10 mode and it crashes in about 30min. I launch dx9 mode with same graphics and everything and play without crashes.

Well 2 days without crashes / BSOD's so i think its solved.

I will install all my software back one by one and see how it goes, but i dont think that any bsods will occur anymore.

Tahnk to everyone who was helping me to figure this out. Especially to 'Axe0' who made me uninstall everything to point it to same error to figure what was causing bsods.