Vraag & Antwoord

Moederborden, processors, overklokken, casemodding en koeling

Output van dump na crash XP op nieuw systeem?

4 antwoorden
  • hmm, nieuw spul, verse installatie XP pro SP2, toch een paar spontane crashes. Ik zal in ieder geval mijn geheugen eens checken met de nieuwe setup. http://forum.computertotaal.nl/phpBB2/viewtopic.php?p=1266313#1266313 [quote:c0c0a6928e]1 GigaByte GA-P35C-DS3R, P35 (ATX, DDR2⁄DDR3, Sound, LAN, SATA II, RAID)19.00% € 97,95 € 97,95 2 Kingston 1GB DDR2 PC6400 800Mhz CL5 (KVR800D2N5⁄1G) 19.00% € 25,80 € 51,60 1 MSI RX3850, (RX3850-T2D256E-OC) ATI Radeon, 256mb DDR3, PCI-E, OC edition 19.00% € 179,95 € 179,95 1 Intel Core 2 Duo E6750 (S775, 2x2.66GHz, 4MB, 1333MHz FSB, Boxed) 19.00% € 158,45 € 158,45 [/quote:c0c0a6928e] Ik heb iig een van de bestanden proberen te bekijken, maar DUMPCHK is totaal nieuw voor me. ik heb de MS Support Tools d XP CD geïnstalleerd en in cmd mode dus deze output gegenereerd. Ik zoek zelf ook wel verder, maar heeft iemand een aha erlebnis bij de output van deze DUMPCHK Verder: geen gele uitroeptekens, vage rapporten in het log [quote:c0c0a6928e]Foutcode; 1000008e, parameter1: c0000005, parameter2: 805e0407, parameter3: b95d7a30, parameter4: 00000000. gebeurtenis id 1003 categorie 102 bron: system error[/quote:c0c0a6928e] [quote:c0c0a6928e]----- 32 bit Kernel Mini Dump Analysis DUMP_HEADER32: MajorVersion 0000000f MinorVersion 00000a28 DirectoryTableBase 0a4c02c0 PfnDataBase 81086000 PsLoadedModuleList 8055c700 PsActiveProcessHead 805627b8 MachineImageType 0000014c NumberProcessors 00000002 BugCheckCode 1000008e BugCheckParameter1 c0000005 BugCheckParameter2 805e0407 BugCheckParameter3 b95d7a30 BugCheckParameter4 00000000 PaeEnabled 00000001 KdDebuggerDataBlock 8054c2e0 MiniDumpFields 00000dff TRIAGE_DUMP32: ServicePackBuild 00000200 SizeOfDump 00010000 ValidOffset 0000fffc ContextOffset 00000320 ExceptionOffset 000007d0 MmOffset 00001068 UnloadedDriversOffset 000010a0 PrcbOffset 00001878 ProcessOffset 000024c8 ThreadOffset 00002728 CallStackOffset 00002980 SizeOfCallStack 000005c0 DriverListOffset 000031d0 DriverCount 00000083 StringPoolOffset 000058b8 StringPoolSize 00001218 BrokenDriverOffset 00000000 TriageOptions 00000041 TopOfStack b95d7a40 DebuggerDataOffset 00002f40 DebuggerDataSize 00000290 DataBlocksOffset 00006ad0 DataBlocksCount 00000005 Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700 Debug session time: Thu Jan 17 20:11:42 2008 System Uptime: 0 days 0:40:34 start end module name 804d7000 806e3000 nt Checksum: 001F6095 Timestamp: Wed Aug 04 07:58:37 2004 (41107B0D) Unloaded modules: a75f7000 a7621000 kmixer.sys Timestamp: unavailable (00000000) a97f7000 a9821000 kmixer.sys Timestamp: unavailable (00000000) aa41e000 aa448000 kmixer.sys Timestamp: unavailable (00000000) ba744000 ba745000 drmkaud.sys Timestamp: unavailable (00000000) ba268000 ba275000 DMusic.sys Timestamp: unavailable (00000000) b95f8000 b9606000 swmidi.sys Timestamp: unavailable (00000000) aa448000 aa46b000 aec.sys Timestamp: unavailable (00000000) ba644000 ba646000 splitter.sys Timestamp: unavailable (00000000) ba428000 ba42d000 Cdaudio.SYS Timestamp: unavailable (00000000) ba56c000 ba56f000 Sfloppy.SYS Timestamp: unavailable (00000000) Finished dump check[/quote:c0c0a6928e]
  • bios dump (deel), dus F4 bios, zou nog naar F5 kunnen (verbeteringen lijken niet zo relevant, even nog over nadenken. [quote:c18ca03c4e]SMBIOS Data Dumper 2.1, Copyright (c) 2002 PC Pitstop LLC ** DMI Header at F0CF:0000 ** TableLength = 1199 TableAddr32 = 000F0100 NumStructs = 39 Revision = 0024 == BIOS (type 0, handle 0000, length 24) == Vendor = Award Software International, Inc. Version = F4 Segment Address = E000 Release Date = 09/07/2007 ROM Size = 1024 KB Characteristics = |PCI|Plug and Play|APM|Flash BIOS|BIOS Shadowing|CD Boot|Selectable Boot|EDD|360KB FDD|1.2MB FDD|720KB FDD|2.88MB FDD|INT5 PrtScrn|Int9 8042|INT14 Serial|INT17 Printer|INT10 CGA/Mono| OEM Characteristics = 00000000 Extended 1 = |ACPI|USB Legacy|LS-120 boot|ATAPI ZIP Boot| Extended 2 = |BIOS Boot Spec|UNDEF#0004| == System (type 1, handle 0001, length 27) == Manufacturer = Gigabyte Technology Co., Ltd. Product Name = P35C-DS3R Version = Serial Number = UUID = 00 00 00 00 00 00 00 00 00 00 00 1A 4D 56 8A 71 Wakeup Type = Power Switch == Baseboard (type 2, handle 0002, length 8) == Manufacturer = Gigabyte Technology Co., Ltd. Product Name = P35C-DS3R Version = x.x Serial Number = == Chassis (type 3, handle 0003, length 17) == Manufacturer = Gigabyte Technology Co., Ltd. Chassis Type = Desktop Version = Serial Number = Asset Tag Number = Bootup State = Unknown Power Supply State = Unknown Thermal State = Unknown Security Status = Unknown OEM-defined = 00000000 == Processor (type 4, handle 0004, length 35) == Socket Designation = Socket 775 Processor Type = CPU Processor Family = Other Processor Manufacturer = Intel Processor ID = 000006FB BFEBFBFF Processor Version = Intel(R) Core(TM)2 Duo CPU Voltage = Currently 1.4V External Clock (MHz) = 333 Max Speed (MHz) = 4000 Current Speed (MHz) = 2666 Status = Populated, Enabled Processor Upgrade = Socket 478 L1 Cache Handle = 000A L2 Cache Handle = 000B L3 Cache Handle = FFFF Serial Number = Asset Tag = [/quote:c18ca03c4e]
  • dmpchk is niet genoeg. meer analyse: http://forums.majorgeeks.com/showthread.php?t=35246 Dan heb je deze 2 nodig: http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx http://www.microsoft.com/whdc/DevTools/Debugging/symbolpkg.mspx en dan windbg draaien en daarna in windbg !analyze -v t (staat in de analyse text) dan krijg je zoets als hieronder. Bij mij lijkt dus de driver van de USB dongel de oorzaak..... [quote:4f324a74fd]Unable to load image ZDCNDIS5.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ZDCNDIS5.sys *** ERROR: Module load completed but symbols could not be loaded for ZDCNDIS5.sys ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000008E, {c0000005, 805e0407, a6530a30, 0} Probably caused by : ZDCNDIS5.sys ( ZDCNDIS5+24be ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* 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: 805e0407, The address that the exception occurred at Arg3: a6530a30, Trap Frame Arg4: 00000000 Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - De instructie op 0x%08lx verwijst naar geheugen op 0x%08lx. De lees- of schrijfbewerking ("%s") op het geheugen is mislukt. FAULTING_IP: nt!Ki386VdmReflectException+ef 805e0407 0fb701 movzx eax,word ptr [ecx] TRAP_FRAME: a6530a30 -- (.trap 0xffffffffa6530a30) ErrCode = 00000000 eax=000000c7 ebx=88c30bc0 ecx=000000c7 edx=a6530c28 esi=00000003 edi=ba3438d0 eip=805e0407 esp=a6530aa4 ebp=a6530aa4 iopl=0 nv up ei pl nz na pe cy cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010207 nt!Ki386VdmReflectException+0xef: 805e0407 0fb701 movzx eax,word ptr [ecx] ds:0023:000000c7=???? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: DRIVER_FAULT BUGCHECK_STR: 0x8E PROCESS_NAME: ZyXEL G-202.exe LAST_CONTROL_TRANSFER: from ba3424be to 805e0407 STACK_TEXT: a6530aa4 ba3424be 000000c7 a6530c28 00000001 nt!Ki386VdmReflectException+0xef WARNING: Stack unwind information not available. Following frames may be wrong. a6530ac0 ba3427f3 a6530c28 88c30c30 88c30bc0 ZDCNDIS5+0x24be a6530bf4 ba342ed9 a6530c3c 00000000 a6530c28 ZDCNDIS5+0x27f3 a6530c30 ba3430b7 88c7a030 c0000001 a6530c64 ZDCNDIS5+0x2ed9 a6530c40 804eeeb1 88c7a030 88c30bc0 806e5410 ZDCNDIS5+0x30b7 a6530c64 8057f4eb 88c7a030 88c30bc0 899b5df0 nt!MiAddViewsForSection+0x38 a6530d00 8057804e 00000138 00000134 00000000 nt!MiFindEmptyAddressRangeDownTree+0x150 a6530d34 8054060c 00000138 00000134 00000000 nt!RtlLengthSecurityDescriptor+0x3a a6530d64 7c90eb94 badb0d00 0012eab0 a8f76d98 nt!RtlIpv4StringToAddressA+0xfd a6530d78 00000000 00000000 00000000 00000000 0x7c90eb94 STACK_COMMAND: kb FOLLOWUP_IP: ZDCNDIS5+24be ba3424be ?? ??? SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: ZDCNDIS5+24be FOLLOWUP_NAME: MachineOwner MODULE_NAME: ZDCNDIS5 IMAGE_NAME: ZDCNDIS5.sys DEBUG_FLR_IMAGE_TIMESTAMP: 43b2047d FAILURE_BUCKET_ID: 0x8E_ZDCNDIS5+24be BUCKET_ID: 0x8E_ZDCNDIS5+24be Followup: MachineOwner --------- [/quote:4f324a74fd]
  • hmm mijn "OEM" toetsenbord deed raar... plots allemaal continue piepjes uit de kast.. (continu) Ander toetsenbord, geen problemen meer gehad. Waarschijnlijk was dit de achterliggende oorzaak....

Beantwoord deze vraag

Weet jij het antwoord op deze vraag? Registreer of meld je aan met je account

Dit is een gearchiveerde pagina. Antwoorden is niet meer mogelijk.