BSOD - różne opisy błędu, prośba o analizę dump

Wszelkie problemy komputerowe, których nie można jednoznacznie sklasyfikować do wybranego działu
bgana

Użytkownik
Posty: 20
Rejestracja: 31 paź 2011, 22:32

BSOD - różne opisy błędu, prośba o analizę dump

Post01 lis 2011, 10:43

Witam, mam męczący problem z BSOD. Komputer jest półroczny, Asus P8H67-M Pro, Intel i-3, 2x2GB DDR3, Radeon 2600, Windows 7 64-bit. BS wyskakuje regularnie, kilka razy dziennie, ale niestety nie znalazłem żadnej prawidłowości jego przyczyny. Czasem wywala podczas przeglądania, czasem podczas gry, a czasem przy logowaniu się do Windowsa... Przeważnie tuż przed BSOD ekran zastyga, mysz przestaje działać, a potem na chwilę ekran pełen jest pikseli i zaraz pokazuje się BSOD.

Co zrobiłem do tej pory:
1. Oczywiście sprawdziłem RAM. Kości razem, osobno, w różnych slotach - memtest nie wykrył błędu.
2. Dysk przetestowałem MHDD oraz SeaTools. Testy nie wykazały żadnych problemów.
3. Obciążałem kartę graficzną Furmarkiem, żeby sprawdzić czy coś z nią się nie dzieje (to jedyny starszy element kompa) - bez żadnych zwisów.
4. Format i czysta instalacja Windowsa - zawiesza się tak samo jak przed reinstalacją. Podobnie brak zmiany bez/z Service Pack 1.
5. Sterowniki - wgrałem stare, otrzymane z płytą i wieszał się. Zaktualizowałem je na najnowsze i wiesza się...

Kończą mi się pomysły. Zasilacz mam porządny, Chiefteca. W programach pokazuje napięcie w normie, chociaż bliżej górnej granicy. Organizuję miernik żeby go sprawdzić.

Załączam dumpy, bo nie potrafię ich analizować. Kolekcja z wczoraj i dziś - dość różne przyczyny z tego co widzę, więc załączam kilka. Z góry dzięki za pomoc. :)

Kod: Zaznacz cały

Loading Dump File [C:\Windows\Minidump\103111-30014-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02658000 PsLoadedModuleList = 0xfffff800`02895e50
Debug session time: Mon Oct 31 14:03:23.229 2011 (GMT+1)
System Uptime: 0 days 0:26:20.525
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
.............................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff88002f8a300, 0, 0}

Unable to load image \SystemRoot\system32\DRIVERS\Rt64win7.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
Probably caused by : NETIO.SYS ( NETIO!NetioAllocateAndReferenceCopyNetBufferListEx+3f )

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

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88002f8a300, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo

FAULTING_IP:
+0
fffff880`02f8a300 28b2f80280f8    sub     byte ptr [rdx-77FFD08h],dh

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800029000e0
 0000000000000000

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  System

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff88002f8b228 -- (.exr 0xfffff88002f8b228)
ExceptionAddress: fffff800027fc90d (nt!ExAllocatePoolWithTag+0x000000000000053d)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff88002f8b2d0 -- (.trap 0xfffff88002f8b2d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00fffffa80065f6e rbx=0000000000000000 rcx=fffffa8006b5f2f1
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800027fc90d rsp=fffff88002f8b460 rbp=fffff80002857880
 r8=0000000000000000  r9=fffff80002857bc0 r10=fffff80002857888
r11=fffff88002f8b658 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!ExAllocatePoolWithTag+0x53d:
fffff800`027fc90d 48895808        mov     qword ptr [rax+8],rbx ds:00fffffa`80065f76=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000275ab2b to fffff800026c9f00

STACK_TEXT: 
fffff880`02f8a248 fffff800`0275ab2b : 00000000`0000001e ffffffff`c0000005 fffff880`02f8a300 00000000`00000000 : nt!KeBugCheckEx
fffff880`02f8a250 fffff800`0271d390 : fffffa80`061cd001 fffffa80`059d18c0 fffffa80`0446f980 00000000`00000001 : nt!KipFatalFilter+0x1b
fffff880`02f8a290 fffff800`026f84dc : fffffa80`0446f9f4 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x95d
fffff880`02f8a2d0 fffff800`026efbed : fffff800`02810470 fffff880`02f8c280 00000000`00000000 fffff800`02658000 : nt!_C_specific_handler+0x8c
fffff880`02f8a340 fffff800`026f7250 : fffff800`02810470 fffff880`02f8a3b8 fffff880`02f8b228 fffff800`02658000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02f8a370 fffff800`027041b5 : fffff880`02f8b228 fffff880`02f8aa80 fffff880`00000000 00000000`00000005 : nt!RtlDispatchException+0x410
fffff880`02f8aa50 fffff800`026c9542 : fffff880`02f8b228 fffff800`02857bc0 fffff880`02f8b2d0 00000000`00001000 : nt!KiDispatchException+0x135
fffff880`02f8b0f0 fffff800`026c7e4a : fffffa80`058ee010 fffffa80`040f8910 fffffa80`053c8010 fffff880`02f8b340 : nt!KiExceptionDispatch+0xc2
fffff880`02f8b2d0 fffff800`027fc90d : 00000000`00000001 00000000`00000001 00000000`00000003 00000000`0214d318 : nt!KiGeneralProtectionFault+0x10a
fffff880`02f8b460 fffff800`026a9a4a : 00000000`00000000 00000000`00000000 00000000`6e6e6e4e 00000000`00000000 : nt!ExAllocatePoolWithTag+0x53d
fffff880`02f8b550 fffff880`014a961e : 00000000`00000000 fffffa80`04a9acd0 fffffa80`05813200 fffff880`015972cf : nt!ExAllocatePoolWithTagPriority+0x4a
fffff880`02f8b5e0 fffff880`014a95af : 00000000`000005b4 00000000`00000000 fffffa80`04296c20 fffff880`014a398a : ndis!ndisAllocateFromNPagedPool+0x1e
fffff880`02f8b610 fffff880`0159f56f : fffffa80`04296af0 00000000`00000000 fffffa80`04296af0 00000000`00000000 : ndis!NdisAllocateNetBufferAndNetBufferList

+0x293
fffff880`02f8b660 fffff880`016037b3 : 00000000`000005b4 00000000`00000000 fffff880`02f8b7f0 fffffa80`0497adf0 : NETIO!

NetioAllocateAndReferenceCopyNetBufferListEx+0x3f
fffff880`02f8b6c0 fffff880`01732143 : 00000000`2163b255 fffff880`0162ce01 fffffa80`053c8010 fffffa80`053c8010 : tcpip!TcpCovetNetBufferList+0xa3
fffff880`02f8b790 fffff880`016bc0f7 : 00000000`000005b4 00000000`00001c84 fffffa80`04296af0 fffffa80`0612e030 : tcpip!TcpInspectReceive+0x33
fffff880`02f8b7e0 fffff880`01675b94 : 00000000`00000001 fffff880`04cda773 fffffa80`04597630 fffff880`04cddd0b : tcpip! ?? ::FNODOBFM::`string'+0x3f336
fffff880`02f8b990 fffff880`0167a0ca : fffffa80`04cbdf00 fffffa80`04cae800 fffffa80`04b6c301 00000000`00000000 : tcpip!TcpTcbReceive+0x694
fffff880`02f8bb40 fffff880`01679c17 : fffff880`02497122 fffffa80`04cc3000 00000000`00000000 fffff880`0165d300 : tcpip!TcpMatchReceive+0x1fa
fffff880`02f8bc90 fffff880`0165c3c7 : fffffa80`04cc3000 fffffa80`04cc2e30 fffffa80`04cb5000 00000000`00000000 : tcpip!TcpPreValidatedReceive+0x177
fffff880`02f8bd40 fffff880`0165c499 : fffff880`02f8bec0 fffff880`0176c9a0 fffff880`02f8bed0 fffff880`00000358 : tcpip!IppDeliverListToProtocol+0x97
fffff880`02f8be00 fffff880`0165c990 : fffffa80`04cc3000 fffffa80`064a9be0 fffffa80`047fea18 fffff880`02f8bec0 : tcpip!IppProcessDeliverList+0x59
fffff880`02f8be70 fffff880`0165b821 : 00000000`00000000 fffffa80`04cc3000 fffff880`0176c9a0 00000000`061b4001 : tcpip!IppReceiveHeaderBatch+0x231
fffff880`02f8bf50 fffff880`0165a272 : fffffa80`05ded510 00000000`00000000 fffffa80`061b4001 00000000`00000001 : tcpip!IpFlcReceivePackets+0x651
fffff880`02f8c150 fffff880`016736ba : fffffa80`061b4010 fffff880`02f8c280 fffffa80`061b4010 00000000`00000000 : tcpip!

FlpReceiveNonPreValidatedNetBufferListChain+0x2b2
fffff880`02f8c230 fffff800`026d964a : fffffa80`04a9acd0 fffff880`02f87000 00000000`00004800 00000000`00000000 : tcpip!

FlReceiveNetBufferListChainCalloutRoutine+0xda
fffff880`02f8c280 fffff880`016730e2 : fffff880`016735e0 fffff880`02f8c390 00000000`00000002 fffffa80`04b80dc0 : nt!KeExpandKernelStackAndCalloutEx+0xda
fffff880`02f8c360 fffff880`0155f0eb : fffffa80`062318d0 00000000`00000000 fffffa80`050851a0 00000000`00000000 : tcpip!FlReceiveNetBufferListChain+0xb2
fffff880`02f8c3d0 fffff880`01528fc6 : fffff880`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisMIndicateNetBufferListsToOpen+0xdb
fffff880`02f8c440 fffff880`014a2ef1 : fffffa80`050851a0 00000000`00000002 00000000`00000001 fffffa80`05e8e190 : ndis!ndisMDispatchReceiveNetBufferLists+0x1d6
fffff880`02f8c8c0 fffff880`04ced8af : fffffa80`04597000 fffffa80`04a9a8d0 fffffa80`04597610 00000000`00000000 : ndis!NdisMIndicateReceiveNetBufferLists+0xc1
fffff880`02f8c910 fffffa80`04597000 : fffffa80`04a9a8d0 fffffa80`04597610 00000000`00000000 00000000`00000001 : Rt64win7+0x158af
fffff880`02f8c918 fffffa80`04a9a8d0 : fffffa80`04597610 00000000`00000000 00000000`00000001 00000000`00000000 : 0xfffffa80`04597000
fffff880`02f8c920 fffffa80`04597610 : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000000 : 0xfffffa80`04a9a8d0
fffff880`02f8c928 00000000`00000000 : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000001 : 0xfffffa80`04597610


STACK_COMMAND:  kb

FOLLOWUP_IP:
NETIO!NetioAllocateAndReferenceCopyNetBufferListEx+3f
fffff880`0159f56f 4885c0          test    rax,rax

SYMBOL_STACK_INDEX:  d

SYMBOL_NAME:  NETIO!NetioAllocateAndReferenceCopyNetBufferListEx+3f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NETIO

IMAGE_NAME:  NETIO.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc18a

FAILURE_BUCKET_ID:  X64_0x1E_NETIO!NetioAllocateAndReferenceCopyNetBufferListEx+3f

BUCKET_ID:  X64_0x1E_NETIO!NetioAllocateAndReferenceCopyNetBufferListEx+3f

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


Kod: Zaznacz cały

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\103111-42603-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 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c5f000 PsLoadedModuleList = 0xfffff800`02ea4670
Debug session time: Mon Oct 31 18:06:34.532 2011 (GMT+1)
System Uptime: 0 days 0:08:05.921
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002cde8e2, fffff880083a6ca0, 0}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002cde8e2, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff880083a6ca0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo

FAULTING_IP:
nt!SwapContext_PatchXRstor+0
fffff800`02cde8e2 0fae29          xrstor  [rcx]

CONTEXT:  fffff880083a6ca0 -- (.cxr 0xfffff880083a6ca0)
rax=0000000000000005 rbx=fffff88002f65180 rcx=fffff880083a7cc0
rdx=0000000000000000 rsi=fffffa80040d0060 rdi=fffffa8005f85b60
rip=fffff80002cde8e2 rsp=fffff880083a7680 rbp=fffff880083a7c70
 r8=fffff88002f69700  r9=0000000000000000 r10=fffff88002f65180
r11=00000000000f0000 r12=0000000000000000 r13=0000000000000000
r14=fffffa8005f77060 r15=fffff88002f69f40
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
nt!SwapContext_PatchXRstor:
fffff800`02cde8e2 0fae29          xrstor  [rcx]
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x3B

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002cde8e2

STACK_TEXT: 
fffff880`083a7680 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SwapContext_PatchXRstor


CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff80002cde803 - nt!SwapContext_PatchXSave+2
   [ 01:21 ]
    fffff80002cde8e4 - nt!SwapContext_PatchXRstor+2 (+0xe1)
   [ 09:29 ]
    fffff80002cdeaa3 - nt!EnlightenedSwapContext_PatchXSave+2 (+0x1bf)
   [ 01:21 ]
    fffff80002cdeb86 - nt!EnlightenedSwapContext_PatchXRstor+2 (+0xe3)
   [ 09:29 ]
4 errors : !nt (fffff80002cde803-fffff80002cdeb86)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  ONE_BIT_LARGE

STACK_COMMAND:  .cxr 0xfffff880083a6ca0 ; kb

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT_LARGE

BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT_LARGE

Followup: memory_corruption
---------


Kod: Zaznacz cały

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\103111-33680-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 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c67000 PsLoadedModuleList = 0xfffff800`02eac670
Debug session time: Mon Oct 31 22:13:35.634 2011 (GMT+1)
System Uptime: 0 days 1:01:39.649
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffffffffffffff2, 0, fffff80002e12dd3, 0}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+43 )

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

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffffffffffff2, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002e12dd3, If non-zero, the instruction address which referenced the bad memory
   address.
Arg4: 0000000000000000, (reserved)

Debugging Details:
------------------


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f16100
 fffffffffffffff2

FAULTING_IP:
nt!ExFreePoolWithTag+43
fffff800`02e12dd3 418b45f0        mov     eax,dword ptr [r13-10h]

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  devices.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800764b370 -- (.trap 0xfffff8800764b370)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000002
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002e12dd3 rsp=fffff8800764b500 rbp=fffff8a00c14a860
 r8=0000000000000004  r9=0000000000000090 r10=fffff80002c67000
r11=00000000000005dc r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!ExFreePoolWithTag+0x43:
fffff800`02e12dd3 418b45f0        mov     eax,dword ptr [r13-10h] ds:ffffffff`fffffff0=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c8f9fc to fffff80002ce3c40

STACK_TEXT: 
fffff880`0764b208 fffff800`02c8f9fc : 00000000`00000050 ffffffff`fffffff2 00000000`00000000 fffff880`0764b370 : nt!KeBugCheckEx
fffff880`0764b210 fffff800`02ce1d6e : 00000000`00000000 ffffffff`fffffff2 00000000`00000000 fffffa80`05b070f0 : nt! ?? ::FNODOBFM::`string'+0x4611f
fffff880`0764b370 fffff800`02e12dd3 : 00000000`00000000 fffff800`02e6e348 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`0764b500 fffff800`02cc1b39 : fffffa80`066bab30 fffff800`02f9803e fffff8a0`0a959000 00000000`000005d0 : nt!ExFreePoolWithTag+0x43
fffff880`0764b5b0 fffff800`02fac42c : 00000000`00000000 fffff8a0`0c14a860 fffff8a0`0c14a868 00000000`00001f6b : nt!ExDeleteResourceLite+0x199
fffff880`0764b610 fffff800`02cedaf4 : 00000000`00000000 00000000`00000000 00000000`00001f6c fffffa80`03c52f30 : nt!SepTokenDeleteMethod+0x8c
fffff880`0764b640 fffff800`02fb88d6 : 00000000`00001f6c fffff8a0`0e678920 fffff8a0`0e678900 fffffa80`03f5bcb8 : nt!ObfDereferenceObject+0xd4
fffff880`0764b6a0 fffff800`02ff0d88 : fffff8a0`0e678900 fffffa80`03f5bcb8 fffff8a0`0e678920 00000000`000004b0 : nt!AlpcpSecurityDestroyProcedure+0x10e
fffff880`0764b6d0 fffff800`02f867bf : 00000000`00000000 fffff8a0`0e678920 fffffa80`03f5bca8 fffffa80`066bab30 : nt!AlpcpDestroyBlob+0x28
fffff880`0764b700 fffff800`02f86617 : 00000000`00000000 fffff8a0`0ae69040 fffffa80`03f5bca8 00000000`000007ff : nt!AlpcpFlushResourcesPort+0x10b
fffff880`0764b730 fffff800`02f8704c : fffffa80`03f5bb90 00000000`00000001 fffff8a0`0ae69040 00000000`00000000 : nt!AlpcpDoPortCleanup+0x97
fffff880`0764b760 fffff800`02fdb174 : 00000000`00000000 fffffa80`03f5bb60 00000000`00000000 fffff800`02cedafc : nt!AlpcpClosePort+0x44
fffff880`0764b790 fffff800`02fdaf31 : fffff8a0`0ae69040 fffff8a0`00000001 fffff8a0`0ae69040 00000000`00000000 : nt!ObpDecrementHandleCount+0xb4
fffff880`0764b810 fffff800`02f9b344 : 00000000`00000414 fffff8a0`0ae69040 fffff8a0`0990d050 00000000`00000414 : nt!ObpCloseHandleTableEntry+0xb1
fffff880`0764b8a0 fffff800`02f9b244 : 00000000`00000404 00000000`00000000 fffffa80`066bab30 fffff800`02f88471 : nt!ObpCloseHandleProcedure+0x30
fffff880`0764b8e0 fffff800`02f9b8c2 : fffff8a0`08d25001 00000000`00000001 fffffa80`066bab30 00000000`00000001 : nt!ExSweepHandleTable+0x74
fffff880`0764b920 fffff800`02fb9ad2 : fffff8a0`08d25060 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ObKillProcess+0x62
fffff880`0764b960 fffff800`02f9b48c : 00000000`00000000 00000000`00000001 00000000`7efdb000 00000000`00000000 : nt!PspExitThread+0x522
fffff880`0764ba60 fffff800`02ce2ed3 : fffffa80`066bab30 00000000`00000000 fffffa80`06758b60 00000000`00dd2a30 : nt!NtTerminateProcess+0x138
fffff880`0764bae0 00000000`779d15da : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0008e318 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x779d15da


STACK_COMMAND:  kb

FOLLOWUP_IP:
nt!ExFreePoolWithTag+43
fffff800`02e12dd3 418b45f0        mov     eax,dword ptr [r13-10h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!ExFreePoolWithTag+43

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0x50_nt!ExFreePoolWithTag+43

BUCKET_ID:  X64_0x50_nt!ExFreePoolWithTag+43

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


Kod: Zaznacz cały

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\110111-23665-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 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c4b000 PsLoadedModuleList = 0xfffff800`02e90670
Debug session time: Mon Oct 31 23:57:02.720 2011 (GMT+1)
System Uptime: 0 days 0:27:53.735
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002fbe671, fffff880026bd970, 0}

Probably caused by : ntkrnlmp.exe ( nt!ObpWaitForMultipleObjects+186 )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002fbe671, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff880026bd970, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo

FAULTING_IP:
nt!ObpWaitForMultipleObjects+186
fffff800`02fbe671 488b4a20        mov     rcx,qword ptr [rdx+20h]

CONTEXT:  fffff880026bd970 -- (.cxr 0xfffff880026bd970)
rax=000000000000002c rbx=fffff8a003036f70 rcx=fffff80002c4b000
rdx=0000000000000000 rsi=000000000000002d rdi=fffffa8005b0e6e0
rip=fffff80002fbe671 rsp=fffff880026be350 rbp=fffff880026beb60
 r8=0000000000000008  r9=fffff8a00303a000 r10=fffffa8005f88b60
r11=fffffffffffffd80 r12=fffff880026be9c0 r13=fffff8a0024ed7d0
r14=000000000000002c r15=0000000000000040
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
nt!ObpWaitForMultipleObjects+0x186:
fffff800`02fbe671 488b4a20        mov     rcx,qword ptr [rdx+20h] ds:002b:00000000`00000020=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002fbe671

STACK_TEXT: 
fffff880`026be350 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ObpWaitForMultipleObjects+0x186


FOLLOWUP_IP:
nt!ObpWaitForMultipleObjects+186
fffff800`02fbe671 488b4a20        mov     rcx,qword ptr [rdx+20h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!ObpWaitForMultipleObjects+186

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

STACK_COMMAND:  .cxr 0xfffff880026bd970 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nt!ObpWaitForMultipleObjects+186

BUCKET_ID:  X64_0x3B_nt!ObpWaitForMultipleObjects+186

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




Kod: Zaznacz cały

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\110111-19546-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 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c58000 PsLoadedModuleList = 0xfffff800`02e9d670
Debug session time: Tue Nov  1 08:45:05.901 2011 (GMT+1)
System Uptime: 0 days 0:03:51.290
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff88003e5f5d8, fffff88003e5ee30, fffff880012bd555}

Probably caused by : Ntfs.sys ( Ntfs!NtfsFindPrefixHashEntry+22c )

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

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

NTFS_FILE_SYSTEM (24)
    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
    parameters are the exception record and context record. Do a .cxr
    on the 3rd parameter and then kb to obtain a more informative stack
    trace.
Arguments:
Arg1: 00000000001904fb
Arg2: fffff88003e5f5d8
Arg3: fffff88003e5ee30
Arg4: fffff880012bd555

Debugging Details:
------------------


EXCEPTION_RECORD:  fffff88003e5f5d8 -- (.exr 0xfffff88003e5f5d8)
ExceptionAddress: fffff880012bd555 (Ntfs!NtfsFindPrefixHashEntry+0x000000000000022c)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 00000000006a0282
Attempt to read from address 00000000006a0282

CONTEXT:  fffff88003e5ee30 -- (.cxr 0xfffff88003e5ee30)
rax=000000000000006a rbx=fffff8a002e72ee0 rcx=00000000000004c0
rdx=0000000000000001 rsi=fffff8a0002c8bc0 rdi=00000000006a006a
rip=fffff880012bd555 rsp=fffff88003e5f810 rbp=0000000000008140
 r8=0000000029b1d260  r9=0000000000000000 r10=0000000000000004
r11=fffff88003e5f858 r12=fffff8a002efcc48 r13=fffff88002e2f970
r14=0000000000000260 r15=0000000000001260
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
Ntfs!NtfsFindPrefixHashEntry+0x22c:
fffff880`012bd555 0fb78718020000  movzx   eax,word ptr [rdi+218h] ds:002b:00000000`006a0282=????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  egui.exe

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  00000000006a0282

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f07100
 00000000006a0282

FOLLOWUP_IP:
Ntfs!NtfsFindPrefixHashEntry+22c
fffff880`012bd555 0fb78718020000  movzx   eax,word ptr [rdi+218h]

FAULTING_IP:
Ntfs!NtfsFindPrefixHashEntry+22c
fffff880`012bd555 0fb78718020000  movzx   eax,word ptr [rdi+218h]

BUGCHECK_STR:  0x24

LAST_CONTROL_TRANSFER:  from fffff880012bbfd2 to fffff880012bd555

STACK_TEXT: 
fffff880`03e5f810 fffff880`012bbfd2 : fffffa80`04553010 fffffa80`04ed1350 fffff8a0`002c8bc0 00000000`00000701 : Ntfs!NtfsFindPrefixHashEntry+0x22c
fffff880`03e5f940 fffff880`012b9911 : fffffa80`04553010 fffffa80`04f0ebd0 fffff880`03e5fb10 fffff880`03e5fb60 : Ntfs!NtfsFindStartingNode+0x452
fffff880`03e5fa10 fffff880`01222a3d : fffffa80`04553010 fffffa80`04f0ebd0 fffff880`02e2f970 fffffa80`05071b00 : Ntfs!NtfsCommonCreate+0x3e1
fffff880`03e5fbf0 fffff800`02ccc757 : fffff880`02e2f8e0 00000000`00000000 00000000`00705e70 00000000`0211ff24 : Ntfs!NtfsCommonCreateCallout+0x1d
fffff880`03e5fc20 fffff800`02ccc711 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxSwitchKernelStackCallout+0x27
fffff880`02e2f7b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSwitchKernelStackContinue


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  Ntfs!NtfsFindPrefixHashEntry+22c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME:  Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce792f9

STACK_COMMAND:  .cxr 0xfffff88003e5ee30 ; kb

FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsFindPrefixHashEntry+22c

BUCKET_ID:  X64_0x24_Ntfs!NtfsFindPrefixHashEntry+22c

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

Kod: Zaznacz cały

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\110111-28438-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 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c5e000 PsLoadedModuleList = 0xfffff800`02ea3670
Debug session time: Tue Nov  1 10:29:55.490 2011 (GMT+1)
System Uptime: 0 days 0:36:30.505
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {28, 2, 0, fffff80002d21bd0}

Probably caused by : memory_corruption ( nt!MiFindNodeOrParent+0 )

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

0: 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: 0000000000000028, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, 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: fffff80002d21bd0, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f0d100
 0000000000000028

CURRENT_IRQL:  2

FAULTING_IP:
nt!MiFindNodeOrParent+0
fffff800`02d21bd0 48f7412800ffffff test    qword ptr [rcx+28h],0FFFFFFFFFFFFFF00h

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  svchost.exe

TRAP_FRAME:  fffff88003a515c0 -- (.trap 0xfffff88003a515c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002d21bd0 rsp=fffff88003a51758 rbp=0000000000000000
 r8=fffff88003a517a0  r9=0000000000000000 r10=fffffa8006168010
r11=fffffa800614a540 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!MiFindNodeOrParent:
fffff800`02d21bd0 48f7412800ffffff test    qword ptr [rcx+28h],0FFFFFFFFFFFFFF00h ds:00000000`00000028=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002cda1e9 to fffff80002cdac40

STACK_TEXT: 
fffff880`03a51478 fffff800`02cda1e9 : 00000000`0000000a 00000000`00000028 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`03a51480 fffff800`02cd8e60 : 00000000`0000041c fffffa80`00000000 fffff880`03a515d0 fffffa80`06168058 : nt!KiBugCheckDispatch+0x69
fffff880`03a515c0 fffff800`02d21bd0 : fffff800`02d23d67 00000000`00000000 ffffe0ea`6919a3f0 fffff8a0`026a5c70 : nt!KiPageFault+0x260
fffff880`03a51758 fffff800`02d23d67 : 00000000`00000000 ffffe0ea`6919a3f0 fffff8a0`026a5c70 fffffa80`06168050 : nt!MiFindNodeOrParent
fffff880`03a51760 fffff800`02d23e3d : fffff800`02e50e80 fffff800`02cded30 00000000`0000068c 00000000`00000000 : nt!MiLocateAddressInTree+0x17
fffff880`03a51790 fffff800`02d23eb8 : 00000000`00000000 00000000`00000000 fffffa80`05b0ebf8 fffffa80`061680c8 : nt!MiGetSharedProtosAtDpcLevel+0xbd
fffff880`03a517e0 fffff800`02c720cb : 00000000`00000000 fffff800`00000000 00000000`00000600 fffff880`07d0fb30 : nt!MiGetSharedProtos+0x18
fffff880`03a51810 fffff800`02ddbbb0 : 00000000`00000000 fffffa80`06168050 fffff880`03a51b60 fffff880`03a51990 : nt! ?? ::FNODOBFM::`string'+0x938b
fffff880`03a51840 fffff800`02d4f4d5 : fffffa80`05ef57d0 00000003`00000000 fffffa80`06168010 fffffa80`061680c8 : nt!MiEmptyPageAccessLog+0x160
fffff880`03a518b0 fffff800`02ff2221 : fffffa80`06672360 00000000`00000001 fffffa80`06a63670 fffffa80`06a63670 : nt! ?? ::FNODOBFM::`string'+0x3b9a6
fffff880`03a519d0 fffff800`02ff2623 : 00000000`00000000 00000000`002f0000 fffffa80`00000001 00000000`00000401 : nt!MiUnmapViewOfSection+0x1b1
fffff880`03a51a90 fffff800`02cd9ed3 : fffffa80`0612bb60 fffff880`03a51b60 fffffa80`05ef57d0 00000000`0000041c : nt!NtUnmapViewOfSection+0x5f
fffff880`03a51ae0 00000000`76e215ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0135ec28 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76e215ba


STACK_COMMAND:  kb

FOLLOWUP_IP:
nt!MiFindNodeOrParent+0
fffff800`02d21bd0 48f7412800ffffff test    qword ptr [rcx+28h],0FFFFFFFFFFFFFF00h

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiFindNodeOrParent+0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0xA_nt!MiFindNodeOrParent+0

BUCKET_ID:  X64_0xA_nt!MiFindNodeOrParent+0

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

Awatar użytkownika
cosik_ktosik

Administrator
Posty: 21416
Rejestracja: 13 lis 2008, 01:17
Lokalizacja: Szczecin
Kontaktowanie:

BSOD - różne opisy błędu, prośba o analizę dump

Post01 lis 2011, 19:45

No to dziwna sprawa. A napięcia i temperatury sprawdziłeś? Podaj zapisane dzienniki zdarzeń do analizy.
Hotfix
Pozdrawiam, cosik_ktosik :)

bgana

Użytkownik
Posty: 20
Rejestracja: 31 paź 2011, 22:32

BSOD - różne opisy błędu, prośba o analizę dump

Post02 lis 2011, 18:03

Spakowane dzienniki zdarzeń: Dostępne tylko dla zarejestrowanych użytkowników

Co określa CPUTin? Po starcie kompa jest w okolicach 60 stopni, a po pewnym czasie dochodzi do 90. Temperatura na Core 60-65 stopni przy duzym obciążeniu/dłuższej pracy.

Zmierzyłem napięcia:
5V: 5.07V
12V: 12,45V
3,3V: 3,40V

Jeszcze test z HD Tune:

Kod: Zaznacz cały

HD Tune: ST3500413AS Health

ID                               Current  Worst    ThresholdData        Status   
(01) Raw Read Error Rate         115      99       6        97500568    Ok       
(03) Spin Up Time                100      100      0        0           Ok       
(04) Start/Stop Count            100      100      20       472         Ok       
(05) Reallocated Sector Count    100      100      36       0           Ok       
(07) Seek Error Rate             78       60       30       68839347    Ok       
(09) Power On Hours Count        99       99       0        1623        Ok       
(0A) Spin Retry Count            100      100      97       0           Ok       
(0C) Power Cycle Count           100      100      20       444         Ok       
(B7) (unknown attribute)         100      100      0        0           Ok       
(B8) (unknown attribute)         100      100      99       0           Ok       
(BB) (unknown attribute)         100      100      0        0           Ok       
(BC) (unknown attribute)         100      100      0        0           Ok       
(BD) (unknown attribute)         100      100      0        0           Ok       
(BE) Airflow Temperature         64       55       45       622067748   Ok       
(C2) Temperature                 36       45       0        36          Ok       
(C3) Hardware ECC Recovered      51       33       0        97500568    Ok       
(C5) Current Pending Sector      100      100      0        0           Ok       
(C6) Offline Uncorrectable       100      100      0        0           Ok       
(C7) Ultra DMA CRC Error Count   200      200      0        0           Ok       
(F0) Head Flying Hours           100      253      0        2832        Ok       
(F1) (unknown attribute)         100      253      0        1671097724  Ok       
(F2) (unknown attribute)         100      253      0        13903778    Ok       

Power On Time         : 1623
Health Status         : Ok


Linie 0A i B8 podświetlone na żółto. Coś niepokojącego?

Dzisiejszy BS:

Kod: Zaznacz cały

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\110211-25022-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 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c60000 PsLoadedModuleList = 0xfffff800`02ea5670
Debug session time: Wed Nov  2 12:26:45.101 2011 (GMT+1)
System Uptime: 0 days 4:24:19.490
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {22, 2, 0, fffff80002d26427}

Probably caused by : ntkrnlmp.exe ( nt!IoBoostThreadIoPriority+1e7 )

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

0: 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: 0000000000000022, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, 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: fffff80002d26427, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f0f100
 0000000000000022

CURRENT_IRQL:  2

FAULTING_IP:
nt!IoBoostThreadIoPriority+1e7
fffff800`02d26427 418a442422      mov     al,byte ptr [r12+22h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  poqexec.exe

TRAP_FRAME:  fffff8800883a1c0 -- (.trap 0xfffff8800883a1c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8800883a3d0 rbx=0000000000000000 rcx=fffff8800883a3e8
rdx=fffffa8004cd704e rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002d26427 rsp=fffff8800883a350 rbp=0000000000000000
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po cy
nt!IoBoostThreadIoPriority+0x1e7:
fffff800`02d26427 418a442422      mov     al,byte ptr [r12+22h] ds:0010:00000000`00000022=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002cdc1e9 to fffff80002cdcc40

STACK_TEXT: 
fffff880`0883a078 fffff800`02cdc1e9 : 00000000`0000000a 00000000`00000022 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0883a080 fffff800`02cdae60 : fffff980`26f1d800 00000000`0000000f 00000000`00b1d800 00000000`00000001 : nt!KiBugCheckDispatch+0x69
fffff880`0883a1c0 fffff800`02d26427 : 00000000`00000000 fffff880`01306e55 00000000`00000001 fffff980`26f1e800 : nt!KiPageFault+0x260
fffff880`0883a350 fffff800`02cbd799 : fffffa80`06aa5788 fffff880`00000002 fffffa80`06aa5b70 fffff880`0883a3d0 : nt!IoBoostThreadIoPriority+0x1e7
fffff880`0883a500 fffff800`02cbd851 : fffffa80`06aa5760 00000000`00000001 00000000`00000000 fffff800`02e52e80 : nt!ExpCheckForIoPriorityBoost+0x151
fffff880`0883a540 fffff800`02ce2b6c : ffffffff`ffb3b4c0 fffffa80`06aa5788 fffffa80`06aa5760 fffff980`26f1d800 : nt!ExpWaitForResource+0x8d
fffff880`0883a5b0 fffff880`012692c3 : 00000000`c00000d8 fffff8a0`103f4010 fffffa80`04937e40 fffffa80`04d49180 : nt!ExAcquireResourceExclusiveLite+0x14f
fffff880`0883a620 fffff880`012d53a4 : 00000000`00000000 fffff880`0883a940 00000000`00000001 fffffa80`04937e40 : Ntfs!NtfsAcquireExclusiveFcb+0x73
fffff880`0883a670 fffff880`012ddfad : fffffa80`04937e40 fffffa80`04d49180 00000000`00100001 00000000`00000000 : Ntfs!NtfsFlushVolume+0x188
fffff880`0883a7a0 fffff880`012de6b4 : fffffa80`04937e40 fffffa80`04e8c8c0 fffffa80`03fd5070 00000000`00000000 : Ntfs!NtfsCommonFlushBuffers+0x459
fffff880`0883a880 fffff880`010cebcf : fffffa80`04e8cca8 fffffa80`04e8c8c0 fffffa80`04937e40 fffff880`0883a8a8 : Ntfs!NtfsFsdFlushBuffers+0x104
fffff880`0883a8f0 fffff880`010cd6df : fffffa80`04bef900 00000000`00000001 fffffa80`04bef900 fffffa80`04e8c8c0 : fltmgr!

FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`0883a980 fffff800`02fe521b : 00000000`00000002 fffffa80`03fd5070 00000000`00000001 fffffa80`04e8c8c0 : fltmgr!FltpDispatch+0xcf
fffff880`0883a9e0 fffff800`02f79b85 : fffffa80`04e8c8c0 fffffa80`04e83b60 fffffa80`03fd5070 fffff880`02f65180 : nt!IopSynchronousServiceTail+0xfb
fffff880`0883aa50 fffff800`02cdbed3 : fffffa80`04e83b60 00000000`00000002 fffffa80`04bef900 fffffa80`03fd5070 : nt!NtFlushBuffersFile+0x171
fffff880`0883aae0 00000000`76f117ca : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0020f998 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76f117ca


STACK_COMMAND:  kb

FOLLOWUP_IP:
nt!IoBoostThreadIoPriority+1e7
fffff800`02d26427 418a442422      mov     al,byte ptr [r12+22h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!IoBoostThreadIoPriority+1e7

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0xA_nt!IoBoostThreadIoPriority+1e7

BUCKET_ID:  X64_0xA_nt!IoBoostThreadIoPriority+1e7

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



Awatar użytkownika
cosik_ktosik

Administrator
Posty: 21416
Rejestracja: 13 lis 2008, 01:17
Lokalizacja: Szczecin
Kontaktowanie:

BSOD - różne opisy błędu, prośba o analizę dump

Post05 lis 2011, 09:48

Czujnik i dysk są OKi. BSOD nie wiele mówi. Jedynie, że w trakcie działania aplikacji PROCESS_NAME: poqexec.exe

Dzienniki zaraz zobaczę.

-- So, 5 lis 2011, 10:48 --

hmm, mam informacje na stronie, że ich tam nie ma.
Hotfix
Pozdrawiam, cosik_ktosik :)

bgana

Użytkownik
Posty: 20
Rejestracja: 31 paź 2011, 22:32

BSOD - różne opisy błędu, prośba o analizę dump

Post20 gru 2011, 10:54

Ostatnie tygodnie bez zwisów, więc mogę napisać co w końcu pomogło - wymiana kości RAM. I to mimo tego, że MemTest i kilka innych testerów, które odpalałem wielokrotnie nie pokazywały błędów. Zaryzykowałem jednak i wyjąłem kości, włożyłem Kingstona zgodnego z płytą główną i wszystko uspokoiło się. :) Dobrze, że RAM jest tani, bo nawet nie mam jak zareklamować tych wcześniejszych kości, skoro nie mogę wykryć błędu.

Awatar użytkownika
cosik_ktosik

Administrator
Posty: 21416
Rejestracja: 13 lis 2008, 01:17
Lokalizacja: Szczecin
Kontaktowanie:

BSOD - różne opisy błędu, prośba o analizę dump

Post21 gru 2011, 08:44

Może potrzebowały większych napięć.
Hotfix
Pozdrawiam, cosik_ktosik :)

bgana

Użytkownik
Posty: 20
Rejestracja: 31 paź 2011, 22:32

BSOD - różne opisy błędu, prośba o analizę dump

Post22 gru 2011, 10:58

W jaki sposób można to sprawdzić?

Awatar użytkownika
cosik_ktosik

Administrator
Posty: 21416
Rejestracja: 13 lis 2008, 01:17
Lokalizacja: Szczecin
Kontaktowanie:

BSOD - różne opisy błędu, prośba o analizę dump

Post23 gru 2011, 01:28

Najłatwiej w specyfikacji, podaj tylko ich nazwę i model.
Hotfix
Pozdrawiam, cosik_ktosik :)

bgana

Użytkownik
Posty: 20
Rejestracja: 31 paź 2011, 22:32

BSOD - różne opisy błędu, prośba o analizę dump

Post23 gru 2011, 09:47

Było: 2x 2GB DDR3 Goodram GR1333D364L9/4GDC
Jest: 1x 4GB DDR3 Kingston KVR1333D3N9/4G

Awatar użytkownika
kominekl

Ekspert
Posty: 5855
Rejestracja: 27 lis 2011, 14:25
Kontaktowanie:

BSOD - różne opisy błędu, prośba o analizę dump

Post23 gru 2011, 15:54

Pokaż jeszcze screen z zakładki Error Scan z HD Tune.
Kiedy komputery staną się twoim jedynym życiem, jedynym totemem odstraszającym klątwę nudy, wtedy prędzej czy później granica między tymi dwoma wymiarami zniknie i postacie z Błękitnej Pustki zaczną pojawiać się w Realu. Czasem są twoimi przyjaciółmi. A czasem nie.



  • Reklama

Wróć do „Problemy”



Kto jest online

Użytkownicy przeglądający to forum: Obecnie na forum nie ma żadnego zarejestrowanego użytkownika i 3 gości