PROBLEMA Crash !

[BCrusade]

Dopo i crash e i seguenti errori...
driver_irql_not_less_or_equal
Memory_management
Effettuo un bel giro di MEMTEST che x ben 12 scansioni nn trova nessun tipo di errore...Allora dico bene! Oggi accendo e....SBAM!!

multiple_irp_complete_requests

Mo cos'è questo!!

 

[TheLastSunrise]

Dopo i crash e i seguenti errori...
driver_irql_not_less_or_equal
Memory_management
Effettuo un bel giro di MEMTEST che x ben 12 scansioni nn trova nessun tipo di errore...Allora dico bene! Oggi accendo e....SBAM!!

multiple_irp_complete_requests

Mo cos'è questo!!

Il sistema riesce almeno ad avviarsi in modalità normale o provvisoria per 10 minuti? se si: scarica whocrashed e incolla qui il report della lettura del file di dmp

 

[BCrusade]

Il sistema riesce almeno ad avviarsi in modalità normale o provvisoria per 10 minuti? se si: scarica whocrashed e incolla qui il report della lettura del file di dmp

Si si il computer va alla grande!! solo che mi crasha 2 o 3 volte e poi basta...

 

[TheLastSunrise]

Si si il computer va alla grande!! solo che mi crasha 2 o 3 volte e poi basta...

Ottimo, fai come ti ho detto :asd:

 

[BCrusade]

Ottimo, fai come ti ho detto :asd:

[FONT=Segoe UI, Arial]Crash Dump Analysis

---

[/FONT]
[FONT=Segoe UI, Arial]Crash dump directory: C:\Windows\Minidump[/FONT]

[FONT=Segoe UI, Arial]Crash dumps are enabled on your computer.
[/FONT]
[FONT=Segoe UI, Arial]On Sun 06/10/2013 11:10:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100613-17830-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75B80)
Bugcheck code: 0x44 (0xFFFFFA8006437AD0, 0xEAE, 0x0, 0x0)
Error: [FONT=Segoe UI, Arial]MULTIPLE_IRP_COMPLETE_REQUESTS[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that a driver has tried to requested an IRP be completed that is already complete.
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 that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Fri 04/10/2013 18:32:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100413-17908-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75B80)
Bugcheck code: 0x1A (0x5003, 0xFFFFF70001080000, 0xD3FF, 0xC4600001A709)
Error: [FONT=Segoe UI, Arial]MEMORY_MANAGEMENT[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.


[/FONT]
[FONT=Segoe UI, Arial]On Fri 04/10/2013 18:16:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100413-18002-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75B80)
Bugcheck code: 0xA (0xFFFFFA7FFFFFEC90, 0x2, 0x1, 0xFFFFF80003083A91)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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 that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Fri 04/10/2013 17:56:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100413-28813-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75B80)
Bugcheck code: 0x1A (0x5003, 0xFFFFF70001080000, 0x2067, 0x22A000004009)
Error: [FONT=Segoe UI, Arial]MEMORY_MANAGEMENT[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.


[/FONT]
[FONT=Segoe UI, Arial]On Thu 03/10/2013 15:58:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100313-18564-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75B80)
Bugcheck code: 0xA (0xFFFFFA7FFFFFD370, 0x2, 0x1, 0xFFFFF800030F67FE)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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 that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Thu 03/10/2013 15:44:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100313-26488-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x35BDE8)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8000335BDE8, 0xFFFFF880033A8968, 0xFFFFF880033A81C0)
Error: [FONT=Segoe UI, Arial]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
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 that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]

---

Conclusion

---

[/FONT]
[FONT=Segoe UI, Arial]6 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.


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.

[/FONT]

 

[TheLastSunrise]

Crash Dump Analysis

---

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 06/10/2013 11:10:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100613-17830-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x44 (0xFFFFFA8006437AD0, 0xEAE, 0x0, 0x0)
Error: MULTIPLE_IRP_COMPLETE_REQUESTS
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a driver has tried to requested an IRP be completed that is already complete.
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 that cannot be identified at this time.



On Fri 04/10/2013 18:32:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100413-17908-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x1A (0x5003, 0xFFFFF70001080000, 0xD3FF, 0xC4600001A709)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.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 Fri 04/10/2013 18:16:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100413-18002-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0xA (0xFFFFFA7FFFFFEC90, 0x2, 0x1, 0xFFFFF80003083A91)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.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 that cannot be identified at this time.



On Fri 04/10/2013 17:56:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100413-28813-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x1A (0x5003, 0xFFFFF70001080000, 0x2067, 0x22A000004009)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.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 03/10/2013 15:58:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100313-18564-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0xA (0xFFFFFA7FFFFFD370, 0x2, 0x1, 0xFFFFF800030F67FE)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.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 that cannot be identified at this time.



On Thu 03/10/2013 15:44:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100313-26488-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x35BDE8)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8000335BDE8, 0xFFFFF880033A8968, 0xFFFFF880033A81C0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
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 that cannot be identified at this time.

---

Conclusion

---

6 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.


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.

Ma sei proprio sicuro che la RAM non abbia problemi? a me sembra sia lei a dar problemi...

 

[BCrusade]

Ma sei proprio sicuro che la RAM non abbia problemi? a me sembra sia lei a dar problemi...

Xke MEMTEST nn rileva problemi ?!

- - - Updated - - -

C'è nn lo dico io che nn ho problemi ho usato MEMTEST e nn ne ha rilevati...

 

[TheLastSunrise]

Xke MEMTEST nn rileva problemi ?!

- - - Updated - - -

C'è nn lo dico io che nn ho problemi ho usato MEMTEST e nn ne ha rilevati...

Mi fido :asd:
Comunque il problema è o la RAM (che escludo visto che hai eseguito un memtest senza errori) o un problema driver.. attendi risposte da @Federico83 saprà sicuramente aiutarti

 

[BCrusade]

Mi fido :asd:
Comunque il problema è o la RAM (che escludo visto che hai eseguito un memtest senza errori) o un problema driver.. attendi risposte da @Federico83 saprà sicuramente aiutarti

Adesso sto usando una ram sola x testarla !!! successivamente la cambierò di slot x testare anche quello poi le invertiro...

 

[TheLastSunrise]

Adesso sto usando una ram sola x testarla !!! successivamente la cambierò di slot x testare anche quello poi le invertiro...

Perfetto, prova e fammi sapere

 

[BCrusade]

Perfetto, prova e fammi sapere

Alla fine....la scheda madre ha ceduto e il pc è caput....