Freezing then Issues on Start up

[Sublime]

I have been having issues with my PC freezing. I just started using Windows 7 after my PC crashed couple weeks ago. I upgraded from Vista 64 bit.
Since then it has been fine except the PC freezes when I play Starcraft 2. I can play the game for about five minutes or so, sometimes more/less it just depends, then it will freeze, the music/sounds that was playing at the time of freeze keeps replaying, and I have to manual reboot.

After I manual reboot when this happens, I get weird issues on start up. Sometimes it will say "failed to read boot disc" or "fail to start windows" "press ctrl+alt+delete to restart". Sometimes it will run CHKDSK on restart and this morning it ran Windows Repair and determined the problem could not be fixed and windows couldn't be started. I turned the PC on and off right after it told me that and it worked fine.

This is very strange to me as I never had any issues with the game freezing on Vista.

System Specs:
Intel E8400
Nvidia GTX 260
4GB Ram
Win7 64 bit
Biostar motherboard (all I know about it)

I have unistalled and reinstalled the game, along with the video card drivers.

Any help is greatly appreciated, thanks!

 

[Capt.Jack Sparrow]

Hello and Welcome !

Follow this article Run Selective Startup using System Configuration and see if that works.

- Captain

 

[Sublime]

Thanks for the reply
But I am not sure how that would help because it start up problems happen randomly after a freeze. Sometimes it won't happen and sometimes it will.

For instance here is my experience this morning.

I ran Windows Memory Diagnostic this morning to see if I had a RAM problem. The first time I ran Windows Memory Diagnostic, I checked on it after a while and my computer was a black screen. I hit CTRL+ALT+DELETE and it restarted but gave me no test results. I re-ran the test and it came back with no problems found. But soon after that my PC froze while writing an email, and when I tried to reboot I got "Can not read disc, press ctrl+alt+delete to restart". I left the PC off for 30 mins and tried again and it has started fine. Every now and then it will act slow. Do you think I might have a RAM problem although the test came back good?

 

[Capt.Jack Sparrow]

Hello,

Run a Hardware Diagnostic (Memory and Hard Drive) follow this link for instructions Hardware Diagnostic !! « Captain Debugger

- Captain

 

[Sublime]

I opened the command prompt and typed "chkdsk /v" and all I get back is "Access denied you do not have sufficient privileges. You have to evoke this utility in elevated mode".

I am not sure what to do

 

[CarlTR6]

You need to run the command prompt as an administrator.

http://www.sevenforums.com/tutorials/783-elevated-command-prompt.html

 

[Sublime]

Ok thanks for the help so far.

I ran chkdsk /v and got "no problems found"
I also restarted and ran chkdsk /r, and I looked at the event viewer but am not sure what I need to be looking for.

On memtest86, I downloaded the file, but am confused on how to use it. Do I need to download an ISO burner program and put the unzipped file on a disc, or do I need to unzip the files, then use the ISO burner to put them on the disc?

 

[Capt.Jack Sparrow]

Ok thanks for the help so far.

I ran chkdsk /v and got "no problems found"
I also restarted and ran chkdsk /r, and I looked at the event viewer but am not sure what I need to be looking for.

On memtest86, I downloaded the file, but am confused on how to use it. Do I need to download an ISO burner program and put the unzipped file on a disc, or do I need to unzip the files, then use the ISO burner to put them on the disc?

Yes here is the Tutorial http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

 

[tezlewis]

Because your getting intermittent disk boot errors it suggests the HDD could have an issue. Try reseating the cable and see if that helps! A HDD test would bew useful about now but if im honest, im not sure of the best ones around so it maybe worth waiting to see if someone can suggest a decent one to give good trusted results!

 

[Sublime]

I ran memtest86 over night for almost 9 hours, when I woke up it said Pass:7 Errors:0
So I guess its not a ram problem. What do you suggest I do now?

 

[Capt.Jack Sparrow]

I ran memtest86 over night for almost 9 hours, when I woke up it said Pass:7 Errors:0
So I guess its not a ram problem. What do you suggest I do now?

Hello,

Did you Download the Hard Disk Diagnostic Tool and run a Hard drive diagnostic ? Even the Check disk showed up OK it's good to make sure we get a green flag from the manufacture's Tool.


Try this free video stress test: FurMark: Graphics Card Stability and Stress Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net

FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit

Try this free stress test: Free Software - GIMPS

Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead.
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
The Test selection box and the stress.txt file describes what components that the program stresses.

Hope this helps,
Captain

 

[Sublime]

I tried to use the Fujitsu diagnostic tools link for the hdd test, but that link does not take you to the right place anymore, I got "The document you have just requested is not on this server." when I click it.

So I used the Hitachi Drive Fitness Test, and I got an error after running the Exercise Test. The error read "Problem detected on a non-hitachi drive. Disposition 0x70"
I ran the "quick test" after that just to make sure and I got the same error.

So I guess I have a HDD issue? Do I need to buy a new hard drive?

Thanks for all the help so far, it is greatly appreciated!

EDIT: I ran the GPU test just to make sure, and got some weird results. The first time I ran it I walked away for a second and came back and my screen was black. I could not do anything and had to manual reboot.

I ran it a second time and watched it the whole time, it looked like it started at about 56 degrees and when it reached about 85 degrees / 7900 frames (this did not take long, I'd say 2 mins), the screen went black again and I had to manual reboot, once again. Does this mean I could have a gpu problem?

 

[Sublime]

http://img831.imageshack.us/img831/3630/furmark.jpg

Here is a screen of the GPU test, about 20 seconds before it would go black on me. I exited after the screen shot was taken because it would give me issues on the start up after this happened.

Opened the side of the PC and ran it a third time just to make sure.

All fans, including the one on the GPU were working. It went to about around 9000 frames this time, and around 87 degrees I think, then I got a red screen. Had to manual reboot. Is it possible I have a defective GPU and hard drive?

 

[Sublime]

Sorry for the triple post, but I am lost at the moment on what to do. Anyone have advice on what I should do from here with these test results?

 

[CarlTR6]

I did some searching for Fujitsu diagnostic tools and this is the best I could come up with. You might poke around further and see if any of this would diagnose your hard drive: support systemdiagnostics Fujitsu

It appears that you have a hard drive problem. Though a manufacturer's tool is best, have you run Disk Check?

Run CHKDSK /R /F from an elevated (Run as adminstrator) Command Prompt. Please do this for each hard drive on your system.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.

Elevated Command Prompt:
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"

CHKDSK LogFile:
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry (wininit for Windows 7) (winlogon for XP).

Copy/paste the results into your next post.

It also appears that you have a GPU problem. Do you have access to another card you can try in your machine?

 

[Sublime]

This one is the chkdsk /r I ran today.

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.                         

CHKDSK is verifying files (stage 1 of 5)...
  99328 file records processed.                                          File verification completed.
  74 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)...
  145398 index entries processed.                                         Index verification completed.
  0 unindexed files scanned.                                           0 unindexed files recovered.                                       CHKDSK is verifying security descriptors (stage 3 of 5)...
  99328 file SDs/SIDs processed.                                         Cleaning up 37 unused index entries from index $SII of file 0x9.
Cleaning up 37 unused index entries from index $SDH of file 0x9.
Cleaning up 37 unused security descriptors.
Security descriptor verification completed.
  23036 data files processed.                                            CHKDSK is verifying Usn Journal...
  33678496 USN bytes processed.                                             Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
  99312 files processed.                                                 File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
  47297000 free clusters processed.                                         Free space verification is complete.
Windows has checked the file system and found no problems.

 244196351 KB total disk space.
  54753244 KB in 73899 files.
     48852 KB in 23037 indexes.
         0 KB in bad sectors.
    206255 KB in use by the system.
     65536 KB occupied by the log file.
 189188000 KB available on disk.

      4096 bytes in each allocation unit.
  61049087 total allocation units on disk.
  47297000 allocation units available on disk.

Internal Info:
00 84 01 00 b3 7a 01 00 27 d6 02 00 00 00 00 00  .....z..'.......
71 01 00 00 2c 00 00 00 00 00 00 00 00 00 00 00  q...,...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................

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

This one ran automatically on a reboot a few days ago. It is different that the one I ran today.

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)...
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xbc5ce0 for possibly 0x40 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x16d27 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 93479.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xae2656 for possibly 0x10 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x16dfa is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 93690.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x8d4aac for possibly 0x4 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x16e57 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 93783.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x908b20 for possibly 0x4 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x16e58 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 93784.
  99328 file records processed.                                          File verification completed.
  70 large file records processed.                                      0 bad file records processed.                                        0 EA records processed.                                              44 reparse records processed.                                       CHKDSK is verifying indexes (stage 2 of 3)...
The file reference 0x36000000016d22 of index entry 0345F19Ed01 of index $I30
with parent 0x16df3 is not the same as 0x37000000016d22.
Deleting index entry 0345F19Ed01 in index $I30 of file 93683.
The file reference 0x36000000016d22 of index entry 0345F1~1 of index $I30
with parent 0x16df3 is not the same as 0x37000000016d22.
Deleting index entry 0345F1~1 in index $I30 of file 93683.
The file reference 0x3a000000014233 of index entry 04899F19d01 of index $I30
with parent 0x16df3 is not the same as 0x3b000000014233.
Deleting index entry 04899F19d01 in index $I30 of file 93683.
The file reference 0x3a000000014233 of index entry 04899F~1 of index $I30
with parent 0x16df3 is not the same as 0x3b000000014233.
Deleting index entry 04899F~1 in index $I30 of file 93683.
Unable to locate the file name attribute of index entry 089E3640d01
of index $I30 with parent 0x16df3 in file 0x15e05.
Deleting index entry 089E3640d01 in index $I30 of file 93683.
Unable to locate the file name attribute of index entry 089E36~1
of index $I30 with parent 0x16df3 in file 0x15e05.
Deleting index entry 089E36~1 in index $I30 of file 93683.
Unable to locate the file name attribute of index entry 0BD4A335d01
of index $I30 with parent 0x16df3 in file 0x15e5d.
Deleting index entry 0BD4A335d01 in index $I30 of file 93683.
Unable to locate the file name attribute of index entry 0BD4A3~1
of index $I30 with parent 0x16df3 in file 0x15e5d.
Deleting index entry 0BD4A3~1 in index $I30 of file 93683.
Unable to locate the file name attribute of index entry 13578709d01
of index $I30 with parent 0x16df3 in file 0x15a4a.
Deleting index entry 13578709d01 in index $I30 of file 93683.
Unable to locate the file name attribute of index entry 135787~1
of index $I30 with parent 0x16df3 in file 0x15a4a.
Deleting index entry 135787~1 in index $I30 of file 93683.
The file reference 0x6800000000fda6 of index entry 154AD8AFd01 of index $I30
with parent 0x16df3 is not the same as 0x6900000000fda6.
Deleting index entry 154AD8AFd01 in index $I30 of file 93683.
The file reference 0x6800000000fda6 of index entry 154AD8~1 of index $I30
with parent 0x16df3 is not the same as 0x6900000000fda6.
Deleting index entry 154AD8~1 in index $I30 of file 93683.
Unable to locate the file name attribute of index entry 174D464Fd01
of index $I30 with parent 0x16df3 in file 0x15a27.
Deleting index entry 174D464Fd01 in index $I30 of file 93683.
Unable to locate the file name attribute of index entry 174D46~1
of index $I30 with parent 0x16df3 in file 0x15a27.
Deleting index entry 174D46~1 in index $I30 of file 93683.
The file reference 0xe000000014d13 of index entry 1FD17E05d01 of index $I30
with parent 0x16df3 is not the same as 0x1b000000014d13.
Deleting index entry 1FD17E05d01 in index $I30 of file 93683.
The file reference 0xe000000014d13 of index entry 1FD17E~1 of index $I30
with parent 0x16df3 is not the same as 0x1b000000014d13.
Deleting index entry 1FD17E~1 in index $I30 of file 93683.
Unable to locate the file name attribute of index entry 25772C1Cd01
of index $I30 with parent 0x16df3 in file 0x15e01.
Deleting index entry 25772C1Cd01 in index $I30 of file 93683.
Unable to locate the file name attribute of index entry 25772C~1
of index $I30 with parent 0x16df3 in file 0x15e01.
Deleting index entry 25772C~1 in index $I30 of file 93683.
The file reference 0x6c000000015de9 of index entry 264DCE09d01 of index $I30
with parent 0x16df3 is not the same as 0x7e000000015de9.
Deleting index entry 264DCE09d01 in index $I30 of file 93683.
The file reference 0x6c000000015de9 of index entry 264DCE~1 of index $I30
with parent 0x16df3 is not the same as 0x7e000000015de9.
Deleting index entry 264DCE~1 in index $I30 of file 93683.
Unable to locate the file name attribute of index entry 2FE2146Fd01
of index $I30 with parent 0x16df3 in file 0x15d64.
Deleting index entry 2FE2146Fd01 in index $I30 of file 93683.
Unable to locate the file name attribute of index entry 2FE214~1
of index $I30 with parent 0x16df3 in file 0x15d64.
Deleting index entry 2FE214~1 in index $I30 of file 93683.
Unable to locate the file name attribute of index entry 383A263Ad01
of index $I30 with parent 0x16df3 in file 0x15a93.
Deleting index entry 383A263Ad01 in index $I30 of file 93683.
Unable to locate the file name attribute of index entry 383A26~1
of index $I30 with parent 0x16df3 in file 0x15a93.
Deleting index entry 383A26~1 in index $I30 of file 93683.
Index entry 38A5F42Ad01 of index $I30 in file 0x16df3 points to unused file 0xfd74.
Deleting index entry 38A5F42Ad01 in index $I30 of file 93683.
Index entry 38A5F4~1 of index $I30 in file 0x16df3 points to unused file 0xfd74.
Deleting index entry 38A5F4~1 in index $I30 of file 93683.
Unable to locate the file name attribute of index entry 47287710d01
of index $I30 with parent 0x16df3 in file 0x15700.
Deleting index entry 47287710d01 in index $I30 of file 93683.
Unable to locate the file name attribute of index entry 472877~1
of index $I30 with parent 0x16df3 in file 0x15700.
Deleting index entry 472877~1 in index $I30 of file 93683.
The file reference 0xf000000015ec9 of index entry 49F99E45d01 of index $I30
with parent 0x16df3 is not the same as 0x10000000015ec9.
Deleting index entry 49F99E45d01 in index $I30 of file 93683.
The file reference 0xf000000015ec9 of index entry 49F99E~1 of index $I30
with parent 0x16df3 is not the same as 0x10000000015ec9.
Deleting index entry 49F99E~1 in index $I30 of file 93683.
Unable to locate the file name attribute of index entry 4B5BEDCBd01
of index $I30 with parent 0x16df3 in file 0x15e36.
Deleting index entry 4B5BEDCBd01 in index $I30 of file 93683.
Unable to locate the file name attribute of index entry 4B5BED~1
of index $I30 with parent 0x16df3 in file 0x15e36.
Deleting index entry 4B5BED~1 in index $I30 of file 93683.
The file reference 0x43000000015a18 of index entry 4E8B5207d01 of index $I30
with parent 0x16df3 is not the same as 0x44000000015a18.
Deleting index entry 4E8B5207d01 in index $I30 of file 93683.
The file reference 0x43000000015a18 of index entry 4E8B52~1 of index $I30
with parent 0x16df3 is not the same as 0x44000000015a18.
Deleting index entry 4E8B52~1 in index $I30 of file 93683.
Unable to locate the file name attribute of index entry 4F93B444d01
of index $I30 with parent 0x16df3 in file 0x1537f.
Deleting index entry 4F93B444d01 in index $I30 of file 93683.
Unable to locate the file name attribute of index entry 4F93B4~1
of index $I30 with parent 0x16df3 in file 0x1537f.
Deleting index entry 4F93B4~1 in index $I30 of file 93683.
The file reference 0x420000000142d1 of index entry 58F3D5BAd01 of index $I30
with parent 0x16df3 is not the same as 0x500000000142d1.
Deleting index entry 58F3D5BAd01 in index $I30 of file 93683.
The file reference 0x420000000142d1 of index entry 58F3D5~1 of index $I30
with parent 0x16df3 is not the same as 0x500000000142d1.
Deleting index entry 58F3D5~1 in index $I30 of file 93683.
The file reference 0x4e000000016d1f of index entry 64BE5DFEd01 of index $I30
with parent 0x16df3 is not the same as 0x4f000000016d1f.
Deleting index entry 64BE5DFEd01 in index $I30 of file 93683.
The file reference 0x4e000000016d1f of index entry 64BE5D~1 of index $I30
with parent 0x16df3 is not the same as 0x4f000000016d1f.
Deleting index entry 64BE5D~1 in index $I30 of file 93683.
Unable to locate the file name attribute of index entry 654A3CD5d01
of index $I30 with parent 0x16df3 in file 0x15872.
Deleting index entry 654A3CD5d01 in index $I30 of file 93683.
Unable to locate the file name attribute of index entry 654A3C~1
of index $I30 with parent 0x16df3 in file 0x15872.
Deleting index entry 654A3C~1 in index $I30 of file 93683.
The file reference 0xc00000000ff8e of index entry 68DA3627d01 of index $I30
with parent 0x16df3 is not the same as 0x1000000000ff8e.
Deleting index entry 68DA3627d01 in index $I30 of file 93683.
The file reference 0xc00000000ff8e of index entry 68DA36~1 of index $I30
with parent 0x16df3 is not the same as 0x1000000000ff8e.
Deleting index entry 68DA36~1 in index $I30 of file 93683.
The file reference 0x3000000005497 of index entry 6B69F94Fd01 of index $I30
with parent 0x16df3 is not the same as 0xd000000005497.
Deleting index entry 6B69F94Fd01 in index $I30 of file 93683.
The file reference 0x3000000005497 of index entry 6B69F9~1 of index $I30
with parent 0x16df3 is not the same as 0xd000000005497.
Deleting index entry 6B69F9~1 in index $I30 of file 93683.
The file reference 0x15000000014d07 of index entry 734582A4d01 of index $I30
with parent 0x16df3 is not the same as 0x17000000014d07.
Deleting index entry 734582A4d01 in index $I30 of file 93683.
The file reference 0x15000000014d07 of index entry 734582~1 of index $I30
with parent 0x16df3 is not the same as 0x17000000014d07.
Deleting index entry 734582~1 in index $I30 of file 93683.
The file reference 0x6000000015e11 of index entry 7CF5B383d01 of index $I30
with parent 0x16df3 is not the same as 0xf000000015e11.
Deleting index entry 7CF5B383d01 in index $I30 of file 93683.
The file reference 0x6000000015e11 of index entry 7CF5B3~1 of index $I30
with parent 0x16df3 is not the same as 0xf000000015e11.
Deleting index entry 7CF5B3~1 in index $I30 of file 93683.
Unable to locate the file name attribute of index entry 7D14AEFDd01
of index $I30 with parent 0x16df3 in file 0x15dfd.
Deleting index entry 7D14AEFDd01 in index $I30 of file 93683.
Unable to locate the file name attribute of index entry 7D14AE~1
of index $I30 with parent 0x16df3 in file 0x15dfd.
Deleting index entry 7D14AE~1 in index $I30 of file 93683.
Unable to locate the file name attribute of index entry 832EE99Cd01
of index $I30 with parent 0x16df3 in file 0x158ae.
Deleting index entry 832EE99Cd01 in index $I30 of file 93683.
Unable to locate the file name attribute of index entry 832EE9~1
of index $I30 with parent 0x16df3 in file 0x158ae.
Deleting index entry 832EE9~1 in index $I30 of file 93683.
The file reference 0x18000000016c2e of index entry 87E0BB8Ad01 of index $I30
with parent 0x16df3 is not the same as 0x1a000000016c2e.
Deleting index entry 87E0BB8Ad01 in index $I30 of file 93683.
The file reference 0x18000000016c2e of index entry 87E0BB~1 of index $I30
with parent 0x16df3 is not the same as 0x1a000000016c2e.
Deleting index entry 87E0BB~1 in index $I30 of file 93683.
Unable to locate the file name attribute of index entry 8E40505Cd01
of index $I30 with parent 0x16df3 in file 0x15acd.
Deleting index entry 8E40505Cd01 in index $I30 of file 93683.
Unable to locate the file name attribute of index entry 8E4050~1
of index $I30 with parent 0x16df3 in file 0x15acd.
Deleting index entry 8E4050~1 in index $I30 of file 93683.
Index entry 9388DF35d01 of index $I30 in file 0x16df3 points to unused file 0x5412.
Deleting index entry 9388DF35d01 in index $I30 of file 93683.
Index entry 9388DF~1 of index $I30 in file 0x16df3 points to unused file 0x5412.
Deleting index entry 9388DF~1 in index $I30 of file 93683.
The file reference 0x27000000014d1b of index entry 94401B60d01 of index $I30
with parent 0x16df3 is not the same as 0x29000000014d1b.
Deleting index entry 94401B60d01 in index $I30 of file 93683.
The file reference 0x27000000014d1b of index entry 94401B~1 of index $I30
with parent 0x16df3 is not the same as 0x29000000014d1b.
Deleting index entry 94401B~1 in index $I30 of file 93683.
Unable to locate the file name attribute of index entry 9ACB56DBd01
of index $I30 with parent 0x16df3 in file 0x15e02.
Deleting index entry 9ACB56DBd01 in index $I30 of file 93683.
Unable to locate the file name attribute of index entry 9ACB56~1
of index $I30 with parent 0x16df3 in file 0x15e02.
Deleting index entry 9ACB56~1 in index $I30 of file 93683.
The file reference 0x2200000001306d of index entry 9C37D4E6d01 of index $I30
with parent 0x16df3 is not the same as 0x2300000001306d.
Deleting index entry 9C37D4E6d01 in index $I30 of file 93683.
The file reference 0x2200000001306d of index entry 9C37D4~1 of index $I30
with parent 0x16df3 is not the same as 0x2300000001306d.
Deleting index entry 9C37D4~1 in index $I30 of file 93683.
The file reference 0x12000000014d03 of index entry B28D4E5Cd01 of index $I30
with parent 0x16df3 is not the same as 0x15000000014d03.
Deleting index entry B28D4E5Cd01 in index $I30 of file 93683.
The file reference 0x12000000014d03 of index entry B28D4E~1 of index $I30
with parent 0x16df3 is not the same as 0x15000000014d03.
Deleting index entry B28D4E~1 in index $I30 of file 93683.
Index entry BB86F350d01 of index $I30 in file 0x16df3 points to unused file 0xfd73.
Deleting index entry BB86F350d01 in index $I30 of file 93683.
Index entry BB86F3~1 of index $I30 in file 0x16df3 points to unused file 0xfd73.
Deleting index entry BB86F3~1 in index $I30 of file 93683.
The file reference 0x14a00000000e0be of index entry BFB121F1d01 of index $I30
with parent 0x16df3 is not the same as 0x14b00000000e0be.
Deleting index entry BFB121F1d01 in index $I30 of file 93683.
The file reference 0x14a00000000e0be of index entry BFB121~1 of index $I30
with parent 0x16df3 is not the same as 0x14b00000000e0be.
Deleting index entry BFB121~1 in index $I30 of file 93683.
The file reference 0x3e00000000fe0c of index entry C184B047d01 of index $I30
with parent 0x16df3 is not the same as 0x3f00000000fe0c.
Deleting index entry C184B047d01 in index $I30 of file 93683.
The file reference 0x3e00000000fe0c of index entry C184B0~1 of index $I30
with parent 0x16df3 is not the same as 0x3f00000000fe0c.
Deleting index entry C184B0~1 in index $I30 of file 93683.
Unable to locate the file name attribute of index entry C3946A60d01
of index $I30 with parent 0x16df3 in file 0x15e65.
Deleting index entry C3946A60d01 in index $I30 of file 93683.
Unable to locate the file name attribute of index entry C3946A~1
of index $I30 with parent 0x16df3 in file 0x15e65.
Deleting index entry C3946A~1 in index $I30 of file 93683.
The file reference 0x6000000015e0d of index entry CCC1302Cd01 of index $I30
with parent 0x16df3 is not the same as 0x7000000015e0d.
Deleting index entry CCC1302Cd01 in index $I30 of file 93683.
The file reference 0x6000000015e0d of index entry CCC130~1 of index $I30

I also found the Western Digital hard drive diagnostics test for my hard drive. I will ran that one and post the results since that is my HDD manufacture.

 

[Capt.Jack Sparrow]

Hello,
I'm sorry i was caught up with some other stuff couldn't respond to your post. Please run the WD Diagnostic Tool. Then regarding the Funmark result I'm suspecting it might be Heat issues if not the something with the card. Open your side panel and point a mains fan squarely at the motherboard. That will rule out most (lack of) cooling issues. See if you could borrow Display card from a friend to test it.

Good Luck,
Captain

 

[Sublime]

Test Option: EXTENDED TEST Model Number: WDC WD2500AAJS-22VTA0 Unit Serial Number: WD-WMART1873685 Firmware Number: 01.01B01 Capacity: 250.06 GB SMART Status: PASS Test Result: PASS Test Time: 14:45:40, September 29, 2010

Results of the WD Test I just got finished running.

And I am not sure what you mean by the fan. Do you want me to unscrew the main fan on my PC, and face it towards the motherboard, and run the furmark test again?

Thanks again for all the help! I really do appreciate it.

 

[Capt.Jack Sparrow]

Test Option: EXTENDED TEST Model Number: WDC WD2500AAJS-22VTA0 Unit Serial Number: WD-WMART1873685 Firmware Number: 01.01B01 Capacity: 250.06 GB SMART Status: PASS Test Result: PASS Test Time: 14:45:40, September 29, 2010

Results of the WD Test I just got finished running.

And I am not sure what you mean by the fan. Do you want me to unscrew the main fan on my PC, and face it towards the motherboard, and run the furmark test again?

Thanks again for all the help! I really do appreciate it.

No ... Just the Home fan. Seems like the HDD came clean.

 

[Sublime]

Took the side off the PC and pointed the fan right at it, same results with the GPU test, crashed at about 2:00 mins of running.