Multiple BSODs even after fresh re-installation.

I've had this problem since the last month or so. It started with just one or two BSODs randomly occurring until it got to the point where every session with my laptop results in a BSOD or two. Even now, I'm scared it'll boot me out and show a random BSOD error.

I thought it was because of a ton of programs and games I had in my laptop before the re-installation but it persists even after that. The different types of errors i get are:

KERNEL_SECURITY_CHECK_FAILURE
BAD_POOL_HEADER
IRQL_NOT_LESS_OR_EQUAL
NTFS_FILE_SYSTEM
SYSTEM_SERVICE_EXCEPTION
ATTEMPTED_WRITE_TO_READONLY_MEMORY

I've attempted to read the files using "WhoCrashed" but it doesn't really make sense to me.

My Specs:
Operating System: Windows 8.1 64-bit (6.3, Build 9600) (9600.winblue_r8.150127-1500)
System Manufacturer: LENOVO
System Model: 20216
BIOS: 74CN47WW(V3.08)
Processor: Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz (8 CPUs), ~2.4GHz
Memory: 8192MB RAM
Available OS Memory: 8104MB RAM
Page File: 4230MB used, 12066MB available
RAM: 8GB DDR3L Non-ECC ram
Display: Nvidia 750M + Intel 4600 HD
1TB HDD SATA II
24GB M.2 SSD via NGFF 42mm port
Windows 8 + UEFI/Secureboot BIOS
Intel Centrino 2230 Wireless-N
6Cell Lenovo Battery, 48W/h, 62W/h or 72W/h


Dropbox link to the BSODs zip

The WhoCrashed info:

Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Tue 5/26/2015 7:01:19 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\052615-19718-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0)
Bugcheck code: 0x139 (0x3, 0xFFFFD001D9E8D000, 0xFFFFD001D9E8CF58, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
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 5/26/2015 7:01:19 PM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x139 (0x3, 0xFFFFD001D9E8D000, 0xFFFFD001D9E8CF58, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
Bug check description: The kernel has detected the corruption of a critical data structure.
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 5/26/2015 1:54:43 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\052515-22031-01.dmp
This was probably caused by the following module: ci.dll (CI+0x2D8AF)
Bugcheck code: 0x19 (0x3, 0xFFFFC00080DD3290, 0xFFFFC00080DD3210, 0xFFFFC00080DD3290)
Error: BAD_POOL_HEADER
file path: C:\WINDOWS\system32\ci.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Code Integrity Module (Test)
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 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 5/20/2015 9:34:06 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\052015-22156-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0)
Bugcheck code: 0x139 (0x3, 0xFFFFD00023BEC130, 0xFFFFD00023BEC088, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
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 5/17/2015 2:23:30 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\051615-23093-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xFD0E1)
Bugcheck code: 0xA (0x40, 0x2, 0x1, 0xFFFFF801BA528002)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 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 5/17/2015 2:18:20 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\051615-20812-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x31EEC)
Bugcheck code: 0x24 (0xB500190645, 0xFFFFD000236B5C98, 0xFFFFD000236B54A0, 0xFFFFF8010D13BF5F)
Error: NTFS_FILE_SYSTEM
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 a problem occurred in the NTFS file system.
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 Mon 5/11/2015 11:32:55 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\051115-26609-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0)
Bugcheck code: 0x19 (0xD, 0xFFFFC001B36221B0, 0x64C2233E6C4DAB70, 0x64C2233E6C4DABF0)
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 Sun 5/3/2015 7:49:16 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\050315-18000-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0)
Bugcheck code: 0x139 (0x3, 0xFFFFD0002219D410, 0xFFFFD0002219D368, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
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 5/3/2015 2:12:56 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\050215-14750-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x128669)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000167669, 0xFFFFD00022BF3CA0, 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 Sun 5/3/2015 1:46:23 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\050215-15171-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x1392D4)
Bugcheck code: 0xBE (0xFFFFF960001AB2D4, 0x1F000012378B021, 0xFFFFD000253B2910, 0xB)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\WINDOWS\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
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.
1 answer Last reply
More about multiple bsods fresh installation
  1. The KERNEL_SECURITY_CHECK_FAILURE is an bug check indicates that the kernel has detected the corruption of a critical data structure.Here's more info: https://msdn.microsoft.com/en-us/library/windows/hardware/jj569891(v=vs.85).aspx

    The BAD_POOL_HEADER is caused by a corrupted memory pool.The memory pool is paged and non paged files in the memory, there's no real fix this.Here's more info: https://msdn.microsoft.com/en-us/library/windows/hardware/ff557389(v=vs.85).aspx

    The IRQL_NOT_LESS_OR_EQUAL error indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.Here's more info: https://msdn.microsoft.com/en-us/library/windows/hardware/ff560129(v=vs.85).aspx

    The NTFS_FILE_SYSTEM error indicates a problem occurred in ntfs.sys, the driver file that allows the system to read and write to NTFS drives.Here's more info: https://msdn.microsoft.com/en-us/library/windows/hardware/ff557433(v=vs.85).aspx

    The ATTEMPTED_WRITE_TO_READONLY_MEMORY error is issued if a driver attempts to write to a read-only memory segment.Here's more info: https://msdn.microsoft.com/en-us/library/windows/hardware/ff560161(v=vs.85).aspx

    The SYSTEM_SERVICE_EXCEPTION error indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.Here's more info: https://msdn.microsoft.com/en-us/library/windows/hardware/ff558949(v=vs.85).aspx

    Windows site says to follow this guide for adressing these errors:
    http://windows.microsoft.com/en-us/windows-8/resolve-windows-blue-screen-errors
Ask a new question

Read More

Laptops Blue Screen Multiple BSOD Driver Failure