BSOD - što, zašto i kako

ok javim se kad to sve napravim...

EDIT: napravio sam to, nema u BIOS-u baš tim imenom za miša ali ima ta opcija... na stranici proizvođača kaže da podržava 1.0b ACPI samo. update-o sam drivere za chipset... i onemogućio hibernaciju... sad ostaje vidjeti dalje, ako se opet pojavi vidjeti ću.

inače mali update, imam 4gb rama ddr2 u dual chanel-u u 4 slota... e sada kada su bila 3 komada manje se rušilo, ali opet prošao sam s memory testovima i kažu da je sve ok

RAM je OCZ PC2-6400 (1GB x 4kom.)

MBO Gigabyte GA-EX38-DQ6

EDIT2: opet sam dobio BSOD... svašta, neam više energije za ovo... majku mu 

Šta bi ovo moglo bit: dobijen bsod nakon 10 min igre bc2 dok u left for dead sve ok

Followup: MachineOwner
---------

1: kd> lmvm hardware
start             end                 module name
1: kd> lmvm nt
start             end                 module name
fffff800`02c1c000 fffff800`031f8000   nt       T (no symbols)          
    Loaded symbol image file: ntoskrnl.exe
    Image path: ntoskrnl.exe
    Image name: ntoskrnl.exe
    Timestamp:        Sat Apr 09 06:14:44 2011 (4D9FDD34)
    CheckSum:         00547734
    ImageSize:        005DC000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Edit: problem riješen,instaliran ponovo driver

Pozdrav,

zadnja dva dana dva puta mi se pojavio BSOF, nisam stigao uslikati da stavim baš svoj, ali radi se o MEMORY MANAGMENT

Sigurno je sličan kao ovaj na netu

Konfiguracija pod moj komp

Pa ako je netko imao sličnih problema, nek se uključi

Evo mene nazad, dajte pogledajte crash dump..

http://www.megaupload.com/?d=C405X3SC

Izgleda da etron driver se kolje s nečim..Ak može ko to potvrdit?

Uglavnom uvijek baca taj F4 error...

I to se sruši dok niš ne delam na kompu..

Izbrisal sam drivere etron to je usb 3.0 pa bumo vidli..

A vi slobodno recite još nekaj ak treba popravit..

Pozdrav!

Uzeo sam novi procesor AMD 955 black edition 4x3.2,novu matičnu Asrock 770 xtreme3,napajanje Corsair 550w,rame 2x2 Corsair.Kada sam sve komponente promijenio dešavao mi se pad sistema i plavi zaslon.Počeo sam provjeravat komponente sa programom PC check i ukazao mi je na ne ispravan ram koji sam zamijenio i na ne isparavan hard koji sam isto tako zamijenio.

Instalirao sam windows 7 ultimate 64bit i sve drivere da bi to sve ljepo funkcioniralo dok nisam opet dočeko plavi zaslon.Opet sam sve testirao i program mi nije ukazao na kvar od komponenti.

Kad mi se sistem restarto pogledao sam na windowsu šta piše pod detaljima od pada i bilo je u svezi Bcc,bcp1,bcp2,bcp3,bcp4 coda.Kad sam pokušao kopirati podatke u post kaže ukoliko sam koristio podatke formiranog teksta da mu uklonim formatiranje...pošto nisam neki stručnjak samo sam opisao ovo ukratko.                     

Što se tiče debug alata dobio sam tri dumpa ali ih nemogu postat jer sam stavio krive simbole,pa sad pogađam koji su....

Loading Dump File [C:\Windows\Minidump\062211-25796-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: D:\Symbols

Executable search path is: 

Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2

*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe

Windows 7 Kernel Version 7600 MP (4 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 7600.16792.amd64fre.win7_gdr.110408-1633

Machine Name:

Kernel base = 0xfffff800`02c11000 PsLoadedModuleList = 0xfffff800`02e4ee50

Debug session time: Wed Jun 22 20:25:15.613 2011 (UTC + 2:00)

System Uptime: 0 days 0:11:39.972

Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2

*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe

Loading Kernel Symbols

...............................................................

................................................................

.....................

Loading User Symbols

Loading unloaded module list

.....

*******************************************************************************

*                                        *

*             Bugcheck Analysis                   *

*                                        *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002c8e19d, fffff8800383c0c0, 0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************

***                                   ***

***                                   ***

***   Your debugger is not using the correct symbols          ***

***                                   ***

***   In order for this command to work properly, your symbol path   ***

***   must point to .pdb files that have full type information.    ***

***                                   ***

***   Certain .pdb files (such as the public OS symbols) do not    ***

***   contain the required information.  Contact the group that    ***

***   provided you with these symbols if you need this command to   ***

***   work.                              ***

***                                   ***

***   Type referenced: nt!_KPRCB                    ***

***                                   ***

*************************************************************************

*************************************************************************

***                                   ***

***                                   ***

***   Your debugger is not using the correct symbols          ***

***                                   ***

***   In order for this command to work properly, your symbol path   ***

***   must point to .pdb files that have full type information.    ***

***                                   ***

***   Certain .pdb files (such as the public OS symbols) do not    ***

***   contain the required information.  Contact the group that    ***

***   provided you with these symbols if you need this command to   ***

***   work.                              ***

***                                   ***

***   Type referenced: nt!_KPRCB                    ***

***                                   ***

*************************************************************************

*************************************************************************

***                                   ***

***                                   ***

***   Your debugger is not using the correct symbols          ***

***                                   ***

***   In order for this command to work properly, your symbol path   ***

***   must point to .pdb files that have full type information.    ***

***                                   ***

***   Certain .pdb files (such as the public OS symbols) do not    ***

***   contain the required information.  Contact the group that    ***

***   provided you with these symbols if you need this command to   ***

***   work.                              ***

***                                   ***

***   Type referenced: nt!_KPRCB                    ***

***                                   ***

*************************************************************************

Probably caused by : ntoskrnl.exe ( nt+7d19d )

Ima toga još:

Loading Dump File [C:\Windows\Minidump\062211-26609-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: D:\Symbols

Executable search path is: 

Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2

*** WARNING: Unable to verify timestamp for ntoskrnl.exe

*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe

Windows 7 Kernel Version 7600 MP (4 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 7600.16792.amd64fre.win7_gdr.110408-1633

Machine Name:

Kernel base = 0xfffff800`02c01000 PsLoadedModuleList = 0xfffff800`02e3ee50

Debug session time: Wed Jun 22 14:17:48.180 2011 (UTC + 2:00)

System Uptime: 0 days 0:03:24.540

Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2

*** WARNING: Unable to verify timestamp for ntoskrnl.exe

*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe

Loading Kernel Symbols

...............................................................

................................................................

......................

Loading User Symbols

Loading unloaded module list

....

*******************************************************************************

*                                        *

*             Bugcheck Analysis                   *

*                                        *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C2, {7, 1097, 0, fffff8a003c38258}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************

***                                   ***

***                                   ***

***   Your debugger is not using the correct symbols          ***

***                                   ***

***   In order for this command to work properly, your symbol path   ***

***   must point to .pdb files that have full type information.    ***

***                                   ***

***   Certain .pdb files (such as the public OS symbols) do not    ***

***   contain the required information.  Contact the group that    ***

***   provided you with these symbols if you need this command to   ***

***   work.                              ***

***                                   ***

***   Type referenced: nt!PVOID                    ***

***                                   ***

*************************************************************************

unable to get nt!MmSpecialPoolStart

unable to get nt!MmSpecialPoolEnd

*************************************************************************

***                                   ***

***                                   ***

***   Your debugger is not using the correct symbols          ***

***                                   ***

***   In order for this command to work properly, your symbol path   ***

***   must point to .pdb files that have full type information.    ***

***                                   ***

***   Certain .pdb files (such as the public OS symbols) do not    ***

***   contain the required information.  Contact the group that    ***

***   provided you with these symbols if you need this command to   ***

***   work.                              ***

***                                   ***

***   Type referenced: nt!_POOL_HEADER                 ***

***                                   ***

*************************************************************************

unable to get nt!MmPoolCodeStart

unable to get nt!MmPoolCodeEnd

*************************************************************************

***                                   ***

***                                   ***

***   Your debugger is not using the correct symbols          ***

***                                   ***

***   In order for this command to work properly, your symbol path   ***

***   must point to .pdb files that have full type information.    ***

***                                   ***

***   Certain .pdb files (such as the public OS symbols) do not    ***

***   contain the required information.  Contact the group that    ***

***   provided you with these symbols if you need this command to   ***

***   work.                              ***

***                                   ***

***   Type referenced: nt!_POOL_HEADER                 ***

***                                   ***

*************************************************************************

*************************************************************************

***                                   ***

***                                   ***

***   Your debugger is not using the correct symbols          ***

***                                   ***

***   In order for this command to work properly, your symbol path   ***

***   must point to .pdb files that have full type information.    ***

***                                   ***

***   Certain .pdb files (such as the public OS symbols) do not    ***

***   contain the required information.  Contact the group that    ***

***   provided you with these symbols if you need this command to   ***

***   work.                              ***

***                                   ***

***   Type referenced: nt!_POOL_TRACKER_BIG_PAGES           ***

***                                   ***

*************************************************************************

Cannot get _POOL_TRACKER_BIG_PAGES type size

*************************************************************************

***                                   ***

***                                   ***

***   Your debugger is not using the correct symbols          ***

***                                   ***

***   In order for this command to work properly, your symbol path   ***

***   must point to .pdb files that have full type information.    ***

***                                   ***

***   Certain .pdb files (such as the public OS symbols) do not    ***

***   contain the required information.  Contact the group that    ***

***   provided you with these symbols if you need this command to   ***

***   work.                              ***

***                                   ***

***   Type referenced: nt!_KPRCB                    ***

***                                   ***

*************************************************************************

*************************************************************************

***                                   ***

***                                   ***

***   Your debugger is not using the correct symbols          ***

***                                   ***

***   In order for this command to work properly, your symbol path   ***

***   must point to .pdb files that have full type information.    ***

***                                   ***

***   Certain .pdb files (such as the public OS symbols) do not    ***

***   contain the required information.  Contact the group that    ***

***   provided you with these symbols if you need this command to   ***

***   work.                              ***

***                                   ***

***   Type referenced: nt!_POOL_HEADER                 ***

***                                   ***

*************************************************************************

*************************************************************************

***                                   ***

***                                   ***

***   Your debugger is not using the correct symbols          ***

***                                   ***

***   In order for this command to work properly, your symbol path   ***

***   must point to .pdb files that have full type information.    ***

***                                   ***

***   Certain .pdb files (such as the public OS symbols) do not    ***

***   contain the required information.  Contact the group that    ***

***   provided you with these symbols if you need this command to   ***

***   work.                              ***

***                                   ***

***   Type referenced: nt!_POOL_HEADER                 ***

***                                   ***

*************************************************************************

*************************************************************************

***                                   ***

***                                   ***

***   Your debugger is not using the correct symbols          ***

***                                   ***

***   In order for this command to work properly, your symbol path   ***

***   must point to .pdb files that have full type information.    ***

***                                   ***

***   Certain .pdb files (such as the public OS symbols) do not    ***

***   contain the required information.  Contact the group that    ***

***   provided you with these symbols if you need this command to   ***

***   work.                              ***

***                                   ***

***   Type referenced: nt!_POOL_TRACKER_BIG_PAGES           ***

***                                   ***

*************************************************************************

Cannot get _POOL_TRACKER_BIG_PAGES type size

*************************************************************************

***                                   ***

***                                   ***

***   Your debugger is not using the correct symbols          ***

***                                   ***

***   In order for this command to work properly, your symbol path   ***

***   must point to .pdb files that have full type information.    ***

***                                   ***

***   Certain .pdb files (such as the public OS symbols) do not    ***

***   contain the required information.  Contact the group that    ***

***   provided you with these symbols if you need this command to   ***

***   work.                              ***

***                                   ***

***   Type referenced: nt!_KPRCB                    ***

***                                   ***

*************************************************************************

*************************************************************************

***                                   ***

***                                   ***

***   Your debugger is not using the correct symbols          ***

***                                   ***

***   In order for this command to work properly, your symbol path   ***

***   must point to .pdb files that have full type information.    ***

***                                   ***

***   Certain .pdb files (such as the public OS symbols) do not    ***

***   contain the required information.  Contact the group that    ***

***   provided you with these symbols if you need this command to   ***

***   work.                              ***

***                                   ***

***   Type referenced: nt!_KPRCB                    ***

***                                   ***

*************************************************************************

Probably caused by : ntoskrnl.exe ( nt+70700 )

I još malo:

Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2

*** WARNING: Unable to verify timestamp for ntoskrnl.exe

*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe

Windows 7 Kernel Version 7600 MP (4 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 7600.16792.amd64fre.win7_gdr.110408-1633

Machine Name:

Kernel base = 0xfffff800`02c49000 PsLoadedModuleList = 0xfffff800`02e86e50

Debug session time: Wed Jun 22 14:21:31.223 2011 (UTC + 2:00)

System Uptime: 0 days 0:02:58.645

Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2

*** WARNING: Unable to verify timestamp for ntoskrnl.exe

*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe

Loading Kernel Symbols

...............................................................

................................................................

......................

Loading User Symbols

Loading unloaded module list

....

*******************************************************************************

*                                        *

*             Bugcheck Analysis                   *

*                                        *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff80002decf8c, 0, ffffffffffffffff}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************

***                                   ***

***                                   ***

***   Your debugger is not using the correct symbols          ***

***                                   ***

***   In order for this command to work properly, your symbol path   ***

***   must point to .pdb files that have full type information.    ***

***                                   ***

***   Certain .pdb files (such as the public OS symbols) do not    ***

***   contain the required information.  Contact the group that    ***

***   provided you with these symbols if you need this command to   ***

***   work.                              ***

***                                   ***

***   Type referenced: nt!_KPRCB                    ***

***                                   ***

*************************************************************************

*************************************************************************

***                                   ***

***                                   ***

***   Your debugger is not using the correct symbols          ***

***                                   ***

***   In order for this command to work properly, your symbol path   ***

***   must point to .pdb files that have full type information.    ***

***                                   ***

***   Certain .pdb files (such as the public OS symbols) do not    ***

***   contain the required information.  Contact the group that    ***

***   provided you with these symbols if you need this command to   ***

***   work.                              ***

***                                   ***

***   Type referenced: nt!_KPRCB                    ***

***                                   ***

*************************************************************************

*************************************************************************

***                                   ***

***                                   ***

***   Your debugger is not using the correct symbols          ***

***                                   ***

***   In order for this command to work properly, your symbol path   ***

***   must point to .pdb files that have full type information.    ***

***                                   ***

***   Certain .pdb files (such as the public OS symbols) do not    ***

***   contain the required information.  Contact the group that    ***

***   provided you with these symbols if you need this command to   ***

***   work.                              ***

***                                   ***

***   Type referenced: nt!_KPRCB                    ***

***                                   ***

*************************************************************************

Probably caused by : ntoskrnl.exe ( nt+1a3f8c )

C:\Windows\Minidump\062311-24468-01.dmp

  C:\Users\Koki\AppData\Local\Temp\WER-42687-0.sysdata.xml

Kod mene,naravno,opet problem sa kompom.Sve je bilo ljepo,radilo.I tako par dana nisam palio komp i nekako dodje mi zelja za igrat GTA 4.Nakon 10 min igranja BSOD.Ok,nema veze.Igram ponovno,opet BSOD.Gledam temp,dobre su.I sad pokusavam instalirat nove drivere za GTX 460 i na pola opet BSOD.Na kraju skeniram sa MBAM-om i Nortonom,nista nisu nasli.Ok,ajmo probat sa HD Tuneom,nema bad sectora.Na kraju nekako uspijem instalirat drivere za graficku,ali nakon nekoliko minuta opet BSOD.Danas provedem sat vremena na internetu da vidim hoce li opet se ugasit,nista.Nakon toga upalim F1 2010 i na ucitavanju opet BSOD.Probao sam memtest i oba dvije plocice su prosle bez greske.Sad,neki put odma cim pokrenem vise programa dodje BSOD.

Eh da,ovo kaze WhoCrashed: On Fri 15.7.2011 9:49:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini071511-01.dmp
This was probably caused by the following module: hal.dll (hal+0xC658)
Bugcheck code: 0x7F (0xD, 0x0, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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 15.7.2011 9:49:53 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalTranslateBusAddress+0x8F8)
Bugcheck code: 0x7F (0xD, 0x0, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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 14.7.2011 18:20:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini071411-03.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xCDB3F)
Bugcheck code: 0x1A (0x5003, 0xFFFFFFFFC0802000, 0x2A1C, 0xA1C43C)
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 Thu 14.7.2011 13:35:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini071411-02.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x672A7)
Bugcheck code: 0xD1 (0x4D0, 0x2, 0x0, 0xFFFFFFFF8BE6D2A7)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 14.7.2011 9:52:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini071411-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4DFD9)
Bugcheck code: 0xC5 (0x1868, 0x2, 0x0, 0xFFFFFFFF82F02770)
Error: DRIVER_CORRUPTED_EXPOOL
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 system attempted to access invalid memory at a process IRQL that was too high.
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.

Ništa, nikako ne možemo znati uzrok. Napravi ovako pa ako se opet pojavi ćemo znati u čemu je problem.

Nema veze, ako su 64-bitni windowsi, onda je 64 KB. Glavno da je stavljeno na Small memory dump.

meni se danas bsod dogodio par puta za redom i nije mi htjelo uc u windowse. ono sto sam uspio uhvatit okom,dok je kratko pokazivao razloge bsoda su: cache memory manager i  drugi put system service exception.

neznam tocno sta to znaci,samo znam da sam jucer reinstaliravao windowse,razlog je redovno odrzavanje kompjutera,format C particije,na kojoj mi je instaliran w7 ultimate 64bit.

prekjucer sam kupio nove 2 plocice corsair rama od 2 gb svaka plocica.sad sam isao isprobavat tj. vadit jednu plocicu da vidim da li je do loseg rama i ispada da je,jer mi je sad normalno usao u windowse.cini se da je ta prva plocica,koju sam izvadio,pokvarena i da je bsod nastajao zbog nje.

samo bih htio da mi netko potvrdi,da je bas zbog toga ili ipak moze biti jos nesto drugo.

Imam problem sa BSOD na systemu Win 7 x64, prosli su testovi prime95, memtest i visestruko testiranje u futuremark-u. Racunalo je poslan u servis... uredno naplaceno medutim nisu i neznaju uklonit kvar. Jedino sta trenutno imam je ovi ss pa ako mi mozete pomoc bijo bih vam zahvalan.

ipak nisam otkrio nista,nego me kompjuter *ebe u zdrav mozak.

danas sam trebao ic nosit memu na garanciju,ali sam isao probavat zadnji put.mijenjao sam sa svakom plocicom zasebno po slotovima,da vidim oce li mi bacit bsod.nije bio bsod,ali mi je nestalo slike na jednom od slotova.nakon 2 restarta sam ugasio komp i dodao jos jednu plocicu,onda je usao u windowse.

tu sam opet ugasio komp i izvadio onu plocicu koju sam naknadno stavio unutra.sada se slika pokazuje najnormalnije i tu sam odvrtio 2 sata memtesta,na tom "pokvarenom" slotu i sa "pokvarenom" plocicom.(da nebi bilo nismo znali,svi kablovi su bili ustekani,sto se tice grafe i monitora pa tako i ostalog..)

ali nista od greske,5 testova su prosli sa 100%.

onda sam stavio tu drugu plocicu i odvrtio opet 2 puta test,i opet je proslo sa 100%.

neznam vise sta bi radio,sad kao da se smirio,pa vise ne baca bsod,iako je prosli tjedan uporno bacao restart prije ulaska u windowse i bsodove.

prosao sam hard sa hd tuneom i nista,prosao sam sa mbamom i nista,memtest ne baca nista...bilo je par puta situacija di mi je zamrzno u pola testa, i tu sam mislio da je do rama,al sad neznam vise sta bi mislio.

-ostaju 2 mogucnosti,ili rami ili maticna a nikako nemogu ponovit situaciju da dobijem prisilno bsod,pa da onda vidim u cem je problem,iako kad mi je frend iscitavao fajlove od bsoda,rekao je da je do rama najvjerovatnije zbog fajlova sta je procitao.

-imao sam stare kingamax rame koje sam prodao,i radili su najnormalnije.onda sam stavio nove plocice,formatirao C particiju,i stavio svjeze windowse 64 bitne.2 dana je komp radio normalno,i tu su poceli problemi sa bsodovima

pretpostavljam da cu opet reinstalirat windowse.takoder mi je danas bacio gresku CMOS checksum bad,na pocetku paljenja kompa.koju sam dobio jos jednom prije jedno tjedan i pol.

1.Pregledao sam,i cini se sve u redu,neznam sad tocno kolko bi to trebalo bit nabubreno,ali po mojem je sve uredu.

2.Istina je da imam jogurt verziju windowsa,ali neznam zasto bi sad odjednom poceli radit probleme,kad ih vec 2 godine koristim bez problema.ako si pod zastitom mislio na antivirusni,imam punu verziju,licenciranu originalnim kljucem,BitDefender-a.

kolko se sjecam,niti jednom mi se windowsi nisu krešali u radu,nego samo u loading screenu,na pocetku ulaska u windowse.nakon par minuta restarta i bsod-a,bi usli normalno i radili normalno vise sati.

nemam nikog s kim bi se mogao zamijenit na dijelove,bar na jedan dan..svi su na moru,a i nemamo kompatibilne komponente.

evo ti link na moje minidump fileove,pa pogledaj i reci sta bi moglo bit,ako zelis.

http://dl.dropbox.com/u/29491981/bsod.zip

istina,sad nisam updejtao windowse,inace kad izbaci poruku da nisu genuine,onda bih upotrijebio onaj wat remover.prvo cu napravit sve updejtove,i ponovit postupak sa wat removeroma a onda ako ce bacat opet bsod-ove,probat cu stavit linux kao dual boot pa cemo vidjet.

sto se tice dio loga za rusenja,mislim da mi nema smisla,s obzirom da ima vise razloga zbog kojeg se bsod desava.tako da jedan dio loga nece obuhvatit cijeli problem.

-moja maticna je m3a770de am3 socket,pretpostavljam da su na njoj solid state kondenzatori,posto nije stara maticna.

p.s. danas mi je opet bacio bsod na pocetku ulaska u windowse.sad se prvo vidio samo pointer od misa,a podloga je bila crna,onda sam resetirao i tu mi je dosao do loading screena i resetirao se sam od sebe a prije tog je bacio bsod...bio je dual channel postavljen.ugasio sam komp i izvadio jednu plocicu,te opet upalio i sad je uspio uc u windowse bez problema.

ponudio mi je da pokrenem windows startup repair nesto,ali to sam vec bio pokrenuo i nista nije popravilo,tako da sam otisao na start windows normaly