Random BSOD dopo upgrade RAM

[homeruccio91]

Salve a tutti,
come da titolo sto sperimentando frequenti BSOD da quando ho upgradato la RAM. Per assicurarmi che i banchi comprati (2*2 GB Kingston) non fossero difettosi ho eseguito un memtest. Testandoli in coppia, nel pass 4 sono stati riscontrati 8 errori. Ho eseguito allora il test sui singoli banchi ma non ci sono stati errori, ho anche cambiato slot pensando potessi avere degli slot difettosi sulla mobo e nuovamente non ho riscontrato errori. Ho eseguito allora un clear CMOS e ritestato i moduli sia in coppia che singolarmente (per circa 10h) nessun errore. Ho provato allora a attivare driver verifier per capire se potesse essere un problema software e il risultato è che il pc non si avvia e viene mostrata una BSOD con il messaggio di STOP 0x000000C4 .
Ho salvato i minidump ma non so davvero che pesci prendere.
Testando l'hard disk ho notato che ci sono dei settori corrotti,potrebbe essere l' HD la causa di tutto?
Help please

EDIT: aggiunti minidump

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

The problem seems to be caused by the following file: xNtKrnl.exe

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears 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 such 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 Options, and then
select Safe Mode.

Technical Information:

*** STOP: 0x1000007e (0xffffffffc0000005, 0xfffff8000355f5a8, 0xfffff880039e71b8, 
0xfffff880039e6a20)

*** xNtKrnl.exe - Address 0xfffff8000355f5a8 base at 0xfffff8000321f000 DateStamp 
0x4d9fdd34

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

The problem seems to be caused by the following file: intelppm.sys

IRQL_NOT_LESS_OR_EQUAL

If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears 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 such 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 Options, and then
select Safe Mode.

Technical Information:

*** STOP: 0x0000000a (0x00000d700079db58, 0x0000000000000002, 0x0000000000000001, 
0xfffff800032da3a4)

*** intelppm.sys - Address 0xfffffa800038a390 base at 0xfffff88003dd5000 DateStamp 
0x4a5bc0fd

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

The problem seems to be caused by the following file: raspppoe.sys

MEMORY_MANAGEMENT

If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears 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 such 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 Options, and then
select Safe Mode.

Technical Information:

*** STOP: 0x0000001a (0x0000000000041790, 0xfffffa80019a9340, 0x000000000000ffff, 
0x0000000000000000)

*** raspppoe.sys - Address 0xfffffa80019a9340 base at 0xfffff88003f6d000 DateStamp 
0x4a5bcce9

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

The problem seems to be caused by the following file: CI.dll

SYSTEM_SERVICE_EXCEPTION

If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears 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 such 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 Options, and then
select Safe Mode.

Technical Information:

*** STOP: 0x0000003b (0x00000000c0000005, 0xfffff88000e99714, 0xfffff88006bccc10, 
0x0000000000000000)

*** CI.dll - Address 0xfffff88000e99714 base at 0xfffff88000e4a000 DateStamp 
0x4ce7c944

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

The problem seems to be caused by the following file: raspppoe.sys

MEMORY_MANAGEMENT

If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears 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 such 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 Options, and then
select Safe Mode.

Technical Information:

*** STOP: 0x0000001a (0x0000000000041790, 0xfffffa80019a9340, 0x000000000000ffff, 
0x0000000000000000)

*** raspppoe.sys - Address 0xfffffa80019a9340 base at 0xfffff88003f6d000 DateStamp 
0x4a5bcce9

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

The problem seems to be caused by the following file: atikmdag.sys

IRQL_NOT_LESS_OR_EQUAL

If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears 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 such 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 Options, and then
select Safe Mode.

Technical Information:

*** STOP: 0x0000000a (0x000016a001239d48, 0x0000000000000002, 0x0000000000000000, 
0xfffff80003501115)

*** atikmdag.sys - Address 0xfffff88004afb4fc base at 0xfffff88004a16000 DateStamp 
0x4f7e4b69

[Eress]

Ti conviene testarli singolarmente, scollegando tutti gli altri e provando il pc.
Comunque ci sono molti errori, mi pare strano che siano iniziati tutti insieme con l'upgrade ram

[Blue_screen_of_death]

Originariamente inviato da Eress

Ti conviene testarli singolarmente, scollegando tutti gli altri e provando il pc.
Comunque ci sono molti errori, mi pare strano che siano iniziati tutti insieme con l'upgrade ram

Assicurati che i moduli di ram sono compatibili con la tua scheda madre...

E controlla se sono presenti nella qvl della tua mobo

[homeruccio91]

Originariamente inviato da Eress

Ti conviene testarli singolarmente, scollegando tutti gli altri e provando il pc.
Comunque ci sono molti errori, mi pare strano che siano iniziati tutti insieme con l'upgrade ram

Ciao, i banchi li ho testati sia singolarmente, sia in coppia. singolarmente per 10h, e in coppia per 6-7h.
guardando i dump, dall'upgrade ram gli errori sono stati in sequenza:


SYSTEM_THREAD_EXCEPTION_NOT_HANDLED xNtKrnl.exe
IRQL_NOT_LESS_OR_EQUAL intelppm.sys
UNEXPECTED_KERNEL_MODE_TRAP ntoskrnl.exe
IRQL_NOT_LESS_OR_EQUAL ntoskrnl.exe
IRQL_NOT_LESS_OR_EQUAL ntoskrnl.exe
MEMORY_MANAGEMENT raspppoe.sys
IRQL_NOT_LESS_OR_EQUAL fdc.sys
IRQL_NOT_LESS_OR_EQUAL ntoskrnl.exe
IRQL_NOT_LESS_OR_EQUAL atikmdag.sys
SYSTEM_SERVICE_EXCEPTION CI.dll
IRQL_NOT_LESS_OR_EQUAL intelppm.sys
IRQL_NOT_LESS_OR_EQUAL ntoskrnl.exe
IRQL_NOT_LESS_OR_EQUAL ntoskrnl.exe
IRQL_NOT_LESS_OR_EQUAL ntoskrnl.exe
PAGE_FAULT_IN_NONPAGED_AREA ntoskrnl.exe
IRQL_NOT_LESS_OR_EQUAL ntoskrnl.exe
IRQL_NOT_LESS_OR_EQUAL ntoskrnl.exe
IRQL_NOT_LESS_OR_EQUAL ntoskrnl.exe

Tutti dal 17/07 al 23/07
Mi sono ricordato che da windows,ho disabilitato il file di paging, pensando il problema potesse essere l'hard disk. ma le scheramte blu sono continuate.
Non so che fare..

[homeruccio91]

Originariamente inviato da Blue_screen_of_death

Assicurati che i moduli di ram sono compatibili con la tua scheda madre...

E controlla se sono presenti nella qvl della tua mobo

Ciao, i moduli sono compatilbili con la scheda madre ma non sono nella qvl.

Aggiungo specifiche di sistema
Processore intel core duo E8500
Scheda madre ASUS P5QL-PRO
Scheda video ATI RADEON HD4870 1GB
Ram 2*2GB Kingston KVR800D2N6/2G

[Blue_screen_of_death]

credo sia un problema di settaggio della ram nel bios.

Controlla innanzitutto se nel bios a ram riconosciuta correttamente.. E se vengo riconosciuti tutti i moduli

Le frequenze sono impostate in automatico??

[homeruccio91]

Originariamente inviato da Blue_screen_of_death

credo sia un problema di settaggio della ram nel bios.

Controlla innanzitutto se nel bios a ram riconosciuta correttamente.. E se vengo riconosciuti tutti i moduli

Le frequenze sono impostate in automatico??

Nel bios sembra tutto ok, le RAM vengo no viste come DDR2 800 quindi tutto ok, le frequenze sono impostate su automatico. Forse cambiando la velocità si può risolvere qualcosa?

[Blue_screen_of_death]

si... prova a impostarle manualmente...

[homeruccio91]

Originariamente inviato da Blue_screen_of_death

si... prova a impostarle manualmente...

Ok ora provo e posto l'esito dei test.