Hello everyone,
I am not very tech savy, but I decided to build my own gaming PC to save some money and to my luck have been experiencing common BSODs. I had Windows 8.1 installed and after the unfamiliarity and annoyance it caused me, I switched to Windows 7. Both versions of Windows had common BSODs. Using WhoCrashed, ntoskrnl.exe seems to be a common factor in all the crashes. MY computer BSOD at vary random points from doing absolutely nothing to gaming which is what I built the computer for. Below is a list of the crash reports from WhoCrashed.
I would appreciate any help with this situation.
System Information (local)
--------------------------------------------------------------------------------
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: Z87X-UD5H, Gigabyte Technology Co., Ltd., Z87X-UD5H-CF
CPU: GenuineIntel Intel(R) Core(TM) i5-4670K CPU @ 3.40GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 17131462656 total
VM: 2147352576, free: 1930915840
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sat 9/20/2014 8:32:49 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092014-8782-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA800D9A3680, 0xFFFFF800038073D8, 0xFFFFFA800D2E1E10)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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 9/20/2014 6:56:03 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092014-8377-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1 (0x76D1186A, 0x22, 0x0, 0xFFFFF88004FCEB60)
Error: APC_INDEX_MISMATCH
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 there has been a mismatch in the APC state index.
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 9/6/2014 4:31:40 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092014-7113-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x19 (0x3, 0xFFFFF800030099D0, 0xFFFFF800030091D0, 0xFDFFF800030099D0)
Error: BAD_POOL_HEADER
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 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.
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 9/6/2014 3:49:01 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090614-9765-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0x80, 0x2, 0x1, 0xFFFFF80002E88F1F)
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 Tue 9/2/2014 6:46:38 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090614-7566-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CB2A)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002E89B2A, 0xFFFFF880031AF708, 0xFFFFF880031AEF60)
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 Tue 9/2/2014 6:21:52 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090214-8002-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002E918E6, 0xFFFFF88008BF5DD0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 9/2/2014 6:20:03 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090214-6973-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC5E9D)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000185E9D, 0xFFFFF88008727FF0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 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 Tue 9/2/2014 6:09:58 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090214-8143-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xD1 (0xFFFFFC818FDB7C10, 0x2, 0x8, 0xFFFFFC818FDB7C10)
Error: DRIVER_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 a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 Tue 9/2/2014 5:44:37 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090214-7456-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0xFFFFF808030FDC38, 0xC, 0x0, 0xFFFFF80002EE4749)
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 Tue 9/2/2014 5:20:18 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090214-6817-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B90)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
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.
System Information (local)
--------------------------------------------------------------------------------
I am not very tech savy, but I decided to build my own gaming PC to save some money and to my luck have been experiencing common BSODs. I had Windows 8.1 installed and after the unfamiliarity and annoyance it caused me, I switched to Windows 7. Both versions of Windows had common BSODs. Using WhoCrashed, ntoskrnl.exe seems to be a common factor in all the crashes. MY computer BSOD at vary random points from doing absolutely nothing to gaming which is what I built the computer for. Below is a list of the crash reports from WhoCrashed.
I would appreciate any help with this situation.
System Information (local)
--------------------------------------------------------------------------------
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: Z87X-UD5H, Gigabyte Technology Co., Ltd., Z87X-UD5H-CF
CPU: GenuineIntel Intel(R) Core(TM) i5-4670K CPU @ 3.40GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 17131462656 total
VM: 2147352576, free: 1930915840
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sat 9/20/2014 8:32:49 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092014-8782-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA800D9A3680, 0xFFFFF800038073D8, 0xFFFFFA800D2E1E10)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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 9/20/2014 6:56:03 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092014-8377-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1 (0x76D1186A, 0x22, 0x0, 0xFFFFF88004FCEB60)
Error: APC_INDEX_MISMATCH
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 there has been a mismatch in the APC state index.
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 9/6/2014 4:31:40 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092014-7113-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x19 (0x3, 0xFFFFF800030099D0, 0xFFFFF800030091D0, 0xFDFFF800030099D0)
Error: BAD_POOL_HEADER
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 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.
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 9/6/2014 3:49:01 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090614-9765-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0x80, 0x2, 0x1, 0xFFFFF80002E88F1F)
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 Tue 9/2/2014 6:46:38 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090614-7566-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CB2A)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002E89B2A, 0xFFFFF880031AF708, 0xFFFFF880031AEF60)
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 Tue 9/2/2014 6:21:52 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090214-8002-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002E918E6, 0xFFFFF88008BF5DD0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 9/2/2014 6:20:03 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090214-6973-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC5E9D)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000185E9D, 0xFFFFF88008727FF0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 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 Tue 9/2/2014 6:09:58 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090214-8143-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xD1 (0xFFFFFC818FDB7C10, 0x2, 0x8, 0xFFFFFC818FDB7C10)
Error: DRIVER_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 a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 Tue 9/2/2014 5:44:37 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090214-7456-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0xFFFFF808030FDC38, 0xC, 0x0, 0xFFFFF80002EE4749)
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 Tue 9/2/2014 5:20:18 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090214-6817-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B90)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
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.
System Information (local)
--------------------------------------------------------------------------------
My Computer
At a glance
Windows 7 Professional 64-bitIntel(R) Core(TM) i5-4670K CPU @ 3.40GHzNVDIA GeForce GTX 770
- Computer type
- PC/Desktop
- Computer Manufacturer/Model Number
- custom build
- OS
- Windows 7 Professional 64-bit
- CPU
- Intel(R) Core(TM) i5-4670K CPU @ 3.40GHz
- Motherboard
- Z87X-UD5H, Gigabyte Technology Co., Ltd., Z87X-UD5H-CF
- Graphics Card(s)
- NVDIA GeForce GTX 770
