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

Blue screen boot loop


  • Please log in to reply
10 replies to this topic

#1 Magdalena

Magdalena

  • Members
  • 51 posts
  • OFFLINE
  •  
  • Gender:Female
  • Local time:08:03 PM

Posted 07 January 2012 - 10:04 PM

Booted up my computer after shutting it down not even 30 minutes earlier and the computer made it all the way to the Windows Logo screen. Then it quickly shoots up a Blue screen and reboots completely. I haven't been able to get a code off of the BSOD because it flashes too quickly. Need to get this back up and running and not sure where to start.


Safe modes and Last known good configuration do not work. It still Blue screens and reboots.

Was attempting to get into the Windows XP disc and while loading it Blue Screened with
STOP: 0x0000006F.

Got Windows XP CD to work enough to make it to the Recovery Console and ran a chkdsk /p that found several errors. Exited Recovery Console and restarted from Hard drive. Attempted Safe mode with success. Wondering now if I should go about checking/repairing Registry?

Ok so I restarted again and the computer did a full boot up and seems to be running fine. I do not feel completely satisfied and fear there is still an issue that may come back up down the road. If anyone has any advise as to what I can do to check/repair/ etc please let me know.

Edited by Magdalena, 07 January 2012 - 10:58 PM.


BC AdBot (Login to Remove)

 


#2 AustrAlien

AustrAlien

    Inquisitor


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

Posted 08 January 2012 - 12:08 AM

Please download BlueScreenView (in zip file)
Extract (right-click > Extract all) the contents of bluescreenview.zip.
Double-click on the BlueScreenView.exe file, to run the program. (No installation is required.)
When scanning is done (usually complete by the time the interface appears), 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.
(Let us know if no information is reported in the BlueScreenView interface: This means that there are no minidumps saved in the default location.)
==================

Check Event Viewer to see if there was a log recorded after running chkdsk /p from the Recovery Console ...
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.

Edited by AustrAlien, 08 January 2012 - 12:12 AM.

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

Posted Image

#3 Magdalena

Magdalena
  • Topic Starter

  • Members
  • 51 posts
  • OFFLINE
  •  
  • Gender:Female
  • Local time:08:03 PM

Posted 08 January 2012 - 11:12 PM

==================================================
Dump File : Mini040911-01.dmp
Crash Time : 4/9/2011 8:21:44 PM
Bug Check String : THREAD_STUCK_IN_DEVICE_DRIVER
Bug Check Code : 0x000000ea
Parameter 1 : 0x88d5d598
Parameter 2 : 0x8947ef60
Parameter 3 : 0x8994bd20
Parameter 4 : 0x00000001
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+e3f9f
File Description : Multi-User Win32 Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2105)
Processor : 32-bit
Crash Address : nv4_disp.dll+65532
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini040911-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 98,203
==================================================

==================================================
Dump File : Mini101410-01.dmp
Crash Time : 10/14/2010 7:39:07 AM
Bug Check String : THREAD_STUCK_IN_DEVICE_DRIVER
Bug Check Code : 0x000000ea
Parameter 1 : 0x8712a020
Parameter 2 : 0x897e33f0
Parameter 3 : 0x897bd478
Parameter 4 : 0x00000001
Caused By Driver : nv4_disp.dll
Caused By Address : nv4_disp.dll+a254a
File Description : NVIDIA Windows XP Display driver, Version 280.26
Product Name : NVIDIA Windows XP Display driver, Version 280.26
Company : NVIDIA Corporation
File Version : 6.14.12.8026
Processor : 32-bit
Crash Address : nv4_disp.dll+a24f2
Stack Address 1 : nv4_disp.dll+f9bcf
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini101410-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 96,399
==================================================




Event Type: Information
Event Source: Winlogon
Event Category: None
Event ID: 1001
Date: 1/7/2012
Time: 8:46:21 PM
User: N/A
Computer: ANYAJ
Description:
Checking file system on \DosDevices\C:
The type of the file system is NTFS.

The volume is dirty.
Index entry A0128927.ini of index $I30 in file 0x2228 points to unused file 0x60b.
Deleting index entry A0128927.ini in index $I30 of file 8744.
The file reference 0x1fb00000000023f of index entry chrome_installer.log of index $I30
with parent 0x25a7 is not the same as 0x1f700000000023f.
Deleting index entry chrome_installer.log in index $I30 of file 9639.
The file reference 0x1fb00000000023f of index entry CHROME~1.LOG of index $I30
with parent 0x25a7 is not the same as 0x1f700000000023f.
Deleting index entry CHROME~1.LOG in index $I30 of file 9639.
The file reference 0x3b10000000005ff of index entry SETUP.EXE-2E62E515.pf of index $I30
with parent 0x2887 is not the same as 0x3ae0000000005ff.
Deleting index entry SETUP.EXE-2E62E515.pf in index $I30 of file 10375.
The file reference 0x3b10000000005ff of index entry SETUPE~3.PF of index $I30
with parent 0x2887 is not the same as 0x3ae0000000005ff.
Deleting index entry SETUPE~3.PF in index $I30 of file 10375.
Index entry tmp.edb of index $I30 in file 0x3586 points to unused file 0x624.
Deleting index entry tmp.edb in index $I30 of file 13702.
The file reference 0xa2b00000000054c of index entry chrome_shutdown_ms.txt of index $I30
with parent 0xcf43 is not the same as 0xa2900000000054c.
Deleting index entry chrome_shutdown_ms.txt in index $I30 of file 53059.
The file reference 0xa2b00000000054c of index entry CHROME~1.TXT of index $I30
with parent 0xcf43 is not the same as 0xa2900000000054c.
Deleting index entry CHROME~1.TXT in index $I30 of file 53059.
The file reference 0x2950000000003e5 of index entry Local State of index $I30
with parent 0xcf43 is not the same as 0x2930000000003e5.
Deleting index entry Local State in index $I30 of file 53059.
The file reference 0x2950000000003e5 of index entry LOCALS~1 of index $I30
with parent 0xcf43 is not the same as 0x2930000000003e5.
Deleting index entry LOCALS~1 in index $I30 of file 53059.
The file reference 0x13d0000000002ba of index entry Preferences of index $I30
with parent 0xcf46 is not the same as 0x13b0000000002ba.
Deleting index entry Preferences in index $I30 of file 53062.
The file reference 0x13d0000000002ba of index entry PREFER~1 of index $I30
with parent 0xcf46 is not the same as 0x13b0000000002ba.
Deleting index entry PREFER~1 in index $I30 of file 53062.
Index entry avgcchfi.dat of index $I30 in file 0x1cf47 points to unused file 0x70d.
Deleting index entry avgcchfi.dat in index $I30 of file 118599.
Index entry avgcchmi.dat of index $I30 in file 0x1cf47 points to unused file 0x6f1.
Deleting index entry avgcchmi.dat in index $I30 of file 118599.
Cleaning up minor inconsistencies on the drive.
CHKDSK is recovering lost files.
Recovering orphaned file WEBDAT~2 (575) into directory file 53062.
Recovering orphaned file Web Data-journal (575) into directory file 53062.
Recovering orphaned file ETILQS~4 (698) into directory file 9639.
Recovering orphaned file etilqs_zD15HxKSaOYI4uu (698) into directory file 9639.
Recovering orphaned file flaD1.tmp (997) into directory file 9639.
Recovering orphaned file CHROME~1.LOG (1356) into directory file 9639.
Recovering orphaned file chrome_installer.log (1356) into directory file 9639.
Recovering orphaned file LOCALS~1 (1535) into directory file 53059.
Recovering orphaned file Local State (1535) into directory file 53059.
Recovering orphaned file PREFER~1 (1816) into directory file 53062.
Recovering orphaned file Preferences (1816) into directory file 53062.
Recovering orphaned file ETILQS~3 (2587) into directory file 9639.
Recovering orphaned file etilqs_MsJE1Ghx8P8TtPA (2587) into directory file 9639.
Recovering orphaned file HI382F~1 (2636) into directory file 53062.
Recovering orphaned file History Index 2011-12-journal (2636) into directory file 53062.
Recovering orphaned file HISTOR~2 (2770) into directory file 53062.
Recovering orphaned file History-journal (2770) into directory file 53062.
Recovering orphaned file tmp.edb (14300) into directory file 3427.
Recovering orphaned file avgcchmi.dat (40811) into directory file 118599.
Recovering orphaned file avgcchfi.dat (40812) into directory file 118599.
Recovering orphaned file PERFLI~3.DAT (40832) into directory file 72.
Recovering orphaned file Perflib_Perfdata_4bc.dat (40832) into directory file 72.
Cleaning up 676 unused index entries from index $SII of file 0x9.
Cleaning up 676 unused index entries from index $SDH of file 0x9.
Cleaning up 676 unused security descriptors.
CHKDSK is verifying Usn Journal...
The USN Journal length 0x11678a400 in file 0x3ec7 is less the
largest USN encountered, 0x11678b1a0, plus eight in file 0x1d2a3.
Repairing Usn Journal $J data stream.
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.

312560608 KB total disk space.
180581896 KB in 106051 files.
40812 KB in 8524 indexes.
0 KB in bad sectors.
216164 KB in use by the system.
65536 KB occupied by the log file.
131721736 KB available on disk.

4096 bytes in each allocation unit.
78140152 total allocation units on disk.
32930434 allocation units available on disk.

Internal Info:
10 23 02 00 9b bf 01 00 f9 5b 02 00 00 00 00 00 .#.......[......
18 2f 00 00 00 00 00 00 f1 04 00 00 00 00 00 00 ./..............
86 68 d2 02 00 00 00 00 1a 70 93 6e 00 00 00 00 .h.......p.n....
3a 2d d7 02 00 00 00 00 00 00 00 00 00 00 00 00 :-..............
00 00 00 00 00 00 00 00 20 f6 91 75 00 00 00 00 ........ ..u....
99 9e 36 00 00 00 00 00 43 9e 01 00 00 00 00 00 ..6.....C.......
00 20 d8 0d 2b 00 00 00 4c 21 00 00 00 00 00 00 . ..+...L!......


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

#4 a_cup

a_cup

  • Members
  • 172 posts
  • OFFLINE
  •  
  • Gender:Female
  • Local time:09:03 PM

Posted 08 January 2012 - 11:22 PM

Hi Magdalena,

Caused By Driver : nv4_disp.dll
Caused By Address : nv4_disp.dll+a254a
File Description : NVIDIA Windows XP Display driver, Version 280.26
Product Name : NVIDIA Windows XP Display driver, Version 280.26
Company : NVIDIA Corporation


Check the following Microsoft KB
Error message in Windows XP: "STOP 0x000000EA THREAD_STUCK_IN_DEVICE_DRIVER"


Pauline

#5 AustrAlien

AustrAlien

    Inquisitor


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

Posted 08 January 2012 - 11:26 PM

Looking at the dates on the minidump files, the most recent was from September of 2011, so it appears that no minidumps were saved after the last episode of BSODs, and they are not going to be of any use in this instance.

Looking at the chkdsk log, there was significant corruption of the disk file system, corrected by running chkdsk /p. Let's firstly check that the hard drive itself is not causing the disk file system problem.

Test the hard drive. If you tell us the hard drive manufacturer's name (brand name) and model we can point you to the most appropriate diagnostic utility to use. It is best to use the hard drive manufacturer's own diagnostic utility, but Seagate's tool will work OK on most brands. The diagnostic tool is run from a bootable CD (Windows does not need to be working.The first two steps are done on a working computer, while the third step is to boot the ailing computer with the CD that you create in the first two steps.)

:step1: Please download SeaTools for DOS (CD) from Seagate's SeaTools for DOS web page

or use the following direct download link to download the latest version of SeaTools for DOS:
Download SeaTools for DOS ISO Image

The downloaded file name is SeaToolsDOS223ALL.ISO
[/list]
:step2: Burn the downloaded .ISO image to a CD using the appropriate burning software.
  • If you do not already have a suitable burning program for writing .ISO images to disc ...
    • Download and install ImgBurn.
      Ensure that you UN-check the box agreeing to install the Ask toolbar during the installation.
    • Place a new (blank) CD disc in the drive tray.
    • Choose Write image file to disc.
    • Under Source, click on the Browse button: Navigate to and select the .ISO file that you wish to burn.
    • Place a check-mark in the box beside Verify.
  • Click Posted Image

    When the CD has been burned and verified as successful, it will be bootable.

:step3: Boot from the CD.
  • (You may need to access the BIOS Setup Menu or the Boot Menu and change the boot order to enable booting from CD before hard drive.)
  • From Basic tests on the Main Menu, run the Short test and then the Long test.

    (The long test will take some considerable time to complete.)
    The results will be shown as either a PASS or FAIL.
    There is a chance that during the Long test, you may be offered the opportunity to attempt repairs on the hard drive:
  • If so, go ahead and attempt to do so, but ONLY after backing up all important personal files.
[/list]Note: You may wish to view the following ...
Please let us know the results of the tests.

When you can, include the make and model number of the problematic hard drive. If you do choose to use SeaTools, you will see the model number (and maybe the make) when SeaTools first detects the hard drive.

Edited by AustrAlien, 08 January 2012 - 11:30 PM.

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

Posted Image

#6 Magdalena

Magdalena
  • Topic Starter

  • Members
  • 51 posts
  • OFFLINE
  •  
  • Gender:Female
  • Local time:08:03 PM

Posted 10 January 2012 - 10:33 AM

Well my hard drive is a Western Digital and hopefully working just fine seeing as its less than a year old. Should I still use the Seagate tool or would you have a Western Digital you would prefer I use?

#7 AustrAlien

AustrAlien

    Inquisitor


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

Posted 10 January 2012 - 02:05 PM

The exact same tool is used for all Western Digital hard drives, so do not concern yourself about the reference to a different model in the following instructions ....

Check your system HDD with the HDD manufacturer's diagnostic utility ...

:step1: Go to the WD Caviar Black Downloads page and download Data Lifeguard Diagnostic for DOS (CD)
  • Unzip (right-click > Extract all) the file when you have downloaded it, to get to the .ISO image file.
    (Read the instructions while you are there.)

:step2: If you do not already have a suitable burning program for writing .ISO images to disc ...
  • Download and install ImgBurn.
    Ensure that you UN-check the box agreeing to install the Ask toolbar during the installation.
  • Place a new (blank) CD disc in the drive tray.
  • Choose Write image file to disc.
    • Under Source, click on the Browse button: Navigate to and select the .ISO file that you wish to burn.
    • Place a check-mark in the box beside Verify.
  • Click Posted Image

    When the CD has been burned and verified as successful, it will be bootable.

:step3: Boot from the CD.
  • (You may need to change the boot order to enable booting from CD before hard drive.)
  • Run the Short/Quick test and then the Long/Extended test].
    There is a chance that during the Long test, you may be offered the opportunity to attempt repairs on the hard drive:
    • If so, go ahead and attempt to do so, but ONLY after backing up all important personal files.
  • Please let us know the results of the tests.

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

Posted Image

#8 Magdalena

Magdalena
  • Topic Starter

  • Members
  • 51 posts
  • OFFLINE
  •  
  • Gender:Female
  • Local time:08:03 PM

Posted 10 January 2012 - 02:44 PM

Well I downloaded the file and extracted the iso image. I then burned the image to a cd using Nero6. I restarted my computer, boot from CD and after loading it said that no Disc was found and went to a command entry A:

I obviously did something incorrect but am at a lose as to what.

#9 AustrAlien

AustrAlien

    Inquisitor


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

Posted 10 January 2012 - 02:52 PM

I obviously did something incorrect ...

Perhaps not: I just tested what happens when booting the WD diagnostic CD without any hard drive attached to the system and ended up with the same result.

Please try starting the computer normally (don't forget to remove the CD). What happens?
AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#10 Magdalena

Magdalena
  • Topic Starter

  • Members
  • 51 posts
  • OFFLINE
  •  
  • Gender:Female
  • Local time:08:03 PM

Posted 10 January 2012 - 04:31 PM

It starts normally

#11 AustrAlien

AustrAlien

    Inquisitor


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

Posted 10 January 2012 - 04:37 PM

That's interesting. I'm not sure what is going on there.

Please try with the SeaTools bootable CD as in the earlier instructions.
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