Windows blue screen when starting game, after fall patch.

[IzzyTheFool]

The game was working fine just the other day. The fall patch seems to have critically broken the game. When starting, I'm instantly booted to a Windows 10 BSOD stating the computer encountered an error must restart. It blames Classpnp.sys.

This is not happening with any other game on steam, and the laptop has no other errors. It's only 4 months old. I checked to make sure my video drivers are current.

I tried uninstalling, and reinstalling Civ6, and the problem continues. It doesn't look like I'm the only one either.

[Poseidon92100]

Exactly the same for me, I reinstall and always the blue screen !!!!!!!!!!!!!!!!

[Poseidon92100]

Ok man I have the solution. go to "Mydocuments/mygames/Civ6/" and erase all the content. This is probably due to old mods that you had (even if you unsuscribed). It works fine with me

[Acratenn]

Originally posted by Rancendo:

Ok man I have the solution. go to "Mydocuments/mygames/Civ6/" and erase all the content. This is probably due to old mods that you had (even if you unsuscribed). It works fine with me

Thank you! Works for me as well.

Update: Seems like the bug comes back every time I close and reopen the game. No mods installed at all.

[Poseidon92100]

Same here. The bug come back every time

[IzzyTheFool]

I was able to get the game working once on my laptop by deleting that folder, but like the others the bug happens again when the game is restarted. Only the installation on my Windows 10 laptop appears to be affected, the game patched and is working ok on my Windows 7 desktop. This is very annoying.

[Proxima04]

Update window version 1709 worked for me

[Poseidon92100]

Originally posted by Proxima04:

Update window version 1709 worked for me

It changed nothing for me

[Sibylus]

Partner has run into the same issue, and the combo issue of the game continually reading as uninstalled on Steam.

[IzzyTheFool]

Can confirm, after crash steam reads game as uninstalled. Attempting to reinstall locates existing files. I'm curious, does your partner install to a steamdirectory other then C:/ drive? I have my steam installations on a drive seperate from my C:/ SSD. Wpondering if that is a variable.

Also, windows 10 is fully updated, still crashing.

[Novemberchild83]

Hi!

I had exactly the same BSOD - problem when starting the game (Windows 10 - Ver. 1709 - fall update and Geforce Game Ready Driver 388.0). I think i found a solution that works! I started Windows and went completely offline. Next I turned off my Kaspersky Internet Security including Firewall and started Steam in offline mode. Now i was able to start the game without any problems. I closed the game and turned off my PC. Last I startet Windows again turned on Kaspersky and Firewall and game is still starting for 3 times now. Can't tell if the game runs stable at this time. I really hope i could help somebody!

Best regards

[Poseidon92100]

Originally posted by Novemberchild83:

Hi!

I had exactly the same BSOD - problem when starting the game (Windows 10 - Ver. 1709 - fall update and Geforce Game Ready Driver 388.0). I think i found a solution that works! I started Windows and went completely offline. Next I turned off my Kaspersky Internet Security including Firewall and started Steam in offline mode. Now i was able to start the game without any problems. I closed the game and turned off my PC. Last I startet Windows again turned on Kaspersky and Firewall and game is still starting for 3 times now. Can't tell if the game runs stable at this time. I really hope i could help somebody!

Best regards

I also have Kapersky. This is perhaps the source of the problem. Will try your solution

[Novemberchild83]

Originally posted by Rancendo:

Originally posted by Novemberchild83:

Hi!

I had exactly the same BSOD - problem when starting the game (Windows 10 - Ver. 1709 - fall update and Geforce Game Ready Driver 388.0). I think i found a solution that works! I started Windows and went completely offline. Next I turned off my Kaspersky Internet Security including Firewall and started Steam in offline mode. Now i was able to start the game without any problems. I closed the game and turned off my PC. Last I startet Windows again turned on Kaspersky and Firewall and game is still starting for 3 times now. Can't tell if the game runs stable at this time. I really hope i could help somebody!

Best regards

I also have Kapersky. This is perhaps the source of the problem. Will try your solution

Unfortunately the Blue Screen - problem returned! All Drivers are up to date, never used any MOD! I also made a complete hardwarecheck including stress tests (CPU, GPU, RAM, HDD,....,...) every test passed perfectly on my Alienware 17R3. I suspect either a problem with the Windows 10 Fall Update or the new Civ Update! I never had any problems with any game before and still every other game works fine even with high details.

Hardware:
CPU: i7 6820HK 4x 2,7GHz
GPU: Nvidia Geforce GTX980M 8GB
RAM: 16GB

Clean Windows install didn’t help! :-(

I would be grateful for any advice and information! The only information I have: I start the game via steam and get directly the blue screen....classpnp.sys

[IzzyTheFool]

A few observations that may help. My problem resolved itself after Steam did an update sometime last week. Earlier that same day, I noticed that I was somehow still subscribed to a mod on this computer, that wasn't showing up in my subscribed workshop files on my desktop. Specificly it was a workshop mod for the Maori civ. I fixed the problem by resubscribing on my desktop, and then unsubscribing from the laptop, which removed it on both computers. My best guess is this was some sort of synching error, and the laptop was still downloading the mod while the desktop wasn't.

My best guess is that either the steam update, or the resetting of that glitched synch fixed my problem. I'm no longer getting any errors, aside from the sound stutter glitch other people are complaining about since the fall patch. Good luck!

Also, just FYI, as others have stated I also have Kaspersky software, so I could be completely wrong. It does seem unusual that three people with Kaspersky had this problem.