Hello. I'm new to the forums, although I've frequently browsed the threads here when I have technical issues or just want to read up on how something works.
Lately I've been experiencing semi-regular BSOD crashes on one of my computers. It's an extremely mediocre setup (Sempron 2400+, 512mb, etc) that I use solely for running some P2P clients, so I don't have to waste resources on my other computer or leave it on constantly. Anyway, back to the issue.
Maybe 4-5 times a day I've been getting a blue screen of death. It used to just reboot, until I changed the "automatically restart" option in the hopes of getting some more info to try to solve the issue. The blue screen mentions TCPIP.SYS and some memory addresses, but aside from that doesn't give much of a clue as to what's going on. I *think* the problem is related to BitComet, as it only seems to happen when that app is running, though I haven't extensively tested that theory (I'm going to tonight, I plan on leaving it on without BitComet running and see if it crashes).
At first, after Googling the "Your System has Recovered from a Serious Error" message that I initially was getting after an auto-reboot, I thought it might be bad RAM, so I ran MEMTEST and sure enough there were errors, so I replaced that right away. MEMTEST no longer finds errors in the RAM, but the problem persists, unchanged.
Then I got to thinking about what had changed recently that might be a factor, and thought that the problem might have begun when I switched from my motherboard's onboard Marvell LAN to the onboard NVidia LAN, so I switched back and disabled the NVidia LAN in the BIOS, but no luck there either - it just crashed again right before I came here and started writing this post.
I've created debug logs of my minidumps for two of the crashes - the most recent one after switching back to the Marvel LAN, and an earlier one with NVidia LAN. I'll attach both, if anyone thinks they can glean any useful information from them. One difference I noticed is that the latter debug log, the one for the crash that occurred with the Marvel LAN, has a few error messages about being unable to identify modules, while the earlier crash does not.
I know for sure that it's not malware or a virus, as I've had Kaspersky Internet Security Suite running real-time protection and I've done a full scan on the highest protection settings. I also should mention that I did a fresh format very recently, installed all Windows updates, etc. Oh and, the problem DID exist before the format, I was hoping it would get rid of it.
I haven't completely ruled out the NVidia LAN as the culprit, since even though it's disabled in the BIOS the drivers would still be installed, would they not? Right now that's my only lead, since the problem did seem to start when I switched to that onboard LAN. Aside from that there's nothing I can think of except a hardware failure of some sort, and I've already ruled out the RAM by replacing it with a brand new stick.
Sorry this post is so long, but I always prefer to err on the side of too much detail than not enough.
So, can anyone suggest anything, or gather any clues from the debug logs? I'd be eternally grateful for any help.
PS. Crash1.txt is the earlier crash, with the NVidia LAN, and Crash2.txt is the later crash with the Marvell LAN.
Lately I've been experiencing semi-regular BSOD crashes on one of my computers. It's an extremely mediocre setup (Sempron 2400+, 512mb, etc) that I use solely for running some P2P clients, so I don't have to waste resources on my other computer or leave it on constantly. Anyway, back to the issue.
Maybe 4-5 times a day I've been getting a blue screen of death. It used to just reboot, until I changed the "automatically restart" option in the hopes of getting some more info to try to solve the issue. The blue screen mentions TCPIP.SYS and some memory addresses, but aside from that doesn't give much of a clue as to what's going on. I *think* the problem is related to BitComet, as it only seems to happen when that app is running, though I haven't extensively tested that theory (I'm going to tonight, I plan on leaving it on without BitComet running and see if it crashes).
At first, after Googling the "Your System has Recovered from a Serious Error" message that I initially was getting after an auto-reboot, I thought it might be bad RAM, so I ran MEMTEST and sure enough there were errors, so I replaced that right away. MEMTEST no longer finds errors in the RAM, but the problem persists, unchanged.
Then I got to thinking about what had changed recently that might be a factor, and thought that the problem might have begun when I switched from my motherboard's onboard Marvell LAN to the onboard NVidia LAN, so I switched back and disabled the NVidia LAN in the BIOS, but no luck there either - it just crashed again right before I came here and started writing this post.
I've created debug logs of my minidumps for two of the crashes - the most recent one after switching back to the Marvel LAN, and an earlier one with NVidia LAN. I'll attach both, if anyone thinks they can glean any useful information from them. One difference I noticed is that the latter debug log, the one for the crash that occurred with the Marvel LAN, has a few error messages about being unable to identify modules, while the earlier crash does not.
I know for sure that it's not malware or a virus, as I've had Kaspersky Internet Security Suite running real-time protection and I've done a full scan on the highest protection settings. I also should mention that I did a fresh format very recently, installed all Windows updates, etc. Oh and, the problem DID exist before the format, I was hoping it would get rid of it.
I haven't completely ruled out the NVidia LAN as the culprit, since even though it's disabled in the BIOS the drivers would still be installed, would they not? Right now that's my only lead, since the problem did seem to start when I switched to that onboard LAN. Aside from that there's nothing I can think of except a hardware failure of some sort, and I've already ruled out the RAM by replacing it with a brand new stick.
Sorry this post is so long, but I always prefer to err on the side of too much detail than not enough.
So, can anyone suggest anything, or gather any clues from the debug logs? I'd be eternally grateful for any help.
PS. Crash1.txt is the earlier crash, with the NVidia LAN, and Crash2.txt is the later crash with the Marvell LAN.
