[RassK]

Mingi täielik jama on käimas. Arvutit pole nädal aega keegi puudutanud (seisis lihtsalt kinni). Krt veidike aega saab midagi teha siis lampi lendab BSOD kaela...
Eriti vihaseks ajab see et aru ei saa mis seda põhjustab kõik toimis ennem mitmeid kuid laitmatult... ja nüüd mingi piix kallal

Arvuti konf on profiilis.

Mälu probleem ei ole, neid sai vahetatud. Vista sai ka uuesti peale pandud... mida veel teha?
DUMP failidest midagi tarka välja ei loe...

Ühesõnaga mul on mõistus otsas

[tahanteada]

Aga toide on ju la"bi proovimata. Ja kui toide lahjaks on ja"a"nud, ka siis oskavad arvutid lolliks minna.

Postitatud mobile device

[A.S.]

[Tomorrow]

Kuna mälu vahetasid siis vaata järgmisena HDD poole.Minul kukkus kah ükspäev lampi BSOD pilduma(enne seda oli ketaste jõudlus vähenenud ja vahel kadusid ära).Tuli välja,et kahel kettal oli andmekaablitega mingi jama.Õnneks mul kablaid vedeleb siin seega vahetasin ära ja kõik jälle rock soliidne

[RassK]

Samas ega bios ei või lolliks minna aja peale?
Siiamaani veel kunagisest proovimisest UD3P Pi Bios peal ...

A.S., Tänu nendele DUMPidele ma tegingi format C + uus win peale. Tulemus oli 0...
Õnneks mul alati win eraldi ideelisel kettal, seega ajakahjum tuli hulga väiksem...

[A.S.]

Format C siis esialgu kõvaketta vea välistab, aga kuna see format ei aidanud, siis rauaprobleem ikkagi jääb. Järgmisena siis toiteploki vahetus plaanis?

Mõned DUMP failid äkki teed avalikuks?
 

[RassK]

Mnja hetkel pole kusagilt toidet ka saada... uut ei raatsi ka osta kohe ilma, et viga oleks 100% teada...

Pärast lisan mõned dump failid...
Jätkuvalt on dumpis veateade Default_bucket_id: Vista_Driver_Fault ja progressideks erinevad programmid nagu chrome.exe, setup.exe jne.
Viimane veateade oli siiski Default_bucket_id: Common_system_fault ja progressiks avp.exe (kuulub kasperskyle).

Seega jah... systeem on jumala lolliks läinud

[XYZ]

Kui klokk peal, siis võta prooviks maha + mälu vahetasid küll aga kuipalju sa seejuures memtest'i jooksutasid?

[RassK]

Klokki peal pole, uuel just OC jaoks mõeldud emaplaadil on midagi selle vastu. Nii kui väike OC teha on kohe BSOD...
Vana low-end platega sai ilusti 4GHz stabiilseks

Emaplaat garantiisse?

Memtesti pole korralikult jooksutada saanud... jooksis 3-4 tundi umbes ilma veata.

[tahanteada]

krusu70: Ära näe vaeva "mälude peksmisega"

See Sinu masina BSOD & Jamad on täiesti tüüpiline pookutu BlueStormi käitumine, muide.

Ja veel - BlueStorm sobib oma sisemise ehituse poolest Kontorimasinasse, kus Office-t jooksutatakse, mitte masinasse, kus käib kõva Klokkimine-Häkkimine.
--------------------------------------------------------------------
Kui Tallinnas oled, siis võin laenata katsetamiseks 600W-se Chieftec-i.

[RassK]

tahanteada, garanteerid 100%? Toide muidu 3a vana ka...
Tallinnast olen kaugel Toite testriga testimine reedaks toite koolmis protsessi?

muidu veits debugge: 4 tükki lisatud. tänase päeva jooksul kokku olnud siiani 5... eks tuleb juurde...

Spoiler

******************************************************************************* *                                                                             * *                        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: 1c716ac3, memory referenced Arg2: 00000002, IRQL Arg3: 00000000, value 0 = read operation, 1 = write operation Arg4: 8db324c2, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from 81b75868 Unable to read MiSystemVaType memory at 81b55420 1c716ac3 CURRENT_IRQL:  2 FAULTING_IP: smb!SmbBatchedSetBindingInfo+de 8db324c2 8b08            mov     ecx,dword ptr [eax] CUSTOMER_CRASH_COUNT:  2 DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT BUGCHECK_STR:  0xD1 PROCESS_NAME:  System TRAP_FRAME:  8336ba10 -- (.trap 0xffffffff8336ba10) ErrCode = 00000000 eax=1c716ac3 ebx=8db39318 ecx=00000014 edx=00000000 esi=87b82990 edi=881b4e5c eip=8db324c2 esp=8336ba84 ebp=8336baa8 iopl=0         ov up ei ng nz ac po cy cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010a93 smb!SmbBatchedSetBindingInfo+0xde: 8db324c2 8b08            mov     ecx,dword ptr [eax]  ds:0023:1c716ac3=???????? Resetting default scope LAST_CONTROL_TRANSFER:  from 8db324c2 to 81a98d84 STACK_TEXT:  8336ba10 8db324c2 badb0d00 00000000 882646a8 nt!KiTrap0E+0x2ac 8336baa8 8db32919 881b4e68 00000014 00000000 smb!SmbBatchedSetBindingInfo+0xde 8336bac0 8caa9a32 881b7200 881b71e0 87d7a570 smb!SmbAddressDeletion+0x5d 8336baec 8caa9f02 8caac1a0 881b71c0 00000000 TDI!TdiNotifyPnpClientList+0x132 8336bb10 8caaa314 880819e0 00000000 8ae1f338 TDI!TdiExecuteRequest+0x176 8336bb48 8caaa567 001b71c0 0000000c 8336bbd4 TDI!TdiHandleSerializedRequest+0x1b2 8336bb58 8ae17978 881b71c0 00000010 8336bc98 TDI!TdiDeregisterNetAddress+0xf 8336bbd4 8ae17d7f 8779da18 00000000 879eadf0 tdx!TdxProcessAddressChangeRoutine+0x22e 8336bbf0 825ba031 00000000 8336bc98 8336bca0 tdx!TdxNaAddressChangeEvent+0x7d 8336bc58 82621342 8336bc8c 81a0f0b0 88213540 NETIO!NsiParameterChange+0x73 8336bcf8 82621113 88259fd8 857c602c 8336bd2c tcpip!IppNotifyAddressChangeAtPassive+0x12c 8336bd08 825b5996 88259fd8 81b4013c 85623240 tcpip!IppCompartmentNotificationWorker+0x11 8336bd2c 81c5a245 85623240 857c602c 857c6698 NETIO!NetiopIoWorkItemRoutine+0x2f 8336bd44 81a7641d 857c6698 00000000 84889020 nt!IopProcessWorkItem+0x2d 8336bd7c 81c13a1c 857c6698 208eef98 00000000 nt!ExpWorkerThread+0xfd 8336bdc0 81a6ca3e 81a76320 00000001 00000000 nt!PspSystemThreadStartup+0x9d 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16 STACK_COMMAND:  kb FOLLOWUP_IP: smb!SmbBatchedSetBindingInfo+de 8db324c2 8b08            mov     ecx,dword ptr [eax] SYMBOL_STACK_INDEX:  1 SYMBOL_NAME:  smb!SmbBatchedSetBindingInfo+de FOLLOWUP_NAME:  MachineOwner MODULE_NAME: smb IMAGE_NAME:  smb.sys DEBUG_FLR_IMAGE_TIMESTAMP:  479190cf FAILURE_BUCKET_ID:  0xD1_smb!SmbBatchedSetBindingInfo+de BUCKET_ID:  0xD1_smb!SmbBatchedSetBindingInfo+de Followup: MachineOwner

******************************************************************************* *                                                                             * *                        Bugcheck Analysis                                    * *                                                                             * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) 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 a kernel debugger is available get the stack backtrace. Arguments: Arg1: 1625013b, memory referenced Arg2: 00000002, IRQL Arg3: 00000001, bitfield :    bit 0 : value 0 = read operation, 1 = write operation    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: 81a42a02, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: GetPointerFromAddress: unable to read from 81b3b868 Unable to read MiSystemVaType memory at 81b1b420 1625013b CURRENT_IRQL:  2 FAULTING_IP: nt!CcMoveVacbToReuseTail+8 81a42a02 890a            mov     dword ptr [edx],ecx CUSTOMER_CRASH_COUNT:  1 DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT BUGCHECK_STR:  0xA PROCESS_NAME:  setup.exe TRAP_FRAME:  9460f948 -- (.trap 0xffffffff9460f948) ErrCode = 00000002 eax=a9e459c3 ebx=00001000 ecx=857be2fa edx=1625013b esi=a9e459b3 edi=87acfc08 eip=81a42a02 esp=9460f9bc ebp=9460f9e4 iopl=0         nv up ei ng nz na pe nc cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010286 nt!CcMoveVacbToReuseTail+0x8: 81a42a02 890a            mov     dword ptr [edx],ecx  ds:0023:1625013b=???????? Resetting default scope LAST_CONTROL_TRANSFER:  from 81a42a02 to 81a5ed84 STACK_TEXT:  9460f948 81a42a02 badb0d00 1625013b 803d1000 nt!KiTrap0E+0x2ac 9460f9b8 81a4867f 87acfc08 9460fab0 00000000 nt!CcMoveVacbToReuseTail+0x8 9460f9e4 81a4d916 00001000 00000000 9460fa4c nt!CcGetVirtualAddress+0x120 9460fa6c 81c2d648 86508218 9460fab0 00003000 nt!CcPinFileData+0x90 9460fae4 81bee6d2 86508218 00000000 00003000 nt!CcPinMappedData+0xce 9460fb44 81bede4d 8f2d7c50 9da19000 8bc07780 nt!CmpPinView+0x43 9460fb70 81bee1bf 8bc07780 00000000 00000020 nt!HvMarkDirty+0x102 9460fbac 81bed097 8bc07780 00f2d22c 00000060 nt!HvMarkDirty+0x472 9460fbd4 81bec555 00f2d230 00000000 9a086b06 nt!HvMarkCellDirty+0x22b 9460fc80 81becc74 a02388d0 9460fcf8 00000001 nt!CmSetValueKey+0x850 9460fd44 81a5ba7a 0000015a 0012d930 00000000 nt!NtSetValueKey+0x30a 9460fd44 77ce9a94 0000015a 0012d930 00000000 nt!KiFastCallEntry+0x12a WARNING: Frame IP not in any known module. Following frames may be wrong. 0012d8fc 00000000 00000000 00000000 00000000 0x77ce9a94 STACK_COMMAND:  kb FOLLOWUP_IP: nt!CcMoveVacbToReuseTail+8 81a42a02 890a            mov     dword ptr [edx],ecx SYMBOL_STACK_INDEX:  1 SYMBOL_NAME:  nt!CcMoveVacbToReuseTail+8 FOLLOWUP_NAME:  MachineOwner MODULE_NAME: nt IMAGE_NAME:  ntkrpamp.exe DEBUG_FLR_IMAGE_TIMESTAMP:  47918b12 FAILURE_BUCKET_ID:  0xA_nt!CcMoveVacbToReuseTail+8 BUCKET_ID:  0xA_nt!CcMoveVacbToReuseTail+8 Followup: MachineOwner

******************************************************************************* *                                                                             * *                        Bugcheck Analysis                                    * *                                                                             * ******************************************************************************* 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: bd9c14d4, memory referenced. Arg2: 00000000, value 0 = read operation, 1 = write operation. Arg3: 805aa76b, If non-zero, the instruction address which referenced the bad memory    address. Arg4: 00000002, (reserved) Debugging Details: ------------------ Could not read faulting driver name READ_ADDRESS: GetPointerFromAddress: unable to read from 81b6a868 Unable to read MiSystemVaType memory at 81b4a420 bd9c14d4 FAULTING_IP: fltmgr!FltpPerformPreCallbacks+247 805aa76b 8b4804          mov     ecx,dword ptr [eax+4] MM_INTERNAL_CODE:  2 CUSTOMER_CRASH_COUNT:  3 DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT BUGCHECK_STR:  0x50 PROCESS_NAME:  chrome.exe CURRENT_IRQL:  0 TRAP_FRAME:  a0206740 -- (.trap 0xffffffffa0206740) ErrCode = 00000000 eax=bd9c14d0 ebx=85372b80 ecx=92a93c98 edx=00000000 esi=93922008 edi=9392235c eip=805aa76b esp=a02067b4 ebp=a02067fc iopl=0         nv up ei ng nz na po nc cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010282 fltmgr!FltpPerformPreCallbacks+0x247: 805aa76b 8b4804          mov     ecx,dword ptr [eax+4] ds:0023:bd9c14d4=???????? Resetting default scope LAST_CONTROL_TRANSFER:  from 81a8dbb4 to 81ad8155 STACK_TEXT:  a0206728 81a8dbb4 00000000 bd9c14d4 00000000 nt!MmAccessFault+0x10a a0206728 805aa76b 00000000 bd9c14d4 00000000 nt!KiTrap0E+0xdc a02067fc 805acff8 a020682c 85372be0 00000000 fltmgr!FltpPerformPreCallbacks+0x247 a0206810 805ae7b6 a020682c 00000000 89edc108 fltmgr!FltpPassThroughInternal+0x32 a0206844 805c3772 8819ee00 8e1e4124 00000000 fltmgr!FltPerformSynchronousIo+0xa8 a0206860 8e1cf362 8819ee00 92a93c98 a0206880 fltmgr!FltSetInformationFile+0xc2 WARNING: Stack unwind information not available. Following frames may be wrong. a0206888 8e1d0bec 8e1e4124 0003b984 a02068e8 klif+0x20362 a02068b0 8e1d000c 89edc108 87d392c4 9fd35d58 klif+0x21bec a02068dc 8e1b1e42 87d392c4 00000000 00000001 klif+0x2100c a020690c 805aa0f3 853dae88 a0206930 a7757860 klif+0x2e42 a0206970 805ad090 003dae28 84dedbb7 853dae28 fltmgr!FltpPerformPostCallbacks+0x1f1 a0206984 805ad5c6 853dae28 84deda00 a02069c8 fltmgr!FltpProcessIoCompletion+0x10 a0206994 81a6d0e4 8636aa90 84deda00 853dae28 fltmgr!FltpPassThroughCompletion+0x94 a02069c8 8281b0db 84deda00 a0206a54 a0206a54 nt!IopfCompleteRequest+0x11d a02069e0 828232dd a0206a54 84deda00 00000000 Ntfs!NtfsExtendedCompleteRequest+0x104 a0206a14 828a9e96 a0206a54 84deda00 22a4e09e Ntfs!NtfsCommonCleanupOnNewStack+0x7b a0206ba4 81aef053 86369020 84deda00 84deda00 Ntfs!NtfsFsdCleanup+0x154 a0206bbc 805adba7 8636aa90 84deda00 00000000 nt!IofCallDriver+0x63 a0206be0 805add64 a0206c00 8636aa90 00000000 fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x251 a0206c18 81aef053 8636aa90 84deda00 84deda10 fltmgr!FltpDispatch+0xc2 a0206c30 81c54a41 8529ad90 8488b8c0 00000001 nt!IofCallDriver+0x63 a0206c74 81c50550 8529ad90 943d4ac8 0012019f nt!IopCloseFile+0x387 a0206cc4 81c503e0 8529ad90 0088b8c0 0012019f nt!ObpDecrementHandleCount+0x146 a0206d14 81c505f0 a5b59ea8 a56a54a0 8529ad90 nt!ObpCloseHandleTableEntry+0x234 a0206d44 81c50815 8529ad90 851aea01 851aea01 nt!ObpCloseHandle+0x73 a0206d58 81a8aa7a 00000250 01e7f484 770b9a94 nt!NtClose+0x20 a0206d58 770b9a94 00000250 01e7f484 770b9a94 nt!KiFastCallEntry+0x12a 01e7f484 00000000 00000000 00000000 00000000 0x770b9a94 STACK_COMMAND:  kb FOLLOWUP_IP: klif+20362 8e1cf362 ??              ??? SYMBOL_STACK_INDEX:  6 SYMBOL_NAME:  klif+20362 FOLLOWUP_NAME:  MachineOwner MODULE_NAME: klif IMAGE_NAME:  klif.sys DEBUG_FLR_IMAGE_TIMESTAMP:  4981a5cb FAILURE_BUCKET_ID:  0x50_klif+20362 BUCKET_ID:  0x50_klif+20362 Followup: MachineOwner

******************************************************************************* *                                                                             * *                        Bugcheck Analysis                                    * *                                                                             * ******************************************************************************* NTFS_FILE_SYSTEM (24)     If you see NtfsExceptionFilter on the stack then the 2nd and 3rd     parameters are the exception record and context record. Do a .cxr     on the 3rd parameter and then kb to obtain a more informative stack     trace. Arguments: Arg1: 001904aa Arg2: 8a1cb4e8 Arg3: 8a1cb1e4 Arg4: 81a85bd0 Debugging Details: ------------------ EXCEPTION_RECORD:  8a1cb4e8 -- (.exr 0xffffffff8a1cb4e8) ExceptionAddress: 81a85bd0 (nt!FsRtlLookupPerFileObjectContext+0x00000090)    ExceptionCode: c0000005 (Access violation)   ExceptionFlags: 00000000 NumberParameters: 2    Parameter[0]: 00000000    Parameter[1]: 6e108049 Attempt to read from address 6e108049 CONTEXT:  8a1cb1e4 -- (.cxr 0xffffffff8a1cb1e4) eax=6e108041 ebx=00000000 ecx=8e2e895c edx=8e2e8958 esi=8e2e8978 edi=855ecdc8 eip=81a85bd0 esp=8a1cb5b0 ebp=8a1cb5c0 iopl=0         ov up ei ng nz ac pe cy cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010a97 nt!FsRtlLookupPerFileObjectContext+0x90: 81a85bd0 397808          cmp     dword ptr [eax+8],edi ds:0023:6e108049=???????? Resetting default scope CUSTOMER_CRASH_COUNT:  5 DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT PROCESS_NAME:  chrome.exe CURRENT_IRQL:  1 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_PARAMETER1:  00000000 EXCEPTION_PARAMETER2:  6e108049 READ_ADDRESS: GetPointerFromAddress: unable to read from 81b7e868 Unable to read MiSystemVaType memory at 81b5e420 6e108049 FOLLOWUP_IP: Ntfs!NtfsCopyReadA+188 82881dc0 84c0            test    al,al FAULTING_IP: nt!FsRtlLookupPerFileObjectContext+90 81a85bd0 397808          cmp     dword ptr [eax+8],edi BUGCHECK_STR:  0x24 LAST_CONTROL_TRANSFER:  from 805b3b7f to 81a85bd0 STACK_TEXT:  8a1cb5c0 805b3b7f 00000000 855ecdc8 00000000 nt!FsRtlLookupPerFileObjectContext+0x90 8a1cb5dc 805aec4a 8e2d8b50 8a1cb61c 000000f3 fltmgr!FltpGetStartingCallbackNode+0x3b 8a1cb5fc 805c211c 8a1cb61c 8584eb8c 94b2e0f8 fltmgr!FltpPassThroughFastIo+0x1c 8a1cb63c 82881dc0 8e2d8b50 8584eb8c 00000004 fltmgr!FltpFastIoCheckIfPossible+0x152 8a1cb760 805aeadc 94b2e0f8 0084eb8c 00000004 Ntfs!NtfsCopyReadA+0x188 8a1cb794 805aecab 00000003 00000000 8584eb84 fltmgr!FltpPerformFastIoCall+0x22e 8a1cb7c0 805b0b01 001cb810 00000000 00000000 fltmgr!FltpPassThroughFastIo+0x7d 8a1cb830 8c991284 88546bf8 8e2d8b50 00000000 fltmgr!FltReadFile+0x207 WARNING: Stack unwind information not available. Following frames may be wrong. 8a1cb864 8c991379 8c9a6124 8a1cb8e8 00000004 klif+0x20284 8a1cb888 8c992bec 8c9a6124 0001b258 8a1cb8e8 klif+0x20379 8a1cb8b0 8c99200c 94b2e380 88536ab4 ac8789a0 klif+0x21bec 8a1cb8dc 8c973e42 88536ab4 00000000 00000001 klif+0x2100c 8a1cb90c 805ac0f3 853058a0 8a1cb930 aa122590 klif+0x2e42 8a1cb970 805af090 00305840 8517d82f 85305840 fltmgr!FltpPerformPostCallbacks+0x1f1 8a1cb984 805af5c6 85305840 8517d678 8a1cb9c8 fltmgr!FltpProcessIoCompletion+0x10 8a1cb994 81a810e4 863c0c98 8517d678 85305840 fltmgr!FltpPassThroughCompletion+0x94 8a1cb9c8 828140db 8517d678 8a1cba54 8a1cba54 nt!IopfCompleteRequest+0x11d 8a1cb9e0 8281c2dd 8a1cba54 8517d678 00000000 Ntfs!NtfsExtendedCompleteRequest+0x104 8a1cba14 828a2e96 8a1cba54 8517d678 0898a0c4 Ntfs!NtfsCommonCleanupOnNewStack+0x7b 8a1cbba4 81b03053 86404020 8517d678 8517d678 Ntfs!NtfsFsdCleanup+0x154 8a1cbbbc 805afba7 863c0c98 8517d678 00000000 nt!IofCallDriver+0x63 8a1cbbe0 805afd64 8a1cbc00 863c0c98 00000000 fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x251 8a1cbc18 81b03053 863c0c98 8517d678 8517d688 fltmgr!FltpDispatch+0xc2 8a1cbc30 81c68a41 851b8d90 8488b8c0 00000001 nt!IofCallDriver+0x63 8a1cbc74 81c64550 851b8d90 850217d8 00120196 nt!IopCloseFile+0x387 8a1cbcc4 81c643e0 851b8d90 0088b8c0 00120196 nt!ObpDecrementHandleCount+0x146 8a1cbd14 81c645f0 ad3477a0 af85af40 851b8d90 nt!ObpCloseHandleTableEntry+0x234 8a1cbd44 81c64815 851b8d90 9ae0c801 9ae0c801 nt!ObpCloseHandle+0x73 8a1cbd58 81a9ea7a 000007a0 021cef10 77d69a94 nt!NtClose+0x20 8a1cbd58 77d69a94 000007a0 021cef10 77d69a94 nt!KiFastCallEntry+0x12a 021cef10 00000000 00000000 00000000 00000000 0x77d69a94 SYMBOL_STACK_INDEX:  4 SYMBOL_NAME:  Ntfs!NtfsCopyReadA+188 FOLLOWUP_NAME:  MachineOwner MODULE_NAME: Ntfs IMAGE_NAME:  Ntfs.sys DEBUG_FLR_IMAGE_TIMESTAMP:  47918a96 STACK_COMMAND:  .cxr 0xffffffff8a1cb1e4 ; kb FAILURE_BUCKET_ID:  0x24_Ntfs!NtfsCopyReadA+188 BUCKET_ID:  0x24_Ntfs!NtfsCopyReadA+188 Followup: MachineOwner

[Tomorrow]

Ühenda kõik peale hädavajaliku lahti(Jäta üks RAM pulk esimesse def slotti,ühenda kõik peale OS ketta lahti,ühenda lahti DVD kirjutaja jms USB jubinad v.a klaver ja hiir.Samuti helikaart jne) ja vaata kas probleem püsib

[RassK]

Jätan ta ööseks mälu testima siiski ja siis nädalapärast näis mis too teeb. Lihtsalt nädalasees ei ole arvuti lähiduses...

[R A T]

Mina panen oma raha toiteploki peale.
See on minuarust kõige levinum probleem. Vigaseid mälusid ma isiklikult ei olegi vist leidnud kunagi testimise käigus :S
Samas vaata kindlasti ka emaplaadil olevaid kondekaid, kas on punnis või mitte (sama keiss toitekal).

"ControlPanel->AdministrativeTools->EventViewer" vaata ka läbi.

[RassK]

BSOD'd ronivad ka suvalistel hetkedel, mitte ei saa aru mille peale näiteks vms.
Mõnikord jõuan winni ja üritan avada midagi siis saan hetkega BSOD, teinekord ei juhtu midagi mitu tundi...

Emaplaadil tunduvad kõik konded korralikud olema, PSU omi ei tea. Warranty kleeps on peal, ei tea kas tasub maha võtta?
Ma ei tea ka kaua tal see garantii on...

Vahepeal lasin orthost ja CCC'ga videokaardi auto tune't et saavutada nii 100% load mälule, CPU'le ja graafikale korraga. Mitte midagi imelikku silma ei hakanud...
Oleks vaid korralikum GFX stresser... AtiTool ei tööta

[Tomorrow]

[R A T]

Tee siiski ka scandisk ja peale seda vaata event viewerist scandiski tulemusi (see vist on application logide all).

[RassK]

Nii, hoidsin arvuti siis terve nädala vooluvõrgust väljas (voolukaabel ka lahti ühendatud)

Eile olin kokku ~2h ja täna ~10h ... ning nüüd peale seda jätkub jälle tavapärane anomaalia, ehk siis kummitavad BSOD'd.

OCCT on toredad võimalused kuid millegipärast kasutada ei saa nagu PSU ja GPU test...

R A T, Proovin

Riistvara testimisvõimalused on ka piiratud, seega uut ei tahaks lampi osta... eriti praegusel ajal.

Computer Management alt võttes Disk Management ütleb et ketas ja parti.'d on terved...
Event viewer'is summary of administrative eventsi all olevaid asju vaadeldes 24h lõikes:
Erroreid 10
Hoiatusi 10
Audit failure 6

On see ebanormaalne nähtus?

Edit: Ja need arvud suurenevad endiselt ...

[Ollaz]

[RassK]

muud erilist ei ole kui sellised:
1)Unable to initialize the security package Kerberos for server side authentication. The data field contains the error number.
2)The previous system shutdown at 23:17:03 on 29.08.2009 was unexpected.
3)The provider failed while storing notifications from the driver. The Virtual Disk Service should be restarted. hr=80042505
4)Atheros AR5007UG Wireless Network Adapter : Could not find a network adapter.
5)An I/O operation initiated by the Registry failed unrecoverably.The Registry could not flush hive (file): '\SystemRoot\System32\Config\SOFTWARE'.
6)Faulting application ATITool.exe, version 0.26.0.0, time stamp 0x45798368, faulting module ATITool.exe, version 0.26.0.0, time stamp 0x45798368, exception code 0xc0000005, fault offset 0x0011d32a, process id 0x115c, application start time 0x01ca242cc592633b.
7)Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface. hr = 0x80070005. This is often caused by incorrect security settings in either the writer or requestor process.

Operation:
Gathering Writer Data

Context:
Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Name: System Writer
Writer Instance ID: {4e6c5fa1-8ba0-43ba-bf51-15ed24c8ad9d}

Ülejäänud on identsed...

[Ollaz]

Proovi maha võtta WLAN draiverid ja ATitool kinni panna. Kõige rohkem võib seda põhjustada antud Atherose draiverid.. endal ei saa veebikat usb-st välja võtta, nii kui tagasi torkan virutab BSODi ette kohe.

[RassK]

AtiToolis asi olla ei saa nagunii, sest see sai pandud alles peale seda kui jama oli ammu juba majas.
Üldse Format peaks need mõlemad vead välistama.

Panin Biosest mäludele seekord paika 2.0v ennem oli Auto (kuigi mitmeid kuid ometi töötas ?! )
Tulemuseks on vähem BSOD'sid päevas...

Edit: tulemus ei andnud siiski veel tulemust kõik on endine. Katkusin seekord kõik tagant, eks nüüd näis mis saab ...

Edit: Plate vist perses... mälu kanalitega mingi jama (mälu muude kanalisse panemisel ei tule postki ette -.- esimene kanal peab täidetud olema, muidu tööle ei hakka )

[tahanteada]

Muide - paljudel emaplaadi tüüpidel peab esimene mälupesa täidetud olema, muidu emaplaat ei tööta.

Nii, et võta Manuaal näppu ja loe sellest, et mis järjekorras mälupesad täidetud peavad olema.

Aga kui Sa senini toidet kontrollinud pole - suures kartuses toiteplokkide ees , siis jäädki aega raiskama ja nii mälusid kui emaplaati peksma. Ning toiteplokk naerab seda vaadates pealt - et peksa aga peksa, peaasi, et Sa mind torkima ei tule.

[RassK]

Selle plate puhul peaks ükstapuha olema.

Hetkel bootis isegi üles kanalis nr 2 eile ei jõudnud postinigi

Pealegi mul pole võtta kusagilt teist toidet. Uut osta mitte kuidagi hetkel ei jõua... Garantii kleepsu eemaldada pole mõtet, sest avastasin et toitel veel 1a garantiid