bluescreen i zawieszanie się przeglądarki a potem całego kom

Post21 lut 2014, 17:01

1 raport:


Loading Dump File [C:\Windows\Minidump\022014-34679-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`03402000 PsLoadedModuleList = 0xfffff800`036456d0
Debug session time: Thu Feb 20 22:04:59.190 2014 (UTC + 1:00)
System Uptime: 0 days 3:18:31.174
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, fffff8000348250f}

Probably caused by : ntkrnlmp.exe ( nt!KiTimerExpiration+ef )

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: fffff8000348250f, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800036af100
 0000000000000000 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiTimerExpiration+ef
fffff800`0348250f 488901          mov     qword ptr [rcx],rax

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  chrome.exe

TRAP_FRAME:  fffff80000ba2cd0 -- (.trap 0xfffff80000ba2cd0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa80120cec01 rbx=0000000000000000 rcx=0000000000000000
rdx=000000000000008b rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000348250f rsp=fffff80000ba2e60 rbp=00000000000ba68b
 r8=fffff8800473fb70  r9=00000000000000ff r10=000000000000008b
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz ac po cy
nt!KiTimerExpiration+0xef:
fffff800`0348250f 488901          mov     qword ptr [rcx],rax ds:52a8:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003477169 to fffff80003477bc0

STACK_TEXT:  
fffff800`00ba2b88 fffff800`03477169 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff800`00ba2b90 fffff800`03475de0 : fffffa80`0fb2fb50 00000000`00000000 fffffa80`0fb2fc58 0000001b`bb9cf7df : nt!KiBugCheckDispatch+0x69
fffff800`00ba2cd0 fffff800`0348250f : 0000001b`bb9cf7df fffff800`00ba2e88 00000000`000ba68b fffff800`035f63e8 : nt!KiPageFault+0x260
fffff800`00ba2e60 fffff800`034823c7 : fffff880`0fbd97ff fffff800`000ba68b fffffa80`071e4578 00000000`0000008b : nt!KiTimerExpiration+0xef
fffff800`00ba2f00 fffff800`0347ad15 : 00000000`00000000 fffffa80`11c29b50 00000000`00000000 fffff880`0588113c : nt!KiRetireDpcList+0x277
fffff800`00ba2fb0 fffff800`0347ab2c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KyRetireDpcList+0x5
fffff880`0b97daa0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiTimerExpiration+ef
fffff800`0348250f 488901          mov     qword ptr [rcx],rax

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KiTimerExpiration+ef

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  521ea035

FAILURE_BUCKET_ID:  X64_0xA_nt!KiTimerExpiration+ef

BUCKET_ID:  X64_0xA_nt!KiTimerExpiration+ef

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

2 raport:

Kod: Zaznacz cały


Loading Dump File [C:\Windows\Minidump\022114-35381-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`03450000 PsLoadedModuleList = 0xfffff800`036936d0
Debug session time: Fri Feb 21 11:59:51.814 2014 (UTC + 1:00)
System Uptime: 0 days 13:53:51.782
Loading Kernel Symbols
...............................................................
................................................................
.........................................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )

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

0: 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: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, 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: (Win32) 0 (0) - Operacja uko czona pomy lnie.

FAULTING_IP: 
+3336396232663237
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR:  0x1E_0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff80000ba24f8 -- (.exr 0xfffff80000ba24f8)
ExceptionAddress: fffff800034d40d8 (nt!KiTryUnwaitThread+0x0000000000000028)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff80000ba25a0 -- (.trap 0xfffff80000ba25a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800ac74b18 rbx=0000000000000000 rcx=fffff80003640e80
rdx=fffffa800f7c2140 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800034d40d8 rsp=fffff80000ba2730 rbp=fffff80003644bc8
 r8=0000000000000100  r9=0000000000000000 r10=fffff80003640e80
r11=fffffa800ac74b38 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KiTryUnwaitThread+0x28:
fffff800`034d40d8 f0480fba6b4000  lock bts qword ptr [rbx+40h],0 ds:0b50:00000000`00000040=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800034bd5be to fffff800034c5b90

STACK_TEXT:  
fffff800`00ba15d8 fffff800`034bd5be : 00000000`00000000 fffffa80`07710c00 fffff800`00ba1d50 fffff800`034f0a90 : nt!KeBugCheck
fffff800`00ba15e0 fffff800`034f075d : fffff800`036d4380 fffff800`03611260 fffff800`03450000 fffff800`00ba24f8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`00ba1610 fffff800`034ef535 : fffff800`03614f64 fffff800`00ba1688 fffff800`00ba24f8 fffff800`03450000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`00ba1640 fffff800`035004c1 : fffff800`00ba24f8 fffff800`00ba1d50 fffff800`00000000 fffff800`03644b00 : nt!RtlDispatchException+0x415
fffff800`00ba1d20 fffff800`034c5242 : fffff800`00ba24f8 cf892eda`34109f86 fffff800`00ba25a0 d15a8a50`dd109fd1 : nt!KiDispatchException+0x135
fffff800`00ba23c0 fffff800`034c3b4a : 00000000`00000000 00000000`00000002 fffffa80`121e7660 fffff800`034a66c6 : nt!KiExceptionDispatch+0xc2
fffff800`00ba25a0 fffff800`034d40d8 : 00000000`00000002 00000000`00000000 00000000`00000002 fffff800`03640e00 : nt!KiGeneralProtectionFault+0x10a
fffff800`00ba2730 fffff800`0351eee6 : fffff800`03644bd0 fffff800`03644bc8 d15a8a50`dd109fd1 fffff800`03644bc8 : nt!KiTryUnwaitThread+0x28
fffff800`00ba2790 fffff800`034d069d : fffff800`03644bc8 fffffa80`06f86c58 fffffa80`06f86c58 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0xb2f3
fffff800`00ba2810 fffff800`0354da3a : 00000074`7d441871 fffff800`00ba2e88 00000000`0030efe8 fffff800`03644f88 : nt!KiProcessExpiredTimerList+0x6d
fffff800`00ba2e60 fffff800`034d03c7 : fffff880`0fb467ff fffff800`0030efe8 00000000`00000000 00000000`000000e8 : nt! ?? ::FNODOBFM::`string'+0x57d9f
fffff800`00ba2f00 fffff800`034c8d15 : 00000000`00000000 fffffa80`0fb70410 00000000`00000000 fffff880`0fb47180 : nt!KiRetireDpcList+0x277
fffff800`00ba2fb0 fffff800`034c8b2c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KyRetireDpcList+0x5
fffff880`0843eaa0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiKernelCalloutExceptionHandler+e
fffff800`034bd5be 90              nop

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KiKernelCalloutExceptionHandler+e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  521ea035

FAILURE_BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e

BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e

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

3 Raport z MEMORY.DMP

Kod: Zaznacz cały

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

WARNING: Whitespace at end of path element
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`03450000 PsLoadedModuleList = 0xfffff800`036936d0
Debug session time: Fri Feb 21 11:59:51.814 2014 (UTC + 1:00)
System Uptime: 0 days 13:53:51.782
Loading Kernel Symbols
...............................................................
................................................................
.........................................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000007ff`fffde018).  Type ".hh dbgerr001" for details
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )

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

0: 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: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, 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: (Win32) 0 (0) - Operacja uko czona pomy lnie.

FAULTING_IP: 
+3731383465396334
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR:  0x1E_0

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff80000ba24f8 -- (.exr 0xfffff80000ba24f8)
ExceptionAddress: fffff800034d40d8 (nt!KiTryUnwaitThread+0x0000000000000028)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff80000ba25a0 -- (.trap 0xfffff80000ba25a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800ac74b18 rbx=0000000000000000 rcx=fffff80003640e80
rdx=fffffa800f7c2140 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800034d40d8 rsp=fffff80000ba2730 rbp=fffff80003644bc8
 r8=0000000000000100  r9=0000000000000000 r10=fffff80003640e80
r11=fffffa800ac74b38 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KiTryUnwaitThread+0x28:
fffff800`034d40d8 f0480fba6b4000  lock bts qword ptr [rbx+40h],0 ds:0b50:0040=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800034bd5be to fffff800034c5b90

STACK_TEXT:  
fffff800`00ba15d8 fffff800`034bd5be : 00000000`00000000 fffffa80`07710c00 fffff800`00ba1d50 fffff800`034f0a90 : nt!KeBugCheck
fffff800`00ba15e0 fffff800`034f075d : fffff800`036d4380 fffff800`03611260 fffff800`03450000 fffff800`00ba24f8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`00ba1610 fffff800`034ef535 : fffff800`03614f64 fffff800`00ba1688 fffff800`00ba24f8 fffff800`03450000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`00ba1640 fffff800`035004c1 : fffff800`00ba24f8 fffff800`00ba1d50 fffff800`00000000 fffff800`03644b00 : nt!RtlDispatchException+0x415
fffff800`00ba1d20 fffff800`034c5242 : fffff800`00ba24f8 cf892eda`34109f86 fffff800`00ba25a0 d15a8a50`dd109fd1 : nt!KiDispatchException+0x135
fffff800`00ba23c0 fffff800`034c3b4a : 00000000`00000000 00000000`00000002 fffffa80`121e7660 fffff800`034a66c6 : nt!KiExceptionDispatch+0xc2
fffff800`00ba25a0 fffff800`034d40d8 : 00000000`00000002 00000000`00000000 00000000`00000002 fffff800`03640e00 : nt!KiGeneralProtectionFault+0x10a
fffff800`00ba2730 fffff800`0351eee6 : fffff800`03644bd0 fffff800`03644bc8 d15a8a50`dd109fd1 fffff800`03644bc8 : nt!KiTryUnwaitThread+0x28
fffff800`00ba2790 fffff800`034d069d : fffff800`03644bc8 fffffa80`06f86c58 fffffa80`06f86c58 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0xb2f3
fffff800`00ba2810 fffff800`0354da3a : 00000074`7d441871 fffff800`00ba2e88 00000000`0030efe8 fffff800`03644f88 : nt!KiProcessExpiredTimerList+0x6d
fffff800`00ba2e60 fffff800`034d03c7 : fffff880`0fb467ff fffff800`0030efe8 00000000`00000000 00000000`000000e8 : nt! ?? ::FNODOBFM::`string'+0x57d9f
fffff800`00ba2f00 fffff800`034c8d15 : 00000000`00000000 fffffa80`0fb70410 00000000`00000000 fffff880`0fb47180 : nt!KiRetireDpcList+0x277
fffff800`00ba2fb0 fffff800`034c8b2c : 00000000`06a1d7f0 fffff800`03411895 fffff800`03437460 fffff880`0843eb60 : nt!KyRetireDpcList+0x5
fffff880`0843eaa0 fffff800`03510b53 : fffff800`034c2140 fffff800`034c21ac 00000000`014c8e40 fffff880`0843eb60 : nt!KiDispatchInterruptContinue
fffff880`0843ead0 fffff800`034c21ac : 00000000`014c8e40 fffff880`0843eb60 00000000`040aff40 00000000`06a56e80 : nt!KiDpcInterruptBypass+0x13
fffff880`0843eae0 000007fe`f7e74f50 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x1fc
00000000`033ceb30 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`f7e74f50


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiKernelCalloutExceptionHandler+e
fffff800`034bd5be 90              nop

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KiKernelCalloutExceptionHandler+e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  521ea035

FAILURE_BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e

BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e

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

Również mam tak , że kursor nagle w miejscu stoi i nic nie mogę zrobić!!!
przeglądarka się zatnie, a potem cały komp i niestety trzeba zrobić reset, ale po pewnym czasie znowu to samo

Post21 lut 2014, 17:17

Po pierwsze to może być problem sprzętowy lub ze sterownikami,
po drugie taka sytuacja może świadczyć również na obecność wirusów:

Również mam tak , że kursor nagle w miejscu stoi i nic nie mogę zrobić!!!
przeglądarka się zatnie, a potem cały komp i niestety trzeba zrobić reset, ale po pewnym czasie znowu to samo

Przeskanuj komputer programem Dostępne tylko dla zarejestrowanych użytkowników
Pełne skanowanie
(usuń zainfekowane pliki)
(nie instaluj wersji PRO tylko Freeware)
Po skanowaniu wrzuć z niego raport na:
Dostępne tylko dla zarejestrowanych użytkowników
Podaj link do niego na forum.

Obowiązkowe logi:
OTL.txt i Extras.txt --> http://www.hotfix.pl/obsluga-programu-otl-a143.htm
TDSSKiller --> http://www.hotfix.pl/instrukcja-obslugi ... r-a341.htm

Logi/raporty wklejasz na:
Dostępne tylko dla zarejestrowanych użytkowników
a na forum podajesz tylko linki do nich.

Post21 lut 2014, 19:27

OTL: Dostępne tylko dla zarejestrowanych użytkowników

Extras: Dostępne tylko dla zarejestrowanych użytkowników

TDSSkiller: Dostępne tylko dla zarejestrowanych użytkowników

log MBAM: Dostępne tylko dla zarejestrowanych użytkowników

Wcześniej usunąłem Advanced System Care 7.2 i Sandboxie 4.08 ponieważ źle wpływały na pracę programu Kaspersky LAB

Post22 lut 2014, 00:10

Przenoszę do działu bezpieczeństwo dla sprawdzenia logów.

Post22 lut 2014, 08:45

Kosmetyka:
Do Notatnika wklej:

Kod: Zaznacz cały

Windows Registry Editor Version 5.00

[HKEY_USERS\.DEFAULT\Software\Microsoft\Internet Explorer\SearchScopes]
"DefaultScope"=-

[HKEY_USERS\S-1-5-18\Software\Microsoft\Internet Explorer\SearchScopes]
"DefaultScope"=-

[HKEY_USERS\S-1-5-19\Software\Microsoft\Internet Explorer\SearchScopes]
"DefaultScope"=-

[HKEY_USERS\S-1-5-20\Software\Microsoft\Internet Explorer\SearchScopes]
"DefaultScope"=-

[HKEY_USERS\S-1-5-21-4285428301-1045311921-1022846929-500\Software\Microsoft\Internet Explorer\SearchScopes]
"DefaultScope"=-1

Z Menu Notatnika >> Plik >> Zapisz jako >> Ustaw rozszerzenie na Wszystkie pliki >> Zapisz jako> FIX.REG >>
plik uruchom (dwuklik i OK).

Nie ma tu żadnej infekcji, więc temat powinien wrócić tam, skąd tu przyszedł.

F.

Post04 mar 2014, 13:48

czy coś jeszcze trzeba zrobić?

Post05 mar 2014, 12:44

Pod względem "wirusowym" - nie, nic więcej nie ma do roboty.
Natomiast w kwestii "bluescreenu i zawieszeń" - to pozostawiam do rozstrzygnięcia Moderatorom.

F.

Post13 mar 2014, 09:50

Bardzo proszę o pomoc!

Rano wyskoczył mi nowy bluescreen:

Kod: Zaznacz cały

Microsoft ® Windows Debugger Version 6.12.0002.633 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\031314-73460-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`03409000 PsLoadedModuleList = 0xfffff800`0364c6d0
Debug session time: Thu Mar 13 06:56:27.377 2014 (UTC + 1:00)
System Uptime: 0 days 1:29:32.250
Loading Kernel Symbols
...............................................................
................................................................
........................................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )

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

3: 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: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, 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: (Win32) 0 (0) - Operacja uko czona pomy lnie.

FAULTING_IP: 
+3864393232303338
00000000`00000000 ?? ???

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR: 0x1E_0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 2

EXCEPTION_RECORD: fffff880039ff188 -- (.exr 0xfffff880039ff188)
ExceptionAddress: fffff8000348d0d8 (nt!KiTryUnwaitThread+0x0000000000000028)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME: fffff880039ff230 -- (.trap 0xfffff880039ff230)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff800035fe188 rbx=0000000000000000 rcx=fffff880039d7180
rdx=fffffa8011611140 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000348d0d8 rsp=fffff880039ff3c0 rbp=fffff880009ebbe8
r8=0000000000000100 r9=0000000000000000 r10=0000000000000034
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!KiTryUnwaitThread+0x28:
fffff800`0348d0d8 f0480fba6b4000 lock bts qword ptr [rbx+40h],0 ds:c4d8:00000000`00000040=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff800034765be to fffff8000347eb90

STACK_TEXT: 
fffff880`039fe268 fffff800`034765be : fffffa80`11a79c00 fffff880`0371b585 fffff880`039fe9e0 fffff800`034a9a90 : nt!KeBugCheck
fffff880`039fe270 fffff800`034a975d : fffff800`0368d380 fffff800`035ca260 fffff800`03409000 fffff880`039ff188 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`039fe2a0 fffff800`034a8535 : fffff800`035ce038 fffff880`039fe318 fffff880`039ff188 fffff800`03409000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`039fe2d0 fffff800`034b94c1 : fffff880`039ff188 fffff880`039fe9e0 fffff880`00000000 fffff880`009ebb00 : nt!RtlDispatchException+0x415
fffff880`039fe9b0 fffff800`0347e242 : fffff880`039ff188 5c2ca1c9`6a240af1 fffff880`039ff230 8cbff16b`712a0b97 : nt!KiDispatchException+0x135
fffff880`039ff050 fffff800`0347cb4a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`039ff230 fffff800`0348d0d8 : 00000000`00083338 00000000`000832de fffffa80`06b1cc20 fffff880`039d7100 : nt!KiGeneralProtectionFault+0x10a
fffff880`039ff3c0 fffff800`034d7ee6 : fffff880`009ebbf0 fffff880`009ebbe8 8cbff16b`712a0b97 fffff880`009ebbe8 : nt!KiTryUnwaitThread+0x28
fffff880`039ff420 fffff800`0348969d : fffff880`009ebbe8 fffffa80`0fb2dc58 fffffa80`0fb2dc58 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0xb2f3
fffff880`039ff4a0 fffff800`03506a3a : 0000000c`821c6101 fffff880`039ffb18 00000000`00054134 fffff880`039d9c08 : nt!KiProcessExpiredTimerList+0x6d
fffff880`039ffaf0 fffff800`034893c7 : 00000002`702694ff 00000002`00054134 00000002`7026943f 00000000`00000034 : nt! ?? ::FNODOBFM::`string'+0x57d9f
fffff880`039ffb90 fffff800`034768ca : fffff880`039d7180 fffff880`039e20c0 00000000`00000001 fffff800`00000000 : nt!KiRetireDpcList+0x277
fffff880`039ffc40 00000000`00000000 : fffff880`03a00000 fffff880`039fa000 fffff880`039ffc00 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: kb

FOLLOWUP_IP: 
nt!KiKernelCalloutExceptionHandler+e
fffff800`034765be 90 nop

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!KiKernelCalloutExceptionHandler+e

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 521ea035

FAILURE_BUCKET_ID: X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e

BUCKET_ID: X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e

Followup: MachineOwner

Post13 mar 2014, 13:01

Sprawdź inne sterowniki do karty graficznej.
Starsze mogą być lepsze.
Nie wiesz które wybrać to podaj system bit. nazwę karty graficznej oraz wersję obecnie posiadanych sterowników.

Nie pomoże to sprawdź pamięć:
http://www.hotfix.pl/instrukcja-obslugi ... m-a204.htm

Przenoszę temat z działu Bezpieczeństwo Problemy,
XMan.