Tip: Run a free scan for common Windows errors ad

re: SysFader will not fade away Saturday, June 1, 2002 at 4:13 pm Posted by Abel (3 messages posted) Hi jc, I just happened to see your message. After a month you may already have found an answer yourself, but in case not, here is some information: SysFader is not really a process, yet it is spawned as a process by a dll named browseui.dll when Internet Explorer wants to use transition effects. As is the design of win2k and winXP, IE is everywhere and these transition effects are also used when you exit your computer. This information I have from several newsgroups and my own experiences; MS doesn't say anything about it. It is not likely that SysFader itself is the culprit. In my case (I also had the same error you had) ZoneAlarm and PGP Personal Firewall were running simultaneously and blocking all kinds of stuff, avoiding processes to run and so on. After removing ZoneAlarm everything went fine again. The moral here: look at recently installed or changed processes/services/drivers and see what happens if you remove or disable them. Don't forget to look in the Run-keys in the registry. On Monday, April 29, 2002 at 5:18 pm, jc wrote: >When shutting down Win2000, I get a message that SysFader is not responding. I can >always hit the "cancel now" button but that is annoying. > >I have scanned the disk and the registry for sysfader. I cannot find it. Where >is it, and how do I get rid of it? [Reply or follow-up to this message] re: SysFader will not fade away Saturday, June 1, 2002 at 4:24 pm Posted by Abel (3 messages posted) Sorry, forgot to mention: if you turn of "Use transition effects" in your browser then the error should not appear anymore. cheers! On Monday, April 29, 2002 at 5:18 pm, jc wrote: >When shutting down Win2000, I get a message that SysFader is not responding. I can >always hit the "cancel now" button but that is annoying. > >I have scanned the disk and the registry for sysfader. I cannot find it. Where >is it, and how do I get rid of it? [Reply or follow-up to this message] re: SysFader will not fade away Sunday, June 2, 2002 at 3:49 pm Posted by jc (4 messages posted) Hi Abel, thanks for your reply. I did finally come across the transition effects options, and turned it off. Now instead, it is Explorer that will not die. EVERY time I start up and then shut down Windows, Explorer fails to exit. Maybe it is something I am running; I do not have ZA but I do have others like IconCorral and Freemem Pro. I will turn those off and see if one of those is not the culprit. Thanks! ~>jc On Saturday, June 1, 2002 at 4:24 pm, Abel wrote: >Sorry, forgot to mention: if you turn of "Use transition effects" in your browser >then the error should not appear anymore. > >cheers! > > [Reply or follow-up to this message] re: SysFader will not fade away Sunday, June 2, 2002 at 5:39 pm Posted by Abel (3 messages posted) Hi jc, Explorer.exe and windows processes in general are extendable in certain ways with in-process services (usually dlls). Well known are context menu handlers (WinZip is an example), drag and drop handlers (again, WinZip) and SysTray processes, which reside at least partly in the Explorer.exe address space (WinAmp is an example). Of course, these handlers should respond to end process messages, but if they don't, the system, or in this case, Explorer.exe may hang. The whole matter itself can become quite complex if you have to investigate by hand what dlls might cause this problem. The easiest way is checking all applications you installed and removing the most suspicious once, especially those that you think must dig deep into the system to do what they do. To make matters worse, any device driver can also cause your system (or any process) to hang, but hey, what's new! For quite a while I couldn't quit my system at all (unless I used the reset button) due to a Matrox Millennium graphics device driver. An update helped in that case. Getting back to what you said: it's not SysFader anymore but Explorer.exe that hangs. This is basically the same. SysFader was part of the browseui.dll, that one is loaded by Explorer.exe. If the (erroneous) message showed that SysFader could not quit, it most probably was Explorer.exe in the first place that couldn't quit. As a final note, in networked environments Explorer.exe often stops responding when the network is suddenly not available anymore, the traffic is suddenly blocked (a firewall may do that, but also a wrong unloading of network devices) or due to a block it can't release remote handles, which causes the same result: a hanging explorer.exe. If you have a networked environment you can simply check this: just close all your network connections, log on locally and see if the same problem still occurs. Good luck with culprit-hunting, you'll need it! Cheers, Abel On Sunday, June 2, 2002 at 3:49 pm, jc wrote: >Hi Abel, thanks for your reply. I did finally come across the transition effects >options, and turned it off. Now instead, it is Explorer that will not die. EVERY >time I start up and then shut down Windows, Explorer fails to exit. Maybe it is >something I am running; I do not have ZA but I do have others like IconCorral and >Freemem Pro. I will turn those off and see if one of those is not the culprit. >Thanks! > >~>jc > > > [Reply or follow-up to this message] re: SysFader will not fade away Saturday, June 8, 2002 at 11:11 am Posted by jc (4 messages posted) Hello again Abel... It appears the culprit is Cacheman. I reinstalled a fresh Win2k into a fresh partition, and everything was fine until I loaded Cacheman. One of Cacheman's options is to change the wait-to-kill-app and wait-for-app-not-responding timeouts. I think it is one of those buggers that is causing the problem. I will go to Cacheman's site and see if there is a report of or fix for this problem. Thanks for the discourse on DLL's though! ~>jc ** jeffrey w comer [Reply or follow-up to this message] re: SysFader will not fade away Wednesday, July 10, 2002 at 5:02 am Posted by Eugen Brochier (1 messages posted) In my case on a customer machine running W2K sysfader captured the run32.dll and takes 512MByte diskspace. The disk is high active and no other Process is realy able to acces the disk for its own need. Shutdown is not possible - also update of service pack cannot be done. On Sunday, June 2, 2002 at 5:39 pm, Abel wrote: >Hi jc, > >Explorer.exe and windows processes in general are extendable in certain ways with >in-process services (usually dlls). Well known are context menu handlers (WinZip >is an example), drag and drop handlers (again, WinZip) and SysTray processes, which >reside at least partly in the Explorer.exe address space (WinAmp is an example). >Of course, these handlers should respond to end process messages, but if they don't, >the system, or in this case, Explorer.exe may hang. > >The whole matter itself can become quite complex if you have to investigate by hand >what dlls might cause this problem. The easiest way is checking all applications >you installed and removing the most suspicious once, especially those that you think >must dig deep into the system to do what they do. > >To make matters worse, any device driver can also cause your system (or any process) >to hang, but hey, what's new! For quite a while I couldn't quit my system at all >(unless I used the reset button) due to a Matrox Millennium graphics device driver. >An update helped in that case. > >Getting back to what you said: it's not SysFader anymore but Explorer.exe that hangs. >This is basically the same. SysFader was part of the browseui.dll, that one is loaded >by Explorer.exe. If the (erroneous) message showed that SysFader could not quit, >it most probably was Explorer.exe in the first place that couldn't quit. > >As a final note, in networked environments Explorer.exe often stops responding when >the network is suddenly not available anymore, the traffic is suddenly blocked (a >firewall may do that, but also a wrong unloading of network devices) or due to a >block it can't release remote handles, which causes the same result: a hanging explorer.exe. >If you have a networked environment you can simply check this: just close all your >network connections, log on locally and see if the same problem still occurs. > >Good luck with culprit-hunting, you'll need it! > >Cheers, >Abel > > [Reply or follow-up to this message] re: SysFader will not fade away Tuesday, July 16, 2002 at 6:23 pm Posted by Gwendolyn (1 messages posted) Pardon, I just found this post and am having my own problems with SysFader. I built my own machine and installed Windows XP home on it. Everything works fine, except my CD Rom. I've double checked all my connections and they are accurate. When I put a disk in and try to read it, the green button just keeps flashing and nothing pops up. I know it's trying to do something because my system lags. I tried to end task the attempt to read the disk, and all that showed up in my task manager is SysFader. I tried to end task it, and it refused to end task and Windows tried to send an error report to Microsoft. I was offline at the time so I clicked Don't Send. I finally got the machine to stop trying to read the CD by pushing the eject button and taking the disk out of the drive. I tried to go in again and check the CD drive and see if it did the same thing while it was empty. It comes up with a window that asks me to place the disk into the drive. So the machine is recognizing that the CD is not present. I have also tried to uninstall and reinstall the driver, and still have the same problems. I tried to disable screen effects in my browser, but I couldn't find the location of the option to disable it. If that is indeed my problem, please tell me how to find that option in my settings. If that is not the problem, could you please share with me any ideas you think it might be? Sincerest thanks. [Reply or follow-up to this message] re: SysFader will not fade away Tuesday, October 22, 2002 at 8:57 am Posted by Stefania (1 messages posted) I've got something wrong with my sysfader, but the strange thing is that my ie 6 sp1, hangs only when I try to open "google". When I use explorer for viewing microsoft site (for example) or other sites, everything is ok; but when I try to open google the program doesn't respond owing to sysfader. What do you suggest me? On Wednesday, July 10, 2002 at 5:02 am, Eugen Brochier wrote: > >In my case on a customer machine running W2K sysfader captured the run32.dll and >takes 512MByte diskspace. The disk is high active and no other Process is realy able >to acces the disk for its own need. Shutdown is not possible - also update of service >pack cannot be done. > [Reply or follow-up to this message] re: SysFader will not fade away Wednesday, April 16, 2003 at 10:49 am Posted by dave (1 messages posted) Try using system restore, its seems to be connected with software install that effects the registry. On Tuesday, July 16, 2002 at 6:23 pm, Gwendolyn wrote: >Pardon, I just found this post and am having my own problems with SysFader. I built >my own machine and installed Windows XP home on it. Everything works fine, except >my CD Rom. I've double checked all my connections and they are accurate. When I put >a disk in and try to read it, the green button just keeps flashing and nothing pops >up. I know it's trying to do something because my system lags. I tried to end task >the attempt to read the disk, and all that showed up in my task manager is SysFader. >I tried to end task it, and it refused to end task and Windows tried to send an error >report to Microsoft. I was offline at the time so I clicked Don't Send. > >I finally got the machine to stop trying to read the CD by pushing the eject button >and taking the disk out of the drive. I tried to go in again and check the CD drive >and see if it did the same thing while it was empty. It comes up with a window that >asks me to place the disk into the drive. So the machine is recognizing that the >CD is not present. I have also tried to uninstall and reinstall the driver, and still >have the same problems. > >I tried to disable screen effects in my browser, but I couldn't find the location >of the option to disable it. If that is indeed my problem, please tell me how to >find that option in my settings. If that is not the problem, could you please share >with me any ideas you think it might be? > >Sincerest thanks. [Reply or follow-up to this message] re: SysFader will not fade away Monday, April 28, 2003 at 10:39 am Posted by t0maz (2 messages posted) Hello, As I was looking for a solution to my problem I stumbled into here. I have the exact same problem. First SysFader didn't want to quit, but a few days later it was Explorer.EXE that didn't want to quit. It could be caused by ZAp, because I have that too, but the other program mentioned, Cacheman, I have never heard of. I do not have found a solution yet, but when I find one, I will post it here. I also have some problems with other programs (like EditPlus, Valve Hammer Editor). When I open them (or with Hammer as I want to draw something) it crashes (in dutch it gives an "ongeldige bewerking" error, I don't know what it is in english). I think it has something to do with the explorer crash, because I get it every time I get the explorer.exe error (after a clean installation with some programs). Bye On Monday, April 29, 2002 at 5:18 pm, jc wrote: >When shutting down Win2000, I get a message that SysFader is not responding. I can >always hit the "cancel now" button but that is annoying. > >I have scanned the disk and the registry for sysfader. I cannot find it. Where >is it, and how do I get rid of it? On Monday, April 29, 2002 at 5:18 pm, jc wrote: >When shutting down Win2000, I get a message that SysFader is not responding. I can >always hit the "cancel now" button but that is annoying. > >I have scanned the disk and the registry for sysfader. I cannot find it. Where >is it, and how do I get rid of it? [Reply or follow-up to this message] re: SysFader will not fade away Monday, April 28, 2003 at 12:29 pm Posted by jc (4 messages posted) I just gave up on it. Honestly, if Microsoft can't make something work right, then why should I waste my time on it? I can't find it, I can't keep it from loading, I can't kill it. Seriously, I have better things to do than chase some bug hunt. When I went to XP the problem went away. I am downloading Red Hat Linux 9 now. I can't wait. On Monday, April 28, 2003 at 10:39 am, t0maz wrote: >Hello, > >As I was looking for a solution to my problem I stumbled into here. I have the exact >same problem. First SysFader didn't want to quit, but a few days later it was Explorer.EXE >that didn't want to quit. It could be caused by ZAp, because I have that too, but >the other program mentioned, Cacheman, I have never heard of. I do not have found >a solution yet, but when I find one, I will post it here. > >I also have some problems with other programs (like EditPlus, Valve Hammer Editor). >When I open them (or with Hammer as I want to draw something) it crashes (in dutch >it gives an "ongeldige bewerking" error, I don't know what it is in english). I think >it has something to do with the explorer crash, because I get it every time I get >the explorer.exe error (after a clean installation with some programs). > >Bye > > [Reply or follow-up to this message] re: SysFader will not fade away Thursday, May 1, 2003 at 8:53 am Posted by David_S (2 messages posted) Well - here's my followup, over a year after the original post - I found this forum by searching '"windows 2000" sysfader shutdown problems' on Google. I have three variations on the problem for you :-) Firstly, I know how and when it happened. Shortly after my last clean install, I was running WinMX, having conigured it to shutdown Windows when all downloads finished. My download terminated unexpectedly; those who know WinMX will know that its approach to shutting down is pretty brute-force. I was installing another program (Paint Shop Pro, as it happens) at the time... The shutdown problem came back at the very next Windows session, and hasn't gone away since. Exactly the same progression as everyone else; Sysfader halts a few times, then Explorer, permanently. It's pretty clear that the forced shutdown, with the installation going on at the same time, did the damage. Unfortunately, I can't remember if that coincidence of events happened last time, but it might well have done. System File Checker, System Restore and turning off the transition effects haven't done the trick. Secondly, it's only when I'm logged on as Administrator that the problem occurs every time (I was Administrator when it first happened). When we're using our general/family account, it happens occasionally, but the shutdown, logoff or reboot is clean more often than not. Thirdly; do other people have the situation where either the desktop closes, or the taskbar, but never both? No solution yet, unfortunately - it may need to be a fresh reinstall. On Monday, April 28, 2003 at 12:29 pm, jc wrote: >I just gave up on it. Honestly, if Microsoft can't make something work right, then >why should I waste my time on it? I can't find it, I can't keep it from loading, >I can't kill it. Seriously, I have better things to do than chase some bug hunt. >When I went to XP the problem went away. > >I am downloading Red Hat Linux 9 now. I can't wait. > > > [Reply or follow-up to this message] re: SysFader will not fade away Thursday, May 1, 2003 at 9:04 am Posted by David_S (2 messages posted) Sorry - I didn't describe the sequence correctly in my previous message. I had the problem with a previous installation, got nowhere, did a clean reinstall, and the problem returned after the WinMX incident. On Thursday, May 1, 2003 at 8:53 am, David_S wrote: > >No solution yet, unfortunately - it may need to be a fresh reinstall. > > > [Reply or follow-up to this message] re: SysFader will not fade away Tuesday, May 13, 2003 at 7:07 am Posted by ian (3 messages posted) had the same problem and can confirm turning off transition in under effects in desktop properties helps as well On Monday, April 28, 2003 at 10:39 am, t0maz wrote: >Hello, > >As I was looking for a solution to my problem I stumbled into here. I have the exact >same problem. First SysFader didn't want to quit, but a few days later it was Explorer.EXE >that didn't want to quit. It could be caused by ZAp, because I have that too, but >the other program mentioned, Cacheman, I have never heard of. I do not have found >a solution yet, but when I find one, I will post it here. > >I also have some problems with other programs (like EditPlus, Valve Hammer Editor). >When I open them (or with Hammer as I want to draw something) it crashes (in dutch >it gives an "ongeldige bewerking" error, I don't know what it is in english). I think >it has something to do with the explorer crash, because I get it every time I get >the explorer.exe error (after a clean installation with some programs). > >Bye > > [Reply or follow-up to this message] re: SysFader will not fade away Tuesday, May 13, 2003 at 7:12 am Posted by ian (3 messages posted) turn off scroll effects and transtions On Wednesday, April 16, 2003 at 10:49 am, dave wrote: >Try using system restore, its seems to be connected with software install that effects >the registry. > > [Reply or follow-up to this message] re: SysFader will not fade away Tuesday, May 13, 2003 at 7:19 am Posted by ian (3 messages posted) http://is-it-true.org/nt/xp/utips/utips1.shtml have alook at this re transitions On Wednesday, April 16, 2003 at 10:49 am, dave wrote: >Try using system restore, its seems to be connected with software install that effects >the registry. > > [Reply or follow-up to this message] re: SysFader will not fade away Saturday, May 17, 2003 at 7:29 am Posted by Wilco (1 messages posted) I was searching for a solution for this problem for a long time. Display property / Effects \ Use transition=No Thanks..... On Tuesday, May 13, 2003 at 7:07 am, ian wrote: >had the same problem and can confirm turning off transition in under effects in desktop >properties helps as well > > [Reply or follow-up to this message] re: SysFader will not fade away Thursday, September 4, 2003 at 11:07 am Posted by ISD (1 messages posted) I've had a similar SysFader problem with explorer tyring to run.. I fixed by unistalling HotBar.. Hotbar was installed by the user and it gets into Internet Explorer and Windows Explorer... Hope this helps.. On Monday, April 29, 2002 at 5:18 pm, jc wrote: >When shutting down Win2000, I get a message that SysFader is not responding. I can >always hit the "cancel now" button but that is annoying. > >I have scanned the disk and the registry for sysfader. I cannot find it. Where >is it, and how do I get rid of it? [Reply or follow-up to this message] re: SysFader will not fade away Sunday, December 12, 2004 at 3:55 am Posted by Han (1 messages posted) I recently got this stupid error, and I put in the system restore CD provided by my laptop manufacturer...and used the WinXP repair function...got some XP components reinstalled/repaired. Voila! the error is gone! Praise the lord! > On Thursday, September 4, 2003 at 11:07 am, ISD wrote: >I've had a similar SysFader problem with explorer tyring to run.. I fixed by unistalling >HotBar.. Hotbar was installed by the user and it gets into Internet Explorer and >Windows Explorer... > >Hope this helps.. [Reply or follow-up to this message] re: SysFader will not fade away Friday, March 4, 2005 at 3:03 pm Posted by Carl (1 messages posted) Anyone, My Microsoft Windows XP Home platform is in a state where any invocation of Windows Explorer results in a fatal error in an error dialog window that appears with the following text: SysFader: explorer.exe - Application Error The instruction at "0x10040065" referenced memory at "0x00000000". The memory could not be written. ... Other symptoms included: other applications fail after failure, the Microsoft Error Reporting interface appears (and I select send), the desktop "freezes" and after a long wait, the task bar, system trays and desktop shortcuts are slowly "redisplayed" longer boot times I've unsuccessfully applied many techniques that I've used in the past or that are commonly posted in related threads, which included: I applied all the latest operating system and application patches and service packs, which had no impact on the problem. I ran a virus detection & removal technology with the latest definition files and engine. To be specific, I ran: McAfee VirusScan Pro 2005 Version 9.0 with the latest definitions and several issues were identified. I tried to delete, quarantine and clean the flagged files with McAfee VirusScan Pro 2005 Version 9.0 and a few were removed but for the majority of the files, it failed on all attempts. It had issues with problematic files as identified and named in the GUI that did not exist when it attempted to "cleanse", e.g. it identified C:\WINDOWS\explorer.scf:jzdeh as one of the problematic files during the scan but when I attempted a delete or quarantine or clean ", no file of that name existed. I scanned with "spyware" detection and removal tools with the latest definition files and engine. I used: Microsoft Windows AntiSpyware Beta Lavasoft Ad-Aware SE Personal Edition 1.05 Webroot Spy Sweeper 3.5 PepiMK Software Spybot - Search & Destroy 1.3 and each addressed other less significant issues but did not solve the problem I identified earlier. I executed the latest: Microsoft Malicious Software Removal Tool that resulted in no change. I reran all the previously mentioned tools in "Safe Mode", which made no difference. I've disabled all "Transition Effects", which did not solve my problem. I looked at some of the descriptions of similar problems listed at sites like: http://www.wilderssecurity.com/showthread.php?t=24363&page=2 http://www.annoyances.org/exec/forum/win2000/t1020125925 but all the recommendations did not work or the files or configuration settings did not exist in this situation. I manually removed the explorer.scf. This worked only for explorer.exe issues and only temporarily. It allowed me to invoke Windows Explorer but after several hours of use the problem reappeared. I manually removed the explorer.scf since I didn't recognize it and it seemed to be "wrapping" the real application. This worked. It allowed me to invoke Windows Explorer but after several hours of use the problem reappeared. Does anyone have any suggestions short of reformatting and reinstallation? Thank you in advance for your help. [Reply or follow-up to this message] re: SysFader will not fade away Sunday, June 5, 2005 at 9:48 am Posted by JediFrank (1 messages posted) do this Click Start, go to Settings, click Control Panel, double-click Display. Click Appearance, then click Effects. Now UNCHECK the first four boxes.Not only do you not need any of these, but they will cure your problem and speed up your Desktop. Sysfader is the program used in XP to give you those Fade Effects. It is not a virus or a malware. [Reply or follow-up to this message] re: SysFader will not fade away Sunday, November 6, 2005 at 1:53 pm Posted by Reg Handford (1 messages posted) Thanks, very helpful!!! On Sunday, June 5, 2005 at 9:48 am, JediFrank wrote: >do this > >Click Start, go to Settings, click Control Panel, double-click Display. Click Appearance, >then click Effects. Now UNCHECK the first four boxes.Not only do you not need any >of these, but they will cure your problem and speed up your Desktop. [Reply or follow-up to this message] re: SysFader will not fade away Wednesday, September 6, 2006 at 12:34 pm Posted by Guillermo Uribe Cruz (1 messages posted) My own solution: I just delete my old profile in "c:\documents and settings\my profile" and then i make a new one, after that my PC works fine again. I hope can be usefull. [Reply or follow-up to this message] re: SysFader will not fade away Wednesday, June 13, 2007 at 6:31 pm Posted by robert antonelli (1 messages posted) The problem is an add on in internet explorer. Go into tools>options>programs>manage add on. Disable all add ons.This will fix the problem. Then enable them one by one to see witch one is bad. On Saturday, June 1, 2002 at 4:13 pm, Abel wrote: >Hi jc, > >I just happened to see your message. After a month you may already have found an >answer yourself, but in case not, here is some information: >SysFader is not really a process, yet it is spawned as a process by a dll named browseui.dll >when Internet Explorer wants to use transition effects. As is the design of win2k >and winXP, IE is everywhere and these transition effects are also used when you exit >your computer. This information I have from several newsgroups and my own experiences; >MS doesn't say anything about it. >It is not likely that SysFader itself is the culprit. In my case (I also had the >same error you had) ZoneAlarm and PGP Personal Firewall were running simultaneously >and blocking all kinds of stuff, avoiding processes to run and so on. After removing >ZoneAlarm everything went fine again. > >The moral here: look at recently installed or changed processes/services/drivers >and see what happens if you remove or disable them. Don't forget to look in the Run-keys >in the registry. > [Reply or follow-up to this message] re: SysFader will not fade away Wednesday, September 5, 2007 at 6:13 am Posted by Rob Huffstedtler (1 messages posted) Another possibility is that there is a corrupt link to a document in your Recent Documents folder. I was experiencing a similar behaviour to the one described, but realized that it was only starting if I either intentionally opened Recent Documents or accidentally moused over it. Clearing the Recent Documents solved my problem. On Wednesday, June 13, 2007 at 6:31 pm, robert antonelli wrote: > >The problem is an add on in internet explorer. Go into tools>options>programs>manage >add on. Disable all add ons.This will fix the problem. Then enable them one by one >to see witch one is bad. > > [Reply or follow-up to this message] Tip: Use one of the [Reply or follow-up to this message] links above to add a message to this thread Search this forum Start a new thread on a different subject Report abuse of the forum Return to the Windows 2000 Discussion Forum