I'm well aware of the normal cause's of memory creep. But I have a system that has me stumped.
HP Elitedesk G2 i7-6700, 8g ram running BI 5.3.3.16.
Running about 40MP/s worth of cams.
I did not set this computer up, a friend of my daughters did, supposedly following the directions I gave him.....not.
Doubt this has any relevance, but the SSD was installed as the D: drive, and the spinner was installed as the C: drive.
Win 10 Pro & BI was installed on the C: drive.
I live 10 hrs away from this location, and can't just "drop in". I'm using Team-viewer to remote in.
Bi is ran as a service.
It appears that a fresh install of Win10Pro was installed on the computer, but is there a way I can definitely tell from here since the "friend" didn't follow my other instructions.
I have so far tried these Intel 530 Graphics Drivers, with same results.
1-Failed to record ver
2-27.20.100.9079
3-27.20.100.9030
4-27.20.100.8853
Should I try the non-DCH drivers?
Anyone care to tell me what stable driver ver they are successfully running with their Intel Graphics 530?
Any ideas other than a slash and burn on Windows?
After 42 hrs of running.
After a fresh boot
HP Elitedesk G2 i7-6700, 8g ram running BI 5.3.3.16.
Running about 40MP/s worth of cams.
I did not set this computer up, a friend of my daughters did, supposedly following the directions I gave him.....not.
Doubt this has any relevance, but the SSD was installed as the D: drive, and the spinner was installed as the C: drive.
Win 10 Pro & BI was installed on the C: drive.
I live 10 hrs away from this location, and can't just "drop in". I'm using Team-viewer to remote in.
Bi is ran as a service.
It appears that a fresh install of Win10Pro was installed on the computer, but is there a way I can definitely tell from here since the "friend" didn't follow my other instructions.
I have so far tried these Intel 530 Graphics Drivers, with same results.
1-Failed to record ver
2-27.20.100.9079
3-27.20.100.9030
4-27.20.100.8853
Should I try the non-DCH drivers?
Anyone care to tell me what stable driver ver they are successfully running with their Intel Graphics 530?
Any ideas other than a slash and burn on Windows?
After 42 hrs of running.
After a fresh boot