blue screen

cdruce

does having two copies of drivers for the cpu cause problems they look
identical can either one be removed, also have two identical copies for the
keyboard.
i installed my os hdd on a new machine and now need to work out the bsod
bugs four crashes in three days, nothing is the same "kernal stack in page
error" "win32k.sys' Is there any place to help decipher the problem reports?

Andrew McLaren

"cdruce" <> wrote ...
> does having two copies of drivers for the cpu cause problems they look
> identical can either one be removed, also have two identical copies for
> the
> keyboard.
> i installed my os hdd on a new machine and now need to work out the bsod
> bugs four crashes in three days, nothing is the same "kernal stack in page
> error" "win32k.sys' Is there any place to help decipher the problem
> reports?

When you say "i installed my os hdd on a new machine and now need to work
out the bsod", does that mean you took a hard disk, with an existing
installation of Vista, and moved it to a new machine? If so, this is an
*extremely* unreliable way of installing Vista. Yes, it seems easier than
doing a full clean install ... but it is also much less reliable. Even when
devices have "identical" standard interfaces (such as SATA drives, or Video
cards) they usually have different PnP IDs - so the existing driver which
was configured on the old machine may not be appropriate for the new
machine. Hence blue screens, weird errors etc.

The most reliable way to get the correct set of device drivers is to do a
clean install of Vista.

Analyzing STOP error dumps and error messages is quite straightforward, if
you have a good knowledge of assembly language. Just install the Windows
debugging tools from:


But if you are a end-user, your best bet is to upload the dump to Microsoft,
and let them do the analysis for you. Online Crash Analysis ("OCA") is free
and immediate:


Hope it helps,
Andrew

cdruce

I used the debugging tools to determine that it is related to the hdd
downloaded test sofware from western it says i have a faulty cable ?? all
three cables have same result . (tried three cables on the same single drive)
but still couldnt figure out how to use the microsoft oca site
"Andrew McLaren" wrote:

> "cdruce" <> wrote ...
> > does having two copies of drivers for the cpu cause problems they look
> > identical can either one be removed, also have two identical copies for
> > the
> > keyboard.
> > i installed my os hdd on a new machine and now need to work out the bsod
> > bugs four crashes in three days, nothing is the same "kernal stack in page
> > error" "win32k.sys' Is there any place to help decipher the problem
> > reports?
>
> When you say "i installed my os hdd on a new machine and now need to work
> out the bsod", does that mean you took a hard disk, with an existing
> installation of Vista, and moved it to a new machine? If so, this is an
> *extremely* unreliable way of installing Vista. Yes, it seems easier than
> doing a full clean install ... but it is also much less reliable. Even when
> devices have "identical" standard interfaces (such as SATA drives, or Video
> cards) they usually have different PnP IDs - so the existing driver which
> was configured on the old machine may not be appropriate for the new
> machine. Hence blue screens, weird errors etc.
>
> The most reliable way to get the correct set of device drivers is to do a
> clean install of Vista.
>
> Analyzing STOP error dumps and error messages is quite straightforward, if
> you have a good knowledge of assembly language. Just install the Windows
> debugging tools from:
>
>
> But if you are a end-user, your best bet is to upload the dump to Microsoft,
> and let them do the analysis for you. Online Crash Analysis ("OCA") is free
> and immediate:
>
>
> Hope it helps,
> Andrew
>

Andrew McLaren

"cdruce" <> wrote ...
> I used the debugging tools to determine that it is related to the hdd
> downloaded test sofware from western it says i have a faulty cable ?? all
> three cables have same result . (tried three cables on the same single
> drive)
> but still couldnt figure out how to use the microsoft oca site

What was the STOP error you received?

eg STOP: 0x0000007B (Inaccessible Boot device), STOP: 0x0000000A (IRQL less
than or equal), etc

cdruce

ok it appears to be fixed used repair install.... somtimes you cant see the
forest for the trees. thanks for the help

"Andrew McLaren" wrote:

> "cdruce" <> wrote ...
> > I used the debugging tools to determine that it is related to the hdd
> > downloaded test sofware from western it says i have a faulty cable ?? all
> > three cables have same result . (tried three cables on the same single
> > drive)
> > but still couldnt figure out how to use the microsoft oca site
>
> What was the STOP error you received?
>
> eg STOP: 0x0000007B (Inaccessible Boot device), STOP: 0x0000000A (IRQL less
> than or equal), etc
>
>