Mam taki problem:
Coraz częściej pojawia mi się komunikat - "Program przestał działać" - najczęściej gry, ale też np. przeglądarka (chrome), a także bluescreen (błąd 0000007E, 0000003B, 00000019, 0000000A).
Mam:
płyta H61MXL-K
Intel Core i3-2100 CPU @ 3,10 GHz
6,00 RAM GoodRam DDR3 (4,00 + 2,00)
Karta GeForce 550 Ti
Windows 7 Home Premium 64
Zasilacz GPA 400S
Co już zrobiłam:
przeinstalowałam system, uaktualniłam sterowniki, Memtest nie wykazuje błędów, natomiast nie przechodzi testu 3DMARK11, więc zakładam, że karta graficzna. Aktualizowałam i sprawdzałam sterowniki z oficjalnej strony.
Temperatura karty nie przekroczyła mi 58 stopni (przy rozruchu Wiedźmina1, który jest od razu zamykany - aha, próbowałam zgodności z XP, nic nie daje)
Przykłady:
Podpis problemu:
Nazwa zdarzenia problemu: BlueScreen
Wersja systemu operacyjnego: 6.1.7600.2.0.0.768.3
Identyfikator ustawień regionalnych: 1045
Dodatkowe informacje o problemie:
BCCode: 1e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF80002CA637A
BCP3: 0000000000000000
BCP4: FFFFFFFFFFFFFFFF
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1
Pliki pomagające opisać problem:
C:\Windows\Minidump\062912-25708-01.dmp
C:\Users\Aka\AppData\Local\Temp\WER-58921-0.sysdata.xml
Probably caused by : ntoskrnl.exe
Podpis problemu:
Nazwa zdarzenia problemu: BlueScreen
Wersja systemu operacyjnego: 6.1.7600.2.0.0.768.3
Identyfikator ustawień regionalnych: 1045
Dodatkowe informacje o problemie:
BCCode: 24
BCP1: 00000000001904FB
BCP2: FFFFF880088E5468
BCP3: FFFFF880088E4CC0
BCP4: FFFFF80002E80937
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1
Pliki pomagające opisać problem:
C:\Windows\Minidump\063012-42697-01.dmp
C:\Users\Aka\AppData\Local\Temp\WER-113631-0.sysdata.xml
Probably caused by : Ntfs.sys ( Ntfs+213d8 )
Pliki pomagające opisać problem:
C:\Windows\Minidump\063012-42697-01.dmp
Odnajdź ten plik, spakuj i wrzuć na forum. Ktoś go zanalizuje i powie ci co powoduje BSOD.
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\070112-22729-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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.17017.amd64fre.win7_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`02e4a000 PsLoadedModuleList = 0xfffff800`03086e70
Debug session time: Sun Jul 1 14: 27: 47.695 2012 (UTC + 2: 00)
System Uptime: 0 days 1: 04: 04.055
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff8800432acf7, fffff88003d14668, fffff88003d13ed0}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL: ReferenceAllocationForPreparation+2b )
Followup: MachineOwner
---------
1: 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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8800432acf7, The address that the exception occurred at
Arg3: fffff88003d14668, Exception Record Address
Arg4: fffff88003d13ed0, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo
FAULTING_IP:
dxgmms1!VIDMM_GLOBAL: ReferenceAllocationForPreparation+2b
fffff880`0432acf7 0fba63540d bt dword ptr [rbx+54h],0Dh
EXCEPTION_RECORD: fffff88003d14668 -- (.exr 0xfffff88003d14668)
ExceptionAddress: fffff8800432acf7 (dxgmms1!VIDMM_GLOBAL: ReferenceAllocationForPreparation+0x000000000000002b)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff88003d13ed0 -- (.cxr 0xfffff88003d13ed0)
rax=fffff8a00c03be70 rbx=cffff8a0098f7b10 rcx=fffffa8008203000
rdx=fffffa80069549c0 rsi=fffffa8008203000 rdi=fffffa8008203000
rip=fffff8800432acf7 rsp=fffff88003d148a0 rbp=fffffa800920e4a0
r8=fffffa8006529201 r9=0000000000000000 r10=0000000000000000
r11=000000000000008c r12=fffffa80069549c0 r13=0000000000000001
r14=0000000000000000 r15=0000000000000001
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
dxgmms1!VIDMM_GLOBAL: ReferenceAllocationForPreparation+0x2b:
fffff880`0432acf7 0fba63540d bt dword ptr [rbx+54h],0Dh ds: 002b: cffff8a0`098f7b64=?
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030f10e0
ffffffffffffffff
FOLLOWUP_IP:
dxgmms1!VIDMM_GLOBAL: ReferenceAllocationForPreparation+2b
fffff880`0432acf7 0fba63540d bt dword ptr [rbx+54h],0Dh
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff88004327ed3 to fffff8800432acf7
STACK_TEXT:
fffff880`03d148a0 fffff880`04327ed3 : 00000000`00000000 fffffa80`089dd188 00000000`0000005b 00000000`00000000 : dxgmms1!VIDMM_GLOBAL: ReferenceAllocationForPreparation+0x2b
fffff880`03d148d0 fffff880`0434265d : 00000000`00000000 fffff8a0`084445f0 fffffa80`00000000 fffffa80`06529250 : dxgmms1!VIDMM_GLOBAL: PrepareDmaBuffer+0x43f
fffff880`03d14aa0 fffff880`04342398 : fffff880`02fd9f40 fffff880`04341d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`03d14c90 fffff880`04341e96 : 00000000`00000000 fffffa80`062b6010 00000000`00000080 fffffa80`07d8d410 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`03d14cc0 fffff800`031596e6 : 00000000`00000010 fffffa80`0789ab60 fffffa80`054edb30 00000000`00010282 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`03d14d00 fffff800`02e98566 : fffff880`02fd5180 fffffa80`0789ab60 fffff880`02fdffc0 fffff880`01216970 : nt!PspSystemThreadStartup+0x5a
fffff880`03d14d40 00000000`00000000 : fffff880`03d15000 fffff880`03d0f000 fffff880`03d14650 00000000`00000000 : nt!KiStartSystemThread+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: dxgmms1!VIDMM_GLOBAL: ReferenceAllocationForPreparation+2b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d3fa174
STACK_COMMAND: .cxr 0xfffff88003d13ed0 ; kb
FAILURE_BUCKET_ID: X64_0x7E_VRF_dxgmms1!VIDMM_GLOBAL: ReferenceAllocationForPreparation+2b
BUCKET_ID: X64_0x7E_VRF_dxgmms1!VIDMM_GLOBAL: ReferenceAllocationForPreparation+2b
Followup: MachineOwner
---------
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\070112-19827-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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.17017.amd64fre.win7_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`02e11000 PsLoadedModuleList = 0xfffff800`0304de70
Debug session time: Sun Jul 1 00: 07: 53.719 2012 (UTC + 2: 00)
System Uptime: 0 days 0: 12: 30.703
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {fffff800031206e6, 2, 0, fffff80002eadae2}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : ntkrnlmp.exe ( nt!RtlDispatchException+122 )
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: fffff800031206e6, 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: fffff80002eadae2, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030b80e0
fffff800031206e6
CURRENT_IRQL: 2
FAULTING_IP:
nt!RtlDispatchException+122
fffff800`02eadae2 410fb60c24 movzx ecx,byte ptr [r12]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: fffff88003da5930 -- (.trap 0xfffff88003da5930)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8000309fcf4 rbx=0000000000000000 rcx=fffff80003120730
rdx=fffff8000312068c rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002eadae2 rsp=fffff88003da5ac0 rbp=fffff88003da6968
r8=0000000000001fbf r9=0000000000001fbf r10=fffff88003da6d00
r11=fffff88003da5b08 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!RtlDispatchException+0x122:
fffff800`02eadae2 410fb60c24 movzx ecx,byte ptr [r12] ds: 0104: 00000000`00000000=?
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002e805a9 to fffff80002e81040
STACK_TEXT:
fffff880`03da57e8 fffff800`02e805a9 : 00000000`0000000a fffff800`031206e6 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`03da57f0 fffff800`02e7f220 : fffff880`03da59f0 00000000`0000005a 00000000`00000000 fffff880`1008e37d : nt!KiBugCheckDispatch+0x69
fffff880`03da5930 fffff800`02eadae2 : fffff800`031206e6 fffff880`03da5b08 fffff880`03da6968 fffff880`0564b000 : nt!KiPageFault+0x260
fffff880`03da5ac0 fffff800`02ebadff : fffff880`03da6968 fffff880`03da61d0 fffff880`00000000 fffff880`03da6c70 : nt!RtlDispatchException+0x122
fffff880`03da61a0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x16f
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!RtlDispatchException+122
fffff800`02eadae2 410fb60c24 movzx ecx,byte ptr [r12]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!RtlDispatchException+122
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4fa38fe2
FAILURE_BUCKET_ID: X64_0xA_VRF_nt!RtlDispatchException+122
BUCKET_ID: X64_0xA_VRF_nt!RtlDispatchException+122
Followup: MachineOwner
---------
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\070112-19827-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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.17017.amd64fre.win7_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`02e11000 PsLoadedModuleList = 0xfffff800`0304de70
Debug session time: Sun Jul 1 00: 07: 53.719 2012 (UTC + 2: 00)
System Uptime: 0 days 0: 12: 30.703
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {fffff800031206e6, 2, 0, fffff80002eadae2}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : ntkrnlmp.exe ( nt!RtlDispatchException+122 )
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: fffff800031206e6, 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: fffff80002eadae2, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030b80e0
fffff800031206e6
CURRENT_IRQL: 2
FAULTING_IP:
nt!RtlDispatchException+122
fffff800`02eadae2 410fb60c24 movzx ecx,byte ptr [r12]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: fffff88003da5930 -- (.trap 0xfffff88003da5930)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8000309fcf4 rbx=0000000000000000 rcx=fffff80003120730
rdx=fffff8000312068c rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002eadae2 rsp=fffff88003da5ac0 rbp=fffff88003da6968
r8=0000000000001fbf r9=0000000000001fbf r10=fffff88003da6d00
r11=fffff88003da5b08 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!RtlDispatchException+0x122:
fffff800`02eadae2 410fb60c24 movzx ecx,byte ptr [r12] ds: 0104: 00000000`00000000=?
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002e805a9 to fffff80002e81040
STACK_TEXT:
fffff880`03da57e8 fffff800`02e805a9 : 00000000`0000000a fffff800`031206e6 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`03da57f0 fffff800`02e7f220 : fffff880`03da59f0 00000000`0000005a 00000000`00000000 fffff880`1008e37d : nt!KiBugCheckDispatch+0x69
fffff880`03da5930 fffff800`02eadae2 : fffff800`031206e6 fffff880`03da5b08 fffff880`03da6968 fffff880`0564b000 : nt!KiPageFault+0x260
fffff880`03da5ac0 fffff800`02ebadff : fffff880`03da6968 fffff880`03da61d0 fffff880`00000000 fffff880`03da6c70 : nt!RtlDispatchException+0x122
fffff880`03da61a0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x16f
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!RtlDispatchException+122
fffff800`02eadae2 410fb60c24 movzx ecx,byte ptr [r12]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!RtlDispatchException+122
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4fa38fe2
FAILURE_BUCKET_ID: X64_0xA_VRF_nt!RtlDispatchException+122
BUCKET_ID: X64_0xA_VRF_nt!RtlDispatchException+122
Followup: MachineOwner
---------
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\063012-25162-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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.17017.amd64fre.win7_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`02e65000 PsLoadedModuleList = 0xfffff800`030a1e70
Debug session time: Sat Jun 30 23: 14: 04.383 2012 (UTC + 2: 00)
System Uptime: 0 days 0: 37: 51.726
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff800031c412c, fffff880092a2f30, 0}
Probably caused by : ntkrnlmp.exe ( nt!ObReferenceObjectByHandleWithTag+10c )
Followup: MachineOwner
---------
1: 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: fffff800031c412c, Address of the instruction which caused the bugcheck
Arg3: fffff880092a2f30, 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!ObReferenceObjectByHandleWithTag+10c
fffff800`031c412c 0fb64518 movzx eax,byte ptr [rbp+18h]
CONTEXT: fffff880092a2f30 -- (.cxr 0xfffff880092a2f30)
rax=76fffa800669a5e1 rbx=fffff8a00ae92060 rcx=76fffa800669a5e0
rdx=0000000000000000 rsi=fffff8a007eb7550 rdi=fffffa800806e060
rip=fffff800031c412c rsp=fffff880092a3900 rbp=76fffa800669a5e0
r8=fffff8a00ae92000 r9=0000000000000018 r10=fffff800031eab10
r11=fffff880092a3af8 r12=0000000000000000 r13=0000000000000018
r14=0000000000000001 r15=fffffa80056cf1c0
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202
nt!ObReferenceObjectByHandleWithTag+0x10c:
fffff800`031c412c 0fb64518 movzx eax,byte ptr [rbp+18h] ss: 0018: 76fffa80`0669a5f8=?
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: mscorsvw.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff800031c412c
STACK_TEXT:
fffff880`092a3900 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ObReferenceObjectByHandleWithTag+0x10c
FOLLOWUP_IP:
nt!ObReferenceObjectByHandleWithTag+10c
fffff800`031c412c 0fb64518 movzx eax,byte ptr [rbp+18h]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!ObReferenceObjectByHandleWithTag+10c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4fa38fe2
STACK_COMMAND: .cxr 0xfffff880092a2f30 ; kb
FAILURE_BUCKET_ID: X64_0x3B_nt!ObReferenceObjectByHandleWithTag+10c
BUCKET_ID: X64_0x3B_nt!ObReferenceObjectByHandleWithTag+10c
Followup: MachineOwner
---------
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\063012-22370-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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.17017.amd64fre.win7_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`02e12000 PsLoadedModuleList = 0xfffff800`0304ee70
Debug session time: Sat Jun 30 23: 52: 07.987 2012 (UTC + 2: 00)
System Uptime: 0 days 0: 04: 38.345
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {0, 2, 1, fffff80002e4a853}
Probably caused by : ntkrnlmp.exe ( nt!KeSetEventBoostPriority+3f )
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: 0000000000000000, 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: fffff80002e4a853, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030b90e0
0000000000000000
CURRENT_IRQL: 2
FAULTING_IP:
nt!KeSetEventBoostPriority+3f
fffff800`02e4a853 f00fba2907 lock bts dword ptr [rcx],7
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR: 0xA
PROCESS_NAME: svchost.exe
TRAP_FRAME: fffff880092d1820 -- (.trap 0xfffff880092d1820)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=0000000000000000
rdx=fffffa80066e3640 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002e4a853 rsp=fffff880092d19b0 rbp=fffffa8008300060
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
nt!KeSetEventBoostPriority+0x3f:
fffff800`02e4a853 f00fba2907 lock bts dword ptr [rcx],7 ds: 00000000`00000000=?
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002e815a9 to fffff80002e82040
STACK_TEXT:
fffff880`092d16d8 fffff800`02e815a9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`092d16e0 fffff800`02e80220 : 00000000`00000000 fffff800`02ffbe80 fffff800`0300e440 fffff880`092d1970 : nt!KiBugCheckDispatch+0x69
fffff880`092d1820 fffff800`02e4a853 : 00000000`00000000 fffffa80`07cd5c38 fffff8a0`0b331b70 00000000`00000000 : nt!KiPageFault+0x260
fffff880`092d19b0 fffff800`02e8c0d4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeSetEventBoostPriority+0x3f
fffff880`092d1a20 fffff880`012287a3 : fffffa80`092cb058 00000000`00000000 fffffa80`092cb010 fffffa80`092cb010 : nt!ExpReleaseResourceForThreadLite+0x2cf
fffff880`092d1a80 fffff880`0122def4 : fffffa80`092cb010 00000000`00000001 00000000`00000000 00000000`00000000 : Ntfs!NtfsCleanupIrpContext+0x1d3
fffff880`092d1ad0 fffff880`012c702f : 00000000`00000000 fffffa80`066e2640 fffff880`052063b0 fffffa80`092cb010 : Ntfs!NtfsExtendedCompleteRequestInternal+0xd4
fffff880`092d1b10 fffff880`0122ec0d : fffffa80`092cb010 fffffa80`0675ac10 fffff880`052063b0 fffffa80`08300000 : Ntfs!NtfsCommonCreate+0x2178
fffff880`092d1cf0 fffff800`02e79ec7 : fffff880`05206320 00000000`00000000 000007fe`f907bc50 00000000`000003e8 : Ntfs!NtfsCommonCreateCallout+0x1d
fffff880`092d1d20 fffff800`02e79e81 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxSwitchKernelStackCallout+0x27
fffff880`052061f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSwitchKernelStackContinue
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KeSetEventBoostPriority+3f
fffff800`02e4a853 f00fba2907 lock bts dword ptr [rcx],7
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!KeSetEventBoostPriority+3f
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4fa38fe2
FAILURE_BUCKET_ID: X64_0xA_VRF_nt!KeSetEventBoostPriority+3f
BUCKET_ID: X64_0xA_VRF_nt!KeSetEventBoostPriority+3f
Followup: MachineOwner
---------
Hm... Powinnam coś z tego zrozumieć?
Tak. Są to logi po zdebugowaniu plików które wrzuciłaś.
W każdym z nich jest takie zdanie: Probably caused by ...
Czyli Prawdopodobnie spowodowany przez ...
Daje to wiedzę jakie pliki powodują u ciebie bluescreeny a co za tym idzie który program, sterownik je powoduje.
No tak, przeważnie jest to ntkrnlmp.exe
Ale co można z tym dalej?
Aha, każdy kolejny BSOD ma inny kod błędu - 7E, 3B, 19, 0A, 1A, C1, C4...
Czy to ma znaczenie?
Podaj konfigurację sprzętu, ważne są marka i moc zasilacza.
Sprawdź np. HDTune'm parametry SMART dysku twardego.
Wyłącz na jakiś czas antywirusa i zobacz czy problem będzie dalej występował.
Upewnij się też, że masz aktualne wszystkie sterowniki.
(01.07.2012 15:26)Ankalime napisał(a): [ -> ]Co już zrobiłam:
przeinstalowałam system, uaktualniłam sterowniki, Memtest nie wykazuje błędów, natomiast nie przechodzi testu 3DMARK11, więc zakładam, że karta graficzna. Aktualizowałam i sprawdzałam sterowniki z oficjalnej strony.
Temperatura karty nie przekroczyła mi 58 stopni (przy rozruchu Wiedźmina1, który jest od razu zamykany - aha, próbowałam zgodności z XP, nic nie daje)
Porządna diagnostyka dysku - skan powierzchni sektor po sektorze (nie szybkie skanowanie), odczyt zawartości SMART, test odczytu. Najlepiej pokazać zrzuty. Programów bez liku HD Tune, CrystalDiskinfo, MHDD, Victoria.
Porządne minimum kilkugodzinne testowanie pamięci RAM programem memtest86. Dobrze jest także podmienić na inne sztuki, podejrzeć w biosie ustawienie vdimm oraz timingów czy pokrywają się ze specyfikacją.
Jeśli chodzi o grafikę, porządnym testowym wygrzewaczem jest Furmark (instrukcja użytkowania w dziale faq).
Na czym objawia się nieprzechodzenie 3DM11 ?
W trybie 3D karta pobiera do około 115W energii, sugerowany zasilacz minimum 400W. Przy Twojej konfiguracji zestaw nie ma prawa pobierać więcej jak 280-300W na linii 12V więc ten zasilacz Chieftec'a o ile jest w 100% sprawny (może za szczęśliwy to ta seria Arena nie jest, taki chieftecowy low-end) to się nadaje. Jeśli masz na to gwarancję to pędziłbym z tym bez namysłu.
Komputer wrócił dziś z wymienioną pamięcią.
Temat do zamknięcie (mam nadzieję
)
Dziękuję wszystkim za rady. Jedyną zaletą awarii było to, że trafiłam na to forum.
Przypominam że od dziękowania jest specjalny przycisk.
Dziękujemy za wizytę na forum i zapraszam do dalszej aktywności!
Temat zamykam.
Wątek rozwiązany.