A possible clue why client crashes - Process Explorer information

Are any of you familiar with process explorer? When I crash the gauge of 'I/O' is maximized and I wonder if it may explain the situation.

---

A game is not supposed to be some kind of... place where people enjoy themselves!

Well I/O shows reflect hard drive requests and it's ilk like having your AV program scanning the data as it's being read. Also since the gauges auto scale having the gauge max out isn't all that informative. Is the overall system I/O chart or did you do a properties on the cityofheroes.exe file and look at it's graphs on I/O?

It's possible that the game's files are on a spot of the drive that is temperamental and requires retries or the AV program is getting choked up and the game crashes because the whatever it's trying to get isn't available in a reasonable period of time and it doesn't know how to handle it. If you were only looking at the system chart then maybe some other task is tying up I/O and again the game doesn't know how to handle it well.

---

Father Xmas - Level 50 Ice/Ice Tanker - Victory
$725 and $1350 parts lists --- My guide to computer components

Tempus unum hominem manet

There's also the possibility that the game files are heavily fragmented as well. Leading to excessive amounts of drive thrashing as pieces of files are looked for.
Defragging the game files (if your defrag solution allows it) might help reduce the amount of drive seeking.
(Note: If you're running on an SSD, ignore this suggestion.)

Also, how "full" is the drive?

On an NTFS volume, you start seeing filesystem performance falloff at about 20% free space. You start seeing drastic falloff at 15% and at 10% you may as well just shut everything down and start deleting stuff.

---