BSOD 3 times in two hours of play

[RR]

I am a new player. For 2 hours of play three times the computer fell into BSOD. System configuration: Intel Core i5-3550, 8 Gb RAM, GeForce GTX 1060 6Gb, Windows 10 x64

[Colo]

Almost the same issue here, except it closes the game but leaves the exe half open, impossible to taskkill(cmd), and taskmanager doesn't see it plus the details tab is broken, as is half of Windows, making rebooting/shut down impossible as well without a hard reset.
Seems like it crashes part of the graphics driver and other parts of Windows for me.
GTX980 with 416.16 drivers, W10 x64 1803.

[~]

I think lots are having this problem with the Geforce 411.63 Nvidia drivers , i have to , the latest driver is the 411.70 i have not tried that yet i do not see the 416.16 ?
GTX 1060 -6GB
this happened ages back with SE3 and people rolled back to an earlier driver via the Device Manager
google DDU Tool cleans out old drivers i then run it twice before installing a new driver / Custom / Clean Install

[Cthulhu Calamari /|\(;,;)/|\]

I've been having the same issue on a GTX 1070 w/ the 416.16 driver. Not only do I get BSOD, but if I attempt to restart the system immediately after the game crashes out, my system will hang on the "Restarting" screen indefinitely, until I hit the physical Restart button.

RIP

This game is completely unplayable in this state.

[Cthulhu Calamari /|\(;,;)/|\]

Fired off a message to their Tech Support contact. We'll see how that goes...

[Leppie]

I got BSOD twice and a game crash in about 1 hour of COOP play.

System:
i7-7700, 16 GB DDR4, GTX 1080ti (11 GB), W10 x64, Geforce v416.16

[Sitiran]

Same here. It took place twice and started when updated from 399.24 to 416.16. I'm going to go back to 399.24 and see what happens. Each time the BSOD showed "Bad Pool Caller" as the error and the administrative event was event id was 41 w/ task category (63).

System:
AMD Ryzen 5 1600, 16 GB DDR4, EVGA GTX 1050 Ti, Windows 10 x64 (Build 17134), Driver version 416.16, DX12 version of game

[Wilco Smit]

Yep here as well......
Different messages with the bsod, Bad Pool Caller, DPC watchdog violation, IRQL not less or equal and just had a new one called Kernel Security Check Failure.
And always about after 15 minutes of play.
Looked into it, but everything checks out okay on the PC, and I don't have a problem with other heavy games......
Hope the solve this, it's no fun like this.

[Cthulhu Calamari /|\(;,;)/|\]

I also got both the Bad Pool and the DPC Watchdog messages

[Wilco Smit]

I rolled back to Driver 399.07, and that works fine again......

Nope, I haven't got the 399.24 driver.

But with more than a half hour play, it should be good.

[Cthulhu Calamari /|\(;,;)/|\]

I rolled back to Driver 399.07, and that works fine again...

Interesting. Rebellion’s tech support wanted me to update Windows 10 to see if that was the issue, even though people have noted the issue on multiple Windows versions... I'll toss them that info in my reply.

[Cthulhu Calamari /|\(;,;)/|\]

I'm rolling back to 399.07 now. I'll report back if it works for me, too.

[Cthulhu Calamari /|\(;,;)/|\]

Confirmed. Driver 399.07 totally works. Get it together, Nvidia!

[Wilco Smit]

I also sended a mail to Nvidia, telling them about this issue.
Hope that they can solve this in a new driver update.

[Toastman]

I also had the lockup / ctd when running DX12 and 416.16 NV driver on a clean install of Win10 !809.
I then tried going back to DX11 but got a corrupted checkpoint error , so I had to start campaign again :( .
Not had any more crashes running DX11. Fingers crossed .

[⚡ FaTcaP ⚡]

DX12 + async compute On = Crash game
DX11 = No crash
DX12 + async compute Off = No crash