Intel Communities: Message List

Re: 82579V Blue-Screens during Windows Updates

webadmin@intel.com — Tue, 01 May 2012 23:53:20 GMT

Thanks Mark! Could you let me know if this is an issue and if it will be fixed in a future driver?

82579V Blue-Screens during Windows Updates

webadmin@intel.com — Sun, 29 Apr 2012 18:41:01 GMT

Hi,

When the "Energy Efficient Ethernet" feature in the 82579V's settings is enabled (default) it causes a blue-screen (BAD_POOL_HEADER) during the set of udpates after the first service pack. Basically the set of updates installs fine and when I click to restart the PC is when the PC blue-screens. If I disable this feature prior to installing windows updates then it doesn't blue screen and everything works as expected. For more information as well as a minidump from the BSOD, you can check out his link: http://www.overclock.net/t/1249769/e-peen-would-appreciate-your-help-with-a-bluscreen#post_17100459

I'm using an Asus Sabertooth P67 with the latest BIOS and 17.0 NIC driver. I'm not sure if this problem existed with the previous set of drivers as I was keeping that feature disabled prior but I decided to set it to default with this new driver and that's how I came upon this BSOD. I don't get any BSODs during normal use of the computer; only during the windows updates process.

It'd be nice if Intel could fix this so I don't have to disable it every time I do a fresh format of Windows.

Edit: Forgot to mention that I'm using Win7 64bit.

Thanks!

Re: Intel 82579V Issue

webadmin@intel.com — Fri, 06 Jan 2012 02:03:09 GMT

I didn't read through the thread, just wanted to throw a quick suggestion out there. Try disabling "Energy Efficiency" in the NIC settings and see if that resolves the problem.

Re: 82579V + 16.8 drivers = strange behavior ?

webadmin@intel.com — Fri, 06 Jan 2012 01:58:22 GMT

In my case, I don't get the PXE boot menu appearing but I have it disabled in the BIOS. Version 16.7 of the drivers works fine in my case. I not only get the wrong NIC reported (82579LM) with 16.8 but also the internet doesn't work after I restart the PC after the driver installation. Basically, 16.8 doesn't work, 16.7 works, and I will wait for the fix with the new driver when it's released.

Thanks for the quick response!

82579V & Intel Network Connections 16.8 Problem

webadmin@intel.com — Mon, 02 Jan 2012 19:07:45 GMT

Hi,

I have the Intel 82579V Gigabit NIC which is integrated in the Asus Sabertooth P67 rev 3.0 and any time I try to install the drivers for it (specifically Intel Network Connections 16.8) it can't identify the NIC correctly. What happens is this: I install the driver and it identifies the NIC fine and internet works but when I restart my computer it misidentifies it as some 82579LM (not sure if the number is correct but LM is at the end for sure) and internet doesn't work. I've tried a few different things and can't fix it. Went back to Intel Network Connections 16.7 drivers and everything is fine with those. I'm posting this so you can guys work out the problem and fix it in the next version release of the drivers.

Thanks!

Re: 82579V + 16.8 drivers = strange behavior ?

webadmin@intel.com — Mon, 02 Jan 2012 19:10:53 GMT

I have the same problem with the same NIC on the Asus Sabertooth P67. I just made a post about it. You can view it here: http://communities.intel.com/thread/27226?tstart=0

I'm hoping Intel fixes it in the next version of the drivers because I like having the latest installed on my PC.

Re: Intel RST and Plextor PX-128M2S

webadmin@intel.com — Mon, 27 Jun 2011 03:26:43 GMT

Well, it's been 2 weeks since I last received the error message but yesterday and today I received it again. I didn't notice any freezing because I might not have been at the computer when this happened but in general I don't care about the error message as long as it doesn't interrupt my work (by freezing). Anyway, if Intel have been working on this with the Intel RST drivers, please keep up the good work as the drivers seemed to keep it quiet for a while. Hopefully it can be fixed fully, soon.

Thanks!

Re: Intel RST and Plextor PX-128M2S

webadmin@intel.com — Tue, 14 Jun 2011 18:24:51 GMT

I updated the BIOS to 1606 beta and installed the latest Intel RST drivers from Asus (v10.5.0.1026) and haven't had a freeze/error message in 4 days now. I think it's been fixed.

Re: Intel RST and Plextor PX-128M2S

webadmin@intel.com — Sat, 04 Jun 2011 04:46:33 GMT

Is anyone else getting this? Hopefully it will be fixed with an Intel RST driver update.

Intel RST and Plextor PX-128M2S

webadmin@intel.com — Fri, 13 May 2011 17:14:29 GMT

I just built a new computer and every couple of days the computer would lockup for about 30 seconds and the following error message is posted in the Event Viewer: "The device, \Device\Ide\iaStor0, did not respond within the timeout period." At first I had to reboot the computer but then I realized if I waited it out, the lockup disappears and I can continue working on my PC. While the lockup is going on, the hard drive LED is a solid ON.

I read that this has to do with LPM (Link Power Mode) and that the Intel Rapid Storage Technology drivers send this command to the drive but if it doesn't support the command, the hard drive locks up for about 30 seconds and the error appears in EventViewer. I'm using the latest Intel Rapid Storage Technology driver which is v10.1.0.1008.

I don't have Service Pack 1 installed for Win7 so I don't know if that might resolve the issue but I think it has to do with the Intel AHCI drivers and not windows. I hear this happens with the newest SSDs on the market only.

My computer specs are as follows:
Asus Sabertooth P67 B3 revision, latest 1502 BIOS
Intel i7-2600K
8GB Corsair Vengeance DDR3 1866MHz
EVGA GTX 570
Silverstone Strider Gold ST1000-G 1000W
Lite-On 24x DVD Burner
Plextor PX-128M2S 128GB SSD

Btw, the Plextor SSD is connected to the first Intel SATA6Gb/s port on the motherboard.

I have also posted this on the Plextor forums and would like this to get fixed soon because a lot of people are getting these error messages, especially with the Vertex 3 and Plextor SSDs and until recently the C300 but that was fixed in a firmware release from Crucial.