Šta je novo?
Od:
Filteri

BSoD na 10 min

ILLUVATAR

ILLUVATAR

Slavan
Učlanjen(a)
22.12.2005
Poruke
6
Poena
301
U poslednjih nekoliko dana sam poluduo (kao shto vidite u naslovu je razlog).
Deshava mi se da rachunar zamrze na nekih 30s i onda nastavi sa radom. To je uradio min 10 puta dok sam pisao ovaj post.
Ili BSoD.

Konfiguracija:
ASUS A8V
AMD Ahlon 64 3000+
1GB DDR1 Kingston
GeForce FX5900ZT

2 Sata hard diska:
WD1600 sistemski
WD6400
2 DVD rezacha (Nec i Pioneer)

Napajanje: KungFU 450W


Takodje, pokrenuo sam program koji an analizira .dmp fajlove i dobio ovo:

On Thu 5/6/2010 9:47:39 AM your computer crashed
This was likely caused by the following module: csrss.exe
Bugcheck code: 0xF4 (0x3, 0x86061DA0, 0x86061F14, 0x805FB02E)
Error: CRITICAL_OBJECT_TERMINATION
Dump file: C:\WINDOWS\Minidump\Mini050610-07.dmp
file path: C:\WINDOWS\system32\csrss.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Client Server Runtime Process
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Thu 5/6/2010 5:51:15 AM your computer crashed
This was likely caused by the following module: scsiport.sys
Bugcheck code: 0x7A (0xC02EBBD4, 0xC000009D, 0xBAEF5374, 0x1F1FC860)
Error: KERNEL_DATA_INPAGE_ERROR
Dump file: C:\WINDOWS\Minidump\Mini050610-06.dmp
file path: C:\WINDOWS\system32\drivers\scsiport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: SCSI Port Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Thu 5/6/2010 12:33:59 AM your computer crashed
This was likely caused by the following module: csrss.exe
Bugcheck code: 0xF4 (0x3, 0x86081BE0, 0x86081D54, 0x805FB02E)
Error: CRITICAL_OBJECT_TERMINATION
Dump file: C:\WINDOWS\Minidump\Mini050610-05.dmp
file path: C:\WINDOWS\system32\csrss.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Client Server Runtime Process
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Thu 5/6/2010 12:28:24 AM your computer crashed
This was likely caused by the following module: csrss.exe
Bugcheck code: 0xF4 (0x3, 0x86080DA0, 0x86080F14, 0x805FB02E)
Error: CRITICAL_OBJECT_TERMINATION
Dump file: C:\WINDOWS\Minidump\Mini050610-04.dmp
file path: C:\WINDOWS\system32\csrss.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Client Server Runtime Process
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Thu 5/6/2010 12:25:10 AM your computer crashed
This was likely caused by the following module: csrss.exe
Bugcheck code: 0xF4 (0x3, 0x85F92020, 0x85F92194, 0x805FB02E)
Error: CRITICAL_OBJECT_TERMINATION
Dump file: C:\WINDOWS\Minidump\Mini050610-03.dmp
file path: C:\WINDOWS\system32\csrss.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Client Server Runtime Process
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Thu 5/6/2010 12:19:30 AM your computer crashed
This was likely caused by the following module: csrss.exe
Bugcheck code: 0xF4 (0x3, 0x8605C9D0, 0x8605CB44, 0x805FB02E)
Error: CRITICAL_OBJECT_TERMINATION
Dump file: C:\WINDOWS\Minidump\Mini050610-02.dmp
file path: C:\WINDOWS\system32\csrss.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Client Server Runtime Process
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Thu 5/6/2010 12:06:35 AM your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x7A (0xC02018C8, 0xC000000E, 0x8063263F, 0x298D0860)
Error: KERNEL_DATA_INPAGE_ERROR
Dump file: C:\WINDOWS\Minidump\Mini050610-01.dmp
file path: C:\WINDOWS\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Wed 5/5/2010 4:57:06 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x77 (0xC0000185, 0xC0000185, 0x0, 0x1C39000)
Error: KERNEL_STACK_INPAGE_ERROR
Dump file: C:\WINDOWS\Minidump\Mini050510-09.dmp
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Wed 5/5/2010 4:23:23 PM your computer crashed
This was likely caused by the following module: csrss.exe
Bugcheck code: 0xF4 (0x3, 0x85F6B5A8, 0x85F6B71C, 0x805FB02E)
Error: CRITICAL_OBJECT_TERMINATION
Dump file: C:\WINDOWS\Minidump\Mini050510-08.dmp
file path: C:\WINDOWS\system32\csrss.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Client Server Runtime Process
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Wed 5/5/2010 3:57:14 PM your computer crashed
This was likely caused by the following module: csrss.exe
Bugcheck code: 0xF4 (0x3, 0x85F9B198, 0x85F9B30C, 0x805FB02E)
Error: CRITICAL_OBJECT_TERMINATION
Dump file: C:\WINDOWS\Minidump\Mini050510-07.dmp
file path: C:\WINDOWS\system32\csrss.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Client Server Runtime Process
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Wed 5/5/2010 3:46:54 PM your computer crashed
This was likely caused by the following module: scsiport.sys
Bugcheck code: 0x7A (0xC02EBBD4, 0xC000009D, 0xBAEF5374, 0x256B7860)
Error: KERNEL_DATA_INPAGE_ERROR
Dump file: C:\WINDOWS\Minidump\Mini050510-06.dmp
file path: C:\WINDOWS\system32\drivers\scsiport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: SCSI Port Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Wed 5/5/2010 12:43:15 PM your computer crashed
This was likely caused by the following module: csrss.exe
Bugcheck code: 0xF4 (0x3, 0x8607B210, 0x8607B384, 0x805FB02E)
Error: CRITICAL_OBJECT_TERMINATION
Dump file: C:\WINDOWS\Minidump\Mini050510-05.dmp
file path: C:\WINDOWS\system32\csrss.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Client Server Runtime Process
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Wed 5/5/2010 9:15:56 AM your computer crashed
This was likely caused by the following module: csrss.exe
Bugcheck code: 0xF4 (0x3, 0x86058280, 0x860583F4, 0x805FB02E)
Error: CRITICAL_OBJECT_TERMINATION
Dump file: C:\WINDOWS\Minidump\Mini050510-04.dmp
file path: C:\WINDOWS\system32\csrss.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Client Server Runtime Process
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Wed 5/5/2010 12:20:01 AM your computer crashed
This was likely caused by the following module: scsiport.sys
Bugcheck code: 0x7A (0xC03DDC90, 0xC000009D, 0xF7724374, 0x1F28B860)
Error: KERNEL_DATA_INPAGE_ERROR
Dump file: C:\WINDOWS\Minidump\Mini050510-02.dmp
file path: C:\WINDOWS\system32\drivers\scsiport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: SCSI Port Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Wed 5/5/2010 11:34:01 PM your computer crashed
This was likely caused by the following module: csrss.exe
Bugcheck code: 0xF4 (0x3, 0x85F91020, 0x85F91194, 0x805FB02E)
Error: CRITICAL_OBJECT_TERMINATION
Dump file: C:\WINDOWS\Minidump\Mini050510-03.dmp
file path: C:\WINDOWS\system32\csrss.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Client Server Runtime Process
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Wed 5/5/2010 10:23:59 PM your computer crashed
This was likely caused by the following module: csrss.exe
Bugcheck code: 0xF4 (0x3, 0x86399DA0, 0x86399F14, 0x805FB02E)
Error: CRITICAL_OBJECT_TERMINATION
Dump file: C:\WINDOWS\Minidump\Mini050510-01.dmp
file path: C:\WINDOWS\system32\csrss.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Client Server Runtime Process
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
Kliknite za proširenje...


Prokrenuo sam
Prime95. Proshao (resetovao se jednom sa greshkom 0xF4)
Memchek 2.01. Proshao (10x)
HDD Tune. Bez greshke na 1. (160g)
Kod 2. su mi se deshavale zanimljive situacije. Prvo krene da javlja da je sve OK, pa odjednom svi Bed. Resetujem i pokrenem ponovo, i tada bude sve OK.

Moja predpostavka je da su mozda otishli HDD ili napajanje.

Da li je neko imao nekakva iskustva sa ovim?
Molim za bilo kakvu pomoc...
 
@Admin
Izvinjavam se ako sam promashio podforum. Ako smatrate da treba, premestite temu u Desktop rachunari.
 
hard ili napajanje
 
Prvo raskači taj hard, koji ti javlja bad sektore (koliko vidim taj nije sistemski), pa vidi kako će onda da se ponaša. Ako bude isto, probaj sa nekim drugim napajanjem. I usput proveri temperature. To bih ja uradio za početak.
 
PROVERI DA LI JE NADUVEN ELEKTROLITSKI KONDENZATOR NA PLOCI DOLE DESNO U ODNOSU NA SEVERNI MOST, NEKIH 2-3 cm OD NJEGA.
 
cudno je sto kaze da zamrzne pa najnormalnije nastavi sa radom. to me i plasi da nije samo naduveni elektrolit jedini problem.
 
Taj se obicno prvo naduva na toj ploci. Posledica ili uzrok ne znam ,ali, dva mosfet-a pored njega pocnu da generisu nepravilan oscilogram i posle toga strada severni most koga oni napajaju. Bolje spreciti nego leciti (baciti)...
 
Ako neko zna o cemu se radi zadnja 2 dana komp se stalno restartuje ono sto pise u DMP fajlovima je sledece



On Wed 27.10.2010 0:08:53 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x3452, 0x7620C000, 0xC04069A0, 0x144D30CA)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\102710-41203-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Wed 27.10.2010 0:05:34 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xBE (0xC01DAAD8, 0x33DAF225, 0x80E37A34, 0xC)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
Dump file: C:\Windows\Minidump\102710-39421-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Wed 27.10.2010 23:59:24 your computer crashed
This was likely caused by the following module: storport.sys
Bugcheck code: 0x1A (0x5100, 0xC022D870, 0x2, 0xFF)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\102710-39296-01.dmp
file path: C:\Windows\system32\drivers\storport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Storage Port Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Wed 27.10.2010 23:57:18 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x61940, 0x1512000, 0x135D5804, 0x0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\102710-41171-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Tue 26.10.2010 16:57:11 your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x18 (0x0, 0x847630FA, 0x1, 0x600000)
Error: REFERENCE_BY_POINTER
Dump file: C:\Windows\Minidump\102610-28640-01.dmp
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Tue 26.10.2010 16:22:20 your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x1000008E (0xC0000005, 0x82C82D90, 0x97973B3C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
Dump file: C:\Windows\Minidump\102610-28734-01.dmp
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Tue 26.10.2010 16:18:41 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x3452, 0x5F28000, 0xC040F7B8, 0x21F92824)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\102610-29046-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Tue 26.10.2010 7:46:20 your computer crashed
This was likely caused by the following module: ntfs.sys
Bugcheck code: 0x24 (0x1904FB, 0x80E1B6C8, 0x80E1B2A0, 0x87C8B519)
Error: NTFS_FILE_SYSTEM
Dump file: C:\Windows\Minidump\102610-39906-01.dmp
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Tue 26.10.2010 22:03:17 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x3452, 0x3508000, 0xC04057CC, 0x0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\102610-34031-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Mon 25.10.2010 21:01:09 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x50 (0x6BCF6D90, 0x0, 0x6BCF6D90, 0x8)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Dump file: C:\Windows\Minidump\102510-27578-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Mon 25.10.2010 20:24:46 your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0xC2 (0x7, 0x1097, 0x4A180018, 0xFD6DA420)
Error: BAD_POOL_CALLER
Dump file: C:\Windows\Minidump\102510-28218-01.dmp
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Mon 25.10.2010 20:11:12 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000008E (0xC0000005, 0x82E94BE3, 0x9BD9CAF4, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
Dump file: C:\Windows\Minidump\102510-29156-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
 
Poslednja izmena:
Morate se prijaviti ili registrovati da odgovorite ovde.
Nazad
Vrh Dno