BSOD everytime that Windows tries to install 3 updates

[vrosa]

Every time that I shutdown Windows 7, it tries to instal 3 updates related to DotNet 4.0, and finishes in a BSOD.

I dont have the minidumps cause when it starts again it's like nothing had happened, it doesnt show me any "Unexpected shutdown......" window.

Ideas?

 

[tom982]

Hello vrosa and welcome to the forums

Can you do this for us please?

http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

Tom

 

[vrosa]

Thats what I could get. Minidump file attached.

Thanks in advance.

View attachment 201164

 

[vrosa]

If I try to update through Windows Update I get code 66A ; errors Erro 80070008 ou 8007000e do Windows Update

 

[JMH]

Asacpi.sys

The pre 2009 version of this driver is a known BSOD cause. Yours is dated 2006.

Please visit this link: Asus tek computer inc. -support- drivers and download p7p55d le

ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE
ASUSTeK Computer Inc. - Motherboards- ASUS P5K-VM

Scroll down to the utilities category, then scroll down to the "atk0110 driver for windowsxp/vista/windows 7 32&64-bit" (it's about the 12th item down).

Download and install it.

Go to c:\windows\system32\drivers to check and make sure that the asacpi.sys file is date stamped from 2009 or 2010 (not before).

These crashes were caused by memory corruption/exception (probably a driver).
Please run these two tests to verify your memory and find which driver is causing the problem.

* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have raid update its Driver.



Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



Driver verifier

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 "Special Pool", "Force Pending I/O Requests" and "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.

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.

 

[zigzag3143]

In addition to JMHS' suggestions please do the following

Avast can be a contributing cause of BSOD'S . Please remove and replace with Microsoft Security Essentials AT LEAST TO TEST


http://files.avast.com/files/eng/aswclear5.exe

Microsoft Security Essentials - Free Antivirus for Windows

Old drivers needing updating

ASACPI.sys    10/30/2006 9:09:12 PM        fffff880`0464b000     fffff880`04653000    0x00008000    0x4546b048                        
VMNetSrv.sys    1/24/2007 7:05:46 AM        fffff880`0468c000     fffff880`046a1000    0x00015000    0x45b74b9a                        
SscRdCls.sys    11/16/2007 2:59:09 PM        fffff880`01149000     fffff880`01157000    0x0000e000    0x473df68d                        
adfs.SYS    6/26/2008 3:52:37 PM        fffff880`07090000     fffff880`070a8000    0x00018000    0x48640195                        
vmm.sys    5/15/2009 7:28:12 AM        fffff880`015aa000     fffff880`015f7000    0x0004d000    0x4a0d5fdc                        
SscRdBus.sys    6/18/2009 7:12:35 AM        fffff880`01129000     fffff880`0113e000    0x00015000    0x4a3a2f33

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads