Windows 10: Multiple BSODs caused by ntoskrnl.exe+142760

  1.    23 Mar 2016 #1

    Multiple BSODs caused by ntoskrnl.exe+142760


    This problem has been happening since I built this computer 6 months ago.

    I've tried changing the motherboard, the memory, and the power supply, and have reinstalled windows many times. I suspect I'll have enough parts for a second computer by the time I figure this out. Logs are attached. Thank you!
      My ComputerSystem Spec

  2. Ztruker's Avatar
    Posts : 4,723
    Windows 10 Pro X64 14393.969
       23 Mar 2016 #2

    Are you doing any over clocking? If yes, for the time being set everything back to default.

    I looked at a number of the last dumps (oldest to newest) and these are the identified causes:

    Hardware Memory Error (single bit fail)
    Hardware Memory Error (single bit fail)
    Grim Dawn.exe (Game)
    Grim Dawn.exe (Game)
    Grim Dawn.exe (Game)
    svchost.exe
    MsMpEng.exe (Windows defender)
    MsMpEng.exe (Windows defender)

    Please fill out your System Specs:

    How to fill out System Specs for tenforums.
    See here: System Specs - Fill in at Ten Forums

    All that's left to replace is the hard drive and video card (if not using on-board).
      My ComputersSystem Spec

  3. Ztruker's Avatar
    Posts : 4,723
    Windows 10 Pro X64 14393.969
       23 Mar 2016 #3

    If none of the info I posted is of any help, try running Driver Verifier, see if it shakes out any buggy driver:

    Driver Verifier - Enable and Disable in Windows 10
    Driver Verifier is a diagnostic tool built into Windows 10, it is designed to verify both native Microsoft drivers and third party drivers. Driver Verifier's verification process involves putting heavy stress on drivers with the intention of making bad, outdated, incompatible or misbehaving drivers fail. The required result is a BSOD (Blue Screen of Death) which will generate a crash dump for debugging purposes.
    Machines exposed to Driver Verifier will run very sluggishly due to the stress being applied to the drivers.
    Warning
    It is not advised to run Driver Verifier for more than 48 hours at a time. Disable Driver Verifier after 48 hours or after receiving a BSOD, whichever happens soonest.

    Always create a Restore Point prior to enabling Driver Verifier.
      My ComputersSystem Spec


 

Related Threads
Hello everyone. I have been having some problems with my windows 10. I upgraded from windows 7 about one and a half month ago. I had many problems all around with multiple BSOD per week. I took up the opportunity to format my HDDs and did a...
ntoskrnl.exe causing multiple BSODs a day in BSOD Crashes and Debugging
Hello, I've been having multiple blue screens a day caused by ntoskrnl.exe and have no idea how to fix them. They seem to be happening more frequently when I'm gaming, but I just upgraded from a GTX 650 to a GTX 960 and this hasn't solved...
Solved BSOD caused by ntoskrnl.exe please help in BSOD Crashes and Debugging
Hey all, I've attached 4 minidumps. Can you please help troubleshoot this intermittent BSOD?
BSOD caused by ntoskrnl.exe in BSOD Crashes and Debugging
Hello! I have recurring blue screens on my laptop and can't seem to figure out what's causing them. Sometimes, the computer also freezes completely without any forewarning and the only way to shut it down is to remoce the battery. I should...
BSOD caused by ntoskrnl.exe in BSOD Crashes and Debugging
BSODs have been happening for a while but I'm not really sure what's the actual cause.
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 05:02.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums