WindowBlinds 6 crash on XP SP2

from WinCustomize Forums

I'm using the latest registered version of WB 6 on XP SP2 and lately when I change skins I get a memory exception error in Winlogon.exe which forces the system to reboot (the skins do apply properly).  When I first upgraded from WB 5 to WB 6 this didn't happen, but it's not clear what has changed.  I ran Check Disk (with sector recovery), Disk Cleanup and Defrag - no joy.  The system is generally stable apart from this.  I use PC Tools Firewall Plus v3, AVG AV, Spyware Terminator and Winpatrol.  Suggestions appreciated  :SNIFF!: 

windowblinds
12,883 views 24 replies
Reply #1 from WinCustomize Forums Top
Please post the System info from the WB config.
Reply #2 from WinCustomize Forums Top
Sure:

Microsoft Windows XP
Build 2600.xpsp_sp2_gdr.070227-2254

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.

(Plug and Play Monitor) 1 is attached to NVIDIA GeForce 6600 GT

Wblind.dll 2007/11/06 19:17:20
Wbsrv.dll 2007/11/02 14:33:43
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 16:58:21
Screen.exe 2007/11/02 19:37:51

The display driver is the latest available from the Nvidia site (not beta).
Sins of a Solar Empire II
Reply #3 from WinCustomize Forums Top
Well it appears that you are doing the right things with checking you computer. So the only other thing to think about is have you loaded any other customizing software that could be interferring.

Better yet think back to when this first happened, was it after you changed something in the computer? We are always quick to say I didn't change anything. It could be something very minor.
Reply #4 from WinCustomize Forums Top
Make sure nView is disabled,there's parts of it that don't get along with other customization software
Reply #5 from WinCustomize Forums Top
Very good catch xscorpx, forgot that was being a problem for some folks. :CONGRAT: 
Reply #6 from WinCustomize Forums Top
How do I disable Nview?
Reply #7 from WinCustomize Forums Top
Right click the systray icon and UNcheck the "Enable Nview"
Reply #8 from WinCustomize Forums Top
Right click the systray icon and UNcheck the "Enable Nview"
End of quote


OK, I disabled Nview. Unfortunately that didn't help.
Reply #9 from WinCustomize Forums Top
Well it appears that you are doing the right things with checking you computer. So the only other thing to think about is have you loaded any other customizing software that could be interfering.

Better yet think back to when this first happened, was it after you changed something in the computer? We are always quick to say I didn't change anything. It could be something very minor.
End of quote


Well, I should have said that of the things I've recently changed it's not clear why any of them would impact WindowBlinds. PC Tools Firewall PLus and SafeSpace are new additions. Spyware Terminator and Winpatrol have not caused problems in the past. I'm running all of the same resident security software on 32-bit Vista along with WB 6.x and don't have a problem. I know that's not an apples to apples comparison though. Is anyone else running these apps with WB 6?
Reply #10 from WinCustomize Forums Top
I had the same problem. I ended up having to disable the nVidia manager completely through services.msc to get WB to work. That's a new one, from what SD support said......
Reply #12 from WinCustomize Forums Top
Uninstall it all and do a clean reinstall.
End of quote


You also have the wrong Wbsrv.dll version and a 6600GT.
Reply #13 from WinCustomize Forums Top
Uninstall it all and do a clean reinstall.


You also have the wrong Wbsrv.dll version and a 6600GT.
End of quote


I uninstalled and reinstalled WB 6 and am happy to say that it looks like it solved the problem. With regard to file versions though, the System Information in the WindowBlinds UI reports exactly the same file dates. And what does having a 6600GT have to do with anything? I have had the card for quite some time and never had a problem with WindowBlinds until this particular issue.
Reply #14 from WinCustomize Forums Top
And what does having a 6600GT have to do with anything?
End of quote


The 6600 is notorious for not playing nice with any of NVidia's drivers and thus any number of apps. That said, it's a good card in spite of that shortcoming.

As far as the Wbsrv.dll version...I don't have that version and everyone that has experienced the winlogon error appears to have the 2007/11/02 14:30:08 timestamp....go figure.

happy to say that it looks like it solved the problem
End of quote


....if you're happy...I'm happy  ;) 
Reply #15 from WinCustomize Forums Top

As far as the Wbsrv.dll version...I don't have that version and everyone that has experienced the winlogon error appears to have the 2007/11/02 14:30:08 timestamp....go figure.
End of quote


What version of Wbsrv.dll do you have? Maybe I have to install it manually since the uninstall/reinstall process did not replace it (?)
Reply #16 from WinCustomize Forums Top
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 731B/731BF/731BA/730BA(Analog)) 1 is attached to NVIDIA GeForce 8500 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


This is what the latest dl of WB should look like (at least that's what Mike --milksama-- from SD Support told me)...if you dl'd it from SD Central....
Reply #17 from WinCustomize Forums Top
Well, I spoke too soon. The Winlogon crash after changing a skin is back. I uninstalled the PC Tools Firewall since it was a new addition, but it had no effect.
Reply #18 from WinCustomize Forums Top
do you see the nVidia button in the systray? try right-clicking it and clicking exit. then try running WB. see if that helps at all.....
Reply #19 from WinCustomize Forums Top
Having done an uninstall and a new clean install and the problem comes back sure sounds like it something other than WindowBlinds. Your theory in reply #9 as you say isn't apples to apples, but it does give you a reference point. Is it possiblie that a security software program will work on your Vista box and not on the XP, yes.

I'm more of the mind set to think that there is something on the XP box that is not on the Vista box that is causing the problem. I would look at what is installed on both and compare, keeping in mind Vista vs XP, and try to eliminate any differences. I don't know if anyone has suggested doing a restore of the XP machine. I would hold off doing that. You might clear up the problem but you wouldn't have found the cause.

I would hold off doing anymore uninstalling and reinstalling of WB.

Reply #20 from WinCustomize Forums Top
Disable tray icon in NVidia control panel.

Start/ Run - type "msconfig" (w/o quotes). Under the Startup tab un-check 'NvMcTray'. Apply. Re-boot. On the msconfig prompt after boot, check "Do not show again" and OK.
Reply #21 from WinCustomize Forums Top
if yrags' idea doesn't help, try this:

start/run - type "services.msc" (no quotes), right-click on "NVIDIA display driver services" and select properties. In the 'startup type' box, select "disabled. Then restart your PC. If it doesn't fix the WB problem, you can always turn it back on (just follow the same procedures, except select Automatic instead of disabled).
Reply #22 from WinCustomize Forums Top
if yrags' idea doesn't help, try this:

start/run - type "services.msc" (no quotes), right-click on "NVIDIA display driver services" and select properties. In the 'startup type' box, select "disabled. Then restart your PC. If it doesn't fix the WB problem, you can always turn it back on (just follow the same procedures, except select Automatic instead of disabled).
End of quote


I disabled the service, rebooted the computer, ran services.msc again to confirm that the service was not running and changed my WB skin. The problem remains - the skin is applied just fine, then right at the end the winlogon.exe exception pops up.
Reply #23 from WinCustomize Forums Top
what other enhancements other than WB you have running?
Reply #24 from WinCustomize Forums Top
what other enhancements other than WB you have running?
End of quote


Not sure what you mean by enhancements. I use Icon Packager and Sound Packager. I don't have any other program that alters the appearance of the Windows GUI.