Lee
Wed Jan 28 02:24:57 CST 2004
Well that's an interesting idea as I had just re-enabled
the network controller when I decided to put this machine
on the LAN. The NIC is on the motherboard so I can't move
it to another slot but it had been working fine (with the
NIC enabled) until I was actually doing the software setup
to connect it to the router. I think I did something wrong
somehow although I got no error messages at the time
(using the Network Neighborhood Wizard). I had followed
the instructions that came with the router but wasn't
having any luck getting it to connect so I was trying to
fix that problem. During the various re-boots requested by
the network setup tasks this registry problem popped up. I
just checked and found no newer drivers for this machine
(it's about three years old now) but I will check again to
be sure.
Thanks for the ideas.
Lee
---Original Message-----
>"Lee Hardesty" <anonymous@discussions.microsoft.com>
wrote in message
>news:51ec01c3e55e$4c2733f0$a301280a@phx.gbl...
>> I have a problem similar to Paul Johnson's previous
>> post although I don't know exactly what caused it. I was
>> attempting to add this Me system to our router for
>> internet access and suddenly when I re-booted I got the
>> same message from the Registry Checker. I pressed OK and
>> the system re-booted and when it came up the next time
>> (just when it appeared to be finished loading the
desktop,
>> etc.) it jumped to a blue screen with the following
error
>> message:
>> Filename:VMM(12)+00001A77 Error:0E:0028:C0280A77
>> I re-booted again and was back to the desktop with the
>> Registry Checker error again. This cycle repeated with
>> additional re-boots. So I ended the Registry Checker
task,
>> used the Symantec system scan to fix the registry (found
>> and fixed 23 errors) and still I get the same Registry
>> Checker error. Ran Symantec again and it found no
registry
>> errors and the machine seems to run fine. Still getting
>> the Registry Checker error message every time I boot.
>> What might be going on here and what should I do to
(as
>> safely as possible) fix this problem?
>> Thanks,
>> Lee
>
>Try updating your NIC driver and possibly your display
driver. OE0028 is
>nearly always a device using shared memory whith
improperly written drivers
>accessing memory it isn't allowed to address.
>
>In some cases, the issue pops up when your mobo or
peripheral(s) don't
>support ACPI IRQ steering properly and you have occupied
shared slots. On
>most systems, the AGP port and PCI#1 are shared, on mine,
AGP shares with
>both PCI#1 and PCI#2. The fix is to move the NIC in PCI
slot 1 to another
>slot.
>
>
>
>.
>