Windows 10: BSOD's Solved

  1.    21 Nov 2015 #1


    Hi all,

    Recently, my Windows 10 installation started to give me BSOD's. Never after a fresh boot, but always (some time) after the PC has been in sleep mode.

    Please see the attached files.

    Thanks for your help,
    Kind regards,
      My ComputerSystem Spec

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

    Hi Bas71,

    Welcome to the 10forums.

    ESET and a driver with the description 'SATALink driver accelerator' have been flagged.
    However, these are from a 0x3B and 0xD1. The other 2 are 0xA caused by memory corruption.
    I suggest to first test your memory before doing anything with drivers.
    *** WARNING: Unable to verify timestamp for em008_64.dat
    *** ERROR: Module load completed but symbols could not be loaded for em008_64.dat
    *** WARNING: Unable to verify timestamp for SiWinAcc.sys
    *** ERROR: Module load completed but symbols could not be loaded for SiWinAcc.sys
    Probably caused by : memory_corruption
    MODULE_NAME: hardware
    IMAGE_NAME:  hardware

    BSOD's Diagnostic Test BSOD's

    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

  3.    22 Nov 2015 #3

    Hi axe0,

    First of all, thank you for checking my log files and for helping me.

    Indeed, I recently increased my memory from 3x2GB to 6x2GB. I have two different brands and types: Crucial 1600Mhz (slots 1,3,5) and Hyundai 1333Mhz (slots 2,4,6). All of them are running on 1333Mhz. BIOS takes the SPD settings from the Crucial modules (probably from slot 1). At 1333Mhz, the Crucial SPD timings are slower (more conservative) than the Hyuandai modules.

    If I swap the modules (changing their slotnumbers) the PC will not boot, not even post. There are just beeps indicating a memory error.

    I created a bootable Memtest86 flashdrive and let the test pass two times. There were no errors found. This seems to be consistent with my findings that a BSOD appears after the PC awakes from sleep mode. Never after a fresh (re)boot. Yet, since Memtest86 requires it's own (fresh) boot, how can I test the memory after sleep mode?

    For now I have increased memory voltage from auto (1,50v) to 1,55v. My hypotheses: after sleep mode, perhaps the system sometimes has insufficient power for 6 memory modules of two kinds, resulting in data corruption. It may take up to two weeks (the maximum time between BSOD's) to see if this helps anything.

    What do you suggest for me to do or test next?

      My ComputerSystem Spec

  4. axe0's Avatar
    Posts : 13,707
    Windows 10 Pro
       23 Nov 2015 #4

    I suspect the problem is the different branch and type of memory, you need both the same for proper working memory.
      My ComputersSystem Spec

  5.    23 Nov 2015 #5

    That would make sense: the RAM is OK, but two different brands of modules may sometimes result in system instability. I'll see if the slight increase in RAM voltage is enough to get the system stable again. If not, I'll report back here, or (after two weeks without a BSOD) mark this thread as solved.
      My ComputerSystem Spec

  6.    30 Nov 2015 #6

    *Sigh*. Ok, that did not help. Anyone a suggestion how to increase my system's stability (without having to buy new RAM)?
      My ComputerSystem Spec

  7. axe0's Avatar
    Posts : 13,707
    Windows 10 Pro
       30 Nov 2015 #7

    You simply need modules of the same branch.
      My ComputersSystem Spec

  8.    30 Nov 2015 #8

    I dug little more deeply into the RAM issue. The issue turns out to be incompatibility between the Alienware motherboard / BIOS and the new Crucial RAM. The RAM requires a tRFC of 260 DRAM clocks, but the (latest) BIOS won't go further than 150.

    I've increased the QPI voltage, hoping to get things stable again. If that doesn't work, I'll have to change the new RAM again.

    Anyway, concerning the BSODS I can mark this thread as solved. axe0, thank you for your sharp analysis and all your help!
      My ComputerSystem Spec


Related Threads
Hi, i got this computer about 3~ Weeks ago, and have gotten random BSOD's after that. System Information Bellow Intel Core i5-6600K 3.5Ghz @ 3.5 GeForce GTX960 2gb GDDR5, Physx CUDA 1TB Harddisk 7200RPM 8Gb DDR4 2133Mhz Dual Channel, 2x4gb...
BSOD during bootup (black screen 2min -> BSOD) in BSOD Crashes and Debugging
Hello I recently upgraded to Windows 10 from 7. I did choose the non-clean install, and i wish to keep it this way. i do NOT wish to clean install, as id rather just fix the problem. Anyways, my problem is; During the boot process, the pc...
I recently upgraded my htpc from 8.1 pro to Win 10 pro. I have had multiple BSOD since then. 4 were for store exception not handled and the last 2 were for kmode exception not handled mv91xx.sys. Please advise.
Hi, Over the past couple of days I have been having reasonably frequent BSODs. Some have not created a dump file. I cant pinpoint anything in particular but it seems to be pointing to a driver issue but never identifies the driver from what I can...
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 06:53.
Find Us