ntkrnlpa.exe i halmacpi.dll
- Začetnik teme boki1997
- Datum pokretanja
Član
- Učlanjen(a)
- 10.11.2009
- Poruka
- 1.654
te crvene x oznake sto vidis to su ti greske, a kad kliknes na neku od njih ispod ti pise kao na slici sto si vec pokazao opis greske, na tvojoj slici skajp i tab search nisu radili kako treba, pregledaj i za ostale dane, vidi kakve se jos greske javljaju, vidi da nema kakvih hardverskih gresaka, instaliraj i tune up, nek malo on odradi posla na kompu
Član
- Učlanjen(a)
- 06.09.2009
- Poruka
- 1.388
Nije problem RAM memorija (kvar memorije), već driver za CPU, najverovatnije je narušen odnos sa nekim od modula RAM-a (CPU FSB:RAM), kada se odnos tih frekvencija naruši, dolazi do konflikta sa driver-om, koji je takođe vezan za podešavanja u BIOS-u.
Drugo nisi rekao koja je ploča, CPU i RAM?
Nemožemo napamet da ti pomognemo bez tih osnovnih informacija.
Treće nisi rekao od kada je počeo taj problem sa BSOD-om, da li si naknadno instalirao RAM, software, menjao CPU, radio OC RAM-a ili CPU-a i sl?
Dakle napiši nam konkretno, šta si radio (menjao, dodavao), instalirao itd, kako si testirao RAM (kojim programom)?
Instaliraćeš ovaj besplatni program WhoCrashed za analizu BSOD-a, da vidimo sve BSOD-ove (Dump files):
Drugo nisi rekao koja je ploča, CPU i RAM?
Nemožemo napamet da ti pomognemo bez tih osnovnih informacija.
Treće nisi rekao od kada je počeo taj problem sa BSOD-om, da li si naknadno instalirao RAM, software, menjao CPU, radio OC RAM-a ili CPU-a i sl?
Dakle napiši nam konkretno, šta si radio (menjao, dodavao), instalirao itd, kako si testirao RAM (kojim programom)?
Instaliraćeš ovaj besplatni program WhoCrashed za analizu BSOD-a, da vidimo sve BSOD-ove (Dump files):
Kod:
http://www.resplendence.com/downloadsmaticna je G31M-ES2L,intel dual core 2.50,RAM 1 gb (posto sam 1 mako) DDR 2
problem je poceo bukvalno 2,3 meseca nakon sto sam kupio komp (nista nisam dodatno dogradjivao)
RAM sam testirao programom memtest86+
whocrashed vec imam instalirao kao i bluescreen viewer
uradicu analizu sa whocrashed pa stavljam rezultate
evo analize iz whoCrashed
On Sat 27/10/2012 12:29:28 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrpamp.exe (nt+0xDEE98)
Bugcheck code: 0x4E (0x99, 0x13882, 0x2, 0x23B41)
Error: PFN_LIST_CORRUPThttp://www.google.com/search?q=MSDN+bugcheck+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: ntkrpamp.exe .
Google query: ntkrpamp.exe PFN_LIST_CORRUPThttp://www.google.com/search?q=ntkrpamp.exe+PFN_LIST_CORRUPT
On Fri 19/10/2012 09:26:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101912-16941-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xC0703)
Bugcheck code: 0x1A (0x3452, 0x6AAE000, 0xFFFFFFFFC080EA68, 0x0)
Error: MEMORY_MANAGEMENThttp://www.google.com/search?q=MSDN+bugcheck+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 27/10/2012 12:29:28 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrpamp.exe (nt+0xDEE98)
Bugcheck code: 0x4E (0x99, 0x13882, 0x2, 0x23B41)
Error: PFN_LIST_CORRUPThttp://www.google.com/search?q=MSDN+bugcheck+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: ntkrpamp.exe .
Google query: ntkrpamp.exe PFN_LIST_CORRUPThttp://www.google.com/search?q=ntkrpamp.exe+PFN_LIST_CORRUPT
On Fri 19/10/2012 09:26:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101912-16941-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xC0703)
Bugcheck code: 0x1A (0x3452, 0x6AAE000, 0xFFFFFFFFC080EA68, 0x0)
Error: MEMORY_MANAGEMENThttp://www.google.com/search?q=MSDN+bugcheck+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.
Poslednja izmena od urednika:
Član
- Učlanjen(a)
- 06.09.2009
- Poruka
- 1.388
Prvo, trebao si odmah reklamirati, a ne da čekaš 3 meseca, jer BSOD je ozbiljna stvar, i opet nisi rekao model CPU-a (pretpostavljam da je E5200) i koja je memorija, tj., na kojoj frekvenciji RAM radi?
Drugo, prvo ćeš uraditi update BIOS-a, skini odavde BIOS F10:
Skini i pokreni instalaciju, kad sve završiš restartuj komp, zatim ćeš ući u BIOS i pod sekcijom MB Intelligent Tweaker podesiti ovako:
CPU Clock ratio izaberi 12.5X (ako je taj processor koji sam iznad opisao E5200)
CPU Host Clock Control postavi na Enabled
CPU Host Frequency postavi na 200Mhz
System Memory Multiplier postavi na AUTO (bilo bi poželjno da već znaš frekvenciju RAMa, kako bi je ispod ove opcije namestio ručno)
I na kraju imaš podsekciju System Voltage control, gde ćeš sve postaviti na Normal.
To su podešavanja za naveden CPU i pretpostavkom da je RAM 800Mhz, baš zbog tog odnosa između FSB-a i Clock-a RAM-a, pošto CPU ima podršku za Quad Data rate.
Processor si trebao detaljnije navesti jer postoje 2 dual core cpu-a, koji imaju istu radnu frekvenciju E3300 i 5200, isto ime Wolfdale, s tim što je šerovan L2 cache kod E3300 1MB, a kod E5200 2MB i postoji razlika u BIOS-u za podršku, E3300 radi sa F9 verzijom, dok E5200 sa F5 ili F3 (zavisno od Steppinga).
Odradi sve ovo, instaliraj posle AIDA64 Extreme, evo ti link:
Registruj AIDA64 i odradi Stability test, u testu checkiraj sve i prati stanje, takođe u AIDA pogledaj specifikacije kompa, CPU i RAM i prekopiraj ovde da vidimo
Drugo, prvo ćeš uraditi update BIOS-a, skini odavde BIOS F10:
Kod:
http://www.gigabyte.com/products/product-page.aspx?pid=2889#biosCPU Clock ratio izaberi 12.5X (ako je taj processor koji sam iznad opisao E5200)
CPU Host Clock Control postavi na Enabled
CPU Host Frequency postavi na 200Mhz
System Memory Multiplier postavi na AUTO (bilo bi poželjno da već znaš frekvenciju RAMa, kako bi je ispod ove opcije namestio ručno)
I na kraju imaš podsekciju System Voltage control, gde ćeš sve postaviti na Normal.
To su podešavanja za naveden CPU i pretpostavkom da je RAM 800Mhz, baš zbog tog odnosa između FSB-a i Clock-a RAM-a, pošto CPU ima podršku za Quad Data rate.
Processor si trebao detaljnije navesti jer postoje 2 dual core cpu-a, koji imaju istu radnu frekvenciju E3300 i 5200, isto ime Wolfdale, s tim što je šerovan L2 cache kod E3300 1MB, a kod E5200 2MB i postoji razlika u BIOS-u za podršku, E3300 radi sa F9 verzijom, dok E5200 sa F5 ili F3 (zavisno od Steppinga).
Odradi sve ovo, instaliraj posle AIDA64 Extreme, evo ti link:
Kod:
http://www.softpedia.com/get/System/System-Info/AIDA64-Extreme-Edition.shtml
serial:UAHLY-VF8D6-FUDG2-74DR4-U8YDV
Poslednja izmena od urednika:
Član
- Učlanjen(a)
- 06.09.2009
- Poruka
- 1.388
Ne menja podešavanja znatno, osim što ćeš skinuti BIOS ver. F10 i napiši koja je ta memorija već jednom?
Koja je brzina memorije, da bi ručno podesio brzinu u BIOS-u i napiši koji je model, sve to možeš saznati iz AIDA64?
I ubaci da rade obe memorije
Koja je brzina memorije, da bi ručno podesio brzinu u BIOS-u i napiši koji je model, sve to možeš saznati iz AIDA64?
I ubaci da rade obe memorije
Poslednja izmena:
On Tue 30/10/2012 05:21:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\103012-15802-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x8DB3F)
Bugcheck code: 0x50 (0xFFFFFFFFCAFD33DB, 0x0, 0xFFFFFFFF82AC8016, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
a opet mi se pojavilo al sa drugom sifrom,sta ova znaci?
crash dump file: C:\Windows\Minidump\103012-15802-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x8DB3F)
Bugcheck code: 0x50 (0xFFFFFFFFCAFD33DB, 0x0, 0xFFFFFFFF82AC8016, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
a opet mi se pojavilo al sa drugom sifrom,sta ova znaci?
Poslednja izmena od urednika: