Windows 10: 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

:)

 

BSOD: IRQL_NOT_LESS_OR_EQUAL, SYSTEM_THREAD_NOT_HANDLED

Greetings,

last week i made some hardware changes to my laptop (lenovo z70-80). I installed a new ssd and upgraded my 4gb RAM to 16 gb RAM . The next day i experienced some BSOD errors (only at a cold startup, after the reboot of the system everything works just fine).
Most commonly the cause of BSOD was SYSTEM_THREAD_NOT_HANDLED and just lately the IRQL_NOT_LESS_OR_EQUAL. I post the info from the last BSOD as got from blue screen viewer :

Bug Check String;

IRQL_NOT_LESS_OR_EQUAL

Bug Check Code: 0x0000000a

Parameter1: 00000000`00060001

Parameter2: 00000000`000000ff

Parameter3: 00000000`00000000

Parameter4: fffff802`8266bf72

Caused by Driver: ntoskrnl.exe

Caused by Address: ntoskrnl.exe+16c580

File Description: NT Kernel & System

thanks in advance.

 

HELP getting BSOD IRQL_NOT_LESS_OR_EQUAL

WhoCrashed.exe Said

On Sat 09/12/15 08:28:56 GMT your computer crashed

crash dump file: C:\WINDOWS\Minidump\091215-19812-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x14E240)

Bugcheck code: 0xA (0x4200000052, 0x2, 0x0, 0xFFFFF8026B8C7B07)

Error: IRQL_NOT_LESS_OR_EQUAL

file path: C:\WINDOWS\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.

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.

 

Hi hancock08,

Welcome to the 10forums.

Please upload a new zip file, the dump file may be corrupted.

 

Done

 

This is what they all are saying at the start of opening the dumps
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.

 

The problem is that with windows 8 or 8.1 or 7 i get no bsod. Only on 10 :|. I don't think that it's related to memory. :|

 

Then you might be right and some driver (program) is accessing memory that is not reserved for this driver.






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.

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.

 

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.

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. QUOTE
Thanks, i will try and tell you the results.

 

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.

 

Did you get a message or something that said that?

 

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?

 

A bluescreen means driver verifier detected a violation.
Please use the tool again and upload the zip file.

You haven't done anything wrong*Wink

 

what zip? the verifier makes a zip, or do i have to use the program i used yesterday to make the zip with dump files?

 

If you cannot find the cause, then please use the tool again and upload the zip file.