Verified Answers

If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it! Learn more

  • State Not Answered
  • Replies replies
    8
  • Subscribers subscribers
    4
  • Views views
    240
  • Users 0 members are here
  • Locked Locked
Related
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Windows 7 blue screen

Ken Etter
I have a 32 bit app that works fine in Windows XP, but doesn't work in
Windows 7 64 bit. Created a virtual version of it. The ZAV version
works great in Win7 64bit except printing to our PDF driver causes a
blue screen. I can print to our iPrint printers without problem. I'm
new to ZAV. Any suggestions for how to troubleshoot this?

Thanks,
Ken
Parents
  • 0
    What is the blue screen code you're getting? Are there any errors in the event logs?

    It seems a bit odd that any virtualized app would cause a blue screen.
  • 0 in reply to 
    On Wed, 16 Jan 2013 14:56:02 GMT, zeevromm
    <zeevromm@no-mx.forums.novell.com> wrote:

    >
    >What is the blue screen code you're getting? Are there any errors in
    >the event logs?
    >
    >It seems a bit odd that any virtualized app would cause a blue screen.

    But I can make it happen without fail.

    Found this in the event log:
    The computer has rebooted from a bugcheck. The bugcheck was:
    0x00000050 (0xfffff900c3200000, 0x0000000000000000,
    0xfffff9600025e328, 0x0000000000000002).

    I created a debug version of the app and found this in one of the
    logs:
    0x0B74, 0xB875A:ERROR: 0xD000003A, Unable to open file the startup
    module: \DEVICE\HARDDISKVOLUME2\Program Files (x86)\Tracker
    Software\PDF-XChange Lite 4\pdfSaver4l.exe.

    That is the PDF driver we are using. The driver works great on both
    XP and Win7. And it works fine with the application on XP. But if I
    try to print using the application as a virtual app on Win7, a blue
    screen is guaranteed.
Reply
  • 0 in reply to 
    On Wed, 16 Jan 2013 14:56:02 GMT, zeevromm
    <zeevromm@no-mx.forums.novell.com> wrote:

    >
    >What is the blue screen code you're getting? Are there any errors in
    >the event logs?
    >
    >It seems a bit odd that any virtualized app would cause a blue screen.

    But I can make it happen without fail.

    Found this in the event log:
    The computer has rebooted from a bugcheck. The bugcheck was:
    0x00000050 (0xfffff900c3200000, 0x0000000000000000,
    0xfffff9600025e328, 0x0000000000000002).

    I created a debug version of the app and found this in one of the
    logs:
    0x0B74, 0xB875A:ERROR: 0xD000003A, Unable to open file the startup
    module: \DEVICE\HARDDISKVOLUME2\Program Files (x86)\Tracker
    Software\PDF-XChange Lite 4\pdfSaver4l.exe.

    That is the PDF driver we are using. The driver works great on both
    XP and Win7. And it works fine with the application on XP. But if I
    try to print using the application as a virtual app on Win7, a blue
    screen is guaranteed.
Children

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.