Blue screen while playing overwatch

Ok Brandon I had a gut feeling re the RAM anyway from this

Code:

DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 0000000000000006, IRP passed to IoCompleteRequest contains invalid status
Arg2: 0000000000000103, the status
Arg3: fffff9808822cdc0, the IRP
Arg4: 0000000000000000

The main theme of things was or seemed to revolving around that graphics driver - which if I were you still keep in mind and again if the budget is ok and you do want a change then personally I prefer NVidia mate.

No worries Brandon I think you will find that card a really good choice and when my older GTX 650 Ti's give out or I want to swap them that is the card I would have got if I were into gaming at least:).

I am not sure if you got the Asus or another brand because I would have again picked Asus as I do like their stuff but all the same an excellent choice and I don't think you will have many problems with it. Just keep in mind if you do experience driver issues with it a first line of solving is go back a driver version.

Quite interesting, it appears that the fatal error occured before the ISCTD64 driver could do anything at all.
The IoCompleteRequest routine should have never been called as the IRP was still being processed.

Code:

2: kd> !irp fffff9808822cdc0 7
Irp is active with 5 stacks 3 is current (= 0xfffff9808822cf20)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  Pending has been returned
Flags = 40000000
ThreadListEntry.Flink = fffff9808822cde0
ThreadListEntry.Blink = fffff9808822cde0
IoStatus.Status = 00000103 <-- reason why crash occured, this status means that the requested operation is pending completion
IoStatus.Information = 00000000
RequestorMode = 00000000
Cancel = 00
CancelIrql = 0
ApcEnvironment = 00
UserIosb = 00000000
UserEvent = 00000000
Overlay.AsynchronousParameters.UserApcRoutine = 00000000
Overlay.AsynchronousParameters.UserApcContext = 00000000
Overlay.AllocationSize = 00000000 - 00000000
CancelRoutine = 00000000   
UserBuffer = 00000000
&Tail.Overlay.DeviceQueueEntry = fffff9808822ce38
Tail.Overlay.Thread = 00000000
Tail.Overlay.AuxiliaryBuffer = 00000000
Tail.Overlay.ListEntry.Flink = fffff98089036e28
Tail.Overlay.ListEntry.Blink = fffff8000327fbe0
Tail.Overlay.CurrentStackLocation = fffff9808822cf20
Tail.Overlay.OriginalFileObject = 00000000
Tail.Apc = 00000000
Tail.CompletionKey = 00000000
     cmd  flg cl Device   File     Completion-Context
 [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 fffffa8007a9c3d0 00000000 fffff80003560eb0-fffff9808822ced8 Success Error Cancel pending
	      fffffa8007a9c3d0: Could not read device object or _DEVICE_OBJECT not found
	nt!IovpInternalCompletionTrap
			Args: 00041100 00000000 00000001 00000002
 [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 fffffa80091a1330 00000000 fffff880043eac20-00000000 Success Error Cancel pending
	      fffffa80091a1330: Could not read device object or _DEVICE_OBJECT not found
	ISCTD64 <-- driver is doing something after the problem
			Args: 00041100 00000000 00000001 00000002
>[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)] <-- the problem occured here
            0 e1 fffffa800919a040 00000000 fffff80003560eb0-fffff9808822cf68 Success Error Cancel pending
	      fffffa800919a040: Could not read device object or _DEVICE_OBJECT not found
	nt!IovpInternalCompletionTrap
			Args: 00041100 00000000 00000001 00000002
 [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 fffffa8009198040 00000000 fffff8000331c230-fffffa800a828940 Success Error Cancel pending
	      fffffa8009198040: Could not read device object or _DEVICE_OBJECT not found
	nt!PopSystemIrpCompletion
			Args: 00041100 00000000 00000001 00000002
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-fffffa800a828940    

			Args: 00000000 00000000 00000000 00000000
IO verifier information:
No information available - the verifier is probably disabled

Please make sure that you upload a new zip.

Yep Brandon as ae says mate the new dumps are what we really need for this issue - it may be something quite simple like going back a driver version for the new card (for example) so don't get too worried.