Win Xp, Bsod 3 Min Po Starcie Systemu

[guldur]

Witam,

Sprawa wyglada tak:

-Partycja C: windows kiedys instalowany, dziala bez problemow, wlasnie z niego pisze tego posta

-Partycja D: windows instalowany pozniej od tego co jest na C, ale korzystam glownie z niego. Od pewnego czasu (stalo sie to nagle) jakies 3 min po odpaleniu sie wywala BSOD-a i sie resetuje.

 

Kod bledu: STOP: 0x000000F4

Zawartosc pliku minidump:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86Copyright (c) Microsoft Corporation. All rights reserved.Loading Dump File [E:\WINDOWS\Minidump\Mini032309-02.dmp]Mini Kernel Dump File: Only registers and stack trace are availableSymbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbolsExecutable search path is: Windows XP Kernel Version 2600 (Service Pack 2) MP (4 procs) Free x86 compatibleProduct: WinNt, suite: TerminalServer SingleUserTSBuilt by: 2600.xpsp_sp2_gdr.080814-1233Machine Name:Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700Debug session time: Mon Mar 23 13:57:09.562 2009 (GMT+1)System Uptime: 0 days 0:03:14.559Loading Kernel Symbols.......................................................................................................................................Loading User SymbolsLoading unloaded module list.............********************************************************************************																			 **						Bugcheck Analysis									**																			 ********************************************************************************Use !analyze -v to get detailed debugging information.BugCheck F4, {3, 8a7a76a0, 8a7a7814, 805d1204}unable to get nt!KiCurrentEtwBufferOffsetunable to get nt!KiCurrentEtwBufferBaseProbably caused by : csrss.exeFollowup: MachineOwner---------

Detailed debugged information:

3: kd> !analyze -v********************************************************************************																			 **						Bugcheck Analysis									**																			 ********************************************************************************CRITICAL_OBJECT_TERMINATION (f4)A process or thread crucial to system operation has unexpectedly exited or beenterminated.Several processes and threads are necessary for the operation of thesystem; when they are terminated (for any reason), the system can nolonger function.Arguments:Arg1: 00000003, ProcessArg2: 8a7a76a0, Terminating objectArg3: 8a7a7814, Process image file nameArg4: 805d1204, Explanatory message (ascii)Debugging Details:------------------unable to get nt!KiCurrentEtwBufferOffsetunable to get nt!KiCurrentEtwBufferBasePROCESS_OBJECT: 8a7a76a0IMAGE_NAME:  csrss.exeDEBUG_FLR_IMAGE_TIMESTAMP:  0MODULE_NAME: csrssFAULTING_MODULE: 00000000 PROCESS_NAME:  csrss.exeEXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod "0x%08lx" odwoBUGCHECK_STR:  0xF4_C0000005CUSTOMER_CRASH_COUNT:  2DEFAULT_BUCKET_ID:  DRIVER_FAULTSTACK_TEXT:  b701ad00 805d03ab 000000f4 00000003 8a7a76a0 nt!KeBugCheckEx+0x1bb701ad24 805d12af 805d1204 8a7a76a0 8a7a7814 nt!PspCatchCriticalBreak+0x75b701ad54 8054088c 8a7a78e8 c0000005 00cdebcc nt!NtTerminateProcess+0x7db701ad54 7c90eb94 8a7a78e8 c0000005 00cdebcc nt!KiFastCallEntry+0xfcWARNING: Frame IP not in any known module. Following frames may be wrong.00cdebcc 00000000 00000000 00000000 00000000 0x7c90eb94STACK_COMMAND:  kbFOLLOWUP_NAME:  MachineOwnerFAILURE_BUCKET_ID:  0xF4_C0000005_IMAGE_csrss.exeBUCKET_ID:  0xF4_C0000005_IMAGE_csrss.exeFollowup: MachineOwner---------

SMART dysku z programu Victoria:

SAMSUNG HD322HJ   S17AJDWQ211399-------------------------------------------------------------------------  ID	  Name				   Value  Worst  Tresh	   Raw	Health-------------------------------------------------------------------------  1 Raw read error rate		   100	100	 51		   26   •••••   3 Spin-up time				   95	 95	 11		 2570   ••••    4 Number of spin-up times	   100	100	  0		  370   •••••   5 Reallocated sector count	  100	100	 10			0   •••••   7 Seek error rate			   100	100	 51			0   •••••   8 Seek time perfomance		  100	100	 15			0   •••••   9 Power-on time				  99	 99	  0		 5180   ••••  10 Spin-up retries			   100	100	 51			0   ••••• 11 Recalibration retries		 100	100	  0			1   ••••• 12 Start/stop count			  100	100	  0		  326   ••••• 13 Soft read error rate		  100	100	  0		   26   ••••• 183 unknown attribut			  100	100	  0			0   ••••• 184 End-to-End error			  100	100	 99			0   ••••• 187 Reported UNC error			100	100	  0		   27   ••••• 188 Command timeout			   100	100	  0			0   ••••• 190 Airflow temperature			77	 67	  0	23°C/73°F   ••••  194 HDA Temperature				74	 66	  0	26°C/78°F   ••••  195 Hardware ECC recovered		100	100	  0	 56827271   ••••• 196 Reallocated event count	   100	100	  0			0   ••••• 197 Current pending sectors	   100	100	  0			1   ••••• 198 Offline scan UNC sectors	  100	100	  0			0   ••••• 199 Ultra DMA CRC errors		  100	100	  0			0   ••••• 200 Write error rate			  100	100	  0			0   ••••• 201 Off-track errors count		100	 99	  0			0   •••••

Aczkolwiek to raczej soft skoro na drugiej instalce dziala poprawnie. Dodam jeszcze, ze tryb awaryjny instalki spod D tez dziala poprawnie, tylko przy "normalnym" odpaleniu sie wysypuje.