|
Answer» I used SF TOOL for dumps, it is in attachment. Please if someone can help. :huh:
Code: [Select]Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Fri 28.8.2015 12:47:27 GMT your computer crashed crash dump file: C:\Windows\Minidump\082815-17378-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x80640) Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80002E753DE) Error: IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be IDENTIFIED at this time.
On Fri 28.8.2015 12:47:27 GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: clfs.sys (CLFS!ClfsLsnContainer+0x1E49) Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80002E753DE) Error: IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\clfs.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: Common Log File System Driver Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Fri 28.8.2015 12:38:47 GMT your computer crashed crash dump file: C:\Windows\Minidump\082815-18142-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x80640) Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80002E653DE) Error: IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 28.8.2015 12:30:21 GMT your computer crashed crash dump file: C:\Windows\Minidump\082815-18938-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x80640) Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80002E663DE) Error: IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. [attachment deleted by ADMIN to conserve space]Run memtest86 to test system RAM as well as run a Hard Drive test tool on system from drive manufacturer or if windows still runs enough to run drive diagnostic then run CrystalDiskInfo and check to see if your hard drive or SSD is still detected as healthy.Hi, Dave. Thanks for the answer.
memtest86, 5 hours, 4 passes, no errors.
wdc test for western digital, quick and extended, both without errors.
sfc /scannow - did not find integrity violationsMalwarebytes scan - 1 pup open candy warning only HD Tune hdd test - all green sectors/blocks.
Bugcheck ANALYSIS:
Code: [Select]* * * 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: 0000000000000000, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000001, 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: fffff80002e753de, address which referenced memory
Debugging Details:
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030c80e8 GetUlongFromAddress: unable to read from fffff800030c8198 0000000000000000 Nonpaged pool
CURRENT_IRQL: 2
FAULTING_IP: nt!ExDeleteResourceLite+ce fffff800`02e753de 488908 mov qword ptr [rax],rcx
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: svchost.exe
TRAP_FRAME: fffff88008f957d0 -- (.trap 0xfffff88008f957d0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000 rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002e753de rsp=fffff88008f95960 rbp=fffff8a00013f700 r8=fffffa8007318010 r9=fffff880009e8180 r10=fffffa8006d36c70 r11=fffffa80075c3ae0 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei PL zr na po nc nt!ExDeleteResourceLite+0xce: fffff80002e753de 488908 mov qword ptr [rax],rcx ds:0000000000000000=???????????????? Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002e96be9 to fffff80002e97640
STACK_TEXT: fffff88008f95688 fffff80002e96be9 : 000000000000000a 0000000000000000 0000000000000002 0000000000000001 : nt!KeBugCheckEx fffff88008f95690 fffff80002e95860 : 0000000000000000 0000000000000001 fffff88008f95958 fffffa8007caf5c8 : nt!KiBugCheckDispatch+0x69 fffff88008f957d0 fffff80002e753de : fffff8a00013f750 fffff8a00013f6e0 fffffa8007d9eda8 fffff8a00013f698 : nt!KiPageFault+0x260 fffff88008f95960 fffff88000c68e2d : 0000000000000000 fffff8a00013f700 fffffa8007caf530 0000000000000001 : nt!ExDeleteResourceLite+0xce fffff88008f959c0 fffff88000c94a68 : 0000000000000000 fffff88008f95a38 fffffa8007d9ecb0 fffff88000c693c3 : CLFS!CClfsLogCcb::scalar deleting destructor'+0xcd fffff88008f95a00 fffff88000c68157 : fffffa8007caf2c0 000000000000000b fffffa8007caf2c0 fffff88000c69241 : CLFS!CClfsLogCcb::Release+0x20 fffff88008f95a30 fffff88000c67934 : 0000000000000000 0000000000000001 fffffa8007caf2c0 fffffa8007d9ecb0 : CLFS!CClfsRequest::scalar deleting destructor'+0x123 fffff88008f95a60 fffff88000cb0d50 : 0000000000000000 fffff8a00013f700 0000000000000001 fffff8a003865000 : CLFS!CClfsRequest::Release+0x20 fffff88008f95a90 fffff88000ca95be : fffffa8007caf690 0000000000000000 fffff8a0003c7000 fffff80000000400 : CLFS!ClfsReserveAndAppendLogInternal+0x3c4 fffff88008f95ba0 fffff88000ca7d13 : fffff8a00013f700 fffff8a0000a0c00 fffff8a000000006 0000000000000008 : CLFS!CClfsKernelMarshallingContext::AppendWriteBlockToFlushQueue+0x1c2 fffff88008f95ca0 fffff88000cb088f : fffff8a00013f700 0000000000000000 0000000000000007 0000000000000008 : CLFS!CClfsKernelMarshallingContext::ReserveAndAppendLog+0x4d7 fffff88008f95d80 fffff80003126806 : ffffffff00000000 0000000000000000 fffffa8006f3d340 0000000000000001 : CLFS!ClfsReserveAndAppendLogAligned+0x2ab fffff88008f95e10 fffff80003124398 : 0000000000000000 fffff8a0000a0cf0 fffffa8000000007 fffff88008f96008 : nt!TmpWriteLog+0x176 fffff88008f95ec0 fffff8000311d22a : 00000000c0190013 fffffa8006f3d340 fffffa80075a7c30 fffffa80075a7cf8 : nt!TmpLogTransaction+0x810 fffff88008f96080 fffff800031204c4 : 0000000000000000 00000000c0190013 fffffa80075a7c30 fffffa80075a7c00 : nt!TmpTxActionDoCommit+0xda fffff88008f960e0 fffff800031254d7 : fffffa80075a7c30 fffffa8006f3d340 0000000000000004 0000000000000000 : nt!TmCommitEnlistment+0x100 fffff88008f96120 fffff800031258c2 : 0000000000000000 0000000000000000 0000000000000003 0000000000000000 : nt!TmpInternalCrmNotification+0x15b fffff88008f961a0 fffff80003123acd : 0000000000000003 fffffa8006f3d340 fffff80002fd21d0 0000000000000000 : nt!TmpSetNotificationResourceManager+0xf2 fffff88008f96220 fffff8000311d2c5 : 0000000000000005 0000000000000004 fffffa80072ab101 fffffa80072ab1c0 : nt!TmpNotifyAllEnlistmentsTransaction+0x19d fffff88008f962a0 fffff800031203bc : fffffa80072ab1c0 0000000000000000 0000000000000000 fffffa80072ab1c0 : nt!TmpTxActionDoCommit+0x175 fffff88008f96300 fffff80003126e6d : fffffa80075b71e0 0000000000000001 0000000000000000 fffff8a003536300 : nt!TmpTxActionDoPrepareComplete+0xa0 fffff88008f96350 fffff800031250fa : fffffa80075b71e0 0000000000000000 0000000000000000 0000000000000000 : nt!TmpProcessNotificationResponse+0x12d fffff88008f963c0 fffff8000311f34d : 0000000000000000 fffff8a003536370 0000000000000000 0000000000000002 : nt!TmPrepareComplete+0x5e fffff88008f96420 fffff800031258c2 : fffff88008f96700 0000000000000002 0000000000000002 fffffa80072ab288 : nt!CmKtmNotification+0x461 fffff88008f964f0 fffff80003123acd : 0000000000000002 fffffa80075b71e0 fffff80002fd21d0 fffff8a003536370 : nt!TmpSetNotificationResourceManager+0xf2 fffff88008f96570 fffff80003122268 : 0000000000000002 fffff88000000002 0000000000000001 fffffa80072ab1c0 : nt!TmpNotifyAllEnlistmentsTransaction+0x19d fffff88008f965f0 fffff8000311dd6f : fffffa80072ab1c0 fffff88008f96734 0000000000000001 fffffa80072ab1c0 : nt!TmpTxActionDoPrepare+0x84 fffff88008f96630 fffff80003126e6d : fffffa8000000000 0000000000000000 0000000000000000 0000000000000000 : nt!TmpTxActionDoPrePrepareComplete+0x67 fffff88008f96680 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!TmpProcessNotificationResponse+0x12d
STACK_COMMAND: kb
FOLLOWUP_IP: CLFS!CClfsLogCcb::scalar deleting destructor'+cd fffff88000c68e2d ff05a96b0100 inc dword ptr [CLFS!CClfsLogCcb::m_laList+0x1c (fffff880`00c7f9dc)]
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: CLFS!CClfsLogCcb::`scalar deleting destructor'+cd
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: CLFS
IMAGE_NAME: CLFS.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc11d
FAILURE_BUCKET_ID: X64_0xA_CLFS!CClfsLogCcb::_scalar_deleting_destructor_+cd
BUCKET_ID: X64_0xA_CLFS!CClfsLogCcb::_scalar_deleting_destructor_+cd
Followup: MachineOwner
|