Windows 7: BSOD after exiting games

Hello, most of the times I exit a game (usually by Alt-F4) I get a bsod. It doesn't specify any files. Does anyone have any insight on this?



Win 7 ultimate x86
Laptop is brand new, installed windows last week.

Dump blames CDD.DLL, part of the Canonical Display Driver in windows, Run system file checker
SFC /SCANNOW Command - System File Checker

Hi, welcome to the forums

Firstly using ALT+F4 is exiting the game while it is still in a 'full-active' state. ALT+F4 is designed mostly for closing down Explorer windows or any other Windows environment applications (e.g. Paint, Office, Media Player). Using the game's 'Exit' facility (in-game menu) will cause the game to systematically stop internal processes then shut the game down. This 'active game state' could possibly be what's causing your BSOD.


OS

Hey, SFC didn't find any problems. The BSOD problem was fixed though. Acer has a really bad habit of having ALL the possible components of a laptop written in the product overview and I don't really know what exactly I have in my laptop. The processor, vid card, hdd etc are obvious, but things like motherboard, sound card, network card I had no idea. So I may have chosen the wrong drivers. After checking for more info and found out what I actually had, I installed the right drivers and all worked out fine. Thanks for your suggestions guys. Also, I'll stop using ALT + F4 in games

That's good news, glad it was a simple fix

Please enjoy the rest of the forums. You may even be able to contribute to other issues


OS

Oh my. It wasn't a simple fix after all The issue is back, and seems here to stay. The worst problem is that the BSOD also occurs when a game crashes, so even if I did stop using ALT-F4 it's still happening. Games that crash a lot (I'm looking at you, Fallout 3) got put aside for the moment, but I'm guessing that it will happen to other games. Eventually.

I added new dump and perfmon report files.

This is getting a bump because, unfortunately, not only that this BSOD problem persists, I have ANOTHER BSOD (this one came out of the blue, no game was opened. It pointed out to win32k.sys).

Attaching NEW BSOD dumb, see last post for the one I get after exiting a game (or, for example, closing the process on a game that's not responding).

LE: Please note that the 2 dumps have the same name Sorry about that, forgot.

It's fixed. The problem was Acer Launch Manager, which apparently isn't compatible with Windows 7. Deleting it fixed all my BSODs.