Several BSOD with different errors

Hello.
Last night when I was playing Battlefield 3, the game crashed and right after it the first BSOD occured. When I started the game for 2nd time, it happened again after few minutes of gameplay. And so did for the 3rd time.
I also updated the AMD graphic drivers.

Then I had problem getting back into windows, but after some tries I got in.
But the BSOD still happened few more times.
I also tried windows update(since it popped up that there are updates), but even there 2 updates kept failing to update.

Last time it errored I was scanning for viruses with AVG. For now its running normally, but I have yet to test it with BF3 again.

Right now im also running extended disk test, since my friend recommended it.

So I would like your help with this issue.

System specs:

Windows 7 Ultimate x64
AMD Phenom II X6 1055T Processor
Asus Motherboard
8Gb
ATI Radeon HD 5770
WD 800 GB

Tried running BF3 to see if the problem "magically" went away, but no luck :/
BSOD again, attaching new dump file
Also, noticed that AVG gave me some error. Could it be AVG causing all this, or is just being affected? Attaching the screenshot too.

Remove AMD Overdrive. It is known to cause instability on systems.


Your crashes primarily indicate hard disk problems. This could mean 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 but the advanced tests with SeaTools for 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.

Thank you for the reply.

As I dont have much time today and over the weekend I only ran sfc /scannow. I ran it 4 times and it couldn't fix the error. Im attaching the details file.

I already did memtest yesterday (only 1 pass, since I couldnt afford downtime on the pc.. exams and stuff :/), and it didnt give any errors. I will run a longer test in few days when I get back home.

All SeaTools tests passed, except extended test which would take too long.

Also did Disk Check about twice after the BDOS.
I will run rest of the tests when i get back home(on sunday probably). Again, thank you for your time, and i'll post back asap. Now I gotta hurry and catch the train. o/

Here are some dskchk logs:

1:
Log Name: Application
Source: Microsoft-Windows-Wininit
Date: 14.6.2012 14:06:29
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: powha-PC
Description:


Checking file system on C:
The type of the file system is NTFS.


One of your disks needs to be checked for consistency. You
may cancel the disk check, but it is strongly recommended
that you continue.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 3)...
392704 file records processed.

File verification completed.
1687 large file records processed.

0 bad file records processed.

2 EA records processed.

60 reparse records processed.

CHKDSK is verifying indexes (stage 2 of 3)...
481552 index entries processed.

Index verification completed.
0 unindexed files scanned.

0 unindexed files recovered.

CHKDSK is verifying security descriptors (stage 3 of 3)...
392704 file SDs/SIDs processed.

Cleaning up 103 unused index entries from index $SII of file 0x9.
Cleaning up 103 unused index entries from index $SDH of file 0x9.
Cleaning up 103 unused security descriptors.
CHKDSK is compacting the security descriptor stream
44425 data files processed.

CHKDSK is verifying Usn Journal...
35386528 USN bytes processed.

Usn Journal verification completed.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.

269306879 KB total disk space.
150912816 KB in 339704 files.
154280 KB in 44428 indexes.
0 KB in bad sectors.
502743 KB in use by the system.
65536 KB occupied by the log file.
117737040 KB available on disk.

4096 bytes in each allocation unit.
67326719 total allocation units on disk.
29434260 allocation units available on disk.

Internal Info:
00 fe 05 00 8c dc 05 00 da 37 09 00 00 00 00 00 .........7......
67 b3 00 00 3c 00 00 00 00 00 00 00 00 00 00 00 g...<...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Windows has finished checking your disk.
Please wait while your computer restarts.

2:
Log Name: Application
Source: Microsoft-Windows-Wininit
Date: 13.6.2012 23:43:04
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: powha-PC
Description:


Checking file system on C:
The type of the file system is NTFS.


One of your disks needs to be checked for consistency. You
may cancel the disk check, but it is strongly recommended
that you continue.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 3)...
The record length 0x4d70 is too large for attribute of type 0x30
and instance tag 0x2 in file 0x393e4. The maximum value is 0x98.
Truncating badly linked attribute records
from file record segment 234468.
392704 file records processed.

File verification completed.
1659 large file records processed.

0 bad file records processed.

2 EA records processed.

60 reparse records processed.

CHKDSK is verifying indexes (stage 2 of 3)...
Unable to locate the file name attribute of index entry oem25.CAT
of index $I30 with parent 0x924 in file 0x393e4.
Deleting index entry oem25.CAT in index $I30 of file 2340.
488836 index entries processed.

Index verification completed.
CHKDSK is scanning unindexed files for reconnect to their original directory.
0 unindexed files scanned.

CHKDSK is recovering remaining unindexed files.
1 unindexed files recovered.

CHKDSK is verifying security descriptors (stage 3 of 3)...
Replacing invalid security id with default security id for file 234468.
392704 file SDs/SIDs processed.

Cleaning up 1223 unused index entries from index $SII of file 0x9.
Cleaning up 1223 unused index entries from index $SDH of file 0x9.
Cleaning up 1223 unused security descriptors.
Security descriptor verification completed.
Inserting data attribute into file 234468.
48068 data files processed.

CHKDSK is verifying Usn Journal...
The USN Journal length 0x20ae0d838 in file 0xe106 is less the
largest USN encountered, 0xd00ead04b60, plus eight in file 0x393e4.
Repairing Usn Journal $J data stream.
CHKDSK is resetting Usn information...
Usn Journal verification completed.
Correcting errors in the master file table's (MFT) BITMAP attribute.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.

269306879 KB total disk space.
146878860 KB in 336448 files.
152076 KB in 48069 indexes.
0 KB in bad sectors.
472599 KB in use by the system.
65536 KB occupied by the log file.
121803344 KB available on disk.

4096 bytes in each allocation unit.
67326719 total allocation units on disk.
30450836 allocation units available on disk.

Internal Info:
00 fe 05 00 0f de 05 00 75 2a 09 00 00 00 00 00 ........u*......
8d ac 00 00 3c 00 00 00 00 00 00 00 00 00 00 00 ....<...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Windows has finished checking your disk.
Please wait while your computer restarts.

The file that could not be fixed is imageres.dll; you should try to replace it manually following the steps in OPTION THREE of SFC /SCANNOW Command - System File Checker and the tip within that option.


You also need to run a second disk check. The above showed that Windows made corrections to the file system.

When I got back, I started the pc, but after getting into windows it crashed. Then i kept getting bsod until i removed the stick of RAM (4gb, that i bought about 2-3 months ago).

I replaced the file (that friend sent to me) but i still get the error when I do sfc /scannow.

I tried running dskchk again, but I get error saying something like "dskchk cannot open volume for direct access .... use system restore ....". Didnt exactly see what it said as it goes away quickly. There is no new logs regarding that in event viewer(unless its stored somewhere else).

The fact that disk check will not run means there is corruption of the disk check capability. I have seen this happen on my own systems. You have two options:

• Chkdsk will Not Run at Startup in Vista - Vista Forums which may or may not work (I have never tried in Windows 7, but Brink believes it should work the same in 7 as in Vista).
  
  
• You will need to Repair Install Windows 7.
  
  Steps 1-3 and 5-7 of Clean Reinstall - Factory OEM Windows 7 will help you get installation media, backup any important files (just in case), and obtain your license keys for software (just in case) and the Windows license key (you will need this key).

I got new stick of RAM now, and everything is running smoothly. I will still have to do a repair install(or maybe format :3)to fix the corrupted files, but BSOD seems to be resolved.
Thank you for your help.

You're welcome. I am very happy to see the problem solved.