Windows 10: BSOD's

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,
Bas

:)

 

BSOD Loop on boot

Hello,

Earlier today my computer crashed into a BSOD and ever since then it is stuck on a BSOD loop when trying to boot into windows.

Things I have tried so far:

-Booting from a USB Windows (Loads the windows logo then BSOD)

-Letting it do automatic repair (BSOD)

-Letting it do disk check (BSOD)

-Running it with different RAM sticks (BSOD)

-Running it without the 1060 (BSOD)

-Clearing BIOS settings (BSOD)

I am at a loss. Any help appreciated.

System

-Intel i5 6600k

-Nvidia 1060

-16gb ram

-gigabyte z170x

 

Can't install KB3081455

I got so tired of these KB errors and Blue Screen of Death (BSOD) errors I did a clean install of Windows 10. Originally it was an update from 7 to 10. This didn't fix the problems. I got this yesterday:

• 
  IRQL_NOT_LESS_OR_EQUAL BSOD error
  
• 
  PAGE_FAULT_IN_NONPAGED_AREA
  BSOD error
  
• 
  MEMORY_MANAGEMENT BSOD error
  
• 
  BAD_POOL_HEADER BSOD error
  
• 
  2 unable to read memory warnings
  

 

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.
Code: *** 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[/quote]




Diagnostic Test

RAM TEST


Run MemTest86+ - Test RAM - Windows 10 Forums



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.

 

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?

Thanks,
Bas

 

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

 

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.

 

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

 

You simply need modules of the same branch.

 

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!