Keep getting BSOD at random moments

I have Windows 7 Ultimate, I keep getting BSOD errors (they range from MEMORY_MANAGEMENT => BAD_POOL_HEADER)

Here is the dump files, I am really sick of these errors now...

BSODSUCKSBADLY said:

I have Windows 7 Ultimate, I keep getting BSOD errors (they range from MEMORY_MANAGEMENT => BAD_POOL_HEADER)

Here is the dump files, I am really sick of these errors now...

SF_21-04-2013.zip (906 KB)
https://mega.co.nz/#!tUtSTYKQ!MFWScm1Ck01V2H0KVBK8u0pr_9p0u5WdebdSqiFy9Aw

Screenshots and Files - Upload and Post in Seven Forums

Post the zip following this instructions.

Your crash dumps are not showing any finite probable cause.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If memtest comes clean, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

Also, the MSINFO32 you supplied is corrupt. upload your MSINFO32.nfo file.

1. Click on the start button
2. Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
3. File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
4. Give the time for processing, it will save a .nfo file on your desktop.
5. Zip it, and upload it following the instruction.

BSODSUCKSBADLY said:

I couldnt do the driver verifier, it wont boot up my computer when enabled.

I will do a overnight memtest to see if that is the issue, I did a memtest before but nothing turned up.

Here is the system info thingy.

Please save the MSINFO32 as a .nfo version, not in a .exe version. The exe version opens my MSINFO32 only.

Remove everything other than the antivirus from the startup. Then enable Driver verifier again. Make it sure that you are not selecting any driver provided by "microsoft" and "unknown".

Hope you will be able to reach to the desktop with DV enabled now.

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 try driver verifier again ..... dont select any driver provided by "microsoft" or "unknown" in the list. Hopefully you will be able to get reach the desktop with DV enabled.

In the zip, there is only one dump for today ..... 24:04:2013 AM 03:21. Which is not DV enabled.

Code:

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

and indicates to Ntfs.sys as the reason behind the BSOD.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff88001486235, 0, ffffffffffffffff}

Probably caused by : Ntfs.sys ( Ntfs!NtfsOpenFile+6d5 )

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

A deeper search indicates to Acronis True Image Snapshot Manager driver (also included in Seagate DiscWizard), which can cause a storage access issue and a Ntfs.sys BSOD.

Code:

fffff880`0a33a0b8  fffff880`01a288fbUnable to load image \SystemRoot\system32\DRIVERS\snapman.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for snapman.sys
*** ERROR: Module load completed but symbols could not be loaded for snapman.sys
 snapman+0x288fb

It is an old product.

Code:

fffff880`01a00000 fffff880`01a46000   snapman  T (no symbols)           
    Loaded symbol image file: snapman.sys
    Image path: \SystemRoot\system32\DRIVERS\snapman.sys
    Image name: snapman.sys
    Timestamp:        Wed Mar 09 18:52:38 2011 (4D777F1E)
    CheckSum:         0004F614
    ImageSize:        00046000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

First try to update Acronis. If updating does not help, uninstall it.