Fusion OCL detection crashed itself and my OS

Hi all,
is funny that trying to solve a problem switching from sw and ocl render, from cpu and gpu...Fusion crashed itself and my operative system (win7 ultimate).

What Fu console says:
OpenCL clCreateContext failed: CL_INVALID_DEVICE
OpenCL Could not find valid context: CL_DEVICE_NOT_FOUND
...
Renderer3D1: fatal error - hardware shader support not detected (missing GL_ARB_fragment_program extension)
...
What windows warning says (less or more):
a recently installed software creates problem, restore the system before this point.
but restoring is impossible because of an error created in C:/ from a software!

Gpu is a GeForce gts250...an old machine but perfectly working with OCL 1.0 until the crash.
Disabling OpenCL tools and GPU Device from Preferences nothing changes...views are off.

Thanks in advance.

If it worked and suddenly stopped working, I smell driver issues. First off, download the driver manually from Nvidia and during installation, tick "clean install" (or something like that) so the installer will reset any old driver settings. And if it doesn't work anyway, use the rollback driver function in Windows Device Manager - or download an older driver from Nvidia and do a clean install.

Ok, I've launched a clean installation...not solved:

Renderer3D1: fatal error - hardware shader support not detected (missing GL_ARB_fragment_program extension)
Renderer3D1: Render aborted.

and can't rollback driver because windows tells me "file system damaged, first repair it" but its diagnostic tools confirm no errors.
Last but not last...installing old drivers nothing changes.

Summary:
- viewports not visualize, not refresh;
- trying to visualize "tool" nodes from render3d to saver obtain a fatal error;
- trying to visualize "3D tool" nodes Fusion crashes;
- trying to visualize "2D tool" nodes no warnings in console but no images in viewport.

So now you try uninstalling/reinstalling Fusion.

And it sucks when this **** just happens, sadly many love to get into the idea it came from nowhere, but it never does. If something works one day and not the next, something changed. It's just a question of figuring out what and how to fix it. It's all about making sure not to get angry, be methodical and troubleshoot it calmly. Check the Windows logs if you can find any clues there to what changed. Check the Windows update history, etc...

So tired, 2 days of fight is enought for thinking the bad word...format c:\.
If BMD guys had a few shortcuts for analizing and solve....

So tired, 2 days of fight is enought for thinking the bad word...format c:\.
If BMD guys had a few shortcuts for analizing and solve....

There's a decent chance your HDD is bad. Better to set up new install on new drive and keep old drive to pull data from for now.

There's a decent chance your HDD is bad. Better to set up new install on new drive and keep old drive to pull data from for now.

I was thinking, what the h*ll is Chad talking about, bad HDD(?), but I missed the warning about file system needing repair - that isn't a fun message on a production box - so I'm with Chad here, change HDD and do a fresh Windows install.

Chad and Johnny...your are right.
Next step: ssd + fresh win install.