Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.

Windows 7: BSOD on initial startup every day.

22 Apr 2014   #1

Windows Proffessional X64
BSOD on initial startup every day.


I built a new computer in December. Ever since then my computer will Blue screen at a random time after starting for the first time each day. Once it has rebooted from the BSOD it will run fine. I suspect a driver or file is bad as I also have a hard time with some windows updates. With this after doing many searches on here I have tested the memory. It is giving me weird results. The windows memory diagnostics says the memory is good. I have run MEMtest86 with these results:

Two sticks 2 errors
stick 1 slot 1 no errors
stick 1 slot 2 no errors
stick 2 slot 1 no errors
stick 2 slot 2 no errors.

Running driver verifier it instantly BSOD on boot up with both one stick installed and two sticks installed. Any help you can provide will be greatly appreciated.

My System SpecsSystem Spec
23 Apr 2014   #2

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit

Hi TheBarts.

First of all, free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.
  1. Click on the Start button
  2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
  3. Select the “Startup” tab.
  4. Deselect all items other than the antivirus.
  5. Apply > OK
  6. Accept then restart.
Now if you want to use Driver Verifier, it will work.

Then .... are the memory modules are from different brand?
[Physical Memory Array (Type 16) - Length 15 - Handle 002ch]
  Maximum Capacity              8388608KB
  Number of Memory Devices      2
[Memory Array Mapped Address (Type 19) - Length 15 - Handle 002dh]
  Starting Address              00000000h
  Ending Address                008bbfffh
  Memory Array Handle           002ch
  Partition Width               01
[Memory Device (Type 17) - Length 27 - Handle 002eh]
  Physical Memory Array Handle  002ch
  Memory Error Info Handle      [Not Provided]
  Size                          4096MB
  Form Factor                   09h - DIMM
  Device Locator                DIMM0
  Bank Locator                  BANK0
  Memory Type                   01h - Other
  Type Detail                   0080h - Synchronous
  Speed                         667MHz
  Manufacturer                  Manufacturer0
[Memory Device (Type 17) - Length 27 - Handle 0030h]
  Physical Memory Array Handle  002ch
  Memory Error Info Handle      [Not Provided]
  Size                          4096MB
  Form Factor                   09h - DIMM
  Device Locator                DIMM1
  Bank Locator                  BANK1
  Memory Type                   01h - Other
  Type Detail                   0080h - Synchronous
  Speed                         667MHz
  Manufacturer                  Manufacturer1
If those are from different manufacturers, it may cause some sort of mismatch there. Use either one module as a test.

Also increasing the RAM voltages is a way to deal with cold boot BSODs. If you are aware of the process, try it. Otherwise better you keep away from that operation.

And, you did memtest86+ a long, as it seems. How many passes you ran it every times? It needs to run memtest86+ for at least 8 consecutive passes to arrive at the decision that RAM is not failing.

Now, my final suggestion to you will be .... if it does th same cold boot BSOD with only memory module applied, better you get a new RAM kit.
BugCheck 1A, {61940, 23c10000, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+1fe92 )

Followup: MachineOwner
BugCheck 4E, {99, 14a313, 2, 14c875}

*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

Followup: MachineOwner
BugCheck 1A, {41790, fffffa8005b54bf0, ffff, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35084 )

Followup: MachineOwner
My System SpecsSystem Spec

 BSOD on initial startup every day.

Thread Tools

Similar help and support threads
Thread Forum
Flicker on win7 initial startup screen
My first build has been problematic to say the least. (at least) one of my two Corsair CMV4GX3M2A1333C9 2GB memory sticks seems faulty as whenever it is in (in any slot - by itself or with the other 2GB stick) it is bsod'ing just after the login screen comes up. Only on cold boot though, when...
BSOD Help and Support
BSOD on startup after initial 228 windows update
Hey guys, I just received my new gaming pc from a local electronics store. It was going really well and I was happy with it until I did the initial windows update. Aso of now every time my computer tries to configure the updates after installing them it crash and show the error code 0x0000124. I...
BSOD Help and Support
Windows balks on initial desktop startup
Recently I just started getting back into GTA IV. I installed the game on my mechanical drive and it was humming along. This is all assuming that I can actually get the game running. Sometimes it hangs up on the copyright verification. I think the disc is on its last leg aswell... So I installed...
General Discussion
BSOD upon initial startup, memory corruption
Hello, I just made a new computer last week and I have been getting BSODs when I first start up my computer. After the BSOD, the computer restarts and acts as normal. I believe it may have to do with me having my window files on an SSD while my users files on an HDD. I did this separation...
BSOD Help and Support
Windows 7 Startup Error Failure To Initial Environment (MFC)
When I start Windows 7 about 30 seconds after the login, I see an error message popping up that says: "Failed to initial environment". In the task bar I see the an icon that writes MFC, which is the program that gives the error message. I looked in my task manager under processes if I see MFC, but...
General Discussion

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 05:22.
Twitter Facebook Google+