BSOD on most "cold" boots (or first boot after several hours)

Here's the thread that I mentioned above:
Solved Brand new build - different BSODS from a cold boot - Windows 10 Forums

Thanks for this interesting read.

lifetec said:

Are the modules running with these specification
Technical Specifications

• 1600MHz with headroom to allow overclocking
• 1.5V
• 10-10-10-27 latency

I can confirm those were the exact specs. I have upped the voltage to 1.6v, as topgundcp has suggested, and I will see if I get a BSOD on my next cold boot. I'll keep you advised.

Okay so I increased my RAM voltage to 1.6V. After a bit of online research, I discovered that you must not have a RAM voltage more than 0.5V higher than the CPU Vtt, which controls the memory anyway. So the CPU Vtt, which was at 1.056V, was raised to 1.1V by me.

This morning, first boot, and no BSOD!!! I will have to wait several days / several cold boots to confirm, because on some occasions, the PC wouldn't BSOD. However, this is quite promising... I'll keep you updated.

Second cold boot with no BSOD. This is starting to look really good. I hope I continue to be BSOD-less.

Has nothing to do with it, but by the way, anyone know why my boot time is sooo variable?


I run Windows 10 off an SSD. This morning, I spent about 3-7 seconds waiting on the "Welcome" loading screen... this evening, I spent 30+ seconds. It's usually 30+ seconds, but why is it sometimes much faster? They are both cold boots as far as I can tell.

Hi,
I got another BSOD on a cold boot this morning, it was a different one this time though, maybe I'm getting somwhere.
As to answer the other post, I have currently uninstalled Avira while I debug. Also, I don't recall what parameters I ran chkdsk with, so I'll have to run it again.

Today's BSOD I don't think I've had before, just like usual it was just on login, right after booting; "BAD_POOL_HEADER" FLTMGR.SYS+9882 and NTOSKRNL

BlueScreenViewer Info:
012416-5468-01.dmp 1/24/2016 10:11:05 AM BAD_POOL_HEADER 0x00000019 00000000`00000003 ffffe000`71b874b0 ffffe000`704b2ac8 ffffe000`71b874b0 FLTMGR.SYS FLTMGR.SYS+9882 x64 ntoskrnl.exe+142770 C:\WINDOWS\Minidump\012416-5468-01.dmp 4 15 10586 352,436


According to this page, it says the values of parameter 2,3 and 4 should be the same, but my value #3 is different. Something to do with Pool again. I don't know :/

I won't be able to use the computer for about a week starting from now, but I'll keep you posted if I find anything out.

Hey again!

Just a little update over a year later. Problem is NOT solved. It's been going on since September 2015 haha. However, since it only happens on cold startup (computer has been shut down for at least 5+ hrs), I just use sleep, never use shutdown. Once in a while I shut it down just to see if the problem is still there, and it always is, sadly.

Usually a BAD_POOL_HEADER, or even more commonly, MEMORY_MANAGEMENT or IRQL_NOT_LESS_OR_EQUAL... always always pointing to ntoskrnl.exe

By now I've pretty much accepted it must be due to my motherboard (GA-Z77X-UD3H). The web is filled with posts about how my motherboard isn't very good with Windows 10. I know for a fact I have the latest Ethernet/USB drivers for it, but they aren't even designed for Windows 10. Most likely one of them is causing the issue, but I can't get rid of those drivers, they're needed as far as I know.

I don't really mind the BSODs as it's only on cold startup (I use sleep all the time), but it's sad to know my PC isn't working 100% perfectly, and always a little frustrating to see the blue screen once in a while. I've tested my RAM extensively over the past year and tried other sticks, I'm almost convinced this is a driver/motherboard issue.

Just updating, in case one of you guys has a brilliant flash. Thanks for reading!!



Phil H

PhilH said:

Hey again!

Just a little update over a year later. Problem is NOT solved. It's been going on since September 2015 haha. However, since it only happens on cold startup (computer has been shut down for at least 5+ hrs), I just use sleep, never use shutdown. Once in a while I shut it down just to see if the problem is still there, and it always is, sadly.

Usually a BAD_POOL_HEADER, or even more commonly, MEMORY_MANAGEMENT or IRQL_NOT_LESS_OR_EQUAL... always always pointing to ntoskrnl.exe

By now I've pretty much accepted it must be due to my motherboard (GA-Z77X-UD3H). The web is filled with posts about how my motherboard isn't very good with Windows 10. I know for a fact I have the latest Ethernet/USB drivers for it, but they aren't even designed for Windows 10. Most likely one of them is causing the issue, but I can't get rid of those drivers, they're needed as far as I know.

I don't really mind the BSODs as it's only on cold startup (I use sleep all the time), but it's sad to know my PC isn't working 100% perfectly, and always a little frustrating to see the blue screen once in a while. I've tested my RAM extensively over the past year and tried other sticks, I'm almost convinced this is a driver/motherboard issue.

Just updating, in case one of you guys has a brilliant flash. Thanks for reading!!



Phil H

Phil,

I am on Windows 10 1909 and I am getting the same symptoms as you and have no idea what is going on. I always hope every time an update/upgrade is provided by Microsoft will resolve my issues.. still no luck.

It is only happening after a cold boot either 2 hours later or overnight. All the errors you have specified priors, I almost got all of them. I did all the pagefile checking, chkdsk, memory test.. nothing found.

Have you ever sent anything to Microsoft for review?

Please advise.

NSXT said:

Phil,

I am on Windows 10 1909 and I am getting the same symptoms as you and have no idea what is going on. I always hope every time an update/upgrade is provided by Microsoft will resolve my issues.. still no luck.

It is only happening after a cold boot either 2 hours later or overnight. All the errors you have specified priors, I almost got all of them. I did all the pagefile checking, chkdsk, memory test.. nothing found.

Have you ever sent anything to Microsoft for review?

Please advise.

Hey NSXT,

I haven't posted here in years and was surprised when I received the email notification! Sadly, I never ever found a solution to this. I built a new PC from the ground up in March 2018 so I never experience this issue anymore (new PC doesn't do this), but I occasionally turn on my old PC to check something, and yup, it BSODs on the first boot and then if I restart its fine. I'm sorry but I pretty much gave up, I have no idea what was causing it

I didn't send anything to Microsoft no. It must be either a hardware or driver problem but I really don't know...

Sorry about that,

Phil

@NSXT Please create a new thread and we'll look into your issues separately.