Help me with BSOD

[haroonazeem638]

Hello,

I have attached the rar file which contains the dump files after bsod.

This is now an everyday problem. I have updated all my drivers. I have even tried to reinstall Windows 7. I even removed all hardware and put it back in to make sure there was no problem in the case and then I updated the drivers again.

Unfortunately, I get this blue screen almost every week. Please help me figure out what the problem is so I can fix it.

Thank you very much.

Haroon

 

[zigzag3143]

Hello,

I have attached the rar file which contains the dump files after bsod.

This is now an everyday problem. I have updated all my drivers. I have even tried to reinstall Windows 7. I even removed all hardware and put it back in to make sure there was no problem in the case and then I updated the drivers again.

Unfortunately, I get this blue screen almost every week. Please help me figure out what the problem is so I can fix it.

Thank you very much.

Haroon

Since the probable cause is a win 7 file I would run a system file check
to do that type cmd in search>right click and run as admin>sfc /scannow (note the space between sfc and "/")


Let us know if you need help


Ken

 

[haroonazeem638]

I just did that. no errors or problems found.
what should I do now?

 

[usasma]

Lot's of different reasons for this set of errors (hardware and software).
Let's try using Driver Verifier to rule out the 3rd party drivers. Please follow these instructions:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

 

[haroonazeem638]

I tried using the verifier.

After restarting my pc, it crashed before I could reach the desktop. The blue screen gave me a message similar to this.

**EDIT**
Also, this is what I got when I reached my desktop. Don't know if this can help.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033
Additional information about the problem:
BCCode: c4
BCP1: 00000000000000F6
BCP2: 00000000000000EC
BCP3: FFFFFA8006F0D4F0
BCP4: FFFFF880043E7257
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1


**END EDIT**

"A device driver is corrupt. The faulty driver on the kernel stack must be replaced with a working version."

Unfortunately, it did not tell me what driver it was. I had to go to safe mode to turn off the driver verifier as you instructed.

I have attached the new dump file. Please help!

Haroon.

 

[usasma]

Driver Verifier blames ASACPI.sys as the problem. Please visit the Asus website at this link: ASUSTeK Computer Inc.-Support-
Go to the Utilities section and download the ATK0110 driver for WindowsXP/Vista/Win7 32&64-bit


Then, extract the file and execute (double click on) the AsAcpiIns.exe file in the 64 directory.
Then check to see what the date/time stamp of the ASACPI.sys file is.

The old one was: Wed May 13 21:25:17 2009
The new one should be: Thu May 14 09:26:24 2009

Let us know if there are any further BSOD's.

Summary of the BSOD:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Apr  4 23:52:02.618 2010 (GMT-4)
System Uptime: 0 days 0:00:35.632
BugCheck C4, {f6, ec, fffffa8006f0d4f0, fffff880043e7257}
*** WARNING: Unable to verify timestamp for ASACPI.sys
*** ERROR: Module load completed but symbols could not be loaded for ASACPI.sys
Probably caused by : ASACPI.sys ( ASACPI+1257 )
BUGCHECK_STR:  0xc4_f6
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  SixEngine.exe

 

[haroonazeem638]

Hi,

The date on the Asacpi.sys is May 14, 2009. 9:26am. I also checked this file in the Windows/system32 folder. It's has the same date and time.

Also, I recently(2 days ago) installed the asus six engine software. However, the BSOD problem was happening before that too. So could there be another driver causing the problem?

Also, I got a BSOD today too and it said that there was some "win32k.sys" error. There is no dump file for this last BSOD, so I have no idea how to give you more information about that.

How do I fix this problem? Do you want me to uninstall the Asus software and try running the driver verifier again to see if there are other drivers causing the BSOD?

Thanks.
Haroon

 

[usasma]

I would suggest removing all the Asus software as it's been known to cause problems in some systems.

Also, the P5 series of boards have been known to have BSOD issues due to memory timings/settings/voltages.
Please verify the settings required on both the Asus website and the OCZ website - then ensure that your timings/settings/voltages are the same (I wouldn't use the "Auto" setting on the P5 series mobo's if you're having problems).

Please check to be sure that the system is still set to make minidumps: Set MiniDump
Please generate the report in this post for us: http://www.sevenforums.com/crash-lockup-debug-how/66913-sf-diagnostic-tool.html

Don't use the Driver Verifier again - it'll just confuse the issue right now.
Let's wait for a couple of BSOD's that we can see - then we'll see if that suggests the use of Driver Verifier.

 

[haroonazeem638]

I just removed all asus software. After a few minutes, I got another BSOD while watching a video online. There was no dump file because it was turned off but after following your instructions, I turned it on.

I got this message:

A problem has been detected and windows has been shut down to prevent further damage to your computer .

IRQL_NOT_LESS_OR_EQUAL

bla bla...

I'll upload the new dump file using your software when I get another BSOD.

Thank you

 

[usasma]

The IRQL NOT LESS OR EQUAL error is a sign that Driver Verifier needs to be run (again).

 

[haroonazeem638]

Hi,

I ran the verifier. I tried to attach the file after using SF diagnostic tool. But the file is too big (71mb). It wouldn't let me attach a file more than 8mb. Any idea?

I have attached the last dump file though. Thanks.

Haroon

 

[usasma]

Zip up the SF Diagnostic Tool folder and upload it to a free filehosting service (don't use RapidShare as the analysts here can't get to it).

Or, zip up things from the folder separately and upload them that way.

AVGIDSDriver.sys is blamed in the memory dump - and the memory dump is a DRIVER_VERIFIER_DETECTED_VIOLATION

The driver is the AVG IDS Application Activity Monitor Driver - and the solution here is to remove AVG and install another antivirus to test. Here's the procedure:

Anti-Virus Removal:
Please do the following:
- download a free antivirus for testing purposes: Free AntiVirus
- uninstall the AVG from your system (you can reinstall it, if so desired, when we're done troubleshooting)
- remove any remnants of AVG using this free tool: AVG Antivirus and Security Software - Tools download
- IMMEDIATELY install and update the free antivirus
- check to see if this fixes the BSOD's

Summary of the BSOD:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Apr  9 01:23:35.268 2010 (GMT-4)
System Uptime: 0 days 0:00:54.281
BugCheck C4, {f6, 534, fffffa8006c81b30, fffff880011e37d9}
*** WARNING: Unable to verify timestamp for AVGIDSDriver.sys
*** ERROR: Module load completed but symbols could not be loaded for AVGIDSDriver.sys
Probably caused by : AVGIDSDriver.sys ( AVGIDSDriver+167d9 )
BUGCHECK_STR:  0xc4_f6
PROCESS_NAME:  svchost.exe

 

[haroonazeem638]

Here is the SF Diagnostic Tool foler uploaded.

http://www.megaupload.com/?d=BW1MZU27

Please check. Thanks

 

[usasma]

Nothing new in the Seven Forums folder.

I ran all of the memory dump files.

The AVG is still your primary problem.
BUT, there is an issue with the ASACPI.sys driver that's dated from 2005.

Extract the files, open the 64 folder and double click on the AsAcpiIns.exe file to install the latest (2009) version of the ASACPI.sys file.

Finally, please check both the Asus support website and the OCZ support website to ensure that you are using the correct settings/timings/voltages for your memory.

Good luck!

Please go to the Asus support website for your motherboard and download the Utility named ATK0110 ACPI Utility.

 

[haroonazeem638]

I havent removed the AVG yet. I was going to do it soon BUT I Found this!(see attached)

SF Diagnostic Tool.exe a Trojan horse?

Any idea?

 

[usasma]

I've used the SF Diagnostic Tool on many occasions.
I'd have to wonder if there's malware on your system that's posting false reports to confuse you.

I'd suggest trying a couple of these free, online scans (in case your current protection is compromised): Malware