Solved COM Surrogate?

Malwarebytes Anti-Malware
www.malwarebytes.org

Scan Date: 16.12.2015
Scan Time: 21:54
Logfile: MBAM1.txt
Administrator: Yes

Version: 2.2.0.1024
Malware Database: v2015.12.16.05
Rootkit Database: v2015.12.07.01
License: Free
Malware Protection: Disabled
Malicious Website Protection: Disabled
Self-protection: Disabled

OS: Windows 10
CPU: x64
File System: NTFS
User: James

Scan Type: Threat Scan
Result: Completed
Objects Scanned: 452547
Time Elapsed: 25 min, 34 sec

Memory: Enabled
Startup: Enabled
Filesystem: Enabled
Archives: Enabled
Rootkits: Disabled
Heuristics: Enabled
PUP: Enabled
PUM: Enabled

Processes: 0
(No malicious items detected)

Modules: 0
(No malicious items detected)

Registry Keys: 0
(No malicious items detected)

Registry Values: 0
(No malicious items detected)

Registry Data: 0
(No malicious items detected)

Folders: 0
(No malicious items detected)

Files: 0
(No malicious items detected)

Physical Sectors: 0
(No malicious items detected)


(end)
 
Screen just went Black again. I was able to see and move the mouse,but the rest was just black, so I rebooted.
Now when I talk about screen, I mean my external monitor. I just tried to switch to the built-in screen, but it is completely dark. I can See my desktop against the light, but theres no backlight coming from the screen. So I plugged in the monitor again. As I was writing this, monitor went Black again. I waited and it sent me back to the Windows-login. I caught a glimpse of the taskmanager which showed 86% RAM just before it went black. This time it was Runtime Broker that took over 4gb of RAM resources.
This is beginning to get on my nerves now... I'm thinking about a windows re install.
 
At this point...

In this forum, we make sure, your computer is free of malware and your computer is clean :)
Because the access to malware forum is very limited, your best option is to create new topic about your current issue, at Windows section.
You'll get more attention.

Good luck :)
 
You're very welcome
p22002759.gif
 
Just a quick update if someone was following this with interest:
There are apps that can induce a memory leak. There's a process called Runtime Broker that manages something app related that will shoot into the sky in terms of CPU and RAM usage when a leaky app is started. I observed this problem when starting the windows Photos app. This is a known bug in Win10 since Technical Preview. It only has come down on me since Threshold 2 update a few days ago (which started without asking me during standby when I was away from the laptop, nice!).
The high CPU usage causes my laptop to overheat which results in the strange graphics errors that I experienced.
So after keeping Runtime Broker out of business, I've had no problems yet. Fingers crossed.

P.S.: I've got no idea what the COM Surrogate 4gb RAM Process had to do with all of this, but it never appeared again...
 
Back