BSOD while Reenabling Ethernet/possibly caused by failing hard disk?

[xohn]

A BSOD happened around a week ago while re-enabling my ethernet adapter on my laptop. This is the first and only time my computer has blue screened as of now.

A previous disk check(yesterday) found bad sectors within my hard drive(might be a sign of a bad hard disk?). Could that have been the cause of the BSOD?

 

[ICIT2LOL]

Xohn now how did you run that chkdsk if you ant to run it thoroughly then follow this
http://www.sevenforums.com/tutorials/433-disk-check.html and use the switches /f and /r in Option 2

If you feel the drive is faling then it may be making some odd and loud noises so to check the drive itself try these
SeaTools for Windows | Seagate and to do a physical drive test (it's surface) use the Partition Wizard surface test
Free Partition Manager for Window PC | MiniTool Partition Wizard Home Edition see my pic

 

[xohn]

The bad sectors has increased from 20kb to 24kb, but the drive doesn't seem to be making weird noises?

 

[ICIT2LOL]

Yep now just because it is not making any odd noises doesn't necessarily mean it isn't failing I just mentioned that to eliminate anything mechanically failing.

The increase in bad sectors just what test were you using? If you haven't run either the Seagate or Partition Wizard ones then I would suggest the Seagate then the Partition Wizard ones in that order because the surface test takes a while to complete.

It might be an idea to send the dump files too http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html as these may give us direct pointers to the problem.

 

[Golden]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {0, 2, 8, 0}

*** WARNING: Unable to verify timestamp for bflwfx64.sys
*** ERROR: Module load completed but symbols could not be loaded for bflwfx64.sys
Probably caused by : bflwfx64.sys ( bflwfx64+287a )

Followup: MachineOwner
---------

0: kd> lmvm bflwfx64
start             end                 module name
fffff880`04e7b000 fffff880`04fce000   bflwfx64 T (no symbols)           
    Loaded symbol image file: bflwfx64.sys
    Image path: \SystemRoot\system32\DRIVERS\[B][COLOR="Red"]bflwfx64.sys[/COLOR][/B]
    Image name: bflwfx64.sys
    Timestamp:        [COLOR="red"][B]Thu Feb 14 03:34:08 2013[/B][/COLOR] (511BC788)
    CheckSum:         0001B330
    ImageSize:        00153000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Name	[00000015] Killer e2200 PCI-E Gigabit Ethernet Controller (NDIS 6.20)

The Bigfoot Networks driver is outdated. Drivers for this device are now provided by Qualcomm - locate and install an updated driver from here:
Driver Downloads | Qualcomm Atheros, Inc.

There is no evidence for a failing hard disk in the .dmp file nor eventviewer log file. Performing a chkdsk /R as suggested will probably address the issue:

1. Click Start

2. In the search box, type cmd
3. In the list that appears, right-click on cmd.exe and choose Run as administrator
4. In the command window that opens, type chkdsk /R and hit enter.

You will be prompted whether you wish to schedule a chkdsk scan at next startup, type 'Y' and hit enter. Now restart your computer and chkdsk will automatically run.

More detail: http://www.sevenforums.com/tutorials/433-disk-check.html

 

[ICIT2LOL]

Hmm didn't notice a dump Golden and the /f /r I did suggest and what I was presuming was throwing up the tra bad sectors. The tests I only added as an addon in case.

 

[xohn]

There is no evidence for a failing hard disk in the .dmp file nor eventviewer log file. Performing a chkdsk /R as suggested will probably address the issue:

This really puts my mind at ease! I read up on the ethernet adapter and it turns out many others were having the similar problems (which I should done first, my bad ).

--
About the hard disk programs, thanks but I've been pretty busy so sorry for the lack of updates. I should be running those programs later tonight to make sure.