Win7 continue schermate blu causate da ntkrnlpa.exe. HELP!!!

[nicola.donolato]

Ciao a tutti,
è una settimana che sto diventando matto col pc di mia nipote (PC che ho assemblato un paio di anni fa e che fino ala settimana scorsa aveva XP).
Chissà che cosa ha installato ma ad un certo punto ha iniziato a fare schermate blu e a riavviarsi.
Visto che c'ero ho sostituito l'HD e installato win7.
Le schermate blu continuavano:
ho insallato whocrashed che mi segnalava inizialmente atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.) e ntkrpamp.exe.

Per atikmdag.sys ho disattivato i driver ATI e messo quelli di window: ho fatto bene?

Per ntkrpamp.exe non capisco proprio cosa devo fare.

Vi metto l'analisi di whocrashed, che ha anche i dettagli del PC :

System Information (local)
computer name: LISA-PC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: AuthenticAMD AMD A4-3300 APU with Radeon(tm) HD Graphics AMD586, level: 18
2 logical processors, active mask: 3
RAM: 1855614976 total
VM: 2147352576, free: 2010976256



Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Thu 10/10/2013 12:02:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101013-17316-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xB9B1D)
Bugcheck code: 0x1A (0x41790, 0xFFFFFFFFC08027BC, 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 that cannot be identified at this time.



On Thu 10/10/2013 12:02:19 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrpamp.exe (nt!KeQueryActiveGroupCount+0x426)
Bugcheck code: 0x1A (0x41790, 0xFFFFFFFFC08027BC, 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 Thu 10/10/2013 05:47:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101013-23056-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDCD10)
Bugcheck code: 0x4E (0x99, 0x8BEB, 0x2, 0x1CB42)
Error: PFN_LIST_CORRUPT
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 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



Conclusion
3 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.



Spero riusciate ad aiutarmi, perchè da solo non ne vengo fuori...
Se ho tralasciato delle informazioni utili, chiedete pure...

Grazie in anticipo per la disponibilità
ciao

[tallines]

Originariamente inviato da nicola.donolato

Ciao a tutti,
è una settimana che sto diventando matto col pc di mia nipote (PC che ho assemblato un paio di anni fa e che fino ala settimana scorsa aveva XP).
Chissà che cosa ha installato ma ad un certo punto ha iniziato a fare schermate blu e a riavviarsi.
Visto che c'ero ho sostituito l'HD e installato win7.
Le schermate blu continuavano:
ho insallato whocrashed che mi segnalava inizialmente atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.) e ntkrpamp.exe.

Per atikmdag.sys ho disattivato i driver ATI e messo quelli di window: ho fatto bene?

Conclusion
3 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.

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.

Ciao praticamente dal report di WhoCrashad il problema è dovuto al driver in oggetto .

Riabilita i driver che hai disabilitato e aggiornali .

[nicola.donolato]

ok, ci provo....
Grazie ciao

[Blue_screen_of_death]

E No. I driver non c'entrano nulla. È un problema di gestione della memoria.
Quindi testa la RAM con MemTest86+.
Inizia testando i moduli singolarmente. Ne lasci collegato solo uno. E li controlli tutti uno per volta.
E ripeti il test in tutti gli slot.
Poi li testi tutti installati contemporaneamente. E ogni test deve durare 3 o 4 pass almeno.

[tallines]

Si facile che sia la Ram .

[nicola.donolato]

si infatti è una delle RAM.
Ne ho appena acquistate 2 di nuove (Corsair Ddr3 1333Mhz 4Gb 2X240 Dimm).
Di quella avanzata cosa posso farci?

[Blue_screen_of_death]

SE E SOLO SE è identica a quella che hai comprato, puoi installarla, a patto di avere slot liberi. Altrimenti la metti da parte. ^^

[tallines]

Originariamente inviato da nicola.donolato

si infatti è una delle RAM.
Ne ho appena acquistate 2 di nuove (Corsair Ddr3 1333Mhz 4Gb 2X240 Dimm).
Di quella avanzata cosa posso farci?

Se non c'è posto negli slot la conservi

[nicola.donolato]

grazie...