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

Page 2 of 2 FirstFirst 12
  1.    20 Jan 2016 #11

    Thanks for this interesting read.
      My ComputerSystem Spec

  2. Posts : 10
    Windows 10 Home 64-bit
    Thread Starter
       21 Jan 2016 #12

    lifetec said: View Post
    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.
      My ComputerSystem Spec

  3. Posts : 10
    Windows 10 Home 64-bit
    Thread Starter
       21 Jan 2016 #13

    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.
      My ComputerSystem Spec

  4. Posts : 10
    Windows 10 Home 64-bit
    Thread Starter
       22 Jan 2016 #14

    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.
      My ComputerSystem Spec

  5. topgundcp's Avatar
    Posts : 2,438
    Ubuntu14.04x64 MintMate17x64 Win10Prox64
       22 Jan 2016 #15

    Things to check:
    1. Make sure that your Windows boot disk (SSD) is connected to the first Sata port and boot priority is set to it instead of USB/DVD or non Windows HD.
    2. What option did you use when running chkdsk ? /r should be used to mark the bad sectors on the HD if any so Windows will avoid using them.
    3. If you have any external USB device connected (except keyboard ans mouse). For testing purpose, disconnect it when booting.
    4. Turn off Anti Virus (Avira) if it is On.
      My ComputerSystem Spec

  6. Posts : 10
    Windows 10 Home 64-bit
    Thread Starter
       24 Jan 2016 #16

    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.
      My ComputerSystem Spec

  7. Posts : 10
    Windows 10 Home 64-bit
    Thread Starter
       20 Feb 2017 #17

    An update without progress...

    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
      My ComputerSystem Spec

Page 2 of 2 FirstFirst 12

Related Threads
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...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 20:50.
Find Us