BSOD crashing IRQL

[Eorl]

Hi there, I was just now getting a number of BSOD's in a row, each with the same error message, IRQL_NOT_LESS_OR_EQUAL. Now, I'm not sure what is exactly happening, but I looked around and supposedly it can do with the system overheating. Hopefully someone can give me a hand and help me fix these

System specs:

Win 7 Ultimate x64
Gigabyte GA-890GPA-UD3H Motherboard
AMD Phenom II X4 965 @ 3.4 GHz
4GB DDR3 RAM
Vapor X HD5770 1GB (x2 CrossFire)
LG W43 1920x1080 Display
Antec 650W
Samsung 1TB Spinpoint F3 SATA II 7200RPM 32M


I just very recently upgraded my computer with these new bits of hardware, and a new install of Win 7. So I'm not sure what is actually going wrong.


Attached is BSOD files

 

[ttran]

It can be Memory issue or drivers that cause memory issue. Memory corruption was blamed in the dump. Let's test the Ram first

Please download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.


Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads

BUGCHECK SUMMARY:

BugCheck A, {28, 2, 0, fffff8000331a410}

Probably caused by : memory_corruption ( nt!MiFindNodeOrParent+0 )

Followup: MachineOwner
---------
BugCheck 1A, {5003, fffff780c0000000, 2fc0, 269300005f82}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2a1ef )

Followup: MachineOwner
---------
BugCheck 19, {3, fffff8000345ca70, fffff8000345ca72, fffff8000345ca70}

Probably caused by : Pool_Corruption ( nt!ExFreePool+536 )

Followup: Pool_corruption
---------
BugCheck A, {28, 2, 0, fffff80003310410}

Probably caused by : memory_corruption ( nt!MiFindNodeOrParent+0 )

Followup: MachineOwner
---------
BugCheck 1E, {ffffffffc0000005, fffff880041864e2, 0, ffffffffffffffff}

Unable to load image \SystemRoot\System32\Drivers\sptd.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for [COLOR=Red]sptd.sys[/COLOR]
*** ERROR: Module load completed but symbols could not be loaded for [COLOR=Red]sptd.sys[/COLOR]
Probably caused by : usbohci.sys ( usbohci!OHCI_ProcessDoneAsyncTd+1d5 )

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

Run system files check please:

Open an elevated command prompt and enter sfc /scannow.

Let us know if you need help

Tuan

 

[Eorl]

Ta mate, uninstalled Daemon tools, and did RAM check, everything is running smoothly now

 

[ttran]

Good! Thanks for reporting back! Let us know if you need more help
Run system file check if you have time:
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html