x-kom hosting

Prośba o pomoc- Niebieski ekran Błędy z ntoskrnl.exe i chyba z csrss.exe

teroon
utworzono
utworzono

Witam,
Jakieś 2-3 miesiące temu zakupiłem funkiel nówkę kompa. Wgrałem system (win7 64) i kilka dni temu zaczął mi wyskakiwać niebieski ekran.
Wyczyściłem rejestr, pliki tymczasowe, odinstalowałem wszystkie zbędne programy, zrobiłem pełen skan avastem, oraz skan podczas bootowania avastem. Zero wirusów wykrytych, problem w mocy. Bez powodu w trakcie pracy komputer wywala mi niebieski ekran. Będę wdzięczny za pomoc, wolałbym uniknąć reinstalki systemu.

Zrzut niebieskiego ekranu poniżej.

[spoiler]
Microsoft ® Windows Debugger Version 6.11.0001.404 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Marcin\Desktop\010616-4758-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`03204000 PsLoadedModuleList = 0xfffff800`03447890
Debug session time: Wed Jan 6 00:34:42.440 2016 (GMT+1)
System Uptime: 0 days 1:24:06.642
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
........................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa800aecb920, fffffa800aecbc00, fffff8000357f270}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

unable to get nt!KiCurrentEtwBufferOffset
unable to get nt!KiCurrentEtwBufferBase
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Probably caused by : csrss.exe

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

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

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa800aecb920, Terminating object
Arg3: fffffa800aecbc00, Process image file name
Arg4: fffff8000357f270, Explanatory message (ascii)

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

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

unable to get nt!KiCurrentEtwBufferOffset
unable to get nt!KiCurrentEtwBufferBase
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************

ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

MODULE_NAME: csrss

FAULTING_MODULE: 0000000000000000

DEBUG_FLR_IMAGE_TIMESTAMP: 0

PROCESS_OBJECT: fffffa800aecb920

IMAGE_NAME: csrss.exe

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xF4

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`079b4e38 fffff800`03607ab2 : 00000000`000000f4 00000000`00000003 fffffa80`0aecb920 fffffa80`0aecbc00 : nt+0x75bc0
fffff880`079b4e40 00000000`000000f4 : 00000000`00000003 fffffa80`0aecb920 fffffa80`0aecbc00 fffff800`0357f270 : nt+0x403ab2
fffff880`079b4e48 00000000`00000003 : fffffa80`0aecb920 fffffa80`0aecbc00 fffff800`0357f270 44890c54`e46eead8 : 0xf4
fffff880`079b4e50 fffffa80`0aecb920 : fffffa80`0aecbc00 fffff800`0357f270 44890c54`e46eead8 fffffa80`0aecb920 : 0x3
fffff880`079b4e58 fffffa80`0aecbc00 : fffff800`0357f270 44890c54`e46eead8 fffffa80`0aecb920 fffff800`035b2abb : 0xfffffa80`0aecb920
fffff880`079b4e60 fffff800`0357f270 : 44890c54`e46eead8 fffffa80`0aecb920 fffff800`035b2abb ffffffff`ffffffff : 0xfffffa80`0aecbc00
fffff880`079b4e68 44890c54`e46eead8 : fffffa80`0aecb920 fffff800`035b2abb ffffffff`ffffffff fffffa80`0af4b940 : nt+0x37b270
fffff880`079b4e70 fffffa80`0aecb920 : fffff800`035b2abb ffffffff`ffffffff fffffa80`0af4b940 fffffa80`0aecb920 : 0x44890c54`e46eead8
fffff880`079b4e78 fffff800`035b2abb : ffffffff`ffffffff fffffa80`0af4b940 fffffa80`0aecb920 fffffa80`0aecb920 : 0xfffffa80`0aecb920
fffff880`079b4e80 ffffffff`ffffffff : fffffa80`0af4b940 fffffa80`0aecb920 fffffa80`0aecb920 ffffffff`ffffffff : nt+0x3aeabb
fffff880`079b4e88 fffffa80`0af4b940 : fffffa80`0aecb920 fffffa80`0aecb920 ffffffff`ffffffff 00000000`00000008 : 0xffffffff`ffffffff
fffff880`079b4e90 fffffa80`0aecb920 : fffffa80`0aecb920 ffffffff`ffffffff 00000000`00000008 fffffa80`0aecb920 : 0xfffffa80`0af4b940
fffff880`079b4e98 fffffa80`0aecb920 : ffffffff`ffffffff 00000000`00000008 fffffa80`0aecb920 00000000`c0000006 : 0xfffffa80`0aecb920
fffff880`079b4ea0 ffffffff`ffffffff : 00000000`00000008 fffffa80`0aecb920 00000000`c0000006 fffffa80`0af4b940 : 0xfffffa80`0aecb920
fffff880`079b4ea8 00000000`00000008 : fffffa80`0aecb920 00000000`c0000006 fffffa80`0af4b940 fffff800`03531f04 : 0xffffffff`ffffffff
fffff880`079b4eb0 fffffa80`0aecb920 : 00000000`c0000006 fffffa80`0af4b940 fffff800`03531f04 ffffffff`ffffffff : 0x8
fffff880`079b4eb8 00000000`c0000006 : fffffa80`0af4b940 fffff800`03531f04 ffffffff`ffffffff 00000000`00000001 : 0xfffffa80`0aecb920
fffff880`079b4ec0 fffffa80`0af4b940 : fffff800`03531f04 ffffffff`ffffffff 00000000`00000001 fffffa80`0aecb920 : 0xc0000006
fffff880`079b4ec8 fffff800`03531f04 : ffffffff`ffffffff 00000000`00000001 fffffa80`0aecb920 00000000`00000008 : 0xfffffa80`0af4b940
fffff880`079b4ed0 ffffffff`ffffffff : 00000000`00000001 fffffa80`0aecb920 00000000`00000008 fffffa80`746c6644 : nt+0x32df04
fffff880`079b4ed8 00000000`00000001 : fffffa80`0aecb920 00000000`00000008 fffffa80`746c6644 fffff880`079b4f50 : 0xffffffff`ffffffff
fffff880`079b4ee0 fffffa80`0aecb920 : 00000000`00000008 fffffa80`746c6644 fffff880`079b4f50 00000000`00000000 : 0x1
fffff880`079b4ee8 00000000`00000008 : fffffa80`746c6644 fffff880`079b4f50 00000000`00000000 00000980`00000000 : 0xfffffa80`0aecb920
fffff880`079b4ef0 fffffa80`746c6644 : fffff880`079b4f50 00000000`00000000 00000980`00000000 00000000`01d61170 : 0x8
fffff880`079b4ef8 fffff880`079b4f50 : 00000000`00000000 00000980`00000000 00000000`01d61170 00000000`01d60a40 : 0xfffffa80`746c6644
fffff880`079b4f00 00000000`00000000 : 00000980`00000000 00000000`01d61170 00000000`01d60a40 00000000`0010005f : 0xfffff880`079b4f50


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner

[/spoiler]

Youki
komentarz
komentarz

Podaj konfigurację tego PC wraz z marką i mocą zasilacza.

 

Jak uruchomisz debugger, ctrl + S i wklejasz to SRV*c:\symbols*http://msdl.microsoft.com/download/symbols, dajesz OK i potem ctrl+D i ten sam plik otwórz. Wtedy wrzuć całość. 

teroon
komentarz
komentarz (edytowane)

Komputer to ten z linku: http://www.morele.net/komputer-morele-super-efficient-g3000-geforce-edition-g-data-internet-security-707109/
Intel Core i5-4460
Producent chipsetu GeForce GTX 960

MSI GeForce GTX 960 OC (GTX 960 2GD5T OC)

 

Zasilacz Model zasilacza

  • Be Quiet! Pure Power L8-CM-530W, 80 plus BRONZE

Moc [W]

  • 530W

 

 

Wpisuję komendę w CMD ale otrzymuję taki komunikat:
http://postimg.org/image/yzd4sbrp9/

 

A tutaj daję host pliku DMP: http://www.filedropper.com/010616-4758-01

Youki
komentarz
komentarz

Nie w CMD tylko w Microsoft ® Windows Debugger Version 6.11.0001.404 X86

teroon
komentarz
komentarz

Wyświetliło mi coś takiego:

 

 

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


Loading Dump File [C:\Windows\Minidump\010616-4758-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`03204000 PsLoadedModuleList = 0xfffff800`03447890
Debug session time: Wed Jan  6 00:34:42.440 2016 (GMT+1)
System Uptime: 0 days 1:24:06.642
Loading Kernel Symbols
...............................................................
................................................................
........................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa800aecb920, fffffa800aecbc00, fffff8000357f270}

Probably caused by : csrss.exe

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

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

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa800aecb920, Terminating object
Arg3: fffffa800aecbc00, Process image file name
Arg4: fffff8000357f270, Explanatory message (ascii)

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


PROCESS_OBJECT: fffffa800aecb920

IMAGE_NAME:  csrss.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: csrss

FAULTING_MODULE: 0000000000000000

PROCESS_NAME:  csrss.exe

EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.

BUGCHECK_STR:  0xF4_IOERR

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`079b4e38 fffff800`03607ab2 : 00000000`000000f4 00000000`00000003 fffffa80`0aecb920 fffffa80`0aecbc00 : nt!KeBugCheckEx
fffff880`079b4e40 fffff800`035b2abb : ffffffff`ffffffff fffffa80`0af4b940 fffffa80`0aecb920 fffffa80`0aecb920 : nt!PspCatchCriticalBreak+0x92
fffff880`079b4e80 fffff800`03531f04 : ffffffff`ffffffff 00000000`00000001 fffffa80`0aecb920 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x17486
fffff880`079b4ed0 fffff800`03278e53 : fffffa80`0aecb920 fffff800`c0000006 fffffa80`0af4b940 00000000`01d60a40 : nt!NtTerminateProcess+0xf4
fffff880`079b4f50 fffff800`03275410 : fffff800`032c482f fffff880`079b5a38 fffff880`079b5790 fffff880`079b5ae0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`079b50e8 fffff800`032c482f : fffff880`079b5a38 fffff880`079b5790 fffff880`079b5ae0 00000000`01d61750 : nt!KiServiceLinkage
fffff880`079b50f0 fffff800`03279242 : fffff880`079b5a38 00000000`000713b8 fffff880`079b5ae0 00000000`01d61228 : nt! ?? ::FNODOBFM::`string'+0x488e4
fffff880`079b5900 fffff800`03277dba : 00000000`00000000 00000000`772ec334 00000000`7746ff01 00000000`000713b8 : nt!KiExceptionDispatch+0xc2
fffff880`079b5ae0 00000000`77379c42 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`01d61170 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77379c42


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0xF4_IOERR_IMAGE_csrss.exe

BUCKET_ID:  X64_0xF4_IOERR_IMAGE_csrss.exe

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


Jakieś pomysły co mogę zrobić?

  • 2 tygodnie później...
XTeRX
komentarz
komentarz

Spróbuj użyć naprawy systemu z płytki instalacyjnej systemu

Wciąż szukasz rozwiązania problemu? Napisz teraz na forum!

Możesz zadać pytanie bez konieczności rejestracji - wystarczy, że wypełnisz formularz.

×
×
  • Dodaj nową pozycję...

Powiadomienie o plikach cookie

Strona wykorzystuje pliki cookies w celu prawidłowego świadczenia usług i wygody użytkowników. Warunki przechowywania i dostępu do plików cookies możesz zmienić w ustawieniach przeglądarki.