5
Vote

Immediately crashes! OH GOD

description

Running Gateway T-Series Laptop Vista Home Edition (x86), ran as administrator.
 
Description:
Stopped working
 
Problem signature:
Problem Event Name: APPCRASH
Application Name: WBFSManager.exe
Application Version: 3.0.1.0
Application Timestamp: 49fe57c1
Fault Module Name: KERNEL32.dll
Fault Module Version: 6.0.6001.18215
Fault Module Timestamp: 49953395
Exception Code: e0434f4d
Exception Offset: 000442eb
OS Version: 6.0.6001.2.1.0.768.3
Locale ID: 1033
 
Please help!

comments

johncro13 wrote Dec 27, 2009 at 3:29 PM

I have EXACTLY the same problem using a Windows 7 machine. I go to Control Panel > Administrative Tools > Component Services. Under Custom Views > Summary Page events, WBFS Manager is the only application I see - repeatedly! Each instance of the error reads "Event 1000, Application Error" with the EventData of:
WBFSManager.exe
3.0.1.0
49fe57c1
KERNELBASE.dll
6.1.7600.16385
4a5bdaae
e0434f4d
00009617

So, what does it all mean? I'm interested in the fact that the Application timestamp and exception code are the same for what is essentially the same DLL. Googling those numbers with bring you essentially nowhere.

I'm willing to bet there are some other folks having the same issue. Maybe someone here can help recognize the issue.

Vicious_Manjunk wrote Mar 23, 2010 at 6:35 PM

I'm also on Vista 32bit (x86) I have the latest update and am having the same problems as the other post. Kernel32.dll error.. However just a few weeks ago it was working fine.. So i'm currently trying to sort out what i changed or added since it last worked. Will let you know if i find anything. If this has already been solved please someone let me know.. Thanks

RedWarlock wrote May 19, 2011 at 9:56 PM

What i have been able to precipitate from my investigation on the issue is if you are ruing the program with the proper UAC (Administrator) than the issue is highly likely to be an issue with either corrupt files or the registry. I have found a solution that seems to work relatively well. It involves wiping<?sp? out all traces of .net framework in all versions. I have seen many cases where .net framework 2.0 took over and that was causing crashes. if you look in the system event logger after you try to run WBFS manager you will most likely see something to the nature of well here is a cut and paste. (from applications log file)
"5/17/2011 1:39:54 PM .NET Runtime 2.0 Error Reporting Error None 1000 N/A HOMEWORK Faulting application wbfsmanager.exe, version 3.0.1.0, stamp 49fe57d5, faulting module kernel32.dll, version 5.1.2600.5781, stamp 49c4f482, debug? 0, fault address 0x00012afb."
My purposed solution (all files can be found by Google or Microsoft's website)
For those out there that have problems getting WBFS manager to load after trying to re-install .net frame work 3.5 sp1 do the following
  1. download as follows.
    A. dotnetfx cleanup tool
    B.Microsoft .NET Framework 3.5 Service pack 1 (Full Package)
  2. run dotnetfx cleanup tool
  3. leave the default selected ".NET Framework - All Versions"
  4. click "Cleanup Now"
    (it will take a while for the cleanup to complete)
  5. REBOOT! after the cleanup has completed
  6. install Microsoft .NET Framework 3.5 Service pack 1 (Full Package)
  7. REBOOT!! (yes again it is necessary)
  8. install the latest version of WBFS manager
    9.enjoy
  9. help others with the same process.
    (optional)
    un-install .NET Framework 3.5 Service pack 1 first