iTrooper Opublikowano 25 Października 2014 Zgłoś Opublikowano 25 Października 2014 Witam dzisiaj odpaliłem lapka siedziałem sobie trochę na Fb a tu nagle wyskoczył mi Blue Screen. Jako że mało się na tym znam pomogłem sobie trochę poszukując w Google to i owo, Ściągnąłem program WinDbg i odczytałem plik z błędem. Niby błąd powoduje plik ntkrnlmp.exe ale nie wiem co to jest i co dalej mam zrobić żeby się tego pozbyć i naprawić system. Proszę o pomoc, poniżej wkleiłem kopię z raportu. Microsoft ® Windows Debugger Version 6.11.0001.402 X86 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Trooper\Desktop\102514-19390-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 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.18526.amd64fre.win7sp1_gdr.140706-1506 Machine Name: Kernel base = 0xfffff800`03211000 PsLoadedModuleList = 0xfffff800`03454890 Debug session time: Sat Oct 25 07:35:02.420 2014 (GMT+2) System Uptime: 0 days 0:18:34.763 Loading Kernel Symbols ............................................................... ................................................................ .............................................. Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {80, 2, 1, fffff8000328ff1f} Probably caused by : ntkrnlmp.exe ( nt!KeAcquireInStackQueuedSpinLock+5f ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * 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: 0000000000000080, 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: fffff8000328ff1f, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800034be100 0000000000000080 CURRENT_IRQL: 2 FAULTING_IP: nt!KeAcquireInStackQueuedSpinLock+5f fffff800`0328ff1f 488717 xchg rdx,qword ptr [rdi] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: taskhost.exe TRAP_FRAME: fffff88021517ef0 -- (.trap 0xfffff88021517ef0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000 rdx=fffff88021518100 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8000328ff1f rsp=fffff88021518080 rbp=0000000000000000 r8=fffff88021518100 r9=00000000ffffffff r10=ffffffffffffffff r11=0000000000000011 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na po nc nt!KeAcquireInStackQueuedSpinLock+0x5f: fffff800`0328ff1f 488717 xchg rdx,qword ptr [rdi] ds:0039:00000000`00000000=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80003286169 to fffff80003286bc0 STACK_TEXT: fffff880`21517da8 fffff800`03286169 : 00000000`0000000a 00000000`00000080 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx fffff880`21517db0 fffff800`03284de0 : 00000000`00000000 00000000`00034175 fffffa80`009c45f0 00000000`00000000 : nt!KiBugCheckDispatch+0x69 fffff880`21517ef0 fffff800`0328ff1f : 00000000`00000000 fffff6fb`7da00000 fffffa80`09b8cb30 fffff680`00061000 : nt!KiPageFault+0x260 fffff880`21518080 fffff800`03343c8e : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`09b8cb30 : nt!KeAcquireInStackQueuedSpinLock+0x5f fffff880`215180d0 fffff800`032fd3bc : 14127243`499c8016 fffff680`00061000 fffff680`00061000 000fffff`00000005 : nt!MiReleaseConfirmedPageFileSpace+0x5e fffff880`21518150 fffff800`03273142 : fffffa80`00000001 00000000`00005d2a fffffa80`09b8cb30 fffffa80`09b8cec8 : nt! ?? ::FNODOBFM::`string'+0x3ad16 fffff880`215189e0 fffff800`03285e53 : ffffffff`ffffffff 00000000`2658f178 00000000`2658f170 00000000`00004000 : nt!NtFreeVirtualMemory+0x382 fffff880`21518ae0 00000000`76f7149a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`2658f138 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76f7149a STACK_COMMAND: kb FOLLOWUP_IP: nt!KeAcquireInStackQueuedSpinLock+5f fffff800`0328ff1f 488717 xchg rdx,qword ptr [rdi] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nt!KeAcquireInStackQueuedSpinLock+5f FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 53b9f073 FAILURE_BUCKET_ID: X64_0xA_nt!KeAcquireInStackQueuedSpinLock+5f BUCKET_ID: X64_0xA_nt!KeAcquireInStackQueuedSpinLock+5f Followup: MachineOwner --------- Cytuj Udostępnij tę odpowiedź Odnośnik do odpowiedzi Udostępnij na innych stronach Więcej opcji udostępniania...