hola,
al despertar la ultrabook luego de haber estado hibernando o en suspensión Windows me indica que debio reniciarse por un inconveniente y al ver en mas detalles me dice MEMORY.dmp y a veces otros mensajes. estos errores generan archivos en la carpeta minidump
dejando registros que no entiendo. al leer en los fotos descargue WHOCRASHED para que pudiera informarme que podría estar causando el problema y luego del análisis de estos archivos me indica lo que mas abajo detallo, si alguien podría ayudarme lo agradecería.
gracias!
Crash Dump Analysis
Crash dump directory: C:\windows\Minidump
Crash dumps are enabled on your computer.
On Sat 06/07/2013 06:58:15 a.m. GMT your computer crashed
crash dump file: C:\windows\Minidump\070613-8984-01.dmp
This was probably caused by the following module:
ntfs.sys (0xFFFFF880019D01AB)
Bugcheck code: 0x50 (0xFFFFF8A054DE7038, 0x0, 0xFFFFF880019D01AB, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\windows\system32\drivers\ntfs.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Controlador del sistema de archivos NTFS
Bug check description: This indicates that invalid system memory has been referenced.
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 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.
On Sat 06/07/2013 06:58:15 a.m. GMT your computer crashed
crash dump file: C:\windows\memory.dmp
This was probably caused by the following module:
ntfs.sys (Ntfs+0xED1AB)
Bugcheck code: 0x50 (0xFFFFF8A054DE7038, 0x0, 0xFFFFF880019D01AB, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\windows\system32\drivers\ntfs.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Controlador del sistema de archivos NTFS
Bug check description: This indicates that invalid system memory has been referenced.
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 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.
On Sat 06/07/2013 06:18:59 a.m. GMT your computer crashed
crash dump file: C:\windows\Minidump\070613-7906-01.dmp
This was probably caused by the following module:
ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x139 (0x3, 0xFFFFF88002FEC890, 0xFFFFF88002FEC7E8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
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 06/07/2013 05:20:14 a.m. GMT your computer crashed
crash dump file: C:\windows\Minidump\070613-9140-01.dmp
This was probably caused by the following module:
ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x1A (0x41793, 0xFFFFF680375E46E0, 0xDD, 0xDC)
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 05/07/2013 01:49:48 a.m. GMT your computer crashed
crash dump file: C:\windows\Minidump\070413-10187-01.dmp
This was probably caused by the following module:
fileinfo.sys (0xFFFFF880017B9933)
Bugcheck code: 0x50 (0xFFFFFA80520155E0, 0x0, 0xFFFFF880017B9933, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\windows\system32\drivers\fileinfo.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: FileInfo Filter Driver
Bug check description: This indicates that invalid system memory has been referenced.
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 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.
On Thu 04/07/2013 04:19:13 a.m. GMT your computer crashed
crash dump file: C:\windows\Minidump\070413-7343-01.dmp
This was probably caused by the following module:
ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x50 (0xFFFFFA8048C4FF28, 0x0, 0xFFFFF803750A53DC, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_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 invalid system memory has been referenced.
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 04/07/2013 03:54:52 a.m. GMT your computer crashed
crash dump file: C:\windows\Minidump\070413-6859-01.dmp
This was probably caused by the following module:
ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x1A (0x31, 0xFFFFFA8006B47E60, 0xFFFFF8801A67E000, 0xFFFFF8A009DE4BBE)
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 04/07/2013 03:43:34 a.m. GMT your computer crashed
crash dump file: C:\windows\Minidump\070413-6937-01.dmp
This was probably caused by the following module:
ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x1A (0x41792, 0xFFFFF68000004B88, 0x40000000, 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 Sun 30/06/2013 09:05:21 p.m. GMT your computer crashed
crash dump file: C:\windows\Minidump\063013-29796-01.dmp
This was probably caused by the following module:
ntfs.sys (0xFFFFF88001B60703)
Bugcheck code: 0x50 (0xFFFFF8A05050B990, 0x0, 0xFFFFF88001B60703, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\windows\system32\drivers\ntfs.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Controlador del sistema de archivos NTFS
Bug check description: This indicates that invalid system memory has been referenced.
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 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.
On Fri 21/06/2013 08:18:45 p.m. GMT your computer crashed
crash dump file: C:\windows\Minidump\062113-13437-01.dmp
This was probably caused by the following module:
ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x1A (0x41793, 0xFFFFF680678E4D80, 0x1B1, 0x1B0)
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 21/06/2013 07:50:15 p.m. GMT your computer crashed
crash dump file: C:\windows\Minidump\062113-8734-01.dmp
This was probably caused by the following module:
ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x1A (0x41793, 0xFFFFF680001C1FB0, 0x2, 0x1)
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 12/06/2013 11:43:17 p.m. GMT your computer crashed
crash dump file: C:\windows\Minidump\061213-8984-01.dmp
This was probably caused by the following module:
ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x1A (0x41793, 0xFFFFF6801B56BFE0, 0x1FD, 0x1FC)
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*
12 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.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
