Solved

BSOD probably ntoskrnl.exe [Windows 10 (64 bit)] (Dump file included)

I just got this (not the first time), any idea how to fix it?

Here is the dump file: http://www.mediafire.com/download/j9wn7m78n2bk7b2/061116-31812-01.dmp

Is there any more information needed?

Sorry for my bad English and thanks in advance and have a great day guys! :D
7 answers Last reply Best Answer
More about bsod ntoskrnl exe windows bit dump file included
  1. bugcheck was caused by a single bit memory corruption. most likely a hardware problem.
    you should download and run memtest86 to test your hardware
  2. johnbl said:
    bugcheck was caused by a single bit memory corruption. most likely a hardware problem.
    you should download and run memtest86 to test your hardware


    I'm on 70% pass
    Test #7

    And 0 Errors

    When to stop?
  3. Best answer
    I would let it run over night.
    when it gets to the hammer test it tends to expose single bit corruptions.
    hammer test is test 13
    http://www.memtest86.com/troubleshooting.htm

    BSOdemise said:
    johnbl said:
    bugcheck was caused by a single bit memory corruption. most likely a hardware problem.
    you should download and run memtest86 to test your hardware


    I'm on 70% pass
    Test #7

    And 0 Errors

    When to stop?

  4. johnbl said:
    I would let it run over night.
    when it gets to the hammer test it tends to expose single bit corruptions.
    hammer test is test 13
    http://www.memtest86.com/troubleshooting.htm

    BSOdemise said:
    johnbl said:
    bugcheck was caused by a single bit memory corruption. most likely a hardware problem.
    you should download and run memtest86 to test your hardware


    I'm on 70% pass
    Test #7

    And 0 Errors

    When to stop?





    (I don't know if it got to test 7 but now it is over)
    It went to 100% and then restarted and the computer turned on normally (into windows)
    What now?
  5. try running tests of your hard drive after the updates of the BIOS and motherboard drivers.
    you might also turn off your virtual memory, then turn it back on to (goal is to delete your pagefile.sys and make another one at a different location on your drive)

    if you have a solid state drive, use crystaldiskinfo.exe to read the firmware and error stats, then check for SSD firmware updates.

    ok, I looked at the error again, the error was coming from virtual memory
    so that means data was paged out from memory to your pagefile.sys
    then when it was paged back into memory (ram) one bit was modified.

    I would update your intel management engine driver
    System32\drivers\TeeDriverW8x64.sys Tue Jul 07 10:43:32 2015
    directly from intel: https://downloadcenter.intel.com/
    or your motherboard vendor has a specific driver for this that is newer than what you currently have installed.
    http://www.gigabyte.com/products/product-page.aspx?pid=4150#driver
    (I would pick up all of the custom motherboard drivers)


    I would also pick up the new BIOS version f15 for your mother board because of a fix for SATA
    http://www.gigabyte.com/products/product-page.aspx?pid=4150#bios (be sure to check the motherboard version you have)
    Current bios loaded just said motherbord version x.x (it is not filled out)
    Manufacturer Gigabyte Technology Co., Ltd.
    Product B75M-D3H

    --------------
    I will look at the memory dump again and see if i can find anything that might be suspect.
    how long did the test take? and what was the version? Older versions did not have the hammer test.
  6. I believe it's the newest.
    I'll download again from the site and run it overnight, this night.
    In case there will be an error, will it stop? Because I won't be near the computer to see it?

    Anything suspecting in the dmp?

    I really appreciate your help :)
  7. i updated the previous message.
    BSOdemise said:
    I believe it's the newest.
    I'll download again from the site and run it overnight, this night.
    In case there will be an error, will it stop? Because I won't be near the computer to see it?

    Anything suspecting in the dmp?

    I really appreciate your help :)
Ask a new question

Read More

windows 10 Memory Blue Screen Ntoskrnl.Exe