Xevven
Legacy Member
Heb hier pc die boot error geeft, dit is de minidump:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\Mini062409-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18226.x86fre.vistasp1_gdr.090302-1506
Machine Name:
Kernel base = 0x82243000 PsLoadedModuleList = 0x8235ac70
Debug session time: Wed Jun 24 10:20:54.205 2009 (GMT+2)
System Uptime: 0 days 0:00:27.986
Loading Kernel Symbols
...............................................................
..............................................
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9C, {0, 851b2650, f2000040, 800}
Probably caused by : kdcom.dll ( kdcom!_NULL_IMPORT_DESCRIPTOR+315 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
MACHINE_CHECK_EXCEPTION (9c)
A fatal Machine Check Exception has occurred.
KeBugCheckEx parameters;
x86 Processors
If the processor has ONLY MCE feature available (For example Intel
Pentium), the parameters are:
1 - Low 32 bits of P5_MC_TYPE MSR
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of P5_MC_ADDR MSR
4 - Low 32 bits of P5_MC_ADDR MSR
If the processor also has MCA feature available (For example Intel
Pentium Pro), the parameters are:
1 - Bank number
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error
IA64 Processors
1 - Bugcheck Type
1 - MCA_ASSERT
2 - MCA_GET_STATEINFO
SAL returned an error for SAL_GET_STATEINFO while processing MCA.
3 - MCA_CLEAR_STATEINFO
SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA.
4 - MCA_FATAL
FW reported a fatal MCA.
5 - MCA_NONFATAL
SAL reported a recoverable MCA and we don't support currently
support recovery or SAL generated an MCA and then couldn't
produce an error record.
0xB - INIT_ASSERT
0xC - INIT_GET_STATEINFO
SAL returned an error for SAL_GET_STATEINFO while processing INIT event.
0xD - INIT_CLEAR_STATEINFO
SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event.
0xE - INIT_FATAL
Not used.
2 - Address of log
3 - Size of log
4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO
AMD64 Processors
1 - Bank number
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error
Arguments:
Arg1: 00000000
Arg2: 851b2650
Arg3: f2000040
Arg4: 00000800
Debugging Details:
------------------
NOTE: This is a hardware error. This error was reported by the CPU
via Interrupt 18. This analysis will provide more information about
the specific error. Please contact the manufacturer for additional
information about this error and troubleshooting assistance.
This error is documented in the following publication:
- IA-32 Intel(r) Architecture Software Developer's Manual
Volume 3: System Programming Guide
Bit Mask:
MA Model Specific MCA
O ID Other Information Error Code Error Code
VV SDP ___________|____________ _______|_______ _______|______
AEUECRC| | | |
LRCNVVC| | | |
^^^^^^^| | | |
6 5 4 3 2 1
3210987654321098765432109876543210987654321098765432109876543210
----------------------------------------------------------------
1111001000000000000000000100000000000000000000000000100000000000
VAL - MCi_STATUS register is valid
Indicates that the information contained within the IA32_MCi_STATUS
register is valid. When this flag is set, the processor follows the
rules given for the OVER flag in the IA32_MCi_STATUS register when
overwriting previously valid entries. The processor sets the VAL
flag and software is responsible for clearing it.
OVER - Error Overflow
Indicates that a machine check error occurred while the results of a
previous error were still in the error-reporting register bank (that
is, the VAL bit was already set in the IA32_MCi_STATUS register).
the processor sets the OVER flag and software is responsible for
clearing it. Enabled errors are written over disabled errors, and
uncorrected errors are written over corrected errors. Uncorrected
errors are not written over previous valid uncorrected errors.
UC - Error Uncorrected
Indicates that the processor did not or was not able to correct the
error condition. When clear, this flag indicates that the processor
was able to correct the error condition.
EN - Error Enabled
Indicates that the error was enabled by the associated EEj bit of the
IA32_MCi_CTL register.
PCC - Processor Context Corrupt
Indicates that the state of the processor might have been corrupted
by the error condition detected and that reliable restarting of the
processor may not be possible.
BUSCONNERR - Bus and Interconnect Error BUS{LL}_{PP}_{RRRR}_{II}_{T}_err
These errors match the format 0000 1PPT RRRR IILL
Concatenated Error Code:
--------------------------
_VAL_OVER_UC_EN_PCC_BUSCONNERR_0
This error code can be reported back to the manufacturer.
They may be able to provide additional information based upon
this error. All questions regarding STOP 0x9C should be
directed to the hardware manufacturer.
BUGCHECK_STR: 0x9C_GenuineIntel
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 1f
LAST_CONTROL_TRANSFER: from 82216ec5 to 823100e3
SYMBOL_ON_RAW_STACK: 1
STACK_ADDR_RAW_STACK_SYMBOL: ffffffff803d8608
STACK_COMMAND: dds 803D8608-0x20 ; kb
STACK_TEXT:
803d85e8 0000ffff
803d85ec 00cffa00
803d85f0 0000ffff
803d85f4 00cff300
803d85f8 313020ab
803d85fc 80008b3d
803d8600 10002128
803d8604 8040933d kdcom!_NULL_IMPORT_DESCRIPTOR+0x315
803d8608 00004000
803d860c 0040f200
803d8610 0400ffff
803d8614 0000f200
803d8618 00000000
803d861c 00000000
803d8620 54700068
803d8624 8000893d
803d8628 54e00068
803d862c 8000893d
803d8630 00000000
803d8634 00000000
803d8638 00000000
803d863c 00000000
803d8640 f00003ff
803d8644 8300920d
803d8648 00000000
803d864c 00000000
803d8650 00000000
803d8654 00000000
803d8658 00000000
803d865c 00000000
803d8660 00000000
803d8664 00000000
FOLLOWUP_IP:
kdcom!_NULL_IMPORT_DESCRIPTOR+315
8040933d ?? ???
SYMBOL_NAME: kdcom!_NULL_IMPORT_DESCRIPTOR+315
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: kdcom
IMAGE_NAME: kdcom.dll
DEBUG_FLR_IMAGE_TIMESTAMP: 4791a769
FAILURE_BUCKET_ID: 0x9C_GenuineIntel_kdcom!_NULL_IMPORT_DESCRIPTOR+315
BUCKET_ID: 0x9C_GenuineIntel_kdcom!_NULL_IMPORT_DESCRIPTOR+315
Followup: MachineOwner
---------
Der is blijkbaar een driver error maar ik kan begot niet opmaken welke. Minidump zegt ook ergens hardware error en cpu maar geen idee wat ik hier nu moet uit opmaken.
Any experts? Thanks
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\Mini062409-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18226.x86fre.vistasp1_gdr.090302-1506
Machine Name:
Kernel base = 0x82243000 PsLoadedModuleList = 0x8235ac70
Debug session time: Wed Jun 24 10:20:54.205 2009 (GMT+2)
System Uptime: 0 days 0:00:27.986
Loading Kernel Symbols
...............................................................
..............................................
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9C, {0, 851b2650, f2000040, 800}
Probably caused by : kdcom.dll ( kdcom!_NULL_IMPORT_DESCRIPTOR+315 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
MACHINE_CHECK_EXCEPTION (9c)
A fatal Machine Check Exception has occurred.
KeBugCheckEx parameters;
x86 Processors
If the processor has ONLY MCE feature available (For example Intel
Pentium), the parameters are:
1 - Low 32 bits of P5_MC_TYPE MSR
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of P5_MC_ADDR MSR
4 - Low 32 bits of P5_MC_ADDR MSR
If the processor also has MCA feature available (For example Intel
Pentium Pro), the parameters are:
1 - Bank number
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error
IA64 Processors
1 - Bugcheck Type
1 - MCA_ASSERT
2 - MCA_GET_STATEINFO
SAL returned an error for SAL_GET_STATEINFO while processing MCA.
3 - MCA_CLEAR_STATEINFO
SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA.
4 - MCA_FATAL
FW reported a fatal MCA.
5 - MCA_NONFATAL
SAL reported a recoverable MCA and we don't support currently
support recovery or SAL generated an MCA and then couldn't
produce an error record.
0xB - INIT_ASSERT
0xC - INIT_GET_STATEINFO
SAL returned an error for SAL_GET_STATEINFO while processing INIT event.
0xD - INIT_CLEAR_STATEINFO
SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event.
0xE - INIT_FATAL
Not used.
2 - Address of log
3 - Size of log
4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO
AMD64 Processors
1 - Bank number
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error
Arguments:
Arg1: 00000000
Arg2: 851b2650
Arg3: f2000040
Arg4: 00000800
Debugging Details:
------------------
NOTE: This is a hardware error. This error was reported by the CPU
via Interrupt 18. This analysis will provide more information about
the specific error. Please contact the manufacturer for additional
information about this error and troubleshooting assistance.
This error is documented in the following publication:
- IA-32 Intel(r) Architecture Software Developer's Manual
Volume 3: System Programming Guide
Bit Mask:
MA Model Specific MCA
O ID Other Information Error Code Error Code
VV SDP ___________|____________ _______|_______ _______|______
AEUECRC| | | |
LRCNVVC| | | |
^^^^^^^| | | |
6 5 4 3 2 1
3210987654321098765432109876543210987654321098765432109876543210
----------------------------------------------------------------
1111001000000000000000000100000000000000000000000000100000000000
VAL - MCi_STATUS register is valid
Indicates that the information contained within the IA32_MCi_STATUS
register is valid. When this flag is set, the processor follows the
rules given for the OVER flag in the IA32_MCi_STATUS register when
overwriting previously valid entries. The processor sets the VAL
flag and software is responsible for clearing it.
OVER - Error Overflow
Indicates that a machine check error occurred while the results of a
previous error were still in the error-reporting register bank (that
is, the VAL bit was already set in the IA32_MCi_STATUS register).
the processor sets the OVER flag and software is responsible for
clearing it. Enabled errors are written over disabled errors, and
uncorrected errors are written over corrected errors. Uncorrected
errors are not written over previous valid uncorrected errors.
UC - Error Uncorrected
Indicates that the processor did not or was not able to correct the
error condition. When clear, this flag indicates that the processor
was able to correct the error condition.
EN - Error Enabled
Indicates that the error was enabled by the associated EEj bit of the
IA32_MCi_CTL register.
PCC - Processor Context Corrupt
Indicates that the state of the processor might have been corrupted
by the error condition detected and that reliable restarting of the
processor may not be possible.
BUSCONNERR - Bus and Interconnect Error BUS{LL}_{PP}_{RRRR}_{II}_{T}_err
These errors match the format 0000 1PPT RRRR IILL
Concatenated Error Code:
--------------------------
_VAL_OVER_UC_EN_PCC_BUSCONNERR_0
This error code can be reported back to the manufacturer.
They may be able to provide additional information based upon
this error. All questions regarding STOP 0x9C should be
directed to the hardware manufacturer.
BUGCHECK_STR: 0x9C_GenuineIntel
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 1f
LAST_CONTROL_TRANSFER: from 82216ec5 to 823100e3
SYMBOL_ON_RAW_STACK: 1
STACK_ADDR_RAW_STACK_SYMBOL: ffffffff803d8608
STACK_COMMAND: dds 803D8608-0x20 ; kb
STACK_TEXT:
803d85e8 0000ffff
803d85ec 00cffa00
803d85f0 0000ffff
803d85f4 00cff300
803d85f8 313020ab
803d85fc 80008b3d
803d8600 10002128
803d8604 8040933d kdcom!_NULL_IMPORT_DESCRIPTOR+0x315
803d8608 00004000
803d860c 0040f200
803d8610 0400ffff
803d8614 0000f200
803d8618 00000000
803d861c 00000000
803d8620 54700068
803d8624 8000893d
803d8628 54e00068
803d862c 8000893d
803d8630 00000000
803d8634 00000000
803d8638 00000000
803d863c 00000000
803d8640 f00003ff
803d8644 8300920d
803d8648 00000000
803d864c 00000000
803d8650 00000000
803d8654 00000000
803d8658 00000000
803d865c 00000000
803d8660 00000000
803d8664 00000000
FOLLOWUP_IP:
kdcom!_NULL_IMPORT_DESCRIPTOR+315
8040933d ?? ???
SYMBOL_NAME: kdcom!_NULL_IMPORT_DESCRIPTOR+315
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: kdcom
IMAGE_NAME: kdcom.dll
DEBUG_FLR_IMAGE_TIMESTAMP: 4791a769
FAILURE_BUCKET_ID: 0x9C_GenuineIntel_kdcom!_NULL_IMPORT_DESCRIPTOR+315
BUCKET_ID: 0x9C_GenuineIntel_kdcom!_NULL_IMPORT_DESCRIPTOR+315
Followup: MachineOwner
---------
Der is blijkbaar een driver error maar ik kan begot niet opmaken welke. Minidump zegt ook ergens hardware error en cpu maar geen idee wat ik hier nu moet uit opmaken.
Any experts? Thanks
