BIG TROUBLESHOOT POST IF CoD HQ or Black Ops 6 CRASHES

[nurlan2007944]

Hello, since the Black Ops 6 Beta dropped, some people started to have some problem (hardware, software etc). I've made a big thread with possible solution to some problems, however it's really hard to figure out some solutions, especially "error code 0xC000001D (0) N" and "Success launching "cod.exe hdeyguxs3zaumvlgvybm2vyc"", which isn't even a problem on CoD side. Please, use info down below if have any problems. Funny part is that I don't even own CoD BO6.

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

Edit: before you ask for help, please, check two things:

Call of Duty crash log:

C / User / you / AppData / Local / Activision / Call of Duty / Crash_reports /

Sort files by date and open the most recent file with WinRAR or 7-Zip. Inside you will find a file called dxdiag_oncrash.txt, open it, then scroll down to "Diagnostics". Under diagnostics section there will be a line called "Problem Signature", under it, you will see what program or process causes the crash. I hope this will help.

And for Call of Duty HQ, there is a main folder and file called "bootstraper.txt or . log"

———————————

I've got like 20+ friend requests because I can help with some crashes. I've decided to make a big post to save some time for the people, myself included.

IF YOUR CoD HQ CRASHES WITHOUT ANY MESSAGE OR MID-GAME OR WON'T EVEN START, try this:
0 - https://steamcommunity.com/app/1938090/discussions/0/4757577823502590346/

1 - open your main CoD HQ folder, find file "bootstraper.txt" (or .log), open it and watch the last line. If it says "invalid install path", put your STEAM folder into Program Files x86 folder (in french it's called Programmes (x86)) on your system drive. It's and old bug, but it should help.

2 - if your "bootstraper.txt" file says "failed to open randgrid.sys", you have two option:

2.1 - move "randgrid.sys" from your CoD HQ folder to the path it says in the "bootstraper.txt".

Example: your "randgrid.sys" file is the path: c/ steam / steam apps / common / CoD HQ /, but last line in the "bootstraper.txt" says "Failed to open C: / users / UserName / Downloads / Steam / steamapps / common / Call of Duty HQ /". You need to put the file into folder where "bootstraper.txt" tried to find it.

2.2 - If it doesn't help, move entire CoD HQ folder into the folder where "bootstraper.txt" tries to find it. Or just delete the whole game and install into the folder, where "bootstraper.txt" wants to find the "randgrid.sys" file.

3 - If "bootstraper.txt" says "open successfully" and there are some numbers and letters, on your desktop press START - WINDOWS SETTINGS - APPS / PROGRAMS , find Microsoft Visual C++ 2015-2022, you may have 1-4 programs named like this. Click on each one and then click "REPAIR". Once everything is repaired, reboot PC.

4 - If "bootstraper.txt" says nothing and your your CoD HQ doesn't start or crashing, DELETE COD HQ FOLDER from the "Documents" folder. Then validate files integrity through Steam and try to start the game again.

5 - If you have ReWSAD program or whatever it's called or any similar program installed or opened that is used to change the input, try deleting it. CoD Software sees any input changing programs as a cheating software and blocks CoD HQ from launching.

I'll keep adding more info to this post as I go deeper into some troubles. So far this helpes at least 6 people, who asked for help.

Adding: sometimes installing game fresh to the SSD also works wit some problems, but looking at the "bootstraper.txt" is a must

6 - [17148] 09/01/24 11:16:52: Failed to open service atvi-randgrid_sr (1060)

'll leave you two possible solutions, here's first one:
Go to SteamLibrary folder, properties, security tab, click advanced, click add permission, add to "everyone" and run the game

Second:
-Close Steam
-open registry ediotr
-delete this registry
Computer\HKEY_CURRENT_USER\Software\Valve
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Valve
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Valve
-run steam
-run COD

7 - [4144] 09/01/24 11:46:44: Failed to start service (647)

enable "device security" in windows security and restart the PC

8 - Delete GoodbyeDPI

"error code 0xC000001D (0) N" possible solutions:

9 - missing or broken Windows files:

Press win+s , type cmd, run cmd, paste:

dism /online /cleanup-image /restorehealth

wait for the end, then paste:

SFC/scannow

Restart PC

10 - 1: Restart your computer 2: Press delete at the right moment to enter BIOS while your computer is booting 3: Scroll through the settings and you'll find AES extension 4: Enable it 5: Play Game

11 - Some motherboads need an update to enable AES-NI. Do at your own risk. Also, game needs AVX2 ( NOT CONFIRMED YET)

12 - ANY WINDOWS OR Microsoft OFFICE CRACKING programs will get anti-cheat crash the game without a log or message. Delete them.

Update: with tries and errors we figured that BLACK OPS 6 requires your CPU to support AVX2. However, Warzone, Cold War, Modern warfare 1-3 doesn't need AVX2, so for those games fixes above should help

[𝕸𝖎𝖈]

idk if the devs even know about this issue.

[nurlan2007944]

𝕸𝖎𝖈 eredeti hozzászólása:

idk if the devs even know about this issue.

despite overall situation, I really don't know. I hope they will try to fix their anti-cheat behavior towards apps that are not even game related. Because so far, apart from some obvious problems like Visaul C++, wrong path, failed to open randgrid.sys etc, in 99% cases there are some background processes that mess things up for anti-cheat.

[R4VI4TOR]

𝕸𝖎𝖈 eredeti hozzászólása:

idk if the devs even know about this issue.

let them know on x !!!

x.com/codupdates
x.com/treyarch

[nurlan2007944]

R4VI4TOR eredeti hozzászólása:

𝕸𝖎𝖈 eredeti hozzászólása:

idk if the devs even know about this issue.

let them know on x !!!

x.com/codupdates
x.com/treyarch

If someone reports problems, please for the love of God, include this big post, maybe we'll get some help with some problems.

[Mirarsdayo]

короче говоря, если у вас проц без поддержки AVX2, сорян челы, покупайте проц с AVX2, если у вас проц с AVX2, челы, чистите комп от всякого кала

[Vick]

I think that the problem came from the last update for bo6, let's wait for a patch in the next update.. For the moment no more warzone for me

[Mirarsdayo]

Vick eredeti hozzászólása:

I think that the problem came from the last update for bo6, let's wait for a patch in the next update.. For the moment no more warzone for me

its just, stupidity, people bought that crap for 70-100$, just for the early beta, BUT, OOOPS

[Vick]

Someone as an info on when it will be fix?

[Mirarsdayo]

Vick eredeti hozzászólása:

Someone as an info on when it will be fix?

september 6th will be open beta for everyone, wait until then, maybe it will fixed

[nurlan2007944]

Updated

[Vick]

Still not working :P

[nurlan2007944]

Vick eredeti hozzászólása:

Still not working :P

Cool, need more info. bootstrapper.txt, crash log, model of CPU

[Vick]

bootstrapper.txt :
[16492] 09/05/24 09:15:21: Failed to start service (1450).
[20484] 09/05/24 10:35:33: Failed to start service (1450).

Model of CPU:
Intel(R) Core(TM) i5-9600K CPU @ 3.70GHz 3.70 GHz

Model of GC:
NVIDIA GeForce RTX3060

Crash log:
Diagnostics
---------------

Windows Error Reporting:
+++ WER0 +++:
Détecteur d'erreurs 1608445795356976265, type 5
Nom d’événement : RADAR_PRE_LEAK_64
Réponse : Non disponible
ID de CAB : 0

Signature du problème :
P1 : SearchApp.exe
P2 : 10.0.19041.4717
P3 : 10.0.19045.2.0.0
P4 :
P5 :
P6 :
P7 :
P8 :
P9 :
P10 :

Fichiers joints :
/?/C:/Users/Admin/AppData/Local/Temp/RDR8562.tmp/empty.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8572.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER85A2.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER85CC.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER85EC.tmp.txt

Ces fichiers sont peut-être disponibles ici :


Symbole d’analyse :
Nouvelle recherche de la solution : 0
ID de rapport : f8d6c170-3d40-422a-8b38-e9502b2f2729
Statut du rapport : 268435456
Récipient avec hachage : 9f2ca721d6e7a543065258edd0b92489
GUID CAB :0
+++ WER1 +++:
Détecteur d'erreurs 1543289430405120714, type 5
Nom d’événement : RADAR_PRE_LEAK_64
Réponse : Non disponible
ID de CAB : 0

Signature du problème :
P1 : DeadByDaylight-Win64-Shipping.exe
P2 : 5.2.1.0
P3 : 10.0.19045.2.0.0
P4 :
P5 :
P6 :
P7 :
P8 :
P9 :
P10 :

Fichiers joints :
/?/C:/Users/Admin/AppData/Local/Temp/RDRD286.tmp/empty.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD2A7.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD334.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD380.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD3A1.tmp.txt

Ces fichiers sont peut-être disponibles ici :


Symbole d’analyse :
Nouvelle recherche de la solution : 0
ID de rapport : 8258c579-a528-418e-9a85-7f5305660713
Statut du rapport : 268435456
Récipient avec hachage : 829c5bd9f76de9a8956add8f6ce982ca
GUID CAB :0
+++ WER2 +++:
Détecteur d'erreurs , type 0
Nom d’événement : PCA2
Réponse : Non disponible
ID de CAB : 0

Signature du problème :
P1 : Call of Duty Launcher.exe
P2 : 1.18.10.3140
P3 : Call of Duty Launcher
P4 : Call of Duty Launcher
P5 : Blizzard Entertainment
P6 : 100
P7 : 0
P8 :
P9 :
P10 :

Fichiers joints :
\\?\C:\Users\Admin\AppData\Local\Temp\PCW4D05.tmp
\\?\C:\Users\Admin\AppData\Local\Temp\ACG4D16.tmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4D74.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4DB4.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4DB1.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4DD1.tmp.txt

Ces fichiers sont peut-être disponibles ici :
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_Call of Duty Lau_bd68d3614f9ba4a94e27e24bc1c82fcd86c37dd_00000000_0b01eaa2-f2cb-4793-8b43-01077de6bb91

Symbole d’analyse :
Nouvelle recherche de la solution : 0
ID de rapport : 0b01eaa2-f2cb-4793-8b43-01077de6bb91
Statut du rapport : 2147491840
Récipient avec hachage :
GUID CAB :0
+++ WER3 +++:
Détecteur d'erreurs 1679484014129259688, type 5
Nom d’événement : CLR20r3
Réponse : Non disponible
ID de CAB : 0

Signature du problème :
P1 : RzWizard.exe
P2 : 1.0.6.1000
P3 : 56f20403
P4 : System.Xml
P5 : 4.8.9037.0
P6 : 62b63b42
P7 : b84
P8 : 27
P9 : IOIBMURHYNRXKW0ZXKYRVFN0BOYYUFOW
P10 :

Fichiers joints :
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4E3F.tmp.WERInternalMetadata.xml

Ces fichiers sont peut-être disponibles ici :
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_RzWizard.exe_33a8e7963e359b435337e6df79fd95d8c7d281e_1b9da650_5e892c09-b4d3-4333-a82b-e1e113088bd1

Symbole d’analyse :
Nouvelle recherche de la solution : 0
ID de rapport : 60d550a7-0de0-4655-9c8c-82b6a69279cf
Statut du rapport : 268435462
Récipient avec hachage : 46a4dc53981015a4b74eb9d0041f24a8
GUID CAB :0
+++ WER4 +++:
Détecteur d'erreurs , type 0
Nom d’événement : CLR20r3
Réponse : Non disponible
ID de CAB : 0

And more under this ♥♥♥♥

I already try like everything i found on internet, here, uninstalle and nothing work :P

[waiting at home]

nurlan2007944 eredeti hozzászólása:

Hello, since the Black Ops 6 Beta dropped, some people started to have some problem (hardware, software etc). I've made a big thread with possible solution to some problems, however it's really hard to figure out some solutions, especially "error code 0xC000001D (0) N" and "Success launching "cod.exe hdeyguxs3zaumvlgvybm2vyc"", which isn't even a problem on CoD side. Please, use info down below if have any problems. Funny part is that I don't even own CoD BO6.

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

Edit: before you ask for help, please, check two things:

Call of Duty crash log:

C / User / you / AppData / Local / Activision / Call of Duty / Crash_reports /

Sort files by date and open the most recent file with WinRAR or 7-Zip. Inside you will find a file called dxdiag_oncrash.txt, open it, then scroll down to "Diagnostics". Under diagnostics section there will be a line called "Problem Signature", under it, you will see what program or process causes the crash. I hope this will help.

And for Call of Duty HQ, there is a main folder and file called "bootstraper.txt or . log"

———————————

I've got like 20+ friend requests because I can help with some crashes. I've decided to make a big post to save some time for the people, myself included.

IF YOUR CoD HQ CRASHES WITHOUT ANY MESSAGE OR MID-GAME OR WON'T EVEN START, try this:
0 - https://steamcommunity.com/app/1938090/discussions/0/4757577823502590346/

1 - open your main CoD HQ folder, find file "bootstraper.txt" (or .log), open it and watch the last line. If it says "invalid install path", put your STEAM folder into Program Files x86 folder (in french it's called Programmes (x86)) on your system drive. It's and old bug, but it should help.

2 - if your "bootstraper.txt" file says "failed to open randgrid.sys", you have two option:

2.1 - move "randgrid.sys" from your CoD HQ folder to the path it says in the "bootstraper.txt".

Example: your "randgrid.sys" file is the path: c/ steam / steam apps / common / CoD HQ /, but last line in the "bootstraper.txt" says "Failed to open C: / users / UserName / Downloads / Steam / steamapps / common / Call of Duty HQ /". You need to put the file into folder where "bootstraper.txt" tried to find it.

2.2 - If it doesn't help, move entire CoD HQ folder into the folder where "bootstraper.txt" tries to find it. Or just delete the whole game and install into the folder, where "bootstraper.txt" wants to find the "randgrid.sys" file.

3 - If "bootstraper.txt" says "open successfully" and there are some numbers and letters, on your desktop press START - WINDOWS SETTINGS - APPS / PROGRAMS , find Microsoft Visual C++ 2015-2022, you may have 1-4 programs named like this. Click on each one and then click "REPAIR". Once everything is repaired, reboot PC.

4 - If "bootstraper.txt" says nothing and your your CoD HQ doesn't start or crashing, DELETE COD HQ FOLDER from the "Documents" folder. Then validate files integrity through Steam and try to start the game again.

5 - If you have ReWSAD program or whatever it's called or any similar program installed or opened that is used to change the input, try deleting it. CoD Software sees any input changing programs as a cheating software and blocks CoD HQ from launching.

I'll keep adding more info to this post as I go deeper into some troubles. So far this helpes at least 6 people, who asked for help.

Adding: sometimes installing game fresh to the SSD also works wit some problems, but looking at the "bootstraper.txt" is a must

6 - [17148] 09/01/24 11:16:52: Failed to open service atvi-randgrid_sr (1060)

'll leave you two possible solutions, here's first one:
Go to SteamLibrary folder, properties, security tab, click advanced, click add permission, add to "everyone" and run the game

Second:
-Close Steam
-open registry ediotr
-delete this registry
Computer\HKEY_CURRENT_USER\Software\Valve
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Valve
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Valve
-run steam
-run COD

7 - [4144] 09/01/24 11:46:44: Failed to start service (647)

enable "device security" in windows security and restart the PC

8 - Delete GoodbyeDPI

"error code 0xC000001D (0) N" possible solutions:

9 - missing or broken Windows files:

Press win+s , type cmd, run cmd, paste:

dism /online /cleanup-image /restorehealth

wait for the end, then paste:

SFC/scannow

Restart PC

10 - 1: Restart your computer 2: Press delete at the right moment to enter BIOS while your computer is booting 3: Scroll through the settings and you'll find AES extension 4: Enable it 5: Play Game

11 - Some motherboads need an update to enable AES-NI. Do at your own risk. Also, game needs AVX2 ( NOT CONFIRMED YET)

12 - ANY WINDOWS OR Microsoft OFFICE CRACKING programs will get anti-cheat crash the game without a log or message. Delete them.

Update: with tries and errors we figured that BLACK OPS 6 requires your CPU to support AVX2. However, Warzone, Cold War, Modern warfare 1-3 doesn't need AVX2, so for those games fixes above should help

I had problem [1337 (N) crash] and i fix them by disable SVM in BIOS (CPU Virtualization AMD).

Disabled CPU C-State may cause this problem too (need to set Enabled).

This is such nonsense. To run docker, I need virtualization to work, but I need to turn it off to play.

By the way, the game was able to start in the main menu after turning on VSync via a file. Then I turned on the metrics in the game and saw the CPU time : 5.983472859+E14.

After that, I began to guess what the real problem was and used the solution method described above.

[Mirarsdayo]

waiting at home eredeti hozzászólása:

nurlan2007944 eredeti hozzászólása:

Hello, since the Black Ops 6 Beta dropped, some people started to have some problem (hardware, software etc). I've made a big thread with possible solution to some problems, however it's really hard to figure out some solutions, especially "error code 0xC000001D (0) N" and "Success launching "cod.exe hdeyguxs3zaumvlgvybm2vyc"", which isn't even a problem on CoD side. Please, use info down below if have any problems. Funny part is that I don't even own CoD BO6.

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

Edit: before you ask for help, please, check two things:

Call of Duty crash log:

C / User / you / AppData / Local / Activision / Call of Duty / Crash_reports /

Sort files by date and open the most recent file with WinRAR or 7-Zip. Inside you will find a file called dxdiag_oncrash.txt, open it, then scroll down to "Diagnostics". Under diagnostics section there will be a line called "Problem Signature", under it, you will see what program or process causes the crash. I hope this will help.

And for Call of Duty HQ, there is a main folder and file called "bootstraper.txt or . log"

———————————

I've got like 20+ friend requests because I can help with some crashes. I've decided to make a big post to save some time for the people, myself included.

IF YOUR CoD HQ CRASHES WITHOUT ANY MESSAGE OR MID-GAME OR WON'T EVEN START, try this:
0 - https://steamcommunity.com/app/1938090/discussions/0/4757577823502590346/

1 - open your main CoD HQ folder, find file "bootstraper.txt" (or .log), open it and watch the last line. If it says "invalid install path", put your STEAM folder into Program Files x86 folder (in french it's called Programmes (x86)) on your system drive. It's and old bug, but it should help.

2 - if your "bootstraper.txt" file says "failed to open randgrid.sys", you have two option:

2.1 - move "randgrid.sys" from your CoD HQ folder to the path it says in the "bootstraper.txt".

Example: your "randgrid.sys" file is the path: c/ steam / steam apps / common / CoD HQ /, but last line in the "bootstraper.txt" says "Failed to open C: / users / UserName / Downloads / Steam / steamapps / common / Call of Duty HQ /". You need to put the file into folder where "bootstraper.txt" tried to find it.

2.2 - If it doesn't help, move entire CoD HQ folder into the folder where "bootstraper.txt" tries to find it. Or just delete the whole game and install into the folder, where "bootstraper.txt" wants to find the "randgrid.sys" file.

3 - If "bootstraper.txt" says "open successfully" and there are some numbers and letters, on your desktop press START - WINDOWS SETTINGS - APPS / PROGRAMS , find Microsoft Visual C++ 2015-2022, you may have 1-4 programs named like this. Click on each one and then click "REPAIR". Once everything is repaired, reboot PC.

4 - If "bootstraper.txt" says nothing and your your CoD HQ doesn't start or crashing, DELETE COD HQ FOLDER from the "Documents" folder. Then validate files integrity through Steam and try to start the game again.

5 - If you have ReWSAD program or whatever it's called or any similar program installed or opened that is used to change the input, try deleting it. CoD Software sees any input changing programs as a cheating software and blocks CoD HQ from launching.

I'll keep adding more info to this post as I go deeper into some troubles. So far this helpes at least 6 people, who asked for help.

Adding: sometimes installing game fresh to the SSD also works wit some problems, but looking at the "bootstraper.txt" is a must

6 - [17148] 09/01/24 11:16:52: Failed to open service atvi-randgrid_sr (1060)

'll leave you two possible solutions, here's first one:
Go to SteamLibrary folder, properties, security tab, click advanced, click add permission, add to "everyone" and run the game

Second:
-Close Steam
-open registry ediotr
-delete this registry
Computer\HKEY_CURRENT_USER\Software\Valve
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Valve
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Valve
-run steam
-run COD

7 - [4144] 09/01/24 11:46:44: Failed to start service (647)

enable "device security" in windows security and restart the PC

8 - Delete GoodbyeDPI

"error code 0xC000001D (0) N" possible solutions:

9 - missing or broken Windows files:

Press win+s , type cmd, run cmd, paste:

dism /online /cleanup-image /restorehealth

wait for the end, then paste:

SFC/scannow

Restart PC

10 - 1: Restart your computer 2: Press delete at the right moment to enter BIOS while your computer is booting 3: Scroll through the settings and you'll find AES extension 4: Enable it 5: Play Game

11 - Some motherboads need an update to enable AES-NI. Do at your own risk. Also, game needs AVX2 ( NOT CONFIRMED YET)

12 - ANY WINDOWS OR Microsoft OFFICE CRACKING programs will get anti-cheat crash the game without a log or message. Delete them.

Update: with tries and errors we figured that BLACK OPS 6 requires your CPU to support AVX2. However, Warzone, Cold War, Modern warfare 1-3 doesn't need AVX2, so for those games fixes above should help

I had problem [1337 (N) crash] and i fix them by disable SVM in BIOS (CPU Virtualization AMD).

Disabled CPU C-State may cause this problem too (need to set Enabled).

This is such nonsense. To run docker, I need virtualization to work, but I need to turn it off to play.

By the way, the game was able to start in the main menu after turning on VSync via a file. Then I turned on the metrics in the game and saw the CPU time : 5.983472859+E14.

After that, I began to guess what the real problem was and used the solution method described above.

I guees your COD HQ doesnt working cuz the virtualization?