Odpowiedz

BSOD: błąd powodowany przez ntoskrnl.exe

 
thermalfake
Ostatni Mohikanin

Liczba postów: 13.580
Post: #4

RE: BSOD ntoskrnl.exe


Jeden zrzut jest uszkodzony, drugi wskazuje na problemy z pamięcią a błąd został zgłoszony przez plik systemowy.

Kod:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C: \Users\user\Desktop\bsody\26\110912-32807-01.dmp]
Mini Kernel Dump File:  Only registers and stack trace are available

Symbol search path is:  symsrv*symsrv.dll*c: \symb*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.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800`03049000 PsLoadedModuleList = 0xfffff800`0328d670
Debug session time:  Thu Nov  8 23: 20: 44.255 2012 (UTC + 1: 00)
System Uptime:  0 days 2: 46: 02.894
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C1, {fffff9806b66af00, fffff9806b66a247, b3c100, 23}

Unable to load image avgmfx64.sys, Win32 error 0n2
*** WARNING:  Unable to verify timestamp for avgmfx64.sys
*** ERROR:  Module load completed but symbols could not be loaded for avgmfx64.sys
Probably caused by :  luafv.sys ( luafv!LuafvNormalizeNameComponentEx+162 )

Followup:  MachineOwner
---------

1:  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:  fffff9806b66af00, address trying to free
Arg2:  fffff9806b66a247, address where bits are corrupted
Arg3:  0000000000b3c100, (reserved)
Arg4:  0000000000000023, 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:   mscorsvw.exe

CURRENT_IRQL:   0

LAST_CONTROL_TRANSFER:   from fffff8000314e36a to fffff800030c7fc0

STACK_TEXT:  
fffff880`092d9918 fffff800`0314e36a :  00000000`000000c1 fffff980`6b66af00 fffff980`6b66a247 00000000`00b3c100 :  nt!KeBugCheckEx
fffff880`092d9920 fffff800`031c6fb3 :  00000000`00000006 fffff800`03182c8b fffff980`03e94af0 fffffa80`07d94ee0 :  nt!MiCheckSpecialPoolSlop+0x9a
fffff880`092d9960 fffff800`031f2975 :  fffff800`03049000 00000000`6d4e6f49 00000000`000f6078 fffffa80`05a80030 :  nt!MmFreeSpecialPool+0x1d3
fffff880`092d9aa0 fffff800`033bff78 :  fffff980`4ae0af20 00000000`00000001 fffffa80`05a80030 fffff980`051d8fa0 :  nt!ExDeferredFreePool+0xf6d
fffff880`092d9b50 fffff800`030d11d4 :  fffff980`000c4b30 fffff980`25480b30 fffff980`005ccf30 fffff980`00272f90 :  nt!IopDeleteFile+0x168
fffff880`092d9be0 fffff800`033baae4 :  fffff980`25480b30 00000000`00000000 fffff980`4dfd0b50 00000000`00000000 :  nt!ObfDereferenceObject+0xd4
fffff880`092d9c40 fffff800`033bb094 :  00000000`00002144 fffff980`25480b30 fffff980`00272f90 00000000`00002144 :  nt!ObpCloseHandleTableEntry+0xc4
fffff880`092d9cd0 fffff800`030c7253 :  fffff980`4dfd0b50 fffff880`092d9da0 00000000`00000020 00000000`00000000 :  nt!ObpCloseHandle+0x94
fffff880`092d9d20 fffff800`030c3810 :  fffff880`05f56d8e 00000000`00000000 00000000`00000000 00000000`00000020 :  nt!KiSystemServiceCopyEnd+0x13
fffff880`092d9eb8 fffff880`05f56d8e :  00000000`00000000 00000000`00000000 00000000`00000020 fffff800`030a81ba :  nt!KiServiceLinkage
fffff880`092d9ec0 fffff880`00c588c2 :  00000000`0000005b fffffa80`0560bf10 fffff980`4ae0af20 fffff800`0355ff0d :  luafv!LuafvNormalizeNameComponentEx+0x162
fffff880`092d9fc0 fffff880`00c58afe :  00000000`0000fffe fffffa80`0560bf10 00000000`00000000 00000000`00000000 :  fltmgr!FltpCallNormalizeNameComponentHandler+0x82
fffff880`092da020 fffff880`00c59f81 :  00000000`0000006f 00000000`0000006f 00000000`0000005c 00000000`00000000 :  fltmgr!FltpExpandShortNames+0x14e
fffff880`092da080 fffff880`00c59e1e :  fffffa80`0560bf10 00000000`00000000 00000000`00000000 fffffa80`0565f668 :  fltmgr!FltpGetNormalizedFileNameWorker+0xc1
fffff880`092da0c0 fffff880`00c45b9d :  c00000bb`04d1e800 00000000`00000000 fffffa80`07218d90 fffff880`092db000 :  fltmgr!FltpCreateFileNameInformation+0xee
fffff880`092da120 fffff880`00c3fbf6 :  fffffa80`0538f000 fffffa80`072182a0 fffffa80`0565f108 fffff800`030f8696 :  fltmgr!HandleStreamListNotSupported+0x15d
fffff880`092da160 fffff880`00c46b44 :  00000000`00000000 00000000`00000000 fffffa80`072182a0 00000000`00000401 :  fltmgr! ? : FNODOBFM: `string'+0x30f3
fffff880`092da1e0 fffff880`0190e960 :  fffffa80`0560bf10 00000000`00000000 00000000`00000001 00000000`80000000 :  fltmgr!FltGetFileNameInformation+0x184
fffff880`092da270 fffffa80`0560bf10 :  00000000`00000000 00000000`00000001 00000000`80000000 00000000`00000000 :  avgmfx64+0x4960
fffff880`092da278 00000000`00000000 :  00000000`00000001 00000000`80000000 00000000`00000000 fffff800`030f2bcb :  0xfffffa80`0560bf10


STACK_COMMAND:   kb

FOLLOWUP_IP:  
luafv!LuafvNormalizeNameComponentEx+162
fffff880`05f56d8e 4c8d9c24f0000000 lea     r11,[rsp+0F0h]

SYMBOL_STACK_INDEX:   a

SYMBOL_NAME:   luafv!LuafvNormalizeNameComponentEx+162

FOLLOWUP_NAME:   MachineOwner

MODULE_NAME:  luafv

IMAGE_NAME:   luafv.sys

DEBUG_FLR_IMAGE_TIMESTAMP:   4a5bc295

FAILURE_BUCKET_ID:   X64_0xC1_23_VRFK_luafv!LuafvNormalizeNameComponentEx+162

BUCKET_ID:   X64_0xC1_23_VRFK_luafv!LuafvNormalizeNameComponentEx+162

Followup:  MachineOwner
---------

[Obrazek: 2089620800_1406976151.png]

W zamian za pomoc oczekuję poprawnej pisowni. Stop niechlujstwu.
Jak mądrze zadawać pytania? - przejrzyj poradnik na forum.
Nie udzielam porad via PW.

11.11.2012 17:55

Znajdź wszystkie posty użytkownika
Odpowiedz cytując ten post
Odpowiedz


Wiadomości w tym wątku
RE: BSOD ntoskrnl.exe - Kordas - 11.11.2012, 14:32
RE: BSOD ntoskrnl.exe - thermalfake - 11.11.2012 17:55
Podobne wątki
Wątek: Autor Odpowiedzi: Wyświetleń: Ostatni post
BSOD Moloch4 0 924 05.07.2019 11:29
Ostatni post: Moloch4
BSOD Windows 7 luzbluzoner 0 1.437 17.12.2016 20:25
Ostatni post: luzbluzoner
Częsty ekrad BSOD kubajed 0 1.417 03.10.2016 17:46
Ostatni post: kubajed
problem z ntoskrnl.exe Arek101 0 1.666 26.05.2016 20:03
Ostatni post: Arek101
Nowa instalacja, 3 BSOD avocado 0 1.430 20.11.2015 09:46
Ostatni post: avocado
Problem windows, blue screen, ntoskrnl.exe ramzilla 0 1.632 18.10.2015 21:26
Ostatni post: ramzilla
« Starszy wątek | Nowszy wątek »

Temat został oceniony na 0 w skali 1-5 gwiazdek.
Zebrano 1 głosów.