Blue Screen while gaming

[Yankee]

Lately I have started getting BSOD's while playing BF2.

It says "Windows needed to shut down because something was wrong blah blah"

Then it usually gives me a memory address or three. And other times it says the file "NV4_something.dll" was the problem.

 

I'm assuming that is my graphics driver?

So then I updated my driver to the newest (without using DriverCleaner mind you) and I still got the problem.

 

This usually happens about twice in a few hours of gaming. It's not really a big deal because I just restart and keep playing. But I know this is fixable, and I would like to see this go away.

 

Any help would be awesome.

[KimTjik]

I saw you had another thread with practically the same question, but that time focused on testing RAM. So practically you'll have the same problem again, is that correct?

 

Another important question: when you say "BSOD's while playing BF2" I suppose that's done with the settings shown in your signature. Just as a test: if you play BF2 without overclocking settings, do you still get BSOD's? If not it's just a questions of taking the time to adjust your settings, or if that doesn't work maybe "humble" yourself a bit by OC less.

 

I ask this question, since there sometimes seem to be a understanding that you just have to demand certain performance. But OC is OC and there's no garuantees. Test programs will save you a lot of time by telling you when the system is stabile, but that's not 100 % true, since running real applications sometimes prove the opposite.

[Yankee]

Yes, I did post a thread about random restarts while playing BlackHawk Down.

I basically gave up on that game b/c its full of cheaters, so I crossed that off the list.

 

I thought it was a RAM problem b/c it gave me a memory address, and I saw the HUGE thread about ppl having problems w/ Crucial.

And now I'm still getting memory addresses in the BSOD. However, the majority of the time it deals w/ the NV4.dll which deals w/ my graphics. So I was thinking it was my drivers or my video card. I had it clocked at 490/1300.. then got BSOD's, then clocked it at "Optimal" w/ Coolbits. Now it's at 490/1270.

 

I have not tried playing w/ a lesser OC. I suppose that's a start.

I did Prime it for 24 hrs and also ran a MemTest on the RAM for 10+ hrs I believe. (Can't remember exactly how long)

So I assumed the system was completely stable. And yes, I understand that having it stable w/ Prime for 24 hrs doesn't guarantee anything, but it should say something.

I know gaming is the ultimate test to see if you're system is stable, but I have only recently been getting this problem.

 

I would like to avoid 'downclocking' if possible. If I could fix the problem w/o changing BIOS settings, it would be fantastic, but if that's the only solution then I have no choice.

[KimTjik]

Let's say you "downclock" to 2.7Ghz it isn't a catastroph, or? So it at least would be a option. Another point, when you're rightly address the problems some have had with those memory modules, and you refered to MemTest 10+ hrs, does that mean you recently did that test? Or was that done last time you had problems? I'm asking since some guys have experienced degradation of their Ballistix.

[Yankee]

Clocking back to 2.7Ghz isn't a big deal. I really only wanted to peak my performance for benchmarks anyways. It is definitely an option. But do you really think going from 2.8 to 2.7 will actually help/solve the problem?

 

I did the MemTest when I posted about my BSOD's the 1st time. I figured it was my RAM since so many had problems w/ it. I have not done the test since.

[wevsspot]

The NV4.dll fatal error is a classic failure of excessive overclocking on you video card. I can make mine do the exact same thing. You need to back down a little on your video card overclock and run 3DMark01, 03 and 05

 

Continue tweaking your overclock until you can successfully run all three of those benchmarks without any visual artifacting or loss in overall score. Especially in 3DMark05, you will see a drastic reduction in your overall final score if you are "too" far overclocked on your card.

[Yankee]

Thank You! Finally someone actually referring to my posts.

I knew it had to deal w/ the video card.

 

I did put my card settings at "Optimal Frequency" now. I'll run the 3DMark benches tonight and see what happens. Or do you think I should back down even more just to be safe?

 

I only get the BSOD's while playing BF2, which requires a heavy load on the video card.

I'll let ya know how it goes.

 

Thanks again for the tip.

[KimTjik]

This forum works! There's nearly always someone who has experienced the same problem.

[Yankee]

Absolutely!

 

Also, a Thanks to you KimTjik.

 

I just never figured an OC'd video card could create a BSOD.

I always thought it was due to RAM or data corruption. I'm still learning, give me time and patience please.

[wevsspot]

The Nvidia graphics drivers do an interesting thing. They "automatically" add approximately 40mhz to your gpu clocking when you are running in 3D mode. I'll use my GT card as an example. I've manually set my overclock to 435 GPU and 1100 memory. When I run a 3D application my card clocks to 473 on the GPU. Yours will do the same (you can verify this by running 3DMark03 and you will see that your GPU clock at the end of the test will be approx. 40mhz higher than your manual overclock settings. That is what causes the extreme stress on your v/c and the resulting BSOD and driver error messages. I'd recommend downclocking from the Nvidia detected "optimum" frequency. To be safe you could start at about 30mhz below the optimum and start working your way up from there. Testing every change by running all of the 3DMark benchmarks. I just want to reiterate the important information I've provided. Your Nvidia drivers WILL add an additional 35-40mhz to whatever your manual overclock is when running in 3D mode.

[divided]

i have a 6800 gs and nivida "optimal" settings clock it at 515/1200. which is too high for my card. i get artifacts in 3dmarks..although it hasnt blue screened me yet. i usually check the optimal then clock it down a few to be safe.

[tootintorrey]

that bf2 prob crashing with overclocked videocards is all over the bf2 forums. i dont remember the forum i never registered or spent time i was just looking at the list of supported vid cards. the settings for the game recommend that you dont overclock at all while your playing becuase its a very demanding game on your pc. if i would of saw this earlier i could have told you that.