Solved Hard Drive Clicking?

[gbu]

Ok thanks for the fast reply, i think im just going to go ahead with the clean install and see if i have any problems after that.

Thanks for the help everyone and rep to you all, you do a great job

 

[seavixen32]

That's probably a wise move Gbu, and thanks for the kind sentiments - it's appreciated by all of us.

Please post back if you get further problems after the reinstall.

 

[gbu]

I'm sure to back lol

Just a quick question before i do so though, i have a 64bit version of Win7 and was wondering if i should always install 64bit versions of software if there available or doesnt it matter if there 32bit?
I've had some like Flash Player try and auto install when it detects your not running it and previously it installed the 32bit version but ive recently learned you can download a 64bit as well?

 

[writhziden]

It doesn't really matter which version you install in most cases. As long as it is supported by the 64-bit operating system. Some programs that claim to be 32-bit are actually 16-bit and will only run on the 32-bit OS. These will give you a warning/error before installation in most cases and will not install. I do not use the 64-bit programs that much on my system. 64-bit software is still growing and has not yet completely caught up with the 64-bit OS option, in my opinion. There is a lot more support than there was two years ago for 64-bit applications, but it still seems like a work in progress.

In short, it should not matter which you install. If you want to use 64-bit applications more, they will utilize more of the resources available and may perform better. It is more of a preference at this point.

 

[seavixen32]

Windows 64-bit:

You can install either 32-bit applications or 64-bit applications. Both will run without any problem, but you should experience a performance boost with 64-bit software.

32-bit applications will default to Program Files (x86) whilst 64-bit applications will default to Program Files.

You will find two IE9 applications: one will be the 32-bit version and the other will be the 64-bit version.

As for Adobe Flash, the latest 64-bit version includes the 32-bit version as well.

Also, be aware that older 16-bit software will not run on a 64-bit operating system unless you use something like Virtual PC and XP Mode, for which you would at least need Windows 7 Professional.

To recap, if you have any 64-bit software, don't hesitate to install it.

 

[gbu]

Bit of an update, i did a clean install but whilst it was installing the 'clicking' noise was happening quite a bit and a lot louder, i managed to take off the front panel of my case and seeing as my hard drives are in the front it allowed me to place a screwdriver onto the side(safely) and the other end to my ear so i could hear and it was indeed the drive my OS is installed to.

I then disconnected the drive and made a fresh partition on my other drive and have since installed Windows to that drive and good to say theres no noise.

What i am a bit concerned about though is installing the updates as its been stuck on 18 of 81 now for nearly an hour trying to install .NET Framework 3.5.1, should it be taking that long?

 

[gbu]

The installation never completed and i had a BSOD appear!

I ran memory Diagnostics Tool from System Repair and it said there was a hardware problem.

im not sure whats going on as this is a clean install and it seems to be crashing worse then before

 

[writhziden]

Do you still have your bad hard disk connected to the computer?

 

[mjf]

You seem to have backed up which is good!
If the HDD is under warranty I suggest you RMA it.
If not under warranty I would be tempted to write it off as a bad debt. It's too much like an electro-mechanical failure about to happen.

 

[gbu]

No the bad drive has been disconnected.

It's an old(er) drive so couldn't send it back and not bothered by just scrapping it.

 

[mjf]

Well you can keep using it accepting that there will be some data that you will lose when it totally fails unless you pay a specialist Company to recover the data at the cost of ~$1k.

 

[gbu]

Not sure what you mean?

I have said its disconnected and all my data has been backed up and im happy to discard it and buy new?

Its been left on all day and ive had no crashes whilst ive been at work but the problem seems to be the updates just hang and dont get anywhere.

 

[Alsisgevat]

The xact same thing happend to one of my drives, it was a 1tb western digital, first started "ticking" once every hour, then every minute then all the time and eventually in the end it just stopped reading any info. I have not read the rest of this thread, so I am positive you got better advice, but if I may give my point, just trash it, and get a new one, in the end it will stop working, it can be tommorow or in 2 years, mine took 7months. And sorry, but I don't know what caused it,and I am not going to read all the posts to find out

 

[gbu]

Yeah ive trashed it now, got a new drive on order should be here in the next 2-3 days.

Not sure if i should start a new thread or just continue with this one but im still having the same trouble i described in post #26 and #27, has anyone got any ideas as to why this might be please?

 

[writhziden]

You never answered my question in post #28. Did the crash occur while your bad drive was still connected but not installed to?


Please upload your crash reports for the blue screen crash by following the http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html and I will analyze them for you. May indicate what hardware is causing problems if the bad drive was disconnected.

 

[gbu]

Do you still have your bad hard disk connected to the computer?

I answered

No the bad drive has been disconnected.

Anyhow no the drive was completely disconnected when the crash happened.

I'll do the scan and post the BSOD results.

thanks for taking the time to help me

 

[writhziden]

Ah, sorry, must have missed it in the hoopla.

You're welcome. I'll keep an eye out for the crash reports.

 

[gbu]

No problem, i've probably confused matters by changing the problem from the original topic!

Ok heres the attachments for you to look at

 

[writhziden]

Security Software:

mpcmdrun.exe	c:\program files\microsoft security client\antimalware\mpcmdrun.exe	1100	8	200	1380	18/03/2012 20:51	3.0.8402.0	266.95 KB (273,352 bytes)	27/04/2011 18:21
msmpeng.exe	c:\program files\microsoft security client\antimalware\msmpeng.exe	852	8	200	1380	18/03/2012 08:03	3.0.8402.0	12.48 KB (12,784 bytes)	27/04/2011 18:21
nissrv.exe	c:\program files\microsoft security client\antimalware\nissrv.exe	1404	8	200	1380	18/03/2012 08:03	3.0.8402.0	281.52 KB (288,272 bytes)	27/04/2011 18:21
msseces.exe	c:\program files\microsoft security client\msseces.exe	2072	8	200	1380	18/03/2012 08:03	2.1.1116.0	1.37 MB (1,436,736 bytes)	15/06/2011 15:35

Possible out of date driver:

[B][COLOR="Red"]atikmdag	fffff880`0407b000	fffff880`0459d000	Fri Apr 24 04:51:57 2009 (49f199cd)	004cc863		atikmdag.sys[/COLOR][/B]

Update the driver from ASUS - Graphics Cards- ASUS EAH4350 SILENT/DI/1GD2

[list=1][*]
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\gbu\Windows_NT6_BSOD_jcgriff2\031812-32463-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16917.amd64fre.win7_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`02805000 PsLoadedModuleList = 0xfffff800`02a41e70
Debug session time: Sat Mar 17 18:10:10.559 2012 (UTC - 6:00)
System Uptime: 0 days 0:23:36.448
Loading Kernel Symbols
...............................................................
................................................................
.........
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa8003bc0640, ffff, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33476 )

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

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, The subtype of the bugcheck.
Arg2: fffffa8003bc0640
Arg3: 000000000000ffff
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x1a_41790

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  MsMpEng.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800028e862e to fffff80002875540

STACK_TEXT:  
fffff880`02b07928 fffff800`028e862e : 00000000`0000001a 00000000`00041790 fffffa80`03bc0640 00000000`0000ffff : nt!KeBugCheckEx
fffff880`02b07930 fffff800`028b6a9a : 00000000`00000000 00000000`072a0fff fffffa80`00000000 fffffa80`08896060 : nt! ?? ::FNODOBFM::`string'+0x33476
fffff880`02b07af0 fffff800`02874793 : ffffffff`ffffffff 00000000`025fe860 00000000`025fe828 00000000`00008000 : nt!NtFreeVirtualMemory+0x5ca
fffff880`02b07be0 00000000`77a3f89a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`025fe798 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77a3f89a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+33476
fffff800`028e862e cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+33476

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4ec7a284

FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+33476

BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+33476

Followup: MachineOwner
---------
[/list]

1. Possible causes are Drivers... Memory problems...

To determine which of these caused the crash, follow these steps:

• 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).
  
  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.
  Once these steps have been followed, it is safe to remove and replace components within your computer.
  
  
• An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
  
  a. Backup your system and user files
  b. Create a system restore point
  c. If you do not have a Windows 7 DVD, Create a system repair disc
  d. Run Driver Verifier and in step 3, only select Standard settings. Do not select the other two settings in the red boxes.
  
  If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using http://www.sevenforums.com/tutorials/700-system-restore.html OPTION TWO.
  
  Thanks to zigzag3143 for contributing to the Verifier steps.
  If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.​
  The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.

 

[gbu]

Installed new ati driver.

Ran memtest and it picked up errors straight away tried both sticks in different slots one at a time and the errors are still there

if it is the RAM i had this thread from before so im wondering if it isnt compatible after all?
http://www.sevenforums.com/hardware-devices/215972-need-help-selecting-ram-please.html