BSOD while doing nothing, error 0x0000003b/0x0000000a

Hello, vejolkk and welcome to the forums. I will try to help you with this. This is what one dump file said, the other one gave little info.

Code:

BugCheck 3B, {c0000005, fffff80002e518e3, fffff88008d9ad50, 0}
Probably caused by : memory_corruption ( nt!MmCleanProcessAddressSpace+f7 )
Followup: MachineOwner

Please Run Memtest86+

   Information

Please download from this site only http://www.memtest.org/ in the middle of the page are the Download links, you can download the ISO.zip or the Auto USB Flash Drive installer.zip

Extract the Zip file. If you chose the ISO image, burn it to a CD using Windows Disk Image Burner or any Image burner you may have. If you downloaded the Auto USB installer, extract it, insert your USB 2.0 Flash Drive and take note of the drive letter. Run the installer, select the Flash Drive Letter, check the format box and press next. It will install memtest86+ to a flash drive. You can use either V4.20 or V5.01. Boot from your selected media. If you use V5.01 it will tell you to press certain buttons at the start, please press no buttons. The test will begin on it's own and continue to run until you stop it. It needs to run for 8 complete passes or until you receive an error. If you receive an error, stop the test. Even 1 error is a fail. Each pass tests a different part of the ram and each of the 10 tests in each pass tests something different. It takes a minimum of 8 passes to completely test the ram, more passes are better. It is quite a long test and will take several hours depending on how much ram you have. Due to the time length it is best to run overnight. If you have any questions, please do not hesitate to ask

Upload the Blue Screen of Death (BSOD) Posting Instructions again and let's see what's going on now.

I also noticed a lot of errors by Pro Tools.exe which is apparently a program from Avid Technology. Can you tell me what that program is and what it is used for?

Also, please run the Long test with Seatools for DOS SeaTools for DOS and Windows - How to Use

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 Disk Check

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.