Wielokrotny samoczynny restart komputera

Janusz5000 · 12 Października 2015

Witam.

Problem ciągnie się od ponad roku ze zmiennym "natężeniem". Ostatnio stabilne uruchomienie komputera pozwalające na normalną pracę zajmuje około 30 min. Komputer zazwyczaj resetuje się w pierwszych 2 minutach od włączenia. Poniżej załączam zrzut bsod.

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


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*c:\Symbole*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
Built by: 7601.18939.amd64fre.win7sp1_gdr.150722-0600
Machine Name:
Kernel base = 0xfffff800`0320a000 PsLoadedModuleList = 0xfffff800`03451730
Debug session time: Sat Oct 10 23:09:40.003 2015 (UTC + 2:00)
System Uptime: 0 days 0:00:56.236
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols

Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {1844, 2, 1, fffff8000328788f}

Probably caused by : ataport.SYS ( ataport!IdeStartChannelRequest+50 )

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

3: 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: 0000000000001844, 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: fffff8000328788f, address which referenced memory

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


WRITE_ADDRESS:  0000000000001844 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KeAcquireInStackQueuedSpinLock+5f
fffff800`0328788f 488717          xchg    rdx,qword ptr [rdi]

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff88002ffd7e0 -- (.trap 0xfffff88002ffd7e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=0000000000000000
rdx=fffff88002ffda10 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000328788f rsp=fffff88002ffd970 rbp=fffffa80045f2f00
 r8=fffff88002ffda10  r9=fffffa8004a833d0 r10=fffffa8004a70620
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!KeAcquireInStackQueuedSpinLock+0x5f:
fffff800`0328788f 488717          xchg    rdx,qword ptr [rdi] ds:2f00:0000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000327cb69 to fffff8000327d5c0

STACK_TEXT:  
fffff880`02ffd698 fffff800`0327cb69 : 00000000`0000000a 00000000`00001844 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`02ffd6a0 fffff800`0327b7e0 : 00000000`00000001 00000000`00000002 00000000`ffffffff 00000000`00001800 : nt!KiBugCheckDispatch+0x69
fffff880`02ffd7e0 fffff800`0328788f : 00000000`00000001 fffff800`037f87d8 fffffa80`045f2fe0 fffffa80`045b6850 : nt!KiPageFault+0x260
fffff880`02ffd970 fffff880`0112775c : fffffa80`045f2f00 00000000`0000180c fffffa80`04a6f1a0 00000000`00000022 : nt!KeAcquireInStackQueuedSpinLock+0x5f
fffff880`02ffd9c0 fffff880`01127352 : 00000000`00000001 fffffa80`05c58010 00000000`00000001 fffffa80`05c58010 : ataport!IdeStartChannelRequest+0x50
fffff880`02ffda40 fffff880`011295b6 : fffffa80`0513c100 00000000`00000000 fffffa80`04a831b0 fffffa80`05c5a6f0 : ataport!IdeStartNextDeviceRequest+0x18e
fffff880`02ffdae0 fffff880`01129120 : fffffa80`04a6f1a0 00000000`00000000 fffffa80`04a6f1a0 fffffa80`05c5a6f0 : ataport!IdeProcessCompletedRequests+0x26a
fffff880`02ffdc10 fffff800`03288ecc : fffff880`02fd5180 00000000`30384d03 fffffa80`04a6f050 fffffa80`04a6f118 : ataport!IdePortCompletionDpc+0x1a8
fffff880`02ffdcd0 fffff800`032752ca : fffff880`02fd5180 fffff880`02fdffc0 00000000`00000000 fffff880`01128f78 : nt!KiRetireDpcList+0x1bc
fffff880`02ffdd80 00000000`00000000 : fffff880`02ffe000 fffff880`02ff8000 fffff880`02ffdd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
ataport!IdeStartChannelRequest+50
fffff880`0112775c 807b4000        cmp     byte ptr [rbx+40h],0

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  ataport!IdeStartChannelRequest+50

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ataport

IMAGE_NAME:  ataport.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  51fef9b5

FAILURE_BUCKET_ID:  X64_0xA_ataport!IdeStartChannelRequest+50

BUCKET_ID:  X64_0xA_ataport!IdeStartChannelRequest+50

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

Przez ostatnie 3 miesiące komputer był używany sporadycznie. Pod koniec czerwca tego roku przy sciąganiu pdf creatora załapałem SearchProtect . Oprócz zmiany strony startowej przeglądarki nie odnotowałem żadnych szkód.

Proszę o pomoc.