Vista - Vista BSOD and feedback

Hi
I installed Vista Ultimate final (from MSDN subsc) on a P3 machine with a
USB ADSL Modem.
Every now and then I get a BSOD (witch I wasn't used to in XP, but that's
another story.....).
After the boot I get a warning "Windows closed unexp...etc etc" asking me if
I want to send data to Microsoft so that it can help me solve the problem.
But at that point of the boot the pc is NOT connected to Internet
(obvioussly), so the only 2 buttons available are: "Check Later" or "Cancel".
I tried leaving the dialog open and connecting to Internet but no result.

Then yesterday I got BSOD while being online, and after tha boot I was
(finally) asked if I wanted to send data with a "YES" button, so I connected
and sent data to Microsoft ..... and waited .... and waited .... and waited
.....

Guess what ? NO REPLY
Not even a small window telling me that they had no idea of how to solve the
problem (like in the early days of XP before it became stable).
I waited over 10 min (without touching a single key) and still no feedback ?

Am I missing something or is the "Crash report service" a little BETA still ?

Ciao
Marco

Hi Marco,

Simply means there is no answer to the problem that caused the stop error
yet. Most are caused by device drivers, but without knowing the details it's
impossible to tell. The reporting tool is not still in beta, but it does
take time to build a database of error messages and resolutions - and then
only if a resolution exists at all. Microsoft concentrates on the errors
with the highest frequency, so if yours is an isolated case it may be a long
time before it's addressed if at all.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP
http://mvp.support.microsoft.com/
Windows help - www.rickrogers.org

"Marco" <Marco@discussions.microsoft.com> wrote in message
news:04ACAF1D-D8E3-48D0-A227-78FAD12573E5@microsoft.com...
> Hi
> I installed Vista Ultimate final (from MSDN subsc) on a P3 machine with a
> USB ADSL Modem.
> Every now and then I get a BSOD (witch I wasn't used to in XP, but that's
> another story.....).
> After the boot I get a warning "Windows closed unexp...etc etc" asking me
> if
> I want to send data to Microsoft so that it can help me solve the problem.
> But at that point of the boot the pc is NOT connected to Internet
> (obvioussly), so the only 2 buttons available are: "Check Later" or
> "Cancel".
> I tried leaving the dialog open and connecting to Internet but no result.
>
> Then yesterday I got BSOD while being online, and after tha boot I was
> (finally) asked if I wanted to send data with a "YES" button, so I
> connected
> and sent data to Microsoft ..... and waited .... and waited .... and
> waited
> ....
>
> Guess what ? NO REPLY
> Not even a small window telling me that they had no idea of how to solve
> the
> problem (like in the early days of XP before it became stable).
> I waited over 10 min (without touching a single key) and still no feedback
> ?
>
> Am I missing something or is the "Crash report service" a little BETA
> still ?
>
> Ciao
> Marco
>

Thanks Rick.
Still I think that a friendly feedback dialog should appear, like in the old
days of XP.
This way there's no way to tell if the data was actually sent.

I'll check the event viewer to get some details on the BSOD's as soon as I
get back home


Ciao

Marco

"Rick Rogers" wrote:

> Hi Marco,
>
> Simply means there is no answer to the problem that caused the stop error
> yet. Most are caused by device drivers, but without knowing the details it's
> impossible to tell. The reporting tool is not still in beta, but it does
> take time to build a database of error messages and resolutions - and then
> only if a resolution exists at all. Microsoft concentrates on the errors
> with the highest frequency, so if yours is an isolated case it may be a long
> time before it's addressed if at all.
>
> --
> Best of Luck,
>
> Rick Rogers, aka "Nutcase" - Microsoft MVP
> http://mvp.support.microsoft.com/
> Windows help - www.rickrogers.org
>
> "Marco" <Marco@discussions.microsoft.com> wrote in message
> news:04ACAF1D-D8E3-48D0-A227-78FAD12573E5@microsoft.com...
> > Hi
> > I installed Vista Ultimate final (from MSDN subsc) on a P3 machine with a
> > USB ADSL Modem.
> > Every now and then I get a BSOD (witch I wasn't used to in XP, but that's
> > another story.....).
> > After the boot I get a warning "Windows closed unexp...etc etc" asking me
> > if
> > I want to send data to Microsoft so that it can help me solve the problem.
> > But at that point of the boot the pc is NOT connected to Internet
> > (obvioussly), so the only 2 buttons available are: "Check Later" or
> > "Cancel".
> > I tried leaving the dialog open and connecting to Internet but no result.
> >
> > Then yesterday I got BSOD while being online, and after tha boot I was
> > (finally) asked if I wanted to send data with a "YES" button, so I
> > connected
> > and sent data to Microsoft ..... and waited .... and waited .... and
> > waited
> > ....
> >
> > Guess what ? NO REPLY
> > Not even a small window telling me that they had no idea of how to solve
> > the
> > problem (like in the early days of XP before it became stable).
> > I waited over 10 min (without touching a single key) and still no feedback
> > ?
> >
> > Am I missing something or is the "Crash report service" a little BETA
> > still ?
> >
> > Ciao
> > Marco
> >
>
>

Marco--

1) MSFT has people who have been working on real time info for years but
they may not get anything up while most of the people who are there are
employed there so don't hold your breath.
2) It can help to know what the BSOD says, so why don't you either go to
settings and set things so there is no auto restart

Windows key + pause break at same time or type in sysdm.cpl at the run
box>advanced tab>bottom settings button under "system startup">check out of
auto restart box at the bottom.

Also ck event viewer by typing eventvwr.msc in run box>click on
system>scroll down to time of BSOD crash.

What MSFT engineers fail to recognize and many many MVPs but we're trying
hard to educate them is that a number of BSOD stops can be prevented
depending on the source of them by configuring driver verifier (verifier in
run box) not to inspect your antivirus drivers (yes virginia software has
drivers as well--type at cmd prompt driver query and watch 'em roll if you
think I'm pullin ya leg).

Not inspecting the AV drivers is not going to impact the running and
functioning and updating of defs of your AV program one scintilla. How many
people run that AV program they never heard of from that small sinister
company who is sending you bad software drivers? That's righhhhhht none.

Also you disable deadlock detection in DV concomittantly.

We are working on educating MSFT engineers and developers to practice
preventive medicine on the BSODs.

Once you see your BSOD error and number or the message in Event Viewer that
may be there to correspond to it, then you can search engine it or search
engine for a site that explains BSOD stop errors or try searching it with
the key words and number at http://support.microsoft.com home of the famous
MSKB.

MSFT has toyed with ways to provide real time error info. For years
http://oca.microsoft.com is a joke and Jim Allchin will climb in the car for
his last official drive out soon and it will remain a total joke.

They often provide error messages in HEX. Let me assure you that SUV soccer
mom aka Valley girl wanna be younger like again ain't yammering for hours a
day with that little razor cell glued to her big ear in HEX. Most soccer
mom's ain't no HEX decoding expert.

IS HEX helpful to the MSFT customer? Hell no. Does it make sense to show
them the hex or to have error message ectopically and metastatically
scattered to the 4 corners of Windows? Hell no.

Does that qualify for being non-intuitve on some other planet on the Redmond
campus with no conception of what the outside world might need in the way of
error messages? LOL of course it does. But no one has accused engineers,
developers, and PMS on the Redmond campus of ever being remotely logical,
good communicators, or intuitve.

CH


"Marco" <Marco@discussions.microsoft.com> wrote in message
news:04ACAF1D-D8E3-48D0-A227-78FAD12573E5@microsoft.com...
> Hi
> I installed Vista Ultimate final (from MSDN subsc) on a P3 machine with a
> USB ADSL Modem.
> Every now and then I get a BSOD (witch I wasn't used to in XP, but that's
> another story.....).
> After the boot I get a warning "Windows closed unexp...etc etc" asking me
> if
> I want to send data to Microsoft so that it can help me solve the problem.
> But at that point of the boot the pc is NOT connected to Internet
> (obvioussly), so the only 2 buttons available are: "Check Later" or
> "Cancel".
> I tried leaving the dialog open and connecting to Internet but no result.
>
> Then yesterday I got BSOD while being online, and after tha boot I was
> (finally) asked if I wanted to send data with a "YES" button, so I
> connected
> and sent data to Microsoft ..... and waited .... and waited .... and
> waited
> ....
>
> Guess what ? NO REPLY
> Not even a small window telling me that they had no idea of how to solve
> the
> problem (like in the early days of XP before it became stable).
> I waited over 10 min (without touching a single key) and still no feedback
> ?
>
> Am I missing something or is the "Crash report service" a little BETA
> still ?
>
> Ciao
> Marco
>

Grazie mille (thanks a lot) Chad.

"Chad Harris" wrote:

> Marco--
>
> 1) MSFT has people who have been working on real time info for years but
> they may not get anything up while most of the people who are there are
> employed there so don't hold your breath.
> 2) It can help to know what the BSOD says, so why don't you either go to
> settings and set things so there is no auto restart
>
> Windows key + pause break at same time or type in sysdm.cpl at the run
> box>advanced tab>bottom settings button under "system startup">check out of
> auto restart box at the bottom.
>
> Also ck event viewer by typing eventvwr.msc in run box>click on
> system>scroll down to time of BSOD crash.
>
> What MSFT engineers fail to recognize and many many MVPs but we're trying
> hard to educate them is that a number of BSOD stops can be prevented
> depending on the source of them by configuring driver verifier (verifier in
> run box) not to inspect your antivirus drivers (yes virginia software has
> drivers as well--type at cmd prompt driver query and watch 'em roll if you
> think I'm pullin ya leg).
>
> Not inspecting the AV drivers is not going to impact the running and
> functioning and updating of defs of your AV program one scintilla. How many
> people run that AV program they never heard of from that small sinister
> company who is sending you bad software drivers? That's righhhhhht none.
>
> Also you disable deadlock detection in DV concomittantly.
>
> We are working on educating MSFT engineers and developers to practice
> preventive medicine on the BSODs.
>
> Once you see your BSOD error and number or the message in Event Viewer that
> may be there to correspond to it, then you can search engine it or search
> engine for a site that explains BSOD stop errors or try searching it with
> the key words and number at http://support.microsoft.com home of the famous
> MSKB.
>
> MSFT has toyed with ways to provide real time error info. For years
> http://oca.microsoft.com is a joke and Jim Allchin will climb in the car for
> his last official drive out soon and it will remain a total joke.
>
> They often provide error messages in HEX. Let me assure you that SUV soccer
> mom aka Valley girl wanna be younger like again ain't yammering for hours a
> day with that little razor cell glued to her big ear in HEX. Most soccer
> mom's ain't no HEX decoding expert.
>
> IS HEX helpful to the MSFT customer? Hell no. Does it make sense to show
> them the hex or to have error message ectopically and metastatically
> scattered to the 4 corners of Windows? Hell no.
>
> Does that qualify for being non-intuitve on some other planet on the Redmond
> campus with no conception of what the outside world might need in the way of
> error messages? LOL of course it does. But no one has accused engineers,
> developers, and PMS on the Redmond campus of ever being remotely logical,
> good communicators, or intuitve.
>
> CH
>
>
> "Marco" <Marco@discussions.microsoft.com> wrote in message
> news:04ACAF1D-D8E3-48D0-A227-78FAD12573E5@microsoft.com...
> > Hi
> > I installed Vista Ultimate final (from MSDN subsc) on a P3 machine with a
> > USB ADSL Modem.
> > Every now and then I get a BSOD (witch I wasn't used to in XP, but that's
> > another story.....).
> > After the boot I get a warning "Windows closed unexp...etc etc" asking me
> > if
> > I want to send data to Microsoft so that it can help me solve the problem.
> > But at that point of the boot the pc is NOT connected to Internet
> > (obvioussly), so the only 2 buttons available are: "Check Later" or
> > "Cancel".
> > I tried leaving the dialog open and connecting to Internet but no result.
> >
> > Then yesterday I got BSOD while being online, and after tha boot I was
> > (finally) asked if I wanted to send data with a "YES" button, so I
> > connected
> > and sent data to Microsoft ..... and waited .... and waited .... and
> > waited
> > ....
> >
> > Guess what ? NO REPLY
> > Not even a small window telling me that they had no idea of how to solve
> > the
> > problem (like in the early days of XP before it became stable).
> > I waited over 10 min (without touching a single key) and still no feedback
> > ?
> >
> > Am I missing something or is the "Crash report service" a little BETA
> > still ?
> >
> > Ciao
> > Marco
> >
>
>
>