After installing the RTM I'm still having the Blue Screen error with win32k.sys. I am using the new Stardock skin that was given to subscribers. Here are the system details:

Your computer has a Windows Experience Index base score of 2

Your Windows Graphics Experience score is 2

WindowBlinds version : WindowBlinds 5 (5.50 (build 79 x86 - Vista Edition))

WindowBlinds is installed correctly on this PC

WindowBlinds appears to be activated on this PC

You have one monitor in total.

(Generic PnP Monitor) 1 is attached to NVIDIA GeForce Go 7400 (Microsoft Corporation - WDDM)

Wblind.dll 2006/12/20 13:35:20
Wblind64.dll 2006/10/09 11:51:37
Wbsrv.dll 2006/12/29 16:00:39
Wbconfig.exe 2006/12/20 13:35:02
Wbload.exe 2006/03/13 17:54:14
Wbhelp.dll 2004/09/18 16:37:07
Wbui.dll 2005/12/06 21:29:06
Tray.dll 2006/04/28 18:26:49

Comments
on Jan 11, 2007

I am sorry to say that I think you will need to contact Microsoft technical support as a BSOD in win32k.sys will be a bug in the OS itself, or corruption caused by drivers.

The only thing I can suggest is you try using the newer nvidia drivers.

on Jan 11, 2007
Thanks Neil...I looked at Nvidia's website for drivers for my card but only found XP and Win2k drivers. It is a GeForce Go 7400 card in a laptop. Is there another source for beta Vista drivers available?
on Jan 12, 2007

Hi ToeJo,

I have an Nvidia card in my laptop too. Unfortunately Nvidia does not support their laptop graphics cards with their drivers.     We're pretty much forced to wait for our laptop manufacturer to come out with drivers or to get them via Windows Update from Microsoft.

on Jan 17, 2007
I found updated Vista drivers here:
http://drivers.softpedia.com/get/GRAPHICS-BOARD/NVIDIA/Nvidia-GeForce-Go-Forceware-9754-WHQL.shtml

I'll let you know if they work. Keep your fingers crossed!

on Jan 17, 2007
Usually you can find the vista ones at laptopvideo2go.com
on Jan 17, 2007
Just to let you know that we may have reproduced something similar in house.
on Jan 23, 2007
That's good to know. I look forward to your insight. Neil...you've been getting the job done for years now. Keep it up!
on Jan 29, 2007
I've tried the latest drivers. I've uninstalled and re-installed. Windows tells me the problem is with the Catalyst control center. That's very odd considering I'm using an nVidia card. There are no ATI drivers on my system what so ever. I miss WB sooo bad. I feel like an addict going through detox. (OK...maybe not that bad.) The tears of anguish flood the crevices of my keyboard!   
on Jan 29, 2007

The latest WB beta build that was put up on the weekend resolved this issue for the test box we were able to repro on.

Are you still having issues with that build?

on Jan 29, 2007
I tried it last night. (Sunday eve) Same result. The same file came up as a problem. win32k.sys but it had different addresses on it. I saw the build and figured you had found and repaired the problem. No such luck.
on Jan 29, 2007

Assuming you uninstalled WB totally, rebooted & then reinstalled, then it sounds like your problem may be unrelated to WB. 

on Jan 29, 2007
I'll try it again...Thanks Neil.
on Jan 29, 2007
Im wondering what happens if you install a driver in Windows XP mode?

I heard you can try and install device drivers from Windows XP on Vista in an XP Mode when a Vista Driver doesnt exist...
on Jan 29, 2007
    WOOOHOOO!!! This morning after my earlier posts, I noticed an MS update waiting to be installed. It was a new nVidia driver from MS. I installed it and everything is working great! I can breathe again. Neil...thanks for your help. Now...off to the skins!