BSOD When External HDD Plugged In

Area Effect · 19 Feb 2012

I got a BSOD the other day and eventually isolated it to happening whenever my external HDD is plugged in. It happens pretty quickly, usually right after the autoplay window pops up.

The BSOD error is PAGE_FAULT_IN_NONPAGED_AREA and you can view the actual screen here.

I assume my HDD is just damaged or something. If so, is it salvageable at all or do I need a new one?

Attached is all the memory dumps and what not

I'm running Windows 7 Home Premium x64 OEM.

Thanks in advance for any help!

usasma · 19 Feb 2012

If you're concerned about the data on the hard drive, don't do anything with it until you've recovered (or attempted to recover) the data. Each use of the drive increases the chance that you may lose data.

Most external hard drives fail for one of three reasons:
- bad cord
- bad interface board (between the cord and the actual hard drive inside the case)
- bad hard drive

Have you checked the cord on the external drive? Have you tried another cord?
How attached to this device are you? Do you know what kind of hard drive is inside the case? If so, can you slave that hard drive to another computer (if you break it out of the case)? Some external drives have standard IDE or SATA connectors - others have different connectors that can't easily be slaved to other systems.

Here's my canned speech about data recovery:

DATA RECOVERY:

Do not try to run anything on the hard drive until you recover the data. Any writing to the disk may destroy data.

Little damage - use a device to slave your hard drive to another system to copy the data over. I use this device at work (about $30 US): SATA and IDE Hard Drive & Optical Drive USB Adapter Kit COMBO Don't do this until you know that the hard drive inside the case will fit the adapter.

Moderate damage - use file/partition recovery software. There is a lot of freeware out there to do this - but I find it too confusing to use. I use GetDataBack from Data Recovery - Data Recovery Software - RAID Recovery - NAS Data Recovery It's free to see what it can recover, but it'll cost about $80 (US) to actually recover it.

Severe damage - contact a data recovery professional. Very expensive, but worth it if you absolutely must have the data back!

Then run this bootable hard drive diagnostic procedure: HD Diagnostic (read the details at the link) - Test ALL of the hard drives.

Then, start with a hard drive diagnostic on the external drive. Info on this here: HD Diagnostic
You'll have to do this with a bootable disk as the system won't let you plug it it while Windows is running.

More to follow after I review the uploaded files and run the memory dumps.......

usasma · 19 Feb 2012

Norton is showing up in Problem Devices in MSINFO32
Please do the following:

Anti-Virus Removal:
Please do the following:
- download a free antivirus for testing purposes: Free AntiVirus
- uninstall the Norton from your system (you can reinstall it, if so desired, when we're done troubleshooting)
- remove any remnants of Norton using this free tool: http://us.norton.com/support/kb/web_...080710133834EN
- IMMEDIATELY install and update the free antivirus, then check to ensure that the Windows Firewall is turned on.
- check to see if this fixes the BSOD's
NOTE: NEVER run more than 1 anti-virus, firewall, Internet Security/Security Center application at the same time.

All 11 errors are STOP 0x50 and all blame ntfs.sys
Fingerprint scanner driver dates from 2008. Please update. Driver Reference Table
JMicron memory card reader driver dates from 2008. Please update. Driver Reference Table
Infrared driver (IR) dates from 2008. Please update. Driver Reference Table

wacommousefilter.sys dates from 2007. I don't believe that there are any more recent drivers available (so you can't update it). Driver Reference Table

Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html

The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs:
3RD PARTY DRIVERS PRESENT IN THE DUMP FILES
- Create a System Restore Point prior to doing any of this. DO NOT mess with the drivers themselves - leave the Windows\System32\drivers directory alone unless we specifically direct you to it!
- Please either update the older drivers from the device manufacturer's website - or uninstall them from your system. Reference links are included below.
- DO NOT use Windows Update or the Update Drivers function of Device Manager.
- Please feel free to post back about any drivers that you are having difficulty locating.
- Windows Update exceptions may be noted below for Windows drivers.

Code:


amdxata.sys          Fri Mar 19 12:18:18 2010 (4BA3A3CA)
MpFilter.sys         Wed Apr 06 16:07:29 2011 (4D9CC801)
hpdskflt.sys         Fri May 13 14:47:02 2011 (4DCD7CA6)
ElbyCDIO.sys         Thu Dec 16 17:58:13 2010 (4D0A9985)
SynTP.sys            Thu May 27 17:41:36 2010 (4BFEE710)
enecir.sys           Thu Sep 04 05:47:58 2008 (48BFAECE)
GEARAspiWDM.sys      Mon May 18 08:17:04 2009 (4A1151C0)
Accelerometer.sys    Fri May 13 14:47:02 2011 (4DCD7CA6)
jmcr.sys             Thu Aug 07 05:01:36 2008 (489AB9F0)
btusbflt.sys         Thu Apr 08 21:11:36 2010 (4BBE7EC8)
VClone.sys           Sat Jan 15 11:21:04 2011 (4D31C970)
wacommousefilter.sys Fri Feb 16 13:12:17 2007 (45D5F401)
LMouFilt.Sys         Fri Sep 02 02:23:15 2011 (4E607653)
HpqKbFiltr.sys       Wed Apr 29 09:48:30 2009 (49F85AAE)
NETw5s64.sys         Wed Jan 13 11:37:13 2010 (4B4DF6B9)
Rt64win7.sys         Thu Feb 26 04:04:13 2009 (49A65B0D)
wacomvhid.sys        Mon Sep 21 19:29:14 2009 (4AB80C4A)
vfs101a.sys          Wed Feb 06 21:44:54 2008 (47AA70A6)
LHidFilt.Sys         Fri Sep 02 02:23:09 2011 (4E60764D)
stwrt64.sys          Wed Mar 24 00:01:24 2010 (4BA98E94)
nvhda64v.sys         Thu Jul 07 12:21:14 2011 (4E15DCFA)
LEqdUsb.Sys          Fri Sep 02 02:22:56 2011 (4E607640)
LHidEqd.Sys          Fri Sep 02 02:22:59 2011 (4E607643)
NisDrvWFP.sys        Wed Apr 06 16:08:53 2011 (4D9CC855)
nvlddmkm.sys         Sat Oct 15 02:07:55 2011 (4E99233B)
nvBridge.kmd         Fri May 20 23:58:23 2011 (4DD7385F)
MijXfilt.sys         Fri Dec 31 02:54:06 2010 (4D1D8C1E)
xusb21.sys           Wed Apr 08 10:28:44 2009 (49DCB49C)
MpNWMon.sys          Wed Apr 06 16:07:23 2011 (4D9CC7FB)

Code:


Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\021812-24226-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Feb 19 01:47:41.276 2012 (UTC - 5:00)
System Uptime: 0 days 7:32:32.086
Probably caused by : Ntfs.sys ( Ntfs!memmove+250 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_Ntfs!memmove+250
Bugcheck code 00000050
Arguments fffff981`396c26e8 00000000`00000000 fffff880`0123e460 00000000`00000005
BiosVersion = F.24
BiosReleaseDate = 06/16/2009
CPUID:        "Intel(R) Core(TM)2 Duo CPU     P8600  @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: 2394
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\021812-29624-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Feb 18 18:14:30.649 2012 (UTC - 5:00)
System Uptime: 0 days 0:01:47.460
Probably caused by : Ntfs.sys ( Ntfs!memmove+250 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_Ntfs!memmove+250
Bugcheck code 00000050
Arguments fffff981`070026e8 00000000`00000000 fffff880`01249460 00000000`00000005
BiosVersion = F.24
BiosReleaseDate = 06/16/2009
CPUID:        "Intel(R) Core(TM)2 Duo CPU     P8600  @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: 2394
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\021812-28532-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Feb 18 18:11:59.852 2012 (UTC - 5:00)
System Uptime: 0 days 0:05:41.662
Probably caused by : Ntfs.sys ( Ntfs!memmove+250 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_Ntfs!memmove+250
Bugcheck code 00000050
Arguments fffff981`1f5c26e8 00000000`00000000 fffff880`01269460 00000000`00000005
BiosVersion = F.24
BiosReleaseDate = 06/16/2009
CPUID:        "Intel(R) Core(TM)2 Duo CPU     P8600  @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: 2394
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\021812-35755-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Feb 18 18:05:17.063 2012 (UTC - 5:00)
System Uptime: 1 days 20:02:42.466
Probably caused by : Ntfs.sys ( Ntfs!memmove+250 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_Ntfs!memmove+250
Bugcheck code 00000050
Arguments fffff981`1d9c26e8 00000000`00000000 fffff880`0123c460 00000000`00000005
BiosVersion = F.24
BiosReleaseDate = 06/16/2009
CPUID:        "Intel(R) Core(TM)2 Duo CPU     P8600  @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: 2394
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\021612-21949-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Feb 16 22:02:01.546 2012 (UTC - 5:00)
System Uptime: 0 days 0:01:26.232
Probably caused by : Ntfs.sys ( Ntfs!memmove+250 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_Ntfs!memmove+250
Bugcheck code 00000050
Arguments fffff981`0fac26e8 00000000`00000000 fffff880`01229460 00000000`00000005
BiosVersion = F.24
BiosReleaseDate = 06/16/2009
CPUID:        "Intel(R) Core(TM)2 Duo CPU     P8600  @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: 2394
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\021612-28314-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Feb 16 21:59:38.697 2012 (UTC - 5:00)
System Uptime: 0 days 0:01:27.508
Probably caused by : Ntfs.sys ( Ntfs!memmove+250 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_Ntfs!memmove+250
Bugcheck code 00000050
Arguments fffff981`0dc426e8 00000000`00000000 fffff880`0123e460 00000000`00000005
BiosVersion = F.24
BiosReleaseDate = 06/16/2009
CPUID:        "Intel(R) Core(TM)2 Duo CPU     P8600  @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: 2394
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\021612-38875-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Feb 16 21:57:14.975 2012 (UTC - 5:00)
System Uptime: 0 days 0:01:29.785
Probably caused by : Ntfs.sys ( Ntfs!memmove+250 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_Ntfs!memmove+250
Bugcheck code 00000050
Arguments fffff981`0f5826e8 00000000`00000000 fffff880`0124d460 00000000`00000005
BiosVersion = F.24
BiosReleaseDate = 06/16/2009
CPUID:        "Intel(R) Core(TM)2 Duo CPU     P8600  @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: 2394
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\021612-45645-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Feb 16 21:54:14.768 2012 (UTC - 5:00)
System Uptime: 0 days 4:01:46.578
Probably caused by : Ntfs.sys ( Ntfs!memmove+250 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_Ntfs!memmove+250
Bugcheck code 00000050
Arguments fffff981`324826e8 00000000`00000000 fffff880`01261460 00000000`00000005
BiosVersion = F.24
BiosReleaseDate = 06/16/2009
CPUID:        "Intel(R) Core(TM)2 Duo CPU     P8600  @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: 2394
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\021612-22027-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Feb 16 17:51:18.480 2012 (UTC - 5:00)
System Uptime: 0 days 2:03:13.290
Probably caused by : Ntfs.sys ( Ntfs!memmove+250 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_Ntfs!memmove+250
Bugcheck code 00000050
Arguments fffff981`2d6426e8 00000000`00000000 fffff880`0124a460 00000000`00000005
BiosVersion = F.24
BiosReleaseDate = 06/16/2009
CPUID:        "Intel(R) Core(TM)2 Duo CPU     P8600  @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: 2394
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\021612-27768-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Feb 16 15:43:41.256 2012 (UTC - 5:00)
System Uptime: 0 days 0:01:26.067
Probably caused by : Ntfs.sys ( Ntfs!memmove+250 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_Ntfs!memmove+250
Bugcheck code 00000050
Arguments fffff981`0e5026e8 00000000`00000000 fffff880`0122e460 00000000`00000005
BiosVersion = F.24
BiosReleaseDate = 06/16/2009
CPUID:        "Intel(R) Core(TM)2 Duo CPU     P8600  @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: 2394
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\021612-34055-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Feb 16 15:41:13.686 2012 (UTC - 5:00)
System Uptime: 0 days 0:00:58.496
Probably caused by : Ntfs.sys ( Ntfs!memmove+250 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_Ntfs!memmove+250
Bugcheck code 00000050
Arguments fffff981`0e1826e8 00000000`00000000 fffff880`01233460 00000000`00000005
BiosVersion = F.24
BiosReleaseDate = 06/16/2009
CPUID:        "Intel(R) Core(TM)2 Duo CPU     P8600  @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: 2394
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Area Effect · 20 Feb 2012

Well it seems that updating those few drivers did it. Its been a few hours since I did that and no BSOD.

Also, it's odd that Norton would have shown up as I don't have it installed. Could that have just been remnants of it from when I first got the computer? I think it came with a trial version installed or something.

Thanks for the help. Atleast now if it does BSOD me again I'll know that has to just be the hard drive. Luckily there's nothing really important on it, just backups, so I can just get a new one.

usasma · 20 Feb 2012

You won't know it's the hard drive until you run the hardware diagnostic from here: Hardware Diags