neobjasnjivi BSODovi

[NIx Car]

U toku dana me strefi bar 2 3 BSODa, ne znam u cemu je problem. I na 10ki i na 8ci mi se desava....
Evo crash dumpa

On Mon 19-Oct-15 2:05:53 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101915-25062-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x5873)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8006130B873, 0xFFFFD000203D4DC8, 0xFFFFD000203D45D0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Mon 19-Oct-15 2:05:53 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr!FltReleaseContext+0xE03)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF8006130B873, 0xFFFFD000203D4DC8, 0xFFFFD000203D45D0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Mon 19-Oct-15 10:06:37 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101915-23656-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F8A0)
Bugcheck code: 0xBE (0xFFFFC0012E738060, 0xEE3000004DF58121, 0xFFFFD0005F193EA0, 0xB)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 16-Oct-15 9:04:00 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101615-21906-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F8A0)
Bugcheck code: 0x139 (0x3, 0xFFFFD000234CF030, 0xFFFFD000234CEF88, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 13-Oct-15 12:51:53 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101315-20937-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F9A0)
Bugcheck code: 0x1A (0x5003, 0xFFFFF58010804000, 0x1FA1, 0x140CB6043E66A000)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Da li treba da se nosi u servis?

[analayzer]

Imaš ti tu puno različitih bsoda. Da li ti se dešava i na Sedmici? Napravi malu particiju na disku pa instaliraj Win Sedam i osnovne drivere ploča, grafička, zvuk, mrežna framework 4.6, Intel menadžment control ako imaš intela. Nabaci koju igru i testiraj. Možeš i memoriju proveriti memtestom, testiraj grafičku kombusterom ili nečim sličnim. Zabavljaj se brate. Pa ćeš videti kako reaguje.

[NIx Car]

Odneo sam i u servis posto je jos pod garancijom, pa nek se oni igraju sa njim

[NIx Car]

Danas sam ih zvao, rekose za sada laptop prolazi sve hardverske testove....

[analayzer]

To je potpuno normalno kod majstora radi a kod vlasnika jok. " Drži vodu dok majstori ne odu".

[NIx Car]

I sta sad da radim, da mi vrate opet poluispravan laptop a garancija mi istice za 3 nedelje :

EDIT: sada sam zvao ponovo, i rekli su mi da je to njihova koleginica procitala rezultate od prosle reklamacije

[Lex987]

Nemoj da odustajes! Ako ne bude radilo odnesi im opet. Ukoliko se BSOD ponavlja, pokazi im crush dump, slikaj telefonom... moras da budes uporan/dosadan.

[NIx Car]

Vratili mi ga iz servisa, kazu uredjaj je wan windowsa prosao sve hardverrske testove. Ponudili mi reinstlaacija + bekap za 5k
Kada sam preuzimao laptop rekli su mi da instaliram sedmicu i da imam samo basic programe pa da vidim hoce li se desavati BSODovi.
E sad da li mozete da mi kazete neke programe kojima mogu da istestiram komp kako bih probao da prouzrokujem neki od BSODova koji su kao u ogovima od whocrashed?

[mare037]

Ono što je analayzer napisao. Dakle instaliraj neku igru, probaj kako radi i da li ima problema. Posle pusti FurMark, 3D Mark, Linx, HD Sentiel, HD Tune kako bi video kako se ponaša i ima li BSoD-a.