BSOD shortly opening Adobe InDesign error x019

[ryanmPITH]

This one has really stumped me, but I'm hoping the experienced users here can help.

I'm running 10 HP Z420's at my video production facility. They usually run fine. I installed Adobe CC on one system awhile back, got some BSOD's on launch of InDesign. Somehow resolved it, but I can't for the life of me remember.

Months later, on an identical machine which has never been connected till the internet till very recently. I'm having the same issue again, but can't seem to track down a solution.

Here's the things I've tried, which yielded no results:

driver verifier
sfcscan
downloaded malwarebytes and MSE
I checked all drivers vs the other system that has working InDesign, they're the same.

I'm aware my video driver is out of date, but I need to use AVID certified drivers, and the other system has the same drivers and is fine.


x019 is the most recent error, but I've gotten a wide range of them, ALL from when I open InDesign.


Any ideas? Thanks!

 

[essenbe]

Hello ryanmPITH, welcome to Seven Forums. I will try to help you if I can. I have not looked at all of your Dump files but did look at the last 8 or 9. They mostly had different errors and listed different causes, which I will show you below.

BugCheck 19, {3, fffffa801c750e40, fffffa801c750e40, 726f70726f636e49}
*** WARNING: Unable to verify timestamp for e1e6232e.sys
*** ERROR: Module load completed but symbols could not be loaded for e1e6232e.sys
Probably caused by :[COLOR=red] Pool_Corruption[/COLOR] ( nt!ExDeferredFreePool+c96 )

e1e6232e
start             end                 module name
fffff880`0798f000 fffff880`079db000   e1e6232e T (no symbols)           
    Loaded symbol image file: e1e6232e.sys
    Image path: \SystemRoot\system32\DRIVERS\e1e6232e.sys
    Image name: e1e6232e.sys
    Timestamp:        Tue Oct 30 04:19:42 2012 (508F9BAE)
    CheckSum:         0004CD07
    ImageSize:        0004C000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Which is your Intel(R) PRO/1000 PCI Express Network Connection Driver and can be updated from http://downloadcenter.intel.com/Default.aspx

e1c62x64
start             end                 module name
fffff880`08600000 fffff880`0865b000   e1c62x64 T (no symbols)           
    Loaded symbol image file: e1c62x64.sys
    Image path: \SystemRoot\system32\DRIVERS\e1c62x64.sys
    Image name: e1c62x64.sys
    Timestamp:        Wed Jan 11 14:30:54 2012 (4F0DF17E)
    CheckSum:         0005BBF4
    ImageSize:        0005B000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Which is your Intel(R) 82579V Gigabit Network Connection driver

Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff80003381c9f, fffff8800d27ab50, 0}
Probably caused by : [COLOR=red]memory_corruption[/COLOR] ( nt!MiIdentifyPfn+26f )
Followup: MachineOwner

 nvlddmkm
start             end                 module name
fffff880`08608000 fffff880`090a6000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Sat Dec 29 00:47:52 2012 (50DE9218)
    CheckSum:         00A7F96C
    ImageSize:        00A9E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Which of course is your graphics card drivers

AvidFos
start             end                 module name
fffff880`0e2d0000 fffff880`0e384000   AvidFos  T (no symbols)           
    Loaded symbol image file: AvidFos.SYS
    Image path: \SystemRoot\System32\Drivers\AvidFos.SYS
    Image name: AvidFos.SYS
    Timestamp:        Mon Dec 10 23:55:11 2012 (50C6CABF)
    CheckSum:         000A9792
    ImageSize:        000B4000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

There was one other one which I found an Avid PDF about but little else, in a quick search.

fsdk-wrap.sys

I think you can see they were mostly different stop codes and different drivers.

I may suggest you update the 2 Intel Network drivers since they were mentioned twice. The fact that we are getting different stop codes and different reasons leads me to believe the one which says Memory Corruption. Ofthen memory corruption will cause exactly that. So, I'm going to suggest you run memtest86+ first. Due to the reason I mentioned as well as the fact that memory corruption can make everything we get in the debugger not correct, I would do that first. This will tell you how to do it. I know what a pain it can be, I've been there myself too many times. But, I think it is necessary.

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.

If you don't understand the instructions or have any questions, don't hesitate to ask. I don't mind explaining myself at all or the instructions. I realize the time this test takes, and can appreciate you not wanting to take the time, but I really think this is needed. It has to run a minimum of 8 passes all at one time, more is better. That is what it takes for a complete test.​

 

[ryanmPITH]

Hi Essenbe, thank you for your well thought out response!


I unfortunately haven't had a chance to run memtest yet, due to the constant usage of this machine. Also, the issue I have with updating the Intel drivers, is that only specific drivers are supported by our AVID servers, so I wouldn't want to break anything by updating to an "unsupported" driver.


Unfortunately, I'm not expecting much from the memtest results anyway, as I had this exact issue on an identical machine which is now resolved. The main issue was an 0x04A error, which was allegedly resulting from ASPI.sys.

I think getting these new, different stop errors is a result of my attempt to fix it by disabling ASPI32 in the registry. I've restored the default entries for that registry and I'm back to the 0x04A drivers on this machine. I believe the earlier .dmps will reflect my current crashes more accurately.

I hope I'm wrong and it is as simple as replacing the memory modules, and I will update when I'm finally able to run memtest. Again, thanks so much for your time. If you think of anything else in the meantime, let me know!

Best,

Ryan

 

[essenbe]

Would it be too much for you to explain the AVID servers to me. I am not at all familiar with the name and this is maybe more of a curiosity question, but it seems to me that they have to be a major pain. Your computer has to have drivers for the hardware to function properly, but you can't update it because of the AVID Servers. That seems like two competing forces which is doomed to failure, either way. Am I wrong? Windows 7 is an excellent system, if a piece of hardware starts malfunctioning, it will shut down to keep the computer from being damaged. That can be caused by malfunctioning hardware or by a bad driver which causes a piece of hardware to act unexpectedly. What I see on y end, without knowing about the AVID, is that you are afraid to update hardware drivers for fear of it not being compatible with the AVID software, but at the same time, it is possible, that it is causing you a lot of downtime because the computer is crashing. That may not be true at all, but it is what it seems to me. I do understand your concerns, but they seem to be competing forces to me. would it be possible for you to explain that to me, whenever you get time? To me, it seems as we always say you're 'between a rock and a hard place'.

 

[ryanmPITH]

Would it be too much for you to explain the AVID servers to me. I am not at all familiar with the name and this is maybe more of a curiosity question, but it seems to me that they have to be a major pain. Your computer has to have drivers for the hardware to function properly, but you can't update it because of the AVID Servers. That seems like two competing forces which is doomed to failure, either way. Am I wrong? Windows 7 is an excellent system, if a piece of hardware starts malfunctioning, it will shut down to keep the computer from being damaged. That can be caused by malfunctioning hardware or by a bad driver which causes a piece of hardware to act unexpectedly. What I see on y end, without knowing about the AVID, is that you are afraid to update hardware drivers for fear of it not being compatible with the AVID software, but at the same time, it is possible, that it is causing you a lot of downtime because the computer is crashing. That may not be true at all, but it is what it seems to me. I do understand your concerns, but they seem to be competing forces to me. would it be possible for you to explain that to me, whenever you get time? To me, it seems as we always say you're 'between a rock and a hard place'.

To begin my reply, I'd just like to say I believe I've fixed the problem! I will explain what I did at the bottom of the post.

Now, let me briefly explain our AVID system.

The second floor of our office contains a environmentally controlled server room with 10 edit stations, and two ISIS 32TB chassis in RAID 5. They're upstairs for insurance reasons, mainly in the case of flooding due to our location. On this 64TB total server, we store our high resolution transcoded video, projects and other various media. We have Avocent KVM's and Blackmagic switchers running down to our edit suites.

We edit solely on AVID Media Composer. AVID does extensive hardware, software, and driver testing to ensure optimal performance. They certify drivers based on what version of MC you are running. We aren't running the newest version, mainly because this version works fine. This is why we are using older drivers, as well as HP Z420's, as they are certified to run AVID. You need to be using specific hardware for AVID to provide you support.

Now, onto the solution to my problem. I know others have been having this same problem, but I haven't found anyone with a solution that works. I fixed it on my old machine as well, but this isn't what I did. I can't remember how I fixed it then, unfortunately.

I knew that in my BSOD 0x04A errors, ASPI.sys was blamed for the crash. I found someone else had a problem with something similar, and someone recommended they use autoruns.exe to disable a certain driver. I downloaded autoruns.exe from a website, but unfortunately I can't find that link. (If anyone is having this problem, and needs this fix, I can provide the executable for you). I disabled ASPI.sys via autoruns.exe, as it says it was not found anyway. It's too early to confirm, but I haven't had a crash since and I can now work in InDesign.

It's strange, as I disabled this already via regedit, but when it didn't work and caused other stop codes, I reverted it's start code to 1.

I can't really explain why this worked, or why ASPI.sys was being called in the first place, as I don't have that file on my system. I hope this solution helps someone else in the future, and I hope you have a better understanding of why I have to sadly run old drivers.

Thanks again for all your help!

Best,
Ryan

 

[waylandprod]

It's the Isis Client Manager--

We've run into the same error at my institution running Avid Isis as well. It looks like there's a conflict between Indesign and Avid Isis client software, not sure the fix yet. (BSOD at AvidFOS.sys)

I isolated the software conflict to those two bits of software which is what led me here. If I find a resolution I'll report back.

 

[waylandprod]

I know I might be just talking with myself, but in case you're still trying to find a fix, you can create a .bat file that kills the previous conflicting tasks to be run before Indesign:

net stop AvidFosFS
net stop Avid ISIS Benchmark Agent
taskkill /IM BenchmarkAgent.exe /F
taskkill /IM AvidFos_Service.exe /F
taskkill /IM IsisClientManager.exe /F
taskkill /IM AvidBackgroundServicesManager.exe /F
taskkill /IM AvidAppManHelper.exe /F
taskkill /IM AvidEditorDbEngine.exe /F
taskkill /IM AvidEditorMSE.exe /F
taskkill /IM AvidEditorTranscodeStatus.exe /F

Not all of those might be causing the conflict, but I just lumped them all together to make it easier. Right now we're testing whether install order might fix the error. If not, we'll built a .bat file and make a fake link on the desktop so it works without user knowledge.

 

[ryanmPITH]

waylandprod, not sure if you're still reading this, but have you made any progress with this? The issue has recently started again on my system and I'm at a loss...

 

[waylandprod]

Yes, there is a workaround, but it's not the best. What I was forced to do is install a program called "Sandboxie" and then have Indesign run inside it's own sandboxed environment and not let it have access to the network that causes both softwares to crash. I also had to swap out all the shortcuts as well, but it worked. The students have to save on the desktop, but that's not a big deal. We made some documentation and it seems to be working just fine. Printers still work, and that's all we needed. Hope that helps.