I just got a Logitech G15 which lets me monitor the usage of both cores through its LCD Screen (pretty sweet). Anyway, I was working with a program calld LCDStudio, learning to make custom LCD displays for the keyboard, and the program crashed. I wasn't doing anything too strange, I had just opened a blank document, and it reported a VBT (Very Bad Thing 
) Error and shut down. I also happened to be defragging and running Winamp at the time. Just after the crash, I noticed one of the cores had shot up to top usage and stayed there. I tried closing other applications (right now everything is closed but the defrag and the browser I'm typing this in), and it stayed that way.
Anyone else experienced this, or know what I can do to prevent it? I'm sure a restart will fix the problem, which I will do as soon as defrag is complete, but I'm just curious if anyone can explain what happened.
Incidentally, task manager confirms what the G15's display is telling me, it's not just something funky with the keyboard.
) Error and shut down. I also happened to be defragging and running Winamp at the time. Just after the crash, I noticed one of the cores had shot up to top usage and stayed there. I tried closing other applications (right now everything is closed but the defrag and the browser I'm typing this in), and it stayed that way. Anyone else experienced this, or know what I can do to prevent it? I'm sure a restart will fix the problem, which I will do as soon as defrag is complete, but I'm just curious if anyone can explain what happened.
Incidentally, task manager confirms what the G15's display is telling me, it's not just something funky with the keyboard.
Facebook
Twitter