Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD all time, also at safe mode


14 Sep 2013   #1

Windows 7 Pro x64
 
 
BSOD in normal and safe mode. EDITED

Good morning.

I am getting BSOD all time while using IE Chrome while Windows Update, just like any time.
Windows is fresh, it is Windows 7 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.

My System SpecsSystem Spec
.

14 Sep 2013   #2
Arc

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1
 
 

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.
My System SpecsSystem Spec
14 Sep 2013   #3

Windows 7 Pro x64
 
 

UP, new files posted in 1st post.
My System SpecsSystem Spec
.


14 Sep 2013   #4
Arc

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1
 
 

Quote   Quote: Originally Posted by unlimited1991 View Post
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.
My System SpecsSystem Spec
14 Sep 2013   #5

Windows 7 Pro x64
 
 

I erased all minidumps before unistalling ZA, everything is just brand new.
I managed to make proper SF raport, with other than minidump files as well.

It was my 2nd attempt to make post, latest BSOD not included, because i was affraid of not having chance to post anything thanks to it.
My System SpecsSystem Spec
15 Sep 2013   #6
Arc

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1
 
 

Scan the system for possible virus infection with the following programs.
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.
My System SpecsSystem Spec
15 Sep 2013   #7

Windows 7 Pro x64
 
 

WDO- scanned twice- nothing
TDSSKiller- scanned once- found 2 unsinged files- Service: AsSysCtrlService as suspicious object, medium risk.
and- Service: RalinkRegistryWriter as same as above suspicious object, medium risk.
Action- both copied to quarantine.

I got system installed for ~3days and it is original, nothing was cracked or other. I lost my original phisical drive so only downloaded it, burnt bootable Windows 7 DVD and used my original Windows 7 key. Didn't replace any originally installed files.

Also I got from asus page (mobo manufacturer) latest graphic accelerator drivers (for more than 24hrs), but okey i will try to download again them.
In 24hrs i should have my Sapphire Radeon HD 6870 delivered. Maybe than problems will stop ;x

When I tryed to scan with the MSE it switched off like in 15sec after scan start. Weird.

EDIT: Intel Driver Update Utility found newer Graphics Driver than given on Asus support page. I will install it and let you know what new BSOD i will receive. Or if it stop i will mark topic as solved.
My System SpecsSystem Spec
15 Sep 2013   #8
Arc

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1
 
 

It is ok

Run tdsskiller for one more time and upload the log here.
My System SpecsSystem Spec
15 Sep 2013   #9

Windows 7 Pro x64
 
 

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.
My System SpecsSystem Spec
15 Sep 2013   #10
Arc

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1
 
 

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   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   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   Tip

Let us know the results, with the subsequent crash dumps, if any. Post it following the Blue Screen of Death (BSOD) Posting Instructions.
My System SpecsSystem Spec
Reply

 BSOD all time, also at safe mode




Thread Tools




Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 10:38 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33