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

XP Boot Faliure


  • Please log in to reply
11 replies to this topic

#1 ben4205

ben4205

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Local time:09:49 AM

Posted 26 December 2009 - 11:40 AM

Hi,

Firstly, thanks for your time - i have used this site many times before to get solutions to my computing problems, and i guess it shows how good the site is that this is the first time i have had to make a post!

My latop is a Dell Vostro 1510 running XP Professional SP3. It has a 2.4GHz Intel Dual Core processor, 3GB of RAM and a GeForce 8400M video card

My problem is that every time i try to start up my laptop, it sits of the splash screen for ages, then gives me a blue screen of death with the following details:

SESSION3_INITIALIZATION_FAILED

STOP 0x000006F

I have tried loading it up several times normaly, several times with 'last good configuration' and several times in safe mode. The normal and last configuration modes both sat on the splash screen for ages before giving the above BSOD.

When i try to load up in safe mode, the screen fills with drivers it is loading then after 'avgrkx.sys' it says 'Press ESC to cancel loading SPTD.sys' whether i hit ESC or not it sits for ages doing nothing then restarts



I previously had another fault with this computer which i thought had fixed itself. It crashed whilst playing a video, and the next time i started up it ran CHKDSK and fixed some things (i can't really remember what it did, sorry for not being specific). When windows finally loaded it completely froze after about 1 min and i had to turn it off. Every subsequent boot followed the same course - CHKDSK would run and fix a few things (i don't think they were the same things each time, although i cannot be sure) then windows would load and freeze after around 1 min (it even froze a couple of times on the login page if i left it too long before entering my password), however i found that if i left it long enough frozen it gave a BSOD:

0x00000050: PAGE_FAULT_IN_NONPAGED_AREA

In the short space of time i had before each freeze i managed to uninstall a couple of programs i had installed shortly before the problems started (a free dvd burner and it's associated codecs) in the hope that this would fix the problems, but it didn't. I then looked up the STOP error in this site and followed the link from this page - http://aumha.org/a/stop.htm - to the microsoft kb site, where it suggested a method for removing a possible trojan. I did as it said and loaded up safe mode with command prompt, however none of the trojan files it said to remove/rename were present. I therefore restarted and CHKDSK ran as normal but unlike before it found no faults. Windows then loaded up fine and it appeared that everything was fixed, despite me not actually doing anything. It was about 2-3 days after thins that my current problems started.


Sorry for the long and rambling post, i have tried to post up everything i can remember about the various faults!

Thanks for any help,

Ben

BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 56,541 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:02:49 AM

Posted 26 December 2009 - 12:16 PM

Is the XP Recovery Console installed?

Have you tried to run the Dell Diagnostic module?

Louis

#3 ben4205

ben4205
  • Topic Starter

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Local time:09:49 AM

Posted 30 December 2009 - 08:52 AM

No the XP recovery module is not installed

When you say 'Dell Diagnostic module' do you mean the dignostic program you can run from BIOS wich tests the computer hardware? If so then yes, and everything passed, although i didn't run the full memory tests because it said that it had passed the basic tests and the full 30 min test was not required


Update - I just tried booting it again in the 'Last good configuration' option, and after a couple of minutes on the splash screen it started running CHKDSK which it has not manged to do so far (it was always giving a BSOD after a couple of minutes on the splash screen). Looks like CHKDSK didn't find anything wrong - and after the reboot it managed to load up windows properly. It still took about two minutes on the splash screen though. I used system restore to restore it to a point before all these problems started, but when it rebooted it stayed at the splash screen for ages and then gave the SESSION3_INITIALIZATION_FAILED STOP 0x000006F BSOD again.

Sorry for rambling a bit there, i was typing as it was happening!


Any thoughts?

Ben

Edited by ben4205, 30 December 2009 - 09:44 AM.


#4 hamluis

hamluis

    Moderator


  • Moderator
  • 56,541 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:02:49 AM

Posted 30 December 2009 - 11:24 AM

STOP 6F errors, see left column at http://www.aumha.org/a/stop.htm.

My guess would be a hard drive/file system problem and I would try to run the chkdsk /r command from the XP Recovery Console or the Dell Diagnostics module, if such is possible.

Louis

#5 ben4205

ben4205
  • Topic Starter

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Local time:09:49 AM

Posted 30 December 2009 - 11:32 AM

I managed to load up windows and i tried using system restore to revert to before this all started happening. It restarted but gave the STOP 6F error after ~3 mins at the splash screen. I restarted and it again sat at the splash screen for ~3 mins but this time ran CHKDSK then loaded windows normally. I have tried restoring 3 times now to different restore points with the exact same result.

However, i do seem to be able to load up windows now, albeit with a ridiculously long splash screen time and frequent freezes - is there anything more i can do to now that i can get into windows?

I was worried about the hard disk at first, but since CHKDSK has found no errors after the last ~10 crashes/blue screens does this not suggest that it is infact a software problem rather than a disk problem?

#6 hamluis

hamluis

    Moderator


  • Moderator
  • 56,541 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:02:49 AM

Posted 30 December 2009 - 11:40 AM

I guess this isnt' clear to me...did you run the chkdsk /r command, once you were able to boot into XP?

Louis

#7 ben4205

ben4205
  • Topic Starter

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Local time:09:49 AM

Posted 30 December 2009 - 01:26 PM

No i haven't done it in windows itself, i was reffering to the automatic scans windows was running due to incorrect shutting down. I will run chkdsk manually and get back to you

#8 hamluis

hamluis

    Moderator


  • Moderator
  • 56,541 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:02:49 AM

Posted 30 December 2009 - 01:34 PM

The chkdsk /r command results in a more complete repair/maintenance effort...than the 3-step automatic chkdsk triggered by detected problems.

Louis

#9 ben4205

ben4205
  • Topic Starter

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Local time:09:49 AM

Posted 31 December 2009 - 07:46 AM

OK i ran the chkdsk /r overnight last night and when i checked in the morning my computer had restarted and then hibernated. I started it up and it loaded up fine. Does chkdsk make a log? Is tehre any way to check if it found anything?

#10 hamluis

hamluis

    Moderator


  • Moderator
  • 56,541 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:02:49 AM

Posted 31 December 2009 - 12:57 PM

The results can be found in Event Viewer, Application tab...Winlogon will be listed as the Source.

Louis

#11 ben4205

ben4205
  • Topic Starter

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Local time:09:49 AM

Posted 31 December 2009 - 01:01 PM

OK, here's the 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 3 unused index entries from index $SII of file 0x9.
Cleaning up 3 unused index entries from index $SDH of file 0x9.
Cleaning up 3 unused security descriptors.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
Read failure with status 0xc0000185 at offset 0x273dea4000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x273deac000 for 0x1000 bytes.
Windows replaced bad clusters in file 23664
of name \PROGRA~1\CREATI~1\VideoFX\data\Disco.vfx.
Read failure with status 0xc0000185 at offset 0x273df42000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x273df4b000 for 0x1000 bytes.
Windows replaced bad clusters in file 23676
of name \PROGRA~1\CREATI~1\VideoFX\data\LONDON~1.VFX.
Read failure with status 0xc0000185 at offset 0x273de03000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x273de0c000 for 0x1000 bytes.
Windows replaced bad clusters in file 23915
of name \PROGRA~1\CREATI~1\VideoFX\data\STICKM~1.VFX.
Read failure with status 0xc0000185 at offset 0x2743bb8000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x2743bba000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x2743c4b000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x2743c59000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x2743cea000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x2743cf9000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x2743d8a000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x2743d98000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x2743e29000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x2743e37000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x2743ec8000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x2743ed6000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x2743f67000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x2743f75000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x27440c6000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x27440cb000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x274415c000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x274416a000 for 0x1000 bytes.
Windows replaced bad clusters in file 72130
of name \WINDOWS\system32\drivers\Avg\incavi.avm.
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
Free space verification is complete.
Adding 12 bad clusters to the Bad Clusters File.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.

312448184 KB total disk space.
309154968 KB in 269119 files.
114092 KB in 26347 indexes.
48 KB in bad sectors.
588348 KB in use by the system.
65536 KB occupied by the log file.
2590728 KB available on disk.

4096 bytes in each allocation unit.
78112046 total allocation units on disk.
647682 allocation units available on disk.

Internal Info:
c0 92 04 00 36 82 04 00 84 2c 07 00 00 00 00 00 ....6....,......
3e 7b 00 00 02 00 00 00 8e 02 00 00 00 00 00 00 >{..............
ac 4d 71 1c 00 00 00 00 c6 88 51 8b 01 00 00 00 .Mq.......Q.....
2e c9 ae 4a 00 00 00 00 b6 8a f6 d9 16 00 00 00 ...J............
18 df d8 6b 00 00 00 00 ec 84 cf 46 19 00 00 00 ...k.......F....
99 9e 36 00 00 00 00 00 98 38 07 00 3f 1b 04 00 ..6......8..?...
00 00 00 00 00 60 52 b5 49 00 00 00 eb 66 00 00 .....`R.I....f..

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.



Anything i should worry about?

#12 hamluis

hamluis

    Moderator


  • Moderator
  • 56,541 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:02:49 AM

Posted 31 December 2009 - 02:09 PM

Well...I normally don't read these reports after running chkdsk.

But the evidence of bad clusters is not a good one. I would probably run the hard drive's respective diagnostic on the drive, before putting my faith in it.

Long test, not short.

Louis




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users