Hello,
I just had this what seems to be a new idea:
"Detecting memory corruption with sound".
Assuming there is lots of memory corruption but for some reason still hard to find then maybe finding it with sound might be possible ? (Maybe it could work for little bit of corruption too ? ;))
Idea is to for example:
Allocate large ammounts of memory, lock em so they stay at same place.
Then fill that memory with same kind of sound/wave buffer... and then simply play it... while maybe displaying a memory counter or so... which indicates in which memory cell/region/range the sound is currently playing...
The sound could also be stored on harddisk first and then loaded to see if that creates any kind of system corruption...
Maybe this could also be used to test soundblaster..
But the purpose ofcourse should be to somehow track-down what is causing the corruption.
Could be a driver or so...
So I am just bringing this idea to your attention... maybe it has some merit to develop/think about it further... maybe it could be usefull for something in the future ?! ;)
(As I was changing the subject to include "(or system)" and then moving to the end of the subject causing the error beep in outlook express some more sound corruption occured.... I recorded it and it's available on my webdrive as well as other sound samples of: memory (?) or some system/hardware/software (?) corruption, which gave me the idea !)
(I think system got corrupted after millions of reads or writes... or maybe some part of the memory became active because of high memory usage which is normally inactive/unused (?))
Bye, Skybuck !