January 2019
January 2019
@CooperAus is not "elitist" nor is he wrong.
XMP profiles are notorious unreliable and Ram Motherboard compatibility is a increasing problem, especially if you consider the fact that many Hi-end gaming systems run with Ram specs that are not certificated.
After the JEDEC Standard DDR3 is only certificated up to DDR-2133, DDR-4 up to 3200Mhz, and that only if the timings are also inside the parameters.
Or in other words, many XMP profiles overclock your RAM to a certain extend, running it outside the certificated parameters.
January 2019
Here is my GPU Z Sensor Log.
I on purpose did not downclock my GPU for this test. This is the last minute before the crash.
All was perfectly fine, then I got bombed by a plane and before the end of the explosion my computer crashed.
HDR is Off, DX12 on.
As you can see nothings wrong.
I also stress tested the GPU, No problem there. 9200 Furmark 1440p.
2019-01-07 04:03:09 , 2010.0 , 1750.0 , 50.0 , 76 , 2858 , 76 , 2858 , 6807 , 81 , 23 , 0 , 5 , 164.1 , 63.1 , 4 , 1.0370 , 59.1 , 11867 ,
2019-01-07 04:03:10 , 2010.0 , 1750.0 , 50.0 , 76 , 2822 , 76 , 2812 , 6787 , 82 , 23 , 0 , 5 , 191.4 , 73.6 , 4 , 1.0370 , 59.1 , 11871 ,
2019-01-07 04:03:11 , 2010.0 , 1750.0 , 51.0 , 76 , 2808 , 76 , 2797 , 6788 , 89 , 26 , 0 , 4 , 196.9 , 75.7 , 4 , 1.0370 , 59.1 , 11871 ,
2019-01-07 04:03:12 , 2010.0 , 1750.0 , 50.0 , 76 , 2809 , 76 , 2805 , 6788 , 76 , 23 , 0 , 4 , 170.3 , 65.5 , 4 , 1.0370 , 59.1 , 11871 ,
2019-01-07 04:03:13 , 2010.0 , 1750.0 , 49.0 , 75 , 2802 , 75 , 2797 , 6767 , 69 , 19 , 0 , 5 , 152.4 , 58.6 , 4 , 1.0370 , 59.1 , 11873 ,
2019-01-07 04:03:14 , 2010.0 , 1750.0 , 49.0 , 75 , 2775 , 75 , 2775 , 6781 , 68 , 18 , 0 , 5 , 159.7 , 61.4 , 4 , 1.0370 , 59.1 , 11871 ,
2019-01-07 04:03:15 , 2010.0 , 1750.0 , 49.0 , 75 , 2768 , 75 , 2775 , 6756 , 74 , 19 , 0 , 5 , 180.1 , 69.3 , 4 , 1.0370 , 59.1 , 11870 ,
2019-01-07 04:03:16 , 2010.0 , 1750.0 , 50.0 , 75 , 2781 , 75 , 2768 , 6730 , 79 , 20 , 0 , 5 , 175.9 , 67.7 , 4 , 1.0370 , 59.1 , 11875 ,
2019-01-07 04:03:17 , 2010.0 , 1750.0 , 49.0 , 76 , 2788 , 76 , 2790 , 6787 , 74 , 19 , 0 , 6 , 173.5 , 66.7 , 4 , 1.0370 , 59.1 , 11885 ,
2019-01-07 04:03:18 , 2010.0 , 1750.0 , 50.0 , 76 , 2809 , 76 , 2827 , 6776 , 75 , 19 , 0 , 6 , 173.6 , 66.8 , 4 , 1.0370 , 59.1 , 11879 ,
2019-01-07 04:03:19 , 2010.0 , 1750.0 , 49.0 , 76 , 2809 , 76 , 2812 , 6748 , 77 , 20 , 0 , 5 , 170.9 , 65.7 , 4 , 1.0370 , 59.1 , 11884 ,
2019-01-07 04:03:20 , 2010.0 , 1750.0 , 49.0 , 75 , 2795 , 75 , 2783 , 6771 , 73 , 19 , 0 , 6 , 163.9 , 63.0 , 4 , 1.0370 , 59.1 , 11877 ,
2019-01-07 04:03:21 , 2010.0 , 1750.0 , 49.0 , 76 , 2795 , 76 , 2790 , 6690 , 75 , 19 , 0 , 5 , 173.7 , 66.8 , 4 , 1.0370 , 59.1 , 11886 ,
2019-01-07 04:03:22 , 2010.0 , 1750.0 , 49.0 , 75 , 2795 , 75 , 2790 , 6772 , 70 , 18 , 0 , 5 , 176.8 , 68.0 , 4 , 1.0370 , 59.1 , 11884 ,
2019-01-07 04:03:23 , 2010.0 , 1750.0 , 49.0 , 76 , 2795 , 76 , 2797 , 6744 , 72 , 18 , 0 , 5 , 151.9 , 58.4 , 4 , 1.0370 , 59.1 , 11885 ,
2019-01-07 04:03:24 , 2010.0 , 1750.0 , 49.0 , 75 , 2788 , 75 , 2797 , 6765 , 68 , 18 , 0 , 5 , 187.5 , 72.1 , 4 , 1.0370 , 59.1 , 11876 ,
2019-01-07 04:03:25 , 2010.0 , 1750.0 , 49.0 , 76 , 2788 , 76 , 2790 , 6786 , 77 , 21 , 0 , 5 , 165.3 , 63.6 , 4 , 1.0370 , 59.1 , 11870 ,
2019-01-07 04:03:26 , 2010.0 , 1750.0 , 49.0 , 75 , 2795 , 75 , 2790 , 6780 , 67 , 18 , 0 , 5 , 166.0 , 63.9 , 4 , 1.0370 , 59.1 , 11863 ,
2019-01-07 04:03:27 , 2010.0 , 1750.0 , 49.0 , 75 , 2781 , 75 , 2768 , 6742 , 72 , 20 , 0 , 5 , 174.3 , 67.0 , 4 , 1.0370 , 59.1 , 11859 ,
2019-01-07 04:03:28 , 2010.0 , 1750.0 , 48.0 , 75 , 2775 , 75 , 2775 , 6756 , 71 , 19 , 0 , 5 , 140.1 , 53.9 , 4 , 1.0370 , 59.1 , 11868 ,
2019-01-07 04:03:29 , 2010.0 , 1750.0 , 49.0 , 75 , 2781 , 75 , 2775 , 6757 , 69 , 19 , 0 , 5 , 158.4 , 60.9 , 4 , 1.0370 , 59.1 , 11860 ,
Date , GPU Core Clock [MHz] , GPU Memory Clock [MHz] , GPU Temperature [°C] , Fan 1 Speed (%) [%] , Fan 1 Speed (RPM) [RPM] , Fan 2 Speed (%) [%] , Fan 2 Speed (RPM) [RPM] , Memory Used [MB] , GPU Load [%] , Memory Controller Load [%] , Video Engine Load [%] , Bus Interface Load [%] , Power Consumption (W) [W] , Power Consumption (%) [% TDP] , PerfCap Reason [] , VDDC [V] , CPU Temperature [°C] , System Memory Used [MB] ,
January 2019 - last edited January 2019
I really think it's a memory leak... It builds up to 12-13Go of Ram, starting around 4Go, and then some time not so long after that it crashes. The thing is I have 32Go...
January 2019
@FreeyaecoI also have 32GB of ram and I noticed the game is only using 4 max. I had one of the customer service guys tell me I have a memory leak. Unfortunately he just told me to contact Microsoft and closed my case.
I ran memtest for over 24 hours to see if my ram had any problems and 0 errors came back. So something is definitely set up wrong with this game.
January 2019
@biggestwig wrote:
@FreeyaecoI also have 32GB of ram and I noticed the game is only using 4 max. I had one of the customer service guys tell me I have a memory leak. Unfortunately he just told me to contact Microsoft and closed my case.
I ran memtest for over 24 hours to see if my ram had any problems and 0 errors came back. So something is definitely set up wrong with this game.
You normally don't test for the cause of memory leaks using memtest. It's usually bugs in software like the OS, drivers and applications that cause memory leaks and memtest would not detect that.
January 2019
Yes it's weird... Basically depending on the map it uses more or less Ram (normal), but where it gets weird : it's always on the more demanding maps that an explosion will cause the game/computer to crash.
January 2019 - last edited January 2019
@ BlackMoonWolf :
could you please give AT LEAST SOME MORE INFORMATION for your alegations ?!??
- kind of Problems affecting which games?!?!
since i did the Workaround i played BF 1, SW BF 2, Rainbow 6 Siege, Doom and other MP GAMES, with no problems WHAT SO EVER (after deactivating the Service " Killer Network Service")
so no PACKET LOSS , no reduction of PING & down / upload bandwith
besides a few People responded, saying this worked for them too
January 2019
After quite some time I have returned to this thread to report that my solution, removing all OC no longer works. I crash now every few minutes. Sometimes it's just a crash to desktop, other times it's a BSOD.
I've seen everything happen. From Kernelbase errors to simple DirectX issues. I've had my RAM, PSU, GPU and Windows itself have a fatal error according to the logs over time. By that logic my PC should be straight up broken, which it isn't. I can perform any test I'd like and it works like a charm.
BFV seriously needs a patch addressing performance issues.
Now realistically this is not something that is unknown for BF titles after launch. BF3/BF4/BFH/BF1 all have been haunted with severe issues and crashes after their launch. The most notorious one being the "GPU DEVICE REMOVED GTX XXXXX DRIVER XXX.XX" which has been around for all titles so far.
It's the devs turn to provide a solution given the number of people complaining about the exact same errors. There are a few thousand replies in the BF Forum itself and there are hundreds here on the Technical Forum. Should be clear by now that this is not our fault, this is not our own systems failing.
January 2019
@BillSanAnTonio wrote:@ BlackMoonWolf :
could you please give AT LEAST SOME MORE INFORMATION for your alegations ?!??
- kind of Problems affecting which games?!?!
since i did the Workaround i played BF 1, SW BF 2, Rainbow 6 Siege, Doom and other MP GAMES, with no problems WHAT SO EVER (after deactivating the Service " Killer Network Service")
so no PACKET LOSS , no reduction of PING & down / upload bandwith
besides a few People responded, saying this worked for them too
I really don't know who the hell has a "Killer Network Service" - i for sure don't. And my game is crashing more frequent now than before. Every 10-15 Minutes the game freezes and i find myself back at my Desktop again.