Frequent Exception 0Xc0000005 (Bt16 64-Bit On Win2008R2) 追蹤

Legacy Poster

Log Name:      Application
Source:        Application Error
Date:          5/24/2016 12:36:28 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      instance-2
Faulting application name: BarTend.exe, version:, time stamp: 0x56d662cc
Faulting module name: ntdll.dll, version: 6.1.7601.23392, time stamp: 0x56eb3625
Exception code: 0xc0000005
Fault offset: 0x0000000000048d84
Faulting process id: 0xfd4
Faulting application start time: 0x01d1b5b8d820d45f
Faulting application path: C:\Program Files\Seagull\BarTender Suite\BarTend.exe
Faulting module path: C:\windows\SYSTEM32\ntdll.dll
Report Id: 2270b74b-21ac-11e6-a1bf-da68843386fd
Event Xml:
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <TimeCreated SystemTime="2016-05-24T12:36:28.000000000Z" />
    <Security />
    <Data>C:\Program Files\Seagull\BarTender Suite\BarTend.exe</Data>

6 意見

Ian Cummings
評論操作 永久連結

I suggest you get in touch with tech-support for your region to help fault find the issue:

評論操作 永久連結

I have the same problem with BT 10.1 SR4. I totally reinstalled BT servers, windows, updated drivers more times, but it still happens. I hate this ENTERPRISE Software.


Faulting application name: BarTend.exe, version:, time stamp: 0x545e78a1
Faulting module name: ntdll.dll, version: 6.1.7601.23864, time stamp: 0x595fa490
Exception code: 0xc015000f
Fault offset: 0x00084269
Faulting process id: 0x448
Faulting application start time: 0x01d32dec729688f1
Faulting application path: C:\PROGRA~2\Seagull\BARTEN~1\BarTend.exe
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id: b0968b01-99df-11e7-ae8f-005056bb08a2


Faulting application name: splwow64.exe, version: 6.1.7601.17514, time stamp: 0x4ce7b4c8
Faulting module name: GDI32.dll, version: 6.1.7601.23807, time stamp: 0x5915fd6c
Exception code: 0xc0000005
Fault offset: 0x000000000000d60d
Faulting process id: 0xa0c
Faulting application start time: 0x01d32d9700e8c0c5
Faulting application path: C:\Windows\splwow64.exe
Faulting module path: C:\Windows\system32\GDI32.dll
Report Id: 3eb900a5-998a-11e7-bb5c-005056bb08a2


I am getting a calls from our warehouse at night because BT is not working again!!!

Ian Cummings
評論操作 永久連結

I suggest you use the Seagull DriverWizard to do a full removal of Seagull drivers, reboot, and then run the wizard again to reinstall the drivers with the latest version from scratch and thus a clean install. This should clear out any driver corruption that could be causing such crashes.

Are you running BarTender in some form of automated process be it Integration Platform or Commander?  If so I suggest you run the printer drivers in shared isolation mode.  In this way drivers run under a sub-process of the Windows spooler which will auto-respawn in the event of a crash.  In this way the spooler system itself won't be brought down by such a crash, and thus would not require an admin to intervene.

To enable this, open up Printer Management from the Administration Tools window of Windows.  Navigate to the drivers section of your print server, select those drivers that are used by BarTender for printing, right click and choose the "Set driver isolation>Shared" menu item.


評論操作 永久連結

Hello Ian! Thank you a lot! I activate driver isolation as you said. I hope it will help.

評論操作 永久連結

Thanks to Ian Cummings! Driver isolation is working ! Bartender is no longer breaks down.

Ian Cummings
評論操作 永久連結

RikoNw: Good to hear.  You might like to know that the next driver release will have driver isolation enabled by default, in addition to a number of other changes and features.