BSOD

I dont feel like reading through logs.

Next time it happens, remember what stop code it gives. it will say at the bottom something like STOP 0x0000####. Tell me that and I can narrow down your problem greatly and possibly tell you exactly how to fix it.


You may want to turn off the automatic restart on BSOD so you can see what the error is. I cant remember if that is done in the bios or Windows, I think Windows. But I dont remember where off the top of my head.
EDIT here we go:
http://pcsupport.about.com/od/tipstricks/ht/disautorestart.htm
http://pcsupport.about.com/od/windows7/ht/automatic-restart-windows-7.htm

 

What processor do you have?

On Sandy bridge that is normally vcore is too low, but *can* also be the QPI link related (rare). If you have a first gen i7 then maybe you need a higher QPI speed in relation to your uncore speed. It could also be QPI voltage on the 1st gen i7's.

If you have an AMD processor then you need more vcore


Have you ever seen an 0x00000101? That is also vcore related. Generally 101 has to do with the actual cores and processing, while 124 is CPU related but in another area of the CPU that has to do with interconnects and such

 

Yep I thought I remembered your username

So ya, your vcore is too low for the speed you are at. Go into your bios and bump up the core voltage a couple steps. If you are set to auto voltage, then post back what the core speed you are running at is.

For stock speed of the processor (3.8GHz), set your vcore setting to positive (+) offset and then increase the voltage offset by 2 or 3 steps. I dont have a 2600k anymore so I cant you the exact setting, but I think that 3 steps of positive offset is something like 0.015. Sandy Bridge dynamically adjusts the vcore so I dont really know if your problem comes from voltage being scaled too low while idle and then the voltage not being raised fast enough when the processor clocks back up, or if the auto voltage is set too low for at top speed when a high load is placed on the CPU.
You could also try setting the vcore to manual mode and specifically setting something like 1.3v

 

Stock vcore is different for each processor, mine was about 1.25v. So if yours is 1.2v then set your vcore to 1.25. Even that is a bit excessive of a bump to maintain a little stability at stock speeds but a tiny bit extra wont hurt. Going a whole .1v is a bit much and not needed at all in this case. 1.4v is the maximum voltage you should go if you were overclocking.

 

Post back if you have any more bluescreens

 

Sounds like Windows freaked out when you disabled and then re-enabled your NIC.

 

Sounds like you need a new router.


You might be able to get around the problem for a while by assigning each computer their own IP address manually. Set the router to static LAN and not DHCP assign. Then on each device open the properties of the ethernet adapter and in the IPv4 area assign it a manual address.

Youll need to find out your routers address and assign all the IPs and the gateway based on that. Set the primary DNS of each device to just be the routers IP.
So if your routers default IP is 192.168.2.1 then you could set the first computer's IP as 192.168.2.101, then the second computer could be 192.168.2.102, etc. Default gateway would be 192.168.2.1

 

You should ask Q for some advice before you spend money, he may be able to help you further. He is much smarter than I am when it comes to networking.