Possibly the memory too low in voltage so yes memory not compatible.
Attachment 70917
Attachment 70918
Intel Coreâ„¢ i7-6700 Processor (8M Cache, up to 4.00 GHz) Specifications
Vengeance® LPX 16GB (2x8GB) DDR4 DRAM 2400MHz C14 Memory Kit - Black (CMK16GX4M2A2400C14)
I had the same problem with Win 7 but never solved it, however when I moved to Win 10, I again had the same problem but managed to solve it by switching off "Fast Startup" which is configured by default in Windows 10.
This apparently is similar to Hibernate and saves a copy of your system settings and Kernal image,
When you start the computer again, Windows does not have to reload the kernel, drivers, and system state individually. Instead, it just refreshes your RAM with the loaded image from the hibernation file and delivers you to the login screen, or in my case Crashes !!!
I guess if you have slow ram (when Cold) this could be causing the problem, coincidentally I always had similar problems with hibernate on Windows 7.
This link expalains Fast Startup in more detail and explains how to disable it.
The Pros and Cons of Windows 10’s “Fast Startup” Mode
Hi Steven, thank you for your reply. I replaced my RAM with different kit (this time I was reading motherboard specification carefully and selected memory from compatibility matrix - HyperX 2133 kit) and it solved my problem. Will try to find someone with different motherboard to test my first kit and find out whether it works fine or not.
Regardign your idea - it looks quite sensible, but unfortunately I'm not qualified specialist in this area, so I can't say anything for sure. But, again, now with 2133 kit everything works perfectly fine.
Fast startup is the opposite of a cold start, meaning it has nothing to do with the issue this thread was started with.
axe0
I beg to differ. Fast Startup under windows 10 is what happens from a cold start (if enabled) in order to speed up boot time. It cured my BSOD from a cold start and therefore seems entirely relevant.
Did you read the attached link ?
No need to read the link, I know how fast startup works and what the pros and cons are because I have troubleshoot fast startup issues in the past.
I think we have a different definition of a cold start if I read you correctly.
My definition of a cold start is a boot process where fast startup is disabled, AFAIK this definition of a cold start is for many others the same. Basically a startup where the kernel and everything needs to be initialized without the use of a pagefile that holds all data.
I think you're being pedantic.
Technically what you say is true but what most people (after trawling through many websites) mean by BSOD after cold start mean that their computer crashes when they switch on first thing in the morning but doeasn't during subsequent re boots, therefore, in this instance my definition is the correct one (although perhaps not technically correct...)
Anyway, i came here in order to help people find a solution, they can try it, if it works great, if not they can revert to fast start in about 2 minutes.
i don't really think that your harangue helps anyone (except maybe your ego) and muddies the waters...
I don't care much about what most mean to say with a cold startup if it isn't it's true nature, because it is the technical part that is important with troubleshooting BSODs.
It is only an explanation.....i don't really think that your harangue helps anyone
if you say so...
Quote