Comment 1 for bug 1520583

on Nov 24-27 I log in 15.10 Wily 1 T Western Digital produced the following note, which hasn't been solvable; I don't see a way to restore bug's behavior; amid this posting on 11-27th 8am cst, the flicker error pest took over; it close the monitor then w/mouse clicks, the screen achieved sanity, allowing me to post this sentence and hopefully more info below.

immediately after booting OS says: "Could not apply the stored configuration for monitors
none of the selected modes were compatible with the possible modes:
Trying modes for CRTC 63
CRTC 63: trying mode 1440x900@60Hz with output at 1280x1024@75Hz (pass 0)
CRTC 63: trying mode 1440x900@60Hz with output at 1280x1024@75Hz (pass 1)
Trying modes for CRTC 64
CRTC 64: trying mode 1440x900@60Hz with output at 1280x1024@75Hz (pass 0)
CRTC 64: trying mode 1440x900@60Hz with output at 1280x1024@75Hz (pass 1)
Trying modes for CRTC 65
CRTC 65: trying mode 1440x900@60Hz with output at 1280x1024@75Hz (pass 0)
CRTC 65: trying mode 1440x900@60Hz with output at 1280x1024@75Hz (pass 1)

earlier -- on 11-25/26th the following was accumulated:
11-27th Bug #1520583 created.
Flicker err bug #1520583 ? Is it anything like a Nvidia bug? My PC's screen looks like a Venetian blind being mismanaged by swift wind. On P5GC-MX, BIOS 0314, 5/27/2007 1510 Wily Ubuntu. A report I can't find says “unable to handle kernel NULL pointer dereference at 000000000000008
Am running 1510 Wily Ubuntu on My used 1 Tbit WD in Mirus PC clone runs a newly installed OS great for hours; then screen flips into a fluttering blind affect mode; and for all practical purposes, during the crash, it looks unmanageable. like it crashes amid a fluttering Venetian blind.

OS can be retrieved if I'm patient but at times I must power off & login. OS did not produce a reportable error/crash description.
What work around could be used to solve/smash bug #1520583?

I'm baffled by bug #1520583.