KERNEL_DATA_INPAGE_ERROR BSOD 0x0007A randomly occuring while browsing

Recently whenever I keep my browser open for a while - the whole screen freezes for 3 seconds and I BSOD with the message "KERNEL_DATA_INPAGE_ERROR" and with the error code 0x000007A.
It started a couple of weeks ago and I've been trying to fix it since. I did some digging and found out the problem was with the file "ntoskrnl.exe". Does anybody have any idea what to do now to fix it? Thank you in advance.

Hi Krabkebab,

Welcome to the 7forums.

Please read BSOD Posting Instructions & How to upload files

Please visit Windows Update and install every update available, it may take a couple of times to get them all.

Code:

Hotfix(s):                 N/A

If you are using a program like Ccleaner please stop using it while troubleshooting.
This because programs like Ccleaner remove dump files that are needed to troubleshoot.
Or configure Ccleaner to not remove dump files:


Is the SCSI Pass Through Direct driver installed with Daemon tools?

Please move some files from the F partition to increase the free space to at least 10-15%.
Every partition needs at least 10-15% free space so Windows can do its thing in the background.

   Warning

Less free space could cause BSOD's

All the crashes appear to be caused by a windows driver, this usually means a 3rd party driver is actually causing it as windows drivers are a lot false blamed.
But, to rule out windows files, please check the system files.
To find the driver(s) giving the trouble, please run driver verifier.

Please try following:

• Open an admin command prompt
• Copy/paste "sfc/scannow" (without quotes) and press enter
• When it finished reboot your system
• Open again an admin command prompt
• Enter sfc/scannow again

If sfc/scannow does NOT say "Windows Resource Protection did not find any integrity violation", please upload the cbs.log file located at {windows partition}\Windows\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.

Diagnostic Test

 DRIVER VERIFIER

   Warning

Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.

Please follow this tutorial to run driver verifier.

Some windows drivers are blamed in a few crashes, but that usually means that a 3rd party driver is actually the cause.
Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

   Note

Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.