[rshaffer61]

No boot back to normal mode first.

[Advertisements]

Well the scan completed and I ran the event viewer but the system froze up before I was able to post the log. I will reboot and try to post it again. Just an observation, after the chkdsk completed on C: the computer went to reboot but it then started another, 3 step chkdsk on my E: drive. after that completed, the system tried to reboot but it got hung up. I shut down and tried to restart. I tried to run chkdsk again but I aborted out of it before it began. Log to follow soon...I hope

[erf]

Well the scan completed and I ran the event viewer but the system froze up before I was able to post the log. I will reboot and try to post it again. Just an observation, after the chkdsk completed on C: the computer went to reboot but it then started another, 3 step chkdsk on my E: drive. after that completed, the system tried to reboot but it got hung up. I shut down and tried to restart. I tried to run chkdsk again but I aborted out of it before it began. Log to follow soon...I hope

[rshaffer61]

OK I think this is a OS issue but I want to make sure.
Run hard drive diagnostics: http://www.tacktech....ay.cfm?ttid=287
Make sure, you select tool, which is appropriate for the brand of your hard drive.
Depending on the program, it'll create bootable floppy, or bootable CD.
If downloaded file is of .iso type, use ImgBurn: http://www.imgburn.com/ to burn .iso file to a CD (select "Write image file to disc" option), and make the CD bootable.

NOTE. If your hard drive is made by Toshiba, try the Hitachi DFT CD Image version of the software

Thanks to Broni for the instructions








A If you have more than one RAM module installed, try starting computer with one RAM stick at a time.

NOTE Keep in mind, the manual check listed above is always superior to the software check, listed below. DO NOT proceed with memtest, if you can go with option A

B. If you have only one RAM stick installed...
...run memtest...


1. Download - Pre-Compiled Bootable ISO (.zip). If you prefer to use the USB version then use this link USB KEY
2. Unzip downloaded /memtest86+-4.20.iso.zip file.
3. Inside, you'll find /memtest86+-4.20.iso file.
4. Download, and install ImgBurn: http://www.imgburn.com/
5. Insert blank CD into your CD drive.
6. Open ImgBurn, and click on Write image file to disc
7. Click on Browse for a file... icon:



8. Locate memtest86+-4.20.iso file, and click Open button.
9. Click on ImgBurn green arrow to start burning bootable memtest86 CD:



10. Once the CD is created, boot from it, and memtest will automatically start to run. You may have to change the boot sequence in your BIOS to make it work right.

To change Boot Sequence in your BIOS

Reboot the system and at the first post screen (where it is counting up memory) start tapping the DEL button
This will enter you into the Bios\Cmos area.
Find the Advanced area and click Enter
Look for Boot Sequence or Boot Options and highlight that click Enter
Now highlight the first drive and follow the directions on the bottom of the screen on how to modify it and change it to CDrom.
Change the second drive to the C or Main Drive
Once that is done then click F10 to Save and Exit
You will prompted to enter Y to verify Save and Exit. Click Y and the system will now reboot with the new settings.


The running program will look something like this depending on the size and number of ram modules installed:




It's recommended to run 5-6 passes. Each pass contains very same 8 tests.

This will show the progress of the test. It can take a while. Be patient, or leave it running overnight.



The following image is the test results area:



The most important item here is the “errors” line. If you see ANY errors, even one, most likely, you have bad RAM.

[erf]

Here's the event viewer log:

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

A disk check has been scheduled.
Windows will now check the disk.
Cleaning up minor inconsistencies on the drive.
Cleaning up 13 unused index entries from index $SII of file 0x9.
Cleaning up 13 unused index entries from index $SDH of file 0x9.
Cleaning up 13 unused security descriptors.
CHKDSK is verifying file data (stage 4 of 5)...
Windows replaced bad clusters in file 44136
of name \WINDOWS\$N40CA~1\spuninst\updspapi.dll.
Windows replaced bad clusters in file 90914
of name \PROGRA~1\FIREFL~1\CIVCIT~1\fx\neigh_08.wav.
Windows replaced bad clusters in file 91336
of name \PROGRA~1\FIREFL~1\CIVCIT~1\fx\WC92AA~1.WAV.
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
Free space verification is complete.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.

39110210 KB total disk space.
27734148 KB in 106280 files.
22516 KB in 16999 indexes.
0 KB in bad sectors.
393790 KB in use by the system.
65536 KB occupied by the log file.
10959756 KB available on disk.

4096 bytes in each allocation unit.
9777552 total allocation units on disk.
2739939 allocation units available on disk.

Internal Info:
60 91 02 00 99 e1 01 00 e1 3c 02 00 00 00 00 00 `........<......
26 02 00 00 03 00 00 00 f3 07 00 00 00 00 00 00 &...............
18 1b b6 07 00 00 00 00 5c 14 fe 54 00 00 00 00 ........\..T....
04 81 ca 4b 00 00 00 00 98 16 2a 4d 07 00 00 00 ...K......*M....
38 91 de 15 01 00 00 00 14 38 42 13 09 00 00 00 8........8B.....
99 9e 36 00 00 00 00 00 10 3a 07 00 28 9f 01 00 ..6......:..(...
00 00 00 00 00 10 c2 9c 06 00 00 00 67 42 00 00 ............gB..

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


For more information, see Help and Support Center at http://go.microsoft....ink/events.asp.

[erf]

regarding the mem test above, do I physically remove one stick of memory or is there some other way to disable it? Thanks,

-Ernesto

[rshaffer61]

First thing is please rerun the chkdsk test to make sure it corrected everything. Then if you don't feel comfortable working inside the system then skip the manual test and run the memtest86 program itself.

[erf]

Chkdsk ran again. C: drive in 5 steps E: in 3 steps. After finishing E:, it hung up on reboot. Always tries to rerun chkdsk on E: after every reboot. Here is the event viewer log for C: Can the chkdsk /r be done on E:?


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

A disk check has been scheduled.
Windows will now check the disk.
Cleaning up minor inconsistencies on the drive.
Cleaning up 14 unused index entries from index $SII of file 0x9.
Cleaning up 14 unused index entries from index $SDH of file 0x9.
Cleaning up 14 unused security descriptors.
CHKDSK is verifying file data (stage 4 of 5)...
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
Free space verification is complete.

39110210 KB total disk space.
27768880 KB in 106250 files.
22480 KB in 16800 indexes.
0 KB in bad sectors.
394306 KB in use by the system.
65536 KB occupied by the log file.
10924544 KB available on disk.

4096 bytes in each allocation unit.
9777552 total allocation units on disk.
2731136 allocation units available on disk.

Internal Info:
60 91 02 00 b4 e0 01 00 41 3c 02 00 00 00 00 00 `.......A<......
28 02 00 00 03 00 00 00 f5 07 00 00 00 00 00 00 (...............
7e 6d 67 07 00 00 00 00 5e 4b 56 55 00 00 00 00 ~mg.....^KVU....
74 5f a1 49 00 00 00 00 f8 85 be 57 07 00 00 00 t_.I.......W....
d0 da a3 14 01 00 00 00 14 46 69 1a 09 00 00 00 .........Fi.....
99 9e 36 00 00 00 00 00 10 3a 07 00 0a 9f 01 00 ..6......:......
00 00 00 00 00 c0 e0 9e 06 00 00 00 a0 41 00 00 .............A..

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


For more information, see Help and Support Center at http://go.microsoft....ink/events.asp.

[rshaffer61]

It should be able to run on any drive.

[erf]

How would I issue that command for the E: drive from the run window?

[rshaffer61]

I believe it would be chkdsk e: /r

[erf]

Well, I think my problem is with my E: drive. I disconnected the drive and I dont seem to have any more problems. The drive is a Seagate Baracuda ST3500641AS 500 GB SATA drive. Should I repost over in the hardware section or can you still help me?

Thanks, ERF

[rshaffer61]

You can try running the hard drive diagnostics on just the E drive.

[erf]

It still hangs up - it just takes longer. Ok I will go back to your suggested diagnostic on C: and continue on. Thanks

[erf]

OK, I went to Tachtech.com and looked for my drive which is Samsung. Selecting samsung takes me to a Seagate website. Since I already have SeaTools for Windows installed on my computer, I used that to check C:. I ran the short test - result OK, Short Generic test - result OK. Is there something else you would like me to do or should I move on to the memory test?

regarding the mem test, I plan on removing the RAM sticks. Do you just need me to boot up with each different stick? or is there someother test I need to perform.

Thanks, ERF

[rshaffer61]

Take one memory stick out and just boot with one stick. If everything runs find then switch the modules and test the other. If everything runs fine then change the slot the one is in and see if it boots then. Repeat for the other module. If everything then tests fine then run the memtest program on each module by itself. Remember one pass is like 7 tests so let it fo through at leats 3 complete passes before checking the other.