Right Click Properties Crash

[cstebila]

Hey guys,

Been having an issue where upon right clicking (a file, folder, drive, you name it) and clicking properties Windows Explorer will crash.

Heard people were having a similar problem when only right clicking, many solved this by going into their registry and deleting some values. Since their problem was similar to mine, I went ahead and deleted some values under

HKEY_CLASSES_ROOT\*\shellex\ContextMenuHandlers

however, this doesn't seem that is the problem. Any ideas?

UPDATE: After running sfc/scannow I receive a BSOD, upon reboot the following message is displayed. Also I've attached the dump file

Thanks for even reading this, any help is extremely appreciated,

Camaren

 

[Jonathan_King]

Hello,

Have you tried a system files check?

Open an elevated command prompt and enter sfc /scannow.

You might also try a repair install.

 

[cstebila]

Hey Jonathan_King thanks for such a quick reply,

Just tried running this, and got a blue screen after 12% something along the lines of: in page kernel error

Computer rebooted and displayed:

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

Additional information about the problem:
BCCode: 7a
BCP1: C0415D68
BCP2: C0000185
BCP3: 17130860
BCP4: 82BAD5A6
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\110610-16707-01.dmp
C:\Users\usernameremoved\AppData\Local\Temp\WER-28189-0.sysdata.xml

 

[Capt.Jack Sparrow]

Hello and Welcome !

Download the ShellExView is an excellent tool to view and manage all installed shell extensions. The rule is to disable non-Microsoft context menu handlers *one-by-one* and verify if the problem is solved. If disabling one does not solve the problem, undo the disabled item and disable the next non-Microsoft handler. Do the same until the problem is solved and finally identify the culprit. Scroll right to see the Company Name column in ShellExView.

More steps: http://www.sevenforums.com/crash-lo...bleshooting-explorer-exe-crashing-issues.html

Hope this helps,
Captain

 

[cstebila]

Capt.JackSparrow appreciate the help (awesome username btw)

Quick question, did you notice I am specifically having a problem only when clicking on "Properties," in the right click menu? Either way, I'll try and disable some of the shell extensions once more.

Thanks again,

Camaren

edit: Disabled all non-Microsoft shell extensions, problem persists.

 

[Capt.Jack Sparrow]

Did you try SFC /SCANNOW command ?

 

[cstebila]

While running SFC/SCANNOW the computer freezes, bluescreens, and reboots with a prompt. Promp it displayed below, also zipped dump file attached.

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

Additional information about the problem:
BCCode: 7a
BCP1: C0415D68
BCP2: C0000185
BCP3: 17130860
BCP4: 82BAD5A6
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\110610-16707-01.dmp
C:\Users\usernameremoved\AppData\Local\Temp\WER-28189-0.sysdata.xml

Thanks again everyone who is helping! (or can help)

 

[cstebila]

Sorry for double post.

 

[Capt.Jack Sparrow]

Hello,

Seems like it might be your Hard Drive. Go to this link Hardware Diagnostic !! « Captain Debugger and follow the options for Hard Drive Diagnostic. Post us the results.

Bugcheck:

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in.  Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: c0415d68, lock type that was held (value 1,2,3, or PTE address)
Arg2: c0000185, error status (normally i/o status code)
Arg3: 17130860, current process (virtual address for lock type 3, or PTE)
Arg4: 82bad5a6, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

Debugging Details:
------------------

GetPointerFromAddress: unable to read from 82b74700

ERROR_CODE: (NTSTATUS) 0xc0000185 - The I/O device reported an I/O error.

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR:  0x7a_c0000185

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  8ab32c68 -- (.trap 0xffffffff8ab32c68)
ErrCode = 00000010
eax=851ac1f8 ebx=00000000 ecx=00000009 edx=00000000 esi=00000314 edi=84b18168
eip=82bad5a6 esp=8ab32cdc ebp=8ab32d00 iopl=0         nv up ei ng nz na po cy
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010283
nt!PiProcessReenumeration:
82bad5a6 0000            add     byte ptr [eax],al          ds:0023:851ac1f8=??
Resetting default scope

LOCK_ADDRESS:  82b71f60 -- (!locks 82b71f60)

Resource @ nt!PiEngineLock (0x82b71f60)    Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE: 
	Lock address  : 0x82b71f60
	Thread Count  : 0
	Thread address: 0x00000000
	Thread wait   : 0x0

LAST_CONTROL_TRANSFER:  from 82ac061a to 82ae8d10

STACK_TEXT:  
8ab32ac4 82ac061a 0000007a c0415d68 c0000185 nt!KeBugCheckEx+0x1e
8ab32b38 82ab80e5 9b9fe6b4 8ab32b90 82b40540 nt!MiWaitForInPageComplete+0x2fd
8ab32bcc 82a93e5f 82b40540 82bad5a6 9b9fe620 nt!MiIssueHardFault+0x3b2
8ab32c50 82a52638 00000008 82bad5a6 00000000 nt!MmAccessFault+0x2656
8ab32c50 82bad5a6 00000008 82bad5a6 00000000 nt!KiTrap0E+0xdc
8ab32d00 82a79f3b 00000000 00000000 848daa70 nt!PiProcessReenumeration
8ab32d50 82c1a6bb 00000001 94fe3208 00000000 nt!ExpWorkerThread+0x10d
8ab32d90 82acc0f9 82a79e2e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    82bad000-82bad025  38 bytes - nt!IopPnPDispatch+225
	[ 00 00 8b 0d 1c 20 b7 82:9c fe 95 01 00 00 96 01 ]
    82bad028-82bad02f  8 bytes - nt!IopPnPDispatch+24d (+0x28)
	[ 8b 59 14 8b 4e 04 83 e9:00 00 00 00 00 00 00 00 ]
    82bad031-82bad033  3 bytes - nt!IopPnPDispatch+256 (+0x09)
	[ 0f 84 80:c0 fd 7f ]
    82bad037-82bad06e  56 bytes - nt!IopPnPDispatch+25c (+0x06)
	[ 49 49 74 31 49 74 79 49:00 00 00 00 00 00 00 00 ]
    82bad071-82bad0b4  68 bytes - nt!IopPnPDispatch+296 (+0x3a)
	[ c0 75 3c 85 ff 74 38 8b:00 00 00 00 00 00 00 00 ]
    82bad0b7-82bad0df  41 bytes - nt!IopPnPDispatch+2dc (+0x46)
	[ 0f b7 43 14 68 50 70 64:00 00 00 00 00 00 00 00 ]
    82bad0e1-82bad0e2  2 bytes - nt!IopPnPDispatch+306 (+0x2a)
	[ 50 6a:00 00 ]
    82bad0e4-82bad104  33 bytes - nt!IopPnPDispatch+309 (+0x03)
	[ 57 e8 56 dd e9 ff 8b 43:00 00 00 00 00 00 00 00 ]
    82bad107-82bad11d  23 bytes - nt!IopPnPDispatch+32c (+0x23)
	[ 8b 54 24 18 66 83 f9 5c:00 00 00 00 00 00 00 00 ]
    82bad120-82bad130  17 bytes - nt!IopPnPDispatch+345 (+0x19)
	[ 66 89 0a 42 42 40 40 0f:00 00 00 00 00 00 00 00 ]
    82bad134-82bad139  6 bytes - nt!IopPnPDispatch+359 (+0x14)
	[ 66 3b cf 0f 84 f6:00 00 00 00 00 00 ]
    82bad13d-82bad166  42 bytes - nt!IopPnPDispatch+362 (+0x09)
	[ 6a 02 5e 66 83 f9 5c 75:00 00 00 00 00 00 00 00 ]
    82bad16a-82bad17e  21 bytes - nt!IopPnPDispatch+38f (+0x2d)
	[ 8b 54 24 18 03 c6 66 89:00 00 00 00 00 00 00 00 ]
    82bad182-82bad1af  46 bytes - nt!IopPnPDispatch+3a7 (+0x18)
	[ 33 ff 47 39 7e 04 0f 85:00 00 00 00 00 00 00 00 ]
    82bad1b1-82bad1b4  4 bytes - nt!IopPnPDispatch+3d6 (+0x2f)
	[ 83 7c 24 14:00 00 00 00 ]
    82bad1b6-82bad1dd  40 bytes - nt!IopPnPDispatch+3db (+0x05)
	[ 0f 84 5e fc ff ff 68 50:00 00 00 00 00 00 00 00 ]
    82bad1df-82bad1e5  7 bytes - nt!IopPnPDispatch+404 (+0x29)
	[ 56 57 53 e8 18 dc 04:00 00 00 00 00 00 00 ]
    82bad1e7-82bad1ed  7 bytes - nt!IopPnPDispatch+40c (+0x08)
	[ 8b f8 85 ff 7d 46 6a:00 00 00 00 00 00 00 ]
    82bad1ef-82bad1fb  13 bytes - nt!IopPnPDispatch+414 (+0x08)
	[ ff 74 24 14 e8 0d de f7:00 00 00 00 00 00 00 00 ]
    82bad1fd-82bad21b  31 bytes - nt!IopPnPDispatch+422 (+0x0e)
	[ eb 34 8d 44 24 14 50 8d:00 00 00 00 00 00 00 00 ]
    82bad21d-82bad220  4 bytes - nt!IopPnPDispatch+442 (+0x20)
	[ 53 e8 59 de:00 00 00 00 ]
    82bad223-82bad227  5 bytes - nt!IopPnPDispatch+448 (+0x06)
	[ 8b f8 81 ff 34:00 00 00 00 00 ]
    82bad22a-82bad24a  33 bytes - nt!IopPnPDispatch+44f (+0x07)
	[ c0 75 06 33 ff 89 7c 24:00 00 00 00 00 00 00 00 ]
    82bad24c-82bad24d  2 bytes - nt!IopPnPDispatch+471 (+0x22)
	[ 8d 49:00 00 ]
    82bad24f-82bad28e  64 bytes - nt!IopPnPDispatch+474 (+0x03)
	[ 90 fb cf ba 82 fb cf ba:00 00 00 00 00 00 00 00 ]
    82bad291-82bad294  4 bytes - nt!NtLoadDriver+18 (+0x42)
	[ 8a 86 3a 01:00 00 00 00 ]
    82bad297-82bad29f  9 bytes - nt!NtLoadDriver+1e (+0x06)
	[ 88 45 e0 3a c3 0f 84 0b:00 00 00 00 00 00 00 00 ]
    82bad2a2-82bad2b4  19 bytes - nt!NtLoadDriver+29 (+0x0b)
	[ ff 75 e0 ff 35 44 56 d7:00 00 00 00 00 00 00 00 ]
    82bad2b6-82bad2bb  6 bytes - nt!NtLoadDriver+3d (+0x14)
	[ 84 c0 75 0a b8 61:00 00 00 00 00 00 ]
    82bad2be-82bad2c1  4 bytes - nt!NtLoadDriver+45 (+0x08)
	[ c0 e9 58 01:00 00 00 00 ]
    82bad2c4-82bad2ef  44 bytes - nt!NtLoadDriver+4b (+0x06)
	[ 89 5d fc 8b 45 08 8b 0d:00 00 00 00 00 00 00 00 ]
    82bad2f2-82bad2f5  4 bytes - nt!NtLoadDriver+79 (+0x2e)
	[ c0 e9 24 01:00 00 00 00 ]
    82bad2f8-82bad300  9 bytes - nt!NtLoadDriver+7f (+0x06)
	[ f6 c1 01 74 06 e8 55 0f:00 00 00 00 00 00 00 00 ]
    82bad302-82bad377  118 bytes - nt!NtLoadDriver+89 (+0x0a)
	[ cc 0f b7 45 d4 8d 14 01:00 00 00 00 00 00 00 00 ]
    82bad37a-82bad383  10 bytes - nt!NtLoadDriver+100 (+0x78)
	[ c0 e8 d4 f5 e9 ff 8b 45:00 00 00 00 00 00 00 00 ]
    82bad385 - nt!NtLoadDriver+10b (+0x0b)
	[ 8b:00 ]
    82bad387-82bad3df  89 bytes - nt!NtLoadDriver+10d (+0x02)
	[ 89 45 dc 33 c0 40 c3 8b:00 00 00 00 00 00 00 00 ]
    82bad3e3-82bad422  64 bytes - nt!NtLoadDriver+169 (+0x5c)
	[ eb 26 c7 45 b0 29 d4 ba:00 00 00 00 00 00 00 00 ]
    82bad424-82bad458  53 bytes - nt!NtLoadDriver+1aa (+0x41)
	[ 90 90 90 90 90 8b ff 55:00 00 00 00 00 00 00 00 ]
    82bad45a - nt!IopLoadUnloadDriver+31 (+0x36)
	[ 02:00 ]
    82bad45c-82bad465  10 bytes - nt!IopLoadUnloadDriver+33 (+0x02)
	[ 8d 44 24 18 50 c7 44 24:00 00 00 00 00 00 00 00 ]
    82bad469-82bad472  10 bytes - nt!IopLoadUnloadDriver+40 (+0x0d)
	[ 89 5c 24 28 c7 44 24 30:00 00 00 00 00 00 00 00 ]
    82bad475-82bad496  34 bytes - nt!IopLoadUnloadDriver+4c (+0x0c)
	[ 89 5c 24 34 89 5c 24 38:00 00 00 00 00 00 00 00 ]
    82bad499-82bad49e  6 bytes - nt!IopLoadUnloadDriver+70 (+0x24)
	[ 8b f8 81 ff 65 03:00 00 00 00 00 00 ]
    82bad4a0-82bad4ac  13 bytes - nt!IopLoadUnloadDriver+77 (+0x07)
	[ c0 75 06 8b 7c 24 14 eb:00 00 00 00 00 00 00 00 ]
    82bad4ae-82bad4b2  5 bytes - nt!IopLoadUnloadDriver+85 (+0x0e)
	[ c0 75 05 bf 34:00 00 00 00 00 ]
    82bad4b5-82bad4b8  4 bytes - nt!IopLoadUnloadDriver+8c (+0x07)
	[ c0 e8 02 2c:00 00 00 00 ]
    82bad4bb-82bad4d0  22 bytes - nt!IopLoadUnloadDriver+92 (+0x06)
	[ 53 89 7e 28 53 83 c6 10:00 00 00 00 00 00 00 00 ]
    82bad4d2-82bad4f0  31 bytes - nt!IopLoadUnloadDriver+a9 (+0x17)
	[ 90 90 90 90 90 8b ff 55:00 00 00 00 00 00 00 00 ]
    82bad4f2-82bad4fd  12 bytes - nt!PipForAllDeviceNodesCallback+1b (+0x20)
	[ 74 0d 56 68 d7 d4 ba 82:00 00 00 00 00 00 00 00 ]
WARNING: !chkimg output was truncated to 50 lines. Invoke !chkimg without '-lo [num_lines]' to view  entire output.
3713 errors : !nt (82bad000-82badfff)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  LARGE_4096

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE_4096

BUCKET_ID:  MEMORY_CORRUPTION_LARGE_4096

Hope this helps,
Captain

 

[cstebila]

Going right now, thanks so much for the help! (will edit as soon as I get results)

edit: Sorry give me a bit, I'm going to backup my files first. However I will be back tonight, (i don't expect you to wait however)

Thanks for the tips so far, appreciate it!

 

[cstebila]

Bump.

Current situation (any help is extremely appreciated): Every time I right click and click properties explorer crashes and or BSOD. The dump file is posted above (thanks Sparrow!)

I ran a chkdsk in read only mode and receive the following.

Checking file system on C: The type of the file system is NTFS. WARNING! F parameter not specified. Running CHKDSK in read-only mode. WARNING! C parameter specified. Your drive may still be corrupt even after running CHKDSK. CHKDSK is verifying files (stage 1 of 3)... The attribute length 0x1a for attribute of type 0x0 and instance tag 0x30 is too small. The minimum value is 0x44. Attribute record (48, "") from file record segment 7072 is corrupt. 110848 file records processed. File verification completed. 107 large file records processed. Errors found. CHKDSK cannot continue in read-only mode.
00B10100A3700100FCA70200000000007D0100002C0000000000000000000000

I tried running it in a non-read only mode but couldnt find the log file anywhere. Also when I try to run a sfc/scannow it crashes at 12%.

 

[Capt.Jack Sparrow]

Hello,

Try to Download the Diagnostic Tool for Hard Drive vendor and run the Diagnostic and see if that picks up something. More likely it might be a bad Hard drive.

Hope this helps,
Captain

 

[Hopalong X]

Capt. Jack

Right here.
WD Support > Downloads > WD Scorpio & AV-25 > WD Scorpio Blue

Do not select the WRITE ZEROS test. It will erase everything. Run the Quick Test first in instruction list.
Then let us know results then you can go to Extended Test if Capt. Jack wants.

Sound good Capt. Jack?

WD website.

Instructions

1. Download the Windows Data Lifeguard Diagnostics, WinDlg_122.zip
2. Extract and run the program, WinDlg.exe. If running Windows Vista, you will need to Right-Click on the WinDlg.exe file and choose to Run As Administrator.
3. Read and accept the license agreement to continue.
4. On the main program screen, there are two windows. In the top window, you will see the drives in your system, that are available for testing. The model number, serial number, and capacity of each drive will be displayed. In the bottom window, the partition information for the selected drive will be displayed.
5. Highlight the drive and select the icon on the top row to test or run SMART status.
6. The DLGDIAG - Select an Option window appears.
7. You will see the following options:
   • QUICK TEST - performs SMART drive quick self-test to gather and verify the Data Lifeguard information contained on the drive.
   • EXTENDED TEST - performs a Full Media Scan to detect bad sectors. Test may take several hours to complete depending on the size of the drive.
   • WRITE ZEROS - writes zeros to the drive with options of Full Erase and Quick Erase. File system and data will be lost.
   • VIEW TEST RESULT - displays the latest test results.
8. Select the test you wish to perform and click the Start button.
9. When the test completes, you will be notified with a pass/fail message. Click the Close button.

 

[cstebila]

Upon opening Western Digital's Diagnostic Application the user interface shows I have a drive the passes "SMART Status."

http://img.photobucket.com/albums/v11/coolhaircam/1st.jpg?t=1289437136


However upon running the program's "Quick Test" the drive does not pass, and the following reason is given:

http://img.photobucket.com/albums/v11/coolhaircam/then.jpg?t=1289437118

Whats even weirder is I marked both my partitions (volumes?) as dirty and ran a chkdsk, and the results are below. This time around it doesn't seem it found any problems?


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


One of your disks needs to be checked for consistency. You
may cancel the disk check, but it is strongly recommended
that you continue.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 3)...
110848 file records processed. File verification completed.
159 large file records processed. 0 bad file records processed. 2 EA records processed. 44 reparse records processed. CHKDSK is verifying indexes (stage 2 of 3)...
152692 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 3)...
110848 file SDs/SIDs processed. Cleaning up 86 unused index entries from index $SII of file 0x9.
Cleaning up 86 unused index entries from index $SDH of file 0x9.
Cleaning up 86 unused security descriptors.
Security descriptor verification completed.
20923 data files processed. CHKDSK is verifying Usn Journal...
36886920 USN bytes processed. Usn Journal verification completed.
Windows has checked the file system and found no problems.

86960127 KB total disk space.
53903444 KB in 74069 files.
42804 KB in 20924 indexes.
0 KB in bad sectors.
216259 KB in use by the system.
65536 KB occupied by the log file.
32797620 KB available on disk.

4096 bytes in each allocation unit.
21740031 total allocation units on disk.
8199405 allocation units available on disk.

Internal Info:
00 b1 01 00 1b 73 01 00 c1 ae 02 00 00 00 00 00 .....s..........
78 01 00 00 2c 00 00 00 00 00 00 00 00 00 00 00 x...,...........
00 00 00 00 00 00 00 00 00 00 06 00 e0 6d 10 00 .............m..

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

other volume scan

Checking file system on D:
The type of the file system is NTFS.
Volume label is me.


One of your disks needs to be checked for consistency. You
may cancel the disk check, but it is strongly recommended
that you continue.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 3)...
49408 file records processed. File verification completed.
247 large file records processed. 0 bad file records processed. 0 EA records processed. 0 reparse records processed. CHKDSK is verifying indexes (stage 2 of 3)...
58716 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 3)...
49408 file SDs/SIDs processed. Security descriptor verification completed.
4655 data files processed. CHKDSK is verifying Usn Journal...
36901472 USN bytes processed. Usn Journal verification completed.
Windows has checked the file system and found no problems.

401319764 KB total disk space.
321255556 KB in 42141 files.
23392 KB in 4656 indexes.
0 KB in bad sectors.
163956 KB in use by the system.
65536 KB occupied by the log file.
79876860 KB available on disk.

4096 bytes in each allocation unit.
100329941 total allocation units on disk.
19969215 allocation units available on disk.

Internal Info:
00 c1 00 00 d9 b6 00 00 ad 42 01 00 00 00 00 00 .........B......
ff 64 00 00 00 00 00 00 00 00 00 00 00 00 00 00 .d..............
11 00 00 00 00 00 00 00 03 00 00 00 00 00 00 00 ................



Thanks again for keeping up with this guys, to sum up

1.) Crash or BSOD when right clicking anything and clicking properties
2.) Crash or BSOD when right clicking "Computer" on Win 7 Start-Menu
3.) Hard Drive "Passes" but then turns out not too pass
4.) chkdsk finds something wrong when in read-only mode, but when volumes are marked dirty and chkdsk runs, nothing is seemingly found

I really didn't want to have to re-install Win 7, as I've done it some 4 times already in the past, but I can do it again... just was really hoping that was a last option.

 

[LiquidSnak]

Well, I believe that you have a hardware issue. The drive seems to be going out, so I recommend backing up important files. After this is done, I would give a repair installation a try, since it cannot hurt anything. If that fails, your drive might need replacing.

 

[cstebila]

Bump, anyone else any idea?

 

[Capt.Jack Sparrow]

Hello,

The test doesn't look good. I'm no hardware expert i looked about this error this is what i found. Try running MHDD This software can make precise diagnostic of the mechanical part of a drive, view SMART attributes, perform Low-level format, bad sector repair, different tests and tens of other functions HDDGURU: MHDD that also fails then If the drive is under warranty I would definitely RMA it.

Hope this helps,
Captain

 

[cstebila]

Thanks Capt.Jack.Sparrow will run this tomorrow morning! Also Rep added

 

[Dave76]

edit: Sorry give me a bit, I'm going to backup my files first.

I hope have all of your important data backed up.

If there is anything you want to keep on that HDD, backup or save it now.

Data Lifeguard Diagnostic Utility

Page: DLGDIAG FOR DOS – 15

Error/Status Codes
Go to support.wdc.com for further information on many of the error codes listed below as well
as error codes from previous versions of Data Lifeguard Diagnostics.
If you encounter the same error code more than once after restesting, create an RMA
(see “Enter & Print RMA Information” on page 14).

Quick Test — performs a quick S.M.A.R.T. self-test to gather and verify the Data
Lifeguard information contained on the drive.

Knowledge Base Diagnostic Error Codes

0001 - 0008, 0015 SMART Error
Self Monitoring, Analysis, and Reporting Technology (SMART) Error returned during SMART Status/Self Test Command. The drive is defective.
Status: Replace Drive

Your error was 07 (0007)


What is S.M.A.R.T. and S.M.A.R.T. failure?

Note: A S.M.A.R.T. failure indicates that your drive is at risk for imminent failure. If your drive has failed S.M.A.R.T. and you are still able to access your data WD recommends backing up your data as quickly as possible. Once backed up, you should replace your drive.

Frequently Asked Questions

I hope it's still under warranty.

 

[cstebila]

big update: If you remember every time I right click anything, and click properties my computer will either crash or get a BSOD. When checking dump files, etc, it looked like the problem was the hard drive.

However, while backing up my files, I did a right click on my External Hard Drive, right clicked, and clicked "properties," and Windows crashed again. Could this mean, that its potentially not a problem with my internal drive, since it replicated itself on my external?

I'm going to try and find a good freeware virus scanner and see what comes up. Any thoughts on this new development is extremely appreciated!

Thanks guys,

Camaren