Quicken 2016 Turns Screen Black

I'm running Quicken 2016 R6 under Windows 10. I have a two monitor setup and I have Quicken autostarting on the second screen.

I've had a minor variation of this problem for a week or two, but today it started becoming major; it was fine early this morning when I did my usual OSU, but the problem began later. With Quicken running, the second screen goes black. Sometimes it stays black; sometimes it flicks on for a few seconds, then goes black again, and continues alternating.

Sometimes I can shut Quicken down from the task bar; sometimes I can't and have to shut it down from Task Manager. If I shut Quicken down, the screen comes back and stays on. I tried rebooting, but that didn't help. I also tried installing the Mondo update and that didn't help either.

I did a Google search on "quicken 2016 black screen," but I couldn't find anything that helped. One suggestion I saw was making a copy of the qdf file and running that, but it didn't help. Another suggestion was disabling my antivirus. I run Kaspersky and I tried disabling it, but that didn't help either.

Anyone know what's wrong and how to fix it?

Reply to
Ken Blake
Loading thread data ...

An update to this question. I tried restoring my Quicken backup from the day before yesterday into the Quicken Data folder and running it. It didn't help--same problem.

Reply to
Ken Blake

Q16 seems to have major display issues. On my system, it is VERY slow to redraw, making the whole program seem slow. Resizing a window can take a few seconds. I've never seen that happen before. It's obviously doing something odd in screen handling, and may be causing issues with your video drivers.

In my case, this is an Win 7 32-bit, Intel Q6600 with an older nVidia

8600GTS and the latest drivers available for it (nVidia seems to have dropped support for this old card.) Q16 is the ONLY program acting like that. The older Q13 (forced upgrade due to sunetting) was fine.
Reply to
Andrew Rossmann

I haven't been having been having any issues with the speed of Quicken, but it certainly seems like an issue with Quicken.

What seems very odd, however, is that the major problems began today, and they are not because of my data, since the problems remain even if I try opening an older backup file.

And as far as I know, there were no updates to Quicken, Windows, the video driver, or anything else between the time this morning when Quicken was fine and the problems began.

Reply to
Ken Blake

Another update. I just tried reinstalling Quicken. It didn't help.

Unless someone here has a solution for me tonight, I'll try calling Intuit tomorrow.

Reply to
Ken Blake

You might try to check Microsoft "Event Viewer" to see if there are any reports in there that might help determine the issue. I was having problems with some Win 8.1 issues and it helped me track down a problem program that was loading. If you don't know how to get to Event Viewer, just do a Windows search. I even created a shortcut on my desktop to make it easier to check. Pay close attend to Critical Error reports.

Reply to
gp

Good suggestion. I just tried it, but it didn't help. I tried two other things this morning, neither of which helped:

  1. Updating the graphics driver
2 Restoring the registry with an ERUNT Backup
Reply to
Ken Blake

For what it's worth, these are the recent errors I found:

  1. Session "Circular Kernel Context Logger" stopped due to the following error: 0xC0000188
  2. The program qw.exe version 25.1.6.5 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel. Process ID: 2628 Start Time: 01d191a90973109b Termination Time: 4294967295 Application Path: C:\Program Files (x86)\Quicken\qw.exe Report Id:
5ef722c1-fd9c-11e5-9c0b-d0509980f189 Faulting package full name: Faulting package-relative application ID:
  1. Session "EventLog-AirSpaceChannel" stopped due to the following error: 0xC0000188
  2. The description for Event ID 56 from source Application Popup cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

ACPI

5

the message resource is present but the message is not found in the string/message table

  1. A timeout was reached (30000 milliseconds) while waiting for the Sync Host_85528 service to connect.

Having tried to run Quicken from a backup. It now starts without blacking the screen and asks me to choose the file it should open. But as soon as I click on the choice of browsing for a file, it blacks the screen.

Reply to
Ken Blake

It's not exactly fixed, but I found a workaround and I'm back in business.

I moved the Window from the second monitor so that a quarter inch or so of it is on the first screen. The problem disappeared.

I'd still like to find out what was wrong, and what I can do to run it entirely on the second screen

Reply to
Ken Blake

What is your screen resolution (or resolutions per screen.) I wonder if some bug has been triggered causing some form of overflow or other error.

Reply to
Andrew Rossmann

1920 x 1080. But that's on both monitors and the problem occurs only on one of them.
Reply to
Ken Blake

And the problem occurs only if Quicken is running on that screen. Other programs are fine.

Reply to
Ken Blake

It's a Hi-Resolution issue. Q can't handle them.

Reply to
danbrown

Thanks, but the resolution is the same on both monitors, and if you've followed the thread, you'll see that I now have it working on the other monitor.

Reply to
Ken Blake

I just noticed that although the resolution is the same on both monitors, the monitor that Quicken had a problem with is set to 125% (the other monitor is 100%). Might that be the issue?

Reply to
Ken Blake

Wow! I've been reading your thread. It looks as though this is the problem. Could be finicky enough to cause the problem.

Reply to
tconway

I hadn't remembered the 125% setting until just before I sent the message. I don't know for sure, but that could be it.

Reply to
Ken Blake

Even though I had moved Quicken to the other monitor, it happened again this afternoon (on the 125% monitor, not the one now running Quicken). So the problem seems to have nothing to do with Quicken.

I reset the 125% monitor to 100% and I'm planning on leaving it there. I hope that's the end of the problem.

Reply to
Ken Blake

I rest my case.

Reply to
danbrown

I could have spent days on this. Thank you.

Reply to
itvguy2000

BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.