Hi, vejolkko. No, I can's say that Pro Tools is causing your BSODs, but I can say the program is throwing a lot of errors. That can't help. Your latest dump file does not help much.
Code:
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000008, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002eae861, address which referenced memory
I would like to try a few things.
Please run Check disk on all Mechanical Hard drives
http://www.sevenforums.com/tutorials/433-disk-check.html
Please run these online Virus Scanners
Scan with Kaspersky TDSSKiller:
Anti-rootkit utility TDSSKiller
Anti-rootkit utility TDSSKiller
ESET online scanner:
Free Virus Scan | Online Virus Scanner from ESET
Free Online Virus Scanner | ESET
Also download and install Superantispyware, the free version and do a complete scan
SUPERAntiSpyware | Remove Malware | Remove Spyware - AntiMalware, AntiSpyware, AntiAdware!
Also, please open an elevated command prompt ( click start, type
cmd in the search box,
right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste
sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.
If we don't get some promising results from any of these, I would like to run a test. There is a chance that you may have to do a clean install. We take every precaution to make sure that does not happen. I have yet to have it happen with me, but there is always the chance. But, lets hope we get some good results with these tests.
When you ran the long test with Seatools, Did you run all of you hard drives? In the dump files, I keep seeing a lot of NTFS errors and filter manager which usually relate to the hard drive or the file system. The BSODs do not blame the Hard Drives, but the errors are there and is usually a clue.