New
#1
BSOD caused by ntoskrnl.exe (nt+0x14E240) IRQL_NOT_LESS_OR_EQUAL
Hi!
I installed Windows 10 multiple times and every time i get this error. Please help me!Attachment 36488
Last edited by hancock08; 08 Sep 2015 at 15:08.
Hi!
I installed Windows 10 multiple times and every time i get this error. Please help me!Attachment 36488
Last edited by hancock08; 08 Sep 2015 at 15:08.
Hi hancock08,
Welcome to the 10forums.
Please upload a new zip file, the dump file may be corrupted.
This is what they all are saying at the start of opening the dumps
Code:Probably caused by : memory_corruption
Run MemTest86+ to analyse your RAM. 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.
Then you might be right and some driver (program) is accessing memory that is not reserved for this driver.
WarningPlease 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.
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.
NoteYour 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.
I did the driver verifier test, as in tutorial, and all of the drivers passed the test. I selected only what was indicated in the tutorial.
No, I ran driver verifier and then after a short time i got a bsod. After restart, i opened again driver verifier and clicked on the last option, the one that show the test results. I did not get any message right after the bsod. After that i stopped the verifier. I might have done something wrong?