1.    17 Dec 2015 #1


    I was getting a random reboot about once every 36 hours, this is the 1st time I got a BSOD before rebooting

    All I was doing when the BSOD hit was listening to music using Spotify

    I've replaced the power supply and reinstalled windows. I also ran Memtest86+ no issues reported

    Attachment 53992
      My ComputerSystem Spec

  2. axe0's Avatar
    Posts : 13,707
    Windows 10 Pro
       17 Dec 2015 #2

    Daemon tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known cause for BSOD's.
    Please remove Daemon Tools and run the SPTD pass through remover.

    1. Uninstall Daemon Tools
    2. Download the SPTD standalone installer and follow these steps:
      • Double click the executable to open it
      • Click on the button shown below

    If the button is grayed out, like in the image, there is no more SPTD installation on your system, and you can close the window

    Please uninstall Gigabyte software, some are known for causing bluescreens.

    Please update VMware, it has some old drivers.

    How many passes were completed with MemTest86+?

    Please fill in your system specs
    Please follow this tutorial and download the tool. The tool will give you detailed information about your system specs, please fill in your system specs more completely including PSU, cooling system and other used stuff. PSU, cooling system and other used stuff are NOT shown in the tool.
    How to fill in your system specs:

      My ComputersSystem Spec

  3.    03 Jan 2016 #3

    Still having random reboots

    daemon tools is uninstalled
    gigabyte stuff is uninstalled
    vmware is uninstalled

    I don't remember how many passes i completed with MemTest86+ but I ran the test for 18 hours

    Attachment 56922
      My ComputerSystem Spec

  4. axe0's Avatar
    Posts : 13,707
    Windows 10 Pro
       04 Jan 2016 #4

    18h doesn't say much
    Please run it again for 8 complete passes


    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.    04 Jan 2016 #5

    I believe 18 hours gets you past 8 passes even your quote says let it run overnight, but I'm running it again now (1st pass took 41 minutes). I'm sure it is not the memory, one of the 1st things I did was pull memory from a machine that had been up for 60 days and it that memory in the troubled system. It rebooted in less than 24 hours with the "new" memory
      My ComputerSystem Spec

  6. axe0's Avatar
    Posts : 13,707
    Windows 10 Pro
       04 Jan 2016 #6

    Sometimes you need to run it a lot more hours to reach 8 passes, why is unclear however.

    Usually it takes about 10 hours hence the part 'let it run overnight', but there are exceptions.
      My ComputersSystem Spec

  7.   My ComputerSystem Spec

  8. axe0's Avatar
    Posts : 13,707
    Windows 10 Pro
       05 Jan 2016 #8

    What are the 3.3v, 5v and 12v values in the BIOS?
      My ComputersSystem Spec

  9.    08 Jan 2016 #9

    3.3v = 3.324v

    5v = 5.130v

    12v = 12.168v
      My ComputerSystem Spec

  10. axe0's Avatar
    Posts : 13,707
    Windows 10 Pro
       08 Jan 2016 #10


    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 to 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.
      My ComputersSystem Spec


Related Threads
Solved Critical_structure_corruption bsod in BSOD Crashes and Debugging
I have this configuration: MB:Asus M2n-e CPU: Amd 9650 2.3ghz no overclock Ram: corsair 4gb 1066 (working 800mhz) HDD: WD velociraptor 250gb 10000rpm (win 10 64 bit) + 1tb caviar black + 1tb caviar black sata II psu: 650W high power sirtec...
ntkrnlmp.exe bsod windows 10 in BSOD Crashes and Debugging
Hi! I've been getting BSOD for quite som time. i tried to analyse with WhoCrashed, and the message says that it was caused by ntkrnlmp.exe. I dont really know how to fix this problem, so i was hoping annyone could give me a hand. The BSOD...
Hello everyone, I keep on getting bsod's due to ntkrnlmp.exe in Windows 10 Pro 64 bit. This is the analysis carried out by WhoCrashed. Crash dump directory: C:\WINDOWS\Minidump Crash dumps are enabled on your computer. On Wed...
BSOD - ntkrnlmp.exe in BSOD Crashes and Debugging
Experiencing what appears to be random BSOD events. This has been going on for some time now. I've recently switched from Windows 7 to 10, but the problem followed. Bug check points to ntkrnlmp.exe. An internet search has left...
I was browsing Internet and suddenly computer stopped with this BSOD. I have freshly installed Windows 10 Pro. All the drivers are up to date. Last night i tested my rams with Memtest 86 without any errors. I...
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:06.
Find Us