Browsers constantly crashing, BSODs quite often.

[ConstantCrashes]

So I have a very bizarre problem with my PC which I've had on and off with varying degrees for a few years, but it has gotten a lot worse.
The problem is that all web browsers constantly crash. I practically can not use Google Chrome at all, because I get "Aw Snap" page every time I try to load something. It even happens when I try to go to the settings, extensions menu etc. Sometimes I can get pages to load for a few minutes and then get the message, but most of the time it's instant. Google Chrome also flat out crashes to desktop once in a while.
Firefox also crashes to desktop, although a lot less frequently (by which I mean every 10 minutes or so). Microsoft Edge is the most stable, has only crashed a few times.
I don't have any others problems when I'm in Windows 10, I can run games like Battlefield 3/4 without a problem.

My PC also BSOD's quite often, about once a day with different error messages almost every time.

I have two motherboards at home, with both of which I have the same problems. I'm pretty confident the problem is not with RAM, because I also have two different sets (8gb of G.skill and HyperX) both of which also have the same problem.

Due to changing motherboards recently, I now also have a completely fresh Windows 10, so I don't really have anything installed but Google Chrome and Firefox at the moment and the problems persist.

Only thing I can think of is the PSU. Could it really cause these kinds of crashes?

Specs:
i5 2500k
Asus P8Z77-V PRO / Gigabyte Z77X-D3H
Gigabyte Radeon r9 280x
8GB G.Skill RipjawsX 1600 / 8GB HyperX Fury 1866
SeaSonic M12II PSU
OCZ Vertex 4 SSD for the system

 

[Colif]

1 Use edge to visit web site of which ever of the two motherboards are currently installed and get the most up to date drivers and bios for it. Once done, download Driver Booster and fill in all the gaps - If its Browsers, its probably your lan drivers and can also be chip set drivers

2 Download and run a scan using: http://www.resplendence.com/whocrashed
it will look at error logs and create a summary
Copy/Paste its results here

3 Follow option 1: Configure Dump File Settings in Start-up and Recovery
Then do Have Windows Create a Small Memory Dump (Minidump) on BSOD
from this page: http://www.tenforums.com/tutorials/5560-bsod-minidump-configure-create-windows-10-a.html
This will create a file in a folder called C:/Windows/Minidump
Upload the file to a cloud server and share a link in here

If you do the last two steps we can probably work out the cause.

 

[ConstantCrashes]

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Thu 05.05.2016 12:33:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050516-4296-01.dmp
This was probably caused by the following module: ntfs.sys (NTFS!NtfsFileIsInExpression+0x5A)
Bugcheck code: 0x50 (0xFFFFC0014672A462, 0x0, 0xFFFFF8038ECC29CA, 0x0)
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 Thu 05.05.2016 12:33:01 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (NTFS!NtfsFileIsInExpression+0x5A)
Bugcheck code: 0x50 (0xFFFFC0014672A462, 0x0, 0xFFFFF8038ECC29CA, 0x0)
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 04.05.2016 17:01:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050416-13609-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xEF (0xFFFFE001D08D5840, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
Bug check description: This indicates that a critical system process died.
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 Wed 04.05.2016 17:00:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050416-8750-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl!DxgkReportDevicePoweredOn+0x1B)
Bugcheck code: 0xA0 (0x613, 0xFFFFE000EC098C10, 0x0, 0x1)
Error: INTERNAL_POWER_ERROR
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This bug check indicates that the power policy manager experienced a fatal error.
This problem might be caused by a thermal issue.
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.

Minidumps


These are the crashes I've gotten so far on this Windows, probably more to come today.

I also updated all my drivers as you suggested, but it didn't affect the crashes.

 

[Colif]

Just based on who crashed, do an anti virus scan, one of the errors mentions it could be a virus. Try running malwarebytes as well.

Top error refers to the file system so also could point towards a virus (report for some reason repeats first error)

the last error refers to DX so it may have been caused by the Crimson drivers for your AMD card. What are the temperatures in your pc? have you cleaned the case recently?

I can't read the logs myself but someone else here will look at them and figure out what i missed

 

[ConstantCrashes]

I've actually had this problem for quite a long time, but much less frequently than now. I've probably formatted my SSD and installed new Windows about 5 times during this time, I actually had this same problem with browsers crashing before I had my SSD, on my HDD. I've tried different RAM, GPU, MB, I bought this PSU a bit more than a year ago to see if it fixes it, but no.

At this point I'm pretty sure it's nothing software related, because I think I've tried everything. I'm not sure whether all of the parts that I've tried are somehow broken (PSU?), or it's an issue with my CPU or some kind of shorting in the case? I really have no idea how this can keep happening, neither do I really have any knowledge what could possibly cause this.

Meanwhile I've also gotten these crashes:

On Thu 05.05.2016 13:44:15 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (NTFS!NtfsFileIsInExpression+0x5A)
Bugcheck code: 0x50 (0xFFFFD0002106E7F2, 0x0, 0xFFFFF802A00BC9CA, 0x0)
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 Thu 05.05.2016 13:43:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050516-6453-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1 (0x7FFE755D5794, 0x0, 0x6, 0xFFFFD00022FB4B80)
Error: APC_INDEX_MISMATCH
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.

I ran Malwarebytes, but it found nothing.

 

[Colif]

We shall wait and see what the cause is, you appear to have swapped almost all the hardware so it is hit and miss as to what is problem. Probably still outdated drivers somewhere... did you update bios? No point having up to date drivers if bios isn't playing along with them.

Since one was a DX error, I would try this: http://www.tomshardware.com/faq/id-2767677/clean-graphics-driver-install-windows.html

 

[ConstantCrashes]

I do have the latest BIOS, which I put on over a year ago and it seems it's still the latest version available for the Gigabyte motherboard.

 

[ConstantCrashes]

On Wed 11.05.2016 15:09:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051116-9718-01.dmp
This was probably caused by the following module: ntfs.sys (NTFS!NtfsFileIsInExpression+0x5A)
Bugcheck code: 0xCD (0xFFFFCF80C9691F90, 0x0, 0xFFFFF801ECACE9CA, 0x0)
Error: PAGE_FAULT_BEYOND_END_OF_ALLOCATION
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 the system accessed memory beyond the end of some driver's pool allocation.
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 11.05.2016 15:09:43 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (NTFS!NtfsFileIsInExpression+0x5A)
Bugcheck code: 0xCD (0xFFFFCF80C9691F90, 0x0, 0xFFFFF801ECACE9CA, 0x0)
Error: PAGE_FAULT_BEYOND_END_OF_ALLOCATION
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 the system accessed memory beyond the end of some driver's pool allocation.
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 11.05.2016 13:43:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051116-10796-02.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x3B (0xC0000005, 0x0, 0xFFFFD000208F2B30, 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.



On Wed 11.05.2016 6:51:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051116-10796-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR



On Tue 10.05.2016 18:27:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051016-10953-01.dmp
This was probably caused by the following module: verifierext.sys (VerifierExt!SLIC_StatefulAbort+0x294)
Bugcheck code: 0xC4 (0x91001, 0xFFFFF80129A7C700, 0xFFFFE000CF408DF0, 0xFFFFE000CF408EE8)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\drivers\verifierext.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Driver Verifier Extension
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
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 10.05.2016 16:58:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051016-10515-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR



On Mon 09.05.2016 19:17:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050916-9453-01.dmp
This was probably caused by the following module: ntfs.sys (NTFS!NtfsFileIsInExpression+0x5A)
Bugcheck code: 0xCD (0xFFFFCF8076BD77F2, 0x0, 0xFFFFF801268D29CA, 0x0)
Error: PAGE_FAULT_BEYOND_END_OF_ALLOCATION
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 the system accessed memory beyond the end of some driver's pool allocation.
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 08.05.2016 22:15:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050916-9250-01.dmp
This was probably caused by the following module: verifierext.sys (VerifierExt!SLIC_StatefulAbort+0x294)
Bugcheck code: 0xC4 (0x91001, 0xFFFFF8019D86C700, 0xFFFFE00185DE35B0, 0xFFFFE00185DE36A8)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\drivers\verifierext.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Driver Verifier Extension
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
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 08.05.2016 21:45:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050916-6406-01.dmp
This was probably caused by the following module: ntfs.sys (NTFS!NtfsFileIsInExpression+0x5A)
Bugcheck code: 0x19 (0x20, 0xFFFFE00020617EC0, 0xFFFFE00020617F00, 0x404001A)
Error: BAD_POOL_HEADER
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 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 Sun 08.05.2016 9:04:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050816-18109-01.dmp
This was probably caused by the following module: ntfs.sys (NTFS!NtfsFileIsInExpression+0x5A)
Bugcheck code: 0xCD (0xFFFFCF8189B8B7B2, 0x0, 0xFFFFF8011E8D49CA, 0x0)
Error: PAGE_FAULT_BEYOND_END_OF_ALLOCATION
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 the system accessed memory beyond the end of some driver's pool allocation.
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.


These are the crashes I've gotten past few days.

Minidumps

 

[johnbl]

I would start cmd.exe as an admin then run
fltmc.exe

here is the list of filter drivers my system reports:

C:\WINDOWS\system32>fltmc.exe

Filter Name Num Instances Altitude Frame
------------------------------ ------------- ------------ -----
WdFilter 7 328010 0
storqosflt 0 244000 0
FileCrypt 0 141100 0
luafv 1 135000 0
npsvctrig 1 46000 0
FileInfo 7 45000 0
Wof 6 40700 0

just see if you have some filter driver installed that is mucking up your filesystems

when I looked at your drivers some of the time and date stamps were modified, this can happen when the system had malware or rootkits trying to hide.
(they provide a bogus generic list of drivers)

I would run malwarebytes, then tdsskiller to check for rootkits. http://usa.kaspersky.com/downloads/TDSSKiller

I would also run cmd.exe as an admin then run
dism.exe /online /cleanup-image /restorehealth

also, you have verifier turned on but you need to change the memory dump type to kernel or the debugging info gets stripped out and is not recorded in a minidump. when you set the debugtype to kernel the memory dump will be named memory.dmp and be much larger.

might be a virus hiding in your storage driver
spaceport.sys unavailable (00000000)
the date and time stamp has been removed so it can not be checked with known versions.
this also occurred with some of your other drivers. I would think the dism.exe command would fix this by getting a clean copy from a microsoft update server.