|
|||||||
|
|
|
 |
|
|
Strumenti |
19-09-2015, 12:42
|
#1 |
|
Junior Member
Iscritto dal: Jul 2011
Messaggi: 10
|
Schermata blu con errore 0x0000001A
Ciao, già in passato mi avete aiutato direttamente o indirettamente.
Stavolta il problema è il seguente: Compare, sempre con più frequenza, la schermata blu con errore 0x0000001A Non so però se dipenda dalla RAM (o dalla scheda video). Credo sia una delle due, dando più peso alla RAM. Ho analizzato i crash con WhoCrashed. Li copio. Se mi deste un parere, potrei capire perché questo problema si sta ripresentando sempre più frequentemente, per adottare una soluzione. Grazie. Crash Dump Analysis -------------------------------------------------------------------------------- Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. On Fri 18/09/2015 16:26:00 GMT your computer crashed crash dump file: C:\Windows\Minidump\091815-7800-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) Bugcheck code: 0x1A (0x41790, 0xFFFFFA8001382520, 0xFFFF, 0x0) 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 Sat 12/09/2015 07:42:54 GMT your computer crashed crash dump file: C:\Windows\Minidump\091215-9141-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) Bugcheck code: 0x1A (0x41790, 0xFFFFFA8001382520, 0xFFFF, 0x0) 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 Wed 02/09/2015 18:56:31 GMT your computer crashed crash dump file: C:\Windows\Minidump\090215-7410-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) Bugcheck code: 0x1A (0x41790, 0xFFFFFA8001382520, 0xFFFF, 0x0) 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 Mon 24/08/2015 23:15:46 GMT your computer crashed crash dump file: C:\Windows\Minidump\082515-11840-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) Bugcheck code: 0x1A (0x41790, 0xFFFFFA8001382520, 0xFFFF, 0x0) 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 Mon 27/07/2015 20:31:35 GMT your computer crashed crash dump file: C:\Windows\Minidump\072715-7581-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) Bugcheck code: 0x4E (0x99, 0x50135, 0x3, 0x1F98B4) Error: PFN_LIST_CORRUPT 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 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. On Tue 20/01/2015 15:46:21 GMT your computer crashed crash dump file: C:\Windows\Minidump\012015-10140-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) Bugcheck code: 0x1A (0x41790, 0xFFFFFA8001382520, 0xFFFF, 0x0) 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 Tue 04/11/2014 10:38:25 GMT your computer crashed crash dump file: C:\Windows\Minidump\110414-10342-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) Bugcheck code: 0x1A (0x41284, 0x1040A001, 0x3AE6, 0xFFFFF70001080000) 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 30/10/2014 00:15:40 GMT your computer crashed crash dump file: C:\Windows\Minidump\103014-8018-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) Bugcheck code: 0xDE (0x2, 0xFFFFF8A00EDADBB8, 0xFFFFF8A00CCD7169, 0x5F5BF8C0) Error: POOL_CORRUPTION_IN_FILE_AREA 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 corrupted pool memory that is used for holding pages destined for disk. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Mon 27/10/2014 12:56:05 GMT your computer crashed crash dump file: C:\Windows\Minidump\102714-127421-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) Bugcheck code: 0x9F (0x4, 0x258, 0xFFFFFA800731A040, 0xFFFFF80000B9C3D0) Error: DRIVER_POWER_STATE_FAILURE file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation 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. On Thu 23/10/2014 09:56:49 GMT your computer crashed crash dump file: C:\Windows\Minidump\102314-8689-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) Bugcheck code: 0x9F (0x4, 0x258, 0xFFFFFA800731A040, 0xFFFFF80000B9C3D0) Error: DRIVER_POWER_STATE_FAILURE file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation 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. On Sat 19/07/2014 20:51:52 GMT your computer crashed crash dump file: C:\Windows\Minidump\071914-7987-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) Bugcheck code: 0x1A (0x403, 0xFFFFF680000DFBB8, 0xF8300000503C982D, 0xFFFFF680000D7AB2) 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. -------------------------------------------------------------------------------- Conclusion -------------------------------------------------------------------------------- 11 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you. 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 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. |
|
|
|
|
| Strumenti | |
|
|
Tutti gli orari sono GMT +1. Ora sono le: 10:04.
