Windows 10: BSOD on most "cold" boots (or first boot after several hours)
BSOD on most "cold" boots (or first boot after several hours)
Here a summary of my problem... I used to run Windows 7 64-bit and decided it was time to upgrade in August 2015. I bought an SSD and an extra 8GB stick of identical RAM at the same time, and then proceeded to do a full clean (from scratch) install of Windows 10 Home 64-bit.
Everything was actually going fine until a few weeks later, on the 6th of September 2015. That was the date of my first "cold" boot BSOD. I had always been running a 4.7GHz overclock (for flight simulation) so I started by disabling that, just in case, but it didn't fix it... Anyway, I basically get a BSOD on most "cold" boots, but if I let it restart, or just restart myself when the BSOD appears, I'm fine. I have never ever gotten a BSOD while using the PC, only on boots. So it isn't actually a major major problem, but I hate knowing that "something is wrong" with my machine.
As you'll see in the zip file, almost all the BSOD's point to ntoskrnl+142760. Only recently I started getting BSOD's pointing to ntoskrnl+142770. They are mostly MEMORY_MANAGEMENT.
I recently started going crazy and decided I really wanted to fix it. Here's all I remember I did. Maybe your suggestions will remind me of something I have already tried:
-Disabled all overclocks;
-Reset BIOS completely;
-Tried booting with startup items disabled;
-Tried booting with nothing USB plugged in;
-Ran Memtest86 on both sticks of RAM, individually and together, and never got any errors, after 8+passes each time;
-Tried adding a bit of voltage to the 1.5v RAM in BIOS because it was only getting 1.45v at some point... didn't change anything so I reverted back to default;
-Tried uninstalling software that was installed on or near the 6th of September, where it all started;
None of this worked. Here's the interesting part: I gave "Driver Verifier" a spin, using your guide, and it found that my driver used for connecting my DS4 (PS4 controller) to my PC was causing a BSOD instantly at boot. I uninstalled it, then ran verifier again, and all was good. I still get the BSODs... I decided to run verifier again but this time follow another guide, that stated to check almost all the options. Now I noticed that every single driver is getting blamed on boot, so maybe I'm not supposed to run it with all the options ticked after all.
Anyway, all the online guides for my BSOD state I should use Memtest, or run Verifier. I have done both and I have completely baffled. The computer ran fine with Windows 7, and also ran fine for about one month with Windows 10.
PS: I am aware that my sound card driver is outdated, but I have no choice to use it. It was blamed once by verifier, as was every other driver on my machine, when I used the incorrect settings. I tried to uninstall the M-Audio driver and I still got the BSODs, and in any case, I don't know why the PC would have run fine with the M-Audio driver for a month before I started getting the daily BSOD.
Thank you very much for your time!!
There is a (beta) bios F19E with support secure boot option.
In windows10 as far as i know secure boot option is enabled by default.
This could explain your cold boot problems.
Oh, I am running the latest stable BIOS (F18), so I'll try your idea, thanks. Do you think I should go for the latest beta BIOS (F20e) or just the F19e version as this is the one the specifies it fixes secure boot?
I'll laugh if the solution to the problem is this simple. I hope so! Let you know tonight.
Before the BIOS update I did last night, I used "msinfo32" to check the secure boot status, and it said "Unsupported". Now, it says "Off."
I still got the BSOD on this cold boot though, a MEMORY_MANAGEMENT (ntoskrnl.exe+142770). Quick research online using my crash parameters...
||The page table and PFNs are out of sync . This is probably a hardware error, especially if parameters 3 & 4 differ by only a single bit.
I already checked my RAM, already did multiple "SFC /scannow" and already ran chkdsk. Could this have something to do with, I don't know, the paging file?
As you said your Audiodriver is outdated MAudioDelta Thu Jan 26 03:32:22 2012
And L1C63x64 Tue Jul 16 08:56:31 2013 is outdated
Driver Description: Qualcomm Atheros AR8151 PCI-E Gigabit Ethernet Controller (NDIS 6.30)Driver Update Site: Official site: https://www.qualcomm.com/contact (scroll down for product support)
Unofficial site: http://www.atheros.cz
According to your manual they advice with 2 memory modules to use Channel B bank 1 and Channel A bank 2.
extra 8GB stick of identical RAM at the same time
Check if your memory is placed in the right sockets see your manual(check the rev. number of your mobo) see here http://ca.gigabyte.com/support-downl...w=Z77X-UD3H&ck=
Also did the Bios set the right settings for the modules automaticaly, else set it manually.
Thanks for your reply,
I have the latest available driver for the M-Audio and for the Qualcomm adapter, from the website you linked. The latest for Qualcomm is for Windows 8 64-bit, and the latest for M-Audio is for Windows 7. I have not tried removing the Qualcomm driver completely, but I did try removing the M-Audio driver and still got the BSOD. Besides, if it was that, what am I supposed to do? Use the PC with no sound and no internet?
Yes, I did install the RAM in the 2 recommended slots on the motherboard. I also tried the 2 others, just in case, but no difference. All the BIOS settings were selected automatically.
Are the modules running with these specification
- 1600MHz with headroom to allow overclocking
- 10-10-10-27 latency
It sounds like one of your RAM stick is bad. RAM is also sensitive with temperature in your PC. A while back, I happened to help somebody in this forum with the exact symptom. Everything was running fine after a couple of boot when the RAM got warmed up, passed 6~8 times with memory diag and we later found out by unplug the power supply, left it sit for couple of hours then re-run the memory diagnostic and that's when he got all kind of errors.
Since you OC'ed, try to give the RAM a little bit more juice by increasing the RAM voltage to see if it works.
I am not at home for the next 12hours but I am 99% those are the exact specs. I have tried with both ''XMP Profile'' on and off, it made no difference. I will check later tonight.
Thanks for the idea, it's possible. I haven't OCed the RAM though... and my CPU OC has been disabled for weeks, for testing. I can however try to add a bit of voltage, how much more is appropriate? 1.6V maybe?
Here's the thread that I mentioned above:
Solved Brand new build - different BSODS from a cold boot - Windows 10 Forums
You can increase the voltage around 1.63V ~ 1.65V
Hi, guys I got a problem with constantly repeating BSOD mostly because these two reasons in topic. I have checked online and did everything for preventing this from happening.
And it doesnt worked :/
The other things I have done are checking...
BSOD happens only when the computer cold boots from a prolonged inactive state. If the PC is off for several hours and is turned on it occurs. Computer typically blue screens, sometimes it freezes at the bios splash screen where they Windows 10...
I have been having the strangest behavior from my EVGA SR-2 dual Xeon system for the past week or so. The only new software that has been added is the beta nVidia driver 358.59. Now, I could just uninstall it and revert back to the WHQL driver...
I am trying to upgrade through that icon on the toolbar. I don't really understand much else. The first time I clicked on Continue (I am guessing that was the download) it took over 8 hours to finish during which time I got the "Working on it..."...
I recently upgraded to Windows 10. Yesterday I experienced a red boot screen after restoring to a windwos restore point installing a new GeForce driver, that is probably related to this issue. That only happened once. I reinstalled my GPU drivers...