Savet oko crash dump-ova

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

Drugar ima problem i evo par crash dump logova iz Who Crashed, pa ako moze savet, sta da se radi.

On Sun 22/07/2012 10:17:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072212-13322-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x15391B)
Bugcheck code: 0x4E (0x99, 0xB96C, 0x2, 0x4B5AB)
Error: PFN_LIST_CORRUPT
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 which cannot be identified at this time.

On Fri 20/07/2012 15:39:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072012-22058-01.dmp
This was probably caused by the following module: Unknown (0xFFFFFFFF82B2BD10)
Bugcheck code: 0x4E (0x99, 0x43E2B, 0x2, 0x365EA)
Error: PFN_LIST_CORRUPT
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 PFN_LIST_CORRUPT

On Thu 19/07/2012 16:42:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071912-13572-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDCD10)
Bugcheck code: 0x4E (0x99, 0xA8DD, 0x2, 0x9F1E)
Error: PFN_LIST_CORRUPT
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 15/07/2012 13:42:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071512-15553-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xAC5B0)
Bugcheck code: 0x1A (0x41201, 0xFFFFFFFFC0044B98, 0x19D0C867, 0xFFFFFFFF87327760)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 14/07/2012 15:01:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071412-22651-01.dmp
This was probably caused by the following module: aswsnx.sys (aswSnx+0x9EBA4)
Bugcheck code: 0x50 (0xFFFFFFFFBB200004, 0x0, 0xFFFFFFFF8D4C2BA4, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: aswsnx.sys .
Google query: aswsnx.sys PAGE_FAULT_IN_NONPAGED_AREA

On Wed 11/07/2012 10:00:45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071112-12589-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDCD10)
Bugcheck code: 0x4E (0x99, 0x41161, 0x2, 0x1020)
Error: PFN_LIST_CORRUPT
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 10/07/2012 13:31:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071012-21590-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDCD10)
Bugcheck code: 0x4E (0x99, 0x59E93, 0x2, 0x1212)
Error: PFN_LIST_CORRUPT
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 08/07/2012 15:42:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070812-15865-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xAC5B0)
Bugcheck code: 0x1A (0x41201, 0xFFFFFFFFC0032B98, 0x160BF867, 0xFFFFFFFF87508B18)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 08/07/2012 12:15:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070812-15506-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDCD10)
Bugcheck code: 0x4E (0x99, 0x4079F, 0x1, 0x2319F)
Error: PFN_LIST_CORRUPT
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 06/07/2012 13:15:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070612-14882-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x6C25F)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF9653C25F, 0xFFFFFFFFB90B7B28, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
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 which cannot be identified at this time.

On Thu 05/07/2012 15:06:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070512-16894-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDCD10)
Bugcheck code: 0x4E (0x99, 0x539CB, 0x2, 0x5394B)
Error: PFN_LIST_CORRUPT
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 01/07/2012 08:51:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070112-23774-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x467EB)
Bugcheck code: 0xA (0xFFFFFFFFC02B5110, 0x0, 0x0, 0xFFFFFFFF82AAF5A1)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 29/06/2012 23:15:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\063012-21309-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDCD10)
Bugcheck code: 0x4E (0x99, 0x6FBCC, 0x0, 0x7528C)
Error: PFN_LIST_CORRUPT
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

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

Od kada se to desava, ima li odgovarajuce drajvere instalirane, jeste li testirali hard disk i ram memoriju?

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

Pa ja sam nes na netu citao i ono, predlozio da testira hard disk, ali da uzme Hd Tune,posto ja ne mogu ici kod njega da mu odradim preko MHDD(iso fajl, boot itd. takve stvari ne zna da odradi). Takodje sam rekao da preskenira na razne gamadi(viruse,spyware,mallware, trojance itd) i da update drajvere. Pa cemo videti. RAM nisam spomenuo.

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

Uloguj se preko Facebooka da bi skinuo fajl:

Napisano: 26 Jul 2012 13:39

Isprati sledeca uputstva, ne verujem da je problem do RAM memorije, ali za svaki slucaj

==============================

Sledećim postupkom vrši se testiranje RAM memorije.

1. Za pokretanje sa CD-a, ispratite sledeće uputstvo: + Klikni
1a. Preuzmite program Memtest86+, raspakujte zip arhivu i narežite ISO fajl na CD po ovom uputstvu.

1b. Restartujte računar i u BIOS-u podesite da sistem podiže sa optičkog uređaja, po ovom uputstvu.

2. Za pokretanje sa USB-a, ispratite sledeće uputstvo: + Klikni
2a.Preuzmite program Memtest86+ USB Instaler, raspakujte arhivu, priključite prazan USB i pokrenite instalaciju. Tokom instalacije programa na USB, svi fajlovi na njemu će biti obrisani! Napravite backup važnih podataka sa USB-a.




2b. Restartujte računar i u BIOS-u podesite da sistem podiže sa USB Flash diska.

3. Sačekajte da se učitaju neophodni fajlovi, nakon čega počinje testiranje RAM memorije. Testiranje treba da traje bar 8 sati ili 6 prolaza (pass).



U slučaju da se u delu Errors pojave upisi, RAM memorija je oštećena.

Ovako će izgledati u slučaju da je RAM memorija oštećena:



Ako se pojave greške (errors), treba testirati svaki modul RAM-a posebno, da biste utvrdili koji je neispravan. Ako svi moduli prođu pojedinačno testiranje bez greške, verovatno je neki od memorijskih slotova na ploči neispravan. Ubacite pouzdano ispravan modul RAM-a u jedan slot i testirajte ponovo. Ako se ne pojavi greška, ubacite taj modul u sledeći memorijski slot i testirajte ponovo. Ponavljajte ovu proceduru dok ne pronađete koji memorijski slot je neispravan.



Hard disk moze biti uzrok, zato bi njega trebao da testiras, moze i preko USB-a

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

1. Za pokretanje sa CD-a, ispratite sledeće uputstvo: + Klikni
1a.Skinite program MHDD,

1b. Raspakujte zip arhivu i narežite ISO fajl na CD, po ovom uputstvu.

1c. Restartujte računar i u BIOS-u podesite da sistem podiže sa optičkog uređaja, po ovom uputstvu.

2. Za pokretanje sa USB-a, ispratite sledeće uputstvo: + Klikni
2a. Preuzmite MHDD sa [url=https://www.mycity.rs/must-login.png linka. Zatim preuzmite USBFlashTools odavde i raspakujte ga na desktop.

2b. Formatirajte USB disk u FAT file system. Tokom formatiranja diska, svi fajlovi na njemu će biti obrisani! Napravite backup važnih podataka sa USB-a.



2c. Pokrenite USBFlashTools.exe i kliknite na Restore.



2d. Izaberite floppy_1.44.00.img i vaš USB disk pa kliknite na Restore kao na slici:



2e. Zatim restartujte računar, i u BIOS-u izaberite bootovanje sa USB diska.

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



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


Ukucajte Vaš izbor i pritisnite Enter.

5. Pojaviće se sledeći meni.



6. Ukucajte scan i pritisnite Enter.



7. Pojaviće se sledeći meni.


Pritisnite F4.

8. 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: 26 Jul 2012 13:42

Isprati sledece uputstvo i postavi HWinfo izvestaj

[Link mogu videti samo ulogovani korisnici]




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!

Uloguj se preko Facebooka da bi skinuo fajl:

[Link mogu videti samo ulogovani korisnici]

[Link mogu videti samo ulogovani korisnici]

Evo logovi

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

Kad zavrsis u Ambulanti, odradi sledece



Obrisi program Driver Easy, verovatno on i pravi problem, ostaje da vidimo...


Koristis Windows 7 Ultimate bez Service Pack 1. Otidji u Control Panel -> System and Security -> Check for Updates i instaliraj sve important apdejtove koje ti ponudi...




Drajveri za tvoju maticnu su ovde

[Link mogu videti samo ulogovani korisnici]
[Link mogu videti samo ulogovani korisnici]
[Link mogu videti samo ulogovani korisnici]

Za graficku

[Link mogu videti samo ulogovani korisnici]

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

Uloguj se preko Facebooka da bi skinuo fajl:

Evo loga posle update-a iz control panela.


[Link mogu videti samo ulogovani korisnici]

ne vidim da stavljen sp1.. Mora se downloadovati pa instalirati?

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

Ne treba mi taj log, onaj prvi je dovoljan, jedino ako nisi menjao hardware u medjuvremenu

Je si instalirao drajvere? Pojavljuje li se sada BSOD?

Sto se tice apdejta, ides Check for Updates i kad ih prikaze ti samo kliknes na Install i tako dok ih god ima...

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

Odradjeno je to kao i instalacija service pack-a. Ja sam bio pitao da li ce se staviti sp prilikom tog update. Nije, pa je rucno instaliran. Za sad je sve ok. MOZE LOCK!

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

Nisam te razumeo, SP1 se instalira kao i svaki drugi apdejt

Nema kod nas lock