solved

[White1234]

solved

[mpack]

Without a log we can say almost nothing. The log would have to include the slow period.

So, post a VM log file. With the VM fully shut down, right click it in GUI. Select "Show Log" and save "VBox.log" (ONLY) to a zip file. Attach the zip here.

[White1234]

Here the log.
I hope a 7zip file is ok.

[mpack]

7zip is fine, however I need you to follow my instructions otherwise. The VM was not shut down when that log was captured, and since it only deals with the first 25 seconds of a session, I doubt that it included a "slow period" as requested.

Something else you could do is, next time you get a slow period, look in the task list for both host and guest, try to identify the process which is using up all the CPU or I/O time - these things don't just disappear. Usually the culprit will be AV scanning the disk, or Windows Update kicking in.

[White1234]

Ok sorry
Here the new file. I closed after the problem occured. I think it has to do with inactivity. It never happens when im working.

[mpack]

That is the exact same log again.

Make sure all kinds of power saving are disabled in the guest.

[White1234]

Damn, this should be the correct one.
I already changed the power settings before since this was the first solution i found to a similar problem from someone else. But it didnt work.

[White1234]

no one?

[socratis]

00:00:02.103791 Host RAM: 16336MB total, 12657MB available
00:00:02.237210   RamSize           <integer> = 0x00000002ee000000 (12 582 912 000, 11 GB)

You've allocated 12000 MB of RAM out of the 12657 MB available at the launch of the VM. After 14 hours of operation, due mainly to caching and other background tasks (assuming you didn't run anything on the host), your host's memory maybe running out causing all sorts of problems, including, but not limited to what you're seeing.

That is if ALL the guest's power-options have been examined carefully and set to the max performance.