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

BSOD UNMOUNTABLE_BOOT_VOLUME


  • Please log in to reply
12 replies to this topic

#1 Kelvin in Oregon

Kelvin in Oregon

  • Members
  • 49 posts
  • OFFLINE
  •  
  • Local time:08:11 PM

Posted 28 May 2011 - 05:34 PM

My wife's computer is getting the BSOD with the message UNMOUNTABLE_BOOT_VOLUME.

I get the BSOD regardless of whether I try to Start Windows Normally, use Last Known Good Configuration, or boon in Safe Mode.

The first two options get:
STOP 0x000000ED 0x8A5EA9E0, 0xC0000006, 0x00000000, 0x00000000

When I boot in Safe Mode, the first of the 4 values is 0x8A5CA368.

The computer is a Dell Vostro 200 with Windows XP. I tried Last Known Good Configuration at least 10 times, but I got the BSOD each time. The computer did not come with the Installation CDs.

What should I try next?

Thanks so much for your help!!!

Kelvin

BC AdBot (Login to Remove)

 


#2 Kelvin in Oregon

Kelvin in Oregon
  • Topic Starter

  • Members
  • 49 posts
  • OFFLINE
  •  
  • Local time:08:11 PM

Posted 28 May 2011 - 08:49 PM

I found instructions elsewhere to create a Recovery CD (using ARCDC from Artellos) and then run chkdsk /r. I did that and rebooted and the system came up normally.

Is there anything else I should do, or since it came up OK, can I presume (until proven otherwise) that the BSOD issue is resolved?

Thanks!

Kelvin

#3 AustrAlien

AustrAlien

    Inquisitor


  • Members
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:01:11 PM

Posted 28 May 2011 - 08:55 PM

Great! I was just working on a reply to your topic. Well done!

Let's run chkdsk again and have a look at the log that will be produced.

Use the Windows Error Checking utility (Check Disk), with the options to scan the disk surface for errors, and attempt recovery of data and repair the disk.
  • Open "My Computer"
  • Right-click on the drive that you wish to check > Properties > Tools > and in the "Error checking" section, click on "Check now".
  • Place a tick in both boxes > Start.
  • If the disk you have chosen is the system disk:
  • A message will notify you that a restart is necessary: Click OK, and close all windows.
  • Re-start the computer. The disk will be checked when the system boots.
    This test will take some time to run and at times may appear stalled but just let it run.
  • When the disk check is complete, the system will re-start automatically and load Windows.
A log of the disk check is recorded only if the scheduled re-start is used, and only for drives on the same HDD as the Operating System.
To open Event Viewer and view the log:
  • Go to Start > Run > and type eventvwr and press the <ENTER> key.
    The Event Viewer window will open.
  • In the left pane, 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 "Winlogon", with an entry corresponding to the date and time of the disk check.
  • Double-click on that entry to view the log.
  • Click on the Posted Image button to copy the log text to the clipboard.
  • Paste the log text into your next reply.

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

Posted Image

#4 Kelvin in Oregon

Kelvin in Oregon
  • Topic Starter

  • Members
  • 49 posts
  • OFFLINE
  •  
  • Local time:08:11 PM

Posted 29 May 2011 - 01:41 PM

Here is the chkdsk log:
Event Type: Information
Event Source: Winlogon
Event Category: None
Event ID: 1001
Date: 5/29/2011
Time: 10:58:19 AM
User: N/A
Computer: CAMILLE
Description:
Checking file system on C:
The type of the file system is NTFS.
Volume label is OS.

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.
Deleted corrupt attribute list entry
with type code 128 in file 28561.
Unable to locate attribute of type 0x80, lowest vcn 0x0,
instance tag 0x5 in file 0x6f91.
Deleted corrupt attribute list entry
with type code 128 in file 28561.
Unable to locate attribute of type 0x80, lowest vcn 0x0,
instance tag 0x4 in file 0x6f91.
Unable to locate attribute with instance tag 0x4 and segment
reference 0xb000000006f91. The expected attribute type is 0x80.
Deleting corrupt attribute record (128, 0B4227B4)
from file record segment 28561.
Unable to locate attribute with instance tag 0x5 and segment
reference 0xb000000006f91. The expected attribute type is 0x80.
Deleting corrupt attribute record (128, 5C321E34)
from file record segment 28561.
Cleaning up minor inconsistencies on the drive.
Cleaning up 7 unused index entries from index $SII of file 0x9.
Cleaning up 7 unused index entries from index $SDH of file 0x9.
Cleaning up 7 unused security descriptors.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
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.
Windows has made corrections to the file system.

156191962 KB total disk space.
80282260 KB in 102305 files.
51792 KB in 12249 indexes.
0 KB in bad sectors.
234798 KB in use by the system.
65536 KB occupied by the log file.
75623112 KB available on disk.

4096 bytes in each allocation unit.
39047990 total allocation units on disk.
18905778 allocation units available on disk.

Internal Info:
a0 ee 01 00 85 bf 01 00 36 99 02 00 00 00 00 00 ........6.......
e1 4e 00 00 04 00 00 00 06 03 00 00 00 00 00 00 .N..............
de ce d4 0a 00 00 00 00 3a d2 ef 6c 00 00 00 00 ........:..l....
ca e3 ba 0f 00 00 00 00 7e de 05 ca 05 00 00 00 ........~.......
dc 23 8a e5 03 00 00 00 b2 9f a9 40 0a 00 00 00 .#.........@....
c0 b7 cd 82 00 00 00 00 a0 39 08 00 a1 8f 01 00 .........9......
00 00 00 00 00 50 0a 24 13 00 00 00 d9 2f 00 00 .....P.$...../..

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


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

********************
BTW, I only did the chkdsk /r. Some of the other posts described doing a fixmbr or a fixboot. Since they weren't consistent (and since the restart went OK) I figured better safe than sorry. Let me know if I should do either/both of those steps, or anything else.

Thanks!!

Kelvin

Edited by Kelvin in Oregon, 29 May 2011 - 01:44 PM.


#5 AustrAlien

AustrAlien

    Inquisitor


  • Members
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:01:11 PM

Posted 29 May 2011 - 03:34 PM

Since your computer loaded Windows successfully after running chkdsk, there is no need for you to run fixmbr or fixboot.

You have run chkdsk /r twice so far and there are still a lot of errors showing up in the log that you posted. It is not uncommon to have to run chkdsk several times to fix errors when there are a lot of problems to fix. Let's run chkdsk again and have a look at the log after you have done that and see how things are looking then.

There is no need to use the /R switch again, so we will run chkdsk /f, which will complete a lot quicker.

Use the Windows Error checking utility (Check Disk), with the option to "Automatically fix file system errors".
  • Open "My Computer"
  • Right-click on the drive that you wish to check > Properties > Tools > and in the "Error checking" section, click on "Check now".
  • Place a tick in the upper box ONLY (beside "Automatically fix file system errors") > Start.
  • If the disk you have chosen is the system disk:
  • A message will notify you that a restart is necessary: Click OK, and close all windows.
  • Re-start the computer. The disk will be checked when the system boots.
    This test will take some time to run and at times may appear stalled but just let it run.
  • When the disk check is complete, the system will re-start automatically and load Windows.
Please post the log in your next reply.
AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#6 Kelvin in Oregon

Kelvin in Oregon
  • Topic Starter

  • Members
  • 49 posts
  • OFFLINE
  •  
  • Local time:08:11 PM

Posted 29 May 2011 - 11:10 PM

Here is the chkdsk log:

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


A disk check has been scheduled.
Windows will now check the disk.
Cleaning up minor inconsistencies on the drive.
Cleaning up 8 unused index entries from index $SII of file 0x9.
Cleaning up 8 unused index entries from index $SDH of file 0x9.
Cleaning up 8 unused security descriptors.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.

156191962 KB total disk space.
80720600 KB in 106171 files.
53136 KB in 12264 indexes.
0 KB in bad sectors.
235826 KB in use by the system.
65536 KB occupied by the log file.
75182400 KB available on disk.

4096 bytes in each allocation unit.
39047990 total allocation units on disk.
18795600 allocation units available on disk.

Internal Info:
a0 ee 01 00 ae ce 01 00 86 b7 02 00 00 00 00 00 ................
d4 4e 00 00 04 00 00 00 05 03 00 00 00 00 00 00 .N..............
76 45 cb 0a 00 00 00 00 3e f4 64 72 00 00 00 00 vE......>.dr....
5c e2 d9 0f 00 00 00 00 00 00 00 00 00 00 00 00 \...............
00 00 00 00 00 00 00 00 fa ad 5c 96 00 00 00 00 ..........\.....
d0 de cd 82 00 00 00 00 90 38 08 00 bb 9e 01 00 .........8......
00 00 00 00 00 60 cb 3e 13 00 00 00 e8 2f 00 00 .....`.>...../..

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

Thanks again for your help!

Kelvin

#7 AustrAlien

AustrAlien

    Inquisitor


  • Members
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:01:11 PM

Posted 02 June 2011 - 01:10 AM

Cleaning up minor inconsistencies on the drive.
Cleaning up 8 unused index entries from index $SII of file 0x9.
Cleaning up 8 unused index entries from index $SDH of file 0x9.
Cleaning up 8 unused security descriptors.

There is likely to be just a small number of errors remaining. Run chkdsk /f again (same as last time) and you should be right to go.

How's everything running now?

Sorry about the delay. I only just noticed that I hadn't replied to your last post. My apologies.

Edited by AustrAlien, 02 June 2011 - 01:15 AM.

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

Posted Image

#8 Kelvin in Oregon

Kelvin in Oregon
  • Topic Starter

  • Members
  • 49 posts
  • OFFLINE
  •  
  • Local time:08:11 PM

Posted 04 June 2011 - 11:53 AM

Since my last post we got one more BSOD, but with different codes (STOP 0x0000008E ...). It restarted fine and hasn't recurred. Let me know if you want me to post those codes. My wife also had one other failure where a report was sent to MS. I have the Error signature but no other information. I can post that as well, if it would be helpful.

The chkdsk results were:
Event Type: Information
Event Source: Winlogon
Event Category: None
Event ID: 1001
Date: 6/3/2011
Time: 4:31:13 PM
User: N/A
Computer: CAMILLE
Description:
Checking file system on C:
The type of the file system is NTFS.
Volume label is OS.


A disk check has been scheduled.
Windows will now check the disk.
Cleaning up minor inconsistencies on the drive.
Cleaning up 26 unused index entries from index $SII of file 0x9.
Cleaning up 26 unused index entries from index $SDH of file 0x9.
Cleaning up 26 unused security descriptors.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.

156191962 KB total disk space.
79120280 KB in 102816 files.
53652 KB in 12051 indexes.
0 KB in bad sectors.
234298 KB in use by the system.
65536 KB occupied by the log file.
76783732 KB available on disk.

4096 bytes in each allocation unit.
39047990 total allocation units on disk.
19195933 allocation units available on disk.

Internal Info:
a0 ee 01 00 be c0 01 00 f1 9b 02 00 00 00 00 00 ................
7c 4d 00 00 04 00 00 00 1f 03 00 00 00 00 00 00 |M..............
30 82 a7 0a 00 00 00 00 50 d5 57 6e 00 00 00 00 0.......P.Wn....
64 91 09 10 00 00 00 00 00 00 00 00 00 00 00 00 d...............
00 00 00 00 00 00 00 00 52 52 73 92 00 00 00 00 ........RRs.....
e0 05 ce 82 00 00 00 00 a0 39 08 00 a0 91 01 00 .........9......
00 00 00 00 00 60 1e dd 12 00 00 00 13 2f 00 00 .....`......./..

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

Thanks!

#9 AustrAlien

AustrAlien

    Inquisitor


  • Members
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:01:11 PM

Posted 04 June 2011 - 05:02 PM

Let's see if we can get any useful info about what is going on ...

Please download BlueScreenView (in zip file)
Extract the contents of bluescreenview.zip and then double-click on the BlueScreenView.exe file, and click on Run, to run the program. (No installation is required.)
When scanning is done (please be patient), go ...
  • Edit > Select All
  • File > Save Selected Items, and save the report to your Desktop as BSOD.txt.
Close the BlueScreenView window.
Open BSOD.txt using Notepad and go ...
  • Edit > Select All
  • Edit > Copy, and then paste the entire contents of the text file into your next reply.

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

Posted Image

#10 Kelvin in Oregon

Kelvin in Oregon
  • Topic Starter

  • Members
  • 49 posts
  • OFFLINE
  •  
  • Local time:08:11 PM

Posted 06 June 2011 - 01:27 AM

I'm not sure I did this right. Your instructions said "When scanning is done (please be patient)..." When I ran BlueScreenView, it immediately came up with a screen. I waited a little bit, but the screen didn't seem to be changing, so I followed the rest of the instructions.

Here is the contents of BSOD.txt:
==================================================
Dump File : Mini053111-01.dmp
Crash Time : 5/31/2011 10:55:40 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0xba279bb1
Parameter 3 : 0xa702eb88
Parameter 4 : 0x00000000
Caused By Driver : sbhips.sys
Caused By Address : sbhips.sys+2292
File Description : Sunbelt Personal Firewall Host Intrusion Prevention Driver
Product Name : Sunbelt Personal Firewall
Company : Sunbelt Software, Inc.
File Version : 4.6.1827.0
Processor : 32-bit
Crash Address : sbhips.sys+1bb1
Stack Address 1 : sbhips.sys+2292
Stack Address 2 : ntkrnlpa.exe+6a67c
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini053111-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 65,536
==================================================

==================================================
Dump File : Mini052011-01.dmp
Crash Time : 5/20/2011 12:15:16 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x00000000
Parameter 3 : 0xa72efaa0
Parameter 4 : 0x00000000
Caused By Driver : SbFw.sys
Caused By Address : SbFw.sys+13332
File Description : Sunbelt Personal Firewall driver
Product Name : Sunbelt Personal Firewall
Company : Sunbelt Software, Inc.
File Version : 4.6.1860.0
Processor : 32-bit
Crash Address :
Stack Address 1 : SbFw.sys+1291c
Stack Address 2 : SbFw.sys+1335b
Stack Address 3 : avgtdix.sys+5b95
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini052011-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 65,536
==================================================

If I missed a step that was supposed to scan something, please let know what I need to do to start that scan, then I will repeat the rest of the steps.

FYI, no more BSOD's/other errors since my last post.

Thanks so much!

Kelvin

Edited by Kelvin in Oregon, 06 June 2011 - 01:29 AM.


#11 AustrAlien

AustrAlien

    Inquisitor


  • Members
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:01:11 PM

Posted 06 June 2011 - 01:41 AM

You did well.

There are only two BSOD events recorded, one on 31st May, the other on 20th May, and both due to Sunbelt Personal Firewall drivers it seems.

If you keep experiencing BSODs and they are all due to Sunbelt Personal Firewall drivers, then you will need to investigate further: Either remove Sunbelt and install a fresh copy or try some other Firewall software.

When your computer experiences a fatal system error (BSOD), does it stop and allow you to record the error message displayed on the BSOD screen or does it automatically restart again (possibly too quickly for you to record the error details)?
AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#12 Kelvin in Oregon

Kelvin in Oregon
  • Topic Starter

  • Members
  • 49 posts
  • OFFLINE
  •  
  • Local time:08:11 PM

Posted 06 June 2011 - 10:11 AM

The computer does stop when it gets a BSOD, so I am able to record the stop codes, etc.

I presume the way to determine if a BSOD was caused by Sunbelt Firewall is to run BlueScreenViewer and check the Product Name.

Thanks!

#13 AustrAlien

AustrAlien

    Inquisitor


  • Members
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:01:11 PM

Posted 06 June 2011 - 11:17 AM

The computer does stop when it gets a BSOD, so I am able to record the stop codes, etc.

Good.

Yes, using bluescreenview is a good way to check out the logs. It is also possible that you might see the name of the file (driver) involved on the BSOD message screen itself, under Technical Information, as in the example below (ati3diag.dll):

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

Posted Image




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users