Western Digital Data LifeGuard causes BSOD halfway through the extended test - Hardware & Software

I haven't experienced any problems earlier, and I have used the HDD with caution, so I don't understand why It'd give up on me now. Anyway, paranoid as I am, I decided to download and run Western Digital LifeGuard's extended test (It's supposed to find damaged sectors) on my Western Digital Scorpio Blue just in case. Everything works till' 30 minutes into the test (Around 50% done) where the PC just BSODs. I reboot the PC and run the test again. Yet again, BSOD at around 50%. Seeing as I'm really fucking paranoid now, I've been running different instances of CHKDSK and SMART scans the entire afternoon. CHKDSK /v tells me there's 0 kilobytes of damaged sectors, and CHKDSK /f doesn't report any errors. Western Digital LifeGuard's SMART scan tells me everything's OK with the drive, as do SpeedFan's SMART scan and HD Tune Pro. Dump files: [url]https://rapidshare.com/files/2728724216/070711-26566-01.dmp[/url] [url]https://rapidshare.com/files/3206767969/070711-35677-01.dmp[/url] Is my HDD dying?

Does the hard drive make any strange noises? If not then it's most likely that the hard drive is ok and it's just the LifeGuard program which is crashing

The next time i boot into windows i'll look into the dump files you posted and find the cause of the BSOD's.

[QUOTE=djjkps3;30975535]Does the hard drive make any strange noises? [/QUOTE] Nope. Except for your usual HDD read/write noise it's completely silent. No weird clicks or anything.

Windows can't really detect low-level HDD problems anymore since most drivers aren't allowed in Ring 0 (direct hardware access.) The last windows OS that could do direct hardware access was Windows 98SE/ME, and they could detect HDD defects (due to being based on DOS.) that being said, HDD problems [I]usually[/I] don't cause BSODs because Windows is dumb and will try and read a sector over and over again if it has trouble with it and usually end up with the computer freezing or locking up instead. If you want to look at S.M.A.R.T. data, get a program like HDD Tune, it will tell you various attributes of the drives in the computer (including how many bad sectors the drive has.) But even if the drive does have bad sectors, it doesn't mean the drive is failing. The surface of the disk has imperfections that wear out more quickly than the rest of the disk, and manufacturers of drives compensate for this by making a reserved area on the disk to reallocate bad sectors with spares. As long as the bad sector count isn't [I]too[/I] high, you're fine. More than 50 is an indication of a really old or bad disk, and if you have more than 100, you need to replace the disk.

[QUOTE=bohb;30984121] If you want to look at S.M.A.R.T. data, get a program like HDD Tune [/QUOTE] I'll just assume you mean HD Tune Pro, which I've already used. Some results: [img]http://gyazo.com/fcb18ea79d48e3010cadc0285ff1ad6d.png[/img] [img]http://gyazo.com/0eff866eeceab250a23fbd3bf2a0672c.png[/img] [img]http://gyazo.com/d66d71539f3c0546e3abdcd7ce9c1ce7.png[/img] (I did an extended scan, aswell, gave me the same result).

Yeah looks like your hard drive is working fine

[code] Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [D:\Naelstrof\Downloads\dumps\070711-26566-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*D:\SYMBOLS64*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16792.x86fre.win7_gdr.110408-1633 Machine Name: Kernel base = 0x82c3b000 PsLoadedModuleList = 0x82d7a570 Debug session time: Thu Jul 7 10:04:30.935 2011 (GMT-6) System Uptime: 0 days 0:37:41.027 Loading Kernel Symbols ............................................................... ................................................................ ............................. Loading User Symbols Loading unloaded module list ..... 1: kd> !analyze ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 24, {1904fb, 80da9640, 80da9220, 82d5371a} Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+12a ) Followup: Pool_corruption ---------[/code] [code]Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [D:\Naelstrof\Downloads\dumps\070711-35677-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*D:\SYMBOLS64*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16792.x86fre.win7_gdr.110408-1633 Machine Name: Kernel base = 0x82c3d000 PsLoadedModuleList = 0x82d7c570 Debug session time: Thu Jul 7 08:51:51.982 2011 (GMT-6) System Uptime: 0 days 0:10:14.074 Loading Kernel Symbols ............................................................... ................................................................ ............................. Loading User Symbols Loading unloaded module list ..... 0: kd> !analyze ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {d08ec033, 0, 82d5571a, 2} Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+12a ) Followup: Pool_corruption ---------[/code] I advise reading this and following instructions IF you're still getting bluescreens: [url]http://www.sevenforums.com/crashes-debugging/82719-win-7-pro-bsod-pool_corruption.html[/url]

Well, aslong as I don't use the program everything works just fine, something which doesn't really bother me seeing as I've uninstalled it anyway. Yesterday the PC was on for over 15 hours without any problems. So, is everything okay, then?

0x24 BCC= NTFS_FILE_SYSTEM 0x50 BCC= PAGE_FAULT_IN_NONPAGED_AREA Both are saying file system coruption in some way. Open a command prompt and type in SFC /SCANNOW and press enter

[QUOTE=bohb;30984121] that being said, HDD problems [I]usually[/I] don't cause BSODs because Windows is dumb and will try and read a sector over and over again if it has trouble with it and usually end up with the computer freezing or locking up instead. [/QUOTE] I've had about a dozen or so blue screens in the past month due to hard drive damage. Along with a dozen or so freeze-ups.