tosiaan nyt rupesi ihmettyttään kun ostin aikoja sitten HD 5770 näyttiksen ja eka todettiin rikkinäiseksi huollossa, kun se tuli takasi niin samat ongelmat vaan jatkuivat ja laitoin sen takasi huoltoon mutta se oli ehjä tuote joten sama tuli takas. Ainakin yksi bsod viittasi kovalevyyn (katsoin koodin perusteella) joten testasin sen eikä se ollu ainakaan rikki. Tänään tuli tälläinen, tässä minidumb: Microsoft (R) Windows Debugger Version 6.12.0002.633 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\Mini032411-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available WARNING: Whitespace at end of path element Symbol search path is: srv*c:\symbols*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 x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 6002.18327.x86fre.vistasp2_gdr.101014-0432 Machine Name: Kernel base = 0x82236000 PsLoadedModuleList = 0x8234dc70 Debug session time: Thu Mar 24 14:32:58.612 2011 (UTC + 2:00) System Uptime: 0 days 0:01:56.363 Loading Kernel Symbols ............................................................... ................................................................ ................. Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck C1, {a6396e70, a639643c, 170190, 23} Unable to load image \SystemRoot\System32\Drivers\sptd.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for sptd.sys *** ERROR: Module load completed but symbols could not be loaded for sptd.sys Probably caused by : ecache.sys ( ecache!EcDeviceIoCleanup+17 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1) Special pool has detected memory corruption. Typically the current thread's stack backtrace will reveal the guilty party. Arguments: Arg1: a6396e70, address trying to free Arg2: a639643c, address where bits are corrupted Arg3: 00170190, (reserved) Arg4: 00000023, caller is freeing an address where nearby bytes within the same page have been corrupted Debugging Details: ------------------ BUGCHECK_STR: 0xC1_23 SPECIAL_POOL_CORRUPTION_TYPE: 23 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP PROCESS_NAME: explorer.exe CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from 822c0cff to 82303b3f STACK_TEXT: 8039dab4 822c0cff 000000c1 a6396e70 a639643c nt!KeBugCheckEx+0x1e 8039dbac 823230f0 a6396e70 00000000 a6396e70 nt!MmFreeSpecialPool+0x6c 8039dc14 822e8626 a6396e70 00000000 8039dc50 nt!ExFreePoolWithTag+0xeb 8039dc30 825191cd a6396e70 a6266f90 9cf5bba0 nt!IopFreeIrp+0x56 8039dc48 8496a57f 00000000 9cf5bba0 8039dcb4 nt!IovFreeIrpPrivate+0x58 8039dc58 8496e197 9cf5bba0 a6396e70 8039dd58 ecache!EcDeviceIoCleanup+0x17 8039dcb4 82519d4d 8839f020 a6396e70 003ebe68 ecache!EcDispatchReadWriteCompletion+0x4d1 8039dcec 822dd21b 8839f020 a6396e70 8039dd58 nt!IovpLocalCompletionRoutine+0x16e 8039dd20 82519b95 00000000 a3af6008 883167b8 nt!IopfCompleteRequest+0x11d 8039dd90 849a2d5f 8039ddc4 849a23ee 88313ac8 nt!IovCompleteRequest+0x11c 8039dd98 849a23ee 88313ac8 a6396e70 00000001 CLASSPNP!ClassCompleteRequest+0x11 8039ddc4 82519d4d 00000000 a6286f00 00af6008 CLASSPNP!TransferPktComplete+0x2b6 8039ddfc 822dd21b 00000000 a6286f00 8039de68 nt!IovpLocalCompletionRoutine+0x16e 8039de30 82519b95 00000000 a6286f00 a6286f00 nt!IopfCompleteRequest+0x11d 8039dea0 82d2635b a3af60b4 8bd85670 8039ded0 nt!IovCompleteRequest+0x11c 8039deb0 82d26d4a 87575c50 a6286f00 a3af60b4 ataport!IdeCompleteScsiIrp+0x31 8039ded0 82d24020 87575c50 00000000 8039df00 ataport!IdeCommonCrbCompletion+0x44 8039dee0 82d28ef3 875680e0 8bd85670 8bd85670 ataport!IdeTranslateCompletedRequest+0x26 8039df00 82d2912d 875680e0 8bd85670 8756809c ataport!IdeProcessCompletedRequests+0x121 8039df54 806a6882 8756809c 87568028 00000000 ataport!IdePortCompletionDpc+0xab WARNING: Stack unwind information not available. Following frames may be wrong. 8039df88 822e06e2 8756809c 87568028 00000000 sptd+0x13882 8039dff4 822de2f5 9b0bbc68 00000000 00000000 nt!KiRetireDpcList+0x147 8039dff8 9b0bbc68 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x45 822de2f5 00000000 0000001b 00c7850f bb830000 0x9b0bbc68 STACK_COMMAND: kb FOLLOWUP_IP: ecache!EcDeviceIoCleanup+17 8496a57f 8b4628 mov eax,dword ptr [esi+28h] SYMBOL_STACK_INDEX: 5 SYMBOL_NAME: ecache!EcDeviceIoCleanup+17 FOLLOWUP_NAME: MachineOwner MODULE_NAME: ecache IMAGE_NAME: ecache.sys DEBUG_FLR_IMAGE_TIMESTAMP: 49e01f2c FAILURE_BUCKET_ID: 0xC1_23_VRF_ecache!EcDeviceIoCleanup+17 BUCKET_ID: 0xC1_23_VRF_ecache!EcDeviceIoCleanup+17 Followup: MachineOwner Edit: kun nopeesti vilkaisin netistä niin viittaisi muisteihin, mitäs mieltä muut on?
Mulla on jo valmiina toi kun aikasemmin muistit oon testannu, laitan sen yöksi pyörimään ja laitan tuloksen sitte tänne. Kiitos
joo tosiaan molemmilla muisti kammoilla 7h pyöritin testiä ilman yhtäkään error:ia Edit. tässä uusin dumppi: Microsoft (R) Windows Debugger Version 6.12.0002.633 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\Mini032511-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available WARNING: Whitespace at end of path element Symbol search path is: srv*c:\symbols*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 x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 6002.18327.x86fre.vistasp2_gdr.101014-0432 Machine Name: Kernel base = 0x8224b000 PsLoadedModuleList = 0x82362c70 Debug session time: Fri Mar 25 15:58:43.577 2011 (UTC + 2:00) System Uptime: 0 days 0:59:45.440 Loading Kernel Symbols ............................................................... ................................................................ ................ Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000008E, {c0000005, 8242bdec, a28786dc, 0} Probably caused by : memory_corruption ( nt!MiPerformFixups+61 ) Followup: MachineOwner --------- 0: 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: 8242bdec, The address that the exception occurred at Arg3: a28786dc, Trap Frame Arg4: 00000000 Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - K sky osoitteessa 0x%08lx viittasi muistiin osoitteessa 0x%08lx. Muisti ei voi olla %s. FAULTING_IP: nt!MiPerformFixups+61 8242bdec 8b7904 mov edi,dword ptr [ecx+4] TRAP_FRAME: a28786dc -- (.trap 0xffffffffa28786dc) ErrCode = 00000000 eax=00000fff ebx=87e1d000 ecx=00000420 edx=00000420 esi=a20eb000 edi=87e1d000 eip=8242bdec esp=a2878750 ebp=a287877c iopl=0 nv up ei pl nz na po nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202 nt!MiPerformFixups+0x61: 8242bdec 8b7904 mov edi,dword ptr [ecx+4] ds:0023:00000424=???????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP BUGCHECK_STR: 0x8E PROCESS_NAME: iTunes.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 8244e7c8 to 8242bdec STACK_TEXT: a287877c 8244e7c8 9c1249a8 febf0000 00000001 nt!MiPerformFixups+0x61 a28787a0 8226a034 9c1249a8 c0509da8 fffffbfa nt!MiRelocateImagePfn+0xfe a2878804 8240a65a 87851008 c0509da8 00000002 nt!MiValidateImagePages+0x4ce a2878830 8243adf0 87851008 c0509da8 a17189e8 nt!MiSwitchBaseAddress+0x4c a2878854 8247c3d9 87851008 00000000 00000000 nt!MiRelocateImageAgain+0xd6 a2878968 8247cf16 a28789bc 0000000d a2878a0c nt!MmCreateSection+0x51d a28789dc 82405084 a2878a4c 0000000d a2878a0c nt!NtCreateSection+0x177 a2878a54 82404c98 a2878b0c 81879428 a2878a90 nt!PfSnGetSectionObject+0x1a4 a2878ae8 82404059 00878b0c 00000001 00000000 nt!PfSnPrefetchSections+0x1d3 a2878c64 82417614 b08bf000 a2878c94 a2878ca0 nt!PfSnPrefetchScenario+0x13a a2878cf8 824176b4 82465a97 88890398 a2878d50 nt!PfSnBeginAppLaunch+0x382 a2878d08 82465646 6f55f5f6 00000000 00000000 nt!PfProcessCreateNotification+0x65 a2878d50 82289efe 00000000 772d5c88 00000001 nt!PspUserThreadStartup+0x116 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16 STACK_COMMAND: kb FOLLOWUP_IP: nt!MiPerformFixups+61 8242bdec 8b7904 mov edi,dword ptr [ecx+4] SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!MiPerformFixups+61 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 4cb710d6 IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: 0x8E_VRF_nt!MiPerformFixups+61 BUCKET_ID: 0x8E_VRF_nt!MiPerformFixups+61 Followup: MachineOwner ---------
