BSOD all time, also at safe mode

Good morning.

I am getting BSOD all time while using IE Chrome while Windows Update, just like any time.
Windows is fresh, it is Win7 x64 pro, yesterday installed.
Parts as listed in profile Q8400 2x2GB patriot CL9 1333mhz, mobo Asus G41m LX3.
At the moment i dont know why i cannot upload minidump files to this thread. It says about administrator needed permissions to do such an action. But i am administrator.

I will try to reboot at safe mode than i hope i will be able to add files. Because it is 3rd time me trying to post thread- yea BSOD while it and couldnt so far.


EDIT: I uploaded few latest minidump files.
I am following steps from thread "BSOD - Posting Instructions" i only hope i manage to do it before next >.> crash.
EDIT: I uploaded SF tool files as well.

If it BSODs even in a safe mode, it is most possibly a hardware error. But before saying anything, we would like to say the necessary data. Only the minidumps will not be enough. Post it following the Blue Screen of Death (BSOD) Posting Instructions.

unlimited1991 said:

UP, new files posted in 1st post.

Still, crash dumps only.

BTW, Driver verifier is enabled here.

Code:

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

Driver verifier makes the system laggy and crashing on its own virtue. Disable it, following Driver Verifier - Enable and Disable .

And, the BSODs are blaming ZoneAlarm, which is a common thing.

Code:

BugCheck 50, {fffff78041e14688, 0, fffff80002c72331, 2}

*** WARNING: Unable to verify timestamp for vsdatant.sys
*** ERROR: Module load completed but symbols could not be loaded for vsdatant.sys

Could not read faulting driver name
Probably caused by : vsdatant.sys ( vsdatant+4b1ef )

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

Description here: Driver Reference Table - vsdatant.sys

Uninstall ZoneAlarm. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
ownload, install and update those, and then run full system scans with both of them, one by one.

Let us know the results. From the next time, upload data in the subsequent posts only, not editing the original post; and post following the Blue Screen of Death (BSOD) Posting Instructions. Only crash dumps are not enough all the times.

Scan the system for possible virus infection with the following programs.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

Update the Intel HD Graphics Driver, either from our forum link, Latest Intel HD Graphics Driver for Windows 7, or You may get it from Intel Download Center.
Moreover, you may run the Intel (R) Driver Update Utility to auto detect the appropriate driver for your computer.

Code:

fffff880`02e52a58  fffff880`049b7063Unable to load image \SystemRoot\system32\DRIVERS\igdkmd64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
 igdkmd64+0x192063
=============================================================
fffff880`04825000 fffff880`04f264c0   igdkmd64 T (no symbols)           
    Loaded symbol image file: igdkmd64.sys
    Image path: \SystemRoot\system32\DRIVERS\igdkmd64.sys
    Image name: igdkmd64.sys
    Timestamp:        Wed Jul 22 04:02:45 2009 (4A66420D)
    CheckSum:         00710035
    ImageSize:        007014C0
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Let us know the results.

It is ok :)

Run tdsskiller for one more time and upload the log here.

2 scan results and reports from Kaspersky Toolkit, 1st scan with no additional options, 2nd with both ''ticked''.

At least 2 BSOD occured from the time the new graphic card driver was installed. Adding new SF full ZIP.
I left computer running and when i backed it wasn't in state it was left, so he had to restart with bsod.
When i was already at computer after i backed 1 BSOD appeared (so the most fresh) was ''bad pool header'' I didn't manage to write more or make a photo of it.

EDIT: And again BSOD, please let me know if you want another full SF with it. I don't know how to force SF just to give additional info about only new BSOD.

Code:

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

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000020, a pool block header size is corrupt.
Arg2: fffff8a0024ada90, The pool entry we were looking for within the page.
Arg3: fffff8a0024add30, The next pool entry.
Arg4: 00000000052a0209, (reserved)

Debugging Details:
------------------

Your crash dumps are not showing any finite probable cause. In such a situation, it is better to 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. Post it following the Blue Screen of Death (BSOD) Posting Instructions.