8 players for Countdown is terrible. Talk about not understanding the player demographic.

I've got work, I've got kids, I've got other hobbies. Demographics shows that most game players have work, have kids, have other hobbies.

I don't need another thing that requires coordination and scheduling across 8 people after coordinating and scheduling work, kids, and hobbies. I don't have the patience on my fun time to deal with a pick-up group that abjectly fails -- which, in my experience, is a high percentage of the time.

The game mode itself sounds really cool. I really liked Survival in Division 1, so the prospect of a timed event I could just sit down, pick up, and play through _with 1-3 more people_ sounds really fun. There's no way it's happening if it requires 8.

It mystifies me that this even made it through design review. I'd recommend firing the product owners that are that out of touch with the player base demographics. I'm not sure how that much development time was justified for something that a very small fraction of players will ever see.

@ubi-theberry

1) Yes, the system meets the game's requirements
2) Yes, I keep Windows up-to-date.
3) No, I will never run the game with administrator rights. (Note that the exception trace in the post above indicates a problem with the _game_, not with the access rights.)
4) Yes, I did verify the game files.
5) Yes, I ensure my graphics card drivers are up-to-date. WHQL drivers for the past few years of playing this game and it has hung/crashed like this sporadically for that entire time.
6) I terminate all background applications prior to playing the game.

There appears to be no way for me to attach DxDiag or MSInfo output to this post. Attempting to drag and drop the files yields the error "You do not have the privileges to perform this action" from the forums.

I've had spurious crashes on the PC version of Division 2 on and off over the past couple of years, but (somewhat infuriatingly) I can get it to happen "reasonably consistently" near the Hunter that drops the Specter Mask.

Got fed up and discovered the crash dumps in %appdata%/../Local/Temp, grabbed WinDbg, and got the exception trace. Ubisoft, why you gotta be writing to a null pointer?!?

Unfortunately "TheDivision2+0x192ef4" isn't particularly useful to me. Maybe you guys can track this problem down with the real source/executable/debugger?

If there is anything else I can do to provide additional information please let me know. Like I said, it happens pretty consistently around where the Hunter is that drops the Specter Mask. I've had it crash before I've triggered the Hunter, I've had it crash *after* I've triggered the hunter, and sometimes it doesn't crash at all throughout the entire Hunter encounter.

EXCEPTION_RECORD:  (.exr -1)
ExceptionAddress: 00007ff709152ef4 (TheDivision2+0x0000000000192ef4)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000001
   Parameter[1]: 0000000000000000
Attempt to write to address 0000000000000000

PROCESS_NAME:  TheDivision2.exe

WRITE_ADDRESS:  0000000000000000 

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR:  c0000005

EXCEPTION_PARAMETER1:  0000000000000001

EXCEPTION_PARAMETER2:  0000000000000000

STACK_TEXT:  
00000037`38ffe8b8 00007ff7`091f6cad     : 002d0000`1700000c 00000000`00000000 00000000`00000037 00000000`00000040 : TheDivision2+0x192ef4
00000037`38ffe8c0 002d0000`1700000c     : 00000000`00000000 00000000`00000037 00000000`00000040 00007ff7`0ee8ab50 : TheDivision2+0x236cad
00000037`38ffe8c8 00000000`00000000     : 00000000`00000037 00000000`00000040 00007ff7`0ee8ab50 00007ff7`0924a902 : 0x002d0000`1700000c


SYMBOL_NAME:  TheDivision2+192ef4

MODULE_NAME: TheDivision2

IMAGE_NAME:  TheDivision2.exe

STACK_COMMAND:  ~31s; .ecxr ; kb

FAILURE_BUCKET_ID:  NULL_POINTER_WRITE_c0000005_TheDivision2.exe!Unknown

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

8 players for Countdown is terrible. Talk about not understanding the player demographic.

I've got work, I've got kids, I've got other hobbies. Demographics shows that most game players have work, have kids, have other hobbies.

I don't need another thing that requires coordination and scheduling across 8 people after coordinating and scheduling work, kids, and hobbies. I don't have the patience on my fun time to deal with a pick-up group that abjectly fails -- which, in my experience, is a high percentage of the time.

The game mode itself sounds really cool. I really liked Survival in Division 1, so the prospect of a timed event I could just sit down, pick up, and play through _with 1-3 more people_ sounds really fun. There's no way it's happening if it requires 8.

It mystifies me that this even made it through design review. I'd recommend firing the product owners that are that out of touch with the player base demographics. I'm not sure how that much development time was justified for something that a very small fraction of players will ever see.