This is an old post, But I am facing exactly the same problem.
Anybody on the list has any idea about this mode of windbg (it looks 16bit).
Any idea why it happens and if possible how to switch to 64bit mode?
-Deepak
On Tue, Aug 30, 2011 at 10:38 AM, wrote:
> Win7 64bit full kernel crash dump shows “16.0: kd>” as command prompt.
> I know 0 is processor number but no idea of “16”
>
> Another weird thing is “dd” command print as follows like 16bit debug.exe.
> 0000:0000 ??? ??? ??? ???
> 0000:0010 ??? ??? ??? ???
> 0000:0020 ??? ??? ??? ???
> 0000:0030 ??? ??? ??? ???
> 0000:0040 ??? ??? ??? ???
>
> Thanks for your valuable answers in advance.
>
> - Woojung — WINDBG 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
Any chance your dump file is corrupted? What does, “.dumpdebug” say?
-scott
–
Scott Noone
Consulting Associate and Chief System Problem Analyst
OSR Open Systems Resources, Inc.
http://www.osronline.com
“Deepak Gupta” wrote in message news:xxxxx@windbg…
This is an old post, But I am facing exactly the same problem.
Anybody on the list has any idea about this mode of windbg (it looks 16bit).
Any idea why it happens and if possible how to switch to 64bit mode?
-Deepak
On Tue, Aug 30, 2011 at 10:38 AM, wrote:
Win7 64bit full kernel crash dump shows “16.0: kd>” as command prompt.
I know 0 is processor number but no idea of “16”
Another weird thing is “dd” command print as follows like 16bit debug.exe.
0000:0000 ??? ??? ??? ???
0000:0010 ??? ??? ??? ???
0000:0020 ??? ??? ??? ???
0000:0030 ??? ??? ??? ???
0000:0040 ??? ??? ??? ???
Thanks for your valuable answers in advance.
- Woojung — WINDBG 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