BSOD tied to network activity?

[rogMar]

I originally began posting about this in another thread, but the problem I'm having is strange enough to merit it's own thread, and I should have done that to begin with. Besides, this issue includes a completely different computer, so here we go...

On two of my computers, the Compaq and the Gateway, I get the BSOD. The other day I came home and both of them had restarted after an "Unexpected Shutdown".

My knowledge of these things is limited, but I proceeded to google, and before you know it, I had installed WinDDK and thought I had traced my Compaq issue to the NIC driver [dumpFiles1]. (First thread: http://www.sevenforums.com/crashes-debugging/13850-i-have-strange-bsod-windows-7-a-2.html#post718686) I've still had issues with the Compaq, but they seem to be different drivers this time [dumpFiles2], and I don't know what they are. I get the vague impression that it's related to the process of sending data from my computer to the network, but that's about it.

But upon examination of the most recent dmp files from my Gateway, I noticed that it, too, appeared to have issues with it's network drivers [dumpFiles3]. I haven't looked at all of these, and as is my habit, after looking at the most recent two or three of them, I just assUme the other 5 are the same!

JUST kidding. But I did try (it didn't fly, thru the GUI, why? Know not, do I.) to view the first three files, and I do attach them all here [dumpFiles3] because they may tell you more than they told me. There has to be a pattern here, and my gut feeling tells me it has to do with network activity (i.e. uTorrent, browsing, etc.).

I cringe at the collective gasp of horror, but yes, I DO dare say it;

I never had this much trouble with Vista.

Does anyone have any ideas as to what's actually causing these crashes?

 

[Johnathan Lyman]

I originally began posting about this in another thread, but the problem I'm having is strange enough to merit it's own thread, and I should have done that to begin with. Besides, this issue includes a completely different computer, so here we go...

On two of my computers, the Compaq and the Gateway, I get the BSOD. The other day I came home and both of them had restarted after an "Unexpected Shutdown".

My knowledge of these things is limited, but I proceeded to google, and before you know it, I had installed WinDDK and thought I had traced my Compaq issue to the NIC driver [dumpFiles1]. (First thread: http://www.sevenforums.com/crashes-debugging/13850-i-have-strange-bsod-windows-7-a-2.html#post718686) I've still had issues with the Compaq, but they seem to be different drivers this time [dumpFiles2], and I don't know what they are. I get the vague impression that it's related to the process of sending data from my computer to the network, but that's about it.

But upon examination of the most recent dmp files from my Gateway, I noticed that it, too, appeared to have issues with it's network drivers [dumpFiles3]. I haven't looked at all of these, and as is my habit, after looking at the most recent two or three of them, I just assUme the other 5 are the same!

JUST kidding. But I did try (it didn't fly, thru the GUI, why? Know not, do I.) to view the first three files, and I do attach them all here [dumpFiles3] because they may tell you more than they told me. There has to be a pattern here, and my gut feeling tells me it has to do with network activity (i.e. uTorrent, browsing, etc.).

I cringe at the collective gasp of horror, but yes, I DO dare say it;

I never had this much trouble with Vista.

Does anyone have any ideas as to what's actually causing these crashes?

Ok I think I may have a hold of what is going on. You have BSODs jumping from all sorts of drivers, from your PCI network card, to your CDROM. I'm not seeing much of a consistency.

With that in mind, a lot of the errors i saw in the dumps were related to IRQL_NOT_LESS_OR_EQUAL which is indeed driver related but can be paired up with failing or failed ram.

I would give MemTest86+ a shot at Memtest86+ - Advanced Memory Diagnostic Tool and run it for AT LEAST 5 passes, maybe 10, and see if it flags anything.

After that, runn SFC /SCANNOW in a command prompt as well as CHKDSK /R in a command prompt and report back.

 

[rogMar]

I love homework...

K, I'll do that. That makes a bit of sense as the Gateway system properties says

Installed memory (RAM): 2.00 GB (1.87 GB usable)

Also, come to think about it, the memory loads did seem to be higher when a few of the BSODs occurred.

So I'll run the tests 5-10 times on both towers and see what the results are, then run the command prompt apps and get back to you.

Thanks a lot for taking the time to look at my issue. I had just about given up on tracking it down, as you said, it seemed to jump around. I was grasping at straws with the whole network-related theory, I know, but network hardware drivers were the only common thread I could see, at least with 4 or 5 of the dmp files from both computers that I did look at.

Blah Blah Blah, nuff said, I'll go do it and get back. Thanks again!

 

[Johnathan Lyman]

I love homework...

K, I'll do that. That makes a bit of sense as the Gateway system properties says

Installed memory (RAM): 2.00 GB (1.87 GB usable)

Also, come to think about it, the memory loads did seem to be higher when a few of the BSODs occurred.

So I'll run the tests 5-10 times on both towers and see what the results are, then run the command prompt apps and get back to you.

Thanks a lot for taking the time to look at my issue. I had just about given up on tracking it down, as you said, it seemed to jump around. I was grasping at straws with the whole network-related theory, I know, but network hardware drivers were the only common thread I could see, at least with 4 or 5 of the dmp files from both computers that I did look at.

Blah Blah Blah, nuff said, I'll go do it and get back. Thanks again!

Excellent! Let us know!