Windows Explorer vs WBLIND64.dll

When I boot my new PC into windows (Vista64) for some reason it tries to open windows explorer, which fails & gives a "Windows Explorer has stopped working", before sometimes restarting explorer successfully. It also happens intermittently while i'm working.

I have no idea why it is trying to do this, let alone failing, but error logs are pointing to WBLIND64.dll being behind it somehow.

I've played about turning things on & off in Windows blinds & rebooting, but it doesn't seem to make much of a difference. I thought it would possibly have been related to using the Explorer background settings, but disabling them hasn't helped.

Anyone know how I can fix this?

 

 

 

 

21,373 views 16 replies
Reply #1 Top

What version of WindowBlinds do you have installed?

+1 Loading…
Reply #2 Top

WindowsBlinds info:

Your computer has a Windows Experience Index base score of 5.7
Your Windows Graphics Experience score is 5.9

WindowBlinds version : WindowBlinds 6.2 (build 102 x86 - Vista Edition) - 64 bit OS

WindowBlinds is installed correctly on this PC
WindowBlinds appears to be activated on this PC
(SyncMaster 930B/930BC/930BF/198B(Digital)) 1 is attached to ATI Radeon HD 4870 X2

Wblind.dll      2008/07/22 10:08:20
Wblind64.dll      2008/07/22 10:08:21
Wbsrv.dll      2008/07/22 10:11:45
Wbconfig.exe      2008/07/22 10:10:32
Wbload.exe      2008/04/28 11:35:14
Wbhelp.dll      2008/04/28 11:35:07
Tray.dll           2008/04/28 11:35:21
Wbload.dll           2007/09/26 11:53:28
Screen.exe      2008/07/22 10:10:09

 

Full example of error (6/9/08):

Problem signature

Problem Event Name: APPCRASH

Application Name: Explorer.EXE

Application Version: 6.0.6001.18000

Application Timestamp: 4791970c

Fault Module Name: WBLIND64.dll

Fault Module Version: 6.2.0.0

Fault Module Timestamp: 4884bf6a

Exception Code: c00000fd

Exception Offset: 000000000000aa9a

OS Version: 6.0.6001.2.1.0.768.3

Locale ID: 3081

Additional Information 1: e694

Additional Information 2: 09d00768572c0c152c8781be1f780154

Additional Information 3: 85d2

Additional Information 4: e9c96ed825ffb5f1d5998ae9ec7d21c0

Extra information about the problem

Bucket ID: 2029745

 

Reply #3 Top

I have the same problem with WindowBlinds 6.1/6.2. In fact, in the past month Windows Explorer has crashed no less than 36 times with the same exception (0x00000005: INVALID_PROCESS_ATTACH_ATTEMPT). The fault module being identified as WBLIND64.dll. The 'crash' is predominently at Windows start up, but not exclusively. System information:

Your computer has a Windows Experience Index base score of 5.7
Your Windows Graphics Experience score is 5.9

WindowBlinds version : WindowBlinds 6.2 (build 102 x86 - Vista Edition) - 64 bit OS

WindowBlinds is installed correctly on this PC
WindowBlinds appears to be activated on this PC
(SyncMaster 2232BW/2232GW/2232GW Plus,SyncMaster Magic CX2232GW(Digital)) 1 is attached to NVIDIA GeForce GTX 260

Wblind.dll         2008/07/22 10:53:20
Wblind64.dll         2008/07/22 10:53:21
Wbsrv.dll         2008/07/22 10:53:45
Wbconfig.exe         2008/07/22 10:53:32
Wbload.exe         2008/04/26 16:14:14
Wbhelp.dll         2008/04/26 16:14:07
Tray.dll              2008/04/26 16:14:21
Wbload.dll              2008/04/26 16:14:28

Reply #4 Top

My problem seems quite simmiliar to this (the Explorer window opens after the taskbar reappears). From the dates on the above posts, this issue hasn't seen any action for about a month. Any updates from the original posters or on the issue itself?

My info:

Your computer has a Windows Experience Index base score of 5.9
Your Windows Graphics Experience score is 5.9

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

WindowBlinds is installed correctly on this PC
WindowBlinds appears to be activated on this PC
(Generic PnP Monitor) 1 is attached to NVIDIA GeForce 9800 GT

Wblind.dll      2008/09/22 17:59:20
Wblind64.dll      2008/09/24 18:34:30
Wbsrv.dll      2008/09/22 17:59:13
Wbconfig.exe      2008/09/22 17:59:32
Wbload.exe      2008/03/30 12:27:14
Wbhelp.dll      2007/08/27 11:54:07
Tray.dll           2007/09/12 17:58:21
Wbload.dll           2007/09/26 11:53:28
Screen.exe      2008/07/22 10:10:09

Reply #5 Top

For those of you who had the issue, did upgrading to 6.3 help?

Reply #6 Top

I have been having the same issue and it is still happening since the latest update. However it has been occuring less frequently since the update.

Reply #8 Top

Just checked the error log & pretty much everytime I boot, I get that error still.

6.3 hasn't made a difference, although it did have issues installing & took a few reboots to get straight.

Other software has issues occasionally during the boot process too (CCC, Gigabyte Easy Tune tool), but they do not effect explorer & still appear to be functional even after I'm told they are not.

There is another file dispersed amongst all the WBLIND64 errors, wbhelp64.dll, but it crashes Explorer a lot less frequently.

I currently have 71 Windows Explorer problems recorded & most of them are to do with the WBLIND64.DLL.

Other than the explorer crashes Windows Blinds seems to be working as intended.

Happy to provide any further info, logs etc if they'll help?

Reply #9 Top

I am also having this problem mulitple times a day. Pretty much same exact error messages as the ones posted above.

Reply #10 Top

I too, am still experiencing this problem. There has been no peceivable improvement with v6.3. It mainly, but not exclusively, happens after Vista has loaded. One thing I have noticed is that after explorer crashes, AVG anti-virus scanner starts up although it isn't really running as such. This is quite weird and may be significant!

Reply #11 Top

bump; also getting crashes in Windows Explorer:

 

Problem signature

Problem Event Name: APPCRASH

Application Name: Explorer.EXE

Application Version: 6.0.6001.18000

Application Timestamp: 4791970c

Fault Module Name: WBLIND64.dll

Fault Module Version: 6.3.0.0

Fault Module Timestamp: 48f8b6d1

Exception Code: c00000fd

Exception Offset: 000000000000e5ca

OS Version: 6.0.6001.2.1.0.256.1

Locale ID: 1053

Additional Information 1: e694

Additional Information 2: 09d00768572c0c152c8781be1f780154

Additional Information 3: 2397

Additional Information 4: b3befbb9db50c45033f940c9d0e3d743

Extra information about the problem

Bucket ID: 2816837

Your computer has a Windows Experience Index base score of 5.9
Your Windows Graphics Experience score is 5.9

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

WindowBlinds is installed correctly on this PC
WindowBlinds appears to be activated on this PC
(NEC MultiSync 20WGX2(Digital)) 1 is attached to NVIDIA GeForce GTX 280

Wblind.dll      2008/09/22 22:59:20
Wblind64.dll      2008/10/17 21:12:13
Wbsrv.dll      2008/09/22 22:59:13
Wbconfig.exe      2008/09/22 22:59:32
Wbload.exe      2008/04/28 17:35:14
Wbhelp.dll      2008/04/28 17:35:07
Tray.dll           2008/04/28 17:35:21
Wbload.dll           2007/09/26 11:53:28
Screen.exe      2008/07/22 16:10:09

Using KapsulOS as Windowblinds skin, from MyColors.

Reply #12 Top

So far since the latest update I have not had any crashes...might still be too early to tell but I am really hoping that the problem has been fixed...

Reply #14 Top

These explorer errors & the Punkbuster problems have meant that I've not been using Windows Blinds for the past month or so.

The other night I got tired of Aeroglass & decided to try using WB again. I was not surprised to see that the Explorer problem hadn't gone away, but I was surprised to find that a few other issues that I'd never even considered being related to WB, returned suddenly.

I have a Logitech G15 keyboard, the second version, & had been having issues with the software for the LCD not remembering it's settings. Certain aspects of the LCD's software I had shut down or changed, but after a reboot they'd come straight back. For example I turned of the stop watch program & stopped all the apps scrolling, prefering to make changes when & if I needed them. To be honest I hadn't noticed that they'd gone away until I restarted WB & found things were suddenly ignoring any of the settings I made in the LCD's software again. I had though the uissues here were permission based & had set the LCD software to "Run as Admin" which seemed to fix things briefly, but the issues still returned.

I also hadn't specifically noticed that a lot of other apps that load during start up had stopped failing in a similar manner to windows Explorer, until I re-enabled WB & suddenly they are all back again. Things like the Catalyst Control Centre & Gigabyte (Mobo) tools failing during start up.

My other PC also has WB on it & pretty much the same apps, but is XP & I have no issues with it & WB at all.

WB version is still 6.3.

Has anyone had any success in sorting this out yet? It's driving me crazy! Is anyone using Vista 64 Home Premium + Windows Blinds & not experiencing these issues?

 

Reply #15 Top

Quoting Lord, reply 14

Has anyone had any success in sorting this out yet? It's driving me crazy! Is anyone using Vista 64 Home Premium + Windows Blinds & not experiencing these issues?

Simple answer, No! I've had over 100 explorer 'stop working' errors with Wblind64.dll and even occasionally Wbhelp.dll since August last year, I'm beginning to wonder what Microsoft does with all the reports it asks me to send them. It interferes with AVG, or maybe it's the explorer crash, causing it to 'launch' the system tray scanning icon, although it isn't actually running. After the explorer crash it will sometimes cause my complete system to slow down, which can only be corrected by logging off and on again. I do not have this problem with PCs running XP or Vista 32, so this is definitely a 64 bit related problem, maybe due to WB not being a fully compliant 64 bit program, it is mostly run as 32 bit.

Like yourself, I've given up hope of this problem being sorted out anytime soon, if ever and will be reluctant to purchase any future version of this software.

Reply #16 Top

I too am having same problem in vista premium i get error message

Problem Event Name: APPCRASH

Application Name: wbconfig.exe

Application Version: 6.1.0.0

Application Timestamp: 47b580d1

Fault Module Name: WBLIND.dll

Fault Module Version: 6.4.0.0

Fault Module Timestamp: 49623483

Exception Code: c0000005

Exception Offset: 00022e41

OS Version: 6.0.6001.2.1.0.768.3

Locale ID: 1033

Additional Information 1: 8fb6

Additional Information 2: 6293c6d71c6ea52502e1ceaf892bd7dc

Additional Information 3: f8c9

Additional Information 4: 7b28bf8f1fe394a16c5379c19084323a

Read our privacy statement:

 

http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409

 

anyone know what to do