Plavi ekran za OS Win 8.1 - Kolaps racunara i restart

• 0Niko još nije pohvalio poruku.
  Registruj se da bi pohvalio/la poruku!

Uloguj se preko Facebooka da bi skinuo fajl:

Napisano: 11 Jan 2017 12:55

Pozdrav!
U poslednje vreme imam ucestale probleme sa restartovanjem racunara kome prethodni tzv. Blue screen
U nastavku teksta dajem sledece priloge







Kao i skeniranje sistema sa WhoCrashed programom

[Link mogu videti samo ulogovani korisnici]

Dopuna: 11 Jan 2017 13:14

--------------------------------------------------------------------------------
Welcome to WhoCrashed (HOME EDITION) v 5.53
--------------------------------------------------------------------------------

This program checks for drivers which have been crashing your computer. If your computer has displayed a blue (or black) screen of death, suddenly rebooted or shut down then this program might help you find the root cause of the problem and a solution.

Whenever a computer suddenly reboots without displaying any notice or blue (or black) screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue or black screen unless they are configured for this. Instead these systems suddenly reboot without any notice.

This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.

To obtain technical support visit [Link mogu videti samo ulogovani korisnici]

Click here to check if you have the latest version or if an update is available.

Just click the Analyze button for a comprehensible report ...



--------------------------------------------------------------------------------
Home Edition Notice
--------------------------------------------------------------------------------

This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network.

Please note that this version of WhoCrashed is not licensed for use by professional support engineers.

Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.


--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------

Computer name: USER
Windows version: Windows 8.1 , 6.3, build: 9600
Windows dir: C:\Windows
Hardware: 80SR, LENOVO, Toronto 5A1
CPU: GenuineIntel Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8491270144 bytes total




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Wed 11.1.2017. 12:40:31 your computer crashed
crash dump file: C:\Windows\Minidump\011117-65296-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F9A0)
Bugcheck code: 0xC000021A (0xFFFFC00034BDBB70, 0x0, 0x0, 0x0)
Error: STATUS_SYSTEM_PROCESS_TERMINATED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This means that an error has occurred in a crucial user-mode subsystem.
There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 11.1.2017. 12:40:31 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xC000021A (0xFFFFC00034BDBB70, 0x0, 0x0, 0x0)
Error: STATUS_SYSTEM_PROCESS_TERMINATED
Bug check description: This means that an error has occurred in a crucial user-mode subsystem.
There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 11.1.2017. 12:26:39 your computer crashed
crash dump file: C:\Windows\Minidump\011117-16015-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F9A0)
Bugcheck code: 0xC000021A (0xFFFFC0009823D890, 0x0, 0x0, 0x0)
Error: STATUS_SYSTEM_PROCESS_TERMINATED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This means that an error has occurred in a crucial user-mode subsystem.
There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 11.1.2017. 12:12:33 your computer crashed
crash dump file: C:\Windows\Minidump\011117-16359-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F9A0)
Bugcheck code: 0xC000021A (0xFFFFC001C2B40520, 0x0, 0x0, 0x0)
Error: STATUS_SYSTEM_PROCESS_TERMINATED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This means that an error has occurred in a crucial user-mode subsystem.
There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 11.1.2017. 12:00:05 your computer crashed
crash dump file: C:\Windows\Minidump\011117-16234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F9A0)
Bugcheck code: 0xC000021A (0xFFFFC0006D2E0520, 0x0, 0x0, 0x0)
Error: STATUS_SYSTEM_PROCESS_TERMINATED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This means that an error has occurred in a crucial user-mode subsystem.
There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

12 crash dumps have been found and analyzed. Only 5 are included in this report. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

Dopuna: 11 Jan 2017 13:14

Ne znam jel ovo dovoljno....

Dopuna: 11 Jan 2017 13:26

Evo i i MBT analiza

[Link mogu videti samo ulogovani korisnici]

• 1Ovo se svidja korisniku: gvozdenavolja
  
  Registruj se da bi pohvalio/la poruku!

Otvori temu u Ambulanti (uputstvo ćeš naći na tom potforumu). Po ovim izveštajima, problem pravi/prave virus(i). Konkretno ovaj (a možda i njih više) "C:\Program Files (x86)\Plrerch\wuapy.exe".
Ne čačkaj ništa sam, nego pusti da stručni ljudi obave posao u Ambulanti.

• 0Niko još nije pohvalio poruku.
  Registruj se da bi pohvalio/la poruku!

Dobro, evo idem odmah tamo....