Metiux1012
Utente Attivo
- Messaggi
- 62
- Reazioni
- 0
- Punteggio
- 36
ecco a voi i report:
Inizialmente pensavo potesse essere dato dall' hd, perchè ho una partizione che non usavo quasi mai e se non erro un annetto fa avevo avuto qualche schermata blu quando iniziai a utilizzarla.
Non ricordo come le feci sparire, questi sono i report risalenti al 2012:
Potrebbe anche essere la ram andata? ho un unico banco da 4gb
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Fri 28/06/2013 23:31:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062913-21278-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800037C9147, 0xFFFFF8800A5A39C0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 28/06/2013 23:31:38 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800037C9147, 0xFFFFF8800A5A39C0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 28/06/2013 14:50:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062813-20857-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C10)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 kernel-mode program 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.
On Fri 28/06/2013 12:32:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062813-19796-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003707FDA, 0xFFFFF8800B785FF0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 28/06/2013 10:38:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062813-20810-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C10)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 kernel-mode program 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.
On Fri 28/06/2013 08:34:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062813-20638-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C10)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 kernel-mode program 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.
On Thu 27/06/2013 23:45:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062813-35786-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0x18 (0x0, 0xFFFFFA8003C9B060, 0x2, 0xF6BFC40D8E1CA381)
Error: REFERENCE_BY_POINTER
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 the reference count of an object is illegal for the current state of the object.
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.
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Fri 28/06/2013 23:31:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062913-21278-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800037C9147, 0xFFFFF8800A5A39C0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 28/06/2013 23:31:38 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800037C9147, 0xFFFFF8800A5A39C0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 28/06/2013 14:50:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062813-20857-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C10)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 kernel-mode program 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.
On Fri 28/06/2013 12:32:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062813-19796-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003707FDA, 0xFFFFF8800B785FF0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 28/06/2013 10:38:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062813-20810-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C10)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 kernel-mode program 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.
On Fri 28/06/2013 08:34:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062813-20638-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C10)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 kernel-mode program 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.
On Thu 27/06/2013 23:45:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062813-35786-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0x18 (0x0, 0xFFFFFA8003C9B060, 0x2, 0xF6BFC40D8E1CA381)
Error: REFERENCE_BY_POINTER
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 the reference count of an object is illegal for the current state of the object.
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.
Inizialmente pensavo potesse essere dato dall' hd, perchè ho una partizione che non usavo quasi mai e se non erro un annetto fa avevo avuto qualche schermata blu quando iniziai a utilizzarla.
Non ricordo come le feci sparire, questi sono i report risalenti al 2012:
[FONT=Segoe UI, Arial]On Wed 20/06/2012 16:35:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062012-22152-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]dxgmms1.sys[/FONT] (dxgmms1+0x811B)
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF880071BB11B)
Error: [FONT=Segoe UI, Arial]UNEXPECTED_KERNEL_MODE_TRAP[/FONT]
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: DirectX Graphics MMS
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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 that cannot be identified at this time.
[/FONT]
[FONT=Segoe UI, Arial]On Sun 29/04/2012 17:25:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\043012-18376-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7CC80)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8006875060, 0xFFFFF80000B9C518, 0xFFFFFA8004293260)
Error: [FONT=Segoe UI, Arial]DRIVER_POWER_STATE_FAILURE[/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 bug check indicates that the driver is in an inconsistent or invalid power state.
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 Sun 22/04/2012 22:02:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042312-20326-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7CC80)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8006A30060, 0xFFFFF80000B9C518, 0xFFFFFA8008ED0320)
Error: [FONT=Segoe UI, Arial]DRIVER_POWER_STATE_FAILURE[/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 bug check indicates that the driver is in an inconsistent or invalid power state.
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 19/04/2012 23:50:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042012-34491-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7CC80)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8006923060, 0xFFFFF80000B9C518, 0xFFFFFA8009463CA0)
Error: [FONT=Segoe UI, Arial]DRIVER_POWER_STATE_FAILURE[/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 bug check indicates that the driver is in an inconsistent or invalid power state.
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 Mon 05/03/2012 13:57:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030512-27128-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7CC40)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF8000308CC02)
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 13/01/2012 21:25:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011312-17721-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7CC40)
Bugcheck code: 0x9F (0x3, 0xFFFFFA800671B060, 0xFFFFF80004517518, 0xFFFFFA8005B55760)
Error: [FONT=Segoe UI, Arial]DRIVER_POWER_STATE_FAILURE[/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 bug check indicates that the driver is in an inconsistent or invalid power state.
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 Wed 11/01/2012 13:41:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011112-18610-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7CC40)
Bugcheck code: 0x9F (0x3, 0xFFFFFA80068EC060, 0xFFFFF800045BD518, 0xFFFFFA80078C9010)
Error: [FONT=Segoe UI, Arial]DRIVER_POWER_STATE_FAILURE[/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 bug check indicates that the driver is in an inconsistent or invalid power state.
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]
crash dump file: C:\Windows\Minidump\062012-22152-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]dxgmms1.sys[/FONT] (dxgmms1+0x811B)
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF880071BB11B)
Error: [FONT=Segoe UI, Arial]UNEXPECTED_KERNEL_MODE_TRAP[/FONT]
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: DirectX Graphics MMS
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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 that cannot be identified at this time.
[/FONT]
[FONT=Segoe UI, Arial]On Sun 29/04/2012 17:25:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\043012-18376-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7CC80)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8006875060, 0xFFFFF80000B9C518, 0xFFFFFA8004293260)
Error: [FONT=Segoe UI, Arial]DRIVER_POWER_STATE_FAILURE[/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 bug check indicates that the driver is in an inconsistent or invalid power state.
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 Sun 22/04/2012 22:02:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042312-20326-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7CC80)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8006A30060, 0xFFFFF80000B9C518, 0xFFFFFA8008ED0320)
Error: [FONT=Segoe UI, Arial]DRIVER_POWER_STATE_FAILURE[/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 bug check indicates that the driver is in an inconsistent or invalid power state.
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 19/04/2012 23:50:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042012-34491-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7CC80)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8006923060, 0xFFFFF80000B9C518, 0xFFFFFA8009463CA0)
Error: [FONT=Segoe UI, Arial]DRIVER_POWER_STATE_FAILURE[/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 bug check indicates that the driver is in an inconsistent or invalid power state.
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 Mon 05/03/2012 13:57:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030512-27128-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7CC40)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF8000308CC02)
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 13/01/2012 21:25:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011312-17721-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7CC40)
Bugcheck code: 0x9F (0x3, 0xFFFFFA800671B060, 0xFFFFF80004517518, 0xFFFFFA8005B55760)
Error: [FONT=Segoe UI, Arial]DRIVER_POWER_STATE_FAILURE[/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 bug check indicates that the driver is in an inconsistent or invalid power state.
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 Wed 11/01/2012 13:41:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011112-18610-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7CC40)
Bugcheck code: 0x9F (0x3, 0xFFFFFA80068EC060, 0xFFFFF800045BD518, 0xFFFFFA80078C9010)
Error: [FONT=Segoe UI, Arial]DRIVER_POWER_STATE_FAILURE[/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 bug check indicates that the driver is in an inconsistent or invalid power state.
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]
Potrebbe anche essere la ram andata? ho un unico banco da 4gb
