after long and frustrating hours last night i think i have tracked this fault down.
it sems that this fault does not refer to bad memory or bad hardware neither does it mean a bad coroupt operationg system, well it could be but its highly unlikely especially if you have just reinstalled which is when it happens the most.
i have tried to trace this back troough the visual studio debug and well its does never refer to any one consigned memory location and memory hardware is not that screwed as it loads windows fine so how can it be.
anyway to the crunch the error is almost always caused by a 3rd party software. this means it could be a activex a plugin a program just about any kind of softwware that interacts directly with your shell or desktop system.
the best way of tracking this fault down is to backtrack and really serch the debug script try and find out which program is causing it try uninstalling the last five programs you installeduntil the error stops. after it does you will recive refrenced error messages after you have uninstalled the badly programmed application.
applications that have operators in them which have not been assigned a int get assigned junk then when a program calls that memory space it finds junk hence the errors. this is due to bad programing of 3rd party maybe even microsoft in my case it was nero backup lol.
there is a way in which you can flush the virtual memory and reset this then it might get rid of the error too.
anyway this is what i have found in regard to explorer.exe faulting especially with shell32.dll and ntdll.dll
