BF4 causes endless TDR's

[CapStar362]

PSU is tested and within very tight specs using a load meter, DMM and Dr. Power II PSU tester, tested both under load with the meter and DMM. tested clean out of the chassis with DR. Power II Tester. PG is showing on multiple passes around 270-310 ms . all rails are within almost a .2 tightness under load and clean.

only thing i dont have is a full oscilloscope to test ripples.

entire configuration is run behind a APC BR1500G 865 W rated UPS. the most the PC has ever pulled, was about 660 Watts. verified by Kill-a-watt and APC unit. another smaller unit runs the network gear, monitors and accessories. and have no link to each other.


i actually have tested a clean install, running a core environment. latest win 7 pro x64 + SP1, BF4 only and critical OEM Updated drivers only.


any other game? no issues 100% , even BF3 X-Plane, FSX ( running in DX-10 Mode ) , BF2, BF-BC2, Bf-1942, BF2142, BFV.... Rust, Hero's and Generals......nothing has this issue.


im working on getting 8.1, had a minor issue with another car recently, no extra $$$


i have read that the 650 Ti BOOST was particularly buggy at first........ would 660 reference or 660Ti be a better choice? if i can get those from eVGA as RMA's by slight chance of "requesting them" then ill jump on that. eVGA's policy says, that if a SLi config is RMA'ed BOTH cards HAVE to be replaced. if only one of a SLi is present, BOTH cards get bumped.

 

[eidairaman1]

650ti and 660ti are not the same. They will give you a 660 at best if youre lucky otherwise itll be the equivalent in the 700 series

 

[OneMoar]

Which could have a corrupt config file. Clean install is the only way to fly in this case.

what the fk are you talking about jesus sometimes I wonder about you
1. you have no way of knowing if there even is a relevant "config file"
2. by %user% data I mean anything in documents\downloads ect %appdata% is purged
tho you did give me a idea ...
try deleting everything in C:\Users\yourusername\AppData\Local\Temp\NVIDIA Corporation\NV_Cache
also purge documents\my games\battlefield 4 ( you will lose your sp saves)
make sure you are running the latest drivers ofc

 

[TheMailMan78]

Oscilloscope.......I'm so happy to hear you say that. You just gained some serious internet points with me.

Anyway have you trying one card at a time? Not just turning off the SLI but actually yanking the card out? Also tried them in different slots?

Second have you tried down clocking the cards slightly? I can believe you may have a bad card. BUT I doubt you have two bad cards. My gut still tells me this is software.

what the fk are you talking about jesus sometimes I wonder about you
1. you have no way of knowing if there even is a relevant "config file"
2. by %user% data I mean anything in documents\downloads ect %appdata% is purged
tho you did give me a idea ...
try deleting everything in C:\Users\yourusername\AppData\Local\Temp\NVIDIA Corporation\NV_Cache
make sure you are running the latest drivers ofc

BF4 keeps all setting configs in the users folder. I have seen people dump that and it fixed all their issues. Doesn't matter. He already said he did a clean install.

 

[OneMoar]

Oscilloscope.......I'm so happy to hear you say that. You just gained some serious internet points with me.

Anyway have you trying one card at a time? Not just turning off the SLI but actually yanking the card out? Also tried them in different slots?

Second have you tried down clocking the cards slightly? I can believe you may have a bad card. BUT I doubt you have two bad cards. My gut still tells me this is software.

he said its ONLY battlefield 4

 

[TheMailMan78]

he said its ONLY battlefield 4

And? BF4 stresses a system even more than BF3 did. BF4 is a great stability test.

 

[OneMoar]

And? BF4 stresses a system even more than BF3 did. BF4 is a great stability test.

no its just a terribly written console port I had the same issue as the Op with battlefield 3
inefficient engine != stability test

 

[OneMoar]

Oscilloscope.......I'm so happy to hear you say that. You just gained some serious internet points with me.

Anyway have you trying one card at a time? Not just turning off the SLI but actually yanking the card out? Also tried them in different slots?

Second have you tried down clocking the cards slightly? I can believe you may have a bad card. BUT I doubt you have two bad cards. My gut still tells me this is software.



BF4 keeps all setting configs in the users folder. I have seen people dump that and it fixed all their issues. Doesn't matter. He already said he did a clean install.

so why recommend a format if all he needs todo is delete one folder sheesh overkill

Try disabling shader cache via the nv cp
also set single display performance mode to enabled

 

[TheMailMan78]

so why recommend a format if all he needs todo is delete one folder sheesh overkill

Try disabling shader cache via the nv cp
also set single display performance mode to enabled

I recommended a full format to eliminate software conflicts and it will also toss any old configs. That's all irrelivent now as he said he did a clean install so it has to be a driver issue or sadly hardware. I don't want the man to RMA both cards when chances are it would only be one. Just have to narrow things down. Also if you had the same problem as the OP in BF3 how come none of your remedies have worked thus far? You always skip the most basic troubleshooting OneMoar and go right to dicking around in the registry and such. I had no issues with BF3 and any BF4 issues were noted by DICE in "Known Issues". Plus I used to beta test for DICE back in the BF2 days when you were still in diapers. I trouble shoot DICE games like I FAP. Fast and efficient.

And for G-d sake stop double posting. You look like a noob.

 

[CapStar362]

mail, yes, i have tested for the last 4 weeks every possible config with the cards. Single one at a time, swapping both back and forth, SLi Bridge in and enabled, Sli Disabled and Bridge in, SLi bridge Out.... monitors on 1st card then second card. switching between dedicated PhysX and display.... im really about to rip my hair out.


i can try the temp files next. then cache and single card.


honestly, id rather RMA both cards anyways and chance getting 660's or even newer if possible per eVGA's policy.


you BETA'ed BF2? what the hell ? EA has some serious BAWLZ to do what they did to DICE. months into BF2 dev, hire a whole new crew and retain the DICE name!! i wish the original DICE was still here, we wouldnt have this issue. the ORIGINAL DICE of BF-1942 Desert Combat!

thats how long ive played BF Franchise. since 2003.

oh personal note: im 33


also its funny to me, BF3, BfBC2+ Vietnam, BF2142, BFV, BF2, Bf1942 + Desert Combat, FSX, Rust, H&G...... NOT a single other game gives me TDR's for DAYS ( if i were to play them that long endlessly )





two of the files in the C:\Users\yourusername\AppData\Local\Temp\NVIDIA Corporation\NV_Cache

were in use by Windows Manager, could not be deleted. going to test now......

 

[OneMoar]

I recommended a full format to eliminate software conflicts and it will also toss any old configs. Also if you had the same problem as the OP in BF3 how come none of your remedies have worked thus far? You always skip the most basic troubleshooting OneMoar and go right to dicking around in the registry and such. I had no issues with BF3 and any BF4 issues were noted by DICE in "Known Issues". Plus I used to beta test for DICE back in the BF2 days when you were still in diapers. I trouble shoot DICE games like I FAP. Fast and efficient.

because unlike You I have a better understanding of what can trigger and TDR event and what its possible causes are at the API level and if you scroll back you will see that adjusting the tdrdelay did help somewhat I didn't expect it to cure the problem its

recommending a format because one program isn't functioning correctly bit like using a flame thrower to kill weeds with ..effective and completely unnecessary.. and in this case it would have been wrong because he did that it didn't make a fucking bit of difference now did it.

also the final nail in your coffin is that you say stuff like "dicking around in the registry" as if the registry is some magical land of evil trolls and boogiemen that right there tells me where your limit-of-experience is
I have no tolerance for the " I don't really know exactly what the problem is so lets nuke it and start over" school of tech support that just promotes ignorance and FUD and more often then not doesn't get the desired results

 

[OneMoar]

mail, yes, i have tested for the last 4 weeks every possible config with the cards. Single one at a time, swapping both back and forth, SLi Bridge in and enabled, Sli Disabled and Bridge in, SLi bridge Out.... monitors on 1st card then second card. switching between dedicated PhysX and display.... im really about to rip my hair out.


i can try the temp files next. then cache and single card.


honestly, id rather RMA both cards anyways and chance getting 660's or even newer if possible per eVGA's policy.


you BETA'ed BF2? what the hell ? EA has some serious BAWLZ to do what they did to DICE. months into BF2 dev, hire a whole new crew and retain the DICE name!! i wish the original DICE was still here, we wouldnt have this issue. the ORIGINAL DICE of BF-1942 Desert Combat!

thats how long ive played BF Franchise. since 2003.

oh personal note: im 33


also its funny to me, BF3, BfBC2+ Vietnam, BF2142, BFV, BF2, Bf1942 + Desert Combat, FSX, Rust, H&G...... NOT a single other game gives me TDR's for DAYS ( if i were to play them that long endlessly )





two of the files in the C:\Users\yourusername\AppData\Local\Temp\NVIDIA Corporation\NV_Cache

were in use by Windows Manager, could not be deleted. going to test now......

thats fine the files in use are most likely from DWM you can try switching the shader cache off in the NVCP
at this stage I am leaning toward you have a driver problem the nvidia needs to address try the rolling back the driver to 335.23 if the above doesn't correct it
try setting stuff to high one setting at a time while leaving the rest on medium/low to see if you can isolate the problem

 

[TheMailMan78]

mail, yes, i have tested for the last 4 weeks every possible config with the cards. Single one at a time, swapping both back and forth, SLi Bridge in and enabled, Sli Disabled and Bridge in, SLi bridge Out.... monitors on 1st card then second card. switching between dedicated PhysX and display.... im really about to rip my hair out.


i can try the temp files next. then cache and single card.


honestly, id rather RMA both cards anyways and chance getting 660's or even newer if possible per eVGA's policy.


you BETA'ed BF2? what the hell ? EA has some serious BAWLZ to do what they did to DICE. months into BF2 dev, hire a whole new crew and retain the DICE name!! i wish the original DICE was still here, we wouldnt have this issue. the ORIGINAL DICE of BF-1942 Desert Combat!

thats how long ive played BF Franchise. since 2003.

oh personal note: im 33


also its funny to me, BF3, BfBC2+ Vietnam, BF2142, BFV, BF2, Bf1942 + Desert Combat, FSX, Rust, H&G...... NOT a single other game gives me TDR's for DAYS ( if i were to play them that long endlessly )





two of the files in the C:\Users\yourusername\AppData\Local\Temp\NVIDIA Corporation\NV_Cache

were in use by Windows Manager, could not be deleted. going to test now......

I would try down clocking for shits and giggles. At this point how can it hurt? Also see if you can score a copy of Windows 8.1. Even ifs its a 30 day trial. This will tell you right away if its an OS issue and might save you some money RMA'ing your cards. Also don't judge TPU by this thread. You got a special blend of fail for your first thread. "All the know it alls" flowed in and busted on ya. Just get thick skin and look for some kind of clues in the posts. Sometimes people say smart things by mistake Also have you tried rolling back your driver to the drivers that came with the cards to begin with?

FYI I'm 36 so I know were you are coming from on DICE.


@OneMoar its hard to take you seriously when you keep double posting. Not something that would instill confidence to trust your vast registry knowledge. Are you still living in your grandmas addict? You might want to open a window.

 

[Assimilator]

Given all the things you've tried, my suggestion would be to start a process of elimination. Swap out the graphics cards for a different one and test. If problem persists, swap out memory for another set, etc. Repeat until problem goes away or you no longer have a desire to waste your time on an unfinished console port.

 

[TheHunter]

TDR in BF is either gpu voltage issue or driver issue..

Dx errors issue IS corrupted driver with bad gpu OC, reinstalling the driver (overwrite) and lower OC fixes it 100%.

Getting both at the same time, driver, bad OC, voltage issue and even corrupted cfg in my documents, PROFSAVE_profile <<< delete this file (C:\Users\...\Documents\Battlefield 4\settings)

Sometimes altering TDR timeout in windows can help too,
http://http.developer.nvidia.com/Ns...e/HTML/Content/Timeout_Detection_Recovery.htm

http://msdn.microsoft.com/en-us/library/windows/hardware/ff569918(v=vs.85).aspx

 

[CapStar362]

down clock produced no results. so far Moar's TDRDelay reg entry helped the most. trust me when i say, EVERYTHING else you guys have suggested i have done already redundantly!! multiple times for hardware passes, clocks.... i even took my 650Ti BOOST's SSC's to reference 650 Stock speeds, no help.

right now, if you go back and read everything i have done........ it HAS to be either Driver, or BF4.

ive low level tested the cards with VMT and OCCT. 100% Pass for HOURS of testing.

System Components 100% Pass for DAYS of testing.

the only things as of now i cannot test, the game itself the engine itself and DX itself.


assim, i have no other cards to test with, nothing that will run BF4. all i have is a pussy GT120 with 256 DDR2 laying around. least i think its 256