Blue screen

0x0000007e (0x80000004)

Every so often I get a bluescreen during the boot process - Vista
Enterprise. Sometimes, and not others.

I'm really hopeless at pinpointing the cause - can anyone help out?

Thanks.

Danny wrote:

> 0x0000007e (0x80000004)
>
> Every so often I get a bluescreen during the boot process - Vista
> Enterprise. Sometimes, and not others.
>
> I'm really hopeless at pinpointing the cause - can anyone help out?

When during the boot process? In any case, random events are usually caused
by failing hardware. In your case, I'd test the RAM with Memtest86+ from
www.memtest.org. I also see that when you boot with Ultimate (and I assume
Enterprise) there is an option on the first screen for the Microsoft RAM
tester. You might want to try that one, too.

Malke
--
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic!"
MS-MVP Windows - Shell/User

"Malke" <notreally@invalid.invalid> wrote in message
news:uQ6ssjxNHHA.1872@TK2MSFTNGP04.phx.gbl...
> Danny wrote:
>
>> 0x0000007e (0x80000004)
>>
>> Every so often I get a bluescreen during the boot process - Vista
>> Enterprise. Sometimes, and not others.
>>
>> I'm really hopeless at pinpointing the cause - can anyone help out?
>
> When during the boot process?

After the POST, and before the welcome screen. During the black screen with
scrolling bar thingy.

> In any case, random events are usually caused
> by failing hardware.

It's not random though - it's always at the same point, it just doesn't
always happen. And it never happens in Windows.

> In your case, I'd test the RAM with Memtest86+ from
> www.memtest.org. I also see that when you boot with Ultimate (and I assume
> Enterprise) there is an option on the first screen for the Microsoft RAM
> tester. You might want to try that one, too.
>

I'll scan the ram, but I won't find anything - XP would also have been
unstable, and it wasn't.

Danny wrote:

>
> "Malke" <notreally@invalid.invalid> wrote in message
> news:uQ6ssjxNHHA.1872@TK2MSFTNGP04.phx.gbl...
>> Danny wrote:
>>
>>> 0x0000007e (0x80000004)
>>>
>>> Every so often I get a bluescreen during the boot process - Vista
>>> Enterprise. Sometimes, and not others.

>> When during the boot process?
>
> After the POST, and before the welcome screen. During the black screen
> with scrolling bar thingy.
>
>> In any case, random events are usually caused
>> by failing hardware.
>
> It's not random though - it's always at the same point, it just doesn't
> always happen. And it never happens in Windows.

Well, you said "every once in a while" and gave no further information.

>> In your case, I'd test the RAM with Memtest86+ from
>> www.memtest.org. I also see that when you boot with Ultimate (and I
>> assume Enterprise) there is an option on the first screen for the
>> Microsoft RAM tester. You might want to try that one, too.
>>
>
> I'll scan the ram, but I won't find anything - XP would also have been
> unstable, and it wasn't.

Actually, it's quite possible that Vista is accessing a different address of
the RAM than XP so your conclusion that "XP would also have been unstable"
is erroneous. There have been several posts in the Vista ng's recently
about this very topic.

In any case, since I can't see your computer from here and you supplied no
information about it, I gave you the logical next step in troubleshooting.
Something is failing and you need to find out what it is. The only way to
do this is by methodical troubleshooting. Here are general hardware
troubleshooting steps:

http://www.elephantboycomputers.com/...ardware_Tshoot

It could also be caused by flaky drivers, particularly in these early days
of Vista RTM. Look in Vista's Event Viewer for clues. And you should also
ask yourself The First Question Of Troubleshooting: what changed between
the time things worked and the time they didn't?

All of this is meant to help you narrow down the troubleshooting focus.

Malke
--
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic!"
MS-MVP Windows - Shell/User

Malke:
I can't agree more, especially with the phrase "but it works fine
with XP". Starting with XP x64 and now with Vista ram is addressed
differently and can have a flaw. I had a random BSOD with XP x64 about once
a week or two, always in the middle of working. I was running dual channel
ram, found one bad sector on one chip with Memtest86. I called Crucial for
an RMA on the defective stick, to my surprise they sent me an RMA for both
sticks since I was running dual channel. I haven't had a BSOD on that
computer since and the problem occurred while XP x64 was still in beta. Have
a great day.

--
Dennis Pack
Vista x64 Enterprise
Office 2007
"Malke" <notreally@invalid.invalid> wrote in message
news:eAJsA%23xNHHA.4720@TK2MSFTNGP03.phx.gbl...
> Danny wrote:
>
>>
>> "Malke" <notreally@invalid.invalid> wrote in message
>> news:uQ6ssjxNHHA.1872@TK2MSFTNGP04.phx.gbl...
>>> Danny wrote:
>>>
>>>> 0x0000007e (0x80000004)
>>>>
>>>> Every so often I get a bluescreen during the boot process - Vista
>>>> Enterprise. Sometimes, and not others.
>
>>> When during the boot process?
>>
>> After the POST, and before the welcome screen. During the black screen
>> with scrolling bar thingy.
>>
>>> In any case, random events are usually caused
>>> by failing hardware.
>>
>> It's not random though - it's always at the same point, it just doesn't
>> always happen. And it never happens in Windows.
>
> Well, you said "every once in a while" and gave no further information.
>
>>> In your case, I'd test the RAM with Memtest86+ from
>>> www.memtest.org. I also see that when you boot with Ultimate (and I
>>> assume Enterprise) there is an option on the first screen for the
>>> Microsoft RAM tester. You might want to try that one, too.
>>>
>>
>> I'll scan the ram, but I won't find anything - XP would also have been
>> unstable, and it wasn't.
>
> Actually, it's quite possible that Vista is accessing a different address
> of
> the RAM than XP so your conclusion that "XP would also have been unstable"
> is erroneous. There have been several posts in the Vista ng's recently
> about this very topic.
>
> In any case, since I can't see your computer from here and you supplied no
> information about it, I gave you the logical next step in troubleshooting.
> Something is failing and you need to find out what it is. The only way to
> do this is by methodical troubleshooting. Here are general hardware
> troubleshooting steps:
>
> http://www.elephantboycomputers.com/...ardware_Tshoot
>
> It could also be caused by flaky drivers, particularly in these early days
> of Vista RTM. Look in Vista's Event Viewer for clues. And you should also
> ask yourself The First Question Of Troubleshooting: what changed between
> the time things worked and the time they didn't?
>
> All of this is meant to help you narrow down the troubleshooting focus.
>
> Malke
> --
> Elephant Boy Computers
> www.elephantboycomputers.com
> "Don't Panic!"
> MS-MVP Windows - Shell/User

Dennis Pack wrote:

> Malke:
> I can't agree more, especially with the phrase "but it works fine
> with XP". Starting with XP x64 and now with Vista ram is addressed
> differently and can have a flaw. I had a random BSOD with XP x64 about
> once a week or two, always in the middle of working. I was running dual
> channel ram, found one bad sector on one chip with Memtest86. I called
> Crucial for an RMA on the defective stick, to my surprise they sent me an
> RMA for both sticks since I was running dual channel. I haven't had a BSOD
> on that computer since and the problem occurred while XP x64 was still in
> beta. Have a great day.
>

Thanks for that information, Dennis. We know that it was common for the same
RAM installed in older MS operating systems Win9x/ME to not work with XP
since XP was far fussier about marginal RAM. Your information indicates
that the same issues may arise with Vista. I appreciate the definitive
troubleshooting answer you provided.

You have a great day, too!

Malke
--
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic!"
MS-MVP Windows - Shell/User

"Malke" <notreally@invalid.invalid> wrote in message
news:eAJsA%23xNHHA.4720@TK2MSFTNGP03.phx.gbl...
> Danny wrote:
>
>>
>> "Malke" <notreally@invalid.invalid> wrote in message
>> news:uQ6ssjxNHHA.1872@TK2MSFTNGP04.phx.gbl...
>>> Danny wrote:
>>>
>>>> 0x0000007e (0x80000004)
>>>>
>>>> Every so often I get a bluescreen during the boot process - Vista
>>>> Enterprise. Sometimes, and not others.
>
>>> When during the boot process?
>>
>> After the POST, and before the welcome screen. During the black screen
>> with scrolling bar thingy.
>>
>>> In any case, random events are usually caused
>>> by failing hardware.
>>
>> It's not random though - it's always at the same point, it just doesn't
>> always happen. And it never happens in Windows.
>
> Well, you said "every once in a while" and gave no further information.

I didn't say anything of the sort my friend, I said it always happened at
the same time when it occurred, but did not always happen.

>
>>> In your case, I'd test the RAM with Memtest86+ from
>>> www.memtest.org. I also see that when you boot with Ultimate (and I
>>> assume Enterprise) there is an option on the first screen for the
>>> Microsoft RAM tester. You might want to try that one, too.
>>>
>>
>> I'll scan the ram, but I won't find anything - XP would also have been
>> unstable, and it wasn't.
>
> Actually, it's quite possible that Vista is accessing a different address
> of
> the RAM than XP so your conclusion that "XP would also have been unstable"
> is erroneous. There have been several posts in the Vista ng's recently
> about this very topic.

The thought occurs: if the RAM is flaky, and Vista's boot process accesses
an area of it causing BSOD's, is it realistic to suggest that XP has NEVER
accessed that same address? Under ANY circumstances? I find that extremely
difficult to believe.

>
> In any case, since I can't see your computer from here and you supplied no
> information about it, I gave you the logical next step in troubleshooting.
> Something is failing and you need to find out what it is. The only way to
> do this is by methodical troubleshooting. Here are general hardware
> troubleshooting steps:
>
> http://www.elephantboycomputers.com/...ardware_Tshoot
>
> It could also be caused by flaky drivers, particularly in these early days
> of Vista RTM. Look in Vista's Event Viewer for clues. And you should also
> ask yourself The First Question Of Troubleshooting: what changed between
> the time things worked and the time they didn't?

The one change I specifically recall was that I installed a Samsung printer
driver and thereafter, I believe, the boot process became hit and miss. I
have removed it now and hope it helps.

>
> All of this is meant to help you narrow down the troubleshooting focus.
>

And I appreciate all help.

"Dennis Pack" <dennispack@nospam.hotmail.com> wrote in message
newsB05B476-932C-452A-8085-3A1DE005FC30@microsoft.com...
> Malke:
> I can't agree more, especially with the phrase "but it works fine
> with XP". Starting with XP x64 and now with Vista ram is addressed
> differently and can have a flaw. I had a random BSOD with XP x64 about
> once a week or two, always in the middle of working. I was running dual
> channel ram, found one bad sector on one chip with Memtest86. I called
> Crucial for an RMA on the defective stick, to my surprise they sent me an
> RMA for both sticks since I was running dual channel. I haven't had a BSOD
> on that computer since and the problem occurred while XP x64 was still in
> beta. Have a great day.
>

>
I don't see how this helps. You're saying you had RAM causing instability in
XP x64 - then you got that RAM replaced and thereafter XP x64 was stable.

What difference does this make to Vista? Or to this thread?

Danny:
I used XP x64 as an example of how ram can cause oddities from
personal experience. Vista is the same as XP x64 as towards addressing ram
differently. As a side note that same computer is running Vista and other
test programs without any problems, the only change made since it was built
is the replacement of the defective ram over 2 years ago. The whole basis
for my answer is to not overlook ram as a possible cause since there are no
problems when running XP. Have a great day.

--
Dennis Pack
Vista x64 Enterprise
Office 2007
"Danny" <me@there.com> wrote in message
news:zo8qh.36558$RL5.23143@newsfe2-gui.ntli.net...
>
> "Dennis Pack" <dennispack@nospam.hotmail.com> wrote in message
> newsB05B476-932C-452A-8085-3A1DE005FC30@microsoft.com...
>> Malke:
>> I can't agree more, especially with the phrase "but it works fine
>> with XP". Starting with XP x64 and now with Vista ram is addressed
>> differently and can have a flaw. I had a random BSOD with XP x64 about
>> once a week or two, always in the middle of working. I was running dual
>> channel ram, found one bad sector on one chip with Memtest86. I called
>> Crucial for an RMA on the defective stick, to my surprise they sent me an
>> RMA for both sticks since I was running dual channel. I haven't had a
>> BSOD on that computer since and the problem occurred while XP x64 was
>> still in beta. Have a great day.
>>
>
>>
> I don't see how this helps. You're saying you had RAM causing instability
> in XP x64 - then you got that RAM replaced and thereafter XP x64 was
> stable.
>
> What difference does this make to Vista? Or to this thread?

It would be nice if you could show a little civility to those trying to help
you. If you don't want the advice, just ignore it and/or just go away
quietly. If you can't relate to simple examples, well ...

"Danny" <me@there.com> wrote in message
news:zo8qh.36558$RL5.23143@newsfe2-gui.ntli.net...
>
> "Dennis Pack" <dennispack@nospam.hotmail.com> wrote in message
> newsB05B476-932C-452A-8085-3A1DE005FC30@microsoft.com...
>> Malke:
>> I can't agree more, especially with the phrase "but it works fine
>> with XP". Starting with XP x64 and now with Vista ram is addressed
>> differently and can have a flaw. I had a random BSOD with XP x64 about
>> once a week or two, always in the middle of working. I was running dual
>> channel ram, found one bad sector on one chip with Memtest86. I called
>> Crucial for an RMA on the defective stick, to my surprise they sent me an
>> RMA for both sticks since I was running dual channel. I haven't had a
>> BSOD on that computer since and the problem occurred while XP x64 was
>> still in beta. Have a great day.
>>
>
>>
> I don't see how this helps. You're saying you had RAM causing instability
> in XP x64 - then you got that RAM replaced and thereafter XP x64 was
> stable.
>
> What difference does this make to Vista? Or to this thread?