MICHAEL

This is the newsgroup for build 5384. You are using 5456,
that was only released to certain testers- they have their own
newsgroups. When you try and access the wrong newsgroup-
build 5456 is able to sense that and tries to stop you from making
anymore foolish mistakes. Since I am replying to this post, build
5456 is not perfect at preventing this quite yet.... nor does it seem
fool-proof, either.

-Michael

"Richard" <tuco4@hotmail.co.uk> wrote in message
news:B9F5070B-233A-490C-8695-07A10CDD6FDB@microsoft.com...
> Annnnnnnnd another,
>
> STOP:0X0000000A (OXOO64OO64, 0X0000001B, 0X00000000, 0X814695EB)
> "Richard" <tuco4@hotmail.co.uk> wrote in message
> news:0B3A735A-5619-4585-BE1A-B89B633D6DEC@microsoft.com...
>> I've just had another one whilst browsing this group, STOP:0x0000000A
>> (0X94300016,0X0000001B,0X00000001,0X814679FC).
>> "Richard" <tuco4@hotmail.co.uk> wrote in message
>> news:84303ACE-4757-45F6-9A8F-9E87DA09BFFA@microsoft.com...
>>> Hello,
>>>
>>> Whilst online in build 5456 i keep getting a stop: 0x0000000a,
>>> ax00b800b8,0x0000001b,0x00000000,0x814695eb error message, if i'm running avast 4.7 AV then
>>> it hard locks instead ?( not currently installed, using a fresh install as i thought avast
>>> was the problem ) I don't get this problem in the beta 2 **84 build. Does anyone have a
>>> clue as what the problem is & how to fix ?
>>> Thanks,
>>>
>>> Richard.
>>
>