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

Shutdown after chkdsk


  • Please log in to reply
170 replies to this topic

#1 jackiemarie

jackiemarie

  • Members
  • 417 posts
  • OFFLINE
  •  
  • Gender:Female
  • Local time:10:01 AM

Posted 14 June 2011 - 02:46 PM

After a chkdsk scan, the screen disappeared too quickly for me to read it. Then a BS flashed up briefly which I didn't have time to read it, something like "a problem has been detected"; the laptop tried to cycle into the chkdsk again; I stopped it. The system froze, and I shut down at the power button. A few minutes later I started up again. Below is the info from event viewer and the info from the link to the Help Center (same also attached).

Please tell me 1) how to access the info from the chkdsk scan and 2) how to access the info referred to as "sc query"-I'm unaware of the correct service name. Service control manager or scm do not work. I am not aware of any device that is not functioning.

Event viewer:
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7023
Date: 6/14/2011
Time: 11:26:04 AM
User: N/A
Computer: CHARMING
Description:
The Windows Driver Foundation - User-mode Driver Framework service terminated with the following error:
A device attached to the system is not functioning.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
===============================================================================================
Info at Help Center:
Details
Product: Windows Operating System
ID: 7023
Source: Service Control Manager
Version: 5.2
Symbolic Name: EVENT_SERVICE_EXIT_FAILED
Message: The %1 service terminated with the following error:
%2

Explanation
The specified service stopped unexpectedly with the error indicated in the message. The service closed safely.

User Action
To troubleshoot the error:

Review the error information displayed in the message.
To display the WIN32_EXIT_CODE error that SCM encountered, at the command prompt, type
sc query service name
The information displayed can help you troubleshoot possible causes for the error.
===============================================================================
Thank you.

EAM, Malware Bytes Premium

HP g7- Windows 7 Home Prem 64-bit - Intel i3 - 6 GB Ram

What you value is your reward.


BC AdBot (Login to Remove)

 


#2 Allan

Allan

  • BC Advisor
  • 8,614 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:10:01 AM

Posted 14 June 2011 - 02:54 PM

Boot to the recovery console and run chkdsk /r

Checkdisk will not reboot after it completes when from the recovery console and you will be able to see all messages. It's also the best way to run checkdisk witn XP

#3 jackiemarie

jackiemarie
  • Topic Starter

  • Members
  • 417 posts
  • OFFLINE
  •  
  • Gender:Female
  • Local time:10:01 AM

Posted 14 June 2011 - 03:09 PM

Boot to the recovery console and run chkdsk /r

Checkdisk will not reboot after it completes when from the recovery console and you will be able to see all messages. It's also the best way to run checkdisk witn XP


I don't know what Recovery Console is or how to boot to it--I don't have original installation disks. This laptop is 5 years old. There's got to be command line for finding these results, isn't there?

EAM, Malware Bytes Premium

HP g7- Windows 7 Home Prem 64-bit - Intel i3 - 6 GB Ram

What you value is your reward.


#4 Allan

Allan

  • BC Advisor
  • 8,614 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:10:01 AM

Posted 14 June 2011 - 03:16 PM

http://www.cpucare.com/how-to-faqs/OS/XP/Viewing%20ChkDSk%20Results.htm

You did run chkdsk /r, correct?

#5 jackiemarie

jackiemarie
  • Topic Starter

  • Members
  • 417 posts
  • OFFLINE
  •  
  • Gender:Female
  • Local time:10:01 AM

Posted 14 June 2011 - 03:36 PM

I did the chkdsk this way: My Computer>Local disk C:>right click Properties>Tools>Error checking> check automatically fix & check for bad sectors>restart computer--scan started automatically, took 1.5 hours.

Mod Edit: Checking both options is the same as the chkdsk /r command ~ Hamluis.

Edited by hamluis, 14 June 2011 - 04:06 PM.

EAM, Malware Bytes Premium

HP g7- Windows 7 Home Prem 64-bit - Intel i3 - 6 GB Ram

What you value is your reward.


#6 Allan

Allan

  • BC Advisor
  • 8,614 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:10:01 AM

Posted 14 June 2011 - 03:39 PM

That runs chkdsk /f, not chkdsk /r.

If you can't get to the recovery console open an elevated command prompt (right click on a command prompt and "run as administrator"). Then type chkdsk /r and press ENTER

You'll get a message saying the drive is in use and asking if you want to run checkdisk on the next boot. Say yes, exit the command prompt (type "exit" and press ENTER) then reboot.

Edited by Allan, 14 June 2011 - 03:40 PM.


#7 jackiemarie

jackiemarie
  • Topic Starter

  • Members
  • 417 posts
  • OFFLINE
  •  
  • Gender:Female
  • Local time:10:01 AM

Posted 14 June 2011 - 04:57 PM

Thank you, Allan; I went to Event Viewer, clicked on Source and saw the WinLogon entries; not too sure I understand it. But how do I do the user action suggested below, specifically, what are the words I type in after "sc query" in order to view the error message? Below words have been excerpted from the Windows Driver Foundation shutdown after chkdsk finished.
User Action
To troubleshoot the error:

Review the error information displayed in the message.
To display the WIN32_EXIT_CODE error that SCM encountered, at the command prompt, type
sc query service name
The information displayed can help you troubleshoot possible causes for the error.

EAM, Malware Bytes Premium

HP g7- Windows 7 Home Prem 64-bit - Intel i3 - 6 GB Ram

What you value is your reward.


#8 Allan

Allan

  • BC Advisor
  • 8,614 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:10:01 AM

Posted 14 June 2011 - 05:02 PM

If a specific service is mentioned in the error, that's what you enter (the name of the service). But trust me, the information you get back will most likely be even more confusing. None of this has anything to do with checkdisk though, does it?

I just re-read your first post and you said a "bs flashed up". I just realized you are talking about a blue screen error. PLEASE do not make up abbreviations in these threads - nobody but you will know what you are talking about and you will delay our ability to help you.


Download BlueScreenView:
http://www.nirsoft.net/utils/blue_screen_view.html
unzip downloaded file and double click on BlueScreenView.exe to run the program.
when scanning is done, go to EDIT - Select All
Go to FILE - SAVE Selected Items, and save the report as BSOD.txt
Open BSOD.txt in Notepad, copy all of the content, and paste it into your next reply

Edited by Allan, 14 June 2011 - 05:05 PM.


#9 jackiemarie

jackiemarie
  • Topic Starter

  • Members
  • 417 posts
  • OFFLINE
  •  
  • Gender:Female
  • Local time:10:01 AM

Posted 14 June 2011 - 05:39 PM

My apologies, I should have identified myself as a clueless older user.

It seems that the blue screen that appeared this morning immediately after the chkdsk had run was not a BSOD, but I'll wait for you to tell me.
==================================================
Dump File : Mini061111-01.dmp
Crash Time : 6/11/2011 10:53:07 PM
Bug Check String : BAD_POOL_HEADER
Bug Check Code : 0x00000019
Parameter 1 : 0x00000020
Parameter 2 : 0x8879d3b0
Parameter 3 : 0x8879d488
Parameter 4 : 0x0a1b0023
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+22f43
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.6055 (xpsp_sp3_gdr.101209-1647)
Processor : 32-bit
Crash Address : ntkrnlpa.exe+22f43
Stack Address 1 : ntkrnlpa.exe+74583
Stack Address 2 : ntkrnlpa.exe+e4ca1
Stack Address 3 : ntkrnlpa.exe+9f057
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini061111-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 65,536
==================================================

==================================================
Dump File : Mini060911-01.dmp
Crash Time : 6/9/2011 2:05:28 PM
Bug Check String : DRIVER_CORRUPTED_EXPOOL
Bug Check Code : 0x000000c5
Parameter 1 : 0x00000004
Parameter 2 : 0x00000002
Parameter 3 : 0x00000001
Parameter 4 : 0x8054b10f
Caused By Driver : aswTdi.SYS
Caused By Address : aswTdi.SYS+4102
File Description : avast! TDI Filter Driver
Product Name : avast! Antivirus System
Company : AVAST Software
File Version : 6.0.1125.0 built by: WinDDK
Processor : 32-bit
Crash Address : ntkrnlpa.exe+6d758
Stack Address 1 : ntkrnlpa.exe+7410f
Stack Address 2 : ntkrnlpa.exe+7475f
Stack Address 3 : ntkrnlpa.exe+ea0a3
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini060911-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 65,536
==================================================

==================================================
Dump File : Mini052211-01.dmp
Crash Time : 5/22/2011 9:37:14 AM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x10000050
Parameter 1 : 0xf52c0002
Parameter 2 : 0x00000000
Parameter 3 : 0x8054b51a
Parameter 4 : 0x00000000
Caused By Driver : hal.dll
Caused By Address : hal.dll+2aa8
File Description : Hardware Abstraction Layer DLL
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2111)
Processor : 32-bit
Crash Address : ntoskrnl.exe+7451a
Stack Address 1 : ntoskrnl.exe+33952
Stack Address 2 : ntoskrnl.exe+350f9
Stack Address 3 : ntoskrnl.exe+f8fa8
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini052211-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 90,112
==================================================

==================================================
Dump File : Mini032811-01.dmp
Crash Time : 3/28/2011 10:45:07 PM
Bug Check String : DRIVER_CORRUPTED_EXPOOL
Bug Check Code : 0x100000c5
Parameter 1 : 0x996e524c
Parameter 2 : 0x00000002
Parameter 3 : 0x00000001
Parameter 4 : 0x8054bfd2
Caused By Driver : Ntfs.sys
Caused By Address : Ntfs.sys+2b4ad
File Description : NT File System Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2111)
Processor : 32-bit
Crash Address : ntoskrnl.exe+74fd2
Stack Address 1 : ntoskrnl.exe+b303
Stack Address 2 : ntoskrnl.exe+bb1f
Stack Address 3 : ntoskrnl.exe+c7f1
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini032811-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 90,112
==================================================

==================================================
Dump File : Mini032311-01.dmp
Crash Time : 3/23/2011 10:21:40 AM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x1000000a
Parameter 1 : 0x00000045
Parameter 2 : 0x0000001c
Parameter 3 : 0x00000000
Parameter 4 : 0x80502367
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+2b367
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.6055 (xpsp_sp3_gdr.101209-1647)
Processor : 32-bit
Crash Address : ntoskrnl.exe+2b367
Stack Address 1 : ntoskrnl.exe+2b45b
Stack Address 2 : ntoskrnl.exe+24017
Stack Address 3 : ntoskrnl.exe+e9794
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini032311-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 90,112
==================================================

==================================================
Dump File : Mini032111-01.dmp
Crash Time : 3/21/2011 11:09:55 AM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x1000000a
Parameter 1 : 0xef459db8
Parameter 2 : 0x00000002
Parameter 3 : 0x00000000
Parameter 4 : 0x8050aa3e
Caused By Driver : hal.dll
Caused By Address : hal.dll+2aa8
File Description : Hardware Abstraction Layer DLL
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2111)
Processor : 32-bit
Crash Address : ntoskrnl.exe+33a3e
Stack Address 1 : ntoskrnl.exe+350f9
Stack Address 2 : ntoskrnl.exe+f8fa8
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini032111-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 90,112
==================================================

==================================================
Dump File : Mini030411-01.dmp
Crash Time : 3/4/2011 11:13:01 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x805bc7e7
Parameter 3 : 0xa9c5cc18
Parameter 4 : 0x00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+e57e7
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.6055 (xpsp_sp3_gdr.101209-1647)
Processor : 32-bit
Crash Address : ntoskrnl.exe+e57e7
Stack Address 1 : ntoskrnl.exe+e5a03
Stack Address 2 : ntoskrnl.exe+e5377
Stack Address 3 : ntoskrnl.exe+e5415
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini030411-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 90,112
==================================================

==================================================
Dump File : Mini022611-01.dmp
Crash Time : 2/26/2011 6:11:02 PM
Bug Check String : DRIVER_CORRUPTED_EXPOOL
Bug Check Code : 0x100000c5
Parameter 1 : 0x00000004
Parameter 2 : 0x00000002
Parameter 3 : 0x00000001
Parameter 4 : 0x8054bfd2
Caused By Driver : aswSP.SYS
Caused By Address : aswSP.SYS+1f72c
File Description : avast! self protection module
Product Name : avast! Antivirus System
Company : AVAST Software
File Version : 6.0.1125.0
Processor : 32-bit
Crash Address : ntoskrnl.exe+74fd2
Stack Address 1 : aswSP.SYS+1f431
Stack Address 2 : aswSP.SYS+1ff38
Stack Address 3 : aswSP.SYS+1e0ce
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini022611-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 90,112
==================================================




EAM, Malware Bytes Premium

HP g7- Windows 7 Home Prem 64-bit - Intel i3 - 6 GB Ram

What you value is your reward.


#10 Allan

Allan

  • BC Advisor
  • 8,614 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:10:01 AM

Posted 14 June 2011 - 05:44 PM

Uninstall AVAST with the Avast uninstall utility (http://www.avast.com/uninstall-utility). Then either reinstall the latest version of Avast or install another anti virus application. Do not run the system for any period of time without an anti virus app installed.

Then let's check the ram:

To check the ram, download memtest (http://www.memtest.org/). Burn it to a cd using a dedicated .iso burning utility (http://www.petri.co.il/how_to_write_iso_files_to_cd.htm), make sure the cd drive is at the top of the boot order in bios, then boot to the newly created cd and run the utility.

#11 jackiemarie

jackiemarie
  • Topic Starter

  • Members
  • 417 posts
  • OFFLINE
  •  
  • Gender:Female
  • Local time:10:01 AM

Posted 14 June 2011 - 05:58 PM

All I can plead is vast ignorance. I don't trust myself to do what you've written. Using the Sonic Digital MediaPlus v7 on this laptop causes shutdown errors at mediahub.exe, and I do know about bios.
The avast is the paid avast! Internet Security Suite with a key, but I could probably do that.

Would it do any good to go to HP Help Center and check the ram through one of their programs?


EAM, Malware Bytes Premium

HP g7- Windows 7 Home Prem 64-bit - Intel i3 - 6 GB Ram

What you value is your reward.


#12 jackiemarie

jackiemarie
  • Topic Starter

  • Members
  • 417 posts
  • OFFLINE
  •  
  • Gender:Female
  • Local time:10:01 AM

Posted 14 June 2011 - 06:00 PM

Corrected: do NOT know about bios.

EAM, Malware Bytes Premium

HP g7- Windows 7 Home Prem 64-bit - Intel i3 - 6 GB Ram

What you value is your reward.


#13 AustrAlien

AustrAlien

    Inquisitor


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

Posted 14 June 2011 - 09:00 PM

Perhaps I might be able to help out a little here? Let's start by investigating the most important issue, and proceed one step at a time.

Here are some instructions for running "chkdsk /r" using the Windows Error Checking dialog with which you are familiar.

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.

Please copy and paste the content of the most recent log produced by using the above instructions, into your next reply, along with the previous recent logs, so that we can get an understanding of what is going on.

Thank you.

Edited by AustrAlien, 14 June 2011 - 09:05 PM.

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

Posted Image

#14 jackiemarie

jackiemarie
  • Topic Starter

  • Members
  • 417 posts
  • OFFLINE
  •  
  • Gender:Female
  • Local time:10:01 AM

Posted 14 June 2011 - 10:19 PM

Thank you for offer to assist. It is too late here to do another 90 minute check disk scan, but pasted below is the event viewer info from the earlier chkdsk I did today. I was concerned that the computer did not restart after chkdsk finished; instead a dark screen flashed up; I only had enough time to read a few words (something like "a problem has been detected"). Then the computer froze and I had to shut it down with the power button.

Event Type: Information
Event Source: Winlogon
Event Category: None
Event ID: 1001
Date: 6/14/2011
Time: 11:24:52 AM
User: N/A
Computer: CHARMING
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.
Cleaning up minor inconsistencies on the drive.
Cleaning up 564 unused index entries from index $SII of file 0x9.
Cleaning up 564 unused index entries from index $SDH of file 0x9.
Cleaning up 564 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.

103908388 KB total disk space.
32254028 KB in 70316 files.
62632 KB in 8437 indexes.
0 KB in bad sectors.
383940 KB in use by the system.
65536 KB occupied by the log file.
71207788 KB available on disk.

4096 bytes in each allocation unit.
25977097 total allocation units on disk.
17801947 allocation units available on disk.

Internal Info:
b0 b6 01 00 ac 33 01 00 c6 96 01 00 00 00 00 00 .....3..........
24 d3 00 00 03 00 00 00 b9 0a 00 00 00 00 00 00 $...............
80 fe 21 0a 00 00 00 00 b8 5b a5 82 00 00 00 00 ..!......[......
d4 71 17 66 00 00 00 00 c2 92 e2 55 04 00 00 00 .q.f.......U....
08 38 ae 20 05 00 00 00 44 5a 3c 75 0a 00 00 00 .8. ....DZ<u....
99 9e 36 00 00 00 00 00 a8 39 07 00 ac 12 01 00 ..6......9......
00 00 00 00 00 30 a1 b0 07 00 00 00 f5 20 00 00 .....0....... ..

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.

EAM, Malware Bytes Premium

HP g7- Windows 7 Home Prem 64-bit - Intel i3 - 6 GB Ram

What you value is your reward.


#15 AustrAlien

AustrAlien

    Inquisitor


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

Posted 15 June 2011 - 12:30 AM

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

Thank you. Please use Windows Error Checking (Check Disk) as instructed above and post the log when you get a chance. We'll make sure you have the number of those "Cleaning up .... " entries reduced to a minimum. Sometimes it is necessary to run Check Disk a number of times to repair multiple errors in the disk file system.
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