Citation :
System Information (local)
--------------------------------------------------------------------------------
computer name: SYSNOT-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: MS-7821, MSI, Z87-G45 GAMING (MS-7821)
CPU: GenuineIntel Intel(R) Core(TM) i5-4670K CPU @ 3.40GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8531226624 total
VM: 2147352576, free: 1871151104
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 10/03/2014 04:42:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031014-14648-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80002C87C3F)
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 Mon 10/03/2014 04:28:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031014-12355-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80002CD9C3F)
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.
|