Another BSOD Startup Loop

Well youve guessed it another lovely bluescreen of death startup - The story -

About 3 months ago a made a computer for a mate put on the usual XP prof SP2 and let him do the rest - apparently the power cable was kicked out and obviously computer was shut off - fair enough -

Then when attaching the power cables and booting the computer up it had the usual Black screens impropor shut down etc and chose "last settings that worked" (or words to that effect)

Waiting while the Windows Splash screen appeared on the screen with the bar moving across after about the time your keyboard lights give a stunning display of life, the screen flashes blue (always nice to see) and the whole process started off again

The same thing happens when booting in safemode commmand prompt netwroking and normally etc

So hearing this is picked up the computer for a further glance - ive had a very similar problem before..but wait theres more!

I simply last time took out the HD from the computer set to to slave stuck it in another computer ran a CHKDSK let it reboot and go through the check and it worked then fine - job done werhey!

But not in this case with this oh no! - i started this same thing with this one took it out of the computer set to slave put it in another computer loaded the main HD and right clicked on my computer on the friend HardDrive on the normal option for CHKDSK check and fix errors etc clicked start and waited.....nothing happened - so for a clearer indication i ran the command prompt and typed "chksk :f" just to see if there was any message and it stated "cannot complete as drive is RAW"

So startled by this i double clicked on the drive and is said "drive is not formmatted format now?" so clicking now and slightly confused as i knew is was NFTS - i decided to repair the windows by putting the HD back in the computer and booting from the orig XP pro retail disc did this and when youve accepted the licence agreement and ready to type "r" to repair windows it states the partition 1 is "unknown" (131062mb) (131051mb free)

This being very very odd as it def does have a whole load of things on that HD and obivously has a boot record as it tries to boot windows in the first place!!

any help would be a dream and im sorry about this thread being a Novel!

FYI:

NEC AD-7170A-0B 18x DVDRW DL
AMD Athlon 64 X2 3800 Retail AM2
Samsung IDE 8MB
Gigabyte GA-M61VME-S2 Socket AM2
1GB PC5300 Samsung DDR2 667Mhz

 

Not totally clear what happened in another life and what the exact symptoms are this time. Can we have a shortened form with the missing details and the correct figures?

The check disk approach is a good basic one, pity it didn't work this time.

Studio T

 

yeah sure sorry about that!

the HD has capacity of 130gb with 8mb cache

The shortended version is:

when booting the computer going through the windows splash screen it crashes and re loads the same again

ive tried to so a chkdsk attaching the harddrive as a slave in another comp but chkdsk wont work on a RAW harddrive but the harddrive is actually a NTFS with full operating system

When attempting to repair the installing as prob corrupt system files by booting from the OS disc however it thinks the HD is comletly empty saying 130gb free but obviously this is not the case as it has a OS installed - any ideas?

 

Go to the advanced boot options screen by repeatedly tapping F8.

Choose to disable windows restart on error

Restart and post the error message on the blue screen of death. You will know when you have arrived. It will have a number like

stop error 0 x 000 000 7F or something.

You can also enable debugging and post the minidump if you like.

I think what you described before was not the BSOD, just the normal windows GUI booting but not finishing.

Studio T

 

thanks for the reply - im not a pro really what should i do when i can do debugging? is it fixable?

 

Adrynalyne has provided a minidump tutorial @

http://forums.majorgeeks.com/showthread.php?t=35246

Simplified when windows crashes, including during startup, it writes a minidump file if debugging is enabled. Reading this files describes in gory detail what happened just before and during the crash. You need special resources to read the file whcih is why you should post it.

Simpler to read post#4 again and post the stop error if you can, remember to disable automatic restart.

Studio T