Folding Forum

Recently I upgraded to Windows 8.1 and since then I've been getting intermittent Video_scheduler_internal_error BSOD while folding Core_17 and doing normal Windows operations like just moving the mouse. I upgraded the Nvidia drivers from 314.07 to 327.23 as this error is supposed to be entirely a driver issue but that didn't help. What did decrease the frequency was to use the Windows visual effects properties and change it from letting Windows choose best properties to custom and uncheck everything. This is not what I would call an optimum solution. I intend to slowly add back checkmarks to see if I can ID the offending Windows visual effect.

This is on a machine with the following configuration:

stock Q6600 with 4GB RAM; GTX 580@825MHz as primary display with PhysX(also folding) and a GTX 460@825MHz folding only GPU.
Win8.1, Nvidia 327.23 and 314.07 GPU drivers; Client 7.36 with two GPU slots both running Core_17 WU's

I have not seen anyone else here complaining about this so am I the only one? Comments and solutions would be helpful...

If possible, could you try a fresh installation of 8.1? A slim chance that something didn't upgrade properly when you went from 8 to 8.1.

While changing the drivers, did you select clean installation? Did you only install the drivers or other packages (3D, PhysX, etc) too?

Restore the GPU frequencies to their stock values and see if that helps.

Configure your GPUs to get FahCore_15 WUs and see if the same error or a different one appears.

Yes, it was a clean install of the drivers. It was a custom install with only drivers and PhysX. I do not have Win 8.1 install media (not offered unless you buy a new copy of Windows) to do a total re-install of the OS rather than an upgrade. I haven't configured client to only get Core_15's but that is a reasonable diagnostic step. Removing the OC can't hurt but the error is supposed to be at the driver level as opposed to the GPU.

As a last resort, do a fresh installation of Windows 8 (don't install any applications or drivers), install the minimum updates needed to get 8.1 and once that is done, do the remaining updates and drivers. I would also suggest that you try 1 GPU at a time to see if this issue exists with dual GPUs only or not.

That's recommending a lot of work based on no personal or forum experience with windows 8. Maybe you could cite a web page recommending a complete OS install as a specific solution for this error? What if the OS is the problem? Didn't happen in previous OS. And the fact the symptoms are mitigated by reducing OS usage of the GPU seems to place the problem squarely back on the OS and drivers.

Nothing to lose but time reinstalling the OS. Do it and help disprove that as the cause.

I agree, hence I mentioned as a last resort and not the first thing to do. However, if it is the drivers, we might be able to narrow it down to OpenCL (FahCore_17) or CUDA (FahCore_15). Let's just wait for P5-133XL to report back and move on from those results.

I don't know if this might help?Did you read release notes? http://us.download.nvidia.com/Windows/3 ... -notes.pdf There are a couple unresolved issues with 8.1. Maybe 1 applies to your trouble.Did you try dis-abling hardware acceleration? Even possible with 8.1? All I can input.Still xp'ing down the interweb.

For what it's worth, I was getting repeated BSOD's on a Q9550 box running XP-Pro SP3
GPU only folding 2x GTX560Ti

rolled back from 327.23 to 314.07 = no help

cut back to 85% cpu usage = no help

the box will run forever if I don't touch the mouse
the only thing that works reliably is to click on the Icon and switch from Full to Medium, do my work then switch back to Full & walk away

dschief wrote:For what it's worth, I was getting repeated BSOD's on a Q9550 box running XP-Pro SP3
GPU only folding 2x GTX560Ti

rolled back from 327.23 to 314.07 = no help

cut back to 85% cpu usage = no help

the box will run forever if I don't touch the mouse
the only thing that works reliably is to click on the Icon and switch from Full to Medium, do my work then switch back to Full & walk away

Was your BSOD error message the same?

was about a week ago, do not remember exact wording; However it was driver related

As an update, I solved my BSOD problem by simply plugging my monitor into the DVI plug as opposed to previously using the VGA plug. I have no idea why that helps unless the driver is using a different code-path for the two plugs.

I still get the Video_scheduler_internal_error BSOD if I run a video-intensive program like a game while folding but I normally pause folding before gaming so it doesn't normally effect me. What switching the plug did was make it so that normal computer usage like moving the mouse no longer sets the BSOD off.

Although it didn't matter for this case, if you have a retail Windows 8 key Microsoft will allow you to download the 8 and 8.1 ISO for your version (pro, etc.). You can use this ISO to do a clean 8.1 install and activation with your Windows 8 retail key. There are a couple tricks in the process but it isn't too bad (and it is completely legal, no hacks).

No doubt I could but Like others, I hesitate to do clean installs because of the need to reinstall applications and settings. This particular machine has a complete upgrade path from W95. Even complete computer replacements were reimaged from old backups and then forcing Windows to rediscover HW. It wouldn't surprise me if it had a few old OS artifacts.

I also received this BSOD error just after installing Folding@Home on Windows 8.1. I'm using a new GTX 660 card with the latest driver 332.21.

Welcome to the F@H Forum RickSummon,

Could you please post your log file which includes the system configuration and F@H settings (viewtopic.php?f=61&t=16206&p=225958#p225958) so we can see how your FAHClient is setup? Furthermore, please note that if you are using your GPU only for folding, the best driver to fold with Non-GK110 GPUs is 327.23 since the latest drivers will cause a significant slow-down only for folding.