Page 1 of 5 123 ... LastLast
  1.    07 Sep 2015 #1
    Join Date : Sep 2015
    Posts : 21
    windows 10 pro x64

    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.
      My ComputerSystem Spec
  2.    07 Sep 2015 #2
    Join Date : Jun 2015
    Posts : 12,965
    Windows 10 Pro

    Hi hancock08,

    Welcome to the 10forums.

    Please upload a new zip file, the dump file may be corrupted.
      My ComputersSystem Spec
  3.    07 Sep 2015 #3
    Join Date : Sep 2015
    Posts : 21
    windows 10 pro x64
    Thread Starter

    Quote Originally Posted by axe0 View Post
    Hi hancock08,

    Welcome to the 10forums.

    Please upload a new zip file, the dump file may be corrupted.
    Done
      My ComputerSystem Spec
  4.    07 Sep 2015 #4
    Join Date : Jun 2015
    Posts : 12,965
    Windows 10 Pro

    This is what they all are saying at the start of opening the dumps
    Code:
    Probably caused by : memory_corruption



    BSOD caused by ntoskrnl.exe (nt+0x14E240) IRQL_NOT_LESS_OR_EQUAL Diagnostic Test BSOD caused by ntoskrnl.exe (nt+0x14E240) IRQL_NOT_LESS_OR_EQUAL
     RAM TEST

    Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums

    Note   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.
      My ComputersSystem Spec
  5.    07 Sep 2015 #5
    Join Date : Sep 2015
    Posts : 21
    windows 10 pro x64
    Thread Starter

    Quote Originally Posted by hancock08 View Post
    Done
    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. :|
      My ComputerSystem Spec
  6.    07 Sep 2015 #6
    Join Date : Jun 2015
    Posts : 12,965
    Windows 10 Pro

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




    BSOD caused by ntoskrnl.exe (nt+0x14E240) IRQL_NOT_LESS_OR_EQUAL Diagnostic Test BSOD caused by ntoskrnl.exe (nt+0x14E240) IRQL_NOT_LESS_OR_EQUAL
     DRIVER VERIFIER

    warning   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   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.
      My ComputersSystem Spec
  7.    07 Sep 2015 #7
    Join Date : Sep 2015
    Posts : 21
    windows 10 pro x64
    Thread Starter

    Quote Originally Posted by axe0 View Post
    Then you might be right and some driver (program) is accessing memory that is not reserved for this driver.




    BSOD caused by ntoskrnl.exe (nt+0x14E240) IRQL_NOT_LESS_OR_EQUAL Diagnostic Test BSOD caused by ntoskrnl.exe (nt+0x14E240) IRQL_NOT_LESS_OR_EQUAL
     DRIVER VERIFIER

    warning   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   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.
      My ComputerSystem Spec
  8.    08 Sep 2015 #8
    Join Date : Sep 2015
    Posts : 21
    windows 10 pro x64
    Thread Starter

    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.
      My ComputerSystem Spec
  9.    08 Sep 2015 #9
    Join Date : Jun 2015
    Posts : 12,965
    Windows 10 Pro

    Did you get a message or something that said that?
      My ComputersSystem Spec
  10.    08 Sep 2015 #10
    Join Date : Sep 2015
    Posts : 21
    windows 10 pro x64
    Thread Starter

    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?
      My ComputerSystem Spec

 
Page 1 of 5 123 ... LastLast


Similar Threads
Thread Forum
Solved Having randons BSOD caused by ntoskrnl.exe
THIS THREAD WAS SOLVED BY CHANGING THE MOTHER BOARD. Since I bought my PC, randons BSOD appear (most of them caused by ntoskrnl.exe and some caused by hal.dll) >WHEA_UNCORRECTABLE_ERROR, >KMODE_EXCEPTION_NOT_HANDLED, ...
BSOD Crashes and Debugging
Bsod:- irql_not_less_or_equal
BSOD occurs at shutdown:- IRQL NOT LESS OR EQUAL file path: C:\Windows\system32\drivers\clfs.sys
BSOD Crashes and Debugging
BSOD caused by ntoskrnl.exe
BSODs have been happening for a while but I'm not really sure what's the actual cause.
BSOD Crashes and Debugging
BSOD Caused by "ntoskrnl.exe" (nt+0x150CA0) on Windows 10
I keep having the BSOD on my computer about once a day. I have read other posts and are unable to solve the issue. I initially had the issue on my Windows 8.1 system, I then reinstalled Windows 8.1 and still had the issue. I decided to do a clean...
BSOD Crashes and Debugging
BAD_POOL_HEADER caused by ntoskrnl.exe and tcpip.sys
Hello, I have Windows 10 PRO installed. Other important installed applications are Malwarebytes (Antimalware and Antiexploit), Adguard and utorrent. Last night I have started a big download on utorrent (a 20GB file) and after some minutes I...
BSOD Crashes and Debugging
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 00:41.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums