Windows 7: Blue Screen of Death on connecting Ethernet cables

About 2 weeks ago I started to get the BSOD at different random times. I did a system reinstall (Twice) but that has not helped the issue. It seems that the 1 consistent is that when I connect the ethernet cable/s I will get the BSOD. there are 2 separate LAN Ports on the motherboard and it doesn't seem to matter which one gets plugged in. I had both plugged in before this issue began for over a year. I have tested different cables and a different router with no difference in effect.

I am running Window 7 ultimate 64 bit Full Retail

PC is about 2 year old

I am running the PC now using wireless and it seems to be stable.

I am currently using the Cisco EA4500 Router.



I am guessing that it is a driver conflict but nothing new has been added to the system for a while and I try to avoid doing automatic updates to often.

System Age:

Due to the system age, make sure the hardware is compatible with Windows 7: -> Download and run the Windows 7 Upgrade Advisor

Software Concerns:

Code:

Start Menu\Programs\DriverUpdate
Start Menu\Programs\MSI Afterburner

• We do not recommend automated driver update software. It often finds drivers for devices similar to but not exactly the same as the hardware actually on the system. This can lead to conflicts and blue screen crashes. If you need help finding driver updates for a certain device, please start a thread in Drivers - Windows 7 Forums instead of using software. Driver updates are not always necessary and some updates can actually decrease system stability rather than increase it, so it is usually better not to update unless a device or its driver is causing problems with the system. If it ain't broke, don't fix it.
  
  
• MSI Afterburner/RivaTuner is known to cause instability with systems. Please remove the software. Software overclocking does not provide reliable overclocking. Overclocking should be accomplished through the BIOS or through the graphics card manufacturer's software.

Analysis:

Your first crash blames MSI Afterburner directly. The second crash blames a network issue.

The second crash may be due to BitDefender, which is a known cause of system performance and stability issues. Remove BitDefender by following How to uninstall BitDefender and replace it with either of these:

• Microsoft Security Essentials - Free Antivirus for Windows coupled with Malwarebytes. Do not start the free trial of Malwarebytes. Just use the standalone version, update it, and scan your computer once a week with Malwarebytes and with Microsoft Security Essentials.
  
  
• Good and Free system security combination.

3rd Party Drivers:

Update any drivers that are highlighted in red:

Code:

ASACPI.sys Sun Mar 27 20:30:36 2005 (42476C4C)
LHidFilt.Sys Fri Sep 21 05:05:39 2007 (46F3A583)
LMouFilt.Sys Fri Sep 21 05:05:43 2007 (46F3A587)
AsIO.sys Mon Dec 17 02:11:49 2007 (47663D55)
intelppm.sys Mon Jul 13 17:19:25 2009 (4A5BC0FD)
bdvedisk.sys Tue Jan 19 08:45:31 2010 (4B55D39B)
amdxata.sys Fri Mar 19 10:18:18 2010 (4BA3A3CA)
iaStorV.sys Thu Jun 10 18:46:19 2010 (4C11875B)
netr28ux.sys Tue Nov 9 02:44:53 2010 (4CD91815)
mv61xxmm.sys Wed Feb 9 02:28:40 2011 (4D525E48)
mv61xx.sys Wed Feb 9 02:28:49 2011 (4D525E51)
ladfBakerRamd64.sys Fri Mar 18 15:26:10 2011 (4D83CDF2)
ladfBakerCamd64.sys Fri Mar 18 18:10:23 2011 (4D83F46F)
bdfsfltr.sys Wed Jul 27 09:23:21 2011 (4E302D69)
yk62x64.sys Thu Sep 8 01:34:54 2011 (4E68701E)
trufos.sys Wed Oct 19 03:10:43 2011 (4E9E9413)
bdfwfpf.sys Mon Nov 14 10:16:17 2011 (4EC14CE1)
bdfndisf6.sys Mon Nov 14 10:16:24 2011 (4EC14CE8)
avchv.sys Fri Nov 25 02:04:45 2011 (4ECF5A2D)
avc3.sys Tue Mar 20 05:04:13 2012 (4F68642D)
nvlddmkm.sys Tue May 15 01:35:36 2012 (4FB20748)

ASACPI.sys
LHidFilt.Sys
LMouFilt.Sys
AsIO.sys
intelppm.sys
bdvedisk.sys
amdxata.sys
iaStorV.sys
netr28ux.sys
mv61xxmm.sys
mv61xx.sys
ladfBakerRamd64.sys
ladfBakerCamd64.sys
bdfsfltr.sys
yk62x64.sys
trufos.sys
bdfwfpf.sys
bdfndisf6.sys
avchv.sys
avc3.sys
nvlddmkm.sys

Older versions of ASACPI.SYS are a known BSOD problem on Windows 7. Update the driver by:

1. Going to the Asus motherboard support site
   When you reach the website:
2. Scroll down the page and click Utilities
3. Hold Ctrl and press f (ctrl+f) to enter the browser's find feature
4. Search for "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit" (without quotes)
5. Download and install the driver.
6. After installation is complete, verify that it installed correctly.
   • Click Start Menu
   • Click My Computer
   • Go to C:\WIndows\System32\drivers\
   • Verify that the ASACPI.SYS file is dated 2009 or newer (2010,etc.)

I have been using windows 7 and bit defender for over a year before the problem started.

Additionally I got driverupdate software after the issue started in an attempt to fix the problem and while it seemed to help at first it did not solve the issue.

Additionally I use MSI Afterburner for controling the Fan Speed on my Video Card and not over clocking.

However, I am happy to try what you have advised if it fixes the issue. I will let you know how I go.

Thank you for the advise

Sadly the first efforts have failed. I have removed ALL software suggested and updated the Driver as suggested. I did not at this time install Microsoft Security Essentials - Free Antivirus for Windows coupled with Malwarebytes.

The moment I plug in the Ethernet cable this is what I got


Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 24
BCP1: 00000000001904FB
BCP2: FFFFF88009D3B248
BCP3: FFFFF88009D3AAA0
BCP4: FFFFF88001424CCC
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\071712-28953-01.dmp
C:\Users\Office\AppData\Local\Temp\WER-171538-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

I will also post the latest dmp file

This should be the latest Dump info from the BSOD when I plugged in the Ethernet Cable after removing suggested software and updating Drivers.

Hard Disk Problems:

Your crash primarily indicates hard disk problems. This could mean hard disk corruption, bad sectors, a failing hard disk, Windows files or registry corruption, viruses, or memory problems.

• If you are overclocking any hardware, please stop.
  
  
• Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log (you may need to search for wininit instead of chkdsk).
  For any drives that do not give the message:

  Windows has checked the file system and found no problems

  run disk check again as above. In other words, if it says:

  Windows has made corrections to the file system

  after running the disk check, run the disk check again.
  
  
• Run all Basic tests with SeaTools: S.M.A.R.T. Check, Short Drive Self Test, Drive Information, Short Generic, and Long Generic. Run the tests for all HDDs.

  SeaTools for Windows
  
  SeaTools for DOS

• If you have an SSD, make sure the following are up to date:
  • SSD firmware
  • BIOS Version
  • Chipset Drivers
  • Hard disk controller drivers/SATA drivers
  • If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.
  
  
• Check Windows for corruption. Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations. Use OPTION THREE of SFC /SCANNOW Command - System File Checker to provide us with the sfcdetails.txt file if errors occur.
  
  
• Download and install Malwarebytes, update it, do not start the free trial, and then run a full scan. Also run a full scan with your antivirus software installed on your system. If you do not have antivirus software installed, see the Good and Free system security combination. for better security steps and scanning tools. Make sure to update the security software before running the full scan.
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
     Warning

  Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. WARNING: The steps that follow can void your warranty!!!
  
  For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.
  Once these steps have been followed, it is safe to remove and replace components within your computer.

Main_Striped Data:

I note that you are using a Main_Striped data method. That may be the source if your problems. Why RAID is (usually) a Terrible Idea - Puget Custom Computers

All the drives look ok on Chkdsk but here is the log for the scan of the C: Drive (system drive). Still running through the other tests and I will have to do a reinstall to change the Raid Setting but I will get back to that for advise on the reinstall later. will re-run chkdsk on the C: drive tonight


Checking file system on C:
The type of the file system is NTFS.
Volume label is System.

A disk check has been scheduled.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 5)...
432640 file records processed. File verification completed.
347 large file records processed. 0 bad file records processed. 2 EA records processed. 60 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)...
498986 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)...
432640 file SDs/SIDs processed. Cleaning up 406 unused index entries from index $SII of file 0x9.
Cleaning up 406 unused index entries from index $SDH of file 0x9.
Cleaning up 406 unused security descriptors.
Security descriptor verification completed.
33174 data files processed. CHKDSK is verifying Usn Journal...
33564880 USN bytes processed. Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
432624 files processed. File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
427952035 free clusters processed. Free space verification is complete.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.

1953517567 KB total disk space.
240930864 KB in 393123 files.
186572 KB in 33175 indexes.
0 KB in bad sectors.
591987 KB in use by the system.
65536 KB occupied by the log file.
1711808144 KB available on disk.

4096 bytes in each allocation unit.
488379391 total allocation units on disk.
427952036 allocation units available on disk.

Internal Info:
00 9a 06 00 45 81 06 00 45 25 0b 00 00 00 00 00 ....E...E%......
0c 01 00 00 3c 00 00 00 00 00 00 00 00 00 00 00 ....<...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Windows has finished checking your disk.
Please wait while your computer restarts.

Sorry for the delay in replying but the PC died completely and the short version of the story is I replaced the power supply and the video card (replaced video card due to the new power supply not being strong enough for the old video card) and the pc is stable again and has not crashed once. I will be replacing the power supply this weekend and will try the old video card to see if it was the power supply or video card that was the cause of the issue. Will advise the out come

After 48 hours of testing the issue has been isolated to the power supply. I have the old(original) video card back in so now the hardware setup is the same as when the problem started with the exception of the power supply and all is working well.

Thank you for your assistance will certainly come again if I get stuck with other issues