Posted 25 November 2006 - 08:17 AM
Usually the STOP 0x135 error is caused by a corrupt program. It may also be a problem within your registry.
The first step is to uninstall the offending applications and reinstall them using a freshly downloaded copy. This should cure the errors from the applications - but not the Windows error.
Here's an article about the error when starting Windows: http://support.microsoft.com/?kbid=173309&sd=RMVP
Amidst all the stuff that it says, it says that this could be a case of corruption of the user profile hive. And, luckily, there's a free tool that may help out (if the instructions in the article can't be followed). You can download it here: http://www.microsoft.com/downloads/details...;displaylang=en
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able. - John
(my website: http://www.carrona.org/
)**If you need a more detailed explanation, please ask for it. I have the Knack
. ** If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.
<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.