BSOD issues

N7 Serenity

Honorable
Mar 10, 2013
3
0
10,510
My PC crashes constantly, it's quite random. Browsing Chrome, playing ArmA III yesterday, watching a movie, etc. I'll post the WhoCrashed info, but everyone says its a driver that cannot be identified. Any ideas? I've ran MemTest for 11 passes, perfectly fine.








On Sun 3/10/2013 9:32:43 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\031013-6193-01.dmp
This was probably caused by the following module: storport.sys (storport+0x26B5)
Bugcheck code: 0x50 (0xFFFFBA8007B469F8, 0x1, 0xFFFFF801A5F78407, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\WINDOWS\system32\drivers\storport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Storage Port Driver
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 Sun 3/10/2013 7:13:32 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\031013-5460-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x56ADF)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88005ABFADF, 0xFFFFF8800AB2E8B0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
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 Thu 3/7/2013 7:23:25 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\030713-5522-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF8800155C83B)
Bugcheck code: 0x50 (0xFFFFB8A000A12050, 0x0, 0xFFFFF8800155C83B, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 Wed 3/6/2013 9:53:01 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\030613-7644-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7A040)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF801ECA8AD10, 0xFFFFF8800C290D50, 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 Wed 3/6/2013 4:07:08 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\030513-5600-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x4E815)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88005943815, 0xFFFFF8800D5BCF30, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
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 3/3/2013 7:45:08 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\030313-6973-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x40CF8)
Bugcheck code: 0x24 (0xB50019060B, 0xFFFFF8800E901648, 0xFFFFF8800E900E80, 0xFFFFF8800169AD50)
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 Fri 3/1/2013 3:44:52 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\030113-5865-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7A040)
Bugcheck code: 0x139 (0x3, 0xFFFFF8800D93E030, 0xFFFFF8800D93DF88, 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 Thu 2/28/2013 8:56:12 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\022813-6006-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7A040)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800E8C88D10, 0xFFFFF88007B8A100, 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 Wed 2/27/2013 8:00:32 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\022713-7144-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x40CF8)
Bugcheck code: 0x24 (0xB50019060B, 0xFFFFF8800BB22518, 0xFFFFF8800BB21D50, 0xFFFFF8026F073FF7)
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 Fri 2/22/2013 5:24:32 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\022213-5647-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7A040)
Bugcheck code: 0x1A (0x5003, 0xFFFFF70001080000, 0x9D68, 0x1E3DCDFE09)
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.



On Wed 2/20/2013 1:54:30 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\021913-7566-01.dmp
This was probably caused by the following module: fileinfo.sys (fileinfo+0x9D8C)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8800150BD8C, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\fileinfo.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: FileInfo Filter Driver
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 Mon 2/18/2013 5:19:47 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\021813-5943-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7A040)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF803A6BF3504, 0xFFFFF880015F3BF0, 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 Sun 2/17/2013 7:46:49 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\021713-5397-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7A040)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80154EE9D10, 0xFFFFF8800AE3EF30, 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 Sat 2/16/2013 10:52:15 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\021613-6021-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7A040)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF802F30120DE, 0xFFFFF880071A0E00, 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 Wed 2/13/2013 8:14:50 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\021313-5631-01.dmp
This was probably caused by the following module: fileinfo.sys (fileinfo+0x9D8C)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF88000B64D8C, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\fileinfo.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: FileInfo Filter Driver
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.


 

ThunderPumpkin

Honorable
Feb 27, 2013
5
0
10,510
Have you tried running Ckdsk? That could possible help with the NTFS filesystem issue. If not, try running it and seeing if it stems the tide of BSODS.

To run Chkdsk:
1) Go to My Computer
2) Right-click on your main partition
3) Go to "Properties"
4) Go to the "Tools" tab
5) Click "Check"