To Ubisoft developers, here is the memory.dmp output is below. This is the same on all 10th rtx 3080 users who are getting BSOD as well as some AMD users. And the system restarts when bsod happens. This dump log will help ubi developers to fix the problem quickly, you guys can patch it and release an update please. Since it is not possible to submit a ticket, i just share it here. The bsod happens randomly while playing the game, sometimes every 15 minutes, sometimes after 4 hours.

My Specs: 10900K/ 3080 RTX / 32GB / Win10 Pro / Motherboard Name MSI MAG Z490 Tomahawk (MS-7C80) / Nvidia GPU Driver ver. 472.12

@Ubi-Caliburn @Ubi-Borealis @ubi-mark @UBI-VIRAL @Ubi-Alien @Ubi-Cuddles @Ubi-Deta @Ubi-Akatsirin @Ubi-AJ @Ubi-Daffodil @Ubi-Doh

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffff8047bec4a20, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8043a68053e, address which referenced memory

Debugging Details:
------------------


KEY_VALUES_STRING: 1

 Key : Analysis.CPU.mSec
 Value: 1390

 Key : Analysis.DebugAnalysisManager
 Value: Create

 Key : Analysis.Elapsed.mSec
 Value: 1390

 Key : Analysis.Init.CPU.mSec
 Value: 405

 Key : Analysis.Init.Elapsed.mSec
 Value: 259397

 Key : Analysis.Memory.CommitPeak.Mb
 Value: 83

 Key : WER.OS.Branch
 Value: vb_release

 Key : WER.OS.Timestamp
 Value: 2019-12-06T14:06:00Z

 Key : WER.OS.Version
 Value: 10.0.19041.1


BUGCHECK_CODE: a

BUGCHECK_P1: fffff8047bec4a20

BUGCHECK_P2: 2

BUGCHECK_P3: 8

BUGCHECK_P4: fffff8043a68053e

READ_ADDRESS: fffff8047bec4a20 

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: FarCry6.exe

TRAP_FRAME: ffffaa8be480ef60 -- (.trap 0xffffaa8be480ef60)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=ffffbe05ab636268
rdx=ffffbe05ab636268 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8043a68053e rsp=ffffaa8be480f0f0 rbp=ffffaa8be480f1b9
 r8=0000000000000000 r9=0000000000000000 r10=ffffad0080f82180
r11=ffffaa8be480f2b0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0   nv up ei ng nz ac pe cy
nt!KeWaitForMultipleObjects+0x22e:
fffff804`3a68053e 0f84ca030000 je  nt!KeWaitForMultipleObjects+0x5fe (fffff804`3a68090e) [br=0]
Resetting default scope

STACK_TEXT:  
ffffaa8b`e480ee18 fffff804`3a809169  : 00000000`0000000a fffff804`7bec4a20 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
ffffaa8b`e480ee20 fffff804`3a805469  : ffffad00`80f82100 ffffad00`80f8d540 ffffbe05`a821c080 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffaa8b`e480ef60 fffff804`3a68053e  : ffffbe05`00000000 00000000`00000000 00000000`00000800 00000000`00000000 : nt!KiPageFault+0x469
ffffaa8b`e480f0f0 fffff804`3aa6f600  : ffffaa8b`e480f4b0 00000000`00000001 ffffbe05`ac0926b0 fffff804`51443213 : nt!KeWaitForMultipleObjects+0x22e
ffffaa8b`e480f200 fffff804`3aa6f2d9  : 00000000`00000000 ffffad00`00000000 00000000`00000000 fffff804`3a6879e6 : nt!ObWaitForMultipleObjects+0x2f0
ffffaa8b`e480f700 fffff804`3a808bb5  : 00000000`00000000 00000000`00000000 ffffbe05`a821c080 fffff804`3aadadc0 : nt!NtWaitForMultipleObjects+0x119
ffffaa8b`e480f990 00007ffc`8bc4d8c4  : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
0000007f`85eff7c8 00000000`00000000  : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`8bc4d8c4


SYMBOL_NAME: nt!KeWaitForMultipleObjects+22e

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 22e

FAILURE_BUCKET_ID: AV_nt!KeWaitForMultipleObjects

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {0d335bc1-87c8-f4ad-8a69-d4d9985e727a}

Followup:  MachineOwner

@ubi-mark Seriously you guys need to fire the person who did the beta tests organization for this game in order to save ubisoft's future, its a disaster. The game results BSOD and restarts the whole PC without any windows 10 event logs or dump logs. 10900K and 32 GB ram with 3080 RTX crashes to bsod and restarts the system randomly in the game. Dont recommend me troubleshooting I already done all of them and I have the latest windows 10 with latest nvidia driver version. Instead recommend your developers to sit and work, because this is not a user computer issue, it is a shameful bug in the game. I will ask for a refund.

To Ubisoft developers, here is the memory.dmp output is below. This is the same on all 10th rtx 3080 users who are getting BSOD and the system restarts when it happens. This dump log will help you to fix the problem quickly, you guys can patch it and release an update in 10 minutes after you got what you need as below.

My Specs: 10900K/ 3080 RTX / 32GB / Win10 Pro / Motherboard Name MSI MAG Z490 Tomahawk (MS-7C80) / Nvidia GPU Driver ver. 472.12

@Ubi-Caliburn @Ubi-Borealis @ubi-mark @UBI-VIRAL @Ubi-Alien @Ubi-Cuddles @Ubi-Deta @Ubi-Akatsirin @Ubi-AJ @Ubi-Daffodil @Ubi-Doh


IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffff8047bec4a20, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8043a68053e, address which referenced memory

Debugging Details:
------------------


KEY_VALUES_STRING: 1

  Key : Analysis.CPU.mSec
  Value: 1390

  Key : Analysis.DebugAnalysisManager
  Value: Create

  Key : Analysis.Elapsed.mSec
  Value: 1390

  Key : Analysis.Init.CPU.mSec
  Value: 405

  Key : Analysis.Init.Elapsed.mSec
  Value: 259397

  Key : Analysis.Memory.CommitPeak.Mb
  Value: 83

  Key : WER.OS.Branch
  Value: vb_release

  Key : WER.OS.Timestamp
  Value: 2019-12-06T14:06:00Z

  Key : WER.OS.Version
  Value: 10.0.19041.1


BUGCHECK_CODE: a

BUGCHECK_P1: fffff8047bec4a20

BUGCHECK_P2: 2

BUGCHECK_P3: 8

BUGCHECK_P4: fffff8043a68053e

READ_ADDRESS: fffff8047bec4a20 

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: FarCry6.exe

TRAP_FRAME: ffffaa8be480ef60 -- (.trap 0xffffaa8be480ef60)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=ffffbe05ab636268
rdx=ffffbe05ab636268 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8043a68053e rsp=ffffaa8be480f0f0 rbp=ffffaa8be480f1b9
 r8=0000000000000000 r9=0000000000000000 r10=ffffad0080f82180
r11=ffffaa8be480f2b0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0     nv up ei ng nz ac pe cy
nt!KeWaitForMultipleObjects+0x22e:
fffff804`3a68053e 0f84ca030000  je   nt!KeWaitForMultipleObjects+0x5fe (fffff804`3a68090e) [br=0]
Resetting default scope

STACK_TEXT:  
ffffaa8b`e480ee18 fffff804`3a809169   : 00000000`0000000a fffff804`7bec4a20 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
ffffaa8b`e480ee20 fffff804`3a805469   : ffffad00`80f82100 ffffad00`80f8d540 ffffbe05`a821c080 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffaa8b`e480ef60 fffff804`3a68053e   : ffffbe05`00000000 00000000`00000000 00000000`00000800 00000000`00000000 : nt!KiPageFault+0x469
ffffaa8b`e480f0f0 fffff804`3aa6f600   : ffffaa8b`e480f4b0 00000000`00000001 ffffbe05`ac0926b0 fffff804`51443213 : nt!KeWaitForMultipleObjects+0x22e
ffffaa8b`e480f200 fffff804`3aa6f2d9   : 00000000`00000000 ffffad00`00000000 00000000`00000000 fffff804`3a6879e6 : nt!ObWaitForMultipleObjects+0x2f0
ffffaa8b`e480f700 fffff804`3a808bb5   : 00000000`00000000 00000000`00000000 ffffbe05`a821c080 fffff804`3aadadc0 : nt!NtWaitForMultipleObjects+0x119
ffffaa8b`e480f990 00007ffc`8bc4d8c4   : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
0000007f`85eff7c8 00000000`00000000   : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`8bc4d8c4


SYMBOL_NAME: nt!KeWaitForMultipleObjects+22e

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 22e

FAILURE_BUCKET_ID: AV_nt!KeWaitForMultipleObjects

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {0d335bc1-87c8-f4ad-8a69-d4d9985e727a}

Followup:   MachineOwner
---------

@azaraqps4 Same here. 10900K / 3080 rtx / 32 gb / win10pro. Everything is updated and latest, the game crashes randomly and when it happens, it restarts the entire system. This is actually BSOD but it crashes so hard that even windows unable to show the blue screen.

I have the same problem. BSOD and pc restarts, happens randomly in the game.

10900K / 3080 RTX / 32 GB Ram / Windows 10 latest.

@yarok63 The BSOD is a bug in the game, the solutions provided on this thread is mostly for luncher and crash to desktop. The bsod remains and people who think that it is fixed after changing few setting is just not correct at all. The BSOD does not happen always which leads to think that the user is fixed it. Sometimes it happens after 4 hours play, sometimes 30 minutes, it changes. A game fix/update required by the developers. I have created a thread for the developers with the memory dump, they can fix it if they read it of course. Check this thread https://discussions.ubisoft.com/topic/112537/far-cry-6-bsod-pc-restarts-memory-dump-for-developers?lang=en-US

Installing the game and epic luncher together to second M.2 drive fixes the hard crash(bsod) but crash to desktop continues and happens randomly, at least it is crash to desktop without pc restart. So anyone who have hard crash or bsod, should delete the game from epic luncher/store first and then delete epic luncher itself from windows programs list, then delete the ubiconnect as well. Now install epic luncher and and the game on the second M.2 drive. Make sure nothing installed to drive C and c:program files(x86) except ubiconnect.

@ftkanizawa I did try your method, I do run the game from the bin_plus with admin mode and it still crashes to desktop, sometimes after 30 mins and sometimes after 3 hours of play.

To all people who get BSOD, I was able to fix the BSOD, actually I was able to change it to a crash to desktop instead of complete bsod and pc restart.

Here is what I did:
The game was installed in c drive under the c:program files (x86). I uninstalled the ubi connect first from the windows uninstall programs screen, then I uninstalled the game from the Epic Games Launcher, click 3 dots near the game and choose uninstall. Then uninstalled the Epic Games Launcher itself from the windows programs screen.

Then I installed Epic Games Launcher to the second mk2 disk I have, which is disk d: and installed the game with Epic Games Launcher to d: drive under the Epic Games Launcher folder.

So short answer is I just uninstalled everything including ubiconnect and I installed everything including game to the second disk d:. This is fixed BSOD for me, it is now crashing to desktop instead of BSOD at least and tested it for 3 days, I confirm my bsods are turned to crash to desktop this way.

@yarok63 The BSOD is a bug in the game, the solutions provided on this thread is mostly for luncher and crash to desktop. The bsod remains and people who think that it is fixed after changing few setting is just not correct at all. The BSOD does not happen always which leads to think that the user is fixed it. Sometimes it happens after 4 hours play, sometimes 30 minutes, it changes. A game fix/update required by the developers. I have created a thread for the developers with the memory dump, they can fix it if they read it of course. Check this thread https://discussions.ubisoft.com/topic/112537/far-cry-6-bsod-pc-restarts-memory-dump-for-developers?lang=en-US

To Ubisoft developers, here is the memory.dmp output is below. This is the same on all 10th rtx 3080 users who are getting BSOD as well as some AMD users. And the system restarts when bsod happens. This dump log will help ubi developers to fix the problem quickly, you guys can patch it and release an update please. Since it is not possible to submit a ticket, i just share it here. The bsod happens randomly while playing the game, sometimes every 15 minutes, sometimes after 4 hours.

My Specs: 10900K/ 3080 RTX / 32GB / Win10 Pro / Motherboard Name MSI MAG Z490 Tomahawk (MS-7C80) / Nvidia GPU Driver ver. 472.12

@Ubi-Caliburn @Ubi-Borealis @ubi-mark @UBI-VIRAL @Ubi-Alien @Ubi-Cuddles @Ubi-Deta @Ubi-Akatsirin @Ubi-AJ @Ubi-Daffodil @Ubi-Doh

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffff8047bec4a20, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8043a68053e, address which referenced memory

Debugging Details:
------------------


KEY_VALUES_STRING: 1

 Key : Analysis.CPU.mSec
 Value: 1390

 Key : Analysis.DebugAnalysisManager
 Value: Create

 Key : Analysis.Elapsed.mSec
 Value: 1390

 Key : Analysis.Init.CPU.mSec
 Value: 405

 Key : Analysis.Init.Elapsed.mSec
 Value: 259397

 Key : Analysis.Memory.CommitPeak.Mb
 Value: 83

 Key : WER.OS.Branch
 Value: vb_release

 Key : WER.OS.Timestamp
 Value: 2019-12-06T14:06:00Z

 Key : WER.OS.Version
 Value: 10.0.19041.1


BUGCHECK_CODE: a

BUGCHECK_P1: fffff8047bec4a20

BUGCHECK_P2: 2

BUGCHECK_P3: 8

BUGCHECK_P4: fffff8043a68053e

READ_ADDRESS: fffff8047bec4a20 

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: FarCry6.exe

TRAP_FRAME: ffffaa8be480ef60 -- (.trap 0xffffaa8be480ef60)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=ffffbe05ab636268
rdx=ffffbe05ab636268 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8043a68053e rsp=ffffaa8be480f0f0 rbp=ffffaa8be480f1b9
 r8=0000000000000000 r9=0000000000000000 r10=ffffad0080f82180
r11=ffffaa8be480f2b0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0   nv up ei ng nz ac pe cy
nt!KeWaitForMultipleObjects+0x22e:
fffff804`3a68053e 0f84ca030000 je  nt!KeWaitForMultipleObjects+0x5fe (fffff804`3a68090e) [br=0]
Resetting default scope

STACK_TEXT:  
ffffaa8b`e480ee18 fffff804`3a809169  : 00000000`0000000a fffff804`7bec4a20 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
ffffaa8b`e480ee20 fffff804`3a805469  : ffffad00`80f82100 ffffad00`80f8d540 ffffbe05`a821c080 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffaa8b`e480ef60 fffff804`3a68053e  : ffffbe05`00000000 00000000`00000000 00000000`00000800 00000000`00000000 : nt!KiPageFault+0x469
ffffaa8b`e480f0f0 fffff804`3aa6f600  : ffffaa8b`e480f4b0 00000000`00000001 ffffbe05`ac0926b0 fffff804`51443213 : nt!KeWaitForMultipleObjects+0x22e
ffffaa8b`e480f200 fffff804`3aa6f2d9  : 00000000`00000000 ffffad00`00000000 00000000`00000000 fffff804`3a6879e6 : nt!ObWaitForMultipleObjects+0x2f0
ffffaa8b`e480f700 fffff804`3a808bb5  : 00000000`00000000 00000000`00000000 ffffbe05`a821c080 fffff804`3aadadc0 : nt!NtWaitForMultipleObjects+0x119
ffffaa8b`e480f990 00007ffc`8bc4d8c4  : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
0000007f`85eff7c8 00000000`00000000  : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`8bc4d8c4


SYMBOL_NAME: nt!KeWaitForMultipleObjects+22e

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 22e

FAILURE_BUCKET_ID: AV_nt!KeWaitForMultipleObjects

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {0d335bc1-87c8-f4ad-8a69-d4d9985e727a}

Followup:  MachineOwner

To Ubisoft developers, here is the memory.dmp output is below. This is the same on all 10th rtx 3080 users who are getting BSOD and the system restarts when it happens. This dump log will help you to fix the problem quickly, you guys can patch it and release an update in 10 minutes after you got what you need as below.

My Specs: 10900K/ 3080 RTX / 32GB / Win10 Pro / Motherboard Name MSI MAG Z490 Tomahawk (MS-7C80) / Nvidia GPU Driver ver. 472.12

@Ubi-Caliburn @Ubi-Borealis @ubi-mark @UBI-VIRAL @Ubi-Alien @Ubi-Cuddles @Ubi-Deta @Ubi-Akatsirin @Ubi-AJ @Ubi-Daffodil @Ubi-Doh


IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffff8047bec4a20, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8043a68053e, address which referenced memory

Debugging Details:
------------------


KEY_VALUES_STRING: 1

  Key : Analysis.CPU.mSec
  Value: 1390

  Key : Analysis.DebugAnalysisManager
  Value: Create

  Key : Analysis.Elapsed.mSec
  Value: 1390

  Key : Analysis.Init.CPU.mSec
  Value: 405

  Key : Analysis.Init.Elapsed.mSec
  Value: 259397

  Key : Analysis.Memory.CommitPeak.Mb
  Value: 83

  Key : WER.OS.Branch
  Value: vb_release

  Key : WER.OS.Timestamp
  Value: 2019-12-06T14:06:00Z

  Key : WER.OS.Version
  Value: 10.0.19041.1


BUGCHECK_CODE: a

BUGCHECK_P1: fffff8047bec4a20

BUGCHECK_P2: 2

BUGCHECK_P3: 8

BUGCHECK_P4: fffff8043a68053e

READ_ADDRESS: fffff8047bec4a20 

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: FarCry6.exe

TRAP_FRAME: ffffaa8be480ef60 -- (.trap 0xffffaa8be480ef60)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=ffffbe05ab636268
rdx=ffffbe05ab636268 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8043a68053e rsp=ffffaa8be480f0f0 rbp=ffffaa8be480f1b9
 r8=0000000000000000 r9=0000000000000000 r10=ffffad0080f82180
r11=ffffaa8be480f2b0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0     nv up ei ng nz ac pe cy
nt!KeWaitForMultipleObjects+0x22e:
fffff804`3a68053e 0f84ca030000  je   nt!KeWaitForMultipleObjects+0x5fe (fffff804`3a68090e) [br=0]
Resetting default scope

STACK_TEXT:  
ffffaa8b`e480ee18 fffff804`3a809169   : 00000000`0000000a fffff804`7bec4a20 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
ffffaa8b`e480ee20 fffff804`3a805469   : ffffad00`80f82100 ffffad00`80f8d540 ffffbe05`a821c080 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffaa8b`e480ef60 fffff804`3a68053e   : ffffbe05`00000000 00000000`00000000 00000000`00000800 00000000`00000000 : nt!KiPageFault+0x469
ffffaa8b`e480f0f0 fffff804`3aa6f600   : ffffaa8b`e480f4b0 00000000`00000001 ffffbe05`ac0926b0 fffff804`51443213 : nt!KeWaitForMultipleObjects+0x22e
ffffaa8b`e480f200 fffff804`3aa6f2d9   : 00000000`00000000 ffffad00`00000000 00000000`00000000 fffff804`3a6879e6 : nt!ObWaitForMultipleObjects+0x2f0
ffffaa8b`e480f700 fffff804`3a808bb5   : 00000000`00000000 00000000`00000000 ffffbe05`a821c080 fffff804`3aadadc0 : nt!NtWaitForMultipleObjects+0x119
ffffaa8b`e480f990 00007ffc`8bc4d8c4   : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
0000007f`85eff7c8 00000000`00000000   : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`8bc4d8c4


SYMBOL_NAME: nt!KeWaitForMultipleObjects+22e

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 22e

FAILURE_BUCKET_ID: AV_nt!KeWaitForMultipleObjects

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {0d335bc1-87c8-f4ad-8a69-d4d9985e727a}

Followup:   MachineOwner
---------

@azaraqps4 Same here. 10900K / 3080 rtx / 32 gb / win10pro. Everything is updated and latest, the game crashes randomly and when it happens, it restarts the entire system. This is actually BSOD but it crashes so hard that even windows unable to show the blue screen.

I have the same problem. BSOD and pc restarts, happens randomly in the game.

10900K / 3080 RTX / 32 GB Ram / Windows 10 latest.

@ubi-mark Seriously you guys need to fire the person who did the beta tests organization for this game in order to save ubisoft's future, its a disaster. The game results BSOD and restarts the whole PC without any windows 10 event logs or dump logs. 10900K and 32 GB ram with 3080 RTX crashes to bsod and restarts the system randomly in the game. Dont recommend me troubleshooting I already done all of them and I have the latest windows 10 with latest nvidia driver version. Instead recommend your developers to sit and work, because this is not a user computer issue, it is a shameful bug in the game. I will ask for a refund.