New
#11
I have updated both drivers. Tried loading Pro Tools again with Mbox mini plugged in, still BSOD. attached is the new dump. I'm going to do some more research on my end to see if maybe I can't load while the Mbox is plugged in?
Months of system being fine, sudden multiple BSODs this morning
-
-
New #12
My other thought would be completely removing the avid software and then trying to re-install it because the diginet.sys driver doesnt seem to be causing the problem any more its just the anti-piracy software that seems to be acting up, perhaps a fresh install of the program will help.
-
New #13
Alright. Updated both drivers to latest releases. Still getting BSOD on loading of Pro Tools. Uninstalled Pro Tools entirely and re-installed it, still getting BSOD. Also got another BSOD on startup of machine. Attached is the most recent dump file, hopefully something new is in here.
I honestly cannot remember what I did to cause all of this with my Pro Tools except try loading it up with my pre-amp plugged in. Ever since, I can't even start it up without my pre-amp attached...
Unless you're able to find anything new, I think I'm just going to call Avid tech support. Perhaps they've seen this before.
-
New #14
Unfortunately the dumps are still blaming the Tpkd.sys I think speaking to the Avid Tech support would be best because the Driver causing the BSOD is prat of their anti-piracy software that seems to be causing the problem.
-
New #15
Okay. I was on the phone with tech support for almost two hours. We tried uninstalling, reinstalling, the whole shebang. Nothing worked. He didn't think it was caused by the pace software because of the point it was crashing in the load-up(it had already been approved by the iLok).
I might still have Driver Verifier enabled, I'll double check that. Did some searching, enabled DEP and now my system doesn't crash anymore with ProTools. Instead, the program just closes because it cannot open. It gets stuck on the plugin screen, so I might try uninstalling all those or disabling them. Thoughts??
-
New #16
If they are reliably crashing every time you use them it sounds like then uninstalling or disabling would be a good idea as they will only be taking up space on your hard drive and not be getting used.
-
New #17
FIXED! I honestly am not sure how, but here's what I did.
Noticed there was an update to Protools (10.3.3). Downloaded it. Disabled DEP because Pro Tools requires it to at least be disabled to run. However everything I read suggests that 64-bit systems cannot disable DEP. Tried it anyways through command line. Restarted machine, opened Pro Tools like a champ! Thanks for all the support!!
-
Quote
Related Discussions