WindowBlinds 6 crash on XP SP2
Tuesday, December 11, 2007 by Victek | Discussion: WindowBlinds
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 
 |
|
Page 1 of 2 | |
|
|---|
Victek
Reply #2 Tuesday, December 11, 2007 12:10 PM
Reply #2 Tuesday, December 11, 2007 12:10 PM
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).
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).
Philly0381
Reply #3 Tuesday, December 11, 2007 12:28 PM
Reply #3 Tuesday, December 11, 2007 12:28 PM
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.
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.
scorpNZ
Reply #4 Tuesday, December 11, 2007 12:51 PM
Reply #4 Tuesday, December 11, 2007 12:51 PM
Make sure nView is disabled,there's parts of it that don't get along with other customization software
Philly0381
Reply #5 Tuesday, December 11, 2007 12:54 PM
Reply #5 Tuesday, December 11, 2007 12:54 PM
Very good catch xscorpx, forgot that was being a problem for some folks. 
Lantec
Reply #7 Tuesday, December 11, 2007 6:46 PM
Reply #7 Tuesday, December 11, 2007 6:46 PM
Right click the systray icon and UNcheck the "Enable Nview"
Victek
Reply #8 Wednesday, December 12, 2007 10:30 AM
OK, I disabled Nview. Unfortunately that didn't help.
Reply #8 Wednesday, December 12, 2007 10:30 AM
Right click the systray icon and UNcheck the "Enable Nview"
OK, I disabled Nview. Unfortunately that didn't help.
Victek
Reply #9 Wednesday, December 12, 2007 11:02 AM
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 #9 Wednesday, December 12, 2007 11:02 AM
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.
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.
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?
killajosh
Reply #10 Wednesday, December 12, 2007 12:04 PM
Reply #10 Wednesday, December 12, 2007 12:04 PM
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......
Wiccan1
Reply #11 Thursday, December 13, 2007 7:43 PM
Reply #11 Thursday, December 13, 2007 7:43 PM
Do not upgrade over v5. Uninstall it all and do a clean reinstall.
yrag
Reply #12 Thursday, December 13, 2007 7:51 PM
You also have the wrong Wbsrv.dll version and a 6600GT.
Reply #12 Thursday, December 13, 2007 7:51 PM
Uninstall it all and do a clean reinstall.
You also have the wrong Wbsrv.dll version and a 6600GT.
Victek
Reply #13 Thursday, December 13, 2007 10:50 PM
You also have the wrong Wbsrv.dll version and a 6600GT.
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 #13 Thursday, December 13, 2007 10:50 PM
Uninstall it all and do a clean reinstall.
You also have the wrong Wbsrv.dll version and a 6600GT.
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.
yrag
Reply #14 Thursday, December 13, 2007 11:07 PM
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.
....if you're happy...I'm happy
Reply #14 Thursday, December 13, 2007 11:07 PM
And what does having a 6600GT have to do with anything?
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
....if you're happy...I'm happy
Victek
Reply #15 Friday, December 14, 2007 10:20 AM
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.
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 #15 Friday, December 14, 2007 10:20 AM
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.
What version of Wbsrv.dll do you have? Maybe I have to install it manually since the uninstall/reinstall process did not replace it (?)
killajosh
Reply #16 Friday, December 14, 2007 10:26 AM
Reply #16 Friday, December 14, 2007 10:26 AM
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....
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....
Victek
Reply #17 Friday, December 14, 2007 11:52 PM
Reply #17 Friday, December 14, 2007 11:52 PM
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.
killajosh
Reply #18 Friday, December 14, 2007 11:58 PM
Reply #18 Friday, December 14, 2007 11:58 PM
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.....
Philly0381
Reply #19 Saturday, December 15, 2007 12:13 AM
Reply #19 Saturday, December 15, 2007 12:13 AM
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.
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.
yrag
Reply #20 Saturday, December 15, 2007 1:11 AM
Reply #20 Saturday, December 15, 2007 1:11 AM
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.
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.
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!
|
|
Page 1 of 2 | |
|
|---|
Reply #1 Tuesday, December 11, 2007 11:43 AM