Random BSODs every day, different error codes

jtljtl

New member
Local time
3:19 PM
Messages
2
Hi all,

Every day I get around 1-5 BSODs, sometimes while playing games, sometimes it'll be straight after windows has started up and I am struggling to figure out why.

I've run chkdsk and memtest86 multiple times with no errors. I've also tried uninstalling old drivers and deleting infcache.

Also - nothing is being overclocked.

Any suggestions?

Thanks!
 
Last edited:

My Computer

Computer type
PC/Desktop
OS
Windows 7 Home Premium 64bit
WhoCrashed report:

On Fri 9/1/2015 1:30:31 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
uptime: 00:00:28
This was probably caused by the following module: ci.dll (CI+0x577D8)
Bugcheck code: 0x50 (0xFFFFF8A1039C3134, 0x1, 0xFFFFF8000459C550, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ci.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Code Integrity Module
Bug check description: This indicates that invalid system memory has been referenced.
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 Fri 9/1/2015 11:18:35 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\010915-46593-01.dmp
uptime: 00:10:16
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x4E (0x99, 0x27F24, 0x0, 0x27F64)
Error: PFN_LIST_CORRUPT
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
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 Thu 8/1/2015 11:15:50 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\010815-50156-01.dmp
uptime: 00:11:10
This was probably caused by the following module: ntfs.sys (Ntfs!NtfsCommonCleanup+0x369A)
Bugcheck code: 0x24 (0x70F95, 0x0, 0x0, 0x0)
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 Tue 6/1/2015 5:17:40 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\010615-48015-01.dmp
uptime: 03:18:38
This was probably caused by the following module: ntfs.sys (Ntfs!NtfsCommonCleanup+0x369A)
Bugcheck code: 0x24 (0x70F95, 0x0, 0x0, 0x0)
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 Tue 6/1/2015 1:58:40 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\010615-50437-01.dmp
uptime: 02:39:12
This was probably caused by the following module: ntfs.sys (Ntfs! ?? ::FNODOBFM::`string'+0x2899)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800ADD77F8, 0xFFFFF8800ADD7050, 0xFFFFF8000458E5DE)
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/1/2015 8:20:46 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\010515-48328-01.dmp
uptime: 07:10:29
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0xF, 0x2, 0x1, 0xFFFFF8000427DDD0)
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.
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 5/1/2015 11:41:53 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\010515-47984-01.dmp
uptime: 00:40:31
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF800042A8055, 0x2, 0xFFFFFA800427B800)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 Mon 5/1/2015 11:00:35 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\010515-51640-01.dmp
uptime: 00:05:16
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800042B3855, 0xFFFFF880079C5AE0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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.
 

My Computer

Computer type
PC/Desktop
OS
Windows 7 Home Premium 64bit
Back
Top