Win32k.sys error

WTF....

OK. I am not a very happy camper. I lost nearly a weeks time trying to figure out what was going on with my system. I keep my workstation running weeks at a time without a reboot so at first I did not understand what was going on. After a seemingly routine reboot for network refresh purposes I got the BsoD. Moreover no matter what I did I could not avoid it.

So I had to rebuild my system from scratch; a timely process to say the least. Well after nearly a days effort I rebooted and there it was again. I was floored to say the least given I use a 64 bit system. So I did it again, and again...

Anyway to make a long sad story short I isolated it WindowBlinds 5. Now with that said I was under the impression it was 64 bit safe so it was one of the last programs I did not consider in my very long trouble shooting process. Additionally, it may have been the skin I was using I dont know but I'm very irked at the moment. The error from what I can remember is: win32k.sys Datestamp 45d3d32c In short it reset the file creation tag to November 2, 2006. In safe mode I could not alter or replace the file.

I'm also willing to bet this situation is yet another byproduct of the goodness that is the DRM love in Vista.

On a side note, for what it is worth I wish SD would give a listing option in SDC to show products by supported platform only.
6,309 views 9 replies
Reply #1 Top
In SDC if you click on a product, near the bottom (in it's own seperate frame) there will be product information such as version, release, and supported operating systems. In some cases, it might even tell you how large the file is.

Another question to help out Stardock moderators: Are you using Windows Vista or Windows XP? If you are using Vista, which version (Basic, Premium, Ultimate, etc.)? If you are using XP, which version (Home, Pro)? Can you also post a more detailed spec sheet on your system?
Reply #2 Top
Hello,

I have been having the same problem. Here is my system info:


Your computer has a Windows Experience Index base score of 5.2

Your Windows Graphics Experience score is 5.9

WindowBlinds version : WindowBlinds 6 (6.0 (beta build 30 x86 - Vista Edition))

WindowBlinds is installed correctly on this PC

WindowBlinds appears to be activated on this PC

(Dell 2407WFP (Digital)) 1 is attached to NVIDIA GeForce 7950 GX2

Wblind.dll 2007/08/01 10:45:20
Wbsrv.dll 2007/08/01 15:27:02
Wbconfig.exe 2007/08/01 15:27:45
Wbload.exe 2007/07/30 13:14:11
Wbhelp.dll 2007/07/24 10:21:07
Tray.dll 2007/07/24 10:21:49
Wbload.dll 2007/07/24 10:33:56

I am running nVidia driver 162.22_forceware_winvista_32bit_english_whql. I have tried different drivers, ram, ram timings, and different versions of WindowBlinds. With the 5.51.025 WindowBlinds, it would give me the win32k.sys error EVERY time I tried to boot. I would have to go into safe mode and uninstall WindowBlinds to fix it. With the new 5.90[b].022 version, it will BSOD once, then boot normally, every other time. Any help would be appreciated.

Thanks in advance.
Reply #3 Top
Same problem. Tried everything, nothing working until I tried this : open Services, double click the Stardock Windowblinds service, select the logon tab and check the 'allow this service to interact with the desktop' box. Since then, not one bsod. Uncheck the box and back to bsod's. Go figure.
Reply #4 Top

Same problem. Tried everything, nothing working until I tried this : open Services, double click the Stardock Windowblinds service, select the logon tab and check the 'allow this service to interact with the desktop' box. Since then, not one bsod. Uncheck the box and back to bsod's. Go figure.


i tryed your solution but it didn't work... if i set that parameter windows will just crash on win32k.sys at every boot. I guess the only hope for us Vista 64 users is to wait for a WB6 release, since also if wb5 claims to be vista 64 compatible in facts it is not.

--

Your computer has a Windows Experience Index base score of 5.7

Your Windows Graphics Experience score is 5.9

WindowBlinds version : WindowBlinds 5 (5.51 (build 110 x86 - Vista Edition)) - 64 bit OS

WindowBlinds is installed correctly on this PC

WindowBlinds appears to be activated on this PC

(SyncMaster 225BW, SyncMaster CX223BW(Digital)) 1 is attached to NVIDIA GeForce 8800 GTX

Wblind.dll 2007/06/18 15:11:20
Wblind64.dll 2007/06/18 15:11:04
Wbsrv.dll 2007/05/05 16:28:50
Wbconfig.exe 2007/06/19 10:43:03
Wbload.exe 2006/03/13 16:54:14
Wbhelp.dll 2004/09/18 16:37:07
Tray.dll 2006/04/28 18:26:49
Reply #5 Top
digging up an old thread a bit

I've had the same error. I only recently build my desktop machine with vsita and I would intermittently get a bsod on boot in win32k.sys just before the windows flag bubble would show before it went to the welcome screen. I updated my video card drivers the day before yesterday and since then it would give me this error on every cold boot (but after it restarted from that it was fine). I uninstalled WB this morning and haven't had it bsod since. I gave it a couple of cold boots just to be sure but will be keeping an eye on it over the next few weeks.

System specs are

Intel Core2Duo e6750 cpu
Asus P5K-E wifi motherboard
2gb of pc6400 ddr2 ram
nvidia 7900gtx (currently running 163.44 drivers - previously 162.22)
Vista Ultimate 32bit
Windowblinds 6 beta (5.90[b].027)

Interestingly I DON'T get the problem on my laptop which is also running Vista Ultimate 32bit and the latest beta of WB 6. The specs of that are

Intel Core2Duo T7200
2gb ddr2 ram
nvidia geforce go 7700 (158.45 drivers)

On a side note the WB uninstaller left the entry for the WB service behind on uninstall.

EDIT: having had a quick trawl of other forum posts it seems there's some weird interaction happenning with USB devices. Currently I have my keyboard and Mouse plugged in via usb (the mouse being a logitech mx revolution wireless mouse) and also usb hub/card reader on my monitor (which is also where the receiver for the mouse is plugged in for better reception)
Reply #6 Top
I started this thread : WWW Link as I was getting a Win32k.sys error + BSOD on each reboot.In my case a solution was found.It was a usb device causing it,but only when WB was installed..weird,but a happy ending. 
Reply #7 Top
In my case removing any of the usb devices is not an option. Still need to make sure it was something clashing with WB causing the problem (give it a few days with it uninstalled to make sure).
Reply #8 Top
I'm concerned because this is a new PC I have here and I can't use the remote control for the media centre feature if I have WB installed (due to having to unplug the remote sensor).
Question to Stardock...will this issue be fixed so I can use all the features on my new PC as well as WindowBlinds ?