Windows fails to load (BSODs) once a day on first startup attempt

Every morning Windows fails to load on the first start-up attempt of the day. Please note that after I am able to get it to load, I can turn off, turn on, or restart with no issues the rest of the day. It is literally only on the first start-up of each day. As soon as it starts to load windows it will reboot and go straight to windows recovery with an option to load windows normally or check for problems.

• Each time "Start Windows Normally" is selected it will either reboot as soon as windows stats to load, BSOD, or once in a while it will load windows where it will BSOD the second anything is clicked. As soon as it BSOD, the next start-up I can load windows normally and everything will be fine rest of the day.

• If I have it check for a problem it will show it is checking and then ask if I want to restore to an earlier time. As this is a fresh install, I will select "no" and it will begin to attempt a repair. If I let it run the full course it will always return a message stating nothing could be repaired. After which, I can start windows normally with no problems. I have also learned that in the mornings I can choose to repair and immediately restart computer once it begins to check for problems and it will load windows normally.

Other than that there are basically no issues. I can turn off and on rest the day without an issue. There is one other thing, I have noticed if I leave it idle for a very long time (most the day), every now and then I will return and it will be sitting on a BSOD or show a message that it has recovered from a BSOD. If a message shows search for a solution, a solution is never found.

This condition persists every day. Since it began doing this, it has never started properly in the morning and never had an issue after the morning startup.

Couple of quick thoughts:

• When the computer was new it did not do this (it has worked normally in the past).
• Started about 2 weeks after being built
• Following a fresh format of the disk and reinstall of windows the issue does not change
• sfc /scannow has never found an issue.
• memtest86+ has ran all night without finding an issue
• Windows memtester has not found issue
• I have tried starting the computer with most components "unplugged" and the issue persists

Is Windows 7 . . .
- x86 (32-bit) or x64 ? 64bit
- the original installed OS on the system? Is a builder, installed from original Windows 7 disk
- an OEM or full retail version? OEM version installed from disk on built computer
- What is the age of system (hardware)? ~6 weeks
- What is the age of OS installation (have you re-installed the OS?) reinstalled multiple times, last time was 2 days ago and was following full format of entire disk (m4 ssd)


AMD FX(tm)-8120 Eight-Core Processor, 3100 Mhz,Processor(s)
GA-990XA-UD3 Motherboard

Installed Physical Memory (RAM) 8.00 GB
Total Physical Memory 7.98 GB
windows installed on M4-CT128 M4SSD2 Disk


Please find attached reports



Thank you for your help

Both of these were related to pool_corruption. Since memtest has passed I would suspect a driver. To work out which please run driver verifier. My gut feeling is it is your Avast but no definitive info yet.

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Followed your suggestions:

• Created restore point
• Ran verifier per instructions
• Rebooted computer which BSODed immediately upon attempting to load windows
• rebooted and started from last known good configuration
• Windows loaded successfully but noticed that there was no connection to the network and windows could not repair
• Restored from the restore point I created before this process
• Ran jcgriff and Perfmon
• Attached reports to this message

Still the same. Neither DMP appears ot have verifier enabled. Please type verifier /query and let us know the results.

It responds "No drivers are currently verified"

Alkoh said:

It responds "No drivers are currently verified"

Thats what I suspected. Can you upload a snip of this page.

The setting "all drivers" may make the computer a bit slower but will keep an eye on all the drivers.

I have attempted to run verifier in different ways but was unable to. Each time I would select settings and reboot it would BSOD before windows would load (exactly as described above).

This is likely a bit obnoxious to make changes in the middle of a troobleshooting process but I wanted to help narrow down a lot of factors. So the following is what hasa transpired since our last contact:

• Disconnected the M4 SSD drive.
• Formated a Western Digidal Hard drive completely
• Installed a fresh copy of Windows 7
• Installed the drivers that come on the Gigabyte Mother Board disk and windows updates
• did NOT install anything other then Windows 7, the MB drivers, and windows updates
• Set Verifier and BSOD'ed again on the reboot as windows tried to load
• At this point, I reformatted the hdd and loaded windows 7 again. I ran Verifier before loading any drivers or updates. Success! Verifier finally ran.
• I installed all the Windows updates and I was still able to run Verifier.

Next I loaded the drivers from the disk one by one. After each driver install I was able to run Verifier except following the installation of a Realtek HD audio driver and a ACHI/RAID driver. If either of those were installed, I would BSOD on reboot when trying to set Verifier.

So last night I left the computer as described above. No SSD, Only the WD hdd with fresh Windows 7, updates, MB drivers EXCEPT the two problem drivers. No other programs installed. This morning when I went to start the computer I got the BSOD again. Just like every morning it will keep rebooting as windows tries to load and until is BSOD's afterwhich windows will oad normally. Unfortunately, it appears non of the BSOD's recorded a dump file on the new install. It lokks as though there was a Kernel dump?

Regardless, I atatched a new perfmon and JCgriff file.

I have verifier running now with ALL drivers selected. I am a little unclear on which specific screen you would like a screenshot of.

BTW, I truly appreciate the help!

I should mention, those attached files were created without Verifier running. I now have verifier running with all drivers being monitored so tomorrow morning I should be able to get a good record of the crash. I would just like to ensure the BSOD crashes will create a dump file properly. From what I have found online, my computer is set to record the dmps but it did not this morning. Any tips?

Alkoh said:

I should mention, those attached files were created without Verifier running. I now have verifier running with all drivers being monitored so tomorrow morning I should be able to get a good record of the crash. I would just like to ensure the BSOD crashes will create a dump file properly. From what I have found online, my computer is set to record the dmps but it did not this morning. Any tips?

There are several reasons that may prevent you from having a DMP file in the usual places.

If you control panel is not configured for small dump you probably will then find it in C:\windows and it will be called MEMORY.dmp. It will overwrite every crash.

Other reasons are if you have UAC turned off, if you have a small page file, or a page file on a different HD than the OS.