BSOD mi začaly asi před měsícem a od té doby jsem zvládl 7x přeinstalovat systém a dvakrát reklamovat notebook. Mám vyměněnou základní desku a v servisu mi řekli, že to není hardwarová chyba, ale BSOD se objevují hned po reinstalaci systému (po updatování windows a nainstalování driverů). Blbé na tom je, že se objevují náhodně nebo při bootování systému.
Tady je log z posledního BSOD
Kód: Vybrat vše
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\FOREX\Desktop\072310-22354-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0x8281d000 PsLoadedModuleList = 0x82965810
Debug session time: Fri Jul 23 18:48:20.123 2010 (UTC + 2:00)
System Uptime: 0 days 0:00:21.902
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 82e1dabe, 8c0d8814, 0}
Probably caused by : fileinfo.sys ( fileinfo!FIStreamGetInfo+109 )
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: 82e1dabe, The address that the exception occurred at
Arg3: 8c0d8814, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
fltmgr!NameCacheListInsert+6
82e1dabe 8b750c mov esi,dword ptr [ebp+0Ch]
TRAP_FRAME: 8c0d8814 -- (.trap 0xffffffff8c0d8814)
ErrCode = 00000000
eax=0000057b ebx=00000380 ecx=8581e770 edx=89715008 esi=85ad1648 edi=898063f8
eip=82e1dabe esp=8c0d8888 ebp=8c0d888c iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
fltmgr!NameCacheListInsert+0x6:
82e1dabe 8b750c mov esi,dword ptr [ebp+0Ch] ss:0010:8c0d8898=89715048
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: services.exe
CURRENT_IRQL: 1
LAST_CONTROL_TRANSFER: from 82e08c2d to 82e1dabe
STACK_TEXT:
8c0d888c 82e08c2d 89715008 89715048 898063f8 fltmgr!NameCacheListInsert+0x6
8c0d88cc 82e08fa3 00000000 00000000 8c0d8964 fltmgr!FltpGetFileNameInformation+0x42d
8c0d88f4 82fdfc87 0081e6c8 00000401 8c0d8928 fltmgr!FltGetFileNameInformation+0x12b
8c0d8944 82fdfedd 8581e6c8 8c0d8964 00000189 fileinfo!FIStreamGetInfo+0x109
8c0d8980 82e02324 8581e6c8 8c0d89a4 1277dc57 fileinfo!FIPostCreateCallback+0x171
8c0d89e8 82e05512 0081e668 8581e668 1000000c fltmgr!FltpPerformPostCallbacks+0x24a
8c0d89fc 82e05b46 8581e668 89714d40 8c0d8a3c fltmgr!FltpProcessIoCompletion+0x10
8c0d8a0c 82e0629c 8581ecb0 89714d40 8581e668 fltmgr!FltpPassThroughCompletion+0x98
8c0d8a3c 82e198c9 8c0d8a5c 00000000 00000000 fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x33a
8c0d8a88 828594bc 8581ecb0 8581e770 89712854 fltmgr!FltpCreate+0x2db
8c0d8aa0 82a5d66d af5ec796 8c0d8c48 00000000 nt!IofCallDriver+0x63
8c0d8b78 82a3e21f 857ef030 859f58a8 858d9008 nt!IopParseDevice+0xed7
8c0d8bf4 82a6428d 00000000 8c0d8c48 00000040 nt!ObpLookupObjectName+0x4fa
8c0d8c50 82a5c5eb 0026f25c 849f58a8 00000001 nt!ObOpenObjectByName+0x159
8c0d8ccc 82a9762e 0026f2bc 00100021 0026f25c nt!IopCreateFile+0x673
8c0d8d14 8286044a 0026f2bc 00100021 0026f25c nt!NtOpenFile+0x2a
8c0d8d14 776464f4 0026f2bc 00100021 0026f25c nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0026f2c8 00000000 00000000 00000000 00000000 0x776464f4
STACK_COMMAND: kb
FOLLOWUP_IP:
fileinfo!FIStreamGetInfo+109
82fdfc87 85c0 test eax,eax
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: fileinfo!FIStreamGetInfo+109
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: fileinfo
IMAGE_NAME: fileinfo.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc18f
FAILURE_BUCKET_ID: 0x8E_fileinfo!FIStreamGetInfo+109
BUCKET_ID: 0x8E_fileinfo!FIStreamGetInfo+109
Followup: MachineOwner
---------
OS Name Microsoft Windows 7 Ultimate
Version 6.1.7600 Build 7600
System Model HP EliteBook 6930p (FL488AW)
System Type X86-based PC
Processor Intel(R) Core(TM)2 Duo CPU P8600 @ 2.40GHz, 2401 Mhz, 2 Core(s), 2 Logical Processor(s)
BIOS Version/Date Hewlett-Packard 68PCU Ver. F.18, 3/16/2010
SMBIOS Version 2.4
Díky za jakoukoliv pomoc!
Mojmír