Re: How do diagnose & report BSoD during XP x64 boot?

Enable boot logging in Advanced Startup menu if you want a boot log.


"@southdown,co,uk" <""jgrieve\"@southdown,co,uk"> wrote in message
news:...
> Hi all,
>
> I installed XP Pro x64 last night on my home PC, but I get a BSoD upon
> first boot, after Setup. Setup was performed by booting from the CD in
> the usual way. The only quirks of this installation are, I used F6 to add
> the Promise RAID controller driver during setup and the HDD partitions
> look something like this:
>
> [<--- XP Pro 32-bit --->][<-- XP Pro x64 -->][<- Old XP ->]
>
> ...i.e. x64 build lives on a partition in the middle of a 160Gb RAID-0
> array. FWIW, this is how it was when I installed the last 2 x64 RCs with
> no problems.
>
> How can I diagnose this? Is there a log file written during boot? If so,
> where?
>
> I get the problem on a regular boot, Safe Mode and Safe Mode Command
> Prompt. In the last two modes, I see a list of drivers being loaded, and
> I (v. v. briefly) see "ASPITABL" as the last entry, although I think I
> remember correctly that this is irrelevant, as it's the next driver
> that'll be causing the problem.
>
> How can I report this problem to MS? Here, in this NG?
>
> Thanks,
> Jon

John Barnes

Hi John,

How do I do that - bearing in mind that I can't boot the system. Is
this something I can tweak in BOOT.INI from a different partition?

Jon





John Barnes wrote:
> Enable boot logging in Advanced Startup menu if you want a boot log.
>
>
> "@southdown,co,uk" <""jgrieve\"@southdown,co,uk"> wrote in message
> news:...
>
>>Hi all,
>>
>>I installed XP Pro x64 last night on my home PC, but I get a BSoD upon
>>first boot, after Setup. Setup was performed by booting from the CD in
>>the usual way. The only quirks of this installation are, I used F6 to add
>>the Promise RAID controller driver during setup and the HDD partitions
>>look something like this:
>>
>>[<--- XP Pro 32-bit --->][<-- XP Pro x64 -->][<- Old XP ->]
>>
>>...i.e. x64 build lives on a partition in the middle of a 160Gb RAID-0
>>array. FWIW, this is how it was when I installed the last 2 x64 RCs with
>>no problems.
>>
>>How can I diagnose this? Is there a log file written during boot? If so,
>>where?
>>
>>I get the problem on a regular boot, Safe Mode and Safe Mode Command
>>Prompt. In the last two modes, I see a list of drivers being loaded, and
>>I (v. v. briefly) see "ASPITABL" as the last entry, although I think I
>>remember correctly that this is irrelevant, as it's the next driver
>>that'll be causing the problem.
>>
>>How can I report this problem to MS? Here, in this NG?
>>
>>Thanks,
>>Jon
>
>
>

It is on the same menu screen F8 where you said you selected safe mode



"Jon Grieve" <jgrieve@southdown-co-uk> wrote in message
news:%...
>
> Hi John,
>
> How do I do that - bearing in mind that I can't boot the system. Is this
> something I can tweak in BOOT.INI from a different partition?
>
> Jon
>
>
>
>
>
> John Barnes wrote:
>> Enable boot logging in Advanced Startup menu if you want a boot log.
>>
>>
>> "@southdown,co,uk" <""jgrieve\"@southdown,co,uk"> wrote in message
>> news:...
>>
>>>Hi all,
>>>
>>>I installed XP Pro x64 last night on my home PC, but I get a BSoD upon
>>>first boot, after Setup. Setup was performed by booting from the CD in
>>>the usual way. The only quirks of this installation are, I used F6 to
>>>add the Promise RAID controller driver during setup and the HDD
>>>partitions look something like this:
>>>
>>>[<--- XP Pro 32-bit --->][<-- XP Pro x64 -->][<- Old XP ->]
>>>
>>>...i.e. x64 build lives on a partition in the middle of a 160Gb RAID-0
>>>array. FWIW, this is how it was when I installed the last 2 x64 RCs with
>>>no problems.
>>>
>>>How can I diagnose this? Is there a log file written during boot? If
>>>so, where?
>>>
>>>I get the problem on a regular boot, Safe Mode and Safe Mode Command
>>>Prompt. In the last two modes, I see a list of drivers being loaded, and
>>>I (v. v. briefly) see "ASPITABL" as the last entry, although I think I
>>>remember correctly that this is irrelevant, as it's the next driver
>>>that'll be causing the problem.
>>>
>>>How can I report this problem to MS? Here, in this NG?
>>>
>>>Thanks,
>>>Jon
>>
>>