Vista - BSOD whilst online in 5456 ?

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.

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.
>

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.
>>
>

You might want to fix your clock/date. You are a day ahead of everyone
else.

Joe

"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.

"MICHAEL" <u158627_emr@dslr.net> wrote in message
news:e42Ni4pnGHA.764@TK2MSFTNGP03.phx.gbl...
> 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.
>>>
>>
>
>

Not to mention a build.

"Joe727" <nospam@nospam.nospam> wrote in message
news:On4J%230qnGHA.4636@TK2MSFTNGP05.phx.gbl...
> You might want to fix your clock/date. You are a day ahead of everyone
> else.
>
> Joe
>
> "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.
>
>

I just hit delete when I see posts that are pre-dated.
It may be an error but more often than not it's the poster's attempt to keep
their post at the top!
dotcom


"Joe727" <nospam@nospam.nospam> wrote in message
news:On4J%230qnGHA.4636@TK2MSFTNGP05.phx.gbl...
> You might want to fix your clock/date. You are a day ahead of everyone
> else.
>
> Joe
>
> "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.
>
>

If you have a Vista DVD, there is a promising "feature" or utility in Vista
called Win RE or Windows Recovery Environment.

This is the best documentation I can find to post for you--MSFT is more
concerned with using the public Beta to market sales than getting the
writers with the Recovery and Desmond Lee's Win RE team to get off their
butts and publish anything on the web that's substantive. They've done some
superficial chats and Live Meetings that have resulted in Beta testers
posting how much they don't understand about these features regularly, and
there are a couple sentences about this feature that say absolutely nothing
in the so-called Vista Product Guide which is in essence a superficial
cheerleading manual.

Superficial treatment of Startup Repair
http://www.microsoft.com/technet/win.../suppcost.mspx

***Accessing Windows RE (Repair Environment):***

1) Insert Media into PC (the DVD you burned)

2) ***You will see on the Vista logo setup screen after lang. options in the
lower left corner, a link called "System Recovery Options."***

3) Select your OS for repair.

4) Its been my experience that you can see some causes of the crash from
theWin RE feature:

You'll have a choice there of using:

1) Startup Repair
2) System Restore
3) Complete PC Restore


You'll have a choice there of using:

1) Startup Repair
2) System Restore
3) Complete PC Restore

Good luck,

CH




"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.
>>
>

Of all the problems in the world, and all the problems with Vista, and all
the problems in the area that the community managers of these groups can't
fix the multiposting bug for months on the web interface of these groups and
the web interface of these groups for years, whether they are predated or
they are named "Star Jones mud wrestles Condi" for me are right down there
at the bottom as to problems.

The only annoyance is that some of the posts that are predated stay at the
top of the list unless you tweak as to how you want OE or Win Mail as it's
called in Vista to download groups.

CH


"dotcom" <No@nospam.com> wrote in message
news:uSIO5TsnGHA.4496@TK2MSFTNGP04.phx.gbl...
>I just hit delete when I see posts that are pre-dated.
> It may be an error but more often than not it's the poster's attempt to
> keep their post at the top!
> dotcom
>
>
> "Joe727" <nospam@nospam.nospam> wrote in message
> news:On4J%230qnGHA.4636@TK2MSFTNGP05.phx.gbl...
>> You might want to fix your clock/date. You are a day ahead of everyone
>> else.
>>
>> Joe
>>
>> "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.
>>
>>
>
>

Darn that Marty McFly!!!!

"Colin Barnhorst" <colinbarharst(remove)@msn.com> wrote in message
news:%23AWiCQrnGHA.4668@TK2MSFTNGP02.phx.gbl...
> Not to mention a build.
>