A computer which I am working on (Dell Pentium 4, Win XP SP3) can not complete running the Registry Cleanup. It always stalls on the Fonts Section and then when I eventually hit cancel I get an "application error" in ccSvcHst.exe which states "The instruction at '0x66de64d3' referenced memory at '0x66e3a46c'. The memory could not be read." In the Application Error Log it states "Faulting application ccSvcHst.exe, version 11.2.1.4, faulting module jwRC.dll, version 6.0.0.309, fault address 0x000064d3." I have a dump from the last error that I can attach if needed. I appreciate any help anyone can give on getting this straightened out. Thank you.
A computer which I am working on (Dell Pentium 4, Win XP SP3) can not complete running the Registry Cleanup. It always stalls on the Fonts Section and then when I eventually hit cancel I get an "application error" in ccSvcHst.exe which states "The instruction at '0x66de64d3' referenced memory at '0x66e3a46c'. The memory could not be read." In the Application Error Log it states "Faulting application ccSvcHst.exe, version 11.2.1.4, faulting module jwRC.dll, version 6.0.0.309, fault address 0x000064d3." I have a dump from the last error that I can attach if needed. I appreciate any help anyone can give on getting this straightened out. Thank you.
Thanks for coming back to let us know how well the chat worked for you.
Because others can learn from your experience, can you let us know what was found/fixed?
jc,
Do please be careful about letting any regisitry cleaner take action on fonts. It's probably OK in XP but if you get to Windows 7 and decide to run a registry cleaner (I would not unless I had a problem and knew that it came from the registry and I'd make sure I backed up the registry before changing anything) don't let it touch any of the fonts or type library entries.
Windows 7 has added an enormous range of fonts and while I can look at them and say I'll never use this that and the other Windows itself is using them internally and if you delete them you will break Windows.
So please be careful .... and do tell us what the support team did to fix the problem.
Sorry for the delay. The tech guy just reset the registry. He would not say what was causing the problem.
Thanks for the feedback.
It would be consistent with what I'd encountered elsewhere of the sensitivity of Windows to its portfolio of fonts. Best left alone.