Does this happen every time you run the Display Properties applet or just when you update the drivers?
Walt
Hey Walt,
Here's how I was able to do it:
Install a new display driver package from nVidia but don't reboot.
Double-click the BOINC Manager icon in the tray to bring the application up. Click on the Work tab, chose a running Project and finally click on Show Graphics button on the left hand side. If it behaves the way it did here, you should get an error from nVidia drivers and a client error msg scrapping your WU. Note that I haven't tried to get a similar result any other way.
If you look at all the WU I have crunched you will find two client errors that were made with the above method.
HTH
Thanks MadJack, I wasn't sure whether the error occurred when you installed the driver or later.
If you're in the mood for some experimentation, try this next time - open the graphics window with "show graphics" before you install the updated drivers. I'm curious about whether it'll handle the OpenGL modules like the other ones. That is, if it'll schedule the actual installation for those driver files until the reboot. Oh, do it when you have a workunit with very little CPU time already used, in case it breaks again. That way you won't waste so much crunch time.
Its likely the errors occur because you're mixing driver versions. If they're not in use the OpenGL modules could get updated when you install the updated drivers. So when you later "show graphics" it'll load the newer modules, which won't work right with the older drivers already running.
Do you have any other OpenGL applications? Another BOINC project or 3d game? It would be interesting to find out how other OpenGL applications handle driver updates, whether they crash or produce some kind of error. And its certainly not common, theres a very good reason they put up the "reboot" dialog. You can see what happens when you don't.
Other then experimenting with the "show graphics" before updating the driver, I'd recommend not displaying the grapbics until after you're rebooted.
RE: RE: MadJack, Does
)
Thanks MadJack, I wasn't sure whether the error occurred when you installed the driver or later.
If you're in the mood for some experimentation, try this next time - open the graphics window with "show graphics" before you install the updated drivers. I'm curious about whether it'll handle the OpenGL modules like the other ones. That is, if it'll schedule the actual installation for those driver files until the reboot. Oh, do it when you have a workunit with very little CPU time already used, in case it breaks again. That way you won't waste so much crunch time.
Its likely the errors occur because you're mixing driver versions. If they're not in use the OpenGL modules could get updated when you install the updated drivers. So when you later "show graphics" it'll load the newer modules, which won't work right with the older drivers already running.
Do you have any other OpenGL applications? Another BOINC project or 3d game? It would be interesting to find out how other OpenGL applications handle driver updates, whether they crash or produce some kind of error. And its certainly not common, theres a very good reason they put up the "reboot" dialog. You can see what happens when you don't.
Other then experimenting with the "show graphics" before updating the driver, I'd recommend not displaying the grapbics until after you're rebooted.
Walt