RupeeClock RupeeClock

Explorer repeatedly crashing

▼

Explorer repeatedly crashing

Suspected cause is converted MSStyle

from WinCustomize Forums

I recently upgraded to Windows 7 and WindowBlinds 7, and been enjoying it. My skin of choice is Luna Element 5.1 Black, and using the MSstyle converter the skin looks amazing on Win7, despite being designed for WinXP.

Unfortunately though, it occasionally causes explorer.exe to crash, this is not limited to one system either, both my desktop PC and laptop are effected. Specifically, sometimes the taskbar freezes up, doesn't respond, and has to be closed. And it reboots a few seconds later. I don't know how to reproduce this, but it seems to be most frequent when I am multi-tasking.

The same thing also happens with the blue version of Luna Element 5.1. I haven't tried any other skins, but I believe the MSStyle conversion may be causing this bug.

The skin conversion is also not compatible with things such as transparency, and I set my desktop to Windows Classic before applying skin through WindowBlinds.

Is there an immediate fix available, or do I need to wait for a software update?

Thanks

Laptop:
Your computer has a Windows Experience Index base score of 3.1
Your Windows Graphics Experience score is 3.5

WindowBlinds version : WindowBlinds 7.0 (build 230 - Windows 7 Edition)

WindowBlinds is installed correctly on this PC
WindowBlinds appears to be activated on this PC
(Generic PnP Monitor) 1 is attached to Mobile Intel(R) 965 Express Chipset Family

Wblind.dll         2009/11/16 12:43:20
Wbsrv.dll         2009/11/12 09:19:07
SevenConfig.exe         2009/11/12 11:16:53
Wbload.exe         2009/11/10 13:53:12
Wbhelp.dll         2009/06/04 15:14:07
Tray.dll              2009/10/23 19:12:19
Wbload.dll              2009/09/25 07:41:29
Screen.exe         2009/11/07 12:39:26

Also, the crash details for explorer.exe if it helps

Description:
  A problem caused this program to stop interacting with Windows.

Problem signature:
  Problem Event Name:    AppHangB1
  Application Name:    explorer.exe
  Application Version:    6.1.7600.16404
  Application Timestamp:    4a765076
  Hang Signature:    5afe
  Hang Type:    0
  OS Version:    6.1.7600.2.0.0.256.48
  Locale ID:    2057
  Additional Hang Signature 1:    5afe2631333b2f1a53d841d4fc88eda2
  Additional Hang Signature 2:    7b61
  Additional Hang Signature 3:    7b61afbce4f16d51db8992873f2355d7
  Additional Hang Signature 4:    5afe
  Additional Hang Signature 5:    5afe2631333b2f1a53d841d4fc88eda2
  Additional Hang Signature 6:    7b61
  Additional Hang Signature 7:    7b61afbce4f16d51db8992873f2355d7

windowblinds
8,736 views 30 replies
Reply #26 from WinCustomize Forums Top

It is still crashing, unfortunately. :(

Log Name:      Application
Source:        Application Error
Date:          12/12/2009 7:48:36 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:     
Description:
Faulting application Explorer.EXE, version 6.0.6002.18005, time stamp 0x49e01da5, faulting module WBLIND.dll, version 7.0.1.0, time stamp 0x4b216657, exception code 0xc0000005, fault offset 0x0001829a, process id 0x71c, application start time 0x01ca7b7af78054b0.

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

WindowBlinds version : WindowBlinds 7.01 (build 234 x86 - Vista Edition)

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

Wblind.dll      2009/12/10 16:58:20
Wbsrv.dll      2009/12/03 13:44:30
SevenConfig.exe      2009/12/03 13:43:22
Wbload.exe      2009/12/03 13:43:12
Wbhelp.dll      2009/10/07 14:35:07
Tray.dll           2009/10/21 08:13:19
Wbload.dll           2009/09/25 07:41:28
Screen.exe      2009/12/03 13:43:26

 

Reply #27 from WinCustomize Forums Top

Quoting happycamper88, reply 26
It is still crashing, unfortunately.



Log Name:      Application
Source:        Application Error
Date:          12/12/2009 7:48:36 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:     
Description:
Faulting application Explorer.EXE, version 6.0.6002.18005, time stamp 0x49e01da5, faulting module WBLIND.dll, version 7.0.1.0, time stamp 0x4b216657, exception code 0xc0000005, fault offset 0x0001829a, process id 0x71c, application start time 0x01ca7b7af78054b0.
 
End of happycamper88's quote

Given your crashes both have very different addresses, I don't think you are experiencing the same issue as RupeeClock had.  What skin are you using?  Does it happen with other skins?

Are you also using Deskscapes or Fences?

Offworld Trading Company
Reply #28 from WinCustomize Forums Top

These crashes happened while I used two different skins.

The first was "Flash - Live System" by MrPaul & the second was "Windows 7 Ultimate RC3" by Sagor.

I am not using Deskcapes or Fences currently. I am using Right Click & Object Dock Plus though. I have a tabbed dock placed at the taskbar position. I don't know if any of that makes any difference. (??)

I will set a different skin for the next day or so and see if it crashes again. :sun:

Reply #29 from WinCustomize Forums Top

Quoting happycamper88, reply 28
These crashes happened while I used two different skins.

The first was "Flash - Live System" by MrPaul & the second was "Windows 7 Ultimate RC3" by Sagor.

I am not using Deskcapes or Fences currently. I am using Right Click & Object Dock Plus though. I have a tabbed dock placed at the taskbar position. I don't know if any of that makes any difference. (??)

I will set a different skin for the next day or so and see if it crashes again.
End of happycamper88's quote

Can you download this  : http://storage.stardock.com/files/smartexception.exe and install it and make sure it is running.

If you encounter another explorer crash you should be able to double click on the system tray icon for smart exception, find the crash in the list and click email selected exception.  This should open a window where you can click generate exception and an explorer window with a .zip should open. 

E-mail that zip to my first name at stardock.com and I should be able to look into the crash further.  It appears to be some form of memory corruption which is why we need the full call stack rather than just where it crashed.