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

I uploaded another zip file at the begging of the topic

 

Please upload the zip file in the new post and not in the begin post next time.

 

Code: Probably caused by : memory_corruption[/quote]




Diagnostic Test

RAM TEST


Run MemTest86+ - Test RAM - Windows 10 Forums



Note



MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.


Please do the 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 doesn't 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

RAM TEST[/quote]


Run MemTest86+ - Test RAM - Windows 10 Forums



Note



MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.


Please do the 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 doesn't 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. For the moment i've installed windows 7 64bit and i'll run it until bsod, to be sure that ia a windows problem. Meantime i'll take the test and tell you the results. Thanks for helping me!

 

This is the result of memtest86+ Attachment 36727

 

Good, are you doing the system file check?

 

I did the test once, while I was still running windows 10 and it told me that there were some corrupted files and got fixed. I'll run it again and post the file you require.

 

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?

 

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.

 

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.

 

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!

 

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

 

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