BSOD when boot from Check Build Vista

allen_zhang · July 9, 2010, 3:15am

Hello everyone,

VMWare Server 2.0.0.0
Host: XP Pro, SP3

I created a new VM using the automatic settings for Vista. And then I mapped the CD-ROM to the en_windows_vista_x86_check_dvd_X13-31668.iso file from msdn subscriber downloads.

I get the BSOD with STOP: 0x0000008E (0xC0000420, 0x820653A0, 0x8F328854, 0x00000000)
Collecting data from crash dump …
Initalizing disk from crash dump …

I get the BSOD when select “start” button from “Thank you” page of the “Setup Up Windows”.

Best Regards,
Allen

Feitao_Zhou · July 9, 2010, 5:06am

Just enable 1 processor

mm1 · July 9, 2010, 10:16am

Is that in ACPI.SYS?

mm

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@sina.com
Sent: Friday, July 09, 2010 3:14 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] BSOD when boot from Check Build Vista

Hello everyone,

VMWare Server 2.0.0.0
Host: XP Pro, SP3

I created a new VM using the automatic settings for Vista. And then I mapped
the CD-ROM to the en_windows_vista_x86_check_dvd_X13-31668.iso file from
msdn subscriber downloads.

I get the BSOD with STOP: 0x0000008E (0xC0000420, 0x820653A0, 0x8F328854,
0x00000000) Collecting data from crash dump …
Initalizing disk from crash dump …

I get the BSOD when select “start” button from “Thank you” page of the
“Setup Up Windows”.

Best Regards,
Allen

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

Gary_Little-3 · July 9, 2010, 11:01am

Did you take a look at the help docs for WinDbg and find out what the 0x8e
bug check code means? Did you do an !analyze -v? Check NTSTATUS.H for
0xC0000420?

Gary G. Little
H (952) 223-1349
C (952) 454-4629
xxxxx@comcast.net

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@sina.com
Sent: Friday, July 09, 2010 2:14 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] BSOD when boot from Check Build Vista

Hello everyone,

VMWare Server 2.0.0.0
Host: XP Pro, SP3

I created a new VM using the automatic settings for Vista. And then I mapped
the CD-ROM to the en_windows_vista_x86_check_dvd_X13-31668.iso file from
msdn subscriber downloads.

I get the BSOD with STOP: 0x0000008E (0xC0000420, 0x820653A0, 0x8F328854,
0x00000000) Collecting data from crash dump …
Initalizing disk from crash dump …

I get the BSOD when select “start” button from “Thank you” page of the
“Setup Up Windows”.

Best Regards,
Allen

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

allen_zhang · July 9, 2010, 11:43am

Hi, Feitao Zhou, mm & Gary Little.
Thank you for your help.

Feitao Zhou:
Yes, Just enable 1 processor, There is default setting.
And I try to setting 2 processor, The same BSOD will be find.

mm & Gary Little,
I know means of the bug check,“This bug check indicates that a kernel-mode application generated an exception that the error handler did not catch.”
But, How can I start kernel debug? How to setting befoer OS be load on VMWare server 2.0.0.0?
The setup is pending, I can’t enter desktop at all, The BSOD will be find after I input user name,computer name and select “start” button.

Best Regards,
Allen

allen_zhang · July 9, 2010, 11:55am

Another details, The different user name must be choose after BSOD in “Chose a user and picture” of “Set Up Windows”, That is to say, the user account is added, Why do I have to enter a new account?

Allen

Mark_Roddy · July 9, 2010, 11:59am

Checked builds and VMs are generally problematic.
I’d suggest not bothering with that particular configuration and instead
moving to a physical system.

Mark Roddy

On Fri, Jul 9, 2010 at 11:42 AM, wrote:

> Hi, Feitao Zhou, mm & Gary Little.
> Thank you for your help.
>
> Feitao Zhou:
> Yes, Just enable 1 processor, There is default setting.
> And I try to setting 2 processor, The same BSOD will be find.
>
> mm & Gary Little,
> I know means of the bug check,“This bug check indicates that a kernel-mode
> application generated an exception that the error handler did not catch.”
> But, How can I start kernel debug? How to setting befoer OS be load on
> VMWare server 2.0.0.0?
> The setup is pending, I can’t enter desktop at all, The BSOD will be find
> after I input user name,computer name and select “start” button.
>
> Best Regards,
> Allen
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>

Gary_Little-3 · July 9, 2010, 12:55pm

Again, did you check the WinDbg documentation for debugging a virtual
machine? I use WinDbg on 32 bit XP which uses Virtual PC. You have to use a
named pipe and set the virtual PC session to break at first load or break at
fist symbol load. Again, check the docs. You can debug a virtual machine
using WinDbg. Also, some folks have been proclaiming the glory of VirtualKD.
You might check that out.

Gary G. Little
H (952) 223-1349
C (952) 454-4629
xxxxx@comcast.net

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@sina.com
Sent: Friday, July 09, 2010 10:42 AM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] BSOD when boot from Check Build Vista

Hi, Feitao Zhou, mm & Gary Little.
Thank you for your help.

Feitao Zhou:
Yes, Just enable 1 processor, There is default setting.
And I try to setting 2 processor, The same BSOD will be find.

mm & Gary Little,
I know means of the bug check,“This bug check indicates that a kernel-mode
application generated an exception that the error handler did not catch.”
But, How can I start kernel debug? How to setting befoer OS be load on
VMWare server 2.0.0.0?
The setup is pending, I can’t enter desktop at all, The BSOD will be find
after I input user name,computer name and select “start” button.

Best Regards,
Allen

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

Tim_Roberts · July 9, 2010, 1:10pm

xxxxx@sina.com wrote:

Another details, The different user name must be choose after BSOD in “Chose a user and picture” of “Set Up Windows”, That is to say, the user account is added, Why do I have to enter a new account?

This is entirely the wrong forum for this question. If the machine
crashes before it completed setting up User #1, it might think that you
haven’t set up any users at all.

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

mm1 · July 9, 2010, 1:15pm

And unfortunately windbg won’t help you here either, unless you can figure
out how to debug setup, which used to be documented, but no longer is.

mm

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Tim Roberts
Sent: Friday, July 09, 2010 1:10 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] BSOD when boot from Check Build Vista

xxxxx@sina.com wrote:

Another details, The different user name must be choose after BSOD in
“Chose a user and picture” of “Set Up Windows”, That is to say, the user
account is added, Why do I have to enter a new account?

This is entirely the wrong forum for this question. If the machine crashes
before it completed setting up User #1, it might think that you haven’t set
up any users at all.

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

allen_zhang · July 9, 2010, 1:30pm

Hi, Gary Little
Thank you very much.

Yes I set the kernel debug by pipe,
It should be correct, because I can start kernel debug for another system.
I set by the follow setps.
1, Config VM hardware, Add serial port, and named “\.\pipe\com_1”, Near End: Is a server. Far End: Is an application.
I/O Mode, Select Yield CPU on poll.
2,Start Windbg with the follow parameters,
baud rate: 115200
Pipe is checked
Port: \.\pipe\com_1,

It can be start to kernel debug when VM power on,
and then I set “Cycle Initial Break”,
Power off VM, and restart it(power on).
I can see the follow message in windbg,

Opened \.\pipe\com_1
Waiting to reconnect …
Will request initial breakpoint at next boot.

All the message I can see until BOSD, the BOSD can’t be captured, what’s wrong with my setting? Thanks a lot.

Allen

Tim_Roberts · July 9, 2010, 1:36pm

xxxxx@sina.com wrote:

Yes I set the kernel debug by pipe,
It should be correct, because I can start kernel debug for another system.
…
It can be start to kernel debug when VM power on,
and then I set “Cycle Initial Break”,
Power off VM, and restart it(power on).
I can see the follow message in windbg,

Opened \.\pipe\com_1
Waiting to reconnect …
Will request initial breakpoint at next boot.

All the message I can see until BOSD, the BOSD can’t be captured, what’s wrong with my setting? Thanks a lot.

Have you configured boot.ini or bcdedit to enable kernel debugging? Are
you selecting your kernel debug enabled option at boot time?

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

mm1 · July 9, 2010, 2:16pm

Is this during setup?

mm

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@sina.com
Sent: Friday, July 09, 2010 1:28 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] BSOD when boot from Check Build Vista

Hi, Gary Little
Thank you very much.

Yes I set the kernel debug by pipe,
It should be correct, because I can start kernel debug for another system.
I set by the follow setps.
1, Config VM hardware, Add serial port, and named “\.\pipe\com_1”, Near
End: Is a server. Far End: Is an application.
I/O Mode, Select Yield CPU on poll.
2,Start Windbg with the follow parameters, baud rate: 115200 Pipe is checked
Port: \.\pipe\com_1,

It can be start to kernel debug when VM power on, and then I set “Cycle
Initial Break”, Power off VM, and restart it(power on).
I can see the follow message in windbg,

Opened \.\pipe\com_1
Waiting to reconnect …
Will request initial breakpoint at next boot.

All the message I can see until BOSD, the BOSD can’t be captured, what’s
wrong with my setting? Thanks a lot.

Allen

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

allen_zhang · July 9, 2010, 2:22pm

Thank you,Tim Roberts
Yes, I know, Boot.ini should configured, but It doesn’t start once, So I can’t edit boot.ini at all.
I can’t enable kernel debug option at boot time because I press F8 too slowly.
I try agian press F8 quickly, I can select “kernel debug enabled option”.

And the follow lines is the debug information about the BOSD,

MODULE_NAME: nt
FAULTING_MODULE: 81800000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4549ac73

FAULTING_IP:
hal!HalGetInterruptTargetInformation+608
820653a0 cd2c int 2Ch

EXCEPTION_RECORD: ffffffff – (.exr 0xffffffffffffffff)
ExceptionAddress: 820653a0 (hal!HalGetInterruptTargetInformation+0x00000608)
ExceptionCode: c0000420 (Assertion failure)
ExceptionFlags: 00000000
NumberParameters: 0

ERROR_CODE: (NTSTATUS) 0xc0000420 -
EXCEPTION_CODE: (NTSTATUS) 0xc0000420 -
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x0
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 82065782 to 820653a0

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
8eb0fbf8 82065782 8eb0fc44 8193578e 00000000 hal!HalGetInterruptTargetInformation+0x608
8eb0fc00 8193578e 00000000 81936ef9 844b8d78 hal!HalGetInterruptTargetInformation+0x9ea
8eb0fc44 81959bd8 90743520 8eb0fd44 00000000 nt!WmiTraceMessageVa+0x61a
8eb0fcac 8183c108 906473b8 00000000 00f0f4ec nt!KiDispatchInterrupt+0x2e8
8eb0fd08 81ed0441 8eb0f901 00000000 8eb0fd2c nt!KeDelayExecutionThread+0x42e
8eb0fd54 81954e83 00000000 00f0f508 00f0f518 nt!ProbeForRead+0x89d1
8eb0fd64 76a13ea4 badb0d00 00f0f4e4 00000000 nt!KeReleaseInStackQueuedSpinLockFromDpcLevel+0xc47
8eb0fd68 badb0d00 00f0f4e4 00000000 00000000 ntdll!KiFastSystemCallRet
8eb0fd6c 00f0f4e4 00000000 00000000 00000000 0xbadb0d00
8eb0fd70 00000000 00000000 00000000 00000000 0xf0f4e4

STACK_COMMAND: kb

FOLLOWUP_IP:
nt!WmiTraceMessageVa+61a
8193578e c3 ret

SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nt!WmiTraceMessageVa+61a
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: ntkrpamp.exe
BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner
---------

Best Regards,
Allen

Scott_Noone_OSR · July 9, 2010, 2:36pm

Your symbols are wrong, type:

.symfix c:\websymbols
.reload

And then run !analyze -v again.

-scott

–
Scott Noone
Consulting Associate
OSR Open Systems Resources, Inc.
http://www.osronline.com

wrote in message news:xxxxx@ntdev…
> Thank you,Tim Roberts
> Yes, I know, Boot.ini should configured, but It doesn’t start once, So I
> can’t edit boot.ini at all.
> I can’t enable kernel debug option at boot time because I press F8 too
> slowly.
> I try agian press F8 quickly, I can select “kernel debug enabled option”.
>
>
> And the follow lines is the debug information about the BOSD,
>
> MODULE_NAME: nt
> FAULTING_MODULE: 81800000 nt
> DEBUG_FLR_IMAGE_TIMESTAMP: 4549ac73
>
> FAULTING_IP:
> hal!HalGetInterruptTargetInformation+608
> 820653a0 cd2c int 2Ch
>
> EXCEPTION_RECORD: ffffffff – (.exr 0xffffffffffffffff)
> ExceptionAddress: 820653a0
> (hal!HalGetInterruptTargetInformation+0x00000608)
> ExceptionCode: c0000420 (Assertion failure)
> ExceptionFlags: 00000000
> NumberParameters: 0
>
> ERROR_CODE: (NTSTATUS) 0xc0000420 -
> EXCEPTION_CODE: (NTSTATUS) 0xc0000420 -
> DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
> BUGCHECK_STR: 0x0
> CURRENT_IRQL: 0
> LAST_CONTROL_TRANSFER: from 82065782 to 820653a0
>
> STACK_TEXT:
> WARNING: Stack unwind information not available. Following frames may be
> wrong.
> 8eb0fbf8 82065782 8eb0fc44 8193578e 00000000
> hal!HalGetInterruptTargetInformation+0x608
> 8eb0fc00 8193578e 00000000 81936ef9 844b8d78
> hal!HalGetInterruptTargetInformation+0x9ea
> 8eb0fc44 81959bd8 90743520 8eb0fd44 00000000 nt!WmiTraceMessageVa+0x61a
> 8eb0fcac 8183c108 906473b8 00000000 00f0f4ec nt!KiDispatchInterrupt+0x2e8
> 8eb0fd08 81ed0441 8eb0f901 00000000 8eb0fd2c
> nt!KeDelayExecutionThread+0x42e
> 8eb0fd54 81954e83 00000000 00f0f508 00f0f518 nt!ProbeForRead+0x89d1
> 8eb0fd64 76a13ea4 badb0d00 00f0f4e4 00000000
> nt!KeReleaseInStackQueuedSpinLockFromDpcLevel+0xc47
> 8eb0fd68 badb0d00 00f0f4e4 00000000 00000000 ntdll!KiFastSystemCallRet
> 8eb0fd6c 00f0f4e4 00000000 00000000 00000000 0xbadb0d00
> 8eb0fd70 00000000 00000000 00000000 00000000 0xf0f4e4
>
>
> STACK_COMMAND: kb
>
> FOLLOWUP_IP:
> nt!WmiTraceMessageVa+61a
> 8193578e c3 ret
>
> SYMBOL_STACK_INDEX: 2
> SYMBOL_NAME: nt!WmiTraceMessageVa+61a
> FOLLOWUP_NAME: MachineOwner
> IMAGE_NAME: ntkrpamp.exe
> BUCKET_ID: WRONG_SYMBOLS
>
> Followup: MachineOwner
> ---------
>
>
> Best Regards,
> Allen
>

Ken_Johnson · July 9, 2010, 3:37pm

Hitting F10 during startup and typing in the usual /DEBUG /DEBUGPORT=… parameters should work for modern setup.

S

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of M. M. O’Brien
Sent: Friday, July 09, 2010 10:15 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] BSOD when boot from Check Build Vista

And unfortunately windbg won’t help you here either, unless you can figure
out how to debug setup, which used to be documented, but no longer is.

mm

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Tim Roberts
Sent: Friday, July 09, 2010 1:10 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] BSOD when boot from Check Build Vista

xxxxx@sina.com wrote:

Another details, The different user name must be choose after BSOD in
“Chose a user and picture” of “Set Up Windows”, That is to say, the user
account is added, Why do I have to enter a new account?

This is entirely the wrong forum for this question. If the machine crashes
before it completed setting up User #1, it might think that you haven’t set
up any users at all.

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

mm1 · July 9, 2010, 4:24pm

I did not know that. Good to know.

Thanks,

mm

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Skywing
Sent: Friday, July 09, 2010 3:37 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] BSOD when boot from Check Build Vista

Hitting F10 during startup and typing in the usual /DEBUG /DEBUGPORT=…
parameters should work for modern setup.

S

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of M. M. O’Brien
Sent: Friday, July 09, 2010 10:15 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] BSOD when boot from Check Build Vista

And unfortunately windbg won’t help you here either, unless you can figure
out how to debug setup, which used to be documented, but no longer is.

mm

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Tim Roberts
Sent: Friday, July 09, 2010 1:10 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] BSOD when boot from Check Build Vista

xxxxx@sina.com wrote:

Another details, The different user name must be choose after BSOD in
“Chose a user and picture” of “Set Up Windows”, That is to say, the user
account is added, Why do I have to enter a new account?

This is entirely the wrong forum for this question. If the machine crashes
before it completed setting up User #1, it might think that you haven’t set
up any users at all.

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

Ken_Johnson · July 9, 2010, 5:19pm

That will work for normal boots as well, btw. Handy to temporarily flip on 1394 kd or the like for just one boot.

S

-----Original Message-----
From: M. M. O’Brien
Sent: Friday, July 09, 2010 13:24
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] BSOD when boot from Check Build Vista

I did not know that. Good to know.

Thanks,

mm

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Skywing
Sent: Friday, July 09, 2010 3:37 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] BSOD when boot from Check Build Vista

Hitting F10 during startup and typing in the usual /DEBUG /DEBUGPORT=…
parameters should work for modern setup.

- S

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of M. M. O’Brien
Sent: Friday, July 09, 2010 10:15 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] BSOD when boot from Check Build Vista

And unfortunately windbg won’t help you here either, unless you can figure
out how to debug setup, which used to be documented, but no longer is.

mm

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Tim Roberts
Sent: Friday, July 09, 2010 1:10 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] BSOD when boot from Check Build Vista

xxxxx@sina.com wrote:
> Another details, The different user name must be choose after BSOD in
“Chose a user and picture” of “Set Up Windows”, That is to say, the user
account is added, Why do I have to enter a new account?

This is entirely the wrong forum for this question. If the machine crashes
before it completed setting up User #1, it might think that you haven’t set
up any users at all.

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

—
NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

—
NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

—
NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

—
NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

mm1 · July 9, 2010, 5:21pm

So it’s basically enabling /optionsedit?

mm

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Skywing
Sent: Friday, July 09, 2010 5:19 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] BSOD when boot from Check Build Vista

That will work for normal boots as well, btw. Handy to temporarily flip on
1394 kd or the like for just one boot.

S

-----Original Message-----
From: M. M. O’Brien
Sent: Friday, July 09, 2010 13:24
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] BSOD when boot from Check Build Vista

I did not know that. Good to know.

Thanks,

mm

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Skywing
Sent: Friday, July 09, 2010 3:37 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] BSOD when boot from Check Build Vista

Hitting F10 during startup and typing in the usual /DEBUG /DEBUGPORT=…
parameters should work for modern setup.

- S

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of M. M. O’Brien
Sent: Friday, July 09, 2010 10:15 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] BSOD when boot from Check Build Vista

And unfortunately windbg won’t help you here either, unless you can figure
out how to debug setup, which used to be documented, but no longer is.

mm

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Tim Roberts
Sent: Friday, July 09, 2010 1:10 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] BSOD when boot from Check Build Vista

xxxxx@sina.com wrote:
> Another details, The different user name must be choose after BSOD in
“Chose a user and picture” of “Set Up Windows”, That is to say, the user
account is added, Why do I have to enter a new account?

This is entirely the wrong forum for this question. If the machine crashes
before it completed setting up User #1, it might think that you haven’t set
up any users at all.

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

—
NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

—
NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

—
NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

—
NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

—
NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

allen_zhang · July 9, 2010, 8:09pm

Scott Noone, Ken Johnson and mm
Thanks a lot,

It can be connected when I press F8 quickly, And I download the symbols by “SRV*F:\localsymbols *http://msdl.microsoft.com/download/symbols”,
The follow lines is the information about the BSOD,

Debugging Details:

PROCESS_NAME: svchost.exe

FAULTING_IP:
hal!HalpGenerateConsistentPmTimerRead+46
820653a0 cd2c int 2Ch

EXCEPTION_RECORD: ffffffff – (.exr 0xffffffffffffffff)
ExceptionAddress: 820653a0 (hal!HalpGenerateConsistentPmTimerRead+0x00000046)
ExceptionCode: c0000420 (Assertion failure)
ExceptionFlags: 00000000
NumberParameters: 0

ERROR_CODE: (NTSTATUS) 0xc0000420 -

EXCEPTION_CODE: (NTSTATUS) 0xc0000420 -

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x0

CURRENT_IRQL: 1b

LAST_CONTROL_TRANSFER: from 820655c2 to 820653a0

STACK_TEXT:
8eb0fbac 820655c2 844b8d78 8402cd08 00000002 hal!HalpGenerateConsistentPmTimerRead+0x46
8eb0fbf8 82065782 8eb0fc44 8193578e 00000000 hal!HalpQueryBrokenPmTimerCount+0x42
8eb0fc00 8193578e 00000000 81936ef9 844b8d78 hal!HalpBrokenPmTimerQueryPerformanceCounter+0x22
8eb0fc08 81936ef9 844b8d78 906473b8 81981a00 nt!EtwpGetPerfCounter+0x8
8eb0fc44 81959bd8 90743520 8eb0fd44 00000000 nt!EtwTraceContextSwap+0x13f
8eb0fc54 819598a6 8eb0fcac 906473b8 844b8d78 nt!SwapContext_PatchFxe+0x30
8eb0fc68 818441b5 90647440 906473b8 81981b20 nt!KiSwapContext+0x26
8eb0fcac 8183c108 906473b8 00000000 00f0f4ec nt!KiSwapThread+0x50f
8eb0fd08 81ed0441 8eb0f901 00000000 8eb0fd2c nt!KeDelayExecutionThread+0x42e
8eb0fd54 81954e83 00000000 00f0f508 00f0f518 nt!NtDelayExecution+0x8d
8eb0fd54 76a13ea4 00000000 00f0f508 00f0f518 nt!KiFastCallEntry+0x163
00f0f4d8 769ef0c4 740c5c2b 00000000 00f0f508 ntdll!KiFastSystemCallRet
00f0f4dc 740c5c2b 00000000 00f0f508 740ce6e4 ntdll!ZwDelayExecution+0xc
00f0f518 740c6023 00000000 00f0f570 000000c0 mmcss!CiSchedulerWait+0x84
00f0f55c 76a13d6d 00000000 00000000 00000000 mmcss!CiSchedulerApc+0x2af
00f0f8ac 740c33cd 76d6ee1f 008c4442 00000001 ntdll!KiUserApcDispatcher+0x25
00f0f8b4 008c4442 00000001 002842d4 00000000 mmcss!CsServiceMain+0x4a
00f0f8f0 7693a7d0 00000001 002842d4 00000000 svchost!ServiceStarter+0x239
00f0f904 76d6436e 002842c8 00f0f950 76a197bf ADVAPI32!ScSvcctrlThreadA+0x21
00f0f910 76a197bf 002842c8 00f0aac5 00000000 kernel32!BaseThreadInitThunk+0xe
00f0f950 00000000 7693a7af 002842c8 00000000 ntdll!_RtlUserThreadStart+0x23

STACK_COMMAND: kb

FOLLOWUP_IP:
nt!EtwpGetPerfCounter+8
8193578e c3 ret

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!EtwpGetPerfCounter+8

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4549ac73

FAILURE_BUCKET_ID: 0x0_nt!EtwpGetPerfCounter+8

BUCKET_ID: 0x0_nt!EtwpGetPerfCounter+8

Followup: MachineOwner
---------

B.R.
Allen