Vista - BSoD at Windows Vista during shutdown/restart! PLEASE HELP!

Hi to all.

I have Windows Vista Ultimate in my second boot, in the first boot I
have XP SP2 fully patched where is working all fantastic.
Now, I saw problems on Windows Vista Ultimate when I am going to turn
off my PC or restart my PC, then suddenly shows randomly BSoD during
(ONLY at) shutdown/restart, not in every time when I am doing
restart/shutdown but in the randomly times! I don't know what this
cause, because XP Pro SP2 doesn't have these symptoms! I downloaded
debuging software and I installed it on my Windows Vista and here's
complete log:

Microsoft (R) Windows Debugger Version 6.7.0005.1
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Download Sector\Vista minidump
files\Mini072307-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for
ntoskrnl.exe
Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x81800000 PsLoadedModuleList = 0x81908ab0
Debug session time: Mon Jul 23 00:36:07.715 2007 (GMT+2)
System Uptime: 0 days 8:22:19.405
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for
ntoskrnl.exe
Loading Kernel Symbols
..................................................................................................................................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffd09008, 0, 81bb658d, 0}

*** WARNING: Unable to verify timestamp for hal.dll
*** ERROR: Module load completed but symbols could not be loaded for hal.dll
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : ntoskrnl.exe ( nt+57535 )

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

1: kd> !analyze -v
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by
try-except,
it must be protected by a Probe. Typically the address is just plain
bad or it
is pointing at freed memory.
Arguments:
Arg1: ffd09008, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 81bb658d, If non-zero, the instruction address which referenced
the bad memory
address.
Arg4: 00000000, (reserved)

Debugging Details:
------------------

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************

MODULE_NAME: nt

FAULTING_MODULE: 81800000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4549ad6c

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
ffd09008

FAULTING_IP:
hal+2158d
81bb658d ?? ???

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

BUGCHECK_STR: 0x50

LAST_CONTROL_TRANSFER: from 81849304 to 81857535

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be
wrong.
8a6fa980 81849304 00000000 ffd09008 00000000 nt+0x57535
8a6fa998 81bb658d badb0d00 7979c7bc 00000001 nt+0x49304
8a6faa24 81ba034d 8a6faa5c 81825dd7 00000000 hal+0x2158d
8a6faa2c 81825dd7 00000000 00000003 00000000 hal+0xb34d
8a6faa5c 81a6867c 00253078 00000003 00000000 nt+0x25dd7
8a6fab90 818461fa 00000006 00000004 c0000004 nt+0x26867c
8a6faba4 818450b9 badb0d00 8a6fac1c 00000000 nt+0x461fa
8a6fad44 81a8d6ff 00000006 00000004 c0000004 nt+0x450b9
8a6fad58 818461fa 00000002 0012f798 77760f34 nt+0x28d6ff
8a6fad64 77760f34 badb0d00 0012f780 00000000 nt+0x461fa
8a6fad68 badb0d00 0012f780 00000000 00000000 0x77760f34
8a6fad6c 0012f780 00000000 00000000 00000000 0xbadb0d00
8a6fad70 00000000 00000000 00000000 00000000 0x12f780


STACK_COMMAND: kb

FOLLOWUP_IP:
nt+57535
81857535 837c242000 cmp dword ptr [esp+20h],0

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ntoskrnl.exe

SYMBOL_NAME: nt+57535

BUCKET_ID: WRONG_SYMBOLS

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


As I see this is a critical Windows process (ntoskrnl.exe) which is
known for boot Windows Vista, because I am having about 12+ years
expirience on Windows OSes (NT/Win9x/MS-DOS) and I am very worried about
this conflict. What this causing in my windows vista ultimate? Probably
some badly driver?
I ran memtest/chkdisk (on both partitions) and it all passed okay. So I
am 100% sure that THIS ISN'T problem of hardware, because my PC is well
working okay and in the first-boot XP SP2 is working fantastic without
any BSODs and similiar things!
So, thanks many on any respond on this my problem in the advance!
Cheers from Croatia.

P.S My appologize for this such a long post here and sorry if I am on
not at good place for putting my problem/post here on Windows Vista.

"g33k" wrote:

> Hi to all.
>
> I have Windows Vista Ultimate in my second boot, in the first boot I
> have XP SP2 fully patched where is working all fantastic.
> Now, I saw problems on Windows Vista Ultimate when I am going to turn
> off my PC or restart my PC, then suddenly shows randomly BSoD during
> (ONLY at) shutdown/restart, not in every time when I am doing
> restart/shutdown but in the randomly times! I don't know what this
> cause, because XP Pro SP2 doesn't have these symptoms! I downloaded
> debuging software and I installed it on my Windows Vista and here's
> complete log:
>
> Microsoft (R) Windows Debugger Version 6.7.0005.1
> Copyright (c) Microsoft Corporation. All rights reserved.
>
>
> Loading Dump File [C:\Download Sector\Vista minidump
> files\Mini072307-01.dmp]
> Mini Kernel Dump File: Only registers and stack trace are available
>
> Symbol search path is: *** Invalid ***
> ****************************************************************************
> * Symbol loading may be unreliable without a symbol search path. *
> * Use .symfix to have the debugger choose a symbol path. *
> * After setting your symbol path, use .reload to refresh symbol locations. *
> ****************************************************************************
> Executable search path is:
> *********************************************************************
> * Symbols can not be loaded because symbol path is not initialized. *
> * *
> * The Symbol Path can be set by: *
> * using the _NT_SYMBOL_PATH environment variable. *
> * using the -y <symbol_path> argument when starting the debugger. *
> * using .sympath and .sympath+ *
> *********************************************************************
> Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
> *** WARNING: Unable to verify timestamp for ntoskrnl.exe
> *** ERROR: Module load completed but symbols could not be loaded for
> ntoskrnl.exe
> Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
> Product: WinNt, suite: TerminalServer SingleUserTS
> Kernel base = 0x81800000 PsLoadedModuleList = 0x81908ab0
> Debug session time: Mon Jul 23 00:36:07.715 2007 (GMT+2)
> System Uptime: 0 days 8:22:19.405
> *********************************************************************
> * Symbols can not be loaded because symbol path is not initialized. *
> * *
> * The Symbol Path can be set by: *
> * using the _NT_SYMBOL_PATH environment variable. *
> * using the -y <symbol_path> argument when starting the debugger. *
> * using .sympath and .sympath+ *
> *********************************************************************
> Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
> *** WARNING: Unable to verify timestamp for ntoskrnl.exe
> *** ERROR: Module load completed but symbols could not be loaded for
> ntoskrnl.exe
> Loading Kernel Symbols
> ..................................................................................................................................................
> Loading User Symbols
> Loading unloaded module list
> ........
> *******************************************************************************
> *
> *
> * Bugcheck Analysis
> *
> *
> *
> *******************************************************************************
>
> Use !analyze -v to get detailed debugging information.
>
> BugCheck 50, {ffd09008, 0, 81bb658d, 0}
>
> *** WARNING: Unable to verify timestamp for hal.dll
> *** ERROR: Module load completed but symbols could not be loaded for hal.dll
> ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
>
> *************************************************************************
> *** ***
> *** ***
> *** Your debugger is not using the correct symbols ***
> *** ***
> *** In order for this command to work properly, your symbol path ***
> *** must point to .pdb files that have full type information. ***
> *** ***
> *** Certain .pdb files (such as the public OS symbols) do not ***
> *** contain the required information. Contact the group that ***
> *** provided you with these symbols if you need this command to ***
> *** work. ***
> *** ***
> *** Type referenced: nt!_KPRCB ***
> *** ***
> *************************************************************************
> *************************************************************************
> *** ***
> *** ***
> *** Your debugger is not using the correct symbols ***
> *** ***
> *** In order for this command to work properly, your symbol path ***
> *** must point to .pdb files that have full type information. ***
> *** ***
> *** Certain .pdb files (such as the public OS symbols) do not ***
> *** contain the required information. Contact the group that ***
> *** provided you with these symbols if you need this command to ***
> *** work. ***
> *** ***
> *** Type referenced: nt!KPRCB ***
> *** ***
> *************************************************************************
> *************************************************************************
> *** ***
> *** ***
> *** Your debugger is not using the correct symbols ***
> *** ***
> *** In order for this command to work properly, your symbol path ***
> *** must point to .pdb files that have full type information. ***
> *** ***
> *** Certain .pdb files (such as the public OS symbols) do not ***
> *** contain the required information. Contact the group that ***
> *** provided you with these symbols if you need this command to ***
> *** work. ***
> *** ***
> *** Type referenced: nt!_KPRCB ***
> *** ***
> *************************************************************************
> *************************************************************************
> *** ***
> *** ***
> *** Your debugger is not using the correct symbols ***
> *** ***
> *** In order for this command to work properly, your symbol path ***
> *** must point to .pdb files that have full type information. ***
> *** ***
> *** Certain .pdb files (such as the public OS symbols) do not ***
> *** contain the required information. Contact the group that ***
> *** provided you with these symbols if you need this command to ***
> *** work. ***
> *** ***
> *** Type referenced: nt!KPRCB ***
> *** ***
> *************************************************************************
> *************************************************************************
> *** ***
> *** ***
> *** Your debugger is not using the correct symbols ***
> *** ***
> *** In order for this command to work properly, your symbol path ***
> *** must point to .pdb files that have full type information. ***
> *** ***
> *** Certain .pdb files (such as the public OS symbols) do not ***
> *** contain the required information. Contact the group that ***
> *** provided you with these symbols if you need this command to ***
> *** work. ***
> *** ***
> *** Type referenced: nt!_KPRCB ***
> *** ***
> *************************************************************************
> *************************************************************************
> *** ***
> *** ***
> *** Your debugger is not using the correct symbols ***
> *** ***
> *** In order for this command to work properly, your symbol path ***
> *** must point to .pdb files that have full type information. ***
> *** ***
> *** Certain .pdb files (such as the public OS symbols) do not ***
> *** contain the required information. Contact the group that ***
> *** provided you with these symbols if you need this command to ***
> *** work. ***
> *** ***
> *** Type referenced: nt!_KPRCB ***
> *** ***
> *************************************************************************
> Probably caused by : ntoskrnl.exe ( nt+57535 )
>
> Followup: MachineOwner
> ---------
>
> 1: kd> !analyze -v
> *******************************************************************************
> *
> *
> * Bugcheck Analysis
> *
> *
> *
> *******************************************************************************
>
> PAGE_FAULT_IN_NONPAGED_AREA (50)
> Invalid system memory was referenced. This cannot be protected by
> try-except,
> it must be protected by a Probe. Typically the address is just plain
> bad or it
> is pointing at freed memory.
> Arguments:
> Arg1: ffd09008, memory referenced.
> Arg2: 00000000, value 0 = read operation, 1 = write operation.
> Arg3: 81bb658d, If non-zero, the instruction address which referenced
> the bad memory
> address.
> Arg4: 00000000, (reserved)
>
> Debugging Details:
> ------------------
>
> ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
>
> *************************************************************************
> *** ***
> *** ***
> *** Your debugger is not using the correct symbols ***
> *** ***
> *** In order for this command to work properly, your symbol path ***
> *** must point to .pdb files that have full type information. ***
> *** ***
> *** Certain .pdb files (such as the public OS symbols) do not ***
> *** contain the required information. Contact the group that ***
> *** provided you with these symbols if you need this command to ***
> *** work. ***
> *** ***
> *** Type referenced: nt!_KPRCB ***
> *** ***
> *************************************************************************
> *************************************************************************
> *** ***
> *** ***
> *** Your debugger is not using the correct symbols ***
> *** ***
> *** In order for this command to work properly, your symbol path ***
> *** must point to .pdb files that have full type information. ***
> *** ***
> *** Certain .pdb files (such as the public OS symbols) do not ***
> *** contain the required information. Contact the group that ***
> *** provided you with these symbols if you need this command to ***
> *** work. ***
> *** ***
> *** Type referenced: nt!KPRCB ***
> *** ***
> *************************************************************************
> *************************************************************************
> *** ***
> *** ***
> *** Your debugger is not using the correct symbols ***
> *** ***
> *** In order for this command to work properly, your symbol path ***
> *** must point to .pdb files that have full type information. ***
> *** ***
> *** Certain .pdb files (such as the public OS symbols) do not ***
> *** contain the required information. Contact the group that ***
> *** provided you with these symbols if you need this command to ***
> *** work. ***
> *** ***
> *** Type referenced: nt!_KPRCB ***
> *** ***
> *************************************************************************
> *************************************************************************
> *** ***
> *** ***
> *** Your debugger is not using the correct symbols ***
> *** ***
> *** In order for this command to work properly, your symbol path ***
> *** must point to .pdb files that have full type information. ***
> *** ***
> *** Certain .pdb files (such as the public OS symbols) do not ***
> *** contain the required information. Contact the group that ***
> *** provided you with these symbols if you need this command to ***
> *** work. ***
> *** ***
> *** Type referenced: nt!KPRCB ***
> *** ***
> *************************************************************************
> *************************************************************************
> *** ***
> *** ***
> *** Your debugger is not using the correct symbols ***
> *** ***
> *** In order for this command to work properly, your symbol path ***
> *** must point to .pdb files that have full type information. ***
> *** ***
> *** Certain .pdb files (such as the public OS symbols) do not ***
> *** contain the required information. Contact the group that ***
> *** provided you with these symbols if you need this command to ***
> *** work. ***
> *** ***
> *** Type referenced: nt!_KPRCB ***
> *** ***
> *************************************************************************
> *************************************************************************
> *** ***
> *** ***
> *** Your debugger is not using the correct symbols ***
> *** ***
> *** In order for this command to work properly, your symbol path ***
> *** must point to .pdb files that have full type information. ***
> *** ***
> *** Certain .pdb files (such as the public OS symbols) do not ***
> *** contain the required information. Contact the group that ***
> *** provided you with these symbols if you need this command to ***
> *** work. ***

Sounds a lot like this:
http://blog.tiensivu.com/aaron/archi...KB-939720.html

http://support.microsoft.com/kb/939720

I would request the hotfix here:
http://support.microsoft.com/contact...1410&WS=hotfix

---
http://blog.tiensivu.com/aaron
http://mvp.support.microsoft.com/profile/Aaron.Tiensivu

"g33k" wrote:

> Hi to all.
>
> I have Windows Vista Ultimate in my second boot, in the first boot I
> have XP SP2 fully patched where is working all fantastic.
> Now, I saw problems on Windows Vista Ultimate when I am going to turn
> off my PC or restart my PC, then suddenly shows randomly BSoD during
> (ONLY at) shutdown/restart, not in every time when I am doing
> restart/shutdown but in the randomly times! I don't know what this
> cause, because XP Pro SP2 doesn't have these symptoms! I downloaded
> debuging software and I installed it on my Windows Vista and here's
> complete log:
>
> Microsoft (R) Windows Debugger Version 6.7.0005.1
> Copyright (c) Microsoft Corporation. All rights reserved.
>
>
> Loading Dump File [C:\Download Sector\Vista minidump
> files\Mini072307-01.dmp]
> Mini Kernel Dump File: Only registers and stack trace are available
>
> Symbol search path is: *** Invalid ***
> ****************************************************************************
> * Symbol loading may be unreliable without a symbol search path. *
> * Use .symfix to have the debugger choose a symbol path. *
> * After setting your symbol path, use .reload to refresh symbol locations. *
> ****************************************************************************
> Executable search path is:
> *********************************************************************
> * Symbols can not be loaded because symbol path is not initialized. *
> * *
> * The Symbol Path can be set by: *
> * using the _NT_SYMBOL_PATH environment variable. *
> * using the -y <symbol_path> argument when starting the debugger. *
> * using .sympath and .sympath+ *
> *********************************************************************
> Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
> *** WARNING: Unable to verify timestamp for ntoskrnl.exe
> *** ERROR: Module load completed but symbols could not be loaded for
> ntoskrnl.exe
> Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
> Product: WinNt, suite: TerminalServer SingleUserTS
> Kernel base = 0x81800000 PsLoadedModuleList = 0x81908ab0
> Debug session time: Mon Jul 23 00:36:07.715 2007 (GMT+2)
> System Uptime: 0 days 8:22:19.405
> *********************************************************************
> * Symbols can not be loaded because symbol path is not initialized. *
> * *
> * The Symbol Path can be set by: *
> * using the _NT_SYMBOL_PATH environment variable. *
> * using the -y <symbol_path> argument when starting the debugger. *
> * using .sympath and .sympath+ *
> *********************************************************************
> Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
> *** WARNING: Unable to verify timestamp for ntoskrnl.exe
> *** ERROR: Module load completed but symbols could not be loaded for
> ntoskrnl.exe
> Loading Kernel Symbols
> ..................................................................................................................................................
> Loading User Symbols
> Loading unloaded module list
> ........
> *******************************************************************************
> *
> *
> * Bugcheck Analysis
> *
> *
> *
> *******************************************************************************
>
> Use !analyze -v to get detailed debugging information.
>
> BugCheck 50, {ffd09008, 0, 81bb658d, 0}
>
> *** WARNING: Unable to verify timestamp for hal.dll
> *** ERROR: Module load completed but symbols could not be loaded for hal.dll
> ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
>
> *************************************************************************
> *** ***
> *** ***
> *** Your debugger is not using the correct symbols ***
> *** ***
> *** In order for this command to work properly, your symbol path ***
> *** must point to .pdb files that have full type information. ***
> *** ***
> *** Certain .pdb files (such as the public OS symbols) do not ***
> *** contain the required information. Contact the group that ***
> *** provided you with these symbols if you need this command to ***
> *** work. ***
> *** ***
> *** Type referenced: nt!_KPRCB ***
> *** ***
> *************************************************************************
> *************************************************************************
> *** ***
> *** ***
> *** Your debugger is not using the correct symbols ***
> *** ***
> *** In order for this command to work properly, your symbol path ***
> *** must point to .pdb files that have full type information. ***
> *** ***
> *** Certain .pdb files (such as the public OS symbols) do not ***
> *** contain the required information. Contact the group that ***
> *** provided you with these symbols if you need this command to ***
> *** work. ***
> *** ***
> *** Type referenced: nt!KPRCB ***
> *** ***
> *************************************************************************
> *************************************************************************
> *** ***
> *** ***
> *** Your debugger is not using the correct symbols ***
> *** ***
> *** In order for this command to work properly, your symbol path ***
> *** must point to .pdb files that have full type information. ***
> *** ***
> *** Certain .pdb files (such as the public OS symbols) do not ***
> *** contain the required information. Contact the group that ***
> *** provided you with these symbols if you need this command to ***
> *** work. ***
> *** ***
> *** Type referenced: nt!_KPRCB ***
> *** ***
> *************************************************************************
> *************************************************************************
> *** ***
> *** ***
> *** Your debugger is not using the correct symbols ***
> *** ***
> *** In order for this command to work properly, your symbol path ***
> *** must point to .pdb files that have full type information. ***
> *** ***
> *** Certain .pdb files (such as the public OS symbols) do not ***
> *** contain the required information. Contact the group that ***
> *** provided you with these symbols if you need this command to ***
> *** work. ***
> *** ***
> *** Type referenced: nt!KPRCB ***
> *** ***
> *************************************************************************
> *************************************************************************
> *** ***
> *** ***
> *** Your debugger is not using the correct symbols ***
> *** ***
> *** In order for this command to work properly, your symbol path ***
> *** must point to .pdb files that have full type information. ***
> *** ***
> *** Certain .pdb files (such as the public OS symbols) do not ***
> *** contain the required information. Contact the group that ***
> *** provided you with these symbols if you need this command to ***
> *** work. ***
> *** ***
> *** Type referenced: nt!_KPRCB ***
> *** ***
> *************************************************************************
> *************************************************************************
> *** ***
> *** ***
> *** Your debugger is not using the correct symbols ***
> *** ***
> *** In order for this command to work properly, your symbol path ***
> *** must point to .pdb files that have full type information. ***
> *** ***
> *** Certain .pdb files (such as the public OS symbols) do not ***
> *** contain the required information. Contact the group that ***
> *** provided you with these symbols if you need this command to ***
> *** work. ***
> *** ***
> *** Type referenced: nt!_KPRCB ***
> *** ***
> *************************************************************************
> Probably caused by : ntoskrnl.exe ( nt+57535 )
>
> Followup: MachineOwner
> ---------
>
> 1: kd> !analyze -v
> *******************************************************************************
> *
> *
> * Bugcheck Analysis
> *
> *
> *
> *******************************************************************************
>
> PAGE_FAULT_IN_NONPAGED_AREA (50)
> Invalid system memory was referenced. This cannot be protected by
> try-except,
> it must be protected by a Probe. Typically the address is just plain
> bad or it
> is pointing at freed memory.
> Arguments:
> Arg1: ffd09008, memory referenced.
> Arg2: 00000000, value 0 = read operation, 1 = write operation.
> Arg3: 81bb658d, If non-zero, the instruction address which referenced
> the bad memory
> address.
> Arg4: 00000000, (reserved)
>
> Debugging Details:
> ------------------
>
> ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
>
> *************************************************************************
> *** ***
> *** ***
> *** Your debugger is not using the correct symbols ***
> *** ***
> *** In order for this command to work properly, your symbol path ***
> *** must point to .pdb files that have full type information. ***
> *** ***
> *** Certain .pdb files (such as the public OS symbols) do not ***
> *** contain the required information. Contact the group that ***
> *** provided you with these symbols if you need this command to ***
> *** work. ***
> *** ***
> *** Type referenced: nt!_KPRCB ***
> *** ***
> *************************************************************************
> *************************************************************************
> *** ***
> *** ***
> *** Your debugger is not using the correct symbols ***
> *** ***
> *** In order for this command to work properly, your symbol path ***
> *** must point to .pdb files that have full type information. ***
> *** ***
> *** Certain .pdb files (such as the public OS symbols) do not ***
> *** contain the required information. Contact the group that ***
> *** provided you with these symbols if you need this command to ***
> *** work. ***
> *** ***
> *** Type referenced: nt!KPRCB ***
> *** ***
> *************************************************************************
> *************************************************************************
> *** ***
> *** ***
> *** Your debugger is not using the correct symbols ***
> *** ***
> *** In order for this command to work properly, your symbol path ***
> *** must point to .pdb files that have full type information. ***
> *** ***
> *** Certain .pdb files (such as the public OS symbols) do not ***
> *** contain the required information. Contact the group that ***
> *** provided you with these symbols if you need this command to ***
> *** work. ***
> *** ***
> *** Type referenced: nt!_KPRCB ***
> *** ***
> *************************************************************************
> *************************************************************************
> *** ***
> *** ***
> *** Your debugger is not using the correct symbols ***
> *** ***
> *** In order for this command to work properly, your symbol path ***
> *** must point to .pdb files that have full type information. ***
> *** ***
> *** Certain .pdb files (such as the public OS symbols) do not ***
> *** contain the required information. Contact the group that ***
> *** provided you with these symbols if you need this command to ***
> *** work. ***
> *** ***
> *** Type referenced: nt!KPRCB ***
> *** ***
> *************************************************************************
> *************************************************************************
> *** ***
> *** ***
> *** Your debugger is not using the correct symbols ***
> *** ***
> *** In order for this command to work properly, your symbol path ***
> *** must point to .pdb files that have full type information. ***
> *** ***
> *** Certain .pdb files (such as the public OS symbols) do not ***
> *** contain the required information. Contact the group that ***
> *** provided you with these symbols if you need this command to ***
> *** work. ***
> *** ***
> *** Type referenced: nt!_KPRCB ***
> *** ***
> *************************************************************************
> *************************************************************************
> *** ***
> *** ***
> *** Your debugger is not using the correct symbols ***
> *** ***
> *** In order for this command to work properly, your symbol path ***
> *** must point to .pdb files that have full type information. ***
> *** ***
> *** Certain .pdb files (such as the public OS symbols) do not ***
> *** contain the required information. Contact the group that ***
> *** provided you with these symbols if you need this command to ***
> *** work. ***

Here's a link to the STOP 0x50 error: http://aumha.org/a/stop.php#0x50

Most often this is a memory error, so I'd suggest running the built-in
memory diagnostic that Vista includes in the Startup repair menu.

Also, the analysis of the dump file points to ntoskrnl.exe. This is where
the error occurred, not necessarily what caused the error. Also, the symbol
files for your analysis weren't correctly loaded, so the details of the log
could be incorrect.

- John

ATiensivu wrote:
> Sounds a lot like this:
> http://blog.tiensivu.com/aaron/archi...KB-939720.html
>
> http://support.microsoft.com/kb/939720
>
> I would request the hotfix here:
> http://support.microsoft.com/contact...1410&WS=hotfix
>
> ---
> http://blog.tiensivu.com/aaron
> http://mvp.support.microsoft.com/profile/Aaron.Tiensivu

Many thanks, I will call again here in the near future if my problem
will still present.