Topic: Can't kill polcbm gracefully - The display driver has stopped working (Read 1169 times)
Don't know what to tell you since my experience is limited. I've never experienced what you described except unstable overclocking. Do you have enough power going into the vid cards?
June 19, 2011, 12:39:21 AM
Most certainly not. I don't think this has to do with how fast the card is running, since it only happens when I force kill the application. It's not like when I underclock the card and force quit it works.
June 18, 2011, 09:51:56 PM
You overclocking the shit out of your card?
June 18, 2011, 09:25:02 PM
I just took this to be a fact of life for a while, but now that I am trying to automate restarting the polcbm process it's becoming really annoying. If I X out of the cmd window or do a taskkill to the exe, everything goes black for a few seconds and I get a "The display driver has stopped working and has recovered " message. I'm on an NVIDIA card on Windows 7 Ultimate and have the latest drivers. When this happens my fan control gets reset and I have to set it again, not to mention that it's annoying when it blacks out like that. In fact sometimes it even has rebooted after the black screen so I'd really like this not to happen. To get around it, I sent a keyboard interrupt (Ctrl C) in the cmd window a couple of times and it would exit ok.
Does everyone have this problem? Is there some sort of other way I can kill the process without killing the display adapter every time?
Does everyone have this problem? Is there some sort of other way I can kill the process without killing the display adapter every time?
Jump to: