On Wed 8/7/2013 10:34:50 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080713-25599-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x1A (0x411, 0xFFFFF6FC50073B08, 0x8570000011DF6882, 0xFFFFF6FC50073B01)
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 8/7/2013 10:34:50 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x1B88E)
Bugcheck code: 0x1A (0x411, 0xFFFFF6FC50073B08, 0x8570000011DF6882, 0xFFFFF6FC50073B01)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
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 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 Wed 8/7/2013 2:58:37 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080713-7410-02.dmp
This was probably caused by the following module: unknown_module_00000000`00000002.sys (Unloaded_Unknown_Module_00000000`00000002+0x17)
Bugcheck code: 0x19 (0x20, 0xFFFFF8A00928D7E0, 0xFFFFF8A00928D868, 0x5080304)
Error: BAD_POOL_HEADER
Bug check description: This indicates that a pool header is corrupt.
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: unknown_module_00000000`00000002.sys .
Google query: unknown_module_00000000`00000002.sys BAD_POOL_HEADER
On Wed 8/7/2013 2:48:25 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080713-7410-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x4E (0x99, 0x1296EA, 0x2, 0x12A7B5)
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 8/6/2013 9:46:50 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080613-11154-01.dmp
This was probably caused by the following module: asacpi.sys (ASACPI+0x19A0)
Bugcheck code: 0xC9 (0x22F, 0xFFFFF88003FDF9A0, 0xFFFFF980176FECF0, 0x0)
Error: DRIVER_VERIFIER_IOMANAGER_VIOLATION
Bug check description: This is the bug check code for all Driver Verifier
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: asacpi.sys .
Google query: asacpi.sys DRIVER_VERIFIER_IOMANAGER_VIOLATION