[windows2000] Re: 0x51 Registry Error (again)

  • From: "Sullivan, Glenn" <GSullivan@xxxxxxxxxxxxxx>
  • To: <windows2000@xxxxxxxxxxxxx>
  • Date: Wed, 5 Oct 2005 07:14:02 -0400

If they can't solve it, they'll refund you.
They "researched" something for me, but after 9 months they didn't have an 
answer.  So they gave us back the fee.
They didn't want to buy the right answer though, as I had figured it out by 
then... ;-)

Glenn Sullivan, MCSE+I MCDBA
David Clark Company Inc. 



From: windows2000-bounce@xxxxxxxxxxxxx 
[mailto:windows2000-bounce@xxxxxxxxxxxxx] On Behalf Of Neil Bullock
Posted At: Wednesday, October 05, 2005 4:37 AM
Posted To: Windows 2000
Conversation: [windows2000] Re: 0x51 Registry Error (again)
Subject: [windows2000] Re: 0x51 Registry Error (again)

We have thought about giving Microsoft a call.  I think that might have to be 
our next plan of attack.
The machines aren't all the same spec, nor the same age, or even the same image 
(though they do have the same software on for the most part).


        From: windows2000-bounce@xxxxxxxxxxxxx 
[mailto:windows2000-bounce@xxxxxxxxxxxxx] On Behalf Of Dogers
        Sent: 05 October 2005 09:30
        To: windows2000@xxxxxxxxxxxxx
        Subject: [windows2000] Re: 0x51 Registry Error (again)
        If you're at the end of your tether, and the dump analysis didn't give 
up anything (I assume you changed from mini to kernel/full?), I'd seriously 
consider giving MS PSS a call.. £250, but they'll be able to help you in ways 
we can't :) 
        It's especially worth it considering it's happening on loads of your 
machines (I assume theyre all the same machine spec?) - how much is your time 
        On 05/10/05, Neil Bullock <n.bullock@xxxxxxxxxxxxxxxxxxxxx> wrote: 

                > Are you using Sophos AV?  If so, try taking it off one
                > machine and using
                > something else for a bit, like AVG or Norton.  If the problem
                > goes away
                We do, but one of the rooms this happened in didn't have it on. 
 I'll give 
                it a try anyway.
                > then you know what's causing it, and you can investigate more
                > closely.
                > In addition, perhaps your image is corrupted, you may want to
                > consider
                > making a new one. 
                They're not all the same types of machine, so we've made 
several different
                images completely from scratch, so I think it's unlikely to be 
                There'd need to be at least 5 corrupted images.
                I received some information privately about analysing crash 
dump data 
                (thanks), but I didn't find anything obvious about what the 
problem might
                New Site from The Kenzig Group!
                Windows Vista Links, list options
                and info are available at: 
                To Unsubscribe, set digest or vacation
                mode or view archives use the below link.

Other related posts: