sypolog sypolog

WB6 XP explorer crashes on menubar click

WB6 XP explorer crashes on menubar click

Any ideas?

Just upgraded to WindowBlinds V6, which all looks graet, except that if i go to select any option (File, Edit, View etc...) from the standard menu bar in any standard XP window, explorer crashes and the whole desktop resets.

The toolbars work OK, as do IE and application windows. Tried re-installing WB6, but problem remains.

Can anyone help, or should I just revert to V5?
15,456 views 51 replies
Reply #27 Top
I have an itergrated video card: Mobile Intel(R) 945GM Express Chipset Family
This problem is not caused by the video card.
Reply #28 Top

That rules out nview being the issue then.

In that case could you do the following please :

Please download

http://www.microsoft.com/technet/sysinternals/ProcessesAndThreads/ListDlls.mspx

Then run listdlls > log.txt and e-mail me the log.txt file.  My address is my firstname @stardock.com

Reply #29 Top
ok i will do that, however, i have uninstalled everything (Stardock products). I can't go without my PC working. I need it everyday to do work.
Reply #30 Top
Hey, you know what? - I think it *is* nVidia nView that's interfering!

I went into the nView desktop manager and clicked on the button to disable all features - and explorer menu bar is responding fine under WindowBlinds 6!

I'll run like this for a bit to check everything. About the only nView feature I was using was the thing that minimises/restires windows quickly.

Have you tried this, silver?

Comments, Neil?
Reply #31 Top

What version of the nvidia drivers do you have installed?

I tried installing the latest nvidia drivers, but I was unable to find the nview settings.  Did they remove it?

Reply #32 Top
Fixing the nVidia issue seems to be working for a great deal of our customers. If you should be happening to reading this and have an nVidia card please explore this fix. 
Reply #33 Top
Cheers for that Sypolog - im fixed, i've disabled it Although I didnt think I had it as I have the latest version and it doesnt sit in the sys tray like it did with my older versions - I found it sat quitely minding its own business in the control panel.

weeeeeee Im happy now


Neil, I have the latest version I think for my card nForce_5.10_WinXP2K_WHQL_english

Thanks for you help guys
Reply #34 Top
That all depends on recent drivers and/or what OS you are using now.
nView is not present for Vista except with Quadro cards and drivers.

Forceware drivers have also changed to where nView is present only with a few cards for XP using multiple monitors and such.

If you have it - there will be an nView icon with the Nvidia control panel icon in the control panel window. If you don't have it with the latest driver... then you don't have the correct card to be using that feature. It is installed with the drivers and control panel.

Since I use Vista I've been thinking of getting rid of my 8800gts for 2 new Quadro cards and having this feature and even buying the latest MOB for it also the 680i. I hear it is the best and is really nice with nTune too!

SGT
Reply #35 Top
Think I have the same version - latest nVidia WHQL GeForce set, the one where the nView Desktop Manager sits in Control Panel.

nView Desktop manager V120.02

...comprising the following versions...
NVIEW.DLL 6.14.10.12002
NVSHELL.DLL 6.14.10.12002
NVAPPBAR.EXE 6.14.10.12002
NVWDMCPL.DLL 6.14.10.12002
NWIZ.EXE 6.14.10.12002
NVTUICPL.CPL 6.14.10.12002
NVWDDI.DDL 6.14.11.6218
NVCPL.DLL 6.14.11.6218
NVDSPSCH.EXE 6.14.10.12002


And I cannot notice any effects of disabling the NV features. But I used to like its ability to make windows transparent whilst being dragged across the worktop. Can that be made to happen under WindowBlinds?
Reply #37 Top
OK, I'll take a look. But Stardock would come out of it better IMO if you could eliminate the need to workaround nView.

SYpoLoG
Reply #38 Top
Or nView would be better if it played nicely with WB 
Reply #39 Top

What version of the drivers includes nview 120.02?

The latest nvidia drivers (163.71) have nview 111.17 included.

Reply #41 Top
Neil. That's odd. My NV drivers came from 162.18_forceware_winxp_32bit_english_whql
Reply #42 Top

It sounds like they may have gone backwards in nview version then.  I will see if I can find that version.

Reply #44 Top

Neil. That's odd. My NV drivers came from 162.18_forceware_winxp_32bit_english_whql


So did mine - I have NView 120.02 (Something tells this little birdy that she gave the wrong driver information )

[Display]
Processor: AMD Athlon(tm) XP 3200+ (2204 MHz)
Operating System: Microsoft Windows XP (Service Pack 2)
DirectX version: 9.0c
GPU processor: GeForce FX 5500
ForceWare version: 162.18
Memory: 256 MB
Video BIOS version: 4.34.20.87.00
IRQ: 19
Bus: AGP 8X

[Components]

nvCplUIR.dll 1.4.13.09 NVIDIA Control Panel
nvCpl.cpl 1.4.13.09 NVIDIA Control Panel Applet
nvExpBar.dll 1.4.13.09 NVIDIA Control Panel
nvCplUI.exe 1.4.13.09 NVIDIA Control Panel
nvViTvSR.dll 6.14.11.6218 NVIDIA Video and TV Server
nvViTvS.dll 6.14.11.6218 NVIDIA Video and TV Server
nvDispSR.dll 6.14.11.6218 NVIDIA Display Server
NVMCTRAY.DLL 6.14.11.6218 NVIDIA Media Center Library
NVOGLNT.DLL 6.14.11.6218 NVIDIA Compatible OpenGL ICD
nvDispS.dll 6.14.11.6218 NVIDIA Display Server
NVCPL.DLL 6.14.11.6218 NVIDIA Compatible Windows 2000 Display driver, Version 162.18
NV4_MINI.SYS 6.14.11.6218 NVIDIA Compatible Windows 2000 Miniport Driver, Version 162.18
NV4_DISP.DLL 6.14.11.6218 NVIDIA Compatible Windows 2000 Display driver, Version 162.18
nvGameSR.dll 6.14.11.6218 NVIDIA 3D Settings Server
nvGameS.dll 6.14.11.6218 NVIDIA 3D Settings Server

Reply #45 Top

This may be of help for locating previous driver versions:
http://www.nvidia.com/object/winxp-2k_archive.html
(162.18 is the first link here)


The current released drivers that Neil referenced are available here:
http://www.nvidia.com/object/winxp_163.71.html


-Mike
[Stardock Support]




Ahha - now I now why i got confuddled. I did give the correct info. Nvidia released a new set just after i re-installed mine after a hiccup I had.
Reply #46 Top
Just to through in my 2 cents, I'm having this problem as well, but I do not have an nVidia card. I have an ATI x300 (this is a laptop). OS is XP SP2.

Here's what WB is telling me:

WindowBlinds version : WindowBlinds 6.0 (build 32 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.

(Default Monitor) 1 is attached to ATI MOBILITY RADEON X300 (Omega 3.8.273)

Wblind.dll 2007/09/27 12:40:20
Wbsrv.dll 2007/09/23 10:10:43
Wbconfig.exe 2007/10/01 18:09:33
Wbload.exe 2007/09/27 16:42:44
Wbhelp.dll 2007/07/11 15:06:07
Wbui.dll 2007/09/22 13:13:06
Tray.dll 2007/09/12 18:52:21
Screen.exe 2007/09/30 15:18:24


It doesn't seem to happen with any particular app, only with an explorer window or ie7 window. Drop-down menus seem to work fine, but when I click the toolbar or try to open another (or first) explorer window it will either hiccup or crash. With that, here's what log.txt has to say abour explorer.exe:

ntdll.dll, kernel32.dll, ADVAPI32.dll,
RPCRT4.dll, BROWSEUI.dll, GDI32.dll,
USER32.dll, msvcrt.dll, ole32.dll,
SHLWAPI.dll, OLEAUT32.dll, SHDOCVW.dll,
CRYPT32.dll, MSASN1.dll, CRYPTUI.dll,
WINTRUST.dll, IMAGEHLP.dll, NETAPI32.dll,
WININET.dll, Normaliz.dll, iertutil.dll,
WLDAP32.dll, VERSION.dll, SHELL32.dll,
UxTheme.dll, ShimEng.dll, AcGenral.DLL,
WINMM.dll, MSACM32.dll, USERENV.dll,
IMM32.DLL, wbsys.dll, comctl32.dll,
comctl32.dll, msimg32.dll, wbhelp.dll,
MSGINA.DLL, WINSTA.dll, ODBC32.dll,
comdlg32.dll, odbcint.dll, apphelp.dll,
msctfime.ime, CLBCATQ.DLL, COMRes.dll,
cscui.dll, CSCDLL.dll, themeui.dll,
Secur32.dll, xpsp2res.dll, actxprxy.dll,
wmpband.dll, MPR.dll, SAMLIB.dll,
urlmon.dll, SETUPAPI.dll, msi.dll,
LINKINFO.dll, ntshrui.dll, ATL.DLL,
tray.dll, ieframe.dll, PSAPI.DLL,
NETSHELL.dll, credui.dll, iphlpapi.dll,
WS2_32.dll, WS2HELP.dll, rtutils.dll,
MpShHook.dll, MSVCR80.dll, MSVCP80.dll,
rsaenh.dll, webcheck.dll, stobject.dll,
BatMeter.dll, POWRPROF.dll, WTSAPI32.dll,
WPDShServiceObj.dll, WINHTTP.dll,
mydocs.dll, PortableDeviceTypes.dll,
PortableDeviceApi.dll, MLANG.dll,
wdmaud.drv, MSCTF.dll, msacm32.drv,
midimap.dll, WZCSAPI.DLL, mslbui.dll,
drprov.dll, ntlanman.dll, NETUI0.dll,
NETUI1.dll, NETRAP.dll, davclnt.dll,
SXS.DLL, FolderSizeColumn.dll,
awxDTools.dll, MFC80.DLL, MFC80ENU.DLL,
PDFShell.dll, dBShell.dll,
FileMenuTools.dll, WINSPOOL.DRV, oledlg.dll,
browselc.dll, SDHelper.dll, faultrep.dll,
olepro32.dll, shdoclc.dll, jscript.dll,
RASAPI32.dll, rasman.dll, TAPI32.dll,
msv1_0.dll, sensapi.dll, dfshim.dll,
mscoree.dll, wmvcore.dll, WMASF.DLL,
wzcdlg.dll, sti.dll, CFGMGR32.dll,
rarext.dll, UnlockerCOM.dll,
CopyToSendTo.dll, avgse.dll, MSVCP71.dll,
MSVCR71.dll

I don't mean to hijack this thread and I'll create a new one if needed.
Reply #47 Top

Well, I figured I'd try something and it's made the matter worse. I installed Stardock Central and it found that WB needed to be updated. I update that and installed Theme Manager as well. Now whenever I apply a skin from either WB or TM it reverts to Windows Classic. I'll be making my own post now.
Reply #48 Top
Well...

I've upgraded the nVidia drivers to 163.71 (by uninstalling and installing new from scratch). This has meant I have now downgraded nView to 111.17.

And I still have the original problem. So I have to either Disable all nView settings, or just for 'explorer' (using the nView Applications tab) to workaround.
Reply #49 Top

Well...

I've upgraded the nVidia drivers to 163.71 (by uninstalling and installing new from scratch). This has meant I have now downgraded nView to 111.17.

And I still have the original problem. So I have to either Disable all nView settings, or just for 'explorer' (using the nView Applications tab) to workaround.



oh no - mines ok now - totally and I have mine enabled, so perhaps its one of the settigs in there thats causing it.
Reply #50 Top
Well, life's too short, and I'm happy to leave nView disabled.

Pleased yours is working, SS.   Maybe catch you again sometime.


Thanks everyone,
sypolog