Bok svima! Novi sam tu, a nazalost boravak moram pocet ovako
Nedavno sam kupio kompjuter a mami za posao sam dao svoj stari, star cca 4 i pol godine. Na njemu se zadnjih 2, 3 mjeseca pojavljivao ovaj plavi ekran prije onog loga od windowsa XP, bio bi na ekranu pol sekunde, sam bi se resetirao komp i onda bi normalno usao u windowse. i to ne svaki put nego samo nekad (mislim da se to češće događa kad kompjuter vec malo radi pa se ugrije). Ja sam mislio da je to do harda pa smo kupili novi hard i eto ti problema
plavi ekran se nastavio pokazivat jednako kao i dosad... pokuso sam na milijon nacina i nista ne pali...
pa ajde pliz ako netko od vas ima neku ideju sta bi to moglo bit i kako testirat neka kaze.
Za početak navedi sve komponente te konfiguracije. Za prvu ruku loadaj bios na defaultne postavke pa ga tako probaj kresnuti, drugi korak je testiranje RAM-a memtestom, ako ne bude nikakvih errora na RAM-u idemo dalje u dijagnostiku
Imaš negdje u winsima (nažalost, ne mogu to provjeriti na ovom kompu) mogućnost da isključiš automatski restart kod BSOD-a. To isključi, pogledaj šta ti piše u vezi greške i proguglaj da vidiš o čemu se radi.
__________________
"Dvije stvari su beskonačne - svemir i ljudska glupost. Za svemir nisam siguran." A. Einstein
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Danko\Desktop\Mini010105-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: C:\Windows;C:\Windows\system32;C:\Windows\system32\drivers
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_qfe.061219-0311
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805535a0
Debug session time: Sat Jan 1 02:51:29.687 2005 (GMT+2)
System Uptime: 0 days 0:00:18.265
Loading Kernel Symbols
.
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
..............................................................
....................................................
Loading User Symbols
Loading unloaded module list
...
*** WARNING: Unable to verify timestamp for hal.dll
*** ERROR: Module load completed but symbols could not be loaded for hal.dll
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9C, {4, 805463f0, b2000000, 70f0f}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
MACHINE_CHECK_EXCEPTION (9c)
A fatal Machine Check Exception has occurred.
KeBugCheckEx parameters;
x86 Processors
If the processor has ONLY MCE feature available (For example Intel
Pentium), the parameters are:
1 - Low 32 bits of P5_MC_TYPE MSR
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of P5_MC_ADDR MSR
4 - Low 32 bits of P5_MC_ADDR MSR
If the processor also has MCA feature available (For example Intel
Pentium Pro), the parameters are:
1 - Bank number
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error
IA64 Processors
1 - Bugcheck Type
1 - MCA_ASSERT
2 - MCA_GET_STATEINFO
SAL returned an error for SAL_GET_STATEINFO while processing MCA.
3 - MCA_CLEAR_STATEINFO
SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA.
4 - MCA_FATAL
FW reported a fatal MCA.
5 - MCA_NONFATAL
SAL reported a recoverable MCA and we don't support currently
support recovery or SAL generated an MCA and then couldn't
produce an error record.
0xB - INIT_ASSERT
0xC - INIT_GET_STATEINFO
SAL returned an error for SAL_GET_STATEINFO while processing INIT event.
0xD - INIT_CLEAR_STATEINFO
SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event.
0xE - INIT_FATAL
Not used.
2 - Address of log
3 - Size of log
4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO
AMD64 Processors
1 - Bank number
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error
Arguments:
Arg1: 00000004
Arg2: 805463f0
Arg3: b2000000
Arg4: 00070f0f
Debugging Details:
------------------
NOTE: This is a hardware error. This error was reported by the CPU
via Interrupt 18. This analysis will provide more information about
the specific error. Please contact the manufacturer for additional
information about this error and troubleshooting assistance.
This error is documented in the following publication:
- Bios and Kernel Developers Guid for AMD Athlon(r) 64 and AMD Opteron(r) Processors
Bit Mask:
MA Model Specific MCA
O ID Other Information Error Code Error Code
VV SDP ___________|____________ _______|_______ _______|______
AEUECRC| | | |
LRCNVVC| | | |
^^^^^^^| | | |
6 5 4 3 2 1
3210987654321098765432109876543210987654321098765432109876543210
----------------------------------------------------------------
1011001000000000000000000000000000000000000001110000111100001111
VAL - MCi_STATUS register is valid
Indicates that the information contained within the IA32_MCi_STATUS
register is valid. When this flag is set, the processor follows the
rules given for the OVER flag in the IA32_MCi_STATUS register when
overwriting previously valid entries. The processor sets the VAL
flag and software is responsible for clearing it.
UC - Error Uncorrected
Indicates that the processor did not or was not able to correct the
error condition. When clear, this flag indicates that the processor
was able to correct the error condition.
EN - Error Enabled
Indicates that the error was enabled by the associated EEj bit of the
IA32_MCi_CTL register.
PCC - Processor Context Corrupt
Indicates that the state of the processor might have been corrupted
by the error condition detected and that reliable restarting of the
processor may not be possible.
BUSCONNERR - Bus and Interconnect Error BUS{LL}_{PP}_{RRRR}_{II}_{T}_err
These errors match the format 0000 1PPT RRRR IILL
This error code can be reported back to the manufacturer.
They may be able to provide additional information based upon
this error. All questions regarding STOP 0x9C should be
directed to the hardware manufacturer.
BUGCHECK_STR: 0x9C_AuthenticAMD
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
PROCESS_NAME: System
LAST_CONTROL_TRANSFER: from 806d38d7 to 804f8c3f
STACK_TEXT:
805463c8 806d38d7 0000009c 00000004 805463f0 nt!KeBugCheckEx+0x1b
WARNING: Stack unwind information not available. Following frames may be wrong.
805464f4 806cec2e 80042000 00000000 00000000 hal+0x58d7
00000000 00000000 00000000 00000000 00000000 hal+0xc2e
a komponente su:
AMD Athlon 3200+
Gigabyte maticna (nisam siguran tocno koja, mogu pogledat)
Ati radeon x800
2x2 512 rama kingmax
Samsung hard
Codegen 400W napajanje
unaprijed
-->
1. hvala vam na brzom odgovoru
restarto sam bios - ista stvar
pokreno sam memtest iz windowsa i sa ubuntu cd-a. ne nalazi nista
hard disk valjda nije jer sam ga promijenio i stavio novi
probo sam stavit i to da se ne restarta automatski, ali se on svedno resetira odmah. ali sam mu stavio da sejva taj .dmp file u kojem pise sve o tom fatal erroru i njega sam malo proucio. tu cu nabacit sad sta mi on kaze:
Opened log file 'c:debuglog.txt'
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Danko\Desktop\Mini010105-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: C:\Windows;C:\Windows\system32;C:\Windows\system32\drivers
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_qfe.061219-0311
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805535a0
Debug session time: Sat Jan 1 02:51:29.687 2005 (GMT+2)
System Uptime: 0 days 0:00:18.265
Loading Kernel Symbols
.
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
..............................................................
....................................................
Loading User Symbols
Loading unloaded module list
...
*** WARNING: Unable to verify timestamp for hal.dll
*** ERROR: Module load completed but symbols could not be loaded for hal.dll
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9C, {4, 805463f0, b2000000, 70f0f}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
MACHINE_CHECK_EXCEPTION (9c)
A fatal Machine Check Exception has occurred.
KeBugCheckEx parameters;
x86 Processors
If the processor has ONLY MCE feature available (For example Intel
Pentium), the parameters are:
1 - Low 32 bits of P5_MC_TYPE MSR
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of P5_MC_ADDR MSR
4 - Low 32 bits of P5_MC_ADDR MSR
If the processor also has MCA feature available (For example Intel
Pentium Pro), the parameters are:
1 - Bank number
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error
IA64 Processors
1 - Bugcheck Type
1 - MCA_ASSERT
2 - MCA_GET_STATEINFO
SAL returned an error for SAL_GET_STATEINFO while processing MCA.
3 - MCA_CLEAR_STATEINFO
SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA.
4 - MCA_FATAL
FW reported a fatal MCA.
5 - MCA_NONFATAL
SAL reported a recoverable MCA and we don't support currently
support recovery or SAL generated an MCA and then couldn't
produce an error record.
0xB - INIT_ASSERT
0xC - INIT_GET_STATEINFO
SAL returned an error for SAL_GET_STATEINFO while processing INIT event.
0xD - INIT_CLEAR_STATEINFO
SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event.
0xE - INIT_FATAL
Not used.
2 - Address of log
3 - Size of log
4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO
AMD64 Processors
1 - Bank number
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error
Arguments:
Arg1: 00000004
Arg2: 805463f0
Arg3: b2000000
Arg4: 00070f0f
Debugging Details:
------------------
NOTE: This is a hardware error. This error was reported by the CPU
via Interrupt 18. This analysis will provide more information about
the specific error. Please contact the manufacturer for additional
information about this error and troubleshooting assistance.
This error is documented in the following publication:
- Bios and Kernel Developers Guid for AMD Athlon(r) 64 and AMD Opteron(r) Processors
Bit Mask:
MA Model Specific MCA
O ID Other Information Error Code Error Code
VV SDP ___________|____________ _______|_______ _______|______
AEUECRC| | | |
LRCNVVC| | | |
^^^^^^^| | | |
6 5 4 3 2 1
3210987654321098765432109876543210987654321098765432109876543210
----------------------------------------------------------------
1011001000000000000000000000000000000000000001110000111100001111
VAL - MCi_STATUS register is valid
Indicates that the information contained within the IA32_MCi_STATUS
register is valid. When this flag is set, the processor follows the
rules given for the OVER flag in the IA32_MCi_STATUS register when
overwriting previously valid entries. The processor sets the VAL
flag and software is responsible for clearing it.
UC - Error Uncorrected
Indicates that the processor did not or was not able to correct the
error condition. When clear, this flag indicates that the processor
was able to correct the error condition.
EN - Error Enabled
Indicates that the error was enabled by the associated EEj bit of the
IA32_MCi_CTL register.
PCC - Processor Context Corrupt
Indicates that the state of the processor might have been corrupted
by the error condition detected and that reliable restarting of the
processor may not be possible.
BUSCONNERR - Bus and Interconnect Error BUS{LL}_{PP}_{RRRR}_{II}_{T}_err
These errors match the format 0000 1PPT RRRR IILL
This error code can be reported back to the manufacturer.
They may be able to provide additional information based upon
this error. All questions regarding STOP 0x9C should be
directed to the hardware manufacturer.
BUGCHECK_STR: 0x9C_AuthenticAMD
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
PROCESS_NAME: System
LAST_CONTROL_TRANSFER: from 806d38d7 to 804f8c3f
STACK_TEXT:
805463c8 806d38d7 0000009c 00000004 805463f0 nt!KeBugCheckEx+0x1b
WARNING: Stack unwind information not available. Following frames may be wrong.
805464f4 806cec2e 80042000 00000000 00000000 hal+0x58d7
00000000 00000000 00000000 00000000 00000000 hal+0xc2e
Ovu kobasicu si mogao i u screen shot staviti Otvori malo kućište i provjeri situaciju sa cpu hladnjakom u kakvom je stanju, je li koja kopča koja ga drži za matičnu slučajno izletjela van, možeš i u biosu provjeriti temperaturu proca. Btw. jesi pokušao ući u winse u safe modu?
EDIT - stavio si u spoiler, much better
@veve - slažem se, ovaj Šrotegen je najslabija karika cijele konfe, svakako probati s nekim drugim.
hm. provjeravao sam jucer temperature proca. ide najvise do 45°C sto mi se ne cini nis strasno. Otvarali smo i hladnjak na procesoru i stavljali novu pastu. jedan kondenzator je bio nabubrio na maticnoj pa sam bio siguran da je to. međutim frend ga je zaminjenio sa drugim i ista stvar.
rado bih probao sa nekim drugim napajanjem al otkud mi ako ne mislim odmah kupovat drugo prije nego se dijagnosticira problem mislim nije problem uzet novo, ali samo da sam siguran da je do tog. ima jos kakvih ideja?
rado bih probao sa nekim drugim napajanjem al otkud mi ako ne mislim odmah kupovat drugo prije nego se dijagnosticira problem mislim nije problem uzet novo, ali samo da sam siguran da je do tog. ima jos kakvih ideja?
Nismo ni mislili da ideš kupiti nego da posudiš od nekog frenda ili slično, isto tako ako netko ima proc koji ide na tvoj socket posudi pa ubodi drugi proc jer za sada je on uz napajanje prvi sumnjivac.
a neznam stvarno do cega je. jucer sam proveo 6 sati pred ekranom i copy/pastao dijelove iz spojlera da nadjem ako je netko imao nesto slicno i kako je rijesio. medjutim naso sam na blesave izjave tipa: "sigurno je do rama, proca, harda, mobo, graficke ili napajanja".
ma daj ono, to i ja znam
Citiraj:
Autor Doink the Clown
Nismo ni mislili da ideš kupiti nego da posudiš od nekog frenda ili slično, isto tako ako netko ima proc koji ide na tvoj socket posudi pa ubodi drugi proc jer za sada je on uz napajanje prvi sumnjivac.
jeli postoji neki nacin da provjerim stabilnost proca? umjesto da stavljam drugi?
jer jucer sam isao na everest na test stabilnosti i opteretio ga na 100% nekih 10ak minuta tako da se zagrijo maximalno. i sve je ok u windowsima. nikad mi se ne srusi iz windowsa. samo pri startu windowsa. i to samo nekad.
uglavnom prvih 5-10 puta kad ga palim bude sve oke i onda kad se malo zagrije redovno baca na startu taj blue screen. a mama mi nece ni cut za to jer drzi bitne podatke za posao na kompu pa hoce da bude siguran.
Dakle, da rezimiramo: testirao si memu i proc ima normalnu temperaturu. Jedino što preostaje je matična. Obzirom da si mijenjao kondić, velika je vjerojatnost da je taj naponski izboj povukao još nešto sa sobom.
EDIT: stabilnost proca možeš provjeriti sa OCCT-om.
__________________
"Dvije stvari su beskonačne - svemir i ljudska glupost. Za svemir nisam siguran." A. Einstein
ali ja kad opteretim everestom proc 10min on onda pri restartu redovno baca taj ekran. tako da ce i sa tim OCCTom isto sigurno dajte molim vas neko rješenje aaaaaaaaaaa jer ce me mamita udavit
onda ovako:
-hard nije jer sam mijenjao i stavio novi. zar ne?
-memorija valjda nije jer sam pokrenuo ta 2 testa i vadio jednu po jednu pločicu van i sa obje se dogadjala ista stvar.
-grafička? je postoji ikakva sansa da je do nje? mada ja nevidim razlog zasto bi bilo
Ja bih rekao da je taj kondenzator koji je vrisnuo bacio neki izboj koji je sredio matičnu (konkretnije, socket za proc) kao što reče uvaženi kolega coconut ranije, samo se nadam da nije i proc nastradao, potraži nekoga tko ima matičnu za istim socketom i tako testiraj ovo navedeno. Grafička? Sumnjam, prije će biti do matične i cpu-a
Ja bih rekao da je taj kondenzator koji je vrisnuo bacio neki izboj koji je sredio matičnu (konkretnije, socket za proc) kao što reče uvaženi kolega coconut ranije, samo se nadam da nije i proc nastradao, potraži nekoga tko ima matičnu za istim socketom i tako testiraj ovo navedeno. Grafička? Sumnjam, prije će biti do matične i cpu-a
hm nisam siguran da je taj kondenzator bacio nesto jer nije bio otvoren ni gore ni dolje. samo je s obje strane nabubrio. taj frend sto mi je to mijenjao mi kaze da je njemu pred neke 3 god 8 kondenzatora vrisnulo i bas da je teklo nes iz njih i sve i promijenio ih je i dan danas ta maticna radi ko nova hm moguce da je do proca kad redovno baca BSOD kad se zagrije.
evo sad ga pržim, al sam iskopco sve nepotrebno (zip, mrežna, flopi, dvdrom, tv karticu... ) pa ako sad bude radilo moguce da je do napajanja, sta ne?
29.07.2009., 12:31
A R O U N D
unaprijed 
Otvori malo kućište i provjeri situaciju sa cpu hladnjakom u kakvom je stanju, je li koja kopča koja ga drži za matičnu slučajno izletjela van, možeš i u biosu provjeriti temperaturu proca. Btw. jesi pokušao ući u winse u safe modu?
mislim nije problem uzet novo, ali samo da sam siguran da je do tog. ima jos kakvih ideja? 
