New build, random BSODs installing Windows 10
Printed From: ASRock.com
Category: Technical Support
Forum Name: Intel Motherboards
Forum Description: Question about ASRock Intel Motherboards
URL: https://forum.asrock.com/forum_posts.asp?TID=4698
Printed Date: 23 Jul 2025 at 7:04pm
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com
Topic: New build, random BSODs installing Windows 10
Posted By: Cryo
Subject: New build, random BSODs installing Windows 10
Date Posted: 27 Mar 2017 at 5:19am
|
" rel="nofollow - Hello everyone, I'm desperately seeking a solution as I've never run into this before and I'm honestly baffled given I've built many custom machines before, all without issue. As this point, I'm thinking it's an issue with the motherboard. Long story short, new build (some reused components) and I'm experiencing random BSODs during and after Windows 10 installation. Here's a breakdown of the details: [Components Installed] Power Supply: Seasonic X650 (80 Plus Gold) - Used in previous build Motherboard: Asrock Z270 Fatal1ty Gaming K6 (NEW) with latest P1.30 BIOS CPU: I7-6700 (Skylake) (Used and previously working) CPU Cooler: Noctua NH-D15 RAM: 32GB (2 sticks of 16GB) of Corsair Vengeance LPX (2666 MHz), Part: CMK32GX4M2A2666C16 (NEW, tested extensively) Video: Onboard (Have a video card but wanted to wait until after Windows was installed) Boot/install: 250GB Samsung 960 EVO installed into Angelwings PX1 (both NEW) [BIOS - with latest version P1.30] Defaults with the exception of changing CSM to "Enabled" and changing "Launch Storage OpROM Policy" to "UEFI only". *** All components are recognized in the BIOS and all settings are default (no OCing etc) *** [Troubleshooting] > Normal POST with no Dr. Debug codes. > CPU Temp: 22-24C, Motherboard Temp: 30-31C > Reseated the Angelbird card several times. > Placed Angelbird card in 1st and 2nd PCIE slots (X16). > Reinstalled/reseated NVME SSD into Angelbiard card. > Used anternate Angelbird card and Samsung 960 EVO 500GB different NVME drive). > Installed the M.2 directly into the motherboard. > Reset CMOS and then went back in to correct time/date and CSM setting on reboot. > Reseated RAM. > Moved RAM to other slots. > Eliminated 1 stick of RAM, going with 16GB instead of 32GB. (A1 slot) > Replaced CMOS battery with a new one. > Reseated CPU and power cable on motherboard. > Experienced same issues using a standard Intel SSD connected to a SATA port (fully functional on another machine. > Rufus Settings: GPT partition scheme for UEFI; FAT32; 4096 cluster size, Quick format. Have used different Windows 10 ISOs from Pro to Enterprise. I noticed my RAM was defaulted to 2133 while the model indicates it should be running at 2666. I did disable the "MRC Fast Boot" option in the DRAM Configuration. Not sure if that would affect stability.
|
Replies:
Posted By: wardog
Date Posted: 27 Mar 2017 at 10:30am
Push your mem up to its rated 2666 either via XMP Profile(s) or manually and report back please. If you need assistance doing this post back and we'll walk you through it. |
Cryo wrote:Posted By: wardog
Date Posted: 27 Mar 2017 at 10:34am
|
Also, your sticks should be in slots A2 and B2 when doing the above. Reset your BIOS, put mem in A2 and B2, boot into BIOS and follow either steps above. |
Posted By: Cryo
Date Posted: 28 Mar 2017 at 8:22pm
| Thank you both for your quick responses. I moved the modules to slots A2 and B2 as suggested, reset the BIOS to defaults and then went in and set the "DRAM Frequency" to "DDR4-2666 (1:10)". Now, I can't recall the last time I've had to manually set RAM timings but I noticed the "Primary Timing" was set to the following: tCL: 16, tRCDtRP: 18 and tRAS: 35. I did notice those are listed on Coarsair's website ( http://www.corsair.com/en-us/vengeance-lpx-32gb-2x16gb-ddr4-dram-2666mhz-c16-memory-kit-black-cmk32gx4m2a2666c16" rel="nofollow - http://www.corsair.com/en-us/vengeance-lpx-32gb-2x16gb-ddr4-dram-2666mhz-c16-memory-kit-black-cmk32gx4m2a2666c16 ) but as "Tested Latency". I opted to use another flash drive (New USB 3.0 versus old USB 2.0), rebooted, attempted to install Windows 10 and while I did receive a BSOD, it rebooted and finished the install. When I logged into Windows, I noticed the flickering I was experiencing previously was now gone. But shortly thereafter, another random BSOD. I then burned the ISO to a DVD-R and experienced the same issues. I opted to run MemTest86 and that did show the RAM Info as: PC4-21300 DDR4 2667MHz, with no errors experienced through the testing. |
Posted By: parsec
Date Posted: 28 Mar 2017 at 9:28pm
|
The default, non-XMP memory speed for the majority of DDR4 DRAM models is 2133. Frankly, when installing Windows on a new PC for the first time, using the default settings for hardware is the best bet for a safe installation. That removes any variables of an over clock, since given the Intel specs for your i7-6700, 2666 is a memory OC. You said no OC yet, but that is a memory OC over the Intel spec of 2133 max. While 2666 should be possible, the more memory used, the more difficult it is to reach a memory OC. Please double check that your memory is seated in the DIMM slots completely. We've had several threads in the forum about memory problems that were simply caused by the memory not being correctly inserted in the slots. The XMP profiles for DDR4 memory have been problematic since the introduction of the Intel 100 and 200 series chipset boards (like your Fatal1ty Z270 Gaming K6). While Corsair and other memory manufactures claim their XMP profiles work for both Intel X99 and the 100/200 series processor's memory controllers, the processors are from different generations, Haswell and Broadwell for X99, Skylake and Kaby Lake for the others. All memory manufactures don't claim universal cross platform memory compatibility between X99 and the 100/200 series chipset systems. Instead of using the XMP profile, try using the DRAM Tweaker feature in the DRAM Configuration screen. That feature allows you to set the main memory parameters for your memory, without applying all the XMP data. We've had better success using DRAM Tweaker with memory compatibility with users having memory issues, and I've been using it too with no problems. Your Windows installation media seems fine, if Windows 10 boots fine after the installation. I don't see that as your issue at all. Corsair calls "tested latency" as the values they verified will work correctly. I don't understand why you seem to question that. Those timings are typical for DDR4 memory, although you can find DDR4 models with better timings. ------------- http://valid.x86.fr/48rujh" rel="nofollow"> 
|
Posted By: wardog
Date Posted: 28 Mar 2017 at 9:37pm
|
"Tested Latency: 16-18-18-35" is what they run at maybe the "default 2133 JEDEC Timings but certainly their rated 2666. Instead of setting the "DRAM Frequency" , let's try setting them via their XMP Profile. I say "try' as because Corsair doesn't have any Z270 boards from any manufacturer listed in their online Memory Finder I m unable to verify if this kit is Compatible. http://www.corsair.com/en-us/memory-finder" rel="nofollow - http://www.corsair.com/en-us/memory-finder Reset the BIOS, boot into BIOS > then "Save and Exit" and power down, set the boards XMP Switch and reboot, now monitor these glitches you're experiencing. Post back please. Too, I highly suggest you contact Corsiar and 1. inquire just WTH they can't get their Z270 listing incorporated in their online tool as it's MUCH easier on you(and me!) 2. Inquire if this Kit of yours is indeed compatible, or not. |
Posted By: Cryo
Date Posted: 29 Mar 2017 at 9:12pm
|
Great suggestion as far as the default settings are concerned as that makes perfect sense. Thinking maybe the issue had something to do with a CPU issue, i pulled all components including the CPU and inspected everything. No bent pins and no damage found anywhere. I reseated the memory with the motherboard still out and then inspected the seating closely with a flashlight. I also did the same with both the CPU and main power connectors. Everything looked good. As suggested, I've engaged Corsair support as well. Responses have been slow thus far but I have asked them to confirm compatibility and timings for my motherboard. I'll note that the one consistent BSOD I've receiving during the Windows 10 install is "Attempted Execute of Noexecute Memory" which would seem to indicate a possible driver issue based on posts elsewhere on the web. As a result, I went into the BIOS and disabled the onboard audio, NICs, serial port and third party USB 3.1 controller. I'm currently in the midst of attempting to install Windows 10 from a DVD.
|