Page 3 of 5 FirstFirst 12345 LastLast
  1.    10 Sep 2015 #21
    Join Date : Jun 2015
    Posts : 12,668
    Windows 10 Pro

    Please only post the file when sfc finds corrupted files.
      My ComputersSystem Spec
  2.    10 Sep 2015 #22
    Join Date : Sep 2015
    Posts : 21
    windows 10 pro x64
    Thread Starter

    Quote Originally Posted by axe0 View Post
    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?
      My ComputerSystem Spec
  3.    10 Sep 2015 #23
    Join Date : Jun 2015
    Posts : 12,668
    Windows 10 Pro

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

    After you've installed windows 10



    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.

    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.


    When you get a bluescreen while driver verifier is enabled, please use the tool, upload the zip file and reset driver verifier.
      My ComputersSystem Spec
  4.    10 Sep 2015 #24
    Join Date : Sep 2015
    Posts : 21
    windows 10 pro x64
    Thread Starter

    Quote Originally Posted by axe0 View Post
    If you mean with a reinstall a clean install, yes.

    After you've installed windows 10



    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.

    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.


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

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

    Quote Originally Posted by axe0 View Post
    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!
      My ComputerSystem Spec
  7.    10 Sep 2015 #27
    Join Date : Jun 2015
    Posts : 12,668
    Windows 10 Pro

    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.



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

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

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


    Run chkdsk http://www.sevenforums.com/tutorials...isk-check.html
      My ComputersSystem Spec
  8.    10 Sep 2015 #28
    Join Date : Sep 2015
    Posts : 21
    windows 10 pro x64
    Thread Starter

    Quote Originally Posted by axe0 View Post
    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.



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

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

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

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

    Quote Originally Posted by axe0 View Post
    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.
      My ComputerSystem Spec

 
Page 3 of 5 FirstFirst 12345 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 20:54.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums