BSOD Usually once per boot

I usually, but no always, get a BSOD after starting up my computer. After a reboot, I rarely get a BSOD again.

Dump is attached. Thanks for the help.

Hello pgrandst and welcome to TenForums :)

The only BSOD event recorded for us to analyse dates back to 17th Jan so I am not sure that it will be very helpful. The analysis of the dump file suggests a hardware event was to blame. Looking at the detail of the thread shows a graphics driver was misbehaving too.

Code:

BugCheck A, {ffffffffffffff8b, ff, 0, fffff801e32e612a}
Probably caused by : hardware ( nt!PoIdle+32a )

ffff8f80`ef3fb8e8  fffff809`f3a30a2aUnable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
 atikmdag+0x80a2a

The event log confirms what you describe as the shutdowns shortly after the PC restarts. It looks like many of these are from a sleep state and so I'm wondering if the problem is related to this.

Some things to try:

1. Update your graphics driver: the best way to do this is to uninstall everything of AMD using Display Driver Uninstaller and install new drivers from your Graphics card manufacturer or from the AMD website. I would advise to only install the driver and not the Catalyst software for tweaking and control.

2. Some people have had success in disabling "C-states" in the BIOS. This is a low power mode the cpu can use. Make sure it is disabled in your BIOS

Code:

 AMD C1E Support (Note) Enables or disables the C1E CPU power-saving function in system halt state. When enabled, the CPU core frequency and voltage will be reduced during system halt state to decrease power consumption. (Default: Disabled)

3. Turn off the Fast-Start feature - see if this makes a difference.

4. Please fill in your system specs.

Try these ideas for now and report back.

Thanks for your help. I completed #1 and #4 the day after you suggested them and haven't had an issue since.

If I have a further issue, I'll report back.

Problems happened again this weekend... file attached.

Friday night my screen froze so I hit the power switch on the power supply to shut things down. On the next reboot, I got a BSOD within 5 minutes of logging in. After another restart my MB was beeping - I don't know the exact number of beeps, but they were all the same duration and there were more than 5. After roughly three more restarts, I got logged in and my computer worked fine the rest of the night.

Today (Sunday) I've had another BSOD, but have been fine after a restart.

Thanks for the help.

SYSTEM_MANUFACTURER: Gigabyte Technology Co., Ltd.
SYSTEM_PRODUCT_NAME: GA-MA785GM-US2H
BIOS_VERSION: F7
BIOS_DATE: 11/30/2009

Theres a newer BIOS Version for your Mainboard. U should give it a try.

GA-MA785GM-US2H (rev. 3.3) - GIGABYTE - Motherboard , Graphics Card , Laptop , Mini-PC , Server , PC Peripherals and more

Before flashing BIOS please check the Revision on your Mainboard.

I have updated to the latest BIOS - thanks for the tip.

Still having issues both BIOS update. Latest file attached.
Had System Thread Extension not Handled BSOD and then Kernal Security
I also had some BSOD for Inaccessible Boot Device, but that's because I changed to AHCI with the latest BIOS update but then my hard drive wasn't recognized. Booting into safe mode and a few steps later, that was fixed.

Thanks for the help.

Hello again :)

I see you have updated the BIOS to version F11 and you did well to sort out your boot device problem.

The latest crash dump dated yesterday suggests a problem with one of the windows system files.

Code:

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
Probably caused by : WdFilter.sys ( WdFilter!MpAsyncpWorkerThread+201 )

There can be multiple causes for this but with the recent crashes you have had it would be worth checking that you do not have any corrupt system files by running the sfc/ scannow command.

I actually ran sfc/ scannow last night after sorting out the boot device issue - it didn't find anything.

Very Good! :) You are ahead of me!

Would you say the current crashes are exactly like you had before when it always happened just after you started but not after a reboot?

If not, it may be something new and you might need to wait for it to happen a few more times, post a new set of crash dumps so that we can analyse and find a common cause.