Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

HP Boot Problem


  • Please log in to reply
15 replies to this topic

#1 mikako17

mikako17

  • Members
  • 58 posts
  • OFFLINE
  •  
  • Local time:06:11 PM

Posted 24 September 2012 - 08:05 PM

So the problem is that my laptop sometimes restarts and doesn't boot properly. The link to the topic in the Malware section is here.

I have a HP Pavilion dv4-1465dx with Windows Vista 64-bit.

BC AdBot (Login to Remove)

 


#2 jhayz

jhayz

  • BC Advisor
  • 6,922 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:10:11 AM

Posted 25 September 2012 - 12:40 AM

Download Speccy and then install the program. To post and publish a snapshot of your PC.
. In the Menu bar, click File -> Publish Snapshot
. Click Yes > then Copy to Clipboard
. On your next reply, right-click on a empty space and click Paste on reply box then click Post.

Is your laptop equipped with a BIOS or Windows Diagnostic test for the Hard drive and RAM modules?

Tekken
 


#3 mikako17

mikako17
  • Topic Starter

  • Members
  • 58 posts
  • OFFLINE
  •  
  • Local time:06:11 PM

Posted 25 September 2012 - 02:03 AM

Here it is, I ran it in Safe Mode since it wouldn't let me boot it in normal mode, it would flash blue and restart.

http://speccy.piriform.com/results/wWWlPbmPClikVhHSg1mCSS4

Yes, my laptop is equipped with a BIOS test fro hard drive and RAM modules.

#4 AustrAlien

AustrAlien

    Inquisitor


  • BC Advisor
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:12:11 PM

Posted 25 September 2012 - 02:12 AM

... it would flash blue and restart.

Let's have a closer look at that blue "flash", which is likely a BSOD (Blue Screen Of Death) with an error message.

Make the following change while in Windows Safe Mode, and then attempt to start Windows normally.

Disable automatic restart on system failure from within Windows:

Disable Automatic Restart .... VISTA
When the system fails it will not re-start: Instead, you will see a BSOD (blue screen of death) with error message, such as the example shown below:
  • Posted Image
  • Record the error message details, which will be contained in the areas indicated within the red lines in the above image.

    Please post the error details.
When you have recorded the error message, you will need to press the RESTART button or the ON/OFF button (and hold for 5 seconds), to restart/switch off the computer.

Edited by AustrAlien, 25 September 2012 - 02:23 AM.

AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#5 mikako17

mikako17
  • Topic Starter

  • Members
  • 58 posts
  • OFFLINE
  •  
  • Local time:06:11 PM

Posted 25 September 2012 - 02:34 AM

Okay here it is:

A process or thread crucial to system operation has unexpectedly exited or been terminated.

***STOP: 0x000000F4 (0x0000000000000003, 0xFFFFFA8006504040, 0xFFFFFA8006504278, 0xFFFFF80002928c90)

#6 AustrAlien

AustrAlien

    Inquisitor


  • BC Advisor
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:12:11 PM

Posted 25 September 2012 - 02:45 AM

STOP 0x000000F4: CRITICAL_OBJECT_TERMINATION

That's an interesting one! :thumbup2:
  • Please let us know if any BSODs that you see from now on are different at all to that STOP 0x000000F4 error.
When/If you get Windows started normally, please run Speccy again and publish a snapshot/post a link: The result of running Speccy in Safe Mode is of little/no use to us.

I realise that your system is not saving crash dumps, but I would like to see the other information that is also collected using the following method (which can be done in Safe Mode with networking).

Please follow the instructions: Blue Screen of Death (BSOD) Posting Instructions - Windows 8, 7 & Vista

(Note: When you run BSOD_Windows7_Vista_v2.64_jcgriff2_.exe, it will also run autoruns.exe ... and both need to be in the Documents folder!)
... with one exception to the following line under Step 4:
  • "Create a new thread HERE and attach the file(s)."
The BC forums will allow a total attachment size of only 512 kb (and what you need to attach will exceed this limit).
  • Please upload the zip file to a file sharing website of your choice and and post a link to it in this thread so that we can access your uploaded zip file.
See the suggestions in the following links for recommendations on file sharing websites:
  • http://lifehacker.com/388284/best-online-file-sharing-services
  • http://www.hongkiat.com/blog/15-great-free-online-file-sharing-alternatives/
  • http://www.smashingapps.com/2008/08/28/5-best-free-file-hosting-services-to-store-your-files.html

    I can recommend Posted Image: Also suitable is Posted Image

Edited by AustrAlien, 25 September 2012 - 03:04 AM.

AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#7 mikako17

mikako17
  • Topic Starter

  • Members
  • 58 posts
  • OFFLINE
  •  
  • Local time:06:11 PM

Posted 25 September 2012 - 03:18 AM

Here you go, I'll try and see if I can get it to boot to normal mode.

#8 AustrAlien

AustrAlien

    Inquisitor


  • BC Advisor
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:12:11 PM

Posted 25 September 2012 - 07:23 AM

Change your system's settings so that crash dumps will be saved, and the crash/dump events logged.
  • Your system is currently set to do neither.
Configure Dump File Settings in "Startup and Recovery"
After a crash, check the Minidump folder to see if a minidump has been created:
  • It is quite possible that your STOP 0xF4 crashes will not produce a saved dump, even with the settings configured correctly to save the dump.
  • If you find a minidump, zip it up and attach the zipped file to a reply.
  • Navigate to C:\Windows\Minidump <<< folder
    The minidumps will be found inside this folder.
  • Right-click on the minidump file > Send to ... > Compressed (zipped) Folder.
    The zip file will be located in the same place (the Minidump folder).
  • Attach the zip file to your next reply.
    When you click on Add Reply, you will see the facility to attach a file just below the box where you type your message.

AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#9 mikako17

mikako17
  • Topic Starter

  • Members
  • 58 posts
  • OFFLINE
  •  
  • Local time:06:11 PM

Posted 25 September 2012 - 10:08 AM

Here is speccy.

#10 AustrAlien

AustrAlien

    Inquisitor


  • BC Advisor
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:12:11 PM

Posted 25 September 2012 - 03:38 PM

S.M.A.R.T. data taken from the Speccy report:
Hard Drives
FUJITSU MJA2320BH G2 ATA Device
Manufacturer: Unknown manufacturer

S.M.A.R.T
01 Read Error Rate: 100 (076 worst) Data 00000304FE
02 Throughput Performance: 253 (253) Data 0002D10000
03 Spin-Up Time: 100 (100) Data 0000000001
04 Start/Stop Count: 099 (099) Data 0000000C5A
05 Reallocated Sectors Count: 253 (253) Data 0000000000
07 Seek Error Rate: 100 (100) Data 0000000AAD
08 Seek Time Performance: 253 (253) Data 0000000000
09 Power-On Hours (POH): 073 (073) Data 00000035B2
0A Spin Retry Count: 253 (253) Data 0000000000
0B Recalibration Retries: 253 (253) Data 0000000000
0C Device Power Cycle Count: 100 (100) Data 0000000C2A
B4: 100 (100) Data 0000000000
B6: 100 (100) Data 0000000000
B7 SATA Downshift Error Count: 253 (253) Data 0000000000
B8 End-to-End error / IOEDC: 253 (253) Data 0000000000
B9: 253 (253) Data 0000000000
BA: 099 (099) Data 00001D0001
BB Reported Uncorrectable Errors: 100 (001) Data 0000651A03
BC Command Timeout: 100 (099) Data 000006001D
BD High Fly Writes (WDC): 253 (100) Data 0000000000
BE Temperature Difference from 100: 069 (033) Data 001F15001F
BF G-sense error rate: 253 (098) Data 0000FD000C
C0 Power-off Retract Count: 100 (100) Data 0000930093
C1 Load/Unload Cycle Count: 099 (099) Data 00000076F4
C3 Hardware ECC Recovered: 253 (253) Data 00000015D5
C4 Reallocation Event Count: 253 (253) Data 0000000000
C5 Current Pending Sector Count: 001 (001) Data 00000000FF
C6 Uncorrectable Sector Count: 253 (253) Data 0000000000
C7 UltraDMA CRC Error Count: 253 (253) Data 0000000003
The hard drive is failing!

C5 Current Pending Sector Count: 001 (001) Data 00000000FF >>> converts to decimal 255

255 sectors on the hard drive are reported to be unreadable/problematic.

:exclame: Ensure that you have all important personal files backed up to a physically separate device and that you have all preparations in place to replace the failing hard drive with a new one, including the means to install the Windows operating system on a new hard drive! :exclame:

Please check for any existing logs that chkdsk may have created and post them. To open Event Viewer and view the log:
  • Go to Start > and type eventvwr and press the <ENTER> key.
    The Event Viewer window will open.
  • In the left pane, expand "Windows Logs" and then click on Application.
  • In the right pane, at the top, click on the column heading Source to sort the list alphabetically.
  • Look in the Source column for "Wininit", with an entry corresponding to the date and time of the disk check.
  • Click on a Wininit entry to select it.
  • On the top main menu, click Action > Copy > Copy Details as Text.
  • Paste the log text into your next reply.
    Please post all recent chkdsk logs.

AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#11 mikako17

mikako17
  • Topic Starter

  • Members
  • 58 posts
  • OFFLINE
  •  
  • Local time:06:11 PM

Posted 25 September 2012 - 03:47 PM

Here's 9/14/2012:
Log Name: Application
Source: Microsoft-Windows-Wininit
Date: 9/14/2012 4:41:56 PM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: FIRST
Description:


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.
448064 file records processed.

1337 large file records processed.

0 bad file records processed.

0 EA records processed.

74 reparse records processed.

Index entry SADA1E~1 of index $I30 in file 0x26b02 points to unused file 0x2b9e5.
Deleting index entry SADA1E~1 in index $I30 of file 158466.
Index entry Safe Browsing Download Whitelist_new of index $I30 in file 0x26b02 points to unused file 0x2b9e5.
Deleting index entry Safe Browsing Download Whitelist_new in index $I30 of file 158466.
The file reference 0x20000000018750 of index entry Preferences of index $I30
with parent 0x26b0b is not the same as 0x21000000018750.
Deleting index entry Preferences in index $I30 of file 158475.
The file reference 0x20000000018750 of index entry PREFER~1 of index $I30
with parent 0x26b0b is not the same as 0x21000000018750.
Deleting index entry PREFER~1 in index $I30 of file 158475.
548916 index entries processed.

CHKDSK is recovering lost files.
1 unindexed files processed.

Recovering orphaned file {306ED~1 (100176) into directory file 80114.
Recovering orphaned file {306ed198-6bdd-4fa9-a895-553db1768008} (100176) into directory file 80114.
448064 security descriptors processed.

Cleaning up 221 unused index entries from index $SII of file 0x9.
Cleaning up 221 unused index entries from index $SDH of file 0x9.
Cleaning up 221 unused security descriptors.
50427 data files processed.

CHKDSK is verifying Usn Journal...
35815152 USN bytes processed.

Usn Journal verification completed.
Correcting errors in the master file table's (MFT) BITMAP attribute.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.

300317695 KB total disk space.
161715636 KB in 262076 files.
149896 KB in 50428 indexes.
368 KB in bad sectors.
505923 KB in use by the system.
4096 KB occupied by the log file.
137945872 KB available on disk.

4096 bytes in each allocation unit.
75079423 total allocation units on disk.
34486468 allocation units available on disk.

Internal Info:
40 d6 06 00 c3 c4 04 00 22 5d 08 00 00 00 00 00 @......."]......
a9 15 00 00 4a 00 00 00 00 00 00 00 00 00 00 00 ....J...........
30 c7 fd 76 00 00 00 00 50 23 78 ff 00 00 00 00 0..v....P#x.....

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

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/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="2012-09-14T23:41:56.000Z" />
<EventRecordID>77042</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>FIRST</Computer>
<Security />
</System>
<EventData>
<Data>

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.
448064 file records processed.

1337 large file records processed.

0 bad file records processed.

0 EA records processed.

74 reparse records processed.

Index entry SADA1E~1 of index $I30 in file 0x26b02 points to unused file 0x2b9e5.
Deleting index entry SADA1E~1 in index $I30 of file 158466.
Index entry Safe Browsing Download Whitelist_new of index $I30 in file 0x26b02 points to unused file 0x2b9e5.
Deleting index entry Safe Browsing Download Whitelist_new in index $I30 of file 158466.
The file reference 0x20000000018750 of index entry Preferences of index $I30
with parent 0x26b0b is not the same as 0x21000000018750.
Deleting index entry Preferences in index $I30 of file 158475.
The file reference 0x20000000018750 of index entry PREFER~1 of index $I30
with parent 0x26b0b is not the same as 0x21000000018750.
Deleting index entry PREFER~1 in index $I30 of file 158475.
548916 index entries processed.

CHKDSK is recovering lost files.
1 unindexed files processed.

Recovering orphaned file {306ED~1 (100176) into directory file 80114.
Recovering orphaned file {306ed198-6bdd-4fa9-a895-553db1768008} (100176) into directory file 80114.
448064 security descriptors processed.

Cleaning up 221 unused index entries from index $SII of file 0x9.
Cleaning up 221 unused index entries from index $SDH of file 0x9.
Cleaning up 221 unused security descriptors.
50427 data files processed.

CHKDSK is verifying Usn Journal...
35815152 USN bytes processed.

Usn Journal verification completed.
Correcting errors in the master file table's (MFT) BITMAP attribute.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.

300317695 KB total disk space.
161715636 KB in 262076 files.
149896 KB in 50428 indexes.
368 KB in bad sectors.
505923 KB in use by the system.
4096 KB occupied by the log file.
137945872 KB available on disk.

4096 bytes in each allocation unit.
75079423 total allocation units on disk.
34486468 allocation units available on disk.

Internal Info:
40 d6 06 00 c3 c4 04 00 22 5d 08 00 00 00 00 00 @......."]......
a9 15 00 00 4a 00 00 00 00 00 00 00 00 00 00 00 ....J...........
30 c7 fd 76 00 00 00 00 50 23 78 ff 00 00 00 00 0..v....P#x.....

Windows has finished checking your disk.
Please wait while your computer restarts.
</Data>
</EventData>
</Event>

7/25/12
Log Name: Application
Source: Microsoft-Windows-Wininit
Date: 7/25/2012 12:38:44 PM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: First.stanford.edu
Description:


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.
448064 file records processed.

1362 large file records processed.

0 bad file records processed.

0 EA records processed.

76 reparse records processed.

The file reference 0x371000000008730 of index entry SiteTemp of index $I30
with parent 0x191c8 is not the same as 0x372000000008730.
Deleting index entry SiteTemp in index $I30 of file 102856.
546714 index entries processed.

CHKDSK is recovering lost files.
Recovering orphaned file SYMEFA~1.DB- (34608) into directory file 104018.
Recovering orphaned file SYMEFA.DB-journal (34608) into directory file 104018.
Recovering orphaned file NCWPER~1.DB- (102930) into directory file 81951.
Recovering orphaned file ncwperfm.db-journal (102930) into directory file 81951.
Recovering orphaned file MU28FB~1 (102998) into directory file 87111.
Recovering orphaned file musdmys_pmWMMr4LP8juuFQ8lakI (102998) into directory file 87111.
Recovering orphaned file WER8E7~1.TXT (103004) into directory file 9491.
Recovering orphaned file WER8E79.tmp.version.txt (103004) into directory file 9491.
6 unindexed files processed.

Recovering orphaned file SUBSCR~1.DAT (103007) into directory file 689.
Recovering orphaned file Subscription for role 279493.dat (103007) into directory file 689.
448064 security descriptors processed.

Cleaning up 169 unused index entries from index $SII of file 0x9.
Cleaning up 169 unused index entries from index $SDH of file 0x9.
Cleaning up 169 unused security descriptors.
49326 data files processed.

CHKDSK is verifying Usn Journal...
The USN Journal entry at offset 0x3b00ccb28 and length 0xaee095ae crosses
the page boundary.
The USN Journal entry at offset 0x3b00cd000 and length 0x2681afe0 crosses
the page boundary.
The USN Journal entry at offset 0x3b00ce000 and length 0x9aaee020 crosses
the page boundary.
The USN Journal entry at offset 0x3b00cf000 and length 0xa4aee08d crosses
the page boundary.
The USN Journal entry at offset 0x3b00d0000 and length 0xb5aee0af crosses
the page boundary.
The USN Journal entry at offset 0x3b00d1000 and length 0xaee08daf crosses
the page boundary.
The USN Journal entry at offset 0x3b00d2000 and length 0xe02ea9ae crosses
the page boundary.
The USN Journal entry at offset 0x3b00d3000 and length 0xe0a4aee0 crosses
the page boundary.
The USN Journal entry at offset 0x3b00d4000 and length 0xe0b4aee0 crosses
the page boundary.
The USN Journal entry at offset 0x3b00d5000 and length 0xe0bfaee0 crosses
the page boundary.
The USN Journal entry at offset 0x3b00d6000 and length 0xe08dafe0 crosses
the page boundary.
The USN Journal entry at offset 0x3b00d7000 and length 0xe09aaee0 crosses
the page boundary.
Repairing Usn Journal file record segment.
18596728 USN bytes processed.

Usn Journal verification completed.
Correcting errors in the master file table's (MFT) BITMAP attribute.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.

300317695 KB total disk space.
199599728 KB in 243851 files.
148700 KB in 49328 indexes.
0 KB in bad sectors.
488915 KB in use by the system.
4096 KB occupied by the log file.
100080352 KB available on disk.

4096 bytes in each allocation unit.
75079423 total allocation units on disk.
25020088 allocation units available on disk.

Internal Info:
40 d6 06 00 45 79 04 00 35 ec 07 00 00 00 00 00 @...Ey..5.......
9c 15 00 00 4c 00 00 00 00 00 00 00 00 00 00 00 ....L...........
30 c7 5a 77 00 00 00 00 50 23 46 ff 00 00 00 00 0.Zw....P#F.....

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

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/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="2012-07-25T19:38:44.000Z" />
<EventRecordID>71781</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>First.stanford.edu</Computer>
<Security />
</System>
<EventData>
<Data>

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.
448064 file records processed.

1362 large file records processed.

0 bad file records processed.

0 EA records processed.

76 reparse records processed.

The file reference 0x371000000008730 of index entry SiteTemp of index $I30
with parent 0x191c8 is not the same as 0x372000000008730.
Deleting index entry SiteTemp in index $I30 of file 102856.
546714 index entries processed.

CHKDSK is recovering lost files.
Recovering orphaned file SYMEFA~1.DB- (34608) into directory file 104018.
Recovering orphaned file SYMEFA.DB-journal (34608) into directory file 104018.
Recovering orphaned file NCWPER~1.DB- (102930) into directory file 81951.
Recovering orphaned file ncwperfm.db-journal (102930) into directory file 81951.
Recovering orphaned file MU28FB~1 (102998) into directory file 87111.
Recovering orphaned file musdmys_pmWMMr4LP8juuFQ8lakI (102998) into directory file 87111.
Recovering orphaned file WER8E7~1.TXT (103004) into directory file 9491.
Recovering orphaned file WER8E79.tmp.version.txt (103004) into directory file 9491.
6 unindexed files processed.

Recovering orphaned file SUBSCR~1.DAT (103007) into directory file 689.
Recovering orphaned file Subscription for role 279493.dat (103007) into directory file 689.
448064 security descriptors processed.

Cleaning up 169 unused index entries from index $SII of file 0x9.
Cleaning up 169 unused index entries from index $SDH of file 0x9.
Cleaning up 169 unused security descriptors.
49326 data files processed.

CHKDSK is verifying Usn Journal...
The USN Journal entry at offset 0x3b00ccb28 and length 0xaee095ae crosses
the page boundary.
The USN Journal entry at offset 0x3b00cd000 and length 0x2681afe0 crosses
the page boundary.
The USN Journal entry at offset 0x3b00ce000 and length 0x9aaee020 crosses
the page boundary.
The USN Journal entry at offset 0x3b00cf000 and length 0xa4aee08d crosses
the page boundary.
The USN Journal entry at offset 0x3b00d0000 and length 0xb5aee0af crosses
the page boundary.
The USN Journal entry at offset 0x3b00d1000 and length 0xaee08daf crosses
the page boundary.
The USN Journal entry at offset 0x3b00d2000 and length 0xe02ea9ae crosses
the page boundary.
The USN Journal entry at offset 0x3b00d3000 and length 0xe0a4aee0 crosses
the page boundary.
The USN Journal entry at offset 0x3b00d4000 and length 0xe0b4aee0 crosses
the page boundary.
The USN Journal entry at offset 0x3b00d5000 and length 0xe0bfaee0 crosses
the page boundary.
The USN Journal entry at offset 0x3b00d6000 and length 0xe08dafe0 crosses
the page boundary.
The USN Journal entry at offset 0x3b00d7000 and length 0xe09aaee0 crosses
the page boundary.
Repairing Usn Journal file record segment.
18596728 USN bytes processed.

Usn Journal verification completed.
Correcting errors in the master file table's (MFT) BITMAP attribute.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.

300317695 KB total disk space.
199599728 KB in 243851 files.
148700 KB in 49328 indexes.
0 KB in bad sectors.
488915 KB in use by the system.
4096 KB occupied by the log file.
100080352 KB available on disk.

4096 bytes in each allocation unit.
75079423 total allocation units on disk.
25020088 allocation units available on disk.

Internal Info:
40 d6 06 00 45 79 04 00 35 ec 07 00 00 00 00 00 @...Ey..5.......
9c 15 00 00 4c 00 00 00 00 00 00 00 00 00 00 00 ....L...........
30 c7 5a 77 00 00 00 00 50 23 46 ff 00 00 00 00 0.Zw....P#F.....

Windows has finished checking your disk.
Please wait while your computer restarts.
</Data>
</EventData>
</Event>

Would you like one's earlier than this?

#12 AustrAlien

AustrAlien

    Inquisitor


  • BC Advisor
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:12:11 PM

Posted 25 September 2012 - 03:58 PM

Would you like one's earlier than this?

No, there is nothing of use we can now do with them. They do verify that there has been significant file damage and loss of data caused by failing sectors on the hard drive.

368 KB in bad sectors.


Let me know your situation, and what you intend to do/would like to do at this stage, and ask any questions that you may have.
  • I suggest that you replace the hard drive and install a fresh copy of Windows without further ado.

AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#13 mikako17

mikako17
  • Topic Starter

  • Members
  • 58 posts
  • OFFLINE
  •  
  • Local time:06:11 PM

Posted 25 September 2012 - 05:26 PM

Thanks, I'll most likely get a new hard drive at a later date and then refurbish this laptop for a younger sibling. I've been looking to get a new laptop anyway. :/

#14 AustrAlien

AustrAlien

    Inquisitor


  • BC Advisor
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:12:11 PM

Posted 25 September 2012 - 05:48 PM

No worries! :thumbsup2:

Good luck.
AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#15 mikako17

mikako17
  • Topic Starter

  • Members
  • 58 posts
  • OFFLINE
  •  
  • Local time:06:11 PM

Posted 25 September 2012 - 07:20 PM

Thanks for all your guys' help, you're all amazing :D




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users