HELP! Bluescreen!!!

Hi and Welcome

STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL

Usual causes: Device driver
STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control,
STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION

Usual causes: System service, Device driver, graphics driver, ?memory

pctNdis-PacketFilter64.sys is blamed in one of the dump, it is probably PC Tools firewall related drivers. The product must be removed from your system.
Use revo to remove: Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems
After installation, right click on Revo icon, and select "Run as Administrator".

Also, Virtual Cd program such as Deamon tool or Alcohol 120% are known for causing BSODs. If remove PC tool still causing BSODs, please remove Deamon tool completely, then use this tool to remove sptd.sys:
DuplexSecure - Downloads

I can see an exception code ffffffc0000005, memory corruption was blamed in one of the dmp file. Please download third party called memtestx86, burn it to CD using ISO Recorder v3 , and let it run for at least 7 passes

Code:

BugCheck 1000007E, {ffffffffc0000005, fffff80002ad4805, fffff880033e7338, fffff880033e6ba0}

Probably caused by : ntkrnlmp.exe ( nt!ExpInterlockedPopEntrySListFault16+0 )

Followup: MachineOwner
---------
BugCheck 1000007E, {ffffffffc0000005, fffff80002b80d2d, fffff880033e76a8, fffff880033e6f10}

Probably caused by : memory_corruption ( nt!MiLogPageAccess+1bd )

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

BugCheck 3B, {c0000005, fffff80002accfa2, fffff8800a774d20, 0}

Probably caused by : ntkrnlmp.exe ( nt!KxWaitForLockOwnerShip+12 )

Followup: MachineOwner
---------
BugCheck D1, {fffffa8013c26000, 2, 0, fffff880076ef8eb}

Unable to load image \??\C:\Windows\system32\drivers\pctNdis-PacketFilter64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for pctNdis-PacketFilter64.sys
*** ERROR: Module load completed but symbols could not be loaded for pctNdis-PacketFilter64.sys
Probably caused by : pctNdis-PacketFilter64.sys ( pctNdis_PacketFilter64+e8eb )

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

Let us know if you need help

Tuan

you can replace PC tool by Microsoft Security Essential if you need a program to use while not having PC tool
http://www.microsoft.com/security_essentials/

For your second quesstion, I want to quote what Maya producer wrote:

Support for Maya 2010 and Windows 7

Windows 7 is not a tested environment for Maya 2010 products. Please be aware that while nothing may prevent you from using Windows 7 and these products, we may not be able to resolve every issue you encounter at this time.

Maya Station: Support for Maya 2010 and Windows 7


Hope you follow my advise above (remove PC tool, Deamon tool, sptd.sys)


Best regard,


Tuan

I double clicked the setup for sptd.sys and just click uninstall right?

Yep, that's right

I did a memtest86 today but was unable to find any errors...

That's good...remember to run at least 7 passes

You have 2 dumps that draw a lot of interest to me since they are both similar and yet different.

Code:

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED    0x1000007e    ffffffff`c0000005    fffff800`02b80d2d    fffff880`033e76a8    fffff880`033e6f10    ntoskrnl.exe    ntoskrnl.exe+176d2d

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED    0x1000007e    ffffffff`c0000005    fffff800`02ad4805    fffff880`033e7338    fffff880`033e6ba0    atapi.sys    atapi.sys+2b7b

Lets give a little background first. Both had 0x1000007e. The part in bold means the crashed occurred in a piece of the memory owned by a driver. The first one says bad ram. The second one says bad hardware. Now as you have said, you completed the memtest with no flaws. So we can conclude the first one was because of hardware/drivers as well. The most common cause is a bug in the driver and least common is faulty hardware. So make sure all your drivers are up to date with Windows 7 64 bit or if unavailable try for Vista 64 drivers. Also, make sure you are running the latest release of directx.

If windows can't detect an updated driver through windows update it'll just tell you the most up to date drivers are installed. Keep this in mind. Start at the top and go down the list to make sure the most recent update has been installed via visiting manufacturers websites.