Windows XP Residual blocky display after program exit

[Silverhazesurfer]

As the title suggests, I am seeing residual graphics from a program that previously was opened. Here's the scenario:

Using DiVis DVR software on Win XP SP3, fully updated.
When the DVR prog is opened, you have the control frame and the video panes for each camera of the DVR. When I open the software, let it idle for a minute and then close it, everything appears fine. If I let it sit there for 10+ mins and close the application, I get purple blocks toward the top of the screen. They stay there until the machine is restarted. *Note: the panes of the DVR are blue, the same as a TV with no video input.

I have
-reinstalled the DVR software
-cleared system startup of any unnecessary (the machine is pretty bare to begin with. only the DVR starts in startup.)
-disabled services unnecessary to the system. I can post a list if anyone wants to see.
-R&R Intel 82945G Express Chipset drivers. (the dates are so close it's almost as if they don't need it. dated 2008)
-dumbed down graphics performance of Windows via System Properties
-Resolution 1024x768 (native resolution of the DVR software for full screen use)

Also note, changing the wallpaper does not work. Even with it set to none, the blocks are still there.

My focus is system performance causing the issue, but apparently I'm wrong. Could it be hardware failure? I'm open to suggestions, short of reformatting.

edit: moving a window around over top the color blocks does not make it go away either. the blocks are almost as if they are burned into the background.

 

[muckshifter]

sounds like bad graphics artifacts, however I'm sure you have looked at that ... you actually using a DiVis card? they not employed ex ATI driver writers?

monitor, what is it?

 

[Silverhazesurfer]

Yes, there is a DiVis card in the machine. The original complaint was that the cameras couldn't be controlled. The software performed poorly and when closed, resulted in this.

monitor, i'm not in front of at the moment. It's on my bench at the office. I will post when I get it. I want to say it was installed in the system as an NEC.


I also must add some procedures I have taken that I forgot to mention.

-the HD was full at the time I got the machine. 98.6% full to be exact. Used WINDIRSTAT to check out the distribution. Cleared all DVR stored video
-Ran Defrag after file removal
-disabled system restore (was enabled at the time of 98.6% full so I assume system restore kept some of that data.)
-ran SFC in case of Windows file corruption
-ran CHKDSK with no errors.

 

[Silverhazesurfer]

I also have to say that my google-fu is failing me. I cannot come up with a good search to find anything else to check. what do you even call this type of issue?

Also, Monitor = NEC65d

 

[Silverhazesurfer]

So.....

After a bit of digging, I found that the machine caused a dump on 4.25.2011. I found this dump file and moved it to my testing machine to open it with the debugging tool. See https://www.pcreview.co.uk/forums/reading-dump-files-t4035605.html



Here is what was found when analyzing it via the debugging tool. I believe the offending process is DVRmain.exe. However, if you use the Bluescreenviewer app listed in the post above, you can see everything BUT DVRmain.exe. HAL.DLL, LVMPG.SYS, and NTOSKRNL.exe are listed as red. I believe this to be driver related to the hardware input card.

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: f7a295fd, The address that the exception occurred at
Arg3: a7caebf4, Trap Frame
Arg4: 00000000
Debugging Details:
------------------

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
FAULTING_IP:
LVMPG+15fd
f7a295fd 8b5118 mov edx,dword ptr [ecx+18h]
TRAP_FRAME: a7caebf4 -- (.trap 0xffffffffa7caebf4)
ErrCode = 00000000
eax=821e67c8 ebx=82261930 ecx=00000000 edx=82261930 esi=821710e0 edi=82261930
eip=f7a295fd esp=a7caec68 ebp=a7caec94 iopl=0 nv up ei ng nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010282
LVMPG+0x15fd:
f7a295fd 8b5118 mov edx,dword ptr [ecx+18h] ds:0023:00000018=????????
Resetting default scope
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: DvrMain.exe
LAST_CONTROL_TRANSFER: from 8057d4c9 to f7a295fd
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
a7caec94 8057d4c9 82171028 82261930 815c6028 LVMPG+0x15fd
a7caed38 8054162c 00000210 00000000 00000000 nt!NtWriteFile+0x5d7
a7caed38 7c90e514 00000210 00000000 00000000 nt!KiFastCallEntry+0xfc
00117f30 00000000 00000000 00000000 00000000 0x7c90e514

STACK_COMMAND: kb
FOLLOWUP_IP:
LVMPG+15fd
f7a295fd 8b5118 mov edx,dword ptr [ecx+18h]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: LVMPG+15fd
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: LVMPG
IMAGE_NAME: LVMPG.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4b4bd030
FAILURE_BUCKET_ID: 0x8E_LVMPG+15fd
BUCKET_ID: 0x8E_LVMPG+15fd
Followup: MachineOwner
---------

 

[Silverhazesurfer]

Based on all of the above, I swapped the memory modules out. From 2GB to 4GB increase as well. Subsequent restarts and an initial test of the "wait time" has yielded no blocky squares of purple color after shutting down the DVR software.