Hi All,

Made an Account just to post this.

So the long and short is that I have been testing work arounds for this abomination that is Dev error 6068.

I hadn't had any issues since launch then all of a sudden 3 weeks ago I tried to launch campaign and do another play through, it was only once the textures for this had updated that I started to have issue.

First it was in campaign with it freezing within 45 seconds. Then I went to go back and play multiplayer, then all of a sudden I couldn't get past the countdown of a match before the game would error and crash.

After reading through the various forums and trying all manner of fixes as so that I could at least say I had tried. I was now on my 3rd OS reinstall and had created various restore points in windows post install.

Part of this was so that I could one by one go through and try each fix, with all settings in game being set to low or off graphically excluding textures which were set to high.

Now, the 6068 Error in windows is reflected by saying that is has failed to access parts of the working memory.

-----------------------------------------------

Fault bucket 1162274100054865994, type 5
Event Name: D3DDRED2
Response: Not available
Cab Id: 0
Problem signature:
P1: VEN_10DE
P2: 26.21.14.4259
P3: 0x887A0006
P4: 3
P5: ModernWarfare.exe
P6: 1.0.0.0
P7: 
P8: 
P9: 
P10: 
Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF68F.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF6A0.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF6B0.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF6D1.tmp.txt
These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_VEN_10DE_fbbd9533e224289229531938fe99418eafcc50_00000000_956ffeac-5166-41b6-8ead-f424223d8e76
Analysis symbol: 
Rechecking for solution: 0
Report Id: 956ffeac-5166-41b6-8ead-f424223d8e76
Report Status: 268435456
Hashed bucket: 6e68b7d6054ebe7cd0213a22d168384a
Cab Guid: 0

--------------------------------------------

Now to Clarify I have gone through every fix I could find, tested and then rolled back.

The baseline hardware config is:

OS Name Microsoft Windows 10 Pro
Version 10.0.18363 Build 18363
Other OS Description    Not Available
OS Manufacturer Microsoft Corporation
System Name <COMPUTERNAME>
System Manufacturer System manufacturer
System Model    System Product Name
System Type x64-based PC
System SKU  ASUS_MB_CNL
Processor   Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz, 3600 Mhz, 8 Core(s), 8 Logical Processor(s)
BIOS Version/Date   American Megatrends Inc. 1401, 11/26/2019
SMBIOS Version  3.2
Embedded Controller Version 255.255
BIOS Mode   UEFI
BaseBoard Manufacturer  ASUSTeK COMPUTER INC.
BaseBoard Product   ROG MAXIMUS XI FORMULA
BaseBoard Version   Rev 1.xx
Platform Role   Desktop
Secure Boot State   Off
PCR7 Configuration  Binding Not Possible
Windows Directory   C:\WINDOWS
System Directory    C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume2
Locale  United Kingdom
Hardware Abstraction Layer  Version = "10.0.18362.628"
Username    <USERNAME>
Time Zone   
Installed Physical Memory (RAM) 64.0 GB
Total Physical Memory   63.9 GB
Available Physical Memory   58.9 GB
Total Virtual Memory    73.4 GB
Available Virtual Memory    66.1 GB
Page File Space 9.50 GB
Page File   C:\pagefile.sys
Kernel DMA Protection   Off
Virtualisation-based security   Not enabled
Device Encryption Support   Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and the device is not Modern Standby, Un-allowed DMA-capable bus/device(s) detected, TPM is not usable
Hyper-V - VM Monitor Mode Extensions    Yes
Hyper-V - Second Level Address Translation Extensions   Yes
Hyper-V - Virtualisation Enabled in Firmware    No
Hyper-V - Data Execution Protection Yes

​

GPU: (MSI) NVIDIA GTX1080
GPU Driver Version: 442.59-desktop-win10-64bit-international-whql

I made sure that during testing though that I was on the last known working driver for me which was:

436.48-desktop-win10-64bit-international-whql

----------------------------------------------------------------------------------------------------------------------------------------------------

Now during all of this testing there was no AV installed and no other interference from windows defender.

List of fixes tested:

• add argument line to Battlenet '-d3d11'
• modify and reduce all graphical options in COD
• re-install COD with not breaks in the download or patches
• remove all files apart from executables and folders in '<INSTALLED DRIVE>:\Blizzard\Call of Duty Modern Warfare'
• Remove drivers using 'DDU v18.0.2.2'
• Update all GPU Drivers
• Update all Windows Updates
• Roll back to last known working windows updates
• Run Battlenet and COD as Administrator
• Close the Battlenet Launcher after game launch
• Repair the game files post installation
• Run in various screen modes (Borderless, Fullscreen, Windowed etc)
• Update UEFI/BIOS to the latest version
• Test with other games and see if you would still get crashes in those games (I didn't)
• Plus a few others I have forgotten.

​

In the end no matter what I tried the game would not stop crashing, it was even to the point that the game would crash in safe mode sometimes, more so when you tried to play a match.

After some careful verbose logging and monitoring I started to notice that the GPU was starting to spike to 100% just before the crash, essentially this is what you would see if there was a memory leak in a game, either with RAM, VRAM or CPU.

​

This was pretty consistent and I was able to replicate it every time.

I decided to install MSI Afterburner to monitor this further, as it stood I was getting the same results.

There was one last thing to try.

In MSI Afterburner I set the default clock speed down -350MHZ on both the Core clock and the Memory Clock.

​

GPU Spikes in Testing

5 minutes later I was up and running again! Now, I almost lost it when the following day I was back to square one and all of a sudden I wasn't able to play. As it turned out I forgot to save the profile and had to reset the configuration of the clocks. After this I tested again and it worked! I turned it off and it went downhill again, so the fix is able to be replicated.

Long story short, you need to under clock your GPU until Activation fixes this memory leak!

Essentially you need to under-clock it by about 10-15% so it wont spike to 100% usage.

​

TL;DR.

Possible fix is to under-clock your GPU with a default profile using GPU overclocking software (preferably one supplied by your cards manufacturer)