New
#1
Event Viewer logging only since last power on
I'm experiencing this weird freezing issue where I could be playing a game and suddenly everything will pause, and yet some parts of programs will be active. Such as in Battlefront II just now, I could move the camera around my character as he was frozen mid-run, but everything else about the game was stopped. WinAmp was playing in the background and that stopped. I was able to open task manager and kill Battlefront but much of Windows was non-responsive. I was able to bring up the start menu with the Windows key but clicking on the Windows button or anything inside the menu did nothing. This has happened several times in the last month and it's getting really annoying.
My only current guess for a culprit is DisplayFusion, which I've been running for the past month after getting a new monitor and running my old one in portrait display. But before I write the useful DisplayFusion off and look for a replacement, I'd like to know exactly what is going on with Windows when these crashes occur, and so we come to the reason for my post.
Event Viewer is only showing events since the system was last powered on, and nothing from before. I don't think I've ever seen this before on older systems of mine, it's always showed at least the last few days worth of activity. But this time I can open it up, go to Windows Logs > System and it'll only show maybe five entries when I open it directly after logging in.
I've looked around for possible fixes for this but all I can find is stuff about the log size (not an issue, I've expanded it massively and it's made no difference), and to select "Archive the log when full - do not overwrite events", which I have.
Any ideas as to why on this install of Windows Event Viewer is refusing to show past logs?