Norman
Wed Aug 03 23:19:42 CDT 2005
I agree, if the boot failed or hanged then it was more likely due to an
action that was attempted after successfully loading drivers whose names
made it into the boot log.
But if the boot BSODed due to a defective action by a driver, isn't it
possible that the defective driver's name was already recorded in the boot
log when it was about to be loaded?
"Doron Holan [MS]" <doronh@nospam.microsoft.com> wrote in message
news:%23cwLSd$lFHA.3300@TK2MSFTNGP15.phx.gbl...
> In all my time debugging failed / hung boots, the last driver to load
> during the boot process is typically *NOT* the culprit.
>
> d
>
> --
> Please do not send e-mail directly to this alias. this alias is for
> newsgroup purposes only.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
>
> "Norman Diamond" <ndiamond@community.nospam> wrote in message
> news:uVVm1N8lFHA.764@TK2MSFTNGP14.phx.gbl...
>> "Pavel A." <pavel_a@NOwritemeNO.com> wrote in message
>> news:F687B902-1685-44B9-BC6C-534C544FB03C@microsoft.com...
>>> "Omer" wrote:
>>>> And if there was a BSOD, is there any way to know what driver caused
>>>> it,
>>>> or what was the last loading driver?
>>>
>>> Again, not exactly. The dump analyzer of windbg has a "knowledge base"
>>> that allows it to guess the root cause of the crash.
>>> Of course it is not always the last driver.
>>
>> It is still interesting to know what was the last loading driver, because
>> there is a somewhat higher than average probability that the BSOD was due
>> to
>> either that driver or the next one which was supposed to load next.
>>
>>> An unsigned driver from unknown vendor possibly is the culprit.
>>
>> A signed driver from a known vendor possibly is the culprit too.
>> Especially
>> in some known cases.
>>
>
>