Nakon svakog reseta nakon downloada updatea dobijem BSOD, komp se resetira i sve dalje normalno radi. Ovo je crash dump:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\Mini062309-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18226.x86fre.vistasp1_gdr.090302-1506
Machine Name:
Kernel base = 0x81816000 PsLoadedModuleList = 0x81923930
Debug session time: Tue Jun 23 22:20:37.906 2009 (GMT+2)
System Uptime: 0 days 0:00:26.640
Loading Kernel Symbols
...............................................................
................................................................
Loading User Symbols
Loading unloaded module list
.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {c0000005, 0, 80699530, 8069922c}
Probably caused by : ntkrnlmp.exe ( nt!ObpGetObjectSecurity+86 )
Followup: MachineOwner
---------
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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: 00000000, The address that the exception occurred at
Arg3: 80699530, Exception Record Address
Arg4: 8069922c, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
+16
00000000 ?? ???
EXCEPTION_RECORD: 80699530 -- (.exr 0xffffffff80699530)
ExceptionAddress: 00000000
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 00000000
Attempt to read from address 00000000
CONTEXT: 8069922c -- (.cxr 0xffffffff8069922c)
eax=8069962c ebx=80699654 ecx=868bc034 edx=0000003b esi=868bc000 edi=80699658
eip=00000000 esp=806995f8 ebp=80699634 iopl=0 nv up ei ng nz na po cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00210283
00000000 ?? ???
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1: 00000000
EXCEPTION_PARAMETER2: 00000000
READ_ADDRESS: GetPointerFromAddress: unable to read from 819426d8
Unable to read MiSystemVaType memory at 819232e0
00000000
FOLLOWUP_IP:
nt!ObpGetObjectSecurity+86
81a18163 3d230000c0 cmp eax,0C0000023h
FAILED_INSTRUCTION_ADDRESS:
+673b952f035ddd08
00000000 ?? ???
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from 81a18163 to 00000000
STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
806995f4 81a18163 84562bc0 00000001 8069962c 0x0
80699634 81a4132b 84562bc0 00000100 00000000 nt!ObpGetObjectSecurity+0x86
80699664 81a412b4 84562bc0 00000000 80699688 nt!ObpCheckObjectReference+0x28
80699760 819ad71e 806997b0 00000240 00000000 nt!ObReferenceObjectByName+0x1b3
806997d4 819ad087 806997f8 8191a58c 80699850 nt!IopGetLegacyVetoListDrivers+0x13b
80699808 819ad20f 806998f8 806998fc 00000000 nt!IoGetLegacyVetoList+0x4a
80699834 81968579 00699850 806998f8 80699940 nt!PopFilterCapabilities+0x26
806998a8 819686c6 80699bec 00000000 88815c7c nt!PopVerifyPowerActionPolicy+0x49
806998c8 8196894b 00000000 80699c84 00000000 nt!PopVerifySystemPowerPolicy+0xcb
80699ad0 8195e6e5 00000000 000000e8 00000001 nt!PopApplyPolicy+0x72
80699bf8 81b644d8 8080db90 80810d38 00000000 nt!PopResetCurrentPolicies+0xa0
80699c90 81b674d8 00000001 80810d38 8345aad8 nt!PoInitSystem+0x627
80699d74 81968034 80699dc0 819be6d5 80810d38 nt!Phase1InitializationDiscard+0xc0a
80699d7c 819be6d5 80810d38 30906541 00000000 nt!Phase1Initialization+0xd
80699dc0 818a56de 81968027 80810d38 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!ObpGetObjectSecurity+86
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 49ac8fa8
STACK_COMMAND: .cxr 0xffffffff8069922c ; kb
FAILURE_BUCKET_ID: 0x7E_NULL_IP_nt!ObpGetObjectSecurity+86
BUCKET_ID: 0x7E_NULL_IP_nt!ObpGetObjectSecurity+86
Followup: MachineOwner
---------
Ispričavam se na dužini posta ali... To je Vista SP1 Ultimate. Ima netko ideju što se događa?
