Random BSOD

[herbvan]

I've been getting BSODs for a while and have been trying to determine which driver is bad with no success. I ran to log gather program and have attached the .zip file. For each BSOD, any analysis points in different directions (kernal, AVG, this way, that way). I've gone beyond my pay grade with this problem. Thank you in advance for your help.

 

[essenbe]

Hello, herbvan and welcome to the forums. You only have one dump file. If you are using any disk cleanup utilities, please stop until we get this figured out. They all delete dump files and error reports by defult. How long have you had this issue and did you change any hardware, software or drivers just before it started?

Please make sure your computer is configured for Small Memory Dumps. http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html

Please go to Windows Update and click on Installed Updates and search for KB3022345 and KB3068708. If they are installed, please uninstall them, this will tell you how http://www.sevenforums.com/tutorials/24373-windows-update-uninstall-update.html

After doing that please open an elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.

 

[herbvan]

Thanks for climbing in the saddle for this problem. Both of those updates we're installed and I'm in the process of cleaning them out. We'll let that brew for a while and I'll post the results.

 

[essenbe]

Also, please watch Windows update for those Updates to return. If you see them ready to be installed, uncheck them, Right click them and select Hide. Then you shouldn't have to worry about them any more. Also make sure the computer is configured for small Memory Dumps, and if you are using any Disk Cleanup Utilities, please do not use them. They all will delete error reports and dump files by default. We need those. Let me know how the scan goes when you have time to do all of this stuff.

 

[herbvan]

The BSOD just happened for the 3rd time in the past few days and I've attached the dump analysis below (3 dumps). There seems to be no consistency with the causes. I discontinued on the the bad hotfixes that you referenced and the other one has not popped up.

Thank you in advance.

 

[essenbe]

These are the results

fffff880`0c58eb00  fffff8a0`0e7714b0
fffff880`0c58eb08  fffff880`019e864bUnable to load image \SystemRoot\system32\drivers\ddkmdldr.sys, Win32 error 0n2
*** [COLOR=red]WARNING: Unable to verify timestamp for ddkmdldr.sys[/COLOR]
*** ERROR: Module load

OSBASE iDisplay Software

Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff880013914f0, fffff8800badc850, 0}
[COLOR=red]Probably caused by : fltmgr.sys[/COLOR] ( fltmgr!FltAllocateContext+60 )
Followup: MachineOwner

That is the Windows file system manager which comes from Windows Update

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

fffff880`0badc6f8  fffff800`0396e095 nt!ObpLookupObjectName+0x195
fffff880`0badc700  fffff880`01f7c284Unable to load image \SystemRoot\system32\DRIVERS\avgmfx64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for avgmfx64.sys
[COLOR=red]*** ERROR: Module load completed but symbols could not be loaded for avgmfx64.sys[/COLOR]
 avgmfx64+0xb284

That is your AVG A/V.

Please rub Seatools for DOS, both the long and short test http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html#Part3

As far as the Obase, I am sure you know what they do and what software from them is on your computer. OBASE. Please update the driver or uninstall the software.

Your AVG is also causing problems. If the sfc scan you did comes back clean and the Seatools and check disk come out OK, Please uninstall AVG and replace it with Microsoft Security Essentials (Microsoft Security Essentials - Microsoft Windows), at least for a test.
Also please run Check Disk http://www.sevenforums.com/tutorials/433-disk-check.html