(riješeno) BSOD problem
 

Ovo mi se javlja (mislim pojavio se BSOD ali ovo je u safe mode-u windows lijepse ispiso, sad kak da provjerim jel hard otiso vrit il je nadam se neki softverski problem (moram se nadat premda su sanse 1% :( ).

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1050

Additional information about the problem:
BCCode: f4
BCP1: 0000000000000003
BCP2: FFFFFA80088F08F0
BCP3: FFFFFA80088F0BD0
BCP4: FFFFF800039DB460
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\111812-16801-01.dmp
C:\Users\Zen\AppData\Local\Temp\WER-32526-0.sysdata.xml

Ovo mi je sad reko WhoCrashed program, mozete mi objasnit koj mi je slijedeci korak, nadam se da sam vam dosta stvari sad stavio da bi dobio neki odgovor :/

On Sun 18.11.2012. 16:42:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111812-16801-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA80088F08F0, 0xFFFFFA80088F0BD0, 0xFFFFF800039DB460)
Error: CRITICAL_OBJECT_TERMINATION
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 process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 18.11.2012. 16:42:16 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: 0xF4 (0x3, 0xFFFFFA80088F08F0, 0xFFFFFA80088F0BD0, 0xFFFFF800039DB460)
Error: CRITICAL_OBJECT_TERMINATION
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 11.11.2012. 13:02:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111112-18049-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA80087C2B30, 0xFFFFFA80087C2E10, 0xFFFFF80002589460)
Error: CRITICAL_OBJECT_TERMINATION
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 process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

moze mi netko bar pojasnit ovo :D

Evo nakon dosta ignoriranja a mislim da bi ovo bar mogli pogledat neki strucnjaci, iz debugg toolsa je, sad mi samo trebate rec u cemu je problem sa tim winitom i kako ga popravit hvala. Ajde nisam jos izgubio nadu u ovaj forum :(


Microsoft (R) Windows Debugger Version 6.2.9200.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Zen\Desktop\120912-15272-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.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800`03059000 PsLoadedModuleList = 0xfffff800`0329d670
Debug session time: Sun Dec 9 11:37:08.361 2012 (UTC + 1:00)
System Uptime: 0 days 2:39:29.571
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa800a51fb30, fffffa800a51fe10, fffff800033d7460}

----- ETW minidump data unavailable-----
Probably caused by : wininit.exe

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

2: 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: fffffa800a51fb30, Terminating object
Arg3: fffffa800a51fe10, Process image file name
Arg4: fffff800033d7460, Explanatory message (ascii)

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

----- ETW minidump data unavailable-----

PROCESS_OBJECT: fffffa800a51fb30

IMAGE_NAME: wininit.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: wininit

FAULTING_MODULE: 0000000000000000

PROCESS_NAME: wininit.exe

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

BUGCHECK_STR: 0xF4_c0000005

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`1a197e38 fffff800`0345f822 : 00000000`000000f4 00000000`00000003 fffffa80`0a51fb30 fffffa80`0a51fe10 : nt!KeBugCheckEx
fffff880`1a197e40 fffff800`0340be0b : ffffffff`ffffffff fffffa80`0b33eb50 fffffa80`0a51fb30 fffffa80`0a51fb30 : nt!PspCatchCriticalBreak+0x92
fffff880`1a197e80 fffff800`0338af04 : ffffffff`ffffffff 00000000`00000001 fffffa80`0a51fb30 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x176e6
fffff880`1a197ed0 fffff800`030d7253 : fffffa80`0a51fb30 fffff800`c0000005 fffffa80`0b33eb50 00000000`00c00440 : nt!NtTerminateProcess+0xf4
fffff880`1a197f50 fffff800`030d3810 : fffff800`03122b7f fffff880`1a198a38 fffff880`1a198790 fffff880`1a198ae0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`1a1980e8 fffff800`03122b7f : fffff880`1a198a38 fffff880`1a198790 fffff880`1a198ae0 00000000`00c01f50 : nt!KiServiceLinkage
fffff880`1a1980f0 fffff800`030d7642 : fffff880`1a198a38 00000000`0000aab7 fffff880`1a198ae0 00000000`00c01a28 : nt! ?? ::FNODOBFM::`string'+0x488a4
fffff880`1a198900 fffff800`030d61ba : 00000000`00000001 00000000`00c00b58 00000000`77c9ff01 00000000`0000aab7 : nt!KiExceptionDispatch+0xc2
fffff880`1a198ae0 00000000`77b98e3d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`00c00b60 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77b98e3d


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: X64_0xF4_c0000005_IMAGE_wininit.exe

BUCKET_ID: X64_0xF4_c0000005_IMAGE_wininit.exe

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

prvo, nisi konfu naveo. Ova iz my komp?
drugo - niš pametno iz svega ovoga osim da je neki od windows procesa po*izdio ;)
Najlakše - formati i čisti reinstal windowsa, pa testiraj. Pa jedan po jedan driver gore dok ga ne srušiš opet ili dok ne skužiš jednostavno da je bilo vrijeme za reinstal windowsa.

za to postoji moj komp da se procita, ne? :D

a budem reinstall pa vidio. sto je najgore, ovo sam sve novo kupio i samo problemi, trebo sam ostat na pentium 4 :P

Zavrti neki live OS, tako ćeš znati da li je kvar HW ili SW prirode. To bi bilo prvo, a za dalje je lako.

eto riknul je hdd ja mislim, ne pojavljuje se u UEFI/boisu( javi se nekad kad restartam al kad opet restartam da nasnimim windowse nestane, kablovi i utori na mbo nisu provjereno), to bi znacilo da je hard otiso vrit kolko sam guglo i procito clanaka, jos samo da ovdje potvrdim i u kupnju novog.

Sutra mi frend dolazi pa cu provjerit njegov hard jel radi u mojoj kanti i ako radi a 99% je da ce radit to je to 100 % :D