I have been having alot of blue screens lately when either gaming or doing absolutely nothing.I have done a whoscrashed analysis and this is what i have come up with.
Any help would be great.
computer name: DESASTER
windows version: Windows 8.1 , 6.2, build: 9200
windows dir: C:\Windows
Hardware: ASUSTeK Computer INC., M4A78-E
CPU: AuthenticAMD AMD Phenom(tm) 9950 Quad-Core Processor AMD586, level: 16
4 logical processors, active mask: 15
RAM: 4294103040 total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Wed 11/03/2015 6:18:03 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\031115-19000-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF8020E4BC8E3, 0xFFFFF8020E777A00, 0xFFFFF8020E720F80)
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 Wed 11/03/2015 6:18:03 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: afd.sys (afd+0x4EBA0)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF8020E4BC8E3, 0xFFFFF8020E777A00, 0xFFFFF8020E720F80)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\afd.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Ancillary Function Driver for WinSock
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 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 Sun 8/03/2015 4:03:08 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030815-16046-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF802DC83FDB7, 0x0, 0xFF)
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 Wed 4/03/2015 9:13:42 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030415-18375-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4350B4)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8005D4B40B4, 0xFFFFD000832FC988, 0xFFFFD000832FC190)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 system thread 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 Sat 28/02/2015 2:43:16 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\022815-16781-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x40FA)
Bugcheck code: 0xFC (0xFFFFD000B7C40180, 0x80000000005B0963, 0xFFFFD000B7C698D0, 0x2)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that an attempt was made to execute non-executable memory.
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. There is a possibility this problem was caused by a virus or other malware.
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 27/02/2015 5:30:05 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\022715-21375-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0)
Bugcheck code: 0x1A (0x41287, 0x1EDF68, 0x0, 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.
Any help would be great.
computer name: DESASTER
windows version: Windows 8.1 , 6.2, build: 9200
windows dir: C:\Windows
Hardware: ASUSTeK Computer INC., M4A78-E
CPU: AuthenticAMD AMD Phenom(tm) 9950 Quad-Core Processor AMD586, level: 16
4 logical processors, active mask: 15
RAM: 4294103040 total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Wed 11/03/2015 6:18:03 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\031115-19000-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF8020E4BC8E3, 0xFFFFF8020E777A00, 0xFFFFF8020E720F80)
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 Wed 11/03/2015 6:18:03 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: afd.sys (afd+0x4EBA0)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF8020E4BC8E3, 0xFFFFF8020E777A00, 0xFFFFF8020E720F80)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\afd.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Ancillary Function Driver for WinSock
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 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 Sun 8/03/2015 4:03:08 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030815-16046-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF802DC83FDB7, 0x0, 0xFF)
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 Wed 4/03/2015 9:13:42 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030415-18375-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4350B4)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8005D4B40B4, 0xFFFFD000832FC988, 0xFFFFD000832FC190)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 system thread 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 Sat 28/02/2015 2:43:16 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\022815-16781-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x40FA)
Bugcheck code: 0xFC (0xFFFFD000B7C40180, 0x80000000005B0963, 0xFFFFD000B7C698D0, 0x2)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that an attempt was made to execute non-executable memory.
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. There is a possibility this problem was caused by a virus or other malware.
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 27/02/2015 5:30:05 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\022715-21375-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0)
Bugcheck code: 0x1A (0x41287, 0x1EDF68, 0x0, 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.
Facebook
Twitter
Instagram