Hi d bala
Depending on the nature of your "repair" reinstalls, you may be returning some of your system files to versions that don't work properly with some device drivers in your system (as these aren't necessarily replaced in a "repair" reinstall). Some video drivers, for example, require that certain Service Packs be already installed for them to work properly. It can be any of a number of different drivers, or sometimes software that installs a "service" (scanners, printers, & multifunctions are famous for this) -- so tracking the exact culprit can take time.
When you perform a "clean" parallel installation, you are providing drivers from scratch - and the file versions are likely compatible.
Here's a Microsoft Knowledge Base article with an example of a situation that can lead to errors such as you experienced --- http://support.microsoft.com/kb/329293
__________
Another possiblity is rootkit infection, so scan for those. Here is an article describing the known-rootkits that cause the Stop error you experienced --- http://www.jsifaq.com/SF/Tips/Tip.aspx?id=9053
And here are a few Rootkit scanners --- (pay close attention to the instructions, to avoid false-positives)
Microsoft/SysInternals Rootkit Revealer --- http://www.microsoft.com/technet/sysinternals/utilities/RootkitRevealer.mspx
F-Secure Blacklight --- http://www.f-secure.com/blacklight/blacklight.html (use the link "Try F-Secure BlackLight" at the bottom of that page -- the trial period has been extended to April 2007)
__________
Best of luck
. . . Gary
Depending on the nature of your "repair" reinstalls, you may be returning some of your system files to versions that don't work properly with some device drivers in your system (as these aren't necessarily replaced in a "repair" reinstall). Some video drivers, for example, require that certain Service Packs be already installed for them to work properly. It can be any of a number of different drivers, or sometimes software that installs a "service" (scanners, printers, & multifunctions are famous for this) -- so tracking the exact culprit can take time.
When you perform a "clean" parallel installation, you are providing drivers from scratch - and the file versions are likely compatible.
Here's a Microsoft Knowledge Base article with an example of a situation that can lead to errors such as you experienced --- http://support.microsoft.com/kb/329293
__________
Another possiblity is rootkit infection, so scan for those. Here is an article describing the known-rootkits that cause the Stop error you experienced --- http://www.jsifaq.com/SF/Tips/Tip.aspx?id=9053
And here are a few Rootkit scanners --- (pay close attention to the instructions, to avoid false-positives)
Microsoft/SysInternals Rootkit Revealer --- http://www.microsoft.com/technet/sysinternals/utilities/RootkitRevealer.mspx
F-Secure Blacklight --- http://www.f-secure.com/blacklight/blacklight.html (use the link "Try F-Secure BlackLight" at the bottom of that page -- the trial period has been extended to April 2007)
__________
Best of luck
. . . Gary
