Koristite zastareli preglednik. Možda se neće pravilno prikazivati ova ili druge veb stranice. Trebalo bi da nadogradite ili koristite alternativni preglednik.
imam win 7 64bit, i pre nekog vremena poceo sam da imam problem, da kad surfujem netom, popijem blue screen, restartuje se komp i odradi minidump...
to se ne desava svaki cas, vec recimo jednom dnevno, posle dosta surfovanja...
mislim da nije problem u windows-u, jer sam vec probao sa formatiranjem i problem je osta identican...
probao sam da menjam browsere, od mozile ka chrome-u i operi, ali nista nije pomoglo, svuda je ostao isti problem, iako se opera pokazala nesto izdrzljivijom...
jel imate neke predloge?
btw procesor mi je overklokovan, kao i memorija, dugo sam ih koristio na tim vrednostima bez ikakvih problema, ali sad su odjenom naprasno krenuli problemi, a stvarno blage veze nemam zbog cega...nisam nista dzarao po kompu, bilo hardverski, bilo softverski...
Probaj sa Blue Screen View programom,vidi koji je log,sta pise pa iz guglaj. Meni su drajveri za GPU pravili problem. MIslim da je bilo zbog flash materijala na web stranicama i da mi se tada to desilo par puta.
Pokusaj da vratis vrednosti u BIOSu na default, probaj onda da surfujes vidi da li ti se to desava, lepo si rekao u proslom vremenu "koristio overclockovan CPU i Mem" vise ne mozes, mozda ploca mozda napajanje koje vise ne moze da izvuce te vrednosti koje si mu ti zadao?
pozzzz
Meni je Adobe Flash 10-3 stalno to radio. Čak su i oni priznali to, ja sam bio vratio na 10-2 i prestalo je, juče je izašla nova verzija i za sada nema problema.
Meni je Adobe Flash 10-3 stalno to radio. Čak su i oni priznali to, ja sam bio vratio na 10-2 i prestalo je, juče je izašla nova verzija i za sada nema problema.
Da ne otvaram novu temu imam problem ponekad(jednom u 7dana) samo kad surfujem netom popijem blue screen.Jeste masina overklokovana ali mi se cini da je nesto drugo u pitanju.
Mozda Amd driver-a14.4 i 14.4 beta isto mi se desava, ili do flash playera?
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional information about the problem:
BCCode: 1000007e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF8800F555DBB
BCP3: FFFFF88004046228
BCP4: FFFFF88004045A80
OS Version: 6_1_7601
Service Pack: 1_0
BSOD direktno pokazuje na AMD - ATI kernel modul. Očisti drajvere sa Display Driver Uninstaller i probaj ponovo instalaciju stabilnog 14.4 ili stabilne verzije pre njega.
Brisao Display Driver Uninstaller-om i Driver Sweeper-om opet se desava jedino da probam neku stariju verziju drivera. A taman mi lepo radi beta 14.4 tj monitor se budi uvek posle sleep-a inace problem kod 98 posto AMD drivera.
Brisao Display Driver Uninstaller-om i Driver Sweeper-om opet se desava jedino da probam neku stariju verziju drivera. A taman mi lepo radi beta 14.4 tj monitor se budi uvek posle sleep-a inace problem kod 98 posto AMD drivera.
Verovatno je driver ali sam krenuo od flash pleyer-a i vratio staru verziju µtorenta posto kazu da hoce i od njega.
Pa cu videti posto mi se desava jednom nedeljno otprilike
Plavi ekran kod windowsa je dosta cesta pojava. Zovu ga jos i plavi ekran smrti. Razlozi za njegovo pojavljivanje mogu biti razni. Npr.
Plavi ekran moze da nastupi samo zbog neispravnog hardvera ili zbog drajvera.
Obicni programi ne mozgu da izazovu plavi ekran ni pod tackom razno, tako da nema potrebe da gubis vreme sa CCleanerom i slicnim cistacima.
Ukoliko u zadnje vreme nisi instalirao nikakav drajver, onda se mogucnosti suzavaju na neispravan hardver ili na to da ti je neki malware na sistem instalirao rootkit (sto opet spada u drajvere).
Predlazem da za pocetak proveris hard disk i to mozes uciniti na sledeci nacin ako ispratis donji link http://forum.benchmark.rs/showthread.php?326111-Provera-ispravnosti-HDD-a-test
Ajd da ne otvaram novu temu... Zamenih procesor (ubacio ovaj iz potpisa, stari je bio Pentium E5300) pre 2 dana, usput ocistio kuciste od prasine, sve sredio, ubacio jos jedan kuler na kuciste (prednji i zadnji da prave promaju) i kada sam pokrenuo sistem, posle Win logoa izbaci BSOD pa na restart i tako u krug. Nista, kontam posto sam zamenio 2 vrste memorije, 2 ploce i 3 procesora otkad sam instalirao sistem, valjda je doslo vreme da poludi. Reinstaliram sistem i krenu BSODovi random da iskacu, ono sto sam primetio su bili BAD_POOL_CALLER i SYSTEM_SERVICE_EXCEPTION i u jednom od ta dva (sad se ne secam kojem) je pisalo u zagradi win32k.sys.
P.S. Imam i problem sa temperaturom od procesora otkad sam ga ubacio, u biosu je stalno oko 60 stepeni, dok RealTemp, CoreTemp i hwmonitor pokazuju oko 50. Stavio sam istu pastu kao na prethodna 2 procesora (kojima je bila oko 30-35 stepeni), jednom sam i promenio nanos jer sam mislio da mozda nisam dobro stavio prvi put. Pisem ovo jer mozda ima problem sa njim. Fleshovao sam i bios za ovaj procesor ROMom koji sam skinuo sa Asusovog sajta. Nista ne pomaze. Za koji dan bi mi trebala stici Prolimatech PK-1 pasta pa cu i s njom probati. Spominjem ovo cisto da se zna, iako je offtopic ovde, jer mozda ima veze s ovim BSODovima.
Imas problem sa ACPI drajverom.
Idi na http://www.asus.com/Motherboards/P5KC/HelpDesk_Download/
Izaberi Vista 64 bit i pod stavkom ATK skini
ACPI driver for ATK 0110 virtual device for Windows XP(32bit and 64bit)/VISTA(32bit & 64bit)
Instaliraj i restartuj PC,trebalo bi da ti resi problem.
Hmm, da, secam se to je jedino ostalo nenstalirano u Device Manageru kada sam digao sistem, odradio onda automatsku pretragu drajvera i instalaciju. Sad sam obrisao i ubacio ovaj sa sajta, morao sam ga rucno preko DM instalirati jer mi je izbacilo da installer ne podrzava verziju OSa. Ajd pa cemo videti dan-dva kako se ponasa.
I ja imam povremene Blue Screen ali samo prilikom paljenja kompa.Kad se to desi odradim restart i win se podigne normalno.Sta moze da mi pravi problem?
Ne desava se bas svaki dan.Mozda jednom nedeljnkacio sam u atacmentu sta se desava pa ako moze neko ko se razume da mi kaze sta mi pravi problem.
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff96000099f72, Address of the instruction which caused the bugcheck
Arg3: ffffd00179206010, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
Drugi fajl - 060814-34312-01.dmp
IRQL_NOT_LESS_OR_EQUAL (a)
BugCheck A, {55d0, 2, 0, fffff803d8e2ce70}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4fcd0 )
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000000000055d0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff803d8e2ce70, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff803d8fcc150
GetUlongFromAddress: unable to read from fffff803d8fcc208
00000000000055d0 Nonpaged pool
TRAP_FRAME: ffffd00020108880 -- (.trap 0xffffd00020108880)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff803d8e2ce70 rsp=ffffd00020108a10 rbp=00000000ffffffff
r8=0000000000000000 r9=0000000000000000 r10=0000000000003377
r11=0000000000000033 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
nt! ?? ::FNODOBFM::`string'+0x4fcd0:
fffff803`d8e2ce70 8b81d0550000 mov eax,dword ptr [rcx+55D0h] ds:00000000`000055d0=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff803d8dd87e9 to fffff803d8dccca0
Treći fajl - 060914-21734-01.dmp
BAD_POOL_CALLER (c2)
BugCheck C2, {7, 1200, 45702410, ffffe00045702420}
Probably caused by : afd.sys ( afd!PplGenericFreeFunction+46 )
BAD_POOL_CALLER (c2)
The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 0000000000000007, Attempt to free pool which was already freed
Arg2: 0000000000001200, (reserved)
Arg3: 0000000045702410, Memory contents of the pool block
Arg4: ffffe00045702420, Address of the block of pool being deallocated
Četvrti fajl - 060914-26843-01.dmp
BAD_POOL_CALLER (c2)
BugCheck C2, {7, 1200, 45702410, ffffe00045702420}
Probably caused by : afd.sys ( afd!PplGenericFreeFunction+46 )
BAD_POOL_CALLER (c2)
The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 0000000000000007, Attempt to free pool which was already freed
Arg2: 0000000000001200, (reserved)
Arg3: 0000000045702410, Memory contents of the pool block
Arg4: ffffe00045702420, Address of the block of pool being deallocated
Peti fajl - 060914-27703-01.dmp
PAGE_FAULT_IN_NONPAGED_AREA (50)
BugCheck 50, {fffff6fb40000000, 0, 0, 6}
Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+15f08 )
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff6fb40000000, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: 0000000000000000, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000006, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff802469dc138
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
fffff6fb40000000
TRAP_FRAME: ffffd0011ee1a5a0 -- (.trap 0xffffd0011ee1a5a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff6fb40000000 rbx=0000000000000000 rcx=00000904c0000000
rdx=fffff80246688000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8024671b0e8 rsp=ffffd0011ee1a730 rbp=0000000000000001
r8=0000000000000000 r9=0000000000000000 r10=fffff802469703e0
r11=ffffd0011ee1a8b8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po cy
nt!ExFreeLargePool+0x78:
fffff802`4671b0e8 488b00 mov rax,qword ptr [rax] ds:fffff6fb`40000000=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff802468023b8 to fffff802467dbfa0
Uglavnom, lepa zbirka raznih BSODova. Dobro je da je tu Vuk40 sa svojom poznatom intuicijom koja ga nepogrešivo vodi do ASUSovog drajvera - neverovatno kako je nestabilan... Prvi fajl spominje i PROCESS_NAME: Skype.exe, dakle stavi noviju verziju Skype-a sa http://www.skype.com/en/download-skype/skype-for-computer/, nikad se ne zna...
@bojke1: Tvoj problem izgleda lakši - svi BSODovi uglavnom pominju ha20x22k.sys i još poneki Creative drajver fajl - probaj da ažuriraš drajvere za zvučnu kartu.
Heh, evo ga novi DMP, izgleda nesto i graficku zeza :\ *** a juce sam instalirao nove drajvere, i novi Skype... a interesantno, nisam ni jedan jedini bsod imao sa E5300 a jedno desetak dana sam ga furao
Kako to da nijedan minidump nigde ne pokaže na taj drajver? Šta ti je iskustvo... egzaktnije je od dijagnostike ugrađene u operativni sistem. Ne mora čovek ni da gleda u dampove...
Nemaš ti Vuče pojma... Ako ne radiš u nekom od servisa za naše velike distributere, javi se na sledeći konkurs, dobar si materijal za njih.
Inače, ovaj novi fajl - VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e) je novi BSOD, stvarno lepa kolekcija. Da probaš malo neki test stabilnosti, ako već novi Skype i ACPI ATK ne rade? Mada, evo, BSOD prijavljuje PROCESS_NAME: SniperEliteV2, dakle nadam se da si ga pokupio na Steamu jer je bio free za vikend, inače obavezno stavi poslednju verziju .
Probaj svež Prime95 da vidimo da li uspeva da radi, usput prati temperature sa HWInfo... Loš CPU je recimo retka pojava, ali nikad ne reci nikad... Naravno, pretpostavljam da si ucitao safe defaults u BIOSu?
