Solved BSOD after fresh install

[carlocgc]

Windows 7 64 home premium
cpu: Phenom II x4 960t
mobo: Asus M4A87TD EVO
ram: Corsair cmx8gx3m4a1333c9 xms3 4x2gb
psu: Corsair vx 550w
gpu: Asus Radeon 6950

Just installed new cpu and ram as computer has been causing a few hardware related issues did a fresh install still getting random BSOD.

 

[carlocgc]

memtest 86+ and windows memory diagnosis found no errors.

 

[carlocgc]

i'm a complete novice as you can no doubt tell.... any info appreciated

 

[carlocgc]

a more recent crash dump here...

 

[carwiz]

The last dump is pointing to the Realtek driver "RTL8192su.sys". It's pretty old. Download and install the latest drivers for your motherboard.

After looking around, this appears to be a driver for a wireless USB LAN adapter. Please update your system specs so we know what we're looking at.

 

[carlocgc]

thats correct im using a USB WLAN dongle. I used the driver from the disc that came with it and windows updated it once i connected to the net... I will reinstall from the disc. Is there a way to upload my specs with a program thanks for the reply.

 

[carwiz]

The first dump is from the USB port driver. Also old.

Before attempting to debug old drivers, you might want to update Windows.

 

[carlocgc]

still downloading the last of windows updates thanks again

 

[carlocgc]

BSOD interrupted install of windows update. starting to think there are a great many problems with this system... any help with this crash dump appreciated

 

[carwiz]

This one was caused by your antivirus: aswmonflt.sys

Remove Avast - http://www.avast.com/uninstall-utility

Reboot then Install MSE - http://www.microsoft.com/security_essentials/

 

[carlocgc]

thanks for the response will do

 

[carlocgc]

specs updated if they can help with first crash dump

 

[carlocgc]

any help with this crash appreciated

 

[mgorman87]

Please enable driver verifier
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

AODDriver2.sys Wed Jun 15 04:38:35 2011 (4DF86F8B)

AMD OverDrive (AODDriver2.sys) is either a stand-alone application, or a component of the AMD VISION Engine Control Center.
Please uninstall the AMD OverDrive program.
If it's the stand-alone app, uninstall it via Control Panel...Programs...Uninstall a program
If it's in the AMD VISION Engine Control Center, you can uninstall it using the AMD uninstall tool (or uninstall the entire AMD VISION Engine Control Center application through Control Panel

Update your Norton AV. It is outdated

RTL8192su.sys Wed May 27 05:32:20 2009 (4A1D08A4)

Update your Realtek USB - Realtek

Rt64win7.sys Sun May 30 23:46:43 2010 (4C033123)

Update your other Realtek - Realtek

Update to SP1 - Learn how to install Windows 7 Service Pack 1 (SP1)

BSOD BUGCHECK SUMMARY

[font=lucida console]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Sun Jan 29 12:16:52.881 2012 (UTC - 5:00)
System Uptime: 0 days 1:42:37.629
Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Core_iCompleteDoneTransfer+a15 )
BUGCHECK_STR:  0x44
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x44_USBPORT!USBPORT_Core_iCompleteDoneTransfer+a15
BiosReleaseDate = 08/24/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/font]

 

[carwiz]

Update Windows then follow the instructions at the top of this page (or the link below) on how to provide the necessary files for debugging.

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

 

[carlocgc]

thanks for the response will do the above. update: all the above done. no blue screen as yet. thank you

 

[carlocgc]

AMD vision engine control center has been uninstalled but AMD install manager remains driver verifier was activated for 24 hours with no crashes and settings were removed yesterday but ive had 2 bsod since then. updated crash dumps here. is this correct for bsod post?

 

[carlocgc]

two more crashes here failed to boot after second crash had to hard reset

 

[mgorman87]

I'm leaning towards hardware at this point.

You said you've already ran memtest? Was it for 7-8 passes?

Please run Prime95
Prime95 - Run all three tests for 3-4 hours each or until fail - http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html


This is in your prefmon report

[B]Device is not present, not working properly, or does not have all of its drivers installed.[/B]
[B]Cause[/B]:A device has a configuration problem that prevents it from working properly.
[B]Details[/B]:The  device,[B][COLOR=Red] AODDriver4.01[/COLOR][/B], is reporting "tv_ConfigMgrErr24". 
This device  will not be available until the issue is resolved. The Plug and Play ID  for this device is ROOT\LEGACY_AODDRIVER4.01\0000.
[B]Resolution:[/B]
1. Verify the correct driver is installed.
2. Try updating the drivers using Windows Update.
3. Check with the manufacturer for an updated driver.
4. Attempt to uninstall and then reinstall the device using Device Manager.

It doesn't look like you got AODDriver removed properly.

BSOD BUGCHECK SUMMARY

[FONT=lucida console]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Feb  4 10:25:42.571 2012 (UTC - 5:00)
System Uptime: 0 days 0:02:27.116
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Probably caused by : ntkrnlmp.exe ( nt!PoIdle+52a )
BUGCHECK_STR:  0x19_3
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x19_3_nt!PoIdle+52a
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Feb  4 10:22:32.243 2012 (UTC - 5:00)
System Uptime: 0 days 0:13:20.788
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+117c3 )
BUGCHECK_STR:  0x1a_8886
PROCESS_NAME:  MsMpEng.exe
FAILURE_BUCKET_ID:  X64_0x1a_8886_nt!_??_::FNODOBFM::_string_+117c3
BiosReleaseDate = 08/24/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Feb  3 20:00:01.617 2012 (UTC - 5:00)
System Uptime: 0 days 0:04:07.788
Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Core_iCompleteDoneTransfer+b2f )
BUGCHECK_STR:  0x19_20
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x19_20_USBPORT!USBPORT_Core_iCompleteDoneTransfer+b2f
BiosReleaseDate = 08/24/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Feb  3 19:42:04.027 2012 (UTC - 5:00)
System Uptime: 0 days 2:43:54.197
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.
ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0
BUGCHECK_STR:  0x1E_0
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e
BiosReleaseDate = 08/24/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/FONT]

 

[carwiz]

It looks like failing memory. If you are OC-ing memory, roll back to your module's factory settings. If not, follow the Memtest86+ instructions here: http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

You could also remove combinations of memory modules to test each one but in the long run will probably take longer to find a failing module. Run the Memtest and let see what you get.