You could use a process monitor first (e.g. by sysinternals) to see which processes access your sleepy drive.
BTW: didn't you ask in this thread
/t/19546/1
for a solution to wake up a drive? To me that looks like the exact opposite of this "bug" report.