System32 is an very essential folder in Windows Operating System. Anyone can find this folder by visiting this path
It contains different drivers, hosts and several system level programs and dll files. If anyone delete this folder, Windows OS can run. Only Windows OS contains System32 folder. No other OS contain any System folder with this name.
GDIPLUS.DLL is a important dll file and this dll file is used to produce 2d / 3d graphics. Anti-aliased 2D graphics, floating point coordinates, gradient shading are some of the features, offered by gdi+ library function. A programmer can call the dll file and use its function to create graphics. So using this library 2d graphics can be produced. and system uses this dll file to produce graphics. for more deals information you can visit Microsoft's knowledge base.
The reason was a CORRUPTED FONT. In my case it was ukai.ttf. After deleting this file from my C:WindowsFonts folder, the problem was solved.
To see if this is your case, we need to first replace all your fonts with good ones (from the original Windows Installation CD). If the problem is gone, then we go hunting for a offending font file from your old set. So:
Open your Windows XP Installation CD and copy all *.tt_ files to some folder.
Extract all fonts using extract or expand tool (or any tool that you know and works). This is your "clean set of fonts". Delete the *.tt_ files (compressed ones) since we won't need them no more.
Move all your C:WindowsFonts*.ttf files to some other folder.
Copy the "clean set" to C:WindowsFonts.
Note: Points 3 and 4 may require doing it in some other tool than Windows Explorer. In my case I used File Commander, but I guess any other similar tool would work – Total Commander, FAR, etc.
Restart the system (not sure if its needed, but just to be sure 😉
Check if the problem is gone. If so, then it was one of the fonts that causes the problem (see point 7). If not, just reverse points 3 and 4 and look for other reasons.
Open C:WindowsFonts in Windows Explorer (you should see font names, NOT file names!). In some external file manager (as mentioned above) copy fonts from the old set to C:WindowsFonts — but do so in groups of 10.
After copying you should see additional fonts appearing in Windows Explorer window (showing font names). This means that Windows sees the fonts you copy, and activates them. After each 10 fonts are activated run the program that would cause gdiplus.dll error. If there's no error — copy another 10 font files. If the error appears — one (or more) of the last 10 copied font files is causing the problem.
Continue until you have the problem fixed, and almost all of your old fonts back in place.
Hint: it may be advisable to start with largest font files (in my case the offending ukai.ttf was about 17 MB or so).