Tech Support Guy banner
Status
Not open for further replies.

Solved: Systems hangs, then BSOD, then BIOS loses my hdd.

1K views 9 replies 2 participants last post by  pugly 
#1 ·
I recently tried to troubleshoot some errors I saw in the event viewer. I forget what the feature is called, but windows has some startup option that will check your drivers for the right signing or something like that? So when I tried it, windows started failing to boot. Not knowing that I could disable the startup program again from safe mode, I instead did a refresh from my disc.

Thins seemed to go well after that until I started reinstalling Norton 360 while windows update was going at the same time. Windows froze up for the longest time, then I got the BSOD and when the computer rebooted itself, my computer couldn't find anything to boot. I checked BIOS and my hdd was missing from the bootup list. I was able to put it back in the startup list, and things were normal from there.

Got all my updates and everything, Norton seems to be working. But about once a week or so, usually while I'm web browsing, my computer starts to get super slow, and sometimes it eventually hangs. Sometimes when it hangs, I can wait it out and it'll recover. But sometimes, I get the BSOD again.

Now, when it happens, my hdd is missing from bios altogether, as if it is not connected. But, if I shut down, and power back up, it'll be start right back up without me even having to go into bios.

Do I have some bad hardware maybe? Or maybe some kind of malware getting into the RAM? Or is windows messed up?
 
See less See more
#3 ·
You could run chkdsk /r

Be advised that chkdsk /r can take a while to run. If there are errors, it can sometimes take hours to run, but you must let it run to completion - don't stop it or turn off the PC. So be prepared to be without your PC for some time.

Open an elevated Command Prompt (Run as administrator) and type (without the quotes) "chkdsk /r"

You'll be informed that it can't run and asked if you would like to run it on the next restart. Type "y" and then exit the Command window. Restart your PC.
 
#4 ·
You could run chkdsk /r

Be advised that chkdsk /r can take a while to run. If there are errors, it can sometimes take hours to run, but you must let it run to completion - don't stop it or turn off the PC. So be prepared to be without your PC for some time.

Open an elevated Command Prompt (Run as administrator) and type (without the quotes) "chkdsk /r"

You'll be informed that it can't run and asked if you would like to run it on the next restart. Type "y" and then exit the Command window. Restart your PC.
Thanks for the reply.

So I did what you said. Strange thing is the scan barely took long enough for me to notice. On the loading screen all that I saw was "Scanning and repairing Drive C: 100% complete" It was literally a minute between hitting the power button and seeing my desktop.

I also have run Western Digitals HD health program. Did both the short and long scans and passed both.

I'm not sure, but I THINK the problem I described usually happens when I'm recovering windows from sleep mode. Within minutes of recovery. It's possible that it has happened other times after waking up from sleep mode but it took so long that I forgot if it could have been related to it. Does that make sense?
 
#5 ·
So I did what you said. Strange thing is the scan barely took long enough for me to notice. On the loading screen all that I saw was "Scanning and repairing Drive C: 100% complete" It was literally a minute between hitting the power button and seeing my desktop.
Chkdsk /r cannot run that quickly, not even on a SSD. Did you see this screen?

Rectangle Font Display device Electronic device Multimedia


On that screen you should type (without the quotes) "y" and hit Enter. You should then exit the Command Prompt, and from there do a restart of the PC.
 
#6 ·
Tried again and it's now on 10% on the scan for about 10 minutes now.

What happened the first time: I saw the box you showed with all the same warnings. Typed y. Was told to restart. Hit restart and went to the bathroom. Came back nothing happened. I frequently have programs that wont let a shutdown happen, sometimes the os will stop trying to shutdown/restart and show the desktop back by itself.

Anyway I had to close iTunes and then decided to shutdown. I powered on again and that's when it showed 100% right away.

I'm hoping all that restart trouble might explain the quick chkdsk. Anyway it's scanning right this time... Hopefully...

I'll post when it's done.


Sent from my iPhone using Tapatalk
 
#7 ·
Ok so it's done. Looks like it managed to accomplish something. Any idea if it dealt with the problem? Here's the log file I managed to find all by myself with google.

Log Name: Application
Source: Microsoft-Windows-Wininit
Date: 3/6/2015 6:21:53 PM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: *****
Description:

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.

Stage 1: Examining basic file system structure ...
428032 file records processed.

File verification completed.
14541 large file records processed.

0 bad file records processed.

Stage 2: Examining file name linkage ...
547974 index entries processed.

Index verification completed.
CHKDSK is scanning unindexed files for reconnect to their original directory.
1 unindexed files scanned.

Recovering orphaned file IRON.DB-mj7FC97573 (187365) into directory file 101412.
0 unindexed files recovered.

Stage 3: Examining security descriptors ...
Cleaning up 409 unused index entries from index $SII of file 0x9.
Cleaning up 409 unused index entries from index $SDH of file 0x9.
Cleaning up 409 unused security descriptors.
Security descriptor verification completed.
59972 data files processed.

CHKDSK is verifying Usn Journal...
Usn Journal verification completed.

Stage 4: Looking for bad clusters in user file data ...
428016 files processed.

File data verification completed.

Stage 5: Looking for bad, free clusters ...
226721151 free clusters processed.

Free space verification is complete.
CHKDSK discovered free space marked as allocated in the volume bitmap.

Windows has made corrections to the file system.
No further action is required.

976401407 KB total disk space.
68758516 KB in 346374 files.
227416 KB in 59973 indexes.
0 KB in bad sectors.
530871 KB in use by the system.
65536 KB occupied by the log file.
906884604 KB available on disk.

4096 bytes in each allocation unit.
244100351 total allocation units on disk.
226721151 allocation units available on disk.

Internal Info:
00 88 06 00 4e 33 06 00 ab 21 0c 00 00 00 00 00 ....N3...!......
52 01 00 00 5d 00 00 00 00 00 00 00 00 00 00 00 R...]...........

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="2015-03-07T02:21:53.000000000Z" />
<EventRecordID>13992</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>X16</Computer>
<Security />
</System>
<EventData>

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.

Stage 1: Examining basic file system structure ...
428032 file records processed.

File verification completed.
14541 large file records processed.

0 bad file records processed.

Stage 2: Examining file name linkage ...
547974 index entries processed.

Index verification completed.
CHKDSK is scanning unindexed files for reconnect to their original directory.
1 unindexed files scanned.

Recovering orphaned file IRON.DB-mj7FC97573 (187365) into directory file 101412.
0 unindexed files recovered.

Stage 3: Examining security descriptors ...
Cleaning up 409 unused index entries from index $SII of file 0x9.
Cleaning up 409 unused index entries from index $SDH of file 0x9.
Cleaning up 409 unused security descriptors.
Security descriptor verification completed.
59972 data files processed.

CHKDSK is verifying Usn Journal...
Usn Journal verification completed.

Stage 4: Looking for bad clusters in user file data ...
428016 files processed.

File data verification completed.

Stage 5: Looking for bad, free clusters ...
226721151 free clusters processed.

Free space verification is complete.
CHKDSK discovered free space marked as allocated in the volume bitmap.

Windows has made corrections to the file system.
No further action is required.

976401407 KB total disk space.
68758516 KB in 346374 files.
227416 KB in 59973 indexes.
0 KB in bad sectors.
530871 KB in use by the system.
65536 KB occupied by the log file.
906884604 KB available on disk.

4096 bytes in each allocation unit.
244100351 total allocation units on disk.
226721151 allocation units available on disk.

Internal Info:
00 88 06 00 4e 33 06 00 ab 21 0c 00 00 00 00 00 ....N3...!......
52 01 00 00 5d 00 00 00 00 00 00 00 00 00 00 00 R...]...........

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

</EventData>
</Event>

Any idea what Iron-DB is?
 
#8 ·
Ok so it's done. Looks like it managed to accomplish something.

Any idea what Iron-DB is?
It's a file name of an orphaned file; other than that, I don't know of any significance in Windows, but it is mentioned in relation to Symantec.

How is your system performing now?
 
Status
Not open for further replies.
You have insufficient privileges to reply here.
Top