Iznenadni napad BSOD-ova

poruka: 2
|
čitano: 1.056
|
moderatori: pirat, XXX-Man
1
+/- sve poruke
ravni prikaz
starije poruke gore
12 godina
protjeran
offline
Iznenadni napad BSOD-ova

Prvo burazu na laptopu krenu random bsodovi, danas mu reinstalliram windowse, i taman doslovno kako sam zavrsio, moj komp u pozadini zasteka glazba i onaj pitomi blue screen na windows 8.1. " ntfs_file_system error" i nista bez puno panike malo googlao, kad nakon sat vremena jos jedan, dok sam surfao po netu, ali ovaj put  kernel security check failure  onda sam se vec zabrinuo, i odma i to googlao, nakon pola sata jos jedan " Kmode exception not handled " i odma pri bootanju JOŠ JEDAN !

Od onda nije bilo nista probao sam reinstall grafickih drivera, svi ostali updatei su up to date, framework naj noviji, sve 5. Što me jako i cudi nista hardwareski ni softwareski nisam mjenjao/instaliravao/skidao u zadnje vrijeme, baš iz cista mira. I sve komponente su relativno nove, e sad znam sta ce te svi optužit za razlog tolikih bsodova - imam 2 razlicita sticka ram memorije, jedni su g.skill 1333mhz 4gb 1.5v, a drugi su zabunom kupljeni jer je na stranici pisalo 1.5v a na kraju mi stigli Kingston 1600mhz 4gb (koje sam i narucio) ali od 1.32v. U biosu sam spustio ovu da obje rade 1333mhz, a vjerujuci googleu i forumima 1.3v rami mogu raditi kompatibilno sa 1.5v bez problema, jer i neke maticne podrzavaju naj manje 1.5v RAM slotove... Tako da ne vjerujem da je u njima problem a i imam ih vec preko 2mj. rade perfektno nikad problema sa njima - nikad ni 1 BSOD, testirani sa +memtest86 par krugova = sve 5.

 

Tako da sam jako zbunjen, imam i mjesec dana stare win 8.1 radili super, evo trenutno jos radi, samo me to jako uznemirilo i hipohondricni ja sam odma uzrokovao "rikavanje hdda, ili maticne a mozda i graficke, a ni rami nisu na cistom"

Probao sam chkdsk /f - obavilo, resetirao se poslje i nakon toga jos nije bio ni jedan BS

probao malware bytes, scanirao avirom, sredio registry sa ccleanerom, oslobodio hdd ne bitnih stvari.

 

U komentar cu kopirati dump sa svim logovima od bsodova koje sam iščitao sa " Whocrashed " i "BlueScreenViewerom" i oboje su izbacili iste uzrocnike: ntoskrnl. exe i ntkrnlmp. exe

Neki kazu da je to razlog drivera koji se ne podudaraju - Ali kako nisam nikakve nove instaliravao duze vrijeme
Neki kazu da je do hardwarea - Kako ? nisam nista dirao ni mjenjao

 

Eto ako ima neko dobar savjet, puno bi mi pomogao :)

 
0 0 hvala 0
12 godina
protjeran
offline
Iznenadni napad BSOD-ova

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

computer name: DELBOY
windows version: Windows 8.1 , 6.2, build: 9200
windows dir: C:\Windows
Hardware: ASRock, 960GM-VGS3 FX
CPU: AuthenticAMD AMD Phenom(tm) II X4 965 Processor AMD586, level: 16
4 logical processors, active mask: 15
RAM: 8589131776 total
VM: 2147352576, free: 1911091200




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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Mon 26.5.2014. 22:20:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052714-32937-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0x139 (0x3, 0xFFFFD001379BF890, 0xFFFFD001379BF7E8, 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 Mon 26.5.2014. 22:20:48 GMT 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: 0x139 (0x3, 0xFFFFD001379BF890, 0xFFFFD001379BF7E8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
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 Mon 26.5.2014. 21:52:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052614-15515-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0xBD87)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80089C1ED87, 0xFFFFD000AD7BC428, 0xFFFFD000AD7BBC30)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Mode Driver Framework Runtime
Bug check description: This indicates that a kernel-mode program 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 26.5.2014. 21:48:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052614-22953-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0x139 (0x3, 0xFFFFD001111BF360, 0xFFFFD001111BF2B8, 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.

 
0 0 hvala 0
1
Nova poruka
E-mail:
Lozinka:
 
vrh stranice