Vista - WIndows Vista BSODs

Since MS only officially acknowledges 3 BSODs and these aren't on the list,
can I safely assume that are about the same as their Windows XP
counterparts?

BSOD 1:
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6000.2.0.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 1000007e
BCP1: C0000005
BCP2: 8998ABF4
BCP3: 8669226C
BCP4: 86691F68
OS Version: 6_0_6000
Service Pack: 0_0
Product: 256_1

BSOD 2:
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6000.2.0.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 1000008e
BCP1: C0000005
BCP2: 8958AC4D
BCP3: 937F6E60
BCP4: 00000000
OS Version: 6_0_6000
Service Pack: 0_0
Product: 256_1

Should have mentioned:
Windows Vista Ultimate, fresh install, Office 2007, patched. The second BSOD
was when I tried ot open a recovered document (the original untouched
version) in Word 2007.
WSince there is a Windows XP BSOD associated wiuth p[rinter drivers, I have
installed a Vista driver using the detedt printer type option. We shall see
if this fixes this BSOD.


"Bill Hobson" <Ihatespamb-hobson@tamu.edu> wrote in message
news:66344672-2D59-4F82-AD77-B012DDDD812F@microsoft.com...
> Since MS only officially acknowledges 3 BSODs and these aren't on the
> list, can I safely assume that are about the same as their Windows XP
> counterparts?
>
> BSOD 1:
> Problem signature:
> Problem Event Name: BlueScreen
> OS Version: 6.0.6000.2.0.0.256.1
> Locale ID: 1033
>
> Additional information about the problem:
> BCCode: 1000007e
> BCP1: C0000005
> BCP2: 8998ABF4
> BCP3: 8669226C
> BCP4: 86691F68
> OS Version: 6_0_6000
> Service Pack: 0_0
> Product: 256_1
>
> BSOD 2:
> Problem signature:
> Problem Event Name: BlueScreen
> OS Version: 6.0.6000.2.0.0.256.1
> Locale ID: 1033
>
> Additional information about the problem:
> BCCode: 1000008e
> BCP1: C0000005
> BCP2: 8958AC4D
> BCP3: 937F6E60
> BCP4: 00000000
> OS Version: 6_0_6000
> Service Pack: 0_0
> Product: 256_1

Bill--

I haven't tried to catalogue and compare/contrast BSODs from Vista and the
components in the equation (hdw and software) and those of XP. Many Vista
Stop Error message sites will spring up in the coming months. I do think
it's important to install Win RE on your box on a drive other than vista and
become familiar with the components of Win RE needed to repair serious
systemic problems in Vista whether they are attended by a BSOD and a no boot
situation or not. You need not be in a BSOD no boot situation to deploy
startup repair and fix Vista.

That includes Startup Repair and Bootrec.exe

How to use the Bootrec.exe tool in the Windows Recovery Environment to
troubleshoot and repair startup issues in Windows Vista
http://support.microsoft.com/kb/927392/en-us

A Stop error occurs, or the computer stops responding when you try to start
Windows Vista
http://support.microsoft.com/kb/925810/en-us

I'd deploy these if replacing the driver (provided you can boot) doesn't
solve the problem:

You run the startup repair tool this way:

http://support.microsoft.com/kb/925810/en-us

How To Run Startup Repair In Vista Ultimate (Multiple Screenshots)
http://www.windowsvista.windowsreins...rtup/index.htm

Note The computer must be configured to start from a CD or from a DVD. For
information about how to configure the computer to start from a CD or from a
DVD, see the information that came with the computer.
2. Restart the computer. To do this, click Start, click the arrow next to
the Lock button, and then click Restart.

This usually means that you enter bios setup by whatever key or keys
(sometimes there is more than one key that will do it for your model--go to
pc manufacturer site) and configure CD to be first in the boot order.

See for ref:
Access/Enter Motherboard BIOS
http://www.michaelstevenstech.com/bios_manufacturer.htm

Note If you cannot restart the computer by using this method, use the power
button to turn off the computer. Then, turn the computer back on.
3. Set your language preference, and then click Next.

Note In most cases, the startup repair process starts automatically, and you
do not have the option to select it in the System Recovery Options menu.
4. Click Repair your computer.
5. In the System Recovery Options dialog box, click the operating system
that you want to repair, and then click Next.
6. In the System Recovery Options menu, click Startup Repair to start the
repair process.
7. When the repair process is complete, click Finish.

Additional References for Startup Repair With Screenshots:

How to Use Startup Repair:

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

Screenshot: System Recovery Options (Lower Left Link)
http://blogs.itecn.net/photos/liuhui...4/500x375.aspx

Screenshot: (Click first option "Startup Repair"
http://www.leedesmond.com/images/img...SysRecOpt2.bmp

How To Run Startup Repair In Vista Ultimate (Multiple Screenshots)
http://www.windowsvista.windowsreins...rtup/index.htm

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 could also:

Try to F8 to the Windows Adv Options Menu>try 3 safe modes there (I don't
use WGA) and Last Known Good>then I go to Win RE in Vista. That gives you a
choice of Safe Mode, Safe Mode with Networking,and Safe Mode with Command
Prompt.

These methods are outlined in

A description of the Safe Mode Boot options in Windows XP/and Vista
http://support.microsoft.com/kb/315222/

You will need this reference:

How to start the System Restore tool at a command prompt in Windows XP
http://support.microsoft.com/kb/304449/en-us

The command to use for system restore at the safe mode cmd prompt is:

%systemroot%\system32\restore\rstrui.exe

The reason for doing this is one of these choices may work, when the other
doesn't. My experience is that people do not fully try F8 when they think
or have said they have. It is that they can almost always reach Windows
Advanced Options though.


Good luck,

CH



"Bill Hobson" <Ihatespamb-hobson@tamu.edu> wrote in message
news:66344672-2D59-4F82-AD77-B012DDDD812F@microsoft.com...
> Since MS only officially acknowledges 3 BSODs and these aren't on the
> list, can I safely assume that are about the same as their Windows XP
> counterparts?
>
> BSOD 1:
> Problem signature:
> Problem Event Name: BlueScreen
> OS Version: 6.0.6000.2.0.0.256.1
> Locale ID: 1033
>
> Additional information about the problem:
> BCCode: 1000007e
> BCP1: C0000005
> BCP2: 8998ABF4
> BCP3: 8669226C
> BCP4: 86691F68
> OS Version: 6_0_6000
> Service Pack: 0_0
> Product: 256_1
>
> BSOD 2:
> Problem signature:
> Problem Event Name: BlueScreen
> OS Version: 6.0.6000.2.0.0.256.1
> Locale ID: 1033
>
> Additional information about the problem:
> BCCode: 1000008e
> BCP1: C0000005
> BCP2: 8958AC4D
> BCP3: 937F6E60
> BCP4: 00000000
> OS Version: 6_0_6000
> Service Pack: 0_0
> Product: 256_1

On Mon, 5 Feb 2007 09:21:17 -0600, "Bill Hobson"
<Ihatespamb-hobson@tamu.edu> wrote:

>Since MS only officially acknowledges 3 BSODs and these aren't on the list,
>can I safely assume that are about the same as their Windows XP
>counterparts?
>
What are "BSODs"????????????

Alan

==

It's not that I think stupidity should be punishable by death.
I just think we should take the warning labels off of everything
and let the problem take care of itself.

--------------------------------------------------------

Alan Moorman wrote:

> On Mon, 5 Feb 2007 09:21:17 -0600, "Bill Hobson"
> <Ihatespamb-hobson@tamu.edu> wrote:
>
> > Since MS only officially acknowledges 3 BSODs and these aren't on
> > the list, can I safely assume that are about the same as their
> > Windows XP counterparts?
> >
> What are "BSODs"????????????
>
> Alan

http://www.youtube.com/watch?v=X44jcGJbBsA

HTH

--
Paul-B

Alan--

I think you asked this question on another thread a couple days ago perhaps
under a different name.

1) Where in the world is MSFT acknowledging BSODs and lol 3? MSFT has many
MSKBs already on stop errors (BSODs) in Vista and hundreds on XP.

2) What list are you referencing? Forgive me if I think whatever list you
mean isn't universally known as a BSOD list but you referenced it in both
threads you started.

3) You sure cannot assume many stop errors in Vista are the same as their XP
counterparts, because their are many different situations in Vista, although
some migh apply, and the means of fixing them have added Win RE for no boot
situations, and it's tools can be used in situations where you can still
boot as well.

For example:

How to use the Bootrec.exe tool in the Windows Recovery Environment to
troubleshoot and repair startup issues in Windows Vista
http://support.microsoft.com/kb/927392/en-us

A Stop error occurs, or the computer stops responding when you try to start
Windows Vista
http://support.microsoft.com/kb/925810/en-us

I'd deploy these if replacing the driver (provided you can boot) doesn't
solve the problem:

You run the startup repair tool this way:

http://support.microsoft.com/kb/925810/en-us

How To Run Startup Repair In Vista Ultimate (Multiple Screenshots)
http://www.windowsvista.windowsreins...rtup/index.htm

Note The computer must be configured to start from a CD or from a DVD. For
information about how to configure the computer to start from a CD or from a
DVD, see the information that came with the computer.
2. Restart the computer. To do this, click Start, click the arrow next to
the Lock button, and then click Restart.

This usually means that you enter bios setup by whatever key or keys
(sometimes there is more than one key that will do it for your model--go to
pc manufacturer site) and configure CD to be first in the boot order.

See for ref:
Access/Enter Motherboard BIOS
http://www.michaelstevenstech.com/bios_manufacturer.htm

Note If you cannot restart the computer by using this method, use the power
button to turn off the computer. Then, turn the computer back on.
3. Set your language preference, and then click Next.

Note In most cases, the startup repair process starts automatically, and you
do not have the option to select it in the System Recovery Options menu.
4. Click Repair your computer.
5. In the System Recovery Options dialog box, click the operating system
that you want to repair, and then click Next.
6. In the System Recovery Options menu, click Startup Repair to start the
repair process.
7. When the repair process is complete, click Finish.

Additional References for Startup Repair With Screenshots:

How to Use Startup Repair:

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

Screenshot: System Recovery Options (Lower Left Link)
http://blogs.itecn.net/photos/liuhui...4/500x375.aspx

Screenshot: (Click first option "Startup Repair"
http://www.leedesmond.com/images/img...SysRecOpt2.bmp

How To Run Startup Repair In Vista Ultimate (Multiple Screenshots)
http://www.windowsvista.windowsreins...rtup/index.htm

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 could also:

Try to F8 to the Windows Adv Options Menu>try 3 safe modes there (I don't
use WGA) and Last Known Good>then I go to Win RE in Vista. That gives you a
choice of Safe Mode, Safe Mode with Networking,and Safe Mode with Command
Prompt.

These methods are outlined in

A description of the Safe Mode Boot options in Windows XP/and Vista
http://support.microsoft.com/kb/315222/

You will need this reference:

How to start the System Restore tool at a command prompt in Windows XP
http://support.microsoft.com/kb/304449/en-us

The command to use for system restore at the safe mode cmd prompt is:

%systemroot%\system32\restore\rstrui.exe

The reason for doing this is one of these choices may work, when the other
doesn't. My experience is that people do not fully try F8 when they think
or have said they have. It is that they can almost always reach Windows
Advanced Options though.


Good luck,

CH




"Alan Moorman" <amoorman@visi.com> wrote in message
news:ujfhs25rj9au3b86afaodskuh7d6m8tjil@4ax.com...
> On Mon, 5 Feb 2007 09:21:17 -0600, "Bill Hobson"
> <Ihatespamb-hobson@tamu.edu> wrote:
>
>>Since MS only officially acknowledges 3 BSODs and these aren't on the
>>list,
>>can I safely assume that are about the same as their Windows XP
>>counterparts?
>>
> What are "BSODs"????????????
>
> Alan
>
> ==
>
> It's not that I think stupidity should be punishable by death.
> I just think we should take the warning labels off of everything
> and let the problem take care of itself.
>
> --------------------------------------------------------
>

Alan--

I'm sorry. I see you were quoting Bill Hobson--that was the original post.
I should have addressed questions on the list to him but for you--but if you
get a BSOD and can't boot or have serious Vista problems, what I did post
might help you. The BSOD is often associated with a problem in booting, but
does not have to be. It has an error with a number that isn't particularly
appreciated by a reaonable knowledge of the English language. Often that
error can be searched at http://support.microsoft.com but I know several of
them that may apply to many different applications in a variety of
circumstances that can come up on an MSKB search. You can configure XP or
Vista to show the BSOD insetead of attempting to reboot or go to the
Advanced Options screen when one happens.

If you want to make sure your possible BSOD stop stays on the screen for
reading, you can:

Windows Key +Pause Break>Under Startup and Recovery>Settings Button>take
check out of automatic restart. That way you get a good look at the error on
the BSOD which MSFT calls a "stop error."

BTW--I have no idea what the poster, Mr. Hobson was referring to when he
talked about a BSOD list or three BSODs acknowledge by MSFT. He never
elaborated on where he came up with this unique and interesting concept.

The BSOD was birthed in Windows 3.1 in April 1992 when 2 million copies sold
in the first 2 months replete with their BSODs and they have proudly carried
on the tradition, enabling more BSODs than ever to flourish during XP and
Vista. I think the Wagner Edstrom and McCann Ericson motto for Vista is
"The Wow Starts Now. More BSODs than ever in Vista and we again are forcing
OEM Named partners not to ship ways to recover from them by denying you a
Vista DVD when you pay $1000-4000 of your hard earned money for a computer
with pre-loaded Visduh on it."

What surprises me greatly is that MSN Live has not sought to use BSODs as
yet another advertising opportunity in their massive efforts to "catcup"
with the bad boys from Google. For example--why not have a beer or Kevin
Federline ad on a BSOD to lighten things up and accumulate more Redmond
revenue?

http://www.bbspot.com/News/2002/10/bsod_ads.html

Also if you keep your eyes peeled, you can encounter BSODs on the streeet
(always fun):

Blue Screen of Death Top 10
http://www.miguelcarrasco.net/miguel...creen_of_.html


What's a BSOD (Blue Screen of Death)?

http://www.slate.com/id/2107471/

http://en.wikipedia.org/wiki/Blue_Screen_of_Death

http://www.microsoft.com/technet/arc...hrep/bsod.mspx

http://daimyo.org/bsod/

CH

LOL--as they ride the titanic, Irv "Scooter" Libby's $100 million defense
team filed motions this morning that indicate Darth Vader Cheney is chicken
to take the stand and may not be hauling his fat ass into the courtroom to
wrestle with his many lies in order to get hundreds of thousands dead in
Iraq and nearly 4000 Americans into Dover Coffins. That's called the
Ultimate Bush-Cheney Blue Screen of Death. The underlying issue in the
trial is "how crazy is the Harvard Law Grad who was Cheney's chief of staff"
who was so devoted to propping up the Iraq lies that he stupidly made up
scores of false accounts before a Grand Jury. When you get down to it, the
Bush administration lends a new dimension to the words "quitissentially
stupid."

Once again the old adage, the chickens who pushed and are pushing (they want
no debate in Congress which they regard as an annoyance) other peoples'
children, grandparents, sisters, brothers, mothers and fathers to death in
Iraq are afraid to come into the courtroom as one of their bretherin is
being shoved onto a bus to live in a 5X7 concerete slab.





"Alan Moorman" <amoorman@visi.com> wrote in message
news:ujfhs25rj9au3b86afaodskuh7d6m8tjil@4ax.com...
> On Mon, 5 Feb 2007 09:21:17 -0600, "Bill Hobson"
> <Ihatespamb-hobson@tamu.edu> wrote:
>
>>Since MS only officially acknowledges 3 BSODs and these aren't on the
>>list,
>>can I safely assume that are about the same as their Windows XP
>>counterparts?
>>
> What are "BSODs"????????????
>
> Alan
>
> ==
>
> It's not that I think stupidity should be punishable by death.
> I just think we should take the warning labels off of everything
> and let the problem take care of itself.
>
> --------------------------------------------------------
>

The 2 BSODs I have received have nothing to do with booting. Both happened
days after booting. I am guessing that the first one MAY be the USB hub
problem and installed the patch for that. The second, again I am guessing,
happened when opening a Word document, so it may be printer driver related,
so I let Vista search and install it for me. Now comes the waiting game to
see if what I have done fixes what I ran into. In addition, I stopped Vista
for auto-rebooting after a BSOD, hoping more information might be available.

Since I can only find 3 KB articles based on the term BSOD - which it
prominently says at the top of the message WIndows gives me, there is little
information to go on. The hex codes found a dearth of responses - back to
the three I found with BSOD.

It is almost as if MS does not want to acknowledge that there are BSODs,
IMHO.

And if someone knows ways to get more "inside info" on BSODs in VIsta,
please post where.



"Chad Harris" <vistaneedsmuchowork.net> wrote in message
news:OhUUwfiSHHA.3428@TK2MSFTNGP04.phx.gbl...
> Alan--
>
> I'm sorry. I see you were quoting Bill Hobson--that was the original
> post. I should have addressed questions on the list to him but for
> you--but if you get a BSOD and can't boot or have serious Vista problems,
> what I did post might help you. The BSOD is often associated with a
> problem in booting, but does not have to be. It has an error with a
> number that isn't particularly appreciated by a reaonable knowledge of the
> English language. Often that error can be searched at
> http://support.microsoft.com but I know several of them that may apply to
> many different applications in a variety of circumstances that can come up
> on an MSKB search. You can configure XP or Vista to show the BSOD
> insetead of attempting to reboot or go to the Advanced Options screen when
> one happens.
>
> If you want to make sure your possible BSOD stop stays on the screen for
> reading, you can:
>
> Windows Key +Pause Break>Under Startup and Recovery>Settings Button>take
> check out of automatic restart. That way you get a good look at the error
> on the BSOD which MSFT calls a "stop error."
>
> BTW--I have no idea what the poster, Mr. Hobson was referring to when he
> talked about a BSOD list or three BSODs acknowledge by MSFT. He never
> elaborated on where he came up with this unique and interesting concept.
>
> The BSOD was birthed in Windows 3.1 in April 1992 when 2 million copies
> sold in the first 2 months replete with their BSODs and they have proudly
> carried on the tradition, enabling more BSODs than ever to flourish during
> XP and Vista. I think the Wagner Edstrom and McCann Ericson motto for
> Vista is "The Wow Starts Now. More BSODs than ever in Vista and we again
> are forcing OEM Named partners not to ship ways to recover from them by
> denying you a Vista DVD when you pay $1000-4000 of your hard earned money
> for a computer with pre-loaded Visduh on it."
>
> What surprises me greatly is that MSN Live has not sought to use BSODs as
> yet another advertising opportunity in their massive efforts to "catcup"
> with the bad boys from Google. For example--why not have a beer or Kevin
> Federline ad on a BSOD to lighten things up and accumulate more Redmond
> revenue?
>
> http://www.bbspot.com/News/2002/10/bsod_ads.html
>
> Also if you keep your eyes peeled, you can encounter BSODs on the streeet
> (always fun):
>
> Blue Screen of Death Top 10
> http://www.miguelcarrasco.net/miguel...creen_of_.html
>
>
> What's a BSOD (Blue Screen of Death)?
>
> http://www.slate.com/id/2107471/
>
> http://en.wikipedia.org/wiki/Blue_Screen_of_Death
>
> http://www.microsoft.com/technet/arc...hrep/bsod.mspx
>
> http://daimyo.org/bsod/
>
> CH
>
> LOL--as they ride the titanic, Irv "Scooter" Libby's $100 million defense
> team filed motions this morning that indicate Darth Vader Cheney is
> chicken to take the stand and may not be hauling his fat ass into the
> courtroom to wrestle with his many lies in order to get hundreds of
> thousands dead in Iraq and nearly 4000 Americans into Dover Coffins.
> That's called the Ultimate Bush-Cheney Blue Screen of Death. The
> underlying issue in the trial is "how crazy is the Harvard Law Grad who
> was Cheney's chief of staff" who was so devoted to propping up the Iraq
> lies that he stupidly made up scores of false accounts before a Grand
> Jury. When you get down to it, the Bush administration lends a new
> dimension to the words "quitissentially stupid."
>
> Once again the old adage, the chickens who pushed and are pushing (they
> want no debate in Congress which they regard as an annoyance) other
> peoples' children, grandparents, sisters, brothers, mothers and fathers
> to death in Iraq are afraid to come into the courtroom as one of their
> bretherin is being shoved onto a bus to live in a 5X7 concerete slab.
>
>
>
>
>
> "Alan Moorman" <amoorman@visi.com> wrote in message
> news:ujfhs25rj9au3b86afaodskuh7d6m8tjil@4ax.com...
>> On Mon, 5 Feb 2007 09:21:17 -0600, "Bill Hobson"
>> <Ihatespamb-hobson@tamu.edu> wrote:
>>
>>>Since MS only officially acknowledges 3 BSODs and these aren't on the
>>>list,
>>>can I safely assume that are about the same as their Windows XP
>>>counterparts?
>>>
>> What are "BSODs"????????????
>>
>> Alan
>>
>> ==
>>
>> It's not that I think stupidity should be punishable by death.
>> I just think we should take the warning labels off of everything
>> and let the problem take care of itself.
>>
>> --------------------------------------------------------
>>
>

Documentation on a fix of a BSOD

FYI:
Had additional BSOD and found a solution.
BCCode: d1

When I orginally went to Creative labs to find a Vista Driver for my
Creative SoundBlaster 24 Bit Live! sound card, none of the available drivers
would be accepted by Vista (all three of them), so I installed the drivers
that came with the card. It BSODed today and I found a different driver:
SB24_VTDRV_LB_1_04_0065.exe that actually would install and fixed this
particular BSOD. THe trigger was going to Control Panel, Sound and clicking
on the Sounds tab.

"Bill Hobson" <Ihatespamb-hobson@tamu.edu> wrote in message
news:66344672-2D59-4F82-AD77-B012DDDD812F@microsoft.com...
> Since MS only officially acknowledges 3 BSODs and these aren't on the
> list, can I safely assume that are about the same as their Windows XP
> counterparts?
>
> BSOD 1:
> Problem signature:
> Problem Event Name: BlueScreen
> OS Version: 6.0.6000.2.0.0.256.1
> Locale ID: 1033
>
> Additional information about the problem:
> BCCode: 1000007e
> BCP1: C0000005
> BCP2: 8998ABF4
> BCP3: 8669226C
> BCP4: 86691F68
> OS Version: 6_0_6000
> Service Pack: 0_0
> Product: 256_1
>
> BSOD 2:
> Problem signature:
> Problem Event Name: BlueScreen
> OS Version: 6.0.6000.2.0.0.256.1
> Locale ID: 1033
>
> Additional information about the problem:
> BCCode: 1000008e
> BCP1: C0000005
> BCP2: 8958AC4D
> BCP3: 937F6E60
> BCP4: 00000000
> OS Version: 6_0_6000
> Service Pack: 0_0
> Product: 256_1