BSOD on startup not less or equal

Hey, ever since June 3rd, when my computer randomly decided to shut down while browsing the net, I have been getting BSOD's within a few minutes of logging into windows. Currently I am running in safe mode. I have also managed to run a few hours when in disabling driver verification mode. Though that is hit or miss, sometimes it works sometimes it doesnt.

My most common BSOD error is the irql not less or equal message. I have also seen a BAD POOL HEADER message, and PAGE FAULT IN NON PAGED AREA

I originally attempted a system restore that failed. I tried updating drivers. though during a second system restore attempt they probably are no longer updated, but that didnt solve the problem anyway.

I let the memory tester application run last night and it completed 9 passes no errors. I had AVG installed, but after reading another thread thinking that could be a problem I uninstalled it. Tried installing MS security essentials but It wont let me do so in safemode.

A scan with malware bytes resulted with the following: This is a combination of a partial "Full scan" and a quick scan report later.

Registry Keys Infected:
HKEY_CLASSES_ROOT\.fsharproj (Trojan.BHO) -> Quarantined and deleted successfully.

Registry Values Infected:
(No malicious items detected)

Registry Data Items Infected:
HKEY_CLASSES_ROOT\regfile\shell\open\command\(default) (Broken.OpenCommand) -> Bad: ("regedit.exe" "%1") Good: (regedit.exe "%1") -> Quarantined and deleted successfully.

Files Infected:
c:\$Recycle.Bin\s-1-5-21-1327337483-3659072796-1434049381-1000\$R33GMNM.exe (Trojan.FakeAlert) -> Quarantined and deleted successfully.
c:\Users\Jon\AppData\Local\Temp\221B.tmp (Trojan.FakeAlert.SPE) -> Quarantined and deleted successfully.
c:\Users\Jon\AppData\Local\Temp\installmonetizer.exe (Adware.Agent) -> Quarantined and deleted successfully.
c:\Users\Jon\AppData\Local\Temp\~!#9CEE.tmp (Rootkit.Dropper) -> Quarantined and deleted successfully.
c:\Users\Jon\AppData\Local\Temp\~!#ED04.tmp (Trojan.Agent.UAWHGen) -> Quarantined and deleted successfully.

Dump files and system information is attached. Hope you can help.

Problematic Software:

Code:

Start Menu\Programs\Advanced SystemCare 3	Public:Start Menu\Programs\Advanced SystemCare 3	Public
Start Menu\Programs\Smart Defrag	Public:Start Menu\Programs\Smart Defrag	Public

Advanced SystemCare is known to cause problems because over time, it damages Windows and the programs installed.

Smart Defrag may or may not cause issues, but 3rd party defrag tools do sometimes have unforeseen side effects. Some will damage system restore points, and others will cause conflicts with the file system drivers.

• Many of us on the forums actually do not recommend automated optimization tools for Windows 7. Windows 7 does a much better job of handling its own optimization than its predecessors did. We especially do not recommend registry cleaning as an "optimization" step because automated registry cleaning causes more harm to the registry than it actually repairs.
  
  In the future, if you need help optimizing Windows 7, please post a thread in Performance & Maintenance - Windows 7 Forums or follow the tutorial enclosed in that forum to Optimize Windows 7.
  
  
• I do not recommend 3rd party defrag tools. Windows has some nice command line flags for the defrag command that will accomplish the same tasks as 3rd party programs. The -b and -w flags will defrag boot files and the boot registry items as well as compact the data to the center of the disk for faster access.
  defrag c: -b
  defrag -c -v -w
  The first command optimizes boot performance for the Windows drive by defragmenting boot files and boot registry items.
  
  The second command includes all drives on the system through the -c command and optimizes the drives by compacting the data to the center of the disk. Verbose output through the -v option is optional to provide the user with more information about the defrag tasks. The commands have to be run in an Elevated Command Prompt.
  
  For more flags, see Disk Defragmenter - Open and Use.

The following drivers should be updated if possible:

Code:

fffff880`0f048000 fffff880`0f04ea00 ManyCam_x64 ManyCam_x64.sys Thu Mar 13 01:46:01 2008 (47D8DBB9)
fffff880`04b79000 fffff880`04b83980 LVUSBS64 LVUSBS64.sys Sat Jul 26 09:06:36 2008 (488B3D7C)
fffff880`045bf000 fffff880`045fb880 mcdbus mcdbus.sys Tue Feb 24 03:34:07 2009 (49A3CD1F)
fffff880`041c7000 fffff880`041f9000 Rt64win7 Rt64win7.sys Thu Feb 26 02:04:13 2009 (49A65B0D)
fffff880`05639000 fffff880`057e5900 RTKVHD64 RTKVHD64.sys Fri May 22 12:04:20 2009 (4A16E924)

ManyCam_x64.sys - Have seen this cause problems. You may want to look into SplitCam instead.
LVUSBS64.sys
mcdbus.sys
Rt64win7.sys
RTKVHD64.sys



I see some crashes related to your file system drivers. May be due to Smart Defrag. Remove to see if the system is more stable.

I also notice a possible overclock of the CPU. Is this intentional?

Ok, so since you guys were taking a while to respond, I found a thing to review the dmp files myself and saw that it was pointing to ntoskrnl.exe as the problem for every one. So I managed to find a recovery CD download, and copied som drivers and dlls from that to my win directory.
I backed up and copied hal.dll and
ntoskrnl.exe in the system32 folder

and in the drivers folder I replaced acpi, disk, msisadrv, pci volmgr and volsnap
This was based on instructions on another site.

This seems to have worked as I was able to log in just fine, until I tried updating the drivers you suggested. I found a link to the bottom one, RTKVHD64.sys and it uninstalled and rebooted, then It kept crashing again.

I also uninstalled the two programs you mentioned. I'm not sure ive ever used them.


I'm really getting tired of these issues. I have no idea where my win 7 cd is. But I need to fix this computer.

I did manage to get security essentials installed.

Its pinning trojan.DOS/ alureon.A
and Trojan.js/ Tracur. B

It suggest i download windows defender which i did. And i put it on my usb drive, but I cant get it to run on boot.

I ran tdsskiller, and it found something and rebooted. And as of now, my computer is running in normal mode. Lets see how long this last this time. Crossing my fingers.
I'm almost afraid to do anything else.

Alright, let us know if you have other problems before we do anything else. Your caution is noted, so I will not advise until asked.