Witam!
Proszę o pomoc z BSOD. Komputer się włącza i działa przez jakiś czas, ale później, najczęściej w czasie grania, włącza się niebieski ekran. Odczytałem plik minidump i wygląda on następująco:
Loading Dump File [C:\Windows\Minidump\060913-17156-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*D:\Symbols*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.18113.amd64fre.win7sp1_gdr.130318-1533
Machine Name:
Kernel base = 0xfffff800`0304b000 PsLoadedModuleList = 0xfffff800`0328e670
Debug session time: Sun Jun 9 08:31:01.756 2013 (GMT+2)
System Uptime: 0 days 0:30:39.100
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {ffffffffffffff8e, 1, fffff800033bec98, 0}
Could not read faulting driver name
Probably caused by : hardware ( nt!ObOpenObjectByName+428 )
Followup: MachineOwner
---------
0: 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: ffffffffffffff8e, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff800033bec98, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800032f8100
ffffffffffffff8e
FAULTING_IP:
nt!ObOpenObjectByName+428
fffff800`033bec98 00488b add byte ptr [rax-75h],cl
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: SteamService.e
CURRENT_IRQL: 0
TRAP_FRAME: fffff8800a64f920 -- (.trap 0xfffff8800a64f920)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000003 rbx=0000000000000000 rcx=fffffa80069b78e0
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800033bec98 rsp=fffff8800a64fab0 rbp=0000000000000000
r8=fffff8a003bf0000 r9=000000000000023c r10=0000000000000000
r11=fffffa80069b7870 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
nt!ObOpenObjectByName+0x428:
fffff800`033bec98 00488b add byte ptr [rax-75h],cl ds:0028:ffffffff`ffffff8e=??
Resetting default scope
MISALIGNED_IP:
nt!ObOpenObjectByName+428
fffff800`033bec98 00488b add byte ptr [rax-75h],cl
LAST_CONTROL_TRANSFER: from fffff8000313ebe0 to fffff800030c0c00
STACK_TEXT:
fffff880`0a64f7b8 fffff800`0313ebe0 : 00000000`00000050 ffffffff`ffffff8e 00000000`00000001 fffff880`0a64f920 : nt!KeBugCheckEx
fffff880`0a64f7c0 fffff800`030bed2e : 00000000`00000001 ffffffff`ffffff8e fffffa80`03d36600 fffffa80`06603610 : nt! ?? ::FNODOBFM::`string'+0x4518f
fffff880`0a64f920 fffff800`033bec98 : 00000000`00000000 fffffa80`06603610 fffff800`0304b000 fffffa80`03d36500 : nt!KiPageFault+0x16e
fffff880`0a64fab0 fffff800`033a3285 : fffff880`0a64fb88 00000000`00ace118 00000000`00000001 fffff880`0a64fbf8 : nt!ObOpenObjectByName+0x428
fffff880`0a64fb80 fffff800`030bfe93 : fffffa80`051237e0 00000000`000001b4 fffff880`0a64fbb8 fffffa80`05c6fc20 : nt!NtOpenEvent+0x6d
fffff880`0a64fbe0 00000000`775d171a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00ace0b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x775d171a
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!ObOpenObjectByName+428
fffff800`033bec98 00488b add byte ptr [rax-75h],cl
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!ObOpenObjectByName+428
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: hardware
FAILURE_BUCKET_ID: X64_IP_MISALIGNED
BUCKET_ID: X64_IP_MISALIGNED
Followup: MachineOwner
---------
0: kd> lmvm hardware
start end module name
Z tego co widzę, to problem jest w samym hardware-tylko pytanie brzmi co dokładnie się popsuło-wydaje mi się, że jest to procesor, ale czy można to na tej podstawie określić?
Nadmienię, że na pewno nie jest to karta graficzna, bo mam drugą i sprawdziłem, ani płyta główna bo jest ostatnio wymieniona i nie ma poprawy, ani raczej pamięć ram, bo też wymieniłem. Dysk również nie bo sprawdziłem inny i nie ma problemów.
Mój komputer to:
Płyta główna: ASRock P43Twins1600
Procesor: Intel Core 2 Quad Q8400
Grafika GTX 460SE
Zasilacz: Tracer Highlander 550W (TRZ-551)
Z góry dziękuję
Proszę o pomoc z BSOD. Komputer się włącza i działa przez jakiś czas, ale później, najczęściej w czasie grania, włącza się niebieski ekran. Odczytałem plik minidump i wygląda on następująco:
Loading Dump File [C:\Windows\Minidump\060913-17156-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*D:\Symbols*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.18113.amd64fre.win7sp1_gdr.130318-1533
Machine Name:
Kernel base = 0xfffff800`0304b000 PsLoadedModuleList = 0xfffff800`0328e670
Debug session time: Sun Jun 9 08:31:01.756 2013 (GMT+2)
System Uptime: 0 days 0:30:39.100
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {ffffffffffffff8e, 1, fffff800033bec98, 0}
Could not read faulting driver name
Probably caused by : hardware ( nt!ObOpenObjectByName+428 )
Followup: MachineOwner
---------
0: 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: ffffffffffffff8e, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff800033bec98, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800032f8100
ffffffffffffff8e
FAULTING_IP:
nt!ObOpenObjectByName+428
fffff800`033bec98 00488b add byte ptr [rax-75h],cl
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: SteamService.e
CURRENT_IRQL: 0
TRAP_FRAME: fffff8800a64f920 -- (.trap 0xfffff8800a64f920)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000003 rbx=0000000000000000 rcx=fffffa80069b78e0
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800033bec98 rsp=fffff8800a64fab0 rbp=0000000000000000
r8=fffff8a003bf0000 r9=000000000000023c r10=0000000000000000
r11=fffffa80069b7870 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
nt!ObOpenObjectByName+0x428:
fffff800`033bec98 00488b add byte ptr [rax-75h],cl ds:0028:ffffffff`ffffff8e=??
Resetting default scope
MISALIGNED_IP:
nt!ObOpenObjectByName+428
fffff800`033bec98 00488b add byte ptr [rax-75h],cl
LAST_CONTROL_TRANSFER: from fffff8000313ebe0 to fffff800030c0c00
STACK_TEXT:
fffff880`0a64f7b8 fffff800`0313ebe0 : 00000000`00000050 ffffffff`ffffff8e 00000000`00000001 fffff880`0a64f920 : nt!KeBugCheckEx
fffff880`0a64f7c0 fffff800`030bed2e : 00000000`00000001 ffffffff`ffffff8e fffffa80`03d36600 fffffa80`06603610 : nt! ?? ::FNODOBFM::`string'+0x4518f
fffff880`0a64f920 fffff800`033bec98 : 00000000`00000000 fffffa80`06603610 fffff800`0304b000 fffffa80`03d36500 : nt!KiPageFault+0x16e
fffff880`0a64fab0 fffff800`033a3285 : fffff880`0a64fb88 00000000`00ace118 00000000`00000001 fffff880`0a64fbf8 : nt!ObOpenObjectByName+0x428
fffff880`0a64fb80 fffff800`030bfe93 : fffffa80`051237e0 00000000`000001b4 fffff880`0a64fbb8 fffffa80`05c6fc20 : nt!NtOpenEvent+0x6d
fffff880`0a64fbe0 00000000`775d171a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00ace0b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x775d171a
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!ObOpenObjectByName+428
fffff800`033bec98 00488b add byte ptr [rax-75h],cl
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!ObOpenObjectByName+428
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: hardware
FAILURE_BUCKET_ID: X64_IP_MISALIGNED
BUCKET_ID: X64_IP_MISALIGNED
Followup: MachineOwner
---------
0: kd> lmvm hardware
start end module name
Z tego co widzę, to problem jest w samym hardware-tylko pytanie brzmi co dokładnie się popsuło-wydaje mi się, że jest to procesor, ale czy można to na tej podstawie określić?
Nadmienię, że na pewno nie jest to karta graficzna, bo mam drugą i sprawdziłem, ani płyta główna bo jest ostatnio wymieniona i nie ma poprawy, ani raczej pamięć ram, bo też wymieniłem. Dysk również nie bo sprawdziłem inny i nie ma problemów.
Mój komputer to:
Płyta główna: ASRock P43Twins1600
Procesor: Intel Core 2 Quad Q8400
Grafika GTX 460SE
Zasilacz: Tracer Highlander 550W (TRZ-551)
Z góry dziękuję