BSOD caused by ntoskrnl.exe (nt+0x14E240) IRQL_NOT_LESS_OR_EQUAL

axe0 said:

Please only post the file when sfc finds corrupted files.

Attachment 36752 this is the result. should i reinstall windows 10 and do it again?

axe0 said:

If you mean with a reinstall a clean install, yes.

After you've installed windows 10

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 run driver verifier.

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.

When you get a bluescreen while driver verifier is enabled, please use the tool, upload the zip file and reset driver verifier.

I already did a test with driver verifier on Windows 10. It kept giving bsod.

axe0 said:

Indeed you have, but I would need you to do it again.
The last dump files are blaming the memory, but since the RAM is fine I'm pretty sure it is a driver causing it.

Also please scan your system with your antivirus and Malwarebytes.

I have scanned the system with Malwarebytes. Nothing to be found. I'll upload the files you need. Thank you!

axe0 said:

Speaking of memory, the hard drivers are also memory, non-volatile memory meaning they keep the data when the power is gone.
Please perform a HDD test.
I'm not suspecting them, but it would be good to rule them out.

THREE

 HDD TEST

Run SeaTools to check the integrity of your HDD. http://www.sevenforums.com/tutorials...s-how-use.html

   Note

Do not run SeaTools on an SSD as the results will be invalid.

Run chkdsk http://www.sevenforums.com/tutorials...isk-check.html

I did the Seatools test from windows and all passed. Also the chkdsk passed. I'm currently installing windows 10 again

axe0 said:

OK, if you get a bluescreen, please use the tool again.

I'm pretty sure there is a driver causing trouble in windows 10, but not in windows 7.

I started the tool in windows 10 and also selected kernel and all drivers. I'm curently waiting for a bluescreen.