BSOD on startup

Sherm

Sherm

Sherm

Associate
Joined
4 Jun 2003
Posts
903
Location
UK, Dorset
Right, machine was running fine, came back to use it and it had blue screened with 0x0000000A. I have looked this up and as normal it says it's drivers or hardware, which to be honest does not help much does it.

Right, tried starting in safe mode, just eventually blue screens, just takes longer:p. By trying to start with last know config, it either just gets caught in a loop and the little blue bar just keeps going across the bottom, or which suggests what i think it could be, comes up with an NTFS.sys blue screen. This screen says stuff like datastamp at (load of numbers) and asked me to run chkdsk.

Been a while how do i run chkdsk before windows trys starting up? But really sounds like my hard disk is buggered yeah?...

This has all just happened and now sat here thinking bugger, only windows on that drive, but pretty sure my Bioshock saves prob went to the docs folder as they do !! argh !

Anyway any thoughts would be cool!
 
Ok, just trying to repair from cd and seems to freeze doing that aswell !

this is not going well !
 
You can run chkdsk by booting off a bootable disk and running it via dos. Also, it might be worth testing the hdd too, you should be able to make a boot disk via the hdd manufacturers website and run a test that way.
 
If i try and start windows normally it wil get as far the the windows logo and blue moving bar. Trying to start with either last kow or safe mode either freezes or bs's.

Getting this ntfs.sys 0x24 message a lot now. Think my drive is dead, Reckon the info is salvagable as a slave?, only need a few save games, possibly a few emails etc.
 
When you say abot a bootable disk, think the only one that i have is the one that i used for the raid drivers back when i built the machine. Will this disk be ok to boot from?
 
Hi. Before doing anything else with that drive I'd switch it to a slave role and get the data off it. If you have anything you want to keep get it off the drive right now!

After that: Visit the manufacturer's website and search their support section for their diagnostic tools. http://www.ultimatebootcd.com/ should work too. Run the short then long test - if the drive's faulty it's best to find out now rather than waste a lot of effort trying to reinstall windows on it.

If you can't access the data on the drive, the most effective program I've personally used in this situation is Spinrite - google it. It will cost you about forty quid but it's a pretty badass HDD data recovery app, plus it's downloadable so you don't need to wait for it to arrive.
 
Just tried installing with it as a slave, machine blue screens with the same msg even though its not the boot drive. I guess the file structure is checked for integrity on startup.

I hae ordered a new drive from OcUk anyway, so that should be here tomorrow. All the same i would like to be able to get some files off. Not the end of the world, but more of a real pain in the ass.

So, any tricks to be able to get this to boot in slave?
 
Been looking into this Spinrite, looks pretty good. Whats the chances of this being able to fix the ntfs.sys problem?

Will be re-installing windows on the new drive coming tomorrow, but would like to be able to get a few files off the other drive. If Spinrite will be able to fix the drive then i will get a copy, just don't want to spend another £40 to find it does not work.

Any other view on this?
 
This is pro b a long shot and doubt it will work for you, but when I first built this current PC I was getting BSODs at the exact same time as you everytime I booted. All my hardware was new and I thought it was my HDD, but I tried installing on another HDD and got the same.

So I removed one stick of ram (cos this has worked for me many times... and I has 2GB at that time) and what do ya know, it booted fine! The odd thing is, I put the stick back in after and it still booted fine? I know what it is now, but just give it ago... as I say its prob not going to work for you, but some advice is better than no advice right?
 
Well sure, i will give it a go. Although, i have installed the drive as a slave on another machine and i get the same error, even though the drive is not the boot drive.

Just get an NTFS.sys blue screen on startup.

As i have said above, i have already ordered a new drive fom OcUk, so will install Windows on there as the majority of my files are on another drive for safe keeping. Its just the odd save game (BioShock i think !) and emails from the dead drive that i would like to get off. Will look at getting Spinrite later to see if it will reserect the drive.
 
Sherm said:
Been looking into this Spinrite, looks pretty good. Whats the chances of this being able to fix the ntfs.sys problem?
Click to expand...

My guess is that the NTFS system is encountering a bit of malformed data or some other unexpected response from the drive that it can't recover from and boom, BSOD. If the drive itself has some kind of electronics failure causing it to send odd data to the OS then Spinrite will do nothing. If it's just bad sectors then spinrite has a good-high chance of fixing whatever bit of bad data is causing the BSOD. So run the manufacturer's diagnostic first: If that reports an electronics failure you're screwed.

If it's an IDE drive, make sure it's not on the same cable/channel as the boot drive. One drive can disrupt the operation of the other.

I've seen spinrite fix an NTFS.sys BSOD before (and others), though I've also seen it fail to do so. It's also fixed "Windows cannot start because [some startup file] is missing or corrupt" errors. Word of advice: run it on a spare PC. It can potentially run for days if the drive is falling to bits, but usually takes somewhere between 3-16 hours. Depends on the state of the drive. Lastly it's not possible to really predict the success of a data recovery, because you're basicly salvaging from something that's broken in either file system or hardware.
 
You must log in or register to reply here.
Back
Top Bottom