Unable to read selector for PCR for processor 0

WINDBG
1

Hi all,

How do we proceed if we get “Unable to read selector for PCR for processor
0” error in the debugger when a dump is opened for analysis? I am getting
the above error with the following bugcheck code:

BugCheck 24, {190201, f5c338f0, f5c3372c, 80109f33}

Regards.

2

Is this with the 6.0.7 version of the debugger on
http://www.microsoft.com/ddk/debugging?

Did the debugger display this automatically when the dump loaded or did
you do something like !process?

How did you generate the dump? Is it a full memory dump? I am guessing
it is a minidump. A minidump has a very limited set of data so it
should not be surprising if every piece of memory needed by the debugger
is not present.

Do other debugger commands you need to debug the dump appear to be
dysfunctional? Even with this error I think !analyze -v is usually able
to perform a decent analysis and give you a good stack.

-----Original Message-----
From: xxxxx@hotmail.com [mailto:xxxxx@hotmail.com]
Sent: Wednesday, April 24, 2002 5:43 AM
To: Kernel Debugging Interest List
Subject: [windbg] Unable to read selector for PCR for processor 0

Hi all,

How do we proceed if we get “Unable to read selector for PCR for
processor 0” error in the debugger when a dump is opened for analysis? I
am getting the above error with the following bugcheck code:

BugCheck 24, {190201, f5c338f0, f5c3372c, 80109f33}

Regards.

You are currently subscribed to windbg as: xxxxx@microsoft.com To
unsubscribe send a blank email to %%email.unsub%%

3

Hi David,

I have Windbg version 4.0.0018.0 and I had downloaded it from the MS
website. I see the above error as soon as the dump is loaded in the
debugger and its a complete dump. I am not able to get the stack trace
from the dump.

Regards.

4

> How do we proceed if we get "Unable to read selector for PCR

for processor 0" error in the debugger when a dump is opened
for analysis?

I got this a couple of months ago when I first started using WinDbg. It
turned out that my symbols were not set up correctly.

Make sure that you have properly set up the debug symbols for the version of
Windows that you are trying to debug, and that the path to those symbols is
set up in WinDbg (see !sympath) BEFORE you try to open the crash dump. Once
these two items are in place, you should not get the above error anymore.

Good luck!

Stu Bell