[solved]Explorer crashes after login/modules flb.dll tlb.dll

[edit: Issue resolved. Assignment of a custom .ico to a folder in the FLB toolbar caused the crash. For details see below.]

Hi,

I deterministically keep getting Explorer crashes at login. The event viewer shows me, it's flb.dll (I tried with TLB too, same result, crash in tlb.dll). The crash only happens, if the FLB toolbar already is enabled at login. It happens around the moment, when the Toolbar selection menu is populated with the entry of FreeLaunchBar. The fault offset is always the same. Explorer restarts and continues the startup process, but tray icons and other helpers loaded before the crash seem to have gone too (this includes the crashed FLB).

Disabling the FLB taskbar during reboots helps. I can enable it manually and it works as intended. Uninstalling FLB helps too, but that's not the point 'cause in general I love this gadget ;-)

Maybe it's an interference with another piece of software tough I can't fingerpoint a candidate right away. If you would like to get a dump of my installed applications and tools, could you please name me a tool to create such a dump? I'll also try to bisect and isolate any interference later.

Thanks for any help and Best regards,
Leo

-----------------------------------------------------------
Windows Vista SP1 english up-to-date.
Lenovo W700 using most of the Thinkvantage Software.
Kaspersky, Office 2007 german.

Faulting application Explorer.EXE, version 6.0.6001.18164, time stamp 0x4907e242, faulting module flb.dll, version 2.0.0.0, time stamp 0x49e3b92c, exception code 0xc0000005, fault offset 0x0004a74d, process id 0x1680, application start time 0x01c9d5a2816f6134.

Code:

Log Name:      Application
Source:        Application Error
Date:          15.05.2009 23:17:22
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      e3cbrl
Description:
Faulting application Explorer.EXE, version 6.0.6001.18164, time stamp 0x4907e242, faulting module flb.dll, version 2.0.0.0, time stamp 0x49e3b92c, exception code 0xc0000005, fault offset 0x0004a74d, process id 0x1680, application start time 0x01c9d5a2816f6134.
Event Xml:
<Event>
  <System>
    <Provider>
    <EventID>1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated>
    <EventRecordID>3120</EventRecordID>
    <Channel>Application</Channel>
    <Computer>e3cbrl</Computer>
    <Security>
  </System>
  <EventData>
    <Data>Explorer.EXE</Data>
    <Data>6.0.6001.18164</Data>
    <Data>4907e242</Data>
    <Data>flb.dll</Data>
    <Data>2.0.0.0</Data>
    <Data>49e3b92c</Data>
    <Data>c0000005</Data>
    <Data>0004a74d</Data>
    <Data>1680</Data>
    <Data>01c9d5a2816f6134</Data>
  </EventData>
</Event>

Please can you ZIP and send me the toolbar folder (<!-- e --><a href="mailtoupport@truelaunchbar.com">support@truelaunchbar.com</a><!-- e -->). By default this folder is located here: %APPDATA%\Microsoft\Internet Explorer\quick Launch
(just type this string into RUN dialog).

I'll try to reproduce the bug with your settings.

Assignment of a custom .ico to a folder in the FLB toolbar caused the crash.

Normally, you choose an icon out of a .dll or .exe. (Actually you define a reference to the n-th icon inside the .dll/.exe)

I made an .ico icon file from a screenshot with IrfanView. Then I dared to assign this .ico to a folder.
Steps to reproduce:
- create a new "menu" (actually a folder in %APPDATA%\Microsoft\Internet Explorer\quick Launch) in the FLB toolbar
- right click on the new folder, go to Appearance -> Change Icon
- assign it the evil icon attached to this post
- reboot and watch explorer crash right after login

(My guess about the problem is that FLB tries to load icon ressource 0 from the .ico despite the .ico is the icon itself. But I'm not too sure about this, because starting FLB at a later moment works.)

Feel free to correct me if I'm wrong on anything.

Thank you very much for investigation. But I can't to reproduce the bug on my system Please check your PM.