BSODs random since build - various bugcheckcodes

[dagaraelder]

Dear Friends,

I have been experiencing BSODs randomly from time of build. SFdebug files are attached.

Running:

New Build - all new components

Windows 7 Home Premium 64bit full retail - build 6.1.7601 - SP1 and all updates
Motherboard ASUS P8Z77-V
Case - Antec 1100
16 GB DDR3 1600 Corsair
CPU Intel i5-3570K
XFX Pro750 watt power supply
Bios American Megatrends 2104 - 8/13/2013 (just updated - another crash occurred after update)
ASUS Nvidia Geforce GTX650 Ti Boost
C: 120 GB SSD - M4-CT128M4SSD2
D: LG CD/DVD
E: 300 MB WD Sata II - WD3200BEKT
F: WD2002FAEX - 2GB Sata III
G: ASUS Bluray
Cooling - CoolerMaster Gemin II S524 - CPU temp ~29 C.
Display - ASUS VS228
Keyboard Logitech K350 wireless
Touchpad Logitech T650 wireless

System performance rocks except when it crashes. I have tried to update all drivers and as noted above I just flash updated the bios. I have been building machines for years but I have never had BSODs.
All help greatly appreciated.

 

[dagaraelder]

Here are the zip file results of the SF-Diagnostic containing the minidump files. It took me a while to get around the error message.

 

[Arc]

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

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff8800886b210, 0, 0}

*** WARNING: Unable to verify timestamp for avgtdia.sys
*** ERROR: Module load completed but symbols could not be loaded for avgtdia.sys
Probably caused by : NETIO.SYS ( NETIO!ArbitrateAndEnforce+e3 )

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

Uninstall AVG following http://www.avg.com/us-en/utilities. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.

Download, install and update those, and then run full system scans with both of them, one by one; for a security reason, as the installed antivirus is failing.

Let us know the results.

 

[dagaraelder]

Dear Arc,
As per your instructions, I have removed AVG and installed and updated MSE and MBAM.
The computer crashed towards the end of the first MSE full scan. BSOD codes are in the attached file. A second full MSE scan was successfully completed with no exceptions. MBAM completed on the first run and reported one object found which was PUP.Optional.Conduit A which was removed.

 

[dagaraelder]

Minidump file attached with today's minidump somewhere in the middle of the list.

 

[Arc]

Minidump file attached with today's minidump somewhere in the middle of the list.

Checked it, nothing significant is there.

Let us know for any further BSODs.

 

[dagaraelder]

I have done a complete reinstall of Windows 7 SP 1 with all updates and all drivers except I kept the NVidia driver at v.314.22.

System was solid for 2 days and now the BSODs are back. The Blue Screen indicates "memory management" which is an error message that has come up previously.

I am also getting "NVidia Kernel Mode Driver V314.22 stopped responding and has successfully recovered." This message has also come up many times before the format/reinstall of Windows.

 

[Arc]

System was solid for 2 days and now the BSODs are back. The Blue Screen indicates "memory management" which is an error message that has come up previously.

The crash dumps say that you need to update the Drivers for Atheros AR9485 and Windows 7.

I am also getting "NVidia Kernel Mode Driver V314.22 stopped responding and has successfully recovered." This message has also come up many times before the format/reinstall of Windows.

Does it appear with any other version of display driver? A test is required.

 

[dagaraelder]

Thank you.
I have updated the Atheros driver to the version found with your link.
I did get the NVidia driver failure message with other versions of the driver. I think it also appeared with v332.21.

 

[Arc]

I did get the NVidia driver failure message with other versions of the driver. I think it also appeared with v332.21.

Not happy to say it, but it is the time to change the GPU.

 

[dagaraelder]

I have moved the video card to another slot and I have not received any further notices of the video driver failing since my last report. Also the system appeared to be much more stable, however, it crashed again last night.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 4105
Additional information about the problem:
BCCode: 3b
BCP1: 00000000C0000005
BCP2: FFFFF80002F8D16A
BCP3: FFFFF88009561C40
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

 

[Arc]

Follow the Blue Screen of Death (BSOD) Posting Instructions. Upload the data in your next post.

 

[dagaraelder]

I have moved the video card to another slot and I have not received any further notices of the video driver failing since my last report. Also the system appeared to be much more stable, however, it crashed again last night.

 

[dagaraelder]

I have removed the NVidia card and am still getting BSOD.
Updated DMP zip file attached. Thanks.

 

[Arc]

If you dont supply the adequate data to us, it is problematic to us to assist you. Run SF diag tool, zip and upload ALL the data.

Because, the latest BSOD is caused by iaStor.sys, and apparently (from the last supplied data), iaStor is disabled in your computer.

Without the required data, we cannot see what is going on there.

 

[dagaraelder]

Yes, of course. Here is the updated data. Thanks.

 

[Arc]

Get rid of intel rapid storage. First uninstall it from Control Panel > Programs and Features. Then Uninstall the driver from device manager.

1. Right click on "my computer" icon and click "manage" on the context menu.
2. It will open the "computer management" window.
3. Select "Device Manager" in the left pane, It will list all the existing devices up.
4. Expand "IDE ATA/ATAPI controllers" by clicking on the triangle in front of it.
5. Select one Intel device item under it, right click, uninstall.
6. Continue the process for all Intel items under "IDE ATA/ATAPI controllers"
7. Now restart the computer. At restart, windows will auto configure the appropriate native system driver.

The recent BSODs are storage related.

BugCheck 1E, {ffffffffc0000005, fffff80002c6eac5, 0, ffffffffffffffff}

[COLOR=Red]Probably caused by : fileinfo.sys [/COLOR]( fileinfo!FIPreCreateCallback+1ad )

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

BugCheck 24, {c08a5, 0, 0, 0}

[COLOR=Red]Probably caused by : Ntfs.sys[/COLOR] ( Ntfs!NtfsPagingFileIo+155 )

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

BugCheck 50, {fffff78140000b08, 0, fffff80002cc0d21, 5}

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

Could not read faulting driver name
[COLOR=Red]Probably caused by : iaStor.sys[/COLOR] ( iaStor+5208b )

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

And one of them is specifically pointing to Intel Rapid Storage.

 

[dagaraelder]

Done. Thanks.

 

[dagaraelder]

Arc----The crashes continue. On the blue screen they all say "special pool detected memory corruption." I have run memtest86+ many times. The last time for about 9 hours. No errors reported. The crashes started soon after the build. I am wondering if I have a defective motherboard.

 

[Arc]

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.