gabbel

If one Stick is detected, then first try to test it out with Memtest86 (leave it running till one full cycle finished). then replace the RAM Module with the other, if it is detected then do the testing with Memtest86 again. (Burn the ISO with "RUFUS" or a similar tool) If one RAM Module does show up as defective or does not show up at all, then don't throw it away. Many brands offer a "lifetime" warranty, therefore you should be able to get a free replacement (at least if you contact the manufacturer directly). I forgot to consider, that since one module could already have been defective a week ago, maybee when you did that last BIOS update, then that Update could already have gone wrong. Beacause this might in fact be the cause, make sure to check the detected RAM Module for good, then flash the same BIOS Update again, then do the Reset. I still think, that you should do a reset on your BIOS Settings, because sometimes when new BIOS updates provide new functionality, your previous save data does not include or cover all the new settings. I think there might be something wrong because your Moudule should detect in slot A2, therefore take pictures from all your current BIOS settings and then do the reset as I described. The pictures might be nice to have, when you have to enter your settings again. Make sure that you know, what your current storage settings are. If your system is now configurated as "IRS" or "AHCI" then you should set these setting again after the Reset, because otherwise your OS will perhaps be unable to boot. If you are lucky, both modules will detect after you did the reset. but please run first the "Memtest86" or "Memtest86+", both are standalone and available as an ISO CD image. Run Memtest again, when both module are detected to be save that not one of the Registers (for dual Channel Mode) is defective. That should be all. Link to free edition of commercial Memtest86: https://www.memtest86.com/download.htm Link to Open Source Memtest86+: http://www.memtest.org/#downiso

Follow the recommendated settings within the Manual, for a Two RAM Modul Configuration use Slots A2 and B2 If this does not help then go on and read the rest. How new is your BIOS? there have been quiet a lot of updates to fix stability issues... Here you could find your MB Manual: H170_PRO_GAMING BUT BEFORE YOU UPDATE! It's possible that one or both of your RAM modules are broken, or that just your BIOS is "confused" after all the changes. But if you install a BIOS Update with a broken RAM module, you risk to BRICK your Mainboard. Therefore I recommend to follow these steps. 1. Remove the Power cord from the Power Suply. 2. Press the power button a few times (to empty remaining voltage from all caps). 3. Put back one Module to Slot A2 (as recommended within the Manual at chapter: 1.4.2) Optional try here to power on.... if it does not help then restart from "1" and continue. 4. Reset CMOS (There are two Jumpers, be sure to use the right one... ( Within the Manual at 1.6 , 1 Clear RTC RAM !! This will erase your BIOS Settings !!) 5. Connect the Power cord 6. Power On. 7. Use a tool like "Memtest86" to check the RAM (if your system posts). When the Test with Memtest86 passes, then update your BIOS... Follow the recommendated settings within the Manual, for a Two RAM Modul Configuration use Slots A2 and B2

If your using two RAM modules, then please try it again with just one. what kind of Laptop is it? for some there exists key combinations to load BIOS Defaults.

You could try to check with tools like "Wifi Analyzer" if someone else in your neighborhood did setup a WiFi within an overlapping channel. this could effect the speed within your WiFi.

? you could show your dad what an "Ultra-Thin Ethernet Network LAN Cable Flat" looks like and if he agrees and if the router is one room away these are a nice solution, because they could be wired from a window to another and are easy to hide, after all your internet connection would also be more reliable...

Great to read that, have fun with 2TB more... ?

Please try aswell what corrado33 sugested, cause driver related issues could still be an issue otherwise I'm out of ideas. You don't own a NVME drive therefore drivers should not be the main issue. You could still try to reset your BIOS settings but then you need to setup them from scratch...

I'm wrong, even with a 32 bit system you should be able to detect the drive, just you would be unable to boot.

Latest BIOS is: Version 1601 https://www.asus.com/us/Motherboards/ROG-STRIX-Z370-E-GAMING/HelpDesk_BIOS/

When using a Windows, is it a 64 Bit Version (cause of MBR based partition limit and addressing limits)

Is your BIOS the latest?

Just make sure, that you got the new storage in the correct slot to the bottom edge of the Mainboard. The slot close to the CPU does not support "SATA Mode" therefore I think that your storage would never be detected in slot "M.2_2"...

According to the Manual: ROG_STRIX_Z370-E_GAMING You need to place your new M.2 Storage into the lower of both M.2 slots (Labeled: " M.2_1(SOCKET3) ") see "Page 1-19" Then try again to detect your storage. If you already did this, then try force your BIOS to SATA Settings for M.2 see "Page 3-18" M.2_1 Configuration: [SATA mode] and M.2_2 PCIe Bandwidth Configuration: [X4] but if this does not work then try [X2] ?

what kind of system do you own? Did you know that some M.2 slots do not have any SATA wires in place, because then you would be out of luck.... Please tell me what "Model" you got and I will try to find the information if your system does support M.2 storage...

I compared the two CPU's i3-4150 vs i7-4770S And the i3-4150 does not support trusted execution, therefore I will give it another shot and just disable "Trusted Execution" for once on the i7... thank you all for your help so far.

I already tried this, I also tried to disable different "C" power states, I did a full setup with only one core activated and much more, but still no luck.

Thanks for your comment, which is great. I also took a look into the "H81M-Plus" BIOS file and it's got the same CPU microcode Updates like the latest BIOS for the "H81M-A". If anybody got an "H81" with "i7-4770s" it would be very interresting to know if you had issues with Windows 10 updates.

Thanks for your comment, but it does not solve the riddle. It seems that just some chipsets got this issue and that is's linked to "Turbo Boost".

If you own a "Digital Licence" do the following. Search for "CMD" and run it "As an Administrator" Type "SLMGR /ATO" which should run the Licence Management utility with the option to activate your Windows. But I think, that your old licence is no longer valid, cause it was linked to your old Mainboard's S/N. If you got any "Windows 7 Pro/Ultimate" or "Windows 8, 8.1 Pro" licence around, you could still try to activate the new System with these. It should still work and provide you a valid digital licence. With the command from above you could try to force to contact the activation servers. To enter a licence you could also use the CMD and the Licence Management utility: "SLMGR /IPK "YOUR WINDOWS KEY HERE"

I got a strange issue, which I tried to solve for months now and where I got no hope left for a permanent solution. I don't get it, why it's still imposible to do Major Windows 10 Updates without a "freeze", followed by boot looping for serval Haswell or Sandybridge based Systems. Here's what i expirienced with the following combination. A budget PC, OEM by Asus, with a "h81m-a" board and a "i7-4770s" still can't do the update (from Windows 7 or windows 10 first release to April 2018 or second "October" November release), even if the latest official "BIOS" is in place. BIOS manipulations, like a CPU microcode which I applied to the different partitions within the UEFI's (GPT Based) "BIOS" file system (Check "FIT Table" Screenshot) have no effect either. I'm not all alone with this issue (but I don't own a "G3258" CPU). For reference one of many links: Intel forum about H81 and G3258 I suspect that there exists a general problem with all "Intel H81" based systems, but I can't confirm it. But maybe this could be a topic for Linus to investigate. Because so far "team blue" never gave a clear answer to this issue.