What the hell is Sysfader.exe ?

It's another Microsoft "Added Feature". Like with most M$ unrequested features, turn it off.

To get rid of this problem all you need to do is this:

Press Win Flag + Pause break key. If you don't have the Win Flag key just right click on my computer and select properties.
Go to the 'Advanced' tab
Under 'Performance' click on 'Settings'
Under the 'Visual Effects' tab uncheck the first four check boxes
Click on 'OK'

http://beyondteck.blogspot.com/2006/05/how-to-stop-sysfaderexe-error.html

 

I experienced this same problem. A lot of the proposed solutions here didn't work. What finally seems to have solved the problem for me was turning off the Sandboxie toolbar in IE6 (View-Toolbars).

 

The Sysfader error is triggered when iexplore.exe makes the API Function call "mshtml!DllGetClassObject(6365413c)" to the %WINDIR%\system32\mshtml.dll library. It could be a virus/worm that has disabled bits of ie's code (see below), or it may be due to some needed dependancy library(s) that may have been un-installed, & is required for mshtml.dll to complete the called function, & return it's result to iexplore.exe, or ie's web activex control. If that still is not the problem, then iexplore.exe may have requested mshtml.dll to parse corrupted data thus receiving rubbish in return, or an un-wanted program is messing around. If that still is'nt it, then maybe the registry has collision prone entries that is causing IE to try to execute opposing instructions at app termination causing it to get confused, & hang... triggering sysfader (who was told that IE is shutting down) to crash right along with it. Just as a precaution, replace the %WINDIR%\system32\mshtml.dll library with an original copy from either your Win CD, or a trusted dll download site.... it may be corrupted.

It seems to cause the same problem in software that uses the Internet explorer's web control, and makes a similar call.

*----> State Dump for Thread Id 0x1698 <----*
eax=008b52f0 ebx=04b06e68 ecx=03dca5f4 edx=00002539 esi=04b06e68 edi=04a084f8
eip=6365413c esp=0534fad8 ebp=0534fadc iopl=0 nv up ei pl nz na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010206

function: mshtml!DllGetClassObject
63654127 56 push esi
63654128 8bf1 mov esi,ecx
6365412a 8b06 mov eax,[esi]
6365412c 85c0 test eax,eax
6365412e 0f858077fdff jne mshtml!DllGetClassObject+0x90ac9 (6362b8b4)
63654134 832600 and dword ptr [esi],0x0
63654137 5e pop esi
63654138 c3 ret
63654139 8b08 mov ecx,[eax]
6365413b 50 push eax
6365413c ff5108 call dword ptr [ecx+0x8] ds:0023:03dca5fc=??.??.?? The sysfader error message kicks in here.
6365413f ebdb jmp mshtml!DllGetClassObject+0xb9331 (6365411c)
63654141 90 nop
63654142 90 nop
63654143 90 nop Hackers/Crackers... notice anything strange here?
63654144 90 nop
63654145 90 nop
63654146 ff2598105863 jmp dword ptr [mshtml+0x1098 ( 63581098 )]
6365414c 90 nop
6365414d 90 nop How about here?
6365414e 90 nop

[/SIZE]*----> Stack Back Trace <----*
ChildEBP RetAddr Args to Child

WARNING: Following frames may be wrong...

0534fadc 6365c1d4 008b52f0 00000001 6361f804 mshtml!DllGetClassObject+0xb9351
0534fb04 63612699 00000001 04a6eb80 6370a84d mshtml!DllGetClassObject+0xc13e9
0534fb20 6361266d 00000000 00000000 0534fb48 mshtml!DllGetClassObject+0x778ae
0534fb30 63614737 04a6eb80 049fe9b0 049fe8c8 mshtml!DllGetClassObject+0x77882
0534fb48 6370b15d 04a6eb80 00000000 049fe8c8 mshtml!DllGetClassObject+0x7994c
0534fb6c 6365c1a7 049fe8c8 77e6be20 041b6150 mshtml!MatchExactGetIDsOfNames+0x33fe5
0534fb80 6365b766 049fe8c8 0534fb98 636143de mshtml!DllGetClassObject+0xc13bc
0534fb8c 636143de 049fe8d8 0534fbbc 6362695b mshtml!DllGetClassObject+0xc097b
0534fb98 6362695b 041b617c 00000000 041b6150 mshtml!DllGetClassObject+0x795f3
0534fbbc 63703a5c 041b6150 04162ab0 04a2b858 mshtml!DllGetClassObject+0x8bb70
0534fbd8 637039a2 04162ab0 00000000 04162ab0 mshtml!MatchExactGetIDsOfNames+0x2c8e4
0534fbf4 63621c43 00000000 00000000 04162ab0 mshtml!MatchExactGetIDsOfNames+0x2c82a
0534fc18 63640da1 04162ab0 0534fc38 63623cb1 mshtml!DllGetClassObject+0x86e58
0534fc24 63623cb1 04162ab0 00000000 049fc5b0 mshtml!DllGetClassObject+0xa5fb6
0534fc38 6365b766 041b6150 0534fc6c 6370cc84 mshtml!DllGetClassObject+0x88ec6
0534fc44 6370cc84 041b6160 00000000 049fc5b0 mshtml!DllGetClassObject+0xc097b
0534fc6c 6370c735 00000000 00000000 00000000 mshtml!DllCanUnloadNow+0x1993
0534fc94 63610923 049fc5b0 04a48220 0534fcb0 mshtml!DllCanUnloadNow+0x1444
0534fca4 00aa6a9d 04a86db0 0534fcc4 00ac7364 mshtml!DllGetClassObject+0x75b38
0534fcb0 00ac7364 04a48220 04a480d4 04a41e5c IEFRAME!Ordinal300+0x5e87
0534fcc4 00ac760a 00000000 0534fce0 00ac5577 IEFRAME!Ordinal101+0x6400
0534fcd0 00ac5577 04a41e5c 00000002 0534fcf8 IEFRAME!Ordinal101+0x66a6
0534fce0 00ac7284 04a41e5c 00000002 00000000 IEFRAME!Ordinal101+0x4613
0534fcf8 00abbfd8 04a480d4 01d40612 00000002 IEFRAME!Ordinal101+0x6320
0534fd14 00ab1633 04a41e5c 01d40612 00000002 IEFRAME!SetQueryNetSessionCount+0x69b4
0534fd7c 00ac4a29 04a41e5c 01d40612 00000002 IEFRAME!Ordinal224+0x94a3
0534fda4 7739c3b7 04a41e48 00000002 00000000 IEFRAME!Ordinal101+0x3ac5
0534fdd0 7739c484 00ab150b 01d40612 00000002 USER32!EnableMenuItem+0x4cd4
0534fe48 7739ca68 00000000 00ab150b 01d40612 USER32!EnableMenuItem+0x4da1
0534fea4 7739ce7a 007359c0 00000002 00000000 USER32!TranslateMessageEx+0xd5
0534fecc 7c82ec9e 0534fee4 00000018 0534ffdc USER32!MsgWaitForMultipleObjectsEx+0x126
0534ff1c 00ac50de 00000000 04a41e48 04a41e5c ntdll!KiUserCallbackDispatcher+0x2e
0534ff3c 00ac5032 00000000 00000000 041c7f88 IEFRAME!Ordinal101+0x417a
0534ff50 00ac4f6b 00000000 00000000 00000000 IEFRAME!Ordinal101+0x40ce
0534ffb8 77e6608b 04a41e48 00000000 00000000 IEFRAME!Ordinal101+0x4007
0534ffec 00000000 00aa3a37 041c7f88 00000000 kernel32!GetModuleFileNameA+0xeb

*----> Raw Stack Dump <----* [ADDRESS - HEX - ASCII]
000000000534fad8 f0 52 8b 00 04 fb 34 05 - d4 c1 65 63 f0 52 8b 00 .R....4...ec.R..
000000000534fae8 01 00 00 00 04 f8 61 63 - 00 00 00 00 f8 84 a0 04 ......ac........
000000000534faf8 00 00 00 00 f1 0c 62 63 - 80 eb a6 04 20 fb 34 05 ......bc.... .4.
000000000534fb08 99 26 61 63 01 00 00 00 - 80 eb a6 04 4d a8 70 63 .&ac........M.pc
000000000534fb18 80 eb a6 04 00 00 00 00 - 30 fb 34 05 6d 26 61 63 ........0.4.m&ac
000000000534fb28 00 00 00 00 00 00 00 00 - 48 fb 34 05 37 47 61 63 ........H.4.7Gac
000000000534fb38 80 eb a6 04 b0 e9 9f 04 - c8 e8 9f 04 00 00 00 00 ................
000000000534fb48 6c fb 34 05 5d b1 70 63 - 80 eb a6 04 00 00 00 00 l.4.].pc........
000000000534fb58 c8 e8 9f 04 00 00 00 00 - 6d 26 61 63 20 be e6 77 ........m&ac ..w
000000000534fb68 00 00 00 00 80 fb 34 05 - a7 c1 65 63 c8 e8 9f 04 ......4...ec....
000000000534fb78 20 be e6 77 50 61 1b 04 - 8c fb 34 05 66 b7 65 63 ..wPa....4.f.ec
000000000534fb88 c8 e8 9f 04 98 fb 34 05 - de 43 61 63 d8 e8 9f 04 ......4..Cac....
000000000534fb98 bc fb 34 05 5b 69 62 63 - 7c 61 1b 04 00 00 00 00 ..4.[ibc|a......
000000000534fba8 50 61 1b 04 00 00 00 00 - 6d 26 61 63 50 61 1b 04 Pa......m&acPa..
000000000534fbb8 c8 e8 9f 04 d8 fb 34 05 - 5c 3a 70 63 50 61 1b 04 ......4.\cPa..
000000000534fbc8 b0 2a 16 04 58 b8 a2 04 - 50 61 1b 04 80 eb a6 04 .*..X...Pa......
000000000534fbd8 f4 fb 34 05 a2 39 70 63 - b0 2a 16 04 00 00 00 00 ..4..9pc.*......
000000000534fbe8 b0 2a 16 04 00 00 00 00 - 20 be e6 77 18 fc 34 05 .*...... ..w..4.
000000000534fbf8 43 1c 62 63 00 00 00 00 - 00 00 00 00 b0 2a 16 04 C.bc.........*..
000000000534fc08 c0 c9 9f 04 6d 26 61 63 - 01 00 00 00 b0 2a 16 04 ....m&ac.....*..

 

In XP I right clicked on my screen and went to properties and then to appearance and clicked on the effects tab and changed the effect from fade to scroll ...either way worked for me I no longer get the error when shutting down my PC

ot you can uncheck it and disable it I tried that and it worked too

 

Downloading software like GetRight, & others are some of the guilty parties who cause this situation in IE.

Remove all related add-ons of the offending software from IE, & un-install whatever software it is from your system. Make sure that IE is totally terminated before you attempt an un-install. Use TaskManager to terminate iexplore.exe if it is still active in memory after you've closed it. Close any other programs that may be useing IE's activex control like instant messengers. When you have completed the un-install, run IE again, & close it to see if it still hangs on its close request.

Still researching this problem.

 

Re: What the hell is Sysfader.exe ? SOLUTION??

I apologize in advance if anyone has already posted here, or anywhere else for that matter, a solution for this

stupendously aggravating IE7 error or a version similar. Being as how I've searched shallow and deep for a proper

comprehendence and possible end for both Sysfader and a generic 'cannot write to memory' error when opening IE7, I

can only speculate from the enmasse of similar postings, that I am not alone. I can also speculate that either

Microsoft is all too busy with the rolling out of the seemingly debaucherous and holey-coded Vista, or they can't

figure it out either. So once again, it is us fellow geeks, the end user, the uber-obsessive computer recluses, that

must alter and diminish standards set by Microsoft to gain basic and consistent useability.

I tried most of the fixes for these aforementioned IE7 errors, with the exception to Restore points since this is my

fiance's computer, and while so far the Sysfader error has stopped, the other error above hadn't. And then I made

what I believe at this short time span between changing settings, testing and writing this update, is a respectable

discovery, and an applicable fix for IE7 crashing once if not several times on first open, claiming 'cannot write to

memory'. 'Send Microsoft error report'? Why must I continue to send them when they go unanswered?

This is what I came up with. Email me if it works for you, and spread the word as well. Post it on every site

imaginable. It is as follows:

When earlier this morning I began to deeply search for the answer to the Sysfader error, I came across this site, http://beyondteck.blogspot.com/2006/05/how-to-stop-sysfaderexe-error.html

which is the one I mentioned earlier by typing in 'Sysfader error how to fix?'(without the ''s):

http://beyondteck.blogspot.com/2006/05/how-to-stop-sysfaderexe-error.html which also seems to kick back to this

forum board, so I do not know the origin of the posting, but nevertheless... so without taking credit for the

Sysfader fix by my recap, here it is:

1. If you have a Windows key on your keyboard, press that and the Pause button simutaniously and that will bring up

your System settings (better known as Alt+doubleclick on My Computer, or rightclick/properties on My Computer).

2. Go to the Advanced Tab and click Settings on the Performance option.

3. The third tab over says "Data Execution Prevention". What I gathered from the help file (which is like another

language in itself sometimes...or extremely vague and useless) is that while this option monitoring all programs, it

looks for programs using memory incorrectly, which it will associate with the likes of a virus or other malicious

software, and cause it to error out and force it to close. Then it hit me, 'if someone is overloading IE7 with

homepage tabs, and multitasking with other IE windows open outside of the main one, shouldn't that constitute as

poor memory usage, therefore resulting in the DEP to perk up and close down the program? Especially if a users

performance settings are set to 'appearance' and not 'performance'. I believe as well that DEP remembers such

programs repeatedly utilizing poor memory allocation and automatically shuts it down as it opens. This is the only

solution I can apply to my own experience. After about the first week of upgrading to IE7, this began to happen. I

open IE7, my homepages begin to load, I get the error and it crashes. I open it again, and it's fine. But if I shut

it down for any significant amount of time, and decide to reopen, same result. So this is my solution thus:

4. So, going back to the DEP tab, I chose the second option, "Turn on DEP for all programs and services except those

I select" and simply added the IE7 .exe to the list, clicked apply and ok. It asked me to reboot for the changes to

be made, and so I did.

5. Now to test it:

I rebooted as I mentioned, and immediately opened IE7 in excitement expecting dismay, and it did just that...it

opened! Without crashing! So I opened another, and another, and 5 more hoping the memory would funk out and crash

all 7 windows. I didn't get the response I was going for. In fact, only 4 of the windows completely loaded, the

other 3 still churning away; white pages of purgatory.

I closed them all, and opened IE7 again. Loaded. Waited, opened. Loaded. Walked to the store, opened. Loaded!
Now I have but one more test to run, which is again to reboot and attempt it all over again...

(INTERLUDE)

...Rebooted, opened IE7, and it immediately closed itself, but no error.
...repeated the process, and got the same results. It opens, closes itself, but no error message.
This is only a short testing process so far, and like aforementioned, I believe the DEP has a memory of the programs

it monitors, so in theory, it should phase IE7 out the more you use it, but by the immediate test results, that

theory looks bleak. It seems that even the DEP option doesn't seem to do what it should. Maybe there is another

process tied to ie.exe that should also be added to the exception list which I am not aware of. If anyone should

find the combination of settings that correctly disable this atrocious IE7 behaviour, kindly post it and email me as

well. Until then, I will be following my own update advice.

Sorry if this post has been a grand waste of time, but I know that there are more qualified computer geeks out

there, and maybe with this information, a solution is within grasp. One step closer is never a bad thing.


UPDATE:

Simply: Use Firefox v2. That will solve the IE7 problem, and any others that WILL arise.

 

so i dont get the sysfader thing till i try to open network places, then i get an explorer error and a drwatson error, any help would be great

 

This worked for me: use an administrator account, and re-install Flash. This doesn't seem to be related to video card drivers or anything like that. Just re-install Flash, that's it.

 

We had a user with this EXACT issue while in IE (WinXP Pro OS) and it turns out the fix was this (definitely NOT a virus issue):
An a different pc we went to the same webpage where he was receiving this error and it opened a PDF.
We realized the problem was Adobe. His machine had Adobe Pro 6 installed AND Acrobat Reader 7.0.
Uninstalled Acrobat Reader 7.0, then rebooted.
Upon reboot, opened Adobe, at which point a message appeared asking if we'd like to be able to view PDF's in the browser. Chose yes and closed Adobe.
Visited the webpage again and user no longer receives the Sysfader.exe error.
Problem Fixed.
-Brian

 

I had huge problems with SysFader, Auto Suggest Drop Down, and Connections Tray. All would freeze my computer several times each day so that I could not get to any of my web sites, using Internet Explorer 7. Also, Internet Explorer 7 would many times each day say thay it was shutting down because it had encountered a problem and apologized for the inconvenience. I tried several solutions and nothing worked. Then I noticed that somehow my problems seemed to be connected with my attempts to connect to my e-mail service, NetZero. I also remembered that I had disconnected my Windows Firewall at about the same time that I started having trouble with SysFader, etc. I went to the Control Panel and I reinstated and connected Windows Firewall again. Since them I have had absolutely no trouble with Sys Fader, Auto Suggest Drop Down, Connections Tray, or Internet Explorer 7. Everything is perfectly OK. Such a simple fix and it has worked perfectly and beautifully. I hope this helps others with the same SysFader problem.

 

I just got onto my computer and it has slowed down something terribly and my task manager and documents and microsoft word will not respond to the close out command. is this a hacker playing with my computer or is it a program I can delete from my files? I have read several of the posts here and it seem as if nothing is really helping to resolve this problem. why cant people just leave other's belongings alone?

 

Hello lisa bencaz

Is your problem related to sysfader.exe?
If not, please start a new thread with detailed description of your system, security software you're using, recent changes you made, your surfing habits, etc. More details are needed, otherwise it's a guesswork.

From afar, I wouldn't say it's a hacker playing with your system, more likely you picked up some malware - a virus. However, these forums don't provide professional assistance in malware cleaning. See this thread, it should help you to take further steps.

Cheers.

 

Sorry to join this thread late.(Judging from the OP very late)
Just info from Winpatrol on Sysfader.exe

 

Well, I cant launch msn messenger, and lo and behold, every time i click the icon, a little sysfader appears in my taskmanager, which disappears in a couple seconds