BSOD during Windows Update

Kaktussoft said:

So not a reinstall at all!! I asked him many times so he gave as wrong information!

Sorry about that.

writhziden said:

It appears the user is trying to do a repair install. There are a ton of 3rd party drivers installed and loaded, including AVG antivirus software:

Code:

GEARAspiWDM.sys Mon May 18 06:17:04 2009 (4A1151C0)
intelppm.sys Mon Jul 13 17:19:25 2009 (4A5BC0FD)
amdxata.sys Fri Mar 19 10:18:18 2010 (4BA3A3CA)
btath_rcp.sys Thu Jun 24 00:17:21 2010 (4C22F871)
btath_flt.sys Thu Jun 24 00:17:38 2010 (4C22F882)
btath_bus.sys Thu Jun 24 00:17:43 2010 (4C22F887)
btath_hcrp.sys Tue Jun 29 03:30:43 2010 (4C29BD43)
jraid.sys Tue Aug 10 03:28:44 2010 (4C611BCC)
btath_lwflt.sys Mon Sep 13 02:26:54 2010 (4C8DE04E)
btath_a2dp.sys Thu Sep 16 05:34:42 2010 (4C9200D2)
e1c62x64.sys Tue Sep 21 15:34:15 2010 (4C9924D7)
HECIx64.sys Tue Oct 19 17:33:43 2010 (4CBE2AD7)
btfilter.sys Fri Oct 22 00:40:47 2010 (4CC131EF)
RTKVHD64.sys Tue Nov 2 05:25:59 2010 (4CCFF547)
mvxxmm.sys Mon Nov 22 00:00:18 2010 (4CEA1502)
mv91xx.sys Mon Nov 22 00:00:45 2010 (4CEA151D)
nusb3xhc.sys Thu Dec 9 21:50:35 2010 (4D01B19B)
nusb3hub.sys Thu Dec 9 21:50:35 2010 (4D01B19B)
speedfan.sys Fri Mar 18 10:08:46 2011 (4D83838E)
RzSynapse.sys Wed Apr 6 03:29:13 2011 (4D9C3269)
Rt64win7.sys Fri Jun 10 00:33:15 2011 (4DF1BAAB)
avgmfx64.sys Fri Dec 23 05:08:12 2011 (4EF46F2C)
avgrkx64.sys Mon Jan 30 20:11:41 2012 (4F275BED)
avgldx64.sys Tue Feb 21 20:57:53 2012 (4F4467C1)
MpFilter.sys Fri Mar 9 04:05:26 2012 (4F59E3F6)
nvhda64v.sys Wed Apr 18 11:07:54 2012 (4F8EF4EA)
avgidsha.sys Wed Apr 18 20:19:15 2012 (4F8F7623)
nvlddmkm.sys Tue May 15 01:35:36 2012 (4FB20748)

GEARAspiWDM.sys
intelppm.sys
amdxata.sys
btath_rcp.sys
btath_flt.sys
btath_bus.sys
btath_hcrp.sys
jraid.sys
btath_lwflt.sys
btath_a2dp.sys
e1c62x64.sys
HECIx64.sys
btfilter.sys
RTKVHD64.sys
mvxxmm.sys
mv91xx.sys
nusb3xhc.sys
nusb3hub.sys
speedfan.sys
RzSynapse.sys
Rt64win7.sys
avgmfx64.sys
avgrkx64.sys
avgldx64.sys
MpFilter.sys
nvhda64v.sys
avgidsha.sys
nvlddmkm.sys


Analysis:

We need to try to figure out exactly what the issue is. The crash recorded was a 0x7A crash. This indicates hard disk corruption, bad sectors, a failing hard disk, Windows files or registry corruption, viruses, or memory problems.

• If you are overclocking any hardware, please stop.
  
  
• Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log (you may need to search for wininit instead of chkdsk).
  For any drives that do not give the message:
  Windows has checked the file system and found no problems
  run disk check again as above. In other words, if it says:
  Windows has made corrections to the file system
  after running the disk check, run the disk check again.
  
  
• Run all Basic tests with SeaTools: S.M.A.R.T. Check, Short Drive Self Test, Drive Information, Short Generic, and Long Generic. Run the tests for all HDDs.
  SeaTools for Windows
  
  SeaTools for DOS
  
  
• If you have an SSD, make sure the following are up to date:
  • SSD firmware
  • BIOS Version
  • Chipset Drivers
  • Hard disk controller drivers/SATA drivers
  • If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.
  
  
  
• Check Windows for corruption. Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations. Use OPTION THREE of SFC /SCANNOW Command - System File Checker to provide us with the sfcdetails.txt file if errors occur.
  
  
• Download and install Malwarebytes, update it, do not start the free trial, and then run a full scan. Also run a full scan with your antivirus software installed on your system. If you do not have antivirus software installed, see the Good and Free system security combination. for better security steps and scanning tools. Make sure to update the security software before running the full scan.
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
     Warning

  Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. WARNING: The steps that follow can void your warranty!!!
  
  For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
  
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.
  
  Once these steps have been followed, it is safe to remove and replace components within your computer.

BugCheck 0x7A

0x7A:

Windows Dev Center - Hardware said:

Cause

Frequently, you can determine the cause of the KERNEL_DATA_INPAGE_ERROR bug check from the error status (Parameter 2). Some common status codes include the following:

• 0xC000009A, or STATUS_INSUFFICIENT_RESOURCES, indicates a lack of nonpaged pool resources.
  
  
• 0xC000009C, or STATUS_DEVICE_DATA_ERROR, typically indicates bad blocks (sectors) on the hard disk.
  
  
• 0xC000009D, or STATUS_DEVICE_NOT_CONNECTED, indicates defective or loose cabling, termination, or that the controller does not see the hard disk.
  
  
• 0xC000016A, or STATUS_DISK_OPERATION_FAILED, indicates bad blocks (sectors) on the hard disk.
  
  
• 0xC0000185, or STATUS_IO_DEVICE_ERROR, indicates improper termination or defective cabling on SCSI devices or that two devices are trying to use the same IRQ.

These status codes are the most common ones that have specific causes. For more information about other possible status codes that can be returned, see the Ntstatus.h file in the Microsoft Windows Driver Kit (WDK).

Another common cause of this error message is defective hardware or failing RAM.

A virus infection can also cause this bug check.

Resolution

Resolving a bad block problem: An I/O status code of 0xC000009C or 0xC000016A typically indicates that the data could not be read from the disk because of a bad block (sector). If you can restart the computer after the error, Autochk runs automatically and attempts to map the bad sector to prevent it from being used anymore.

If Autochk does not scan the hard disk for errors, you can manually start the disk scanner. Run Chkdsk /f /r on the system partition. You must restart the computer before the disk scan begins. If you cannot start the computer because of the error, use the Recovery Console and run Chkdsk /r.

Warning If your system partition is formatted with the FAT file system, the long file names that the Windows operating system uses might be damaged if you use Scandisk or another MS-DOS-based hard disk tool to verify the integrity of your hard disk from MS-DOS. Always use the version of Chkdsk that matches your version of Windows.

Resolving a defective hardware problem: If the I/O status is C0000185 and the paging file is on an SCSI disk, check the disk cabling and SCSI termination for problems.

Resolving a failing RAM problem: Run the hardware diagnostics that the system manufacturer supplies, especially the memory scanner. For more information about these procedures, see the owner's manual for your computer.

Check that all the adapter cards in the computer are properly seated. Use an ink eraser or an electrical contact treatment, available at electronics supply stores, to ensure adapter card contacts are clean.

Check the System Log in Event Viewer for additional error messages that might help identify the device that is causing the error. You can also disable memory caching of the BIOS to try to resolve this error.

Make sure that the latest Windows Service Pack is installed.

If the preceding steps do not resolve the error, take the system motherboard to a repair facility for diagnostic testing. A crack, a scratched trace, or a defective component on the motherboard can cause this error.

Resolving a virus infection: Check your computer for viruses by using any up-to-date, commercial virus scanning software that examines the Master Boot Record of the hard disk. All Windows file systems can be infected by viruses.

The above was taken from Bug Check 0x7A: KERNEL_DATA_INPAGE_ERROR.

Remove AVG:

AVG can sometimes contribute to these types of crashes. I would recommend removing it with the AVG Remover and replacing it with Microsoft Security Essentials - Free Antivirus for Windows.

My suspicions seem true as the Long Generic Test for hard drive failed. What should I do?

I was doing a windows repair install and it BSOD'd. After running all those tests, the SeaTools long generic tests failed.