PC-HELP.CZ

Už po několikáté se mi stalo že se mi na svém starém PC objevila modrá smrt. Nejde mi foťák tak to sem opíšu.

A problem has been detected and Windows has been shut down to prevent damage to your computer.

MEMORY_MANAGEMENT

If this is the first time you've seen this stop error screen, restart your computer, if this screen appers again, follow these steps:

Check to make sure any new hardware or software is properly installed, if this is a new installation ask your hardware or software manufacturer for any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware or software, disable BIOS memory options suchs as caching or shadowing. If you need to use safe mode to remove or disable components, restart your computer, press F8 to select Advanced Startup option, and then select Safe mode.

Technical information

*** Stop: 0x0000001A (0x00041790, 0xc0802768, 0x0000FFFF, 0x00000000)

Collecting data for crash dump ...
Initializing disk for crash dump ...
Beginning dump of physical memory.
Dumping physical memory to disk: 100
Physical memory to disk: 100
Pchysical memory dump complete.
Contact your system admin or technical support group for further assistance.

Počítač mám ten stařičký:
AMD Athlon 64 Processor 3200+ (procesor)
A8N-SLI PREMIUM (deska)
2Gb Ram
Nvidia Geforce GT 220
disk mám tento: http://www.czechcomputer.cz/product.jsp?artno=65071
Windows 7 Home Premium 32 bit (legalní)

Počítač byl poskládán ze starých dílů na internet a e-mail.

Stáhni si Memtest:

Do políčka vlož největší velikost Tvé jednotlivé paměti RAM (256,512 nebo 1024,2048) dej Start , nech nejméně 2h běžet , pokud bude po 2h stále 0 errors , jsou v pořádku.

Stáhni si a nainstaluj WhoCrashed

otevři ho a klikni na Analyze.
Program vytvoří zprávu , zkopíruj celou a vlož prosím sem.

a co když mám ty ramky takhle já mám dvoje adata s 512 mb a jednu corsaire s 1 gb

--- Doplnění předchozího příspěvku (23 Srp 2011 10:22) ---

ty adata jedou v dualu

dej 1024 nech 2h pak dej 512 a opakuj.

j zatím

--- Doplnění předchozího příspěvku (23 Srp 2011 10:58) ---

To je v pr.... dal jsem tech 1024 a uz mam prez 1600 eroru ta uz asi nebude pouzitelna co?
Pisu prez mobil

RAM je v háji , ještě udělej tohle:
Vypni PC , vyndej tu RAM , očisti kontakty ( opatrně , pozor na stat. elektřinu!) a zase ji pořádně zasuň do slotu.

udělej znovu memtest (1024) , pokud se Ti vyskytne chyba , tak je RAM vadná. Vyjmi ji , při vypnutém PC , zapni a otestuj ty další RAM (512)...

v klidu do 42% pak to našlo 50 erroru teď jdu na ty ostatní jo a zjistil jsem že ta špatná byla adata a ty v tom dualu jsou corsairy

--- Doplnění předchozího příspěvku (23 Srp 2011 14:20) ---

takže tyhle ramky jdou v pohodě

doufám že je tohle správný log


System Information (local)
--------------------------------------------------------------------------------

computer name: ONDRA-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: AuthenticAMD AMD Athlon(tm) 64 Processor 3200+ AMD586, level: 15
1 logical processors, active mask: 1
RAM: 1073274880 total
VM: 2147352576, free: 1964105728



--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Tue 23.8.2011 7:10:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082311-24281-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x9FCE2)
Bugcheck code: 0x1A (0x41790, 0xFFFFFFFFC0802768, 0xFFFF, 0x0)
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 Tue 23.8.2011 7:10:43 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrpamp.exe (nt!ExFreeToPagedLookasideList+0x4B8)
Bugcheck code: 0x1A (0x41790, 0xFFFFFFFFC0802768, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
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.
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 MEMORY_MANAGEMENT




On Mon 22.8.2011 15:36:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082211-22890-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x121996)
Bugcheck code: 0x19 (0x3, 0xFFFFFFFFA6B64810, 0xFFFFFFFFA6B64810, 0x1)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
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 Thu 18.8.2011 19:03:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082011-20750-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x8D07B)
Bugcheck code: 0x116 (0xFFFFFFFF8580E510, 0xFFFFFFFF9242C152, 0xFFFFFFFFC000009A, 0x4)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
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 18.8.2011 14:32:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081811-21703-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x8D07B)
Bugcheck code: 0x116 (0xFFFFFFFF858BC008, 0xFFFFFFFF94C2C152, 0xFFFFFFFFC000009A, 0x4)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
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 Wed 17.8.2011 18:37:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081711-23968-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x8E3DB)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFF6DC, 0x1, 0xFFFFFFFF8305DADC, 0x0)
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.


On Wed 17.8.2011 18:23:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081711-27296-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x415DB)
Bugcheck code: 0xA (0xFFFFFFFFB3C48189, 0x2, 0x0, 0xFFFFFFFF82ED6315)
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.



--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

7 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

ntkrpamp.exe

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

Chyb je tam stejně dost..

Možná je vadný i slot pro tu RAMku...( zákl.deska).

Nech tam jen ty dvě dual.

vypálit soubor .iso a nabootovat z mechaniky CD/DVD.

http://www.memtest86.com/

http://www.pcporadenstvi.cz/memtest-86

+
Klikni na této stránce na výrobce Tvého HDD:
http://www.tacktech.com/display.cfm?ttid=287
Stáhni si CD ( .iso) vypal a vlož do mechaniky a nabootuj.
Program by měl diagnostikovat chyby na disku.

vím že mám tenhle typ ale nevím co stáhnout jestli ten první nebo ten poslední odkaz
http://support.wdc.com/product/download ... 08&lang=en

--- Doplnění předchozího příspěvku (23 Srp 2011 15:07) ---

a ještě mi nejde nikde najít ten iso soubor

Ten pro Windows:
Data Lifeguard Diagnostic for Windows

+
Data Lifeguard Tools 11.0 for DOS and Windows (CD) (01.02.2007)

Memtest 86 si vypálil?

ten nemůžu najít a kde taky najdu ten Data Lifeguard Tools 11.0 for DOS and Windows (CD) (01.02.2007)
buď jsem blbý nebo budu potřebovat brýle a kurz angličtiny

Tak tady máš screen z Western Digital.