rt1970 10 Geschrieben 26. Juli 2011 Melden Teilen Geschrieben 26. Juli 2011 (bearbeitet) Hallo! Seit dem Grafikkartentausch von ATI auf Nvidia startet der Server nur mit BSOD! Nur abgesichert und VGA-Modus funktionieren noch... Vorgehen: ATI-Zeugs unter "Software" deinstalliert, heruntergefahren, gewechselt, gestartet und NVidia-Treiber installiert. Neustart => BSOD! Die Nvidia Grafikkarten, die ich testete sind 8400 GS PCI-X 16 (neuster Nvidia-Treiber) und FX 5200 PCI (Microsoft-Treiber) In div. Foren wird auf den RAM verwiesen. Allerdings lief der Server mit der ATI einwandfrei! Mainboard ASUS DSGC-DW Hier die dmp-Auswertungen: 8400er erster Neustart nach Treiber: SYSTEM_PTE_MISUSE (da) The stack trace identifies the guilty driver. Arguments: Arg1: 00000400, Type of error. Arg2: b5618c00 Arg3: 00000002 Arg4: 00000000 Debugging Details: ------------------ CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP BUGCHECK_STR: 0xDA PROCESS_NAME: rundll32.exe CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from 8083b72b to 80827c83 STACK_TEXT: b21cafd4 8083b72b 000000da 00000400 b5618c00 nt!KeDelayExecutionThread+0xb9 b21caffc 8083d4c2 b5618c00 00000002 8b0ea0f0 nt!MiAllocateContiguousMemory+0xb1 b21cb0a4 b786b14f b5618c00 00000000 8a7c0ed0 nt!MmProbeAndLockSelectedPages+0xce b21cb0c0 b786cc72 8b0ea350 b5618c00 8a34ace8 VIDEOPRT!pVideoPortFreeDeviceBase+0x6f b21cb0d0 b7b3be8b 8b0ea350 b5618c00 00000000 VIDEOPRT!VideoPortUnmapMemory+0x16 b21cb0e0 b21cb170 8a34ab30 8a7c0008 b7b3bf0f nv4_mini!_NULL_IMPORT_DESCRIPTOR <PERF> (nv4_mini+0x2c4e8b) WARNING: Frame IP not in any known module. Following frames may be wrong. 00000000 00000000 00000000 00000000 00000000 0xb21cb170 STACK_COMMAND: kb FOLLOWUP_IP: VIDEOPRT!pVideoPortFreeDeviceBase+6f b786b14f ?? ??? SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: VIDEOPRT!pVideoPortFreeDeviceBase+6f FOLLOWUP_NAME: MachineOwner MODULE_NAME: VIDEOPRT IMAGE_NAME: VIDEOPRT.SYS DEBUG_FLR_IMAGE_TIMESTAMP: 45d69c56 FAILURE_BUCKET_ID: 0xDA_VIDEOPRT!pVideoPortFreeDeviceBase+6f BUCKET_ID: 0xDA_VIDEOPRT!pVideoPortFreeDeviceBase+6f Zweiter Neustart: SYSTEM_PTE_MISUSE (da) The stack trace identifies the guilty driver. Arguments: Arg1: 00000400, Type of error. Arg2: b5618c00 Arg3: 00000002 Arg4: 00000000 Debugging Details: ------------------ CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP BUGCHECK_STR: 0xDA PROCESS_NAME: rundll32.exe CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from 8083b72b to 80827c83 STACK_TEXT: b21cafd4 8083b72b 000000da 00000400 b5618c00 nt!KeDelayExecutionThread+0xb9 b21caffc 8083d4c2 b5618c00 00000002 8b0ea0f0 nt!MiAllocateContiguousMemory+0xb1 b21cb0a4 b786b14f b5618c00 00000000 8a7c0ed0 nt!MmProbeAndLockSelectedPages+0xce b21cb0c0 b786cc72 8b0ea350 b5618c00 8a34ace8 VIDEOPRT!pVideoPortFreeDeviceBase+0x6f b21cb0d0 b7b3be8b 8b0ea350 b5618c00 00000000 VIDEOPRT!VideoPortUnmapMemory+0x16 b21cb0e0 b21cb170 8a34ab30 8a7c0008 b7b3bf0f nv4_mini!_NULL_IMPORT_DESCRIPTOR <PERF> (nv4_mini+0x2c4e8b) WARNING: Frame IP not in any known module. Following frames may be wrong. 00000000 00000000 00000000 00000000 00000000 0xb21cb170 STACK_COMMAND: kb FOLLOWUP_IP: VIDEOPRT!pVideoPortFreeDeviceBase+6f b786b14f ?? ??? SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: VIDEOPRT!pVideoPortFreeDeviceBase+6f FOLLOWUP_NAME: MachineOwner MODULE_NAME: VIDEOPRT IMAGE_NAME: VIDEOPRT.SYS DEBUG_FLR_IMAGE_TIMESTAMP: 45d69c56 FAILURE_BUCKET_ID: 0xDA_VIDEOPRT!pVideoPortFreeDeviceBase+6f BUCKET_ID: 0xDA_VIDEOPRT!pVideoPortFreeDeviceBase+6f Followup: MachineOwner bearbeitet 26. Juli 2011 von rt1970 Zitieren Link zu diesem Kommentar
rt1970 10 Geschrieben 26. Juli 2011 Autor Melden Teilen Geschrieben 26. Juli 2011 Dritter Neustart: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Some common problems are exception code 0x80000003. This means a hard coded breakpoint or assertion was hit, but this system was booted /NODEBUG. This is not supposed to happen as developers should never have hardcoded breakpoints in retail code, but ... If this happens, make sure a debugger gets connected, and the system is booted /DEBUG. This will let us see why this breakpoint is happening. Arguments: Arg1: c0000005, The exception code that was not handled Arg2: 80882748, The address that the exception occurred at Arg3: b26ae9c8, Trap Frame Arg4: 00000000 Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in "0x%08lx" verweist auf Speicher in "0x%08lx". Der Vorgang "%s" konnte nicht auf dem Speicher durchgef hrt werden. FAULTING_IP: nt!KeSwapProcessOrStack+18 80882748 8b448ee8 mov eax,dword ptr [esi+ecx*4-18h] TRAP_FRAME: b26ae9c8 -- (.trap 0xffffffffb26ae9c8) ErrCode = 00000000 eax=2608b170 ebx=88b66610 ecx=00000006 edx=00000000 esi=2608b158 edi=89531770 eip=80882748 esp=b26aea3c ebp=b26aea44 iopl=0 nv up ei ng nz ac po cy cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010293 nt!KeSwapProcessOrStack+0x18: 80882748 8b448ee8 mov eax,dword ptr [esi+ecx*4-18h] ds:0023:2608b158=???????? Resetting default scope CUSTOMER_CRASH_COUNT: 3 DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP BUGCHECK_STR: 0x8E CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 00000000 to 80882748 STACK_TEXT: b26aea38 00000000 80882640 b26aeb00 f74f88ba nt!KeSwapProcessOrStack+0x18 STACK_COMMAND: kb FOLLOWUP_IP: nt!KeSwapProcessOrStack+18 80882748 8b448ee8 mov eax,dword ptr [esi+ecx*4-18h] SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!KeSwapProcessOrStack+18 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlpa.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4cbda48f FAILURE_BUCKET_ID: 0x8E_nt!KeSwapProcessOrStack+18 BUCKET_ID: 0x8E_nt!KeSwapProcessOrStack+18 Vierter Neustart: SYSTEM_PTE_MISUSE (da) The stack trace identifies the guilty driver. Arguments: Arg1: 00000400, Type of error. Arg2: b494dc00 Arg3: 00000002 Arg4: 00000000 Debugging Details: ------------------ CUSTOMER_CRASH_COUNT: 4 DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP BUGCHECK_STR: 0xDA PROCESS_NAME: nvsvc32.exe CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from 8083b72b to 80827c83 STACK_TEXT: b2081768 8083b72b 000000da 00000400 b494dc00 nt!KeDelayExecutionThread+0xb9 b2081790 8083d4c2 b494dc00 00000002 8b0e10f0 nt!MiAllocateContiguousMemory+0xb1 b2081838 b786b14f b494dc00 00000000 8a9d7ed0 nt!MmProbeAndLockSelectedPages+0xce b2081854 b786cc72 8b0e1350 b494dc00 8a33cc70 VIDEOPRT!pVideoPortFreeDeviceBase+0x6f b2081864 b7b3be8b 8b0e1350 b494dc00 00000000 VIDEOPRT!VideoPortUnmapMemory+0x16 b2081874 b2081904 8a33eeb0 8a9d7008 b7b3bf0f nv4_mini!_NULL_IMPORT_DESCRIPTOR <PERF> (nv4_mini+0x2c4e8b) WARNING: Frame IP not in any known module. Following frames may be wrong. 00000000 00000000 00000000 00000000 00000000 0xb2081904 STACK_COMMAND: kb FOLLOWUP_IP: VIDEOPRT!pVideoPortFreeDeviceBase+6f b786b14f ?? ??? SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: VIDEOPRT!pVideoPortFreeDeviceBase+6f FOLLOWUP_NAME: MachineOwner MODULE_NAME: VIDEOPRT IMAGE_NAME: VIDEOPRT.SYS DEBUG_FLR_IMAGE_TIMESTAMP: 45d69c56 FAILURE_BUCKET_ID: 0xDA_VIDEOPRT!pVideoPortFreeDeviceBase+6f BUCKET_ID: 0xDA_VIDEOPRT!pVideoPortFreeDeviceBase+6f Zitieren Link zu diesem Kommentar
rt1970 10 Geschrieben 26. Juli 2011 Autor Melden Teilen Geschrieben 26. Juli 2011 Jetzt die 5200er mit Microsoft-Treiber: 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: ab1df7b7, memory referenced. Arg2: 00000000, value 0 = read operation, 1 = write operation. Arg3: 80882748, If non-zero, the instruction address which referenced the bad memory address. Arg4: 00000000, (reserved) Debugging Details: ------------------ Could not read faulting driver name READ_ADDRESS: ab1df7b7 FAULTING_IP: nt!KeSwapProcessOrStack+18 80882748 ?? ??? MM_INTERNAL_CODE: 0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP BUGCHECK_STR: 0x50 PROCESS_NAME: wmiprvse.exe CURRENT_IRQL: 1 LAST_CONTROL_TRANSFER: from 8085ed47 to 80827c83 STACK_TEXT: b35e2938 8085ed47 00000050 ab1df7b7 00000000 nt!KeDelayExecutionThread+0xb9 b35e29b0 8088c820 00000000 ab1df7b7 00000000 nt!MiQueryAddressState+0x2f7 b35e29c8 80882748 badb0d00 00000000 00000004 nt!ExFreePoolWithTag+0x4ea b35e29d4 00000000 f7557000 b35e29f8 00000001 nt!KeSwapProcessOrStack+0x18 STACK_COMMAND: kb FOLLOWUP_IP: nt!KeSwapProcessOrStack+18 80882748 ?? ??? SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nt!KeSwapProcessOrStack+18 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlpa.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4cbda48f FAILURE_BUCKET_ID: 0x50_nt!KeSwapProcessOrStack+18 BUCKET_ID: 0x50_nt!KeSwapProcessOrStack+18 Noch ein Neustart: 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: 98bdf298, memory referenced. Arg2: 00000000, value 0 = read operation, 1 = write operation. Arg3: 80882748, If non-zero, the instruction address which referenced the bad memory address. Arg4: 00000000, (reserved) Debugging Details: ------------------ Could not read faulting driver name READ_ADDRESS: 98bdf298 FAULTING_IP: nt!KeSwapProcessOrStack+18 80882748 ?? ??? MM_INTERNAL_CODE: 0 CUSTOMER_CRASH_COUNT: 2 DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP BUGCHECK_STR: 0x50 PROCESS_NAME: wmiprvse.exe CURRENT_IRQL: 1 LAST_CONTROL_TRANSFER: from 8085ed47 to 80827c83 STACK_TEXT: b360b938 8085ed47 00000050 98bdf298 00000000 nt!KeDelayExecutionThread+0xb9 b360b9b0 8088c820 00000000 98bdf298 00000000 nt!MiQueryAddressState+0x2f7 b360b9c8 80882748 badb0d00 00000000 00000004 nt!ExFreePoolWithTag+0x4ea b360b9d4 00000000 f7557000 b360b9f8 00000001 nt!KeSwapProcessOrStack+0x18 STACK_COMMAND: kb FOLLOWUP_IP: nt!KeSwapProcessOrStack+18 80882748 ?? ??? SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nt!KeSwapProcessOrStack+18 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlpa.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4cbda48f FAILURE_BUCKET_ID: 0x50_nt!KeSwapProcessOrStack+18 BUCKET_ID: 0x50_nt!KeSwapProcessOrStack+18 Hat jemand eine Idee??? Zitieren Link zu diesem Kommentar
rt1970 10 Geschrieben 26. Juli 2011 Autor Melden Teilen Geschrieben 26. Juli 2011 Unable to load image \WINDOWS\system32\ntkrnlpa.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntkrnlpa.exe Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (4 procs) Free x86 compatible Product: LanManNt, suite: SmallBusiness TerminalServer SmallBusinessRestricted SingleUserTS Machine Name: Kernel base = 0x80800000 PsLoadedModuleList = 0x808a6ea8 Debug session time: Mon Jul 25 22:02:58.717 2011 (GMT+2) System Uptime: 0 days 2:32:29.366 Unable to load image \WINDOWS\system32\ntkrnlpa.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntkrnlpa.exe Unable to load image \SystemRoot\system32\DRIVERS\VIDEOPRT.SYS, Win32 error 0n2 *** WARNING: Unable to verify timestamp for VIDEOPRT.SYS Unable to load image \SystemRoot\system32\DRIVERS\nv4_mini.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for nv4_mini.sys Probably caused by : VIDEOPRT.SYS ( VIDEOPRT!pVideoPortFreeDeviceBase+6f Zitieren Link zu diesem Kommentar
MrCocktail 191 Geschrieben 26. Juli 2011 Melden Teilen Geschrieben 26. Juli 2011 Nimm nen Board / GraKa die zertifiziert sind (oder zumindest die Treiber) Designed from the ground up for professional workstations, ASUS will launch a bran-new workstation DSGC-DW which is loaded with Intel® latest dual/quad core and dual processor platform, Intel® 5000X MCH and Intel® 6321ESB ICH chipset, DDR2 fully buffer DIMM support, and integrated high-speed interfaces for true workstation operation. Ein Workstation Board hat IMHO nichts in einem Server zu suchen. Zitieren Link zu diesem Kommentar
rt1970 10 Geschrieben 27. Juli 2011 Autor Melden Teilen Geschrieben 27. Juli 2011 Hat aber jetzt nicht wirklich etwas mit dem Fehler zu tun!? Trotzdem Danke für den Hinweis! Das Board wird allerdings bei ASUS unter Server gelistet... Zitieren Link zu diesem Kommentar
Empfohlene Beiträge
Schreibe einen Kommentar
Du kannst jetzt antworten und Dich später registrieren. Falls Du bereits ein Mitglied bist, logge Dich jetzt ein.