HD PROBLEM (mhdd)

• 0Niko još nije pohvalio poruku.
  Registruj se da bi pohvalio/la poruku!

imam odredjeni skup problema i vec mesecima se borim da identifikujem da li je problem hardverske ili softverske prirode

masina radi lepo, win 7 64 bitni, konfiguracija je:
MSI Phenom K9A2 Platinum V2 ploča
AMD Phenom 9550 Quad Core 2.2 Ghz
Kingston HyperX 1gb RAM x 2
Gainward 9800gt
jedan ATA i jedan SATA hdd, oba Western Digital, jedan stari i novi
450W Chieftec napajanje

desavaju se odredjeni problemi s kojima izlazim na kraj ali vec ovo sve pocinje da me iritira jer nisam pametan sta dovodi do njih

1. sistem isflesira tipa da se sve ukljucujuci i kursor zamrzne, prodje minut i onda se sve odmrzne i ubrzano sistem zavrsi sve što je počeo. u 99% dok je ukljucen chrome.
2. ako se ne odmrzne pojavi se BSOD
3. posle toga boot sekvenca je izmenjena i vracena prvo na flopi, pa drugi hard, pa onda SATA na kome mi je win 7. danas mi se cak desilo da mi komp vidi SATA hdd ali da ne mogu da ga namestim u boot sekvenci.
4. nakon toga boot up mi je spor, chkdisk ne prijavljuje nista lose i sve ide normalno dok se ponovo ne desi isto.
5. nikad mi se to nije desilo dok igram zahtevne igre ili radim bilo sta drugo, samo dok je ukljucen chrome.
6. problem obicno resava gasenje kompjutera i ponovno paljenje, eventualno podesavanje boot sekvence u BIOSu.

svi hardovi su zdravi, win 7 je instaliran na novom velikom hardu
nemam problema sa nedostatkom prostora, nemam problema sa virusima i crvima, redovno defragmentujem hddove, sandra i astra32 ne javljaju nikakve probleme. probao sam da menjam sata kablove, drugacije portove, radi sve ok odredjeni period (nedelju, dve) i onda bum padne sistem.

desava se da pojedini usb prikljuchci ne rade, ili rade tipa da vide da je nesto ukljuceno ali ne mogu da identifikuju sta. kad to isto ukljucim u drugi usb, sve kul. a i memorija na grafickoj mi je vec jednom izgorela pa sam morao da kupujem drugu.

potpuno sam zbunjen.

• 0Niko još nije pohvalio poruku.
  Registruj se da bi pohvalio/la poruku!

skini malware-bytes-anti-malware i skeniraj tvoj sistem pa nam izbaci izvjestaj ...

• 1Ovo se svidja korisniku: A.L.
  
  Registruj se da bi pohvalio/la poruku!

androlegend ::skini malware-bytes-anti-malware i skeniraj tvoj sistem pa nam izbaci izvjestaj ...

Nema potrebe da ovo preporucujes.

Ako ima indikacija da je problem do malware-a neko od AMF clanova ce ga uputiti u Ambulantu...

• 1Ovo se svidja korisniku: A.L.
  
  Registruj se da bi pohvalio/la poruku!

Vlada ::2. ako se ne odmrzne pojavi se BSOD

Da vidimo mozemo li saznati nesto vise iz tog BSOD-a koji se pojavljuje - sta ga uzrokuje. Uradi sledece:


Preuzmi instalaciju za WhoCrashed program sa sledeceg linka:
http://www.resplendence.com/download/whocrashedSetup.exe
Ovaj program ce analizom pokusati proveriti koji drajver je uzrocnik greske.
Napomena: ovaj program zahteva instalaciju.


Dvoklikom pokreni instalaciju i klikni Next. Stikliraj opciju I Accept the agreement pa zatim ponovo na Next.
Program instaliraj na onu lokaciju i pod onim imenom koju ti program ponudi.
Klikni na Next i u sledecem prozoru klikni Next
Stikliraj opciju Create a Desktop Icon i potom klikni na Next pa zatim na Install.




Kada instaliras WhoCrashed program,pokreni ga.

Napomena: Ukoliko ti program izbaci obavestenje koje bi trebalo da izgleda ovako:

Klikni na Download the requested file from Microsoft site now i pricekaj da se proces
preuzimanja dodatnih fajlova i njihova instalacija dovrsi.


Kada se program pokrene klikni na dugme Analyze.
Kada program zavrsi analizu izbacice ti prozor sa obavestenjem. Klikni Ok.

Desni klik na prostor stranice programa sa izvestajem i izaberi opciju Select All.
Desni klik na prostor stranice programa sa izvestajem i izaberi opciju Copy
Otvori novi notepad i izaberi opciju Paste da bi kopirao sadrzaj loga u notepad.

Sada mozes zatvoriti program.

Okaci notepad sa sadrzajem loga u sledecu poruku.





Citat:sta vi mislite?


Imas li uredno instalirane najnovije drajvere za tvoje komponente koje si skinuo sa sajta proizvodjaca komponenti (ne sa diska koji si dobio uz plocu, grafiku, itd)?









Takodje, uradi sledece, da bi smo imali nekih konkretnih informacija o sistemu i instaliranim aplikacijama ...

Skini MiniToolBox na Desktop;
Pokreni ga dvoklikom, strikliraj sve ponudjene stavke i klikni na Go;
Nakon sto aplikacija zavrsi rad, izbacice izvestaj u Notepad-u; taj izvestaj okaci u sledecoj poruci da pogledamo.

• 0Niko još nije pohvalio poruku.
  Registruj se da bi pohvalio/la poruku!

Napisano: 09 Apr 2012 18:34

cim sam instalirao whocrashed pojavio mi se baloncic koji kaze da je C:\windows\system32\drivers\en-us koruptovan i da bi trebalo da pokrenem chkdisk
evo reporta iz programa:

Citat:Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Sun 8.4.2012 16:43:12 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x7E (0xFFFFFFFFC000001D, 0xFFFFF88000FCF93C, 0xFFFFF8800318E428, 0xFFFFF8800318DC90)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: Unknown .
Google query: Unknown SYSTEM_THREAD_EXCEPTION_NOT_HANDLED




On Mon 27.2.2012 20:49:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022712-36551-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x11837A)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000006, 0xFFFFF8000417737A, 0xFFFFF880009A9808, 0xFFFFF880009A9070)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Wed 8.2.2012 15:00:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020812-37440-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8003D729E0, 0xFFFFFA8003D72CC0, 0xFFFFF8000438B300)
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sun 4.12.2011 0:56:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120411-19812-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x7A (0xFFFFF6FC50034178, 0xFFFFFFFFC0000185, 0x1E831880, 0xFFFFF8A00682FBC6)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sat 3.12.2011 20:13:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120311-18579-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x7A (0xFFFFF6FB800083F8, 0xFFFFFFFFC000000E, 0x3B050880, 0xFFFFF7000107FFF8)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sat 3.12.2011 18:27:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120311-18376-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xF9830)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000006, 0xFFFFF8000414B830, 0xFFFFF880046F3698, 0xFFFFF880046F2F00)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Fri 11.11.2011 23:45:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111211-22105-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x3B (0xC0000095, 0xFFFFF80004308CBD, 0xFFFFF8800A1D2FA0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 which cannot be identified at this time.


On Fri 11.11.2011 14:03:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111111-22729-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8002B8B060, 0xFFFFF80005573518, 0xFFFFFA80036AF010)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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 which cannot be identified at this time.


On Tue 4.10.2011 15:58:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100411-20046-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x7A (0xFFFFF6FC5000D668, 0xFFFFFFFFC0000185, 0x3E27880, 0xFFFFF8A001ACD000)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sun 2.10.2011 16:41:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100211-19250-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA800364AA00, 0xFFFFF8000556C518, 0xFFFFFA8001FB5C10)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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 which cannot be identified at this time.


On Wed 28.9.2011 12:54:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092811-31106-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA800302C520, 0xFFFFF80005579518, 0xFFFFFA8002237C10)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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 which cannot be identified at this time.


On Fri 23.9.2011 21:22:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092311-22323-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8003876A00, 0xFFFFF80000B9C518, 0xFFFFFA80048101F0)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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 which cannot be identified at this time.


On Thu 15.9.2011 20:05:45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091511-20233-01.dmp
This was probably caused by the following module: Unknown (0xFFFFF8800416C7F2)
Bugcheck code: 0x7E (0xFFFFFFFFC000001D, 0xFFFFF8800101FF3C, 0xFFFFF8800338E9E8, 0xFFFFF8800338E250)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: Unknown .
Google query: Unknown SYSTEM_THREAD_EXCEPTION_NOT_HANDLED




On Thu 15.9.2011 0:23:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091511-25474-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8002BBBA00, 0xFFFFF80000B9C518, 0xFFFFFA8002E52670)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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 which cannot be identified at this time.


On Mon 12.9.2011 23:46:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091311-23540-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x7A (0xFFFFF6FC500269E8, 0xFFFFFFFFC0000185, 0x2A9CF820, 0xFFFFF8A004D3D9D6)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


The following dump files were found but could not be read. These files may be corrupt:
C:\Windows\Minidump\101910-18907-01.dmp



i evo iz minitoolboxa:

Citat:MiniToolBox by Farbar Version: 18-01-2012
Ran by CyberJack (administrator) on 09-04-2012 at 18:31:04
Microsoft Windows 7 Ultimate (X64)
Boot Mode: Normal
***************************************************************************

========================= Flush DNS: ===================================

========================= IE Proxy Settings: ==============================

Proxy is not enabled.
No Proxy Server is set.

"Reset IE Proxy Settings": IE Proxy Settings were reset.

========================= FF Proxy Settings: ==============================


"Reset FF Proxy Settings": Firefox Proxy settings were reset.

========================= Hosts content: =================================



========================= IP Configuration: ================================

MT882 = Local Area Connection 7 (Connected)
Realtek RTL8168B/8111B Family PCI-E Gigabit Ethernet NIC (NDIS 6.20) = Local Area Connection (Media disconnected)
========================= Winsock entries =====================================

Catalog5 01 C:\Windows\SysWOW64\NLAapi.dll [51712] (Microsoft Corporation)
Catalog5 02 C:\Windows\SysWOW64\mswsock.dll [232448] (Microsoft Corporation)
Catalog5 03 C:\Windows\SysWOW64\winrnr.dll [20992] (Microsoft Corporation)
Catalog5 04 C:\Windows\SysWOW64\napinsp.dll [52224] (Microsoft Corporation)
Catalog5 05 C:\Windows\SysWOW64\pnrpnsp.dll [65024] (Microsoft Corporation)
Catalog5 06 C:\Windows\SysWOW64\pnrpnsp.dll [65024] (Microsoft Corporation)
Catalog5 07 C:\Program Files (x86)\Bonjour\mdnsNSP.dll [152864] (Apple Inc.)
Catalog9 01 C:\Windows\SysWOW64\mswsock.dll [232448] (Microsoft Corporation)
Catalog9 02 C:\Windows\SysWOW64\mswsock.dll [232448] (Microsoft Corporation)
Catalog9 03 C:\Windows\SysWOW64\mswsock.dll [232448] (Microsoft Corporation)
Catalog9 04 C:\Windows\SysWOW64\mswsock.dll [232448] (Microsoft Corporation)
Catalog9 05 C:\Windows\SysWOW64\mswsock.dll [232448] (Microsoft Corporation)
Catalog9 06 C:\Windows\SysWOW64\mswsock.dll [232448] (Microsoft Corporation)
Catalog9 07 C:\Windows\SysWOW64\mswsock.dll [232448] (Microsoft Corporation)
Catalog9 08 C:\Windows\SysWOW64\mswsock.dll [232448] (Microsoft Corporation)
Catalog9 09 C:\Windows\SysWOW64\mswsock.dll [232448] (Microsoft Corporation)
Catalog9 10 C:\Windows\SysWOW64\mswsock.dll [232448] (Microsoft Corporation)
x64-Catalog5 01 C:\Windows\System32\NLAapi.dll [70144] (Microsoft Corporation)
x64-Catalog5 02 C:\Windows\System32\mswsock.dll [320000] (Microsoft Corporation)
x64-Catalog5 03 C:\Windows\System32\winrnr.dll [28672] (Microsoft Corporation)
x64-Catalog5 04 C:\Windows\System32\napinsp.dll [68096] (Microsoft Corporation)
x64-Catalog5 05 C:\Windows\System32\pnrpnsp.dll [86016] (Microsoft Corporation)
x64-Catalog5 06 C:\Windows\System32\pnrpnsp.dll [86016] (Microsoft Corporation)
x64-Catalog5 07 C:\Program Files\Bonjour\mdnsNSP.dll [193824] (Apple Inc.)
x64-Catalog9 01 C:\Windows\System32\mswsock.dll [320000] (Microsoft Corporation)
x64-Catalog9 02 C:\Windows\System32\mswsock.dll [320000] (Microsoft Corporation)
x64-Catalog9 03 C:\Windows\System32\mswsock.dll [320000] (Microsoft Corporation)
x64-Catalog9 04 C:\Windows\System32\mswsock.dll [320000] (Microsoft Corporation)
x64-Catalog9 05 C:\Windows\System32\mswsock.dll [320000] (Microsoft Corporation)
x64-Catalog9 06 C:\Windows\System32\mswsock.dll [320000] (Microsoft Corporation)
x64-Catalog9 07 C:\Windows\System32\mswsock.dll [320000] (Microsoft Corporation)
x64-Catalog9 08 C:\Windows\System32\mswsock.dll [320000] (Microsoft Corporation)
x64-Catalog9 09 C:\Windows\System32\mswsock.dll [320000] (Microsoft Corporation)
x64-Catalog9 10 C:\Windows\System32\mswsock.dll [320000] (Microsoft Corporation)

========================= Event log errors: ===============================

Application errors:
==================
Error: (04/09/2012 06:24:13 PM) (Source: Application Error) (User: )
Description: Windows cannot access the file C:\Windows\System32\dssenh.dll for one of the following reasons:
there is a problem with the network connection, the disk that the file is stored on, or the storage
drivers installed on this computer; or the disk is missing.
Windows closed the program Host Process for Windows Services because of this error.

Program: Host Process for Windows Services
File: C:\Windows\System32\dssenh.dll

The error value is listed in the Additional Data section.
User Action
1. Open the file again.
This situation might be a temporary problem that corrects itself when the program runs again.
2.
If the file still cannot be accessed and
- It is on the network,
your network administrator should verify that there is not a problem with the network and that the server can be contacted.
- It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.
3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.
4. If the problem persists, restore the file from a backup copy.
5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for
further assistance.

Additional Data
Error value: C0000185
Disk type: 3

Error: (04/09/2012 06:24:13 PM) (Source: Application Error) (User: )
Description: Faulting application name: svchost.exe_wuauserv, version: 6.1.7600.16385, time stamp: 0x4a5bc3c1
Faulting module name: CRYPTSP.dll, version: 6.1.7600.16385, time stamp: 0x4a5bdf96
Exception code: 0xc0000006
Fault offset: 0x000000000000879b
Faulting process id: 0xe28
Faulting application start time: 0xsvchost.exe_wuauserv0
Faulting application path: svchost.exe_wuauserv1
Faulting module path: svchost.exe_wuauserv2
Report Id: svchost.exe_wuauserv3

Error: (04/09/2012 06:21:28 PM) (Source: Application Error) (User: )
Description: Windows cannot access the file C:\Windows\System32\shlwapi.dll for one of the following reasons:
there is a problem with the network connection, the disk that the file is stored on, or the storage
drivers installed on this computer; or the disk is missing.
Windows closed the program Windows Explorer because of this error.

Program: Windows Explorer
File: C:\Windows\System32\shlwapi.dll

The error value is listed in the Additional Data section.
User Action
1. Open the file again.
This situation might be a temporary problem that corrects itself when the program runs again.
2.
If the file still cannot be accessed and
- It is on the network,
your network administrator should verify that there is not a problem with the network and that the server can be contacted.
- It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.
3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.
4. If the problem persists, restore the file from a backup copy.
5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for
further assistance.

Additional Data
Error value: C0000185
Disk type: 3

Error: (04/09/2012 06:21:28 PM) (Source: Application Error) (User: )
Description: Windows cannot access the file C:\Windows\System32\crypt32.dll for one of the following reasons:
there is a problem with the network connection, the disk that the file is stored on, or the storage
drivers installed on this computer; or the disk is missing.
Windows closed the program Host Process for Windows Services because of this error.

Program: Host Process for Windows Services
File: C:\Windows\System32\crypt32.dll

The error value is listed in the Additional Data section.
User Action
1. Open the file again.
This situation might be a temporary problem that corrects itself when the program runs again.
2.
If the file still cannot be accessed and
- It is on the network,
your network administrator should verify that there is not a problem with the network and that the server can be contacted.
- It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.
3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.
4. If the problem persists, restore the file from a backup copy.
5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for
further assistance.

Additional Data
Error value: C0000185
Disk type: 3

Error: (04/09/2012 06:21:28 PM) (Source: Application Error) (User: )
Description: Faulting application name: Explorer.EXE, version: 6.1.7600.16768, time stamp: 0x4d688122
Faulting module name: ntdll.dll, version: 6.1.7600.16915, time stamp: 0x4ec4b137
Exception code: 0xc0000006
Fault offset: 0x0000000000034e8f
Faulting process id: 0x128
Faulting application start time: 0xExplorer.EXE0
Faulting application path: Explorer.EXE1
Faulting module path: Explorer.EXE2
Report Id: Explorer.EXE3

Error: (04/09/2012 06:21:28 PM) (Source: Application Error) (User: )
Description: Faulting application name: svchost.exe_wuauserv, version: 6.1.7600.16385, time stamp: 0x4a5bc3c1
Faulting module name: ntdll.dll, version: 6.1.7600.16915, time stamp: 0x4ec4b137
Exception code: 0xc0000006
Fault offset: 0x00000000000158e5
Faulting process id: 0xe0
Faulting application start time: 0xsvchost.exe_wuauserv0
Faulting application path: svchost.exe_wuauserv1
Faulting module path: svchost.exe_wuauserv2
Report Id: svchost.exe_wuauserv3

Error: (04/09/2012 05:01:10 PM) (Source: Microsoft-Windows-LoadPerf) (User: SYSTEM)SYSTEM
Description: Unloading the performance counter strings for service WmiApRpl (WmiApRpl) failed. The first DWORD in the Data section contains the error code.

Error: (04/09/2012 05:01:10 PM) (Source: Microsoft-Windows-LoadPerf) (User: SYSTEM)SYSTEM
Description: The performance strings in the Performance registry value is corrupted when process Performance extension counter provider. The BaseIndex value from the Performance registry is the first DWORD in the Data section, LastCounter value is the second DWORD in the Data section, and LastHelp value is the third DWORD in the Data section.

Error: (04/09/2012 04:57:17 PM) (Source: Application Error) (User: )
Description: Faulting application name: DkService.exe, version: 14.0.909.0, time stamp: 0x4ca6b84b
Faulting module name: DkService.exe, version: 14.0.909.0, time stamp: 0x4ca6b84b
Exception code: 0x80000003
Fault offset: 0x0000000000035712
Faulting process id: 0xf60
Faulting application start time: 0xDkService.exe0
Faulting application path: DkService.exe1
Faulting module path: DkService.exe2
Report Id: DkService.exe3

Error: (04/09/2012 04:48:46 PM) (Source: Microsoft-Windows-LoadPerf) (User: SYSTEM)SYSTEM
Description: Unloading the performance counter strings for service WmiApRpl (WmiApRpl) failed. The first DWORD in the Data section contains the error code.


System errors:
=============
Error: (04/09/2012 06:29:45 PM) (Source: Service Control Manager) (User: )
Description: The Service Control Manager tried to take a corrective action (Restart the service) after the unexpected termination of the Windows Management Instrumentation service, but this action failed with the following error:
%%1056

Error: (04/09/2012 06:29:45 PM) (Source: Service Control Manager) (User: )
Description: The Service Control Manager tried to take a corrective action (Restart the service) after the unexpected termination of the Multimedia Class Scheduler service, but this action failed with the following error:
%%1056

Error: (04/09/2012 06:29:45 PM) (Source: Service Control Manager) (User: )
Description: The Service Control Manager tried to take a corrective action (Restart the service) after the unexpected termination of the User Profile Service service, but this action failed with the following error:
%%1056

Error: (04/09/2012 06:27:27 PM) (Source: Ntfs) (User: )
Description: The file system structure on the disk is corrupt and unusable.
Please run the chkdsk utility on the volume \Device\HarddiskVolume1.

Error: (04/09/2012 06:27:27 PM) (Source: Ntfs) (User: )
Description: The file system structure on the disk is corrupt and unusable.
Please run the chkdsk utility on the volume \Device\HarddiskVolume1.

Error: (04/09/2012 06:27:27 PM) (Source: Ntfs) (User: )
Description: The file system structure on the disk is corrupt and unusable.
Please run the chkdsk utility on the volume \Device\HarddiskVolume1.

Error: (04/09/2012 06:27:27 PM) (Source: Ntfs) (User: )
Description: The file system structure on the disk is corrupt and unusable.
Please run the chkdsk utility on the volume \Device\HarddiskVolume1.

Error: (04/09/2012 06:27:27 PM) (Source: Ntfs) (User: )
Description: The file system structure on the disk is corrupt and unusable.
Please run the chkdsk utility on the volume \Device\HarddiskVolume1.

Error: (04/09/2012 06:27:27 PM) (Source: Ntfs) (User: )
Description: The file system structure on the disk is corrupt and unusable.
Please run the chkdsk utility on the volume \Device\HarddiskVolume1.

Error: (04/09/2012 06:27:27 PM) (Source: Ntfs) (User: )
Description: The file system structure on the disk is corrupt and unusable.
Please run the chkdsk utility on the volume \Device\HarddiskVolume1.


Microsoft Office Sessions:
=========================
Error: (04/09/2012 06:24:13 PM) (Source: Application Error)(User: )
Description: C:\Windows\System32\dssenh.dllHost Process for Windows ServicesC00001853

Error: (04/09/2012 06:24:13 PM) (Source: Application Error)(User: )
Description: svchost.exe_wuauserv6.1.7600.163854a5bc3c1CRYPTSP.dll6.1.7600.163854a5bdf96c0000006000000000000879be2801cd166cd7ea76efC:\Windows\system32\svchost.exeC:\Windows\system32\CRYPTSP.dll7155a9b3-8260-11e1-88ed-001802f4049c

Error: (04/09/2012 06:21:28 PM) (Source: Application Error)(User: )
Description: C:\Windows\System32\shlwapi.dllWindows ExplorerC00001853

Error: (04/09/2012 06:21:28 PM) (Source: Application Error)(User: )
Description: C:\Windows\System32\crypt32.dllHost Process for Windows ServicesC00001853

Error: (04/09/2012 06:21:28 PM) (Source: Application Error)(User: )
Description: Explorer.EXE6.1.7600.167684d688122ntdll.dll6.1.7600.169154ec4b137c00000060000000000034e8f12801cd1660b7c936b0C:\Windows\Explorer.EXEC:\Windows\SYSTEM32\ntdll.dll0eb2a5dd-8260-11e1-88ed-001802f4049c

Error: (04/09/2012 06:21:28 PM) (Source: Application Error)(User: )
Description: svchost.exe_wuauserv6.1.7600.163854a5bc3c1ntdll.dll6.1.7600.169154ec4b137c000000600000000000158e5e001cd166068135260C:\Windows\system32\svchost.exeC:\Windows\SYSTEM32\ntdll.dll0eb27ecd-8260-11e1-88ed-001802f4049c

Error: (04/09/2012 05:01:10 PM) (Source: Microsoft-Windows-LoadPerf)(User: SYSTEM)SYSTEM
Description: WmiApRplWmiApRpl8F20300004D070000

Error: (04/09/2012 05:01:10 PM) (Source: Microsoft-Windows-LoadPerf)(User: SYSTEM)SYSTEM
Description: Performance1637070000000000000000000009030000

Error: (04/09/2012 04:57:17 PM) (Source: Application Error)(User: )
Description: DkService.exe14.0.909.04ca6b84bDkService.exe14.0.909.04ca6b84b800000030000000000035712f6001cd16610e2fdcb4F:\Programi\Diskeeper Corporation\Diskeeper\DkService.exeF:\Programi\Diskeeper Corporation\Diskeeper\DkService.exe4c471fee-8254-11e1-88ed-001802f4049c

Error: (04/09/2012 04:48:46 PM) (Source: Microsoft-Windows-LoadPerf)(User: SYSTEM)SYSTEM
Description: WmiApRplWmiApRpl8F20300004D070000


=========================== Installed Programs ============================


========================= Devices: ================================

Name:
Description:
Class Guid:
Manufacturer:
Service:
Problem: : The drivers for this device are not installed. (Code 28)
Resolution: To install the drivers for this device, click "Update Driver", which starts the Hardware Update wizard.


========================= Memory info: ===================================

Percentage of memory in use: 63%
Total physical RAM: 2047.37 MB
Available physical RAM: 742.73 MB
Total Pagefile: 4094.73 MB
Available Pagefile: 2610.54 MB
Total Virtual: 4095.88 MB
Available Virtual: 3959.38 MB

========================= Partitions: =====================================

2 Drive c: () (Fixed) (Total:37.57 GB) (Free:4.3 GB) NTFS
3 Drive d: () (Fixed) (Total:40 GB) (Free:12.07 GB) NTFS
4 Drive e: () (Fixed) (Total:34.52 GB) (Free:1.72 GB) NTFS
5 Drive f: () (Fixed) (Total:97.65 GB) (Free:46.99 GB) NTFS
6 Drive g: () (Fixed) (Total:97.65 GB) (Free:22.73 GB) NTFS

========================= Users: ========================================
========================= Minidump Files ==================================

No minidump file found

**** End of log ****

Dopuna: 09 Apr 2012 18:36

inace pustio sam win 7 da sam instalira drajvere kada sam prvi put dizao sistem, tj nisam nista instalirao sa diskova. eventualno sam apdejtovao drajvere za graficku zbog igara.

• 0Niko još nije pohvalio poruku.
  Registruj se da bi pohvalio/la poruku!

Je si siguran da imas najnovije i odgovarajuce drajvere za tvoju graficku?

http://www.nvidia.com/object/win7-winvista-32bit-296.10-whql-driver.html

Je si proveravao tempereturu komponenti?

• 2Ovo se svidja korisnicima: stefke001, TwinHeadedEagle
  
  Registruj se da bi pohvalio/la poruku!

Napisano: 09 Apr 2012 19:24

Da vidimo da li je hard diskom sve u redu pa da idemo dalje ... (sredjivanje sistemskih fajlova koji su osteceni) ...



Sledeći postupak će proveriti da li je Vaš hard disk fizički oštećen.

1. Skinite program MHDD,

2. Raspakujte zip arhivu i narežite ISO fajl na CD,

3. Restartujte računar i u BIOS-u podesite da sistem podiže sa optičkog uređaja.

4. Sačekajte da se učitaju neophodni fajlovi i zatim izaberite opciju 1 kao na slici.


5. Pojaviće se sledeći meni sa opcijama u kojem trebate izabrati koji hard disk želite skenirati.

Ukucajte Vaš izbor i pritisnite Enter.

6. Pojaviće se sledeći meni.


7. Ukucajte scan i pritisnite Enter.


8. Pojaviće se sledeći meni.

Pritisnite F4.

9. Počeće skeniranje hard diska.


U slučaju da se pojavi više od 3 upisa u delu X UNC: Vaš hard disk je fizički oštećen.

Dopuna: 09 Apr 2012 19:28



.




Vlada ::cim sam instalirao whocrashed pojavio mi se baloncic koji kaze da je C:\windows\system32\drivers\en-us koruptovan i da bi trebalo da pokrenem chkdisk



Obavezno pokreni chkdsk za svaku particiju ...
Tutorijal: http://www.sevenforums.com/tutorials/433-disk-check.html


U ovom prozoru strikliraj obe stavke:





Takodje, pokreni komandu sfc /scannow prateci sledece uputstvo: http://www.sevenforums.com/tutorials/1538-sfc-scan.....ecker.html

• 0Niko još nije pohvalio poruku.
  Registruj se da bi pohvalio/la poruku!

izvinjavam se sto kasnim s odgovorom ali znate kako ide praznici, ispiti... nisam imao vremena da se pozabavim problemom. u poslednje vreme da kucnem u drvo sve funkcionise kako treba.
probao sam sa pravljenjem butabilnog sa mhddom (iso fajlom) ali iz nekog razloga sta god uradio nece da ga butuje sa cda.
zato sam skinuo Western Digital Data Lifeguard Diagnostic posto mi je jelte WD hard (oba, mislio sam da je jedan Maxtor ali ocigledno su oba WD)



WinDiag ima 4 seta opcija za svaki hard, quick test, extended test, write zeros, view test result

i quick test i extended test su mi FAIL. quick zbog read errora a extended zbog suvise bad sectora. program nudi i opravku bad sectora ali to znaci gubitak podataka (otpada odmah).



evo rezultata:

Citat:Test Option: QUICK TEST
Model Number: WDC WD2500AAKS-00C9A0
Unit Serial Number: WD-WCARW3484466
Firmware Number: 12.01B02
Capacity: 250.06 GB
SMART Status: PASS
Test Result: FAIL
Test Error Code: 06-Quick Test on drive 1 did not complete! Status code = 07 (Failed read test element), Failure Checkpoint = 97 (Unknown Test) SMART self-test did not complete on drive 1!
Test Time: 01:15:51, May 17, 2012

Test Option: EXTENDED TEST
Model Number: WDC WD2500AAKS-00C9A0
Unit Serial Number: WD-WCARW3484466
Firmware Number: 12.01B02
Capacity: 250.06 GB
SMART Status: PASS
Test Result: FAIL
Test Error Code: 08-
Test Time: 02:38:37, May 17, 2012

dok drugi hard prodje oba testa bez problema. sto me dalje navodi na to da hard ne valja...

i jos jednu stvar sam primetio, iskopao sam neke clanke na MYC da win 7 64 ultimate najslabije radi na 2gb rama, da mu treba jos 2 da bi postizao dobre rezultate sto je upravo primer kod mene. sto znaci ili jos 2 gb rama ili vracanje na 32 bita ili cak XP...

ne znam, pomagajte, dajte neke savete...

• 0Niko još nije pohvalio poruku.
  Registruj se da bi pohvalio/la poruku!

Napisano: 18 Maj 2012 0:51

Hard disk ne mozes testirati dok je isti u upotrebi - a koliko vidim ti si to upravo radio; pokretao skeniranje iz aktivnog Windows-a. Zato smo i predlozili MHDD jer ga pokreces sa diska dok sistem nije aktivan.


Svaki od hard diskova istestiraj sa butabilnim MHDD diskom (flash uredjajem) ali tako da hard disk koji testiras bude na primarnoj grani, postavljen na master mode. Znaci povadis sve hard diskove, ostavis jedan i njega testiras. Otkacis njega - prikljucis drugi pa njega testiras.

Dopuna: 18 Maj 2012 0:52

Vlada ::i jos jednu stvar sam primetio, iskopao sam neke clanke na MYC da win 7 64 ultimate najslabije radi na 2gb rama, da mu treba jos 2 da bi postizao dobre rezultate sto je upravo primer kod mene. sto znaci ili jos 2 gb rama ili vracanje na 32 bita ili cak XP...

ne znam, pomagajte, dajte neke savete...


Diskusija o tome se nalazi ovde - sam donesi zakljucak: http://www.mycity.rs/Windows/Koju-verziju-32-bitnu.....B-RAM.html

• 0Niko još nije pohvalio poruku.
  Registruj se da bi pohvalio/la poruku!

ja se izvinjavam što se tek sad opet aktiviram na ovoj temi. onomad nisam mogao da butujem sa diska mhdd pa sam odustao, dok nisam provalio funkciju za forsirani boot... a i nisam imao većih problema otad do pre par dana kada su se problemi ponovo javili.

u svakom slučaju , testirao sam hard za koji sumnjam da je loš mhddom i u rezultatu imam ČAK 37 UNC sektora (xUNC) i nebrojeno mnogo warninga.

ima li leba od ovog harda ili da se isprsim za novi?

nažalost nisam uhvatio screen al pustiću analizu opet pa ću postovati ovde screen analize i SMART analizu kasnije u toku dana.

pozdrav!