Quote Originally Posted by Sigurd View Post
That this is occurring only in one place and not another is a complete mystery. A Dorm you say? Could it be attempted hacked, by some idiot having spoofing running on your network? Some poorly designed trojan that you have on it distributed by the same culprit? Or designed to do this for the lulz... Just brainstorming here.

The general BSOD message suggests either two things, but could be caused by my previous list.
But since this only happens in one place (your dorm, I am afraid that I am out of suggestions) Have you checked the event viewer?

To do a thorough memory check, you need to be running Memtest. (In combination of removing all sticks and test them one by one and in different slots)
Also to check your drivers use Driver Verifier

If you have any warranty left on it, I would suggest taking it in, because BSOD can sometimes be a combination of faulty Motherboard, RAM slots/sticks which would only be solved if replaced.
well, I've had a new development, but I'll address these suggestions anyways:

-I ran memtest a while ago. nothing wrong, beyond the tcpip.sys obviously. same with driver verifier. the only thing the latter mentioned was that several drivers were not working-which happen to be the ones I shut down on purpose, to prevent the freezing I mentioned in another thread. These are drivers that have little to do with the internet.
-I doubt it. I have literally the best antiviruses I can find (including malwarebytes), and they surely would have detected it-since it would be a crap one. I have detected yesterday a trojan horse, but this one seems to have infected my computer only in the last few days (the last full scan showed nothing-it was exactly a week previous). my problem has been going on for almost two months. added to that that I move in much earlier than other students, and the problem starts even before everyone else moves in, and I have what is by all accounts the best security of anybody in my dorm outside the hardcore computer nerds......
-I already took it to the technicians. they are just as clueless.

come to think of it, I have a suspicion that the problem is actually software caused. what if the tcpip is causing two hardware components to crash, and thus making look like a hardware problem?

so I did the following:

I opened up my cmd, and type the following:

netsh int ip reset
this I am told resets/reinstalls my tcpip. I rebooted my computer, and let it run as normal. I even left it for an hour while logged on. no crashes so far. If this is indeed the solution, and I suffer no crashes in the next week or so (or ever), then we have a cause. if not, we're back to square one, though with the question: why didn't it crash in the two days after reinstallation?

If it did work, then I still have one problem? what happened to my tcpip to cause the computer crashes?