Dell Inspiron 570 Boot Trouble

[Xnaut]

Hello World! A few weeks back my Dell started acting up after being shutdown for the night. When I try to turn it on the screen shows that no "boot device available" or "HDD failure." Funny thing is when I shutdown through my power button and try turning it on again, it works normally and Windows boots up.

I read online that it may be the CMOS, nope. Tried to replace the old SATA cables in hopes that there was a bad connection with my old ones, nope. Tried defragmenting(Surprised that I had 7.0gb worth of data fragmented, then again I got the computer back in '09 and never did defragment it) because Windows may have had its boot sectors messed up, nope. Tried switching the placement of the new SATA cables, moved HDD to SATA-1, CD Drive to SATA-0, nope.

When I was testing my new SATA cables by powering up, shutting down, and powering up right after shutdown a few times, Windows loaded normally. But when I waited for five minutes and then tried to turn it on, I got the "HDD failure." But it still worked after I tried turning it on the second time around.

Another funny thing that I saw after switching the SATA placement, was when I logged in I got a little Windows detecting hardware symbol, with it popping up and telling me that it installed new drivers for my CD Drive, and HDD.

Anyone have an idea as to what I should try to do next?

Moved from General Hardware

mfenn
General Hardware Moderator

 

[denis280]

open CMD and type in CHKDSK come back with result

 

[Steltek]

The next time you get it working, it would be a good idea to backup your data pronto in case the hard drive is actually failing so you don't loose anything important.

If running CHKDSK like Denis said doesn't come back with anything, try running SFC /SCANNOW from an elevated command prompt to check for corrupted system files.

 

[Xnaut]

C:\Windows\system32>chkdsk
The type of the file system is NTFS.
Volume label is OS.

WARNING! F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
299008 file records processed.
File verification completed.
729 large file records processed.
0 bad file records processed.
0 EA records processed.
63 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 3)...
360056 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered.
CHKDSK is verifying security descriptors (stage 3 of 3)...
299008 file SDs/SIDs processed.
Security descriptor verification completed.
30525 data files processed.
CHKDSK is verifying Usn Journal...
34970856 USN bytes processed.
Usn Journal verification completed.
Windows has checked the file system and found no problems.

961187839 KB total disk space.
90218008 KB in 131137 files.
91392 KB in 30526 indexes.
0 KB in bad sectors.
434511 KB in use by the system.
65536 KB occupied by the log file.
870443928 KB available on disk.

4096 bytes in each allocation unit.
240296959 total allocation units on disk.
217610982 allocation units available on disk.

 

[Xnaut]

C:\Windows\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection found corrupt files but was unable to fix some of th
em.
Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example
C:\Windows\Logs\CBS\CBS.log

 

[Ketchup]

http://www.howtogeek.com/134735/how-to-see-if-your-hard-drive-is-dying/

Here is a link to a simple SMART test for your drive. See what comes up here.

On the surface, it sounds like there might be a problem with the hard drive motor, or the power supply not delivering enough juice until warmed up.

The hard drive and cdrom drive messages are normal since you switched ports for each. Windows just has to assign it a device driver, now that they are at different location.

 

[Xnaut]

...

 

[Xnaut]

...

 

[Xnaut]

...

 

[Xnaut]

...

 

[Xnaut]

...

 

[Xnaut]

WHOLE BUNCH OF TEXT

POQ 143 ends.
2015-07-31 16:36:49, Info CSI 0000035a [SR] Repair complete
2015-07-31 16:36:49, Info CSI 0000035b [SR] Committing transaction
2015-07-31 16:36:49, Info CSI 0000035c Creating NT transaction (seq 2), objectname [6]"(null)"
2015-07-31 16:36:49, Info CSI 0000035d Created NT transaction (seq 2) result 0x00000000, handle @0x7d0
2015-07-31 16:36:49, Info CSI 0000035e@2015/7/31:21:36:49.472 CSI perf trace:
CSIPERF:TXCOMMIT;113968
2015-07-31 16:36:49, Info CSI 0000035f [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired

 

[Xnaut]

The hard drive and cdrom drive messages are normal since you switched ports for each. Windows just has to assign it a device driver, now that they are at different location.

Got it, will proceed with the SMART test, thanks for the pointer about the messages, I was confused before but now it makes sense.

 

[Steltek]

The segments of the CBS.log file you posted don't show what files can't be fixed. You need to figure out which files that SFC couldn't fix so you can do a manual repair.

Right-click and copy the CBS.log file. Copy it to your desktop.

Load the CBS.log file into notepad or the text editor of your choice. Use the search function to look within the file for the term cannot repair. Any occurrences of this text should correspond to the file names that are corrupt but which can't be fixed by SFC, i.e. the files you need to fix.

If your CBS log file is huge, you might want to rename the CBS.log file to CBS.bak, then run SFC /scannow again from an elevated command prompt to recreate the log without all the extra junk to make it easier to search.

Post back the names of the corrupt files.

 

[Xnaut]

If your CBS log file is huge, you might want to rename the CBS.log file to CBS.bak, then run SFC /scannow again from an elevated command prompt to recreate the log without all the extra junk to make it easier to search.

Post back the names of the corrupt files.

Will do

 

[Xnaut]

POQ 73 ends.
2015-07-31 16:31:33, Info CSI 000001b3 [SR] Verify complete
2015-07-31 16:31:33, Info CSI 000001b4 [SR] Verifying 100 (0x0000000000000064) components
2015-07-31 16:31:33, Info CSI 000001b5 [SR] Beginning Verify and Repair transaction
2015-07-31 16:31:33, Info CSI 000001b6 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18869_none_fde7d5f71db043ad\utc.app.json do not match actual file [l:24{12}]"utc.app.json" :
Found: {l:32 b:hxHfXj427JxbVLpmOJKBMMwJ3nfvwV57qrOPwblWU6s=} Expected: {l:32 b:6510UErwHGoFg3sRd3gzh3HSbTceuHem3Rnk0NraKS8=}
2015-07-31 16:31:33, Info CSI 000001b7 [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-07-31 16:31:33, Info CSI 000001b8 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18869_none_fde7d5f71db043ad\telemetry.ASM-WindowsDefault.json do not match actual file [l:66{33}]"telemetry.ASM-WindowsDefault.json" :
Found: {l:32 b:gjV6+IPBrpEZS/JCJakDHCFmoTeES1ACzz83yCz1Myk=} Expected: {l:32 b:EeQJzlVPvq9GNIcA2FEwrOjEeuDam1G+ol3x61gKasQ=}
2015-07-31 16:31:33, Info CSI 000001b9 [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-07-31 16:31:36, Info CSI 000001ba Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18869_none_fde7d5f71db043ad\utc.app.json do not match actual file [l:24{12}]"utc.app.json" :
Found: {l:32 b:hxHfXj427JxbVLpmOJKBMMwJ3nfvwV57qrOPwblWU6s=} Expected: {l:32 b:6510UErwHGoFg3sRd3gzh3HSbTceuHem3Rnk0NraKS8=}
2015-07-31 16:31:36, Info CSI 000001bb [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-07-31 16:31:36, Info CSI 000001bc [SR] This component was referenced by [l:162{81}]"Package_250_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.3068708-814_neutral_GDR"
2015-07-31 16:31:36, Info CSI 000001bd Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18869_none_fde7d5f71db043ad\telemetry.ASM-WindowsDefault.json do not match actual file [l:66{33}]"telemetry.ASM-WindowsDefault.json" :
Found: {l:32 b:gjV6+IPBrpEZS/JCJakDHCFmoTeES1ACzz83yCz1Myk=} Expected: {l:32 b:EeQJzlVPvq9GNIcA2FEwrOjEeuDam1G+ol3x61gKasQ=}
2015-07-31 16:31:36, Info CSI 000001be [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-07-31 16:31:36, Info CSI 000001bf [SR] This component was referenced by [l:162{81}]"Package_250_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.3068708-814_neutral_GDR"
2015-07-31 16:31:36, Info CSI 000001c0 Ignoring duplicate ownership for directory [l:92{46}]"\??\C:\ProgramData\Microsoft\Diagnosis\ETLLogs" in component Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral

 

[Xnaut]

POQ 142 ends.
2015-07-31 16:36:49, Info CSI 0000034b [SR] Verify complete
2015-07-31 16:36:49, Info CSI 0000034c [SR] Repairing 1 components
2015-07-31 16:36:49, Info CSI 0000034d [SR] Beginning Verify and Repair transaction
2015-07-31 16:36:49, Info CSI 0000034e Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18869_none_fde7d5f71db043ad\utc.app.json do not match actual file [l:24{12}]"utc.app.json" :
Found: {l:32 b:hxHfXj427JxbVLpmOJKBMMwJ3nfvwV57qrOPwblWU6s=} Expected: {l:32 b:6510UErwHGoFg3sRd3gzh3HSbTceuHem3Rnk0NraKS8=}
2015-07-31 16:36:49, Info CSI 0000034f [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-07-31 16:36:49, Info CSI 00000350 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18869_none_fde7d5f71db043ad\telemetry.ASM-WindowsDefault.json do not match actual file [l:66{33}]"telemetry.ASM-WindowsDefault.json" :
Found: {l:32 b:gjV6+IPBrpEZS/JCJakDHCFmoTeES1ACzz83yCz1Myk=} Expected: {l:32 b:EeQJzlVPvq9GNIcA2FEwrOjEeuDam1G+ol3x61gKasQ=}
2015-07-31 16:36:49, Info CSI 00000351 [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-07-31 16:36:49, Info CSI 00000352 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18869_none_fde7d5f71db043ad\utc.app.json do not match actual file [l:24{12}]"utc.app.json" :
Found: {l:32 b:hxHfXj427JxbVLpmOJKBMMwJ3nfvwV57qrOPwblWU6s=} Expected: {l:32 b:6510UErwHGoFg3sRd3gzh3HSbTceuHem3Rnk0NraKS8=}
2015-07-31 16:36:49, Info CSI 00000353 [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-07-31 16:36:49, Info CSI 00000354 [SR] This component was referenced by [l:162{81}]"Package_250_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.3068708-814_neutral_GDR"
2015-07-31 16:36:49, Info CSI 00000355 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18869_none_fde7d5f71db043ad\telemetry.ASM-WindowsDefault.json do not match actual file [l:66{33}]"telemetry.ASM-WindowsDefault.json" :
Found: {l:32 b:gjV6+IPBrpEZS/JCJakDHCFmoTeES1ACzz83yCz1Myk=} Expected: {l:32 b:EeQJzlVPvq9GNIcA2FEwrOjEeuDam1G+ol3x61gKasQ=}
2015-07-31 16:36:49, Info CSI 00000356 [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-07-31 16:36:49, Info CSI 00000357 [SR] This component was referenced by [l:162{81}]"Package_250_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.3068708-814_neutral_GDR"
2015-07-31 16:36:49, Info CSI 00000358 Ignoring duplicate ownership for directory [l:92{46}]"\??\C:\ProgramData\Microsoft\Diagnosis\ETLLogs" in component Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral

 

[Xnaut]

Those were the only two sections, anything serious?

 

[Steltek]

Microsoft had a broken update for Win10 readiness back a few months ago that caused file corruption. They replaced the update four different times and I don't know if they ever actually got it right. That update caused a lot of headaches for a lot of folks, including myself -- it took me a month of work and two failed repair installs of Win7 before I finally found the solution. Until then, it was a coin flip as to whether my machine would shut down or even restart. It was also throwing NTFS bluescreen errors randomly when put to sleep.

Launch Windows Update. At the bottom left side of the Windows Update window, click on the Installed Updates link. Look through the installed updates for KB3022345. It it shown as installed?

Also, what version of Windows are you running, 7, 8, or 8.1? Are you running 32bit or 64 bit Windows?

You didn't say, so I'm presuming that the SMART testing Ketchup suggested didn't show any problems with your hard drive. By any chance, did you also happen to try running Dell's onboard diagnostics?