Windows XP SP2 restart when any version WindowBlinds is installed.
Winlogon.exe error with WindowBlinds
Thursday, December 6, 2007 by Jean Carlo Santa Anna | Discussion: WindowBlinds
I have Stardock Central and Object Desktop. I always used WindowBlind and never crash my Windows XP SP2,
However, currently, if I keep the windowBlind installed so Windows XP restart randomly and shows the following error: Application crashed winlogon.exe, version 0.0.0.0, module failed WbSrv.dll, version 6.0.0.0, address crashed 0x00017dfe. When unistall WindowBlind, no error and Windows XP works fine. What can I do to solve this problem?
milksama
Reply #2 Friday, December 7, 2007 2:48 PM
Reply #2 Friday, December 7, 2007 2:48 PM
Could you also please post the information located within the System Information section here?
-Mike
[Stardock Support]
Jean Carlo Santa Anna
Reply #3 Friday, December 7, 2007 3:55 PM
Where can i get System Information section? That type of information the system you want?
Reply #3 Friday, December 7, 2007 3:55 PM
Where can i get System Information section? That type of information the system you want?
Jean Carlo Santa Anna
Reply #4 Friday, December 7, 2007 4:31 PM
Reply #4 Friday, December 7, 2007 4:31 PM
Ok, Sorry!
Here system Information:
WindowBlinds version : WindowBlinds 6.01 (build 40 x86)
WindowBlinds is installed correctly on this PC
WindowBlinds appears to be activated on this PC
Your machine supports per pixel borders on WindowBlinds skins.
(SyncMaster 931BW , SyncMaster Magic CX931BW (Digital)) 1 is attached to NVIDIA GeForce 6600 GT
Wblind.dll 2007/11/06 19:17:20
Wbsrv.dll 2007/11/02 14:33:04
Wbconfig.exe 2007/11/02 14:30:08
Wbload.exe 2007/09/27 17:47:44
Wbhelp.dll 2007/08/27 11:54:07
Wbui.dll 2007/11/06 10:13:05
Tray.dll 2007/09/12 17:58:21
Screen.exe 2007/11/02 14:33:51
Here system Information:
WindowBlinds version : WindowBlinds 6.01 (build 40 x86)
WindowBlinds is installed correctly on this PC
WindowBlinds appears to be activated on this PC
Your machine supports per pixel borders on WindowBlinds skins.
(SyncMaster 931BW , SyncMaster Magic CX931BW (Digital)) 1 is attached to NVIDIA GeForce 6600 GT
Wblind.dll 2007/11/06 19:17:20
Wbsrv.dll 2007/11/02 14:33:04
Wbconfig.exe 2007/11/02 14:30:08
Wbload.exe 2007/09/27 17:47:44
Wbhelp.dll 2007/08/27 11:54:07
Wbui.dll 2007/11/06 10:13:05
Tray.dll 2007/09/12 17:58:21
Screen.exe 2007/11/02 14:33:51
yrag
Reply #5 Friday, December 7, 2007 5:55 PM
Well, that answers the question as to what is hooking winlogan.
That's the wrong Wbsrv.dll version.
Reply #5 Friday, December 7, 2007 5:55 PM
Wbsrv.dll 2007/11/02 14:33:04
Well, that answers the question as to what is hooking winlogan.
That's the wrong Wbsrv.dll version.
BigALTho
Reply #6 Friday, December 7, 2007 9:00 PM
Reply #6 Friday, December 7, 2007 9:00 PM
I am having the same problem when I had installed the objectdock full set. My system info. is
WindowBlinds version : WindowBlinds 5 (5.51 (build 97 x86))
WindowBlinds is installed correctly on this PC
WindowBlinds appears to be activated on this PC
Your machine supports per pixel borders on WindowBlinds skins.
(Plug and Play Monitor) 1 is attached to NVIDIA GeForce4 MX 4000
Wblind.dll 2007/06/19 10:39:20
Wbsrv.dll 2007/03/13 09:57:52
Wbconfig.exe 2007/06/19 10:43:03
Wbload.exe 2006/03/13 16: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
Is this correct?
WindowBlinds version : WindowBlinds 5 (5.51 (build 97 x86))
WindowBlinds is installed correctly on this PC
WindowBlinds appears to be activated on this PC
Your machine supports per pixel borders on WindowBlinds skins.
(Plug and Play Monitor) 1 is attached to NVIDIA GeForce4 MX 4000
Wblind.dll 2007/06/19 10:39:20
Wbsrv.dll 2007/03/13 09:57:52
Wbconfig.exe 2007/06/19 10:43:03
Wbload.exe 2006/03/13 16: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
Is this correct?
BigALTho
Reply #7 Friday, December 7, 2007 9:05 PM
Reply #7 Friday, December 7, 2007 9:05 PM
Oh, I forgot I did before I installed the WB 5 version, I had the WB 6 version first and had trouble with it, also. The WB 6 version when I right click to access properties on desktop the tool bar would disappear and then the rest of the desktop would blank out then regain back to normal so that is why I switched to WB 5. Of corse I uninstalled the WB 6 and installed the WB 5 version. Any help?
Jean Carlo Santa Anna
Reply #8 Saturday, December 8, 2007 8:04 AM
Reply #8 Saturday, December 8, 2007 8:04 AM
Ok, but how can i fix the Wbsrv.dll version?
ZubaZ
Reply #9 Saturday, December 8, 2007 9:49 AM
Reply #9 Saturday, December 8, 2007 9:49 AM
Jean, bigaltho: Uninstall, reboot, install again
Your best best is to install Stardock Central and let that manage your installs.
In that case, uninstall WB, install SDC, reboot, install WB (via SDC), reboot.
Your best best is to install Stardock Central and let that manage your installs.
In that case, uninstall WB, install SDC, reboot, install WB (via SDC), reboot.
DrJBHL
Reply #10 Saturday, December 8, 2007 10:21 AM
Reply #10 Saturday, December 8, 2007 10:21 AM
I had a weirdie prob....uninstalled the WB5 and installed Stardock Central...then did the WB6 Update of OD thru SD Cental. Solved all the problems. Glad to see I didn't do something idiotic. Thanks Zubaz....altho I didn't need the help, following yout logic/algorithm was instructive.
Jean Carlo Santa Anna
Reply #12 Saturday, December 8, 2007 2:13 PM
Reply #12 Saturday, December 8, 2007 2:13 PM
I did all reported above, but the error of winlogon.exe and Wbsrv.dll still occurring. Need help, I want to continue using windowBlinds.
Please login to comment and/or vote for this skin.
Welcome Guest! Please take the time to register with us.
There are many great features available to you once you register, including:
- Richer content, access to many features that are disabled for guests like commenting on the forums and downloading skins.
- Access to a great community, with a massive database of many, many areas of interest.
- Access to contests & subscription offers like exclusive emails.
- It's simple, and FREE!
Reply #1 Thursday, December 6, 2007 9:33 PM
If yes and it still doesn't work you can try a few things:
#1- Search winlogon.exe on your HD and make sure you only have one in the System folder. Any others found are malware.
...if you only have the one, then:
#2- Start/ Run/ type "sfc /scannow" (w/o quotes). If your winlogon file is corrupt, it will fix it.
...if it comes up error free, then:
#3- Go back to when this started and check everything you've installed. You're looking for any app that might have a reason to hook onto winlogon.
If all else fails, run a restore point prior to the error.