Windows 7 SOS Random BSOD W7 Pro 64bit [Complete Log Files Attached]

[Pixelation]

Hello everyone, it's nice to find a forum where people are taking their personal time to help others. You have my appreciation and thanks.

I have recently formatted a old PC. Everything seemed to have gone as planned... until I was bombarded by random BSODs. They seem to happen at random; load doesn't seem to be a factor here.

I have attached all necessary log files [W7 Dianostic Tool report, CPU Screenshot and PassMark RAMMON html file].

System Specs are below:

CPU: Phenom II x4 965 (Default clocked w/ Zalman Cooler) [highest temps 62C on overnight Prime95 torture test]
GPU: MSI 5770 1GB
Ram: 4GB [2GB x 2 Corsair @ 1333mhz]
PSU: 430W Thermaltake
HDD: WD Blue 640GB
Case: Antec 300

I used WD's utility program to test the HDD prior to reformat. The HDD is in excellent condition. However, I was bombarded with completely random BSODs upon completing. I decided to reformat again. This time, I got 2 BSOD by day 3; much better than the dozen or so BSOD I got the first time around. However, it still greatly concerns me. I have attached all necessary log files, I have followed the sticky instructional thread down to the letter. Please tell me if I am missing any information. Thanks in advance.

Michael

PS: All I have installed on the PC so far:

=> All W7 system updates
=> Avast Anti-Virus
=> CCCP (Combined Community Codec Pack)
=> League of Legends (haven't really had a chance to play it)
=> CPUZ + HWMonitor
=> GPU Drivers (AMD Catalyst)
=> Utility programs used to create the BSOD logs (as mentioned in the sticky)

I have just finished a "sfc /scannow" in cmd prompt. It said it detected corrupt OS(unsure) files and was unable to repair them.

 

[Pixelation]

I apologize for the double post. But I am desperate at this point because this PC is unstable and is giving random BSODs. I am only using this PC when I absolutely have to because I fear I may further damage or develop the unknown issue at hand.

Any assistance on why my PC is behaving like this would be greatly appreciated.

Please tell me if I missed anything information.


Michael

 

[usasma]

I understand that this is an urgent problem for you. Unfortunately there just aren't very many of us who do BSOD analysis. I'm online once a day and this is my second stop (my first stop is answering all the replies that have been made to previous posts).

There are only 2 memory dumps (from July 3) in the uploaded reports. If there have been more, please do this:

Upload Dump Files:
NOTE: If using a disk cleaning utility, please stop using it while we are troubleshooting your issues.
Please go to C:\Windows\Minidump and zip up the contents of the folder. Then upload/attach the .zip file with your next post.
Left click on the first minidump file.
Hold down the "Shift" key and left click on the last minidump file.
Right click on the blue highlighted area and select "Send to"
Select "Compressed (zipped) folder" and note where the folder is saved.
Upload that .zip file with your next post.

If you have issues with "Access Denied" errors, try copying the files to your desktop and zipping them up from there. If it still won't let you zip them up, post back for further advice.

If you don't have anything in that folder, please check in C:\Windows for a file named MEMORY.DMP. If you find it, zip it up and upload it to a free file hosting service. Then post the link to it in your topic so that we can download it.

Also, search your entire hard drive for files ending in .dmp, .mdmp, and .hdmp. Zip up any that you find and upload them with your next post.

Then, follow the directions here to set your system for Minidumps (much smaller than the MEMORY.DMP file): Link RemovedMore info on dump file options here: Overview of memory dump file options for Windows 2000, Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2

I found 4 of these errors in the System Log of Event Viewer:

Event[4586]:
Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 2013-07-03T18:42:58.501
Event ID: 41
Task: N/A
Level: Critical
Opcode: Info
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: GaMingPC
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

These errors are Windows saying it doesn't know why it shut down. Most often these are hardware errors. I suggest that you start with monitoring your temps with this free program: HWMonitor CPUID - System & hardware benchmark, monitoring, reporting You can also get a head start on the other diagnostics if you'd like: Link Removed

Your BIOS dates from 2009. Please check at the manufacturer's website to see if there are any BIOS updates available for your system. Also check the readme file to see if they apply to the problems that you are having. Please be advised that flashing the BIOS is a very unforgiving process - and one mistake can physically damage your motherboard.

Only 118 Windows Updates installed. Most systems have 160 or more. Please visit Windows Update and get ALL available updates (it may take several trips to get them all).

You have a 802.11n USB Wireless LAN Card:

I do not recommend using wireless USB network devices. Especially in Win7/Win8 systems.
These wireless USB devices have many issues with Win7(and I suspect with Win8) - using Vista drivers with them is almost sure to cause a BSOD.
Should you want to keep using these devices, be sure to have Win7/Win8 drivers - DO NOT use Vista drivers!!!
An installable wireless PCI/PCIe card that's plugged into your motherboard is much more robust, reliable, and powerful.

AMD OverDrive (AODDriver2.sys) is either a stand-alone application, or a component of the AMD VISION Engine Control Center. This driver is known to cause BSOD's on some Windows systems.

Please un-install all AMD/ATI video stuff from Control Panel...Programs...Un-install a program
Then, download (but DO NOT install) a fresh copy of the ATI drivers from Link Removed (in the upper right corner of the page)
Use this procedure to install the DRIVER ONLY: Link Removed

If the device (AODDriver or AODDriver4.01) remains a problem, open Device Manager, select the "View" item.
Then select "Show hidden devices" and scroll down to the Non-Plug and Play Drivers section.
Locate the AODDriver entry, right click on it and select "Un-install". Reboot for changes to take affect.

Sometimes the driver remains and continues to cause BSOD's. If this is the case for you, post back and we'll give further instructions for safely removing it.

If overclocking, please stop. Remove the overclock and return the system to stock/standard values while we're troubleshooting. Once the system is stable again, feel free to resume the overclocking.

If all of this doesn't stop the BSOD's, please run these free hardware diagnostics: Link Removed. Let us know the results and we can move on from there.

Analysis:
The following is for informational purposes only.

[font=lucida console]**************************Wed Jul  3 04:22:15.212 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\070313-17331-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 2:59:09.757[/B]
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
Probably caused by :[B]ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+44cde )[/B]
BugCheck [B]BE, {fffff8a00eee05a4, 800000006b4ed121, fffff8800264f260, b}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: fffff8a00eee05a4, Virtual address for the attempted write.
Arg2: 800000006b4ed121, PTE contents.
Arg3: fffff8800264f260, (reserved)
Arg4: 000000000000000b, (reserved)
BUGCHECK_STR:  0xBE
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID: [B]X64_0xBE_nt!_??_::FNODOBFM::_string_+44cde[/B]
  BIOS Version                  V4.0
  BIOS Release Date             12/17/2009
  Manufacturer                  MICRO-STAR INTERNATIONAL CO.,LTD
  Product Name                  MS-7576
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Jul  3 00:28:01.349 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\070313-26535-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 1:54:28.910[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!HvIsCellAllocated+153 )[/B]
BugCheck [B]50, {fffff8a0c001fe92, 0, fffff80002d10323, 5}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: fffff8a0c001fe92, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002d10323, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000005, (reserved)
BUGCHECK_STR:  0x50
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  rundll32.exe
FAILURE_BUCKET_ID: [B]X64_0x50_nt!HvIsCellAllocated+153[/B]
  BIOS Version                  V4.0
  BIOS Release Date             12/17/2009
  Manufacturer                  MICRO-STAR INTERNATIONAL CO.,LTD
  Product Name                  MS-7576
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.

[font=lucida console]**************************Wed Jul  3 04:22:15.212 2013 (UTC - 4:00)**************************
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
Rt64win7.sys                Fri Jun 10 02:33:15 2011 (4DF1BAAB)
[B]AODDriver2.sys              Thu Apr  5 05:23:37 2012 (4F7D6499)[/B]
netr28ux.sys                Fri Aug 17 10:30:58 2012 (502E55A2)
AtihdW76.sys                Thu Feb 14 17:11:09 2013 (511D60FD)
atikmpag.sys                Thu Mar 28 21:09:45 2013 (5154E9D9)
atikmdag.sys                Thu Mar 28 22:27:04 2013 (5154FBF8)
aswRvrt.sys                 Thu May  9 04:47:02 2013 (518B6286)
aswFsBlk.SYS                Thu May  9 04:47:16 2013 (518B6294)
aswMonFlt.sys               Thu May  9 04:47:23 2013 (518B629B)
aswTdi.SYS                  Thu May  9 04:47:32 2013 (518B62A4)
aswrdr2.sys                 Thu May  9 04:47:41 2013 (518B62AD)
cpuz136_x64.sys             Fri May 10 08:42:51 2013 (518CEB4B)
aswVmm.sys                  Thu Jun 27 11:35:59 2013 (51CC5BDF)
aswSP.SYS                   Thu Jun 27 11:37:21 2013 (51CC5C31)
aswSnx.SYS                  Thu Jun 27 11:37:25 2013 (51CC5C35)
[/font]

Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
aswrdr2.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
Link Removed
Link Removed
Link Removed
Link Removed