I've had my computer for somewhere around 2 years now and I'm getting BSOD's very regularly. I upgraded from windows 7 to windows 10 because I thought it might help my situation but it doesn't seem to have helped.
Since it's a different BSOD almost every time, I don't know what's causing it but I can only assume it is faulty RAM. Could anyone verify this for me?
I ran WhoCrashed and these are the results:
On Sun 1/17/2016 10:54:47 AM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFF80328C49E70)
Bugcheck code: 0x7F (0x8, 0xFFFFF80328C49E70, 0xA824, 0xFFFFF800D4181708)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
A third party driver was identified as the probable root cause of this system error.
Google query: UNEXPECTED_KERNEL_MODE_TRAP
On Tue 1/12/2016 7:05:50 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\011216-8265-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xFC (0xFFFFE001F5258BD0, 0x80000001050009E3, 0xFFFFE001F61B1C80, 0x4)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 1/10/2016 12:38:20 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\011016-9609-01.dmp
This was probably caused by the following module: win32kbase.sys (win32kbase!RGNOBJ::bMerge+0x2B)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF9610C7ABC3B, 0xFFFFD00023962F00, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\win32kbase.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Base Win32k Kernel Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 12/26/2015 12:19:40 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\122615-8500-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x109 (0xA3A01F58B02F77E3, 0xB3B72BDF02B0318C, 0x6, 0x18)
Error: CRITICAL_STRUCTURE_CORRUPTION
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
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 12/22/2015 8:10:40 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\122215-10203-01.dmp
This was probably caused by the following module: Unknown (0xFFFFF801FFF51760)
Bugcheck code: 0xA (0x7FF64CAA5C8C, 0x2, 0x0, 0xFFFFF801FFE4D015)
Error: IRQL_NOT_LESS_OR_EQUAL
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.
A third party driver was identified as the probable root cause of this system
SPECS:
AMD x4 760k @3.8Ghz - CPU
ASRock fm2a75 pro4+ - MOBO
MSI Radeon r7 265 - Graphics card
Crucial Ballistix sport xt 8GB - RAM (1600 MT/s)
Windows 10 64 bit - OS
Since it's a different BSOD almost every time, I don't know what's causing it but I can only assume it is faulty RAM. Could anyone verify this for me?
I ran WhoCrashed and these are the results:
On Sun 1/17/2016 10:54:47 AM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFF80328C49E70)
Bugcheck code: 0x7F (0x8, 0xFFFFF80328C49E70, 0xA824, 0xFFFFF800D4181708)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
A third party driver was identified as the probable root cause of this system error.
Google query: UNEXPECTED_KERNEL_MODE_TRAP
On Tue 1/12/2016 7:05:50 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\011216-8265-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xFC (0xFFFFE001F5258BD0, 0x80000001050009E3, 0xFFFFE001F61B1C80, 0x4)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 1/10/2016 12:38:20 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\011016-9609-01.dmp
This was probably caused by the following module: win32kbase.sys (win32kbase!RGNOBJ::bMerge+0x2B)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF9610C7ABC3B, 0xFFFFD00023962F00, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\win32kbase.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Base Win32k Kernel Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 12/26/2015 12:19:40 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\122615-8500-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x109 (0xA3A01F58B02F77E3, 0xB3B72BDF02B0318C, 0x6, 0x18)
Error: CRITICAL_STRUCTURE_CORRUPTION
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
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 12/22/2015 8:10:40 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\122215-10203-01.dmp
This was probably caused by the following module: Unknown (0xFFFFF801FFF51760)
Bugcheck code: 0xA (0x7FF64CAA5C8C, 0x2, 0x0, 0xFFFFF801FFE4D015)
Error: IRQL_NOT_LESS_OR_EQUAL
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.
A third party driver was identified as the probable root cause of this system
SPECS:
AMD x4 760k @3.8Ghz - CPU
ASRock fm2a75 pro4+ - MOBO
MSI Radeon r7 265 - Graphics card
Crucial Ballistix sport xt 8GB - RAM (1600 MT/s)
Windows 10 64 bit - OS
Facebook
Twitter
Instagram