J
Juergen_2
Threadstarter
- Dabei seit
- 16.06.2009
- Beiträge
- 2
Hallo zusammen,
Hier erstmal mein Equipment:
AMD Athlon 64 X2 Dual Core Prozessor 5000+
Mainboard = ASRock ALIVESATA2-GLAN
http://www.asrock.com/MB/overview.asp?Model=ALiveSATA2-GLAN
GraKa = NVIDIA GeForce 7300 LE
NIC (onboard) = Realtek PCIe GBE Family Controller
Arbeitsspeicher = 8 GB RAM (4 mal 2 GB von Kingston)
Windows Vista Business 64 bit, incl. SP 2 = Hostsystem
Im Geräte-Manager gab es vor ein paar Tagen ein Problem,
habe im BIOS den Game/MIDI-Port deaktiviert und danach
kam dieser Fehler nicht mehr.
Virtual PC 2007, SP 1, Version = 6.0.192.0 = 64 bit
2 mal Windows 7 RC (je 32 Bit) = Gastsysteme (zugewiesener RAM = jeweils 1 GB)
1 mal Windows Server 2008, SP 2 (32 Bit) = Gastsystem (zugewiesener RAM = 2 GB)
Beim Arbeiten mit Windows Server 2008 unter VPC 2007 kam es zum Absturz und einem
anschließenden Bluescreen. Den dazugehörigen MiniDump kann man weiter unten ausführlch
anschauen.
Erste Meldungen:
------------- schnipp on ----------------------------------------------------------------------------------------------
DRIVER_IRQL_NOT_LESS_OR_EQUAL
*** STOP: 0x000000D1 (0x0000000000000010,0x0000000000000002,0x0000000000000001,
0XFFFFFA6000C4AB9E)
*** ndis.sys - Adress FFFFFA6000C4AB9E base at FFFFFA6000C08000,
DateStamp 49e02df3
------------- schnipp off ----------------------------------------------------------------------------------------------
Könnte dies auf Probleme mit der Netzwerkkarte hindeuten?
Es wurden ausführliche Tests bezgl. RAM unternommen: kein Befund!
Und hier der komplette DUMP:
------------- schnipp on ----------------------------------------------------------------------------------------------
t (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\Mini061509-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6002.18005.amd64fre.lh_sp2rtm.090410-1830
Machine Name:
Kernel base = 0xfffff800`01a4f000 PsLoadedModuleList = 0xfffff800`01c13dd0
Debug session time: Mon Jun 15 22:34:39.429 2009 (GMT+2)
System Uptime: 0 days 1:05:17.215
Loading Kernel Symbols
...............................................................
................................................................
..
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {10, 2, 1, fffffa6000c4ab9e}
Unable to load image \SystemRoot\system32\DRIVERS\Rtlh64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Rtlh64.sys
*** ERROR: Module load completed but symbols could not be loaded for Rtlh64.sys
Probably caused by : Rtlh64.sys ( Rtlh64+69d7 )
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: 0000000000000010, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffffa6000c4ab9e, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80001c76080
0000000000000010
CURRENT_IRQL: 2
FAULTING_IP:
ndis!ndisXlateSendCompleteNetBufferListToPacket+3e
fffffa60`00c4ab9e 48c7411036434f4d mov qword ptr [rcx+10h],4D4F4336h
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: Virtual PC.exe
TRAP_FRAME: fffffa600757c3c0 -- (.trap 0xfffffa600757c3c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa80092089b0 rbx=0000000000000000 rcx=0000000000000000
rdx=fffffa600757c5d8 rsi=0000000000000000 rdi=0000000000000000
rip=fffffa6000c4ab9e rsp=fffffa600757c550 rbp=fffffa8007669990
r8=fffffa600757c5d0 r9=fffffa80091b2610 r10=00000000000001be
r11=00000000000001be r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
ndis!ndisXlateSendCompleteNetBufferListToPacket+0x3e:
fffffa60`00c4ab9e 48c7411036434f4d mov qword ptr [rcx+10h],4D4F4336h ds:00000000`00000010=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80001aa91ee to fffff80001aa9450
STACK_TEXT:
fffffa60`0757c278 fffff800`01aa91ee : 00000000`0000000a 00000000`00000010 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffffa60`0757c280 fffff800`01aa80cb : 00000000`00000001 fffffa60`0757c4d0 00000000`00000000 fffffa80`07669990 : nt!KiBugCheckDispatch+0x6e
fffffa60`0757c3c0 fffffa60`00c4ab9e : 00000000`00000042 fffffa80`08dba050 00000000`09659740 fffff800`01a0d5df : nt!KiPageFault+0x20b
fffffa60`0757c550 fffffa60`00db111d : fffffa80`0919f170 fffffa80`070e0120 fffffa60`0757c5f0 fffffa60`0757c5a0 : ndis!ndisXlateSendCompleteNetBufferListToPacket+0x3e
fffffa60`0757c580 fffffa60`00dac492 : 00000000`00000000 fffffa80`092089b0 fffffa80`0920a010 00000000`09659740 : ndis!ndisMSendNetBufferListsCompleteToNdisPackets+0x6d
fffffa60`0757c5d0 fffffa60`00dac24c : fffffa80`08dba1a0 00000000`00000000 fffffa80`08dba1a0 fffffa80`08f7c6c0 : ndis!ndisMSendCompleteNetBufferListsInternal+0xa2
fffffa60`0757c640 fffffa60`00bb09d7 : 00000000`00000000 fffffa80`091b2610 00000000`00000000 fffffa80`091b2610 : ndis!NdisMSendNetBufferListsComplete+0x7c
fffffa60`0757c680 00000000`00000000 : fffffa80`091b2610 00000000`00000000 fffffa80`091b2610 fffffa80`0917df80 : Rtlh64+0x69d7
STACK_COMMAND: kb
FOLLOWUP_IP:
Rtlh64+69d7
fffffa60`00bb09d7 ?? ???
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: Rtlh64+69d7
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Rtlh64
IMAGE_NAME: Rtlh64.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 45190cf7
FAILURE_BUCKET_ID: X64_0xD1_Rtlh64+69d7
BUCKET_ID: X64_0xD1_Rtlh64+69d7
Followup: MachineOwner
---------
------------- schnipp off ----------------------------------------------------------------------------------------------
Welche Problemlösung könnt Ihr mir empfehlen?
Im voraus besten Dank.
Jürgen
Hier erstmal mein Equipment:
AMD Athlon 64 X2 Dual Core Prozessor 5000+
Mainboard = ASRock ALIVESATA2-GLAN
http://www.asrock.com/MB/overview.asp?Model=ALiveSATA2-GLAN
GraKa = NVIDIA GeForce 7300 LE
NIC (onboard) = Realtek PCIe GBE Family Controller
Arbeitsspeicher = 8 GB RAM (4 mal 2 GB von Kingston)
Windows Vista Business 64 bit, incl. SP 2 = Hostsystem
Im Geräte-Manager gab es vor ein paar Tagen ein Problem,
habe im BIOS den Game/MIDI-Port deaktiviert und danach
kam dieser Fehler nicht mehr.
Virtual PC 2007, SP 1, Version = 6.0.192.0 = 64 bit
2 mal Windows 7 RC (je 32 Bit) = Gastsysteme (zugewiesener RAM = jeweils 1 GB)
1 mal Windows Server 2008, SP 2 (32 Bit) = Gastsystem (zugewiesener RAM = 2 GB)
Beim Arbeiten mit Windows Server 2008 unter VPC 2007 kam es zum Absturz und einem
anschließenden Bluescreen. Den dazugehörigen MiniDump kann man weiter unten ausführlch
anschauen.
Erste Meldungen:
------------- schnipp on ----------------------------------------------------------------------------------------------
DRIVER_IRQL_NOT_LESS_OR_EQUAL
*** STOP: 0x000000D1 (0x0000000000000010,0x0000000000000002,0x0000000000000001,
0XFFFFFA6000C4AB9E)
*** ndis.sys - Adress FFFFFA6000C4AB9E base at FFFFFA6000C08000,
DateStamp 49e02df3
------------- schnipp off ----------------------------------------------------------------------------------------------
Könnte dies auf Probleme mit der Netzwerkkarte hindeuten?
Es wurden ausführliche Tests bezgl. RAM unternommen: kein Befund!
Und hier der komplette DUMP:
------------- schnipp on ----------------------------------------------------------------------------------------------
t (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\Mini061509-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6002.18005.amd64fre.lh_sp2rtm.090410-1830
Machine Name:
Kernel base = 0xfffff800`01a4f000 PsLoadedModuleList = 0xfffff800`01c13dd0
Debug session time: Mon Jun 15 22:34:39.429 2009 (GMT+2)
System Uptime: 0 days 1:05:17.215
Loading Kernel Symbols
...............................................................
................................................................
..
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {10, 2, 1, fffffa6000c4ab9e}
Unable to load image \SystemRoot\system32\DRIVERS\Rtlh64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Rtlh64.sys
*** ERROR: Module load completed but symbols could not be loaded for Rtlh64.sys
Probably caused by : Rtlh64.sys ( Rtlh64+69d7 )
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: 0000000000000010, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffffa6000c4ab9e, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80001c76080
0000000000000010
CURRENT_IRQL: 2
FAULTING_IP:
ndis!ndisXlateSendCompleteNetBufferListToPacket+3e
fffffa60`00c4ab9e 48c7411036434f4d mov qword ptr [rcx+10h],4D4F4336h
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: Virtual PC.exe
TRAP_FRAME: fffffa600757c3c0 -- (.trap 0xfffffa600757c3c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa80092089b0 rbx=0000000000000000 rcx=0000000000000000
rdx=fffffa600757c5d8 rsi=0000000000000000 rdi=0000000000000000
rip=fffffa6000c4ab9e rsp=fffffa600757c550 rbp=fffffa8007669990
r8=fffffa600757c5d0 r9=fffffa80091b2610 r10=00000000000001be
r11=00000000000001be r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
ndis!ndisXlateSendCompleteNetBufferListToPacket+0x3e:
fffffa60`00c4ab9e 48c7411036434f4d mov qword ptr [rcx+10h],4D4F4336h ds:00000000`00000010=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80001aa91ee to fffff80001aa9450
STACK_TEXT:
fffffa60`0757c278 fffff800`01aa91ee : 00000000`0000000a 00000000`00000010 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffffa60`0757c280 fffff800`01aa80cb : 00000000`00000001 fffffa60`0757c4d0 00000000`00000000 fffffa80`07669990 : nt!KiBugCheckDispatch+0x6e
fffffa60`0757c3c0 fffffa60`00c4ab9e : 00000000`00000042 fffffa80`08dba050 00000000`09659740 fffff800`01a0d5df : nt!KiPageFault+0x20b
fffffa60`0757c550 fffffa60`00db111d : fffffa80`0919f170 fffffa80`070e0120 fffffa60`0757c5f0 fffffa60`0757c5a0 : ndis!ndisXlateSendCompleteNetBufferListToPacket+0x3e
fffffa60`0757c580 fffffa60`00dac492 : 00000000`00000000 fffffa80`092089b0 fffffa80`0920a010 00000000`09659740 : ndis!ndisMSendNetBufferListsCompleteToNdisPackets+0x6d
fffffa60`0757c5d0 fffffa60`00dac24c : fffffa80`08dba1a0 00000000`00000000 fffffa80`08dba1a0 fffffa80`08f7c6c0 : ndis!ndisMSendCompleteNetBufferListsInternal+0xa2
fffffa60`0757c640 fffffa60`00bb09d7 : 00000000`00000000 fffffa80`091b2610 00000000`00000000 fffffa80`091b2610 : ndis!NdisMSendNetBufferListsComplete+0x7c
fffffa60`0757c680 00000000`00000000 : fffffa80`091b2610 00000000`00000000 fffffa80`091b2610 fffffa80`0917df80 : Rtlh64+0x69d7
STACK_COMMAND: kb
FOLLOWUP_IP:
Rtlh64+69d7
fffffa60`00bb09d7 ?? ???
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: Rtlh64+69d7
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Rtlh64
IMAGE_NAME: Rtlh64.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 45190cf7
FAILURE_BUCKET_ID: X64_0xD1_Rtlh64+69d7
BUCKET_ID: X64_0xD1_Rtlh64+69d7
Followup: MachineOwner
---------
------------- schnipp off ----------------------------------------------------------------------------------------------
Welche Problemlösung könnt Ihr mir empfehlen?
Im voraus besten Dank.
Jürgen