20 replies to this topic

[Jimbo1]

Upfront before we go any futher, This Laptop is a friend of mine who brought it to me yesterday, So if anyone wants to work this problem I am letting you know up front. Reason I asking is because this thing has me stumped as heck. Here is the low down: Dell Inspiron 1764 Core 3 Processor 4 Gigs of DDR3 PC3-8500s-7-10-F2 Memory Windows 7 Premium 64 bit Operating System Here is what he told me, that the labtop was running erattic, the machine is only a year old, but any way he said it was haging up, crashing, being non responsive and so forth. So he brought it to a pc repair shop and they told him one of his memory mod was bad and replaced it, he said after he got the machine back and for the last month it was not even better, in fact it got worst. Als he said something about the machine booting into a blue screen. Now mind you this being a core 3 with 4 gigs ram and 64 bits os should be hauling like a bat out of hell, but when I booted it up and after 27 minuets its still trying boot, I said jezzzzzzzz this sucks. I gave up waiting, so this is what I did: 1. I took out the memory that was replaced and the machine booting less than 3 minuets, So I did a little cleanup and what not and so far so good, so I decided to try and run a scan with MAMB, during the scan process the machine, crashed into the blue screen of death, it went so fast and saying something about kernal something, and saying memory dump ran a quick like scan or something, I could not stop it to see all of the msg. 2. So I was thinking hummm could it be the org memory that was left gone bad, So I took it out and put in the memory that was replaced, Machine booted in less that 3 minuets, I did ok Mabey the org memory that was left was bad also, well I decided to run a scan again to check for Virus or what not and ran MAMB again the machine crashed, This time the same blue screen again and same msg, but cannot stop it long enough to write down all thats said. Also during this process, when I boot back up to the desk top I get this msg: Windows has recovered from a serious error, do you with to go online net time when the system starts to look for a soultion? and here is the rest of the msg: Problem Signature: problem event name: Blue Screen OS Version 6.1.7600.2.0.0.7683 Locale ID: 1033 Additional Info about the problem: BCCode: 7a Bcp1: FFFFF6FC 500129BO BCP2: FFFFFFFF C0000185 BCP3: 00000000485D2880 BCP4: FFFFF8A002536036 OS Version 6-1-7600 Service Pack 0-0 Product 768-1 Files that help describe this problem: C:\Windows\mini dump\102310-20389-01.dmp C:\Users\appdata\local\temp\wer-41059-0.sysdata.xml No matter what scans I try to run a little ways into the scan, wham crashed and that blue screen thing pops up with that kernals thing and what not, it does so fast I cannot read the rest of it. Again if you want to help me you can, because I not that much on a Windows 7 64 bit operating system and with all those error code things. Jimbo1

Edited by Jimbo1, 23 October 2010 - 11:22 AM.

[Jimbo1]

Went ahead and set the windows not to auto restart after a crash, now this is what the system is saying. A problem has been detected and windows has been shut down to prevent damage to your computer. Kernel_Data_Inpage_Error Stop: 0x000007a (0xfffff6fc500413f0, 0x0000000061b13820, 0xffffff8a00827ea4) collecting data for crash dump... Initilizing disk for crash dump... Beginning dump of physical memory Dumping physical memory to disk: 100 Physicial memory dump complete. Contact your system adim or tec support for further assistance. Dump now why does that sound bad, it like it's going to the bathroom or something. Jimbo

Edited by Jimbo1, 23 October 2010 - 01:50 PM.

[paws]

Hi Jimmy, A 7A Stop Error is often a hardware fault, a driver issue or a virus Here's a quick way to check things out to see what is what: 1 Try to boot to safe mode and get copied off to removable media any important stuff that is not included in your friend's latest backup If he hasn't backed up his stuff then its time for some tough talking.... he needs to be taken to one side and the error of his ways pointed out......whilst your at it.... talk to him about a disc image, Acronis, Paragon Ghost etc or one of the free ones..... has he done one? if not why not? Over this side of the pond we call it "tough love" telling him how it actually is and not putting a glossy coat on it..... it may be different in your neck of the woods, so use your own judgement on how hard you hit him with the facts of computer life.... (but do hit him hard if he needs it! and, if it will do him good!) 2 Boot to a live distro of Linux...try Linux Puppy or Ubuntu (you may need to alter boot priority in the BIOS to set optical drive CD/DVD etc as first boot priority followed by hard drive etc) 3 run it extensively.... if it runs Ok and is perfectly usable without blue screening then you have practically ruled out hardware failure, so its (probably a Windows issue, (system problem or virus) or a driver issue. 4 I'll just mention that Dell 1764's come with a factory restore option.... its quick and simple and easy to do.... usual caveats.... it will destroy all files repeat all files including Windows itself.... and data files...everything... before it installs Windows again and returns the computer to its "factory fresh" or " just out of the box" state. 5 If you want me to go further into the next steps then I'll move this topic to Tech Class forum... Regards paws.

Edited by paws, 24 October 2010 - 06:58 AM.

[Jimbo1]

1. Will have to copy all of his stuff and will call him to see what else, he has a snot load of pic, music, work related stuff. Aye I shoot my finger at him hard because when he had an old system last year I told him the way the net is you better be backing up, but he said he is paying for something called data safe online and suppose to be backed up. I will call him tommrow and find out. 2. 2 Boot to a live distro of Linux...try Linux Puppy or Ubuntu (you may need to alter boot priority in the BIOS to set optical drive CD/DVD etc as first boot priority followed by hard drive etc) Sad to say I have never done nothing like that, so how would I go about doing that to test that part? 3. I'll just mention that Dell 1764's come with a factory restore option.... its quick and simple and easy to do.... usual caveats.... it will destroy all files repeat all files including Windows itself.... and data files...everything... before it installs Windows again and returns the computer to its "factory fresh" or " just out of the box" state. I was thinking of this option, but what has me worried, if it's a failing memory problem because as I said one of his org was replaced, but now I tryed just leaving the one that was replaced in only and same problem, and I switch just to his org mod also and same problems, so no matter which memory mod I am using at the time it does the same thing, each stick is a 2gig stick. Whats really said is warrenty is past about 3 months. Jimbo

Edited by Jimbo1, 24 October 2010 - 02:37 PM.

[paws]

Hi Jimmy, Here's a quick rundown on Linux Puppy...its a tool found in most technician's work bag

The Linux Puppy Live distro is available from here:
http://www.puppylinu...load/index.html
its about 100MB in total so only do this using a broadband Internet connection...

You need to burn the downloaded file as an "image" Just copying it is no good.... IMGBurn is excellent for this, details available from here:
http://www.imgburn.com/
the actual download of ImgBurn is available from here:
http://www.imgburn.c...hp?act=download

Linux Puppy a very useful tool, that is in constant use in the workshop, but for a home user it has 3 main uses:

In explanation, Linux Puppy Live distro is a self contained operating system that runs in memory from a CD.....or even a thumb drive if you are crafty (That's what the "Live" bit means), so it doesn't need Windows at all, IE no need for a working copy of Windows XP, Vista, Win 7 or any earlier version of Windows. It is in effect an alternative to Windows and also has the advantage of being free (quite legally). Because Windows is fitted to the majority of PC's, folks are often unaware that there are different operating systems available....one of the advantages of Linux is that it is issued free under a general licence unlike some other operating systems (like Windows) that are charged for by their developers.

1 If a machine won’t boot, then we need to know first off, if its a hardware problem. or an operating system (Windows) problem.....if it is hardware then there's no need for us to spend time trying to alter Windows settings....... so first we try to boot from the Linux Live Puppy disc (altering the boot priority in the BIOS if necessary to facilitate this) if the machine works perfectly under Linux then we can be reasonably sure that the hardware is OK and so we start looking at the Windows operating system to try and identify the problem so that we can fix it.

2 If a machine won't boot into Windows even in safe mode, It can be a very worrying time.
For Example
When the machine won't boot up, no matter what you do and you realise that all your important stuff, (music, photos, work, address books and contact lists, emails, downloaded programs and all your Microsoft Word docs, Excel spreadsheets, data bases PowerPoint presentations and all the rest perhaps including the only draft of the book you have spent the last 3 years researching and writing or your PHd thesis) have all disappeared............
then we can try to boot into Live Puppy, mount the hard drive (Live Puppy does this automatically) and copy off the data to safe external media (its surprising that despite everything that has been written about the need for back ups, so few folks actually have an up to date accurate and reproducible back up of all their important stuff kept safe on removable media......

3 Its a super way of becoming familiar with a different operating system.......without making any changes to the hard drive..that might affect Windows...its a way of learning and experimenting and finding out information in a no risk, or at least low risk way.
Let me know if you have any questions on this.
Regards
paws

Edited by paws, 24 October 2010 - 03:44 PM.

[Jimbo1]

Never having done this before I clicked on the link you gave, but so many files, what is the file name iso i need to download.

What I see is a Directory Puppy-5.1.1 and in that dir their is a file name called lupu-510.iso or 511.iso

so is that file name lupu-510.iso ?

Jimmy

Hi jimmy,
You just need to run the Linux applications not Windows ones ( for the time being that is) Did you download Puppy and burn it as an image using ImgBurn, ? and can you boot the damaged machine from it....?
Do you need a step by step on the above ( your pm to me refers or have you done it all Ok?)
Regards
paws

Ok I was asking of what was the file name to down load. I downloaded from what I saw was directory puppy-5.1.1 did not see anything called Live Puppy. All I see is a file or a few of them is lupu-511.iso.

When ahead and dl that one and made a boot disk and boot into I assume this is the puppy program. I reason I asked in other programs in that section did not know when you would be back on line to ask what is the correct file to download.

Was testing puppy out on my machine to play around with a little bit while waiting for you to see what it was like.

Thats why I was trying to see what programs to run while using puppy to make the system crash when doing the test or to load it up. What I see in puppy is playing the falling blocks, rubix cube thing but is that enough to run this machine through a hard test IE: hd work, memory work ext.

As I said if windows was sitting alone it ran and did not crash, I am able to go online and read all I want and no crash, but once any scan is started and a little while into the scan crash.

So anyhow this is why I want to see if memtest program could be ran while using puppy to test the memory, will download memtest and run it inside of windows to see before we start the test.

Will post back of whats found.
Jimmy

Edited by Jimbo1, 25 October 2010 - 05:05 PM.

[Jimbo1]

Ok here is the run down: Had to go out yesterday and did not get a chance to post back. 1. Before booting into Puppy 5.1.1, I went and tryed a online scan, about 10% into the scan on a file called Chess.dll it stopped and went no futher. This got me to thinking on a problem I worked on in the past when the Guy I was working with was having the same problem, when he ran a scan and it got to a .dll file in IE his system would crash, other than that it would run fine. But anyhow I went ahead and done a memtest run to see what happen, I tested each Mod by itself not both at the same time, both mod passed the memory test, kinda making me think well it cannot be memory, but not sure until you read this. 2. After the memtest I went ahead and booted into puppy and messed around with what they had, found an old game I use to play a long time, played it till my hand started hurting and no crash. Went and read a little on the net and so forth. 3. Booted back into Windows and got to thinking more and read over the post I worked on to see what the fellow problems was. So I Ran a Chkdsk /r and here is the result: Log Name: Application Source: Microsoft-Windows-Wininit Date: 10/25/2010 12:39:02 PM Event ID: 1001 Task Category: None Level: Information Keywords: Classic User: N/A Computer: user-PC Description: Checking file system on C: The type of the file system is NTFS. Volume label is OS. A disk check has been scheduled. Windows will now check the disk. CHKDSK is verifying files (stage 1 of 5)... 123136 file records processed. File verification completed. 146 large file records processed. 0 bad file records processed. 0 EA records processed. 44 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)... 171942 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)... 123136 file SDs/SIDs processed. Cleaning up 73 unused index entries from index $SII of file 0x9. Cleaning up 73 unused index entries from index $SDH of file 0x9. Cleaning up 73 unused security descriptors. Security descriptor verification completed. 24404 data files processed. CHKDSK is verifying Usn Journal... 36285152 USN bytes processed. Usn Journal verification completed. CHKDSK is verifying file data (stage 4 of 5)... Read failure with status 0xc0000185 at offset 0x72d099000 for 0xe000 bytes. Read failure with status 0xc0000185 at offset 0x72d09b000 for 0x1000 bytes. Windows replaced bad clusters in file 20167 of name \Windows\System32\DRIVER~1\FILERE~1\KIT202~1.INF\GF0579~1.RES. Read failure with status 0xc0000185 at offset 0x738b47000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x738b4e000 for 0x1000 bytes. Windows replaced bad clusters in file 20646 of name \MSOCache\ALLUSE~1\{91120~1\setup.exe. Read failure with status 0xc0000185 at offset 0x7327ec000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x7327f3000 for 0x1000 bytes. Windows replaced bad clusters in file 21049 of name \PROGRA~1\COMMON~1\System\Ole DB\oledb32.dll. Read failure with status 0xc0000185 at offset 0x732cbf000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x732cc7000 for 0x1000 bytes. Windows replaced bad clusters in file 22796 of name \PROGRA~2\Java\jre6\lib\fonts\LUDBAB~1.TTF. Read failure with status 0xc0000185 at offset 0x73b696000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x73b69a000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x73b75b000 for 0x8000 bytes. Read failure with status 0xc0000185 at offset 0x73b761000 for 0x1000 bytes. Windows replaced bad clusters in file 25127 of name \PROGRA~2\Adobe\Reader 9.0\Reader\JAVASC~1\JSBYTE~1.BIN. Read failure with status 0xc0000185 at offset 0x704a0b000 for 0x5000 bytes. Read failure with status 0xc0000185 at offset 0x704a0c000 for 0x1000 bytes. Windows replaced bad clusters in file 27087 of name \PROGRA~2\CYBERL~1\POWERD~1\Kernel\Movie\CLSUBT~1.AX. Read failure with status 0xc0000185 at offset 0x731b20000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x731b2e000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x731bef000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x731bf6000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x731b2f000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x731b2f000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x731cb7000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x731cbd000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x731d7e000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x731d84000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x731e45000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x731e4b000 for 0x1000 bytes. Windows replaced bad clusters in file 38612 of name \Users\user\Music\VARIOU~1\SUPERS~3\13YOU'~1.WMA. Read failure with status 0xc0000185 at offset 0x73231b000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x73231f000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x7324d0000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x7324d6000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x732597000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x73259e000 for 0x1000 bytes. Windows replaced bad clusters in file 38620 of name \Users\user\Music\VARIOU~1\SUPERS~4\02LIND~1.WMA. Read failure with status 0xc0000185 at offset 0x8021ec000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x8021f5000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x802436000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x802445000 for 0x1000 bytes. Windows replaced bad clusters in file 39970 of name \Users\user\Music\RICKAS~1.MP3. Read failure with status 0xc0000185 at offset 0x802775000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x802781000 for 0x1000 bytes. Windows replaced bad clusters in file 39971 of name \Users\user\Music\RICKAS~2.MP3. Read failure with status 0xc0000185 at offset 0x738013000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x738018000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x7380d9000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x7380df000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x802b81000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x802b83000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x802c44000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x802c49000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x802d0a000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x802d0e000 for 0x1000 bytes. Windows replaced bad clusters in file 39972 of name \Users\user\Music\RICKAS~3.MP3. Read failure with status 0xc0000185 at offset 0x704532000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x704538000 for 0x1000 bytes. Windows replaced bad clusters in file 40440 of name \Users\user\Pictures\2010-0~3\2010-0~1\IMG_0003.PNG. Read failure with status 0xc0000185 at offset 0x7045fa000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x7045ff000 for 0x1000 bytes. Windows replaced bad clusters in file 40442 of name \Users\user\Pictures\2010-0~4\001.PNG. Read failure with status 0xc0000185 at offset 0x708e0f000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x708e1a000 for 0x1000 bytes. Windows replaced bad clusters in file 40568 of name \Users\user\Pictures\DOCUME~1\My Games\AGEOFE~1\Savegame\WADE~1.AGE. Read failure with status 0xc0000185 at offset 0x708fc2000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x708fd1000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x709092000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x709098000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x709159000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x70915f000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x709220000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x709226000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x7092e7000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x7092ee000 for 0x1000 bytes. Windows replaced bad clusters in file 40580 of name \Users\user\Pictures\DOCUME~1\My Scans\2010-0~1\scan0001.tif. Read failure with status 0xc0000185 at offset 0x70eb12000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x70eb13000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x70ebd4000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x70ebda000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x70ed8b000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x70ed91000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x70ee52000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x70ee58000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x70ef19000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x70ef1f000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x70ef20000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x70ef20000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x70efe1000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x70efe7000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x70f0a8000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x70f0ae000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x70f25f000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x70f265000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x70f326000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x70f32c000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x70f3ed000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x70f3f3000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x70f3f4000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x70f3f4000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x70f4b5000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x70f4bb000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x70f57c000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x70f582000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x70f643000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x70f649000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x70f7fa000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x70f800000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x70f8c1000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x70f8c7000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x70f8c8000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x70f8c8000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x70f989000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x70f98f000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x70fa50000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x70fa56000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x70fb17000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x70fb1d000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x70fbde000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x70fbe4000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x70fd95000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x70fd9b000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x70fd9c000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x70fd9c000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x70fe5d000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x70fe63000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x70ff24000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x70ff2a000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x70ffeb000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x70fff1000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x7100b2000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x7100b8000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x710179000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x71017f000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x710180000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x710180000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x710331000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x710337000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x7103f8000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x7103fe000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x7104bf000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x7104c5000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x710586000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x71058c000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x71064d000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x710653000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x710714000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x71071b000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x7108cc000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x7108d2000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x710993000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x710999000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x710a5a000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x710a60000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x710b21000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x710b27000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x710be8000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x710bef000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x710cb0000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x710cb6000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x710e67000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x710e6d000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x710f2e000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x710f34000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x710ff5000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x710ffb000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x7110bc000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x7110c3000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x711184000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x71118a000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x71124b000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x711251000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x711402000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x711408000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x7114c9000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x7114cf000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x711590000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x711597000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x711658000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x71165e000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x71171f000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x711725000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x7117e6000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset Event Xml: <Event xmlns="http://schemas.micro.../events/event"> <System> <Provider Name="Microsoft-Windows-Wininit" Guid="{206f6dea-d3c5-4d10-bc72-989f03c8b84b}" EventSourceName="Wininit" /> <EventID Qualifiers="16384">1001</EventID> <Version>0</Version> <Level>4</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2010-10-25T17:39:02.000000000Z" /> <EventRecordID>5365</EventRecordID> <Correlation /> <Execution ProcessID="0" ThreadID="0" /> <Channel>Application</Channel> <Computer>user-PC</Computer> <Security /> </System> <EventData> <Data> Checking file system on C: The type of the file system is NTFS. Volume label is OS. A disk check has been scheduled. Windows will now check the disk. CHKDSK is verifying files (stage 1 of 5)... 123136 file records processed. File verification completed. 146 large file records processed. 0 bad file records processed. 0 EA records processed. 44 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)... 171942 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)... 123136 file SDs/SIDs processed. Cleaning up 73 unused index entries from index $SII of file 0x9. Cleaning up 73 unused index entries from index $SDH of file 0x9. Cleaning up 73 unused security descriptors. Security descriptor verification completed. 24404 data files processed. CHKDSK is verifying Usn Journal... 36285152 USN bytes processed. Usn Journal verification completed. CHKDSK is verifying file data (stage 4 of 5)... Read failure with status 0xc0000185 at offset 0x72d099000 for 0xe000 bytes. Read failure with status 0xc0000185 at offset 0x72d09b000 for 0x1000 bytes. Windows replaced bad clusters in file 20167 of name \Windows\System32\DRIVER~1\FILERE~1\KIT202~1.INF\GF0579~1.RES. Read failure with status 0xc0000185 at offset 0x738b47000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x738b4e000 for 0x1000 bytes. Windows replaced bad clusters in file 20646 of name \MSOCache\ALLUSE~1\{91120~1\setup.exe. Read failure with status 0xc0000185 at offset 0x7327ec000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x7327f3000 for 0x1000 bytes. Windows replaced bad clusters in file 21049 of name \PROGRA~1\COMMON~1\System\Ole DB\oledb32.dll. Read failure with status 0xc0000185 at offset 0x732cbf000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x732cc7000 for 0x1000 bytes. Windows replaced bad clusters in file 22796 of name \PROGRA~2\Java\jre6\lib\fonts\LUDBAB~1.TTF. Read failure with status 0xc0000185 at offset 0x73b696000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x73b69a000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x73b75b000 for 0x8000 bytes. Read failure with status 0xc0000185 at offset 0x73b761000 for 0x1000 bytes. Windows replaced bad clusters in file 25127 of name \PROGRA~2\Adobe\Reader 9.0\Reader\JAVASC~1\JSBYTE~1.BIN. Read failure with status 0xc0000185 at offset 0x704a0b000 for 0x5000 bytes. Read failure with status 0xc0000185 at offset 0x704a0c000 for 0x1000 bytes. Windows replaced bad clusters in file 27087 of name \PROGRA~2\CYBERL~1\POWERD~1\Kernel\Movie\CLSUBT~1.AX. Read failure with status 0xc0000185 at offset 0x731b20000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x731b2e000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x731bef000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x731bf6000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x731b2f000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x731b2f000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x731cb7000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x731cbd000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x731d7e000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x731d84000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x731e45000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x731e4b000 for 0x1000 bytes. Windows replaced bad clusters in file 38612 of name \Users\user\Music\VARIOU~1\SUPERS~3\13YOU'~1.WMA. Read failure with status 0xc0000185 at offset 0x73231b000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x73231f000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x7324d0000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x7324d6000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x732597000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x73259e000 for 0x1000 bytes. Windows replaced bad clusters in file 38620 of name \Users\user\Music\VARIOU~1\SUPERS~4\02LIND~1.WMA. Read failure with status 0xc0000185 at offset 0x8021ec000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x8021f5000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x802436000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x802445000 for 0x1000 bytes. Windows replaced bad clusters in file 39970 of name \Users\user\Music\RICKAS~1.MP3. Read failure with status 0xc0000185 at offset 0x802775000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x802781000 for 0x1000 bytes. Windows replaced bad clusters in file 39971 of name \Users\user\Music\RICKAS~2.MP3. Read failure with status 0xc0000185 at offset 0x738013000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x738018000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x7380d9000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x7380df000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x802b81000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x802b83000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x802c44000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x802c49000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x802d0a000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x802d0e000 for 0x1000 bytes. Windows replaced bad clusters in file 39972 of name \Users\user\Music\RICKAS~3.MP3. Read failure with status 0xc0000185 at offset 0x704532000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x704538000 for 0x1000 bytes. Windows replaced bad clusters in file 40440 of name \Users\user\Pictures\2010-0~3\2010-0~1\IMG_0003.PNG. Read failure with status 0xc0000185 at offset 0x7045fa000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x7045ff000 for 0x1000 bytes. Windows replaced bad clusters in file 40442 of name \Users\user\Pictures\2010-0~4\001.PNG. Read failure with status 0xc0000185 at offset 0x708e0f000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x708e1a000 for 0x1000 bytes. Windows replaced bad clusters in file 40568 of name \Users\user\Pictures\DOCUME~1\My Games\AGEOFE~1\Savegame\WADE~1.AGE. Read failure with status 0xc0000185 at offset 0x708fc2000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x708fd1000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x709092000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x709098000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x709159000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x70915f000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x709220000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x709226000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x7092e7000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x7092ee000 for 0x1000 bytes. Windows replaced bad clusters in file 40580 of name \Users\user\Pictures\DOCUME~1\My Scans\2010-0~1\scan0001.tif. Read failure with status 0xc0000185 at offset 0x70eb12000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x70eb13000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x70ebd4000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x70ebda000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x70ed8b000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x70ed91000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x70ee52000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x70ee58000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x70ef19000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x70ef1f000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x70ef20000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x70ef20000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x70efe1000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x70efe7000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x70f0a8000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x70f0ae000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x70f25f000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x70f265000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x70f326000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x70f32c000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x70f3ed000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x70f3f3000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x70f3f4000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x70f3f4000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x70f4b5000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x70f4bb000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x70f57c000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x70f582000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x70f643000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x70f649000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x70f7fa000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x70f800000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x70f8c1000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x70f8c7000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x70f8c8000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x70f8c8000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x70f989000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x70f98f000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x70fa50000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x70fa56000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x70fb17000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x70fb1d000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x70fbde000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x70fbe4000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x70fd95000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x70fd9b000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x70fd9c000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x70fd9c000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x70fe5d000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x70fe63000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x70ff24000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x70ff2a000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x70ffeb000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x70fff1000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x7100b2000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x7100b8000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x710179000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x71017f000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x710180000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x710180000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x710331000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x710337000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x7103f8000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x7103fe000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x7104bf000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x7104c5000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x710586000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x71058c000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x71064d000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x710653000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x710714000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x71071b000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x7108cc000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x7108d2000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x710993000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x710999000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x710a5a000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x710a60000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x710b21000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x710b27000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x710be8000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x710bef000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x710cb0000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x710cb6000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x710e67000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x710e6d000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x710f2e000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x710f34000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x710ff5000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x710ffb000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x7110bc000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x7110c3000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x711184000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x71118a000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x71124b000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x711251000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x711402000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x711408000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x7114c9000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x7114cf000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x711590000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x711597000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x711658000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x71165e000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x71171f000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset 0x711725000 for 0x1000 bytes. Read failure with status 0xc0000185 at offset 0x7117e6000 for 0x10000 bytes. Read failure with status 0xc0000185 at offset </Data> </EventData> </Event> 4. After this was done, I ran scans using MBAM and none were found, Ran Spybot – crashed, ran again and 11 files were found, Ran SuperAnti-Spyware, none were found. Ran AVG and nothing found. Updating AVG and it crashed. Ran AVG again it went ok, no files were found. 5. So I ran Puppy again and played with it and nothing from what I am able to do, I get back online and watch videos and such nothing, run scans again for the heck of it and you crash but now it’s not as often as before all of the above. Granted this is still using only one 2gig memory mod, I will put the other back into the system to see what happens and run test again. Will post back later. If anything is differant. So thats it so far. Jimbo

Edited by Jimbo1, 27 October 2010 - 07:47 AM.

[terry1966]

to me all those read errors looks like the hard drive is failing, first thing i'd do is back up everything on it, if paws(more knowledge) agrees then i think your looking at replacing it with a new hard drive and reinstalling the os.

[Jimbo1]

After the last post here is more info: 1. I went ahead and install the other 2 gig memory stick, boot ed up and everything loaded fine. 2. Ran all the scans again and no infections found, using Spuer Anti-Spyware, Spybot, MAMB, AVG, Did a windows update and playing around on the net. System crashed once but this time the screen just went white when trying to use a program. 3. Rebooted and re-ran MAMB and left it like that, they machine stayed up all night, I turned off all the power saving modes and came in this morning, MAMB reported nothing, had a screen that poped up wanting to register HP Software, I told it no, and went to run Spybot and when I clicked on it the screen when to while, had to reboot. 4. Booted back up, so in the process of copying all his pic's, he told me last night thats all he wanted was not worried about losing anything else. So Terry thinks the drive could be going bad, what do you think, I was thinking of trying to do a Factory out of box state and see what happens. But before doing that just to try a chkdsk /f, done a chkdsk /r already or mabey try SFC /scannow and see what happens.

[paws]

Hi Jimmy, Those errors found and corrected by you running chkdsk /r are worrying, and it could well be that the hard drive is failing as terry says.. The first priority therefore is to check the back up, make sure its up to date reproducible and kept safe on removable media Don't do anything else with the machine until you have completed this and you are happy that everything important has been copied off...if it is going to fail then this may be the last opportunity to copy stuff off...make sure you have a note of any passwords/usernames all serial numbers for Programs (including the Windows 25 character alphanumeric (5 groups of 5) and dont forget downloaded programs, copy off the executable files that were downloaded. Once you are happy then runn chkdsk /r again.....it should now complete with no errors, but if it doesn't then your friend may need to buy a new hard drive or return it under warranty or comsumer protection laws (if applicable in your jurisdiction) If you still get errors when running chkdsk /r a second time its worth trying just one more time... but then you should download a disc checking tool and see what it says... however new hard drives are very cheap from about £30 or so in the UK maybe less where you are? Regards paws

[Jimbo1]

Hi Jimmy,
Those errors found and corrected by you running chkdsk /r
are worrying, and it could well be that the hard drive is failing as terry says..

The first priority therefore is to check the back up, make sure its up to date reproducible and kept safe on removable media
Don't do anything else with the machine until you have completed this and you are happy that everything important has been copied off...if it is going to fail then this may be the last opportunity to copy stuff off...make sure you have a note of any passwords/usernames all serial numbers for Programs (including the Windows 25 character alphanumeric (5 groups of 5) and dont forget downloaded programs, copy off the executable files that were downloaded.

Once you are happy then runn chkdsk /r
again.....it should now complete with no errors, but if it doesn't then your friend may need to buy a new hard drive or return it under warranty or comsumer protection laws (if applicable in your jurisdiction)
If you still get errors when running chkdsk /r a second time its worth trying just one more time... but then you should download a disc checking tool and see what it says... however new hard drives are very cheap from about £30 or so in the UK maybe less where you are?
Regards
paws

Ya started looking around it's a 320 gig seagate, but you know the strange part is, in the last year of all the labtops I have fooled with with failed drive only been 320 gig drives only, making me think are 320 gig drives are not that great and should I go higher or tad lower, but any how the cost is around 49.00 to 60.00 depending where you buy it from.

But my buddy told only to copie his pictures and not worried about nothing else, and that has been done. While waiting for you, a tech friend of mine gave me a program called spinrite, not sure if you know of this or not. but anyhow I was running the program and about 1/2 threw it showed 3 sectors marked unrecovered and was working on the next one when I went to get get something to eat.

When I cam back found the machine had crashed, a white screen with gray looking horz. bars across it.

I try the chkdsk /r again but I getting a bad feeling from what you are saying it may be his drive, makes me wonder is that other ram that was replaced was bad or not and he paid money for it for nothing.

Jimmy

Edited by Jimbo1, 27 October 2010 - 01:59 PM.

[Jimbo1]

Well after I finished copying the guys pictures and all of his doc's, I went to boot the machine to do another chkdsk /r on it and gues what it's DOA, will not boot up into normal mode nor will it boot into safe mode, I get no display at all now. But what is odd that I can hook it up as an external usb drive and see all the files on the drive and can copy what ever I need, just the drive when hooked into the labtop will not boot into windows or safe mode. To be sure it was not the mother board, I had a small 160 gig drive I stuck in and the system booted. So making a phone call to give the poor chap the bad news. Jimbo

Edited by Jimbo1, 27 October 2010 - 02:07 PM.

[Jimbo1]

Hummm this is odd, Consider I guess the drive is a goner. I went and boot up on an install disk and it showed this 100 mb reserved 9.8 Gb Restore 60 GB OS 225 GB Secondary is that weird or is it a stelth virus hidden in them or one of those partions? This suppose to be a 320 Gig hard drive. Ordered a new drive for him found one for 48.00 bucks not to bad. But I got a question? Consider now I am going to format and install his Win 7 he has the install cd, but it does not have no software that came with the machine. So the question is can you copy the recovery section of the old drive and copy it to the new drive and then do a factory restore from those files to get all the stuff back or not? Jimbo1

Edited by Jimbo1, 27 October 2010 - 03:40 PM.

[paws]

Hi Jimmy, the sizes for the hard drive your quote look OK to me... Don't forget that a 320GB hard drive will only actually have about 93% of its nominal capacity truly available for his use.....(overheads and the differences between how a Gigabyte is measured/described).....the manuufacturers will quote the largest figure (for marketing reasons) whilst Windows is more interested in binary..... as a rule of thumb if you assume an overall difference of around 7% you won't be too far out on modest sized drives. Glad that you found a new drive for him at reasonable cost... I would not try and copy a recovery partition..you might get away with by making a disc image of the the Recovery Partition.....and then reimaging the new hard drive and then activating the Recovery Procedure...however its fraught with difficiculty...and there is a fairly wide possibility of failure or corruption. The best way by far is just to reimage the new hard drive with the image that he should have made when he first got his computer up and running fast and sweet and before he had time to break it! If he did this then he can be up and running again in less time than it takes to walk the dog! If he didn;t then he will have learned a valuable lesson.. With not having software application discs handy he will either need to obtain them, ( could be expensive) or use free alternatives Ie Open Office (free) as an alternative to Microsoft Office etc. Presumably he has tried going back to the retailer...they might, just might help him out.... In the Uk he would have a statututory right to seek redress from the retailer for a failed harddrive that failed at 15months...although he would need to prove that the fault was an "inherent defect" he would also need to convince the district judge that it was not normal for a machine that had been well handled not dropped or used roughly to fail within that time...... however your consumer laws are probably different from the ones I work with!...and for $48 ( USD) and a bit of work its hardly worth the hassle! Regards paws

[Jimbo1]

Hi Jimmy,
the sizes for the hard drive your quote look OK to me...

Don't forget that a 320GB hard drive will only actually have about 93% of its nominal capacity truly available for his use.....(overheads and the differences between how a Gigabyte is measured/described).....the manuufacturers will quote the largest figure (for marketing reasons) whilst Windows is more interested in binary..... as a rule of thumb if you assume an overall difference of around 7% you won't be too far out on modest sized drives.

Glad that you found a new drive for him at reasonable cost... I would not try and copy a recovery partition..you might get away with by making a disc image of the the Recovery Partition.....and then reimaging the new hard drive and then activating the Recovery Procedure...however its fraught with difficiculty...and there is a fairly wide possibility of failure or corruption.
The best way by far is just to reimage the new hard drive with the image that he should have made when he first got his computer up and running fast and sweet and before he had time to break it!
If he did this then he can be up and running again in less time than it takes to walk the dog!
If he didn;t then he will have learned a valuable lesson..

With not having software application discs handy he will either need to obtain them, ( could be expensive) or use free alternatives

Ie Open Office (free) as an alternative to Microsoft Office etc.

Presumably he has tried going back to the retailer...they might, just might help him out....

In the Uk he would have a statututory right to seek redress from the retailer for a failed harddrive that failed at 15months...although he would need to prove that the fault was an "inherent defect" he would also need to convince the district judge that it was not normal for a machine that had been well handled not dropped or used roughly to fail within that time...... however your consumer laws are probably different from the ones I work with!...and for $48 ( USD) and a bit of work its hardly worth the hassle!
Regards
paws

Nods, sad fact all of the extra software that came with the machine he does not have a disk, it was all in that recovery section of the drive, that was why I asked if it was possible to copy that file after setting up windows. The windows setup dvd and drivers cd is all he has for the machine.

He does have his MS Office 2007 CD's also so thats not a total lost, theirs pleanty of freeware stuff for the nic nacks and what not. ITunes software and printers he just going have to set up again.

At least I was able to copy all of his pictures before the drive would no longer boot, I still can see the drive hooking it up like a usb drive and copy what files I need.

For the heck of it I tryed to see if I could do a repair but the machine just hangs or when it loads, it load snail slow and none responsive. After an hour of waiting to get to repair option I said heck on it.

But thanks Paws for the help and Thank you Terry also, I never dealt with a problem such as this because it was kinda over my head, being that it's Windows 7 Machine with a 64 bit operating system, this only makes the 3 Windows 7 Machine I ever fooled with. I hope this was a learning tool also for others to see and read.

Edited by Jimbo1, 28 October 2010 - 08:12 AM.