Why is my computer crashing system-wide ... again?

I like dogs

Honorable
Jan 14, 2014
29
0
10,530
I am about to reinstall my legitimate copy of Windows 7 for the third time in 7 months.

I built this computer using all-new components from Newegg in February of this year.

I made the possible mistake of NOT doing a completely fresh install of Windows, since my new Samsung SSD already had my files/XP on it from my old computer, and I didn't have enough backup media at the time. So, my first installation of Win 7 had a Windows.old file installed. Same with the second installation.

I have been running Kaspersky Internet Security the entire time, so I doubt I've gotten a virus... unless it missed something.

Also, I did let the SSD get dangerously(?) full ... temporarily had less than 1GB of space left (out of 128GB).

Anyway, the problems started happening about two weeks ago, when IE started crashing. I got APPCRASH messages from IE in assorted modules ... like jscript9.dll, stackhash_a7aa, msvcrt.dll , and MMDevApi.dll . I saved most of these reports.

I have installed some programs from torrent downloads (Wondershare streaming audio, and Text Aloud text reader) but didn't notice any problems ... at least not right away. Also, have downloaded many movies from Pirate Bay/Vuze.

Now, pretty much any/every program will crash, often accompanied by a BSOD "Memory Management" screen.

My question is ... how do I track down the cause of this problem, so it won't happen again? Is this even possible?

I haven't done the reinstall yet, but I have backed everything up, so I can feel free to mess around.

Any ideas are MUCH appreciated!!!
Fred
 

I like dogs

Honorable
Jan 14, 2014
29
0
10,530


Well, the first time my Windows crashed, I hadn't installed any software from torrents, so I'm not sure that's the problem. Also, I scan everything with Kaspersky (although that may not be helpful).
Mainly, I'd like to be able to track down the source of the problem, if possible.
 

I like dogs

Honorable
Jan 14, 2014
29
0
10,530
OP here...
Turns out the problem was caused by a bad RAM stick.
You can test your ram using memtest86, or just by pulling out one RAM stick at a time and seeing how your computer responds.
Hopefully this will help someone in the future.