re: bsod on restart, BCCodes
Wednesday, May 28, 2008 at 10:05 am
Windows Vista Annoyances Discussion Forum
Posted by jane chandler
(3 messages posted)
Okay, so I downloaded the debugger from Microsoft and opened the .dmp file in it.
Here is what it says -
Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\Mini052808-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 argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows Server 2008 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x8263e000 PsLoadedModuleList = 0x82755c70
Debug session time: Wed May 28 09:15:00.931 2008 (GMT-7)
System Uptime: 0 days 0:00:13.759
*********************************************************************
* 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 argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
........................................................................................................................................
Loading User Symbols
Unable to load image \SystemRoot\system32\drivers\Sidney.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Sidney.sys
*** ERROR: Module load completed but symbols could not be loaded for Sidney.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {807e0b02, 2, 8, 807e0b02}
*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
*** WARNING: Unable to verify timestamp for partmgr.sys
*** ERROR: Module load completed but symbols could not be loaded for partmgr.sys
*** WARNING: Unable to verify timestamp for volmgr.sys
*** ERROR: Module load completed but symbols could not be loaded for volmgr.sys
*** WARNING: Unable to verify timestamp for fvevol.sys
*** ERROR: Module load completed but symbols could not be loaded for fvevol.sys
*** WARNING: Unable to verify timestamp for ecache.sys
*** ERROR: Module load completed but symbols could not be loaded for ecache.sys
*** WARNING: Unable to verify timestamp for CLASSPNP.SYS
*** ERROR: Module load completed but symbols could not be loaded for CLASSPNP.SYS
*** WARNING: Unable to verify timestamp for ataport.SYS
*** ERROR: Module load completed but symbols could not be loaded for ataport.SYS
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
***** 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 ***
*** ***
*************************************************************************
*********************************************************************
* 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 argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* 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 argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Probably caused by : Sidney.sys ( Sidney+11b02 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 807e0b02, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000008, value 0 = read operation, 1 = write operation
Arg4: 807e0b02, address which referenced memory
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 ***
*** ***
*************************************************************************
*********************************************************************
* 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 argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* 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 argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
MODULE_NAME: Sidney
FAULTING_MODULE: 8263e000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4537a33c
READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
807e0b02
CURRENT_IRQL: 2
FAULTING_IP:
Sidney+11b02
807e0b02 ?? ???
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WRONG_SYMBOLS
BUGCHECK_STR: 0xD1
LAST_CONTROL_TRANSFER: from 807e0b02 to 82698d84
FAILED_INSTRUCTION_ADDRESS:
Sidney+11b02
807e0b02 ?? ???
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
803f0bec 807e0b02 badb0d00 855d8e28 00000001 nt+0x5ad84
803f0c74 807ac116 aa669000 855d8e28 85ca96b8 Sidney+0x11b02
803f0c88 807ac151 855f3980 855d8f28 855f38c8 partmgr+0x1116
803f0c9c 826fa053 855f38c8 855d8e28 855d8e28 partmgr+0x1151
803f0cb4 805cd6f1 855d8f68 85ca9600 855d8e28 nt+0xbc053
803f0cd0 826fa053 85ca9600 855d8e28 855d8f8c volmgr+0x16f1
803f0ce8 87f8fd77 00000022 aa669000 803f0d10 nt+0xbc053
803f0cf8 87f90565 85eaf380 855d8e28 8267d1ef fvevol+0x9d77
803f0d10 87f8eb6d 85eaf380 855d8e28 87f76880 fvevol+0xa565
803f0d34 826fa053 85eaf2c8 855d8e28 87f768e0 fvevol+0x8b6d
803f0d4c 87f6a73c 855d8f73 855d8e28 00000000 nt+0xbc053
803f0df4 826780e4 00000000 00010000 870fa000 ecache+0xb73c
803f0e28 87fc0773 803f0e5c 87fc0d4d 856475f8 nt+0x3a0e4
803f0e30 87fc0d4d 856475f8 855d8e28 00000001 CLASSPNP+0x5773
803f0e5c 826780e4 00000000 862264b0 00260258 CLASSPNP+0x5d4d
803f0e94 830ac2d7 86260304 855f3278 803f0ec4 nt+0x3a0e4
803f0ea4 830accc6 855caa78 862264b0 86260304 ataport+0x52d7
803f0ec4 830a9fb2 855caa78 00000000 803f0ef4 ataport+0x5cc6
803f0ed4 830aee6f 855bd0e0 855f3278 855f3278 ataport+0x2fb2
803f0ef4 830af0a9 855bd0e0 855f3278 84ac552c ataport+0x7e6f
803f0f48 8061ba9e 855bd09c 855bd028 00000000 ataport+0x80a9
803f0f78 84ac5a0a 84ac5008 830aeffe 803f0f8c sptd+0x11a9e
803f0ff4 826f29f5 8896f8f8 00000000 00000000 0x84ac5a0a
803f0ff8 8896f8f8 00000000 00000000 00000000 nt+0xb49f5
826f29f5 00000000 00000000 00000000 00000000 0x8896f8f8
STACK_COMMAND: kb
FOLLOWUP_IP:
Sidney+11b02
807e0b02 ?? ???
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: Sidney+11b02
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: Sidney.sys
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
I will appreciate if someone could help me figure this out.
Thanks,
Jane
- Written in response to:
- bsod on restart, BCCodes (jane chandler: Wednesday, May 28, 2008 at 9:50 am)
Responses to this message:
|
|
All messages in this thread [show all]
 |  | re: bsod on restart, BCCodes (jane chandler: Wed, May 28, 2008, 10:05 am) |
| |
| |
| |
Return to the Windows Vista Discussion Forum
|
|
