problems with Bitcomet crashing

[hayashik]

system specs:

CPU: Intel Core 2 Duo E6600 (non OC)

mobo: Asus p5n32-sli premium (n590 chipset)

ram: OCZ ddr2-800 platinum rev.2 timings: 4-4-4-15

video card: EVGA 7950GT superclocked

HDD: Seagate barracuda 7200.10 320 gb sata 2

Problem:

I open bit comet, start a torrent, and it crashes on me, the old computer that I was on didn't have any problems with bitcoment and crashes, however this one does. I am using version .70 I first installed .79 then when It crashed a lot I looked on the forums and saw everyone recommended .70 so I installed it. However, everything is the same and still crashes.

On an interesting note. I was at my girlfriend's house a few days ago and brought along my computer. I ran bitcomet there and It worked perfectly fine for 8+ hours before I shut it down.

The only differences between my setup at her house and my setup at my own are:

1. IP address (duh..)

2. She has a router, I don't and directly connect to the modem.

3. I had a stereo speaker there and 5.1 speakers at home from logitech.

4. I also have a stero mic plugged in from soundmax, called soundmax superbeam.

at the multiple times it crashed I was running many different things and sometimes I was running almost nothing. EG: msn/winamp/lastfm/IE

attached are the error files.. I have no clue what they mean... maybe you guys do .. ALSO the CRASH file is not a txt file Its a *.DMP file but I couldn't upload it as dmp so I renamed it with a txt extension(btw am I supposed to post here or bug reporting? it's an error.. but I don't know what. lol... )

*EDIT*

I have Windows Firewall On but have bitcomet on exception, and i have the antivirus NOD w/IMON (and everything else) on.

*EDIT 2*

I have tried unplugging the mic and speakers as suggested but still experience crashes within 30 seconds of starting the torrent. (thanks for the advice kluelos)

ERRORLOG.TXT

CRASH.txt

[kluelos]

Windows senses what hardware is attached and incorporates/removes drivers and such on the fly, so this isn't quite as useless as it may seem: try unplugging your speakers and mic, and see if the issue goes away.