BSOD on initial startup every day.

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?

Code:

[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.
_____________________________________

Code:

BugCheck 1A, {61940, 23c10000, 0, 0}

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

Followup: MachineOwner
---------

Code:

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
---------

Code:

BugCheck 1A, {41790, fffffa8005b54bf0, ffff, 0}

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

Followup: MachineOwner
---------