• 0

Visio 2013 crashing when printing


Question

Im having a issue with printing in Visio 2013 crashing when im printing to a xerox printer, i have updated the printer drivers and have also deleted and re added the pritners, happening on all visio documents, crashes 8 out of 10 attempts, no addons running, done all office 2013 updates as of 5/12/13, started visio in safemode and still crashed, crash report below -

 

Log Name:      Application
Source:        Application Error
Date:          5/12/2013 3:43:35 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      ********************
Description:
Faulting application name: VISIO.EXE, version: 15.0.4535.1507, time stamp: 0x52282a2a
Faulting module name: VISLIB.dll, version: 15.0.4535.1507, time stamp: 0x52282928
Exception code: 0xc0000005
Fault offset: 0x005a9861
Faulting process id: 0x1bbc
Faulting application start time: 0x01cef1748bdf2a28
Faulting application path: C:\Program Files\Microsoft Office\Office15\VISIO.EXE
Faulting module path: C:\Program Files\Microsoft Office\Office15\VISLIB.dll
Report Id: cc95bd42-5d67-11e3-941b-002564d9fad3
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-12-05T04:43:35.000000000Z" />
    <EventRecordID>59089</EventRecordID>
    <Channel>Application</Channel>
    <Computer>**************</Computer>
    <Security />
  </System>
  <EventData>
    <Data>VISIO.EXE</Data>
    <Data>15.0.4535.1507</Data>
    <Data>52282a2a</Data>
    <Data>VISLIB.dll</Data>
    <Data>15.0.4535.1507</Data>
    <Data>52282928</Data>
    <Data>c0000005</Data>
    <Data>005a9861</Data>
    <Data>1bbc</Data>
    <Data>01cef1748bdf2a28</Data>
    <Data>C:\Program Files\Microsoft Office\Office15\VISIO.EXE</Data>
    <Data>C:\Program Files\Microsoft Office\Office15\VISLIB.dll</Data>
    <Data>cc95bd42-5d67-11e3-941b-002564d9fad3</Data>
  </EventData>
</Event>

Link to comment
https://www.neowin.net/forum/topic/1191407-visio-2013-crashing-when-printing/
Share on other sites

12 answers to this question

Recommended Posts

  • 0

as mentioned there are no addons and no bluetooth enabled, thats why i started visio in safemode

 

Use a PS (post script) or PCL driver?  PCL 5 or PCL 6?

 

We use PS drivers for lots here at my work since PCL doesnt always print pics/projects properly.  I have also seen when using a PCL 6 drive will cause issues while PCL5 works fine.

 

Also, does printing to another printer work?  Or printing the files from a different PC?

  • 0

This might sound crazy, but it in the advanced print bit its 22:54 here my brain is not 100%! But try disable the advanced printing features just to see if that fixes it. It has sorted some issues for me before.

 

disabled advanced printing and hardware accelleration

 

  Problem Event Name:    APPCRASH

  Application Name:    VISIO.EXE

  Application Version:    15.0.4535.1507

  Application Timestamp:    52282a2a

  Fault Module Name:    VISLIB.dll

  Fault Module Version:    15.0.4535.1507

  Fault Module Timestamp:    52282928

  Exception Code:    c0000005

  Exception Offset:    005a90da

  OS Version:    6.1.7601.2.1.0.256.4

  Locale ID:    3081

Additional information about the problem:

  LCID:    1033

  skulcid:    1033

  • 0

After doing some looking around, and prob seeing what you already have. Have you tried this?

 

"I'm was crashing as well as soon as I hit the print dialog.  I disabled the "Send to Bluetooth" add-on, but still crashed.  The problem might have something to do with selecting different themes.  I was using the "Parallel" theme and crashing, them flipped back to the standard Office 2013 theme and was able to bring up the print dialog.  I then switched all my pages back to "Parallel" and can now print."

  • 0

After doing some looking around, and prob seeing what you already have. Have you tried this?

 

"I'm was crashing as well as soon as I hit the print dialog.  I disabled the "Send to Bluetooth" add-on, but still crashed.  The problem might have something to do with selecting different themes.  I was using the "Parallel" theme and crashing, them flipped back to the standard Office 2013 theme and was able to bring up the print dialog.  I then switched all my pages back to "Parallel" and can now print."

no themes are selected just the default theme.

  • 0

Try one of 2 things.

 

First copy the VISLIB.dll from a known good computer into the one with the errors.

If that doesn't work, replace the memory in the computer.  Or if you can't replace it, hopefully it has more than one stick, try alternating sticks.  Yeah sounds weird.  But I had the SAME EXACT issue 2 weeks ago.  There was a bad memory slot on the motherboard.  Changed memory from slots 1 and 3 to 2 and 4 and been fine ever since.

This topic is now closed to further replies.
  • Posts

    • It depends on how technical of an answer you want. Does it stop manufacture drivers? Yes, the universal driver is the only thing that interfaces with the printer hardware. However, print support apps (PSAs) are the new way to provide that functionality you speak of. They integrate directly into the print dialog box just like the older model, so the user doesn't see any difference at all*. This is nothing new...this has been the preferred way to do print drivers for almost 8 years! The only thing changing here is that the older printer model drivers of the past are being deprecated. I highly suspect that you yourself have installed a print support app described as a driver package from the manufacture's support page, had it work exactly as expected, without realizing it was using the universal IPP driver under the covers. For example, USB keyboards have all used the generic HID driver for just about as long as they have existed, but that doesn't stop manufacture "drivers" from enabling more features. *bit of a disclaimer: the PSA process doesn't require the user to see anything different, but in many cases the manufacture v1.0 PSA "drivers" were pretty basic and lacked the polish of their older V4 print model driver brothers.
    • https://www.neowin.net/news/microsofts-captionbot-will-try-to-caption-any-picture---as-long-as-hitlers-not-in-it/ The early days of "AI"!
    • Wow..... 1.8GB of RAM usage. That's just a bit more than MS Teams or VS Code uses.
    • its slower than ever. especially on mobile ios. really poor app. Slack is a million times better. shame the company i work for moved from Slack to teams few years back. was like moving from 2026 to windows ME.
  • Recent Achievements

    • One Month Later
      Sopa flores earned a badge
      One Month Later
    • First Post
      StaticMatrix earned a badge
      First Post
    • Week One Done
      StaticMatrix earned a badge
      Week One Done
    • Rookie
      lamborghiniv10 went up a rank
      Rookie
    • One Month Later
      pinnclepd earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      531
    2. 2
      PsYcHoKiLLa
      209
    3. 3
      +Edouard
      156
    4. 4
      Steven P.
      98
    5. 5
      ATLien_0
      82
  • Tell a friend

    Love Neowin? Tell a friend!