Sign in with
Sign up | Sign in
Your question
Closed

Diagnose startup/boot hang ups in Windows 7

Tags:
Last response: in Windows 7
Share
August 30, 2010 9:27:11 PM

***********************EDIT***********************

PROBLEM FIXED


I'm editing the 1st post for anybody who stumbles on this thread after researching the same problem.

Flashing the BIOS solved my issue, which was that my new pc would freeze at startup.

Read below for other suggestions concerning the registry, hardware drivers, corrupt system files, etc.

Thanks to everybody, and especially to Schan for his wise counsel !

READ DOWN FOR THE ORIGINAL 1st POST.

**********************/EDIT***********************


Hi,

I'd really appreciate suggestions on how to diagnose boot problems.

I recently bought a new system (specs below) and installed Windows 7.
Everything runs fine, except for occasional hang ups at startup. Occasional but very regular.

More precisely, when I boot the pc, as the 4 color spheres appear and start whirling toward making the MS logo, everything freezes.
I then have to manually shut down and reboot. I am then offered to start Windows normally or let Windows attempt a startup repair.
I have tried the latter a couple of times, but Windows failed to come up with anything.

The pc will boot fine 4-5 times in a row, then freeze 2-3 times, sometimes more, then fine again, and so on...

I have tried to consult the Event Viewer after the problem occurred, but nothing dramatic shows up.
[At the moment, I have 2 warnings: A 1014 (DNS client event) and a 3036 (Application, SystemIndex Catalog).]

As far as I can tell, it could be related to software or hardware, but I don't really know where to start looking and how to troubleshoot.

If anybody would be generous enough to offer advice, I'd greatly appreciate.
Thanks.

............
System specs :
cpu : Phenom 2 555 x2 3.2Ghz 7MB Black
Motherboard : GIGABYTE GA-890GPA-UD3H
ram : Kingston KHX1600C9D3K2/4GX Hyper X
Graphics : SAPPHIRE HD5770 1GIG

Running Windows 7 x32.

Windows and drivers all up to date.

............

PS - I've registered an account with this forum, but haven't received the confirmation email yet.
I've asked for it to be resent, checked my email address and everything, but still nothing...
a b $ Windows 7
August 30, 2010 9:43:38 PM

Could be a driver failing to load.

Make sure you have all the latest drivers for all your hardware, via the manufactures websites. (Even though you say we have 'em.)

Since it's "hanging" at the logo, I don't think its the programs loading at start up. But you could check via running the "msconfig" tool. Careful! Don't disable ANY Microsoft applications from loading at start up, except maybe Messenger.
Score
0
August 30, 2010 9:54:29 PM

I'll try PC Pitstop Driver Alert. (Just read about it in the «Windows 7 tips» sticky thread.)

Maybe this'll reveal something...
Score
0
Related resources
August 30, 2010 10:39:32 PM

So...

Driver Alert informed me that I needed to update 2 components (Realtek PCIe GBE Family Controller & Realtek High Definition Audio Device).
I did, and now Driver Alert tells me everything is up to date.

I restarted the system a few times to see if my problem would still occur.

-At the 4th reboot attempt it hung up, and then again the next 2 times.

So it would appear it's something else...
Score
0
August 31, 2010 1:16:44 AM

Some more info.

Here are the programs that are set to run at startup :

HKCU:Run Sidebar C:\Program Files\Windows Sidebar\sidebar.exe /autoRun
HKLM:Run AVG9_TRAY C:\PROGRA~1\AVG\AVG9\avgtray.exe
HKLM:Run JMB36X IDE Setup C:\Windows\RaidTool\xInsIDE.exe
HKLM:Run NUSB3MON "C:\Program Files\Renesas Electronics\USB 3.0 Host Controller Driver\Application\nusb3mon.exe"
HKLM:Run StartCCC "C:\Program Files\ATI Technologies\ATI.ACE\Core-Static\CLIStart.exe" MSRun

I've just disabled "StartCCC" as it's unnecessary. We'll see if that makes a difference, but I'd doubt it.

Otherwise, as you see, I keep this list fairly clean.

Also, I forgot to mention above that I'm running W 7 x32 (I'll edit the intro post).

Anyways, hoping someone will come up with other troubleshooting suggestions.

Thanks.
Score
0
a b $ Windows 7
August 31, 2010 1:50:31 AM

Anyway, the StartCCC is the Catalyst Control Center for the Radeon GFX card. It's OK to disable it, if you didn't tweak the card.

Else, I'm at a loss. The big thing is it hangs at the MS logo. So it's a driver or MS application. Most programs load once you're at the desktop (i.e. CCC). Sorta.
Score
0
August 31, 2010 2:30:28 AM

foscooter said:
Anyway, the StartCCC is the Catalyst Control Center for the Radeon GFX card. It's OK to disable it, if you didn't tweak the card.

Else, I'm at a loss. The big thing is it hangs at the MS logo. So it's a driver or MS application. Most programs load once you're at the desktop (i.e. CCC). Sorta.


Thanks a lot for the input. Greatly appreciated.

I'm wondering if it's due to a corrupt installation then...
Or could it be hardware related ? Say something to do with the RAM ?

(I'm asking about RAM because once, soon after installing the system, I had a BSOD with a warning message related to RAM overheating.
Since then, I've moved a hd away from the sticks to allow better ventilation. I've also done a memtest (8hrs, 10 passes) which came back clean.
I haven't had any BSOD since.)

While browsing different forums, I hit a thread where someone else mentioned he had the same problem, while using the same motherboard as me. Apparently, moving his graphics card from one PCI-E slot to another fixed it.
I haven't tried that yet. Maybe I should...
Score
0
a b $ Windows 7
August 31, 2010 1:18:54 PM

Are you using the USB 3 ports? Try disabling usb 3 and the software and see what happens.
Score
0
August 31, 2010 3:04:06 PM

mhelm1 said:
Are you using the USB 3 ports? Try disabling usb 3 and the software and see what happens.


How would I do that... Through the BIOS ?
(That's one area I'm not too familiar with...)
Score
0
a b $ Windows 7
August 31, 2010 3:17:47 PM

Yes, you disable in bios then stop the app from running in start up or services.
apps should say usb3.0 or such. If it doesn't help re enable and go to the next hardware item to try.
Definitly move the video card to test that theory as well. Just do one at a time.
Score
0
August 31, 2010 3:49:05 PM

Ok, thanks.
I'll fiddle with that later and report back.

(Sometimes, when trying to solve such issues, I can come to forget that I bought this computer to do actual work...)
Score
0
September 2, 2010 7:43:40 AM

mhelm1 said:
Yes, you disable in bios then stop the app from running in start up or services.
apps should say usb3.0 or such. If it doesn't help re enable and go to the next hardware item to try.
Definitly move the video card to test that theory as well. Just do one at a time.


Soooo...

Moved the card from one pci-e slot to the other.
Still got the freeze.

Turned off usb3 in both bios and msconfig.
Still got the freeze.

...
At this point, would it be smart to attempt a W7 startup repair ?
Or if not, what else ?
Score
0
a b $ Windows 7
September 2, 2010 6:14:49 PM

Yep, try the "Start Up repair" or system recovery.

If it still fails, you're looking at a OS clean re-install. Hope you have things backed up!
Score
0
September 2, 2010 7:21:05 PM

foscooter said:
If it still fails, you're looking at a OS clean re-install. Hope you have things backed up!


Frankly, I don't have time these days to start backing up all my stuff and reinstall everything.
If a repair doesn't work, I'll just live with this annoyance for a while. Luckily, this startup freeze appears to be the only bug I have.
Score
0
a b $ Windows 7
September 2, 2010 10:09:15 PM

Let us know what happens, either way.

I'd like to know if the recovery program from the intall disk solves this problem.
Score
0

Best solution

September 2, 2010 11:52:59 PM

Hi, I'll try to put in some input as well. As others have mentioned, it could be a few things: services, drivers, start-up programs, etc (if it's software). Correct me if I'm wrong, but I haven't seen any input on hardware tests. I'll start off with hardware checks then we can move onto more complicated software checks.

I could start off by running hard drive diagnostics. I recommend the free Seagate Diagnostic Tool. Your hard drive does not have to be Seagate for this to run. You can download it at www.seagate.com. It's a GUI so it should be self explanatory.

Next, I would do a memory test. Run memtest. You can download the ISO from memtest.org. Burn the ISO to a cd using your favorite burning software. I would use imgburn (since it's free) if you don't have any. This could take a considerable amount of time, but I would cancel the check after 10-15 passes if there aren't any errors.

Another EXTREMELY important thing to check is a BIOS update. You'll need to go to your manufacturer's website and look for a BIOS update specifically for your motherboard. If you don't know what a BIOS is, it basically stands for Basic Input-Output System. In this issue particularly, it can help improve the interactions between your chipsets/ram/hard drive/etc. This can be why it has flaky performances.

I may have left some other hardware checks, but lets move onto software.

1) Try updating video card driver, if you haven't already.

2) The best way, but time consuming is to do a process of elimination. Load up safe mode by pressing F8 before the Windows logo. Open up MSCONFIG and tell it to do the diagnostic startup. This will only load up basic Windows service and drivers. Now reboot and let it load. IF it loads up perfectly, then we know it's a 3rd party and not related to Windows. If it is related to Windows, I would assume one of the previous checks would have resolved it already or install all your Windows Updates. There is a slight chance of corrupt installation, but that's pretty rare. If that's the case then yeah, you'll have to format and re-install preferably with another media.

Anyways, if it did load up smoothly without problems, just open up msconfig again and check services one by one and reboot until you come across one that causes the problem. If none, then do the same with drivers. I'm almost certain you'll run across one that will cause you a problem.

If you need help to figure out how to resolve that issue ...feel free to post the service or driver here and I'll see what I can do.

Good luck and have fun!
Share
a b $ Windows 7
September 3, 2010 6:32:32 PM

GR8 advice schan!

I forgot about the diagnotic start up in msconfig.
Score
0
September 3, 2010 9:48:06 PM

foscooter said:
GR8 advice schan!

I forgot about the diagnotic start up in msconfig.


Thanks for the compliment!
Score
0
September 8, 2010 5:12:12 AM

Thanks a lot for all the input guys.
Sorry I haven't answered in a few days : I haven't received email notifications, so I assumed the thread had died out.

...
Schan,

Over the next few days, I will attempt the different tricks you suggested. I'm familiar enough with all of them.

-I have been doing overnight memtests 4-5 times since the last few weeks. So far everything is fine on that front.
-I have updated all my hardware drivers just last week, including my video card's.

So, these next few days I will try :
-the Seagate test
-flashing the bios
-the msconfig diagnostic startup tool

...
I'll keep you posted.

Thanks immensely for taking time with this.
Score
0
September 8, 2010 8:24:53 PM

A quick report :

1) I used SeaTools on my drives, both "long drive self test" and "long generic" tests. I got a "Pass" verdict everywhere.

Should I also perform other tests ?

2) I attempted a "diagnostic startup" from MSCONFIG.
It froze like it does usually at the 4th restart attempt...

...
I guess this indicates that my problem is either related to BIOS or a corrupt Windows installation.

So, unless someone has another suggestion, I figure I'll 1st attempt to flash the BIOS, and if that doesn't solve it then a startup repair procedure from a new Windows 7 installation cd.

[If all of that fails, then I'll just live with it for the time being. I simply cannot afford the time needed to backup all my data, format and reinstall from scratch right now.
-I already lost nearly 2 weeks of work when my old system blew up and I had to order and install this one.]

Thanks.
Score
0
September 9, 2010 12:08:21 AM

Which service or driver did it start doing that or did you mean it even did that on diagnostic startup? If so, then yes I would say flashing the BIOS would be the next thing. If it still does that, then you are already aware of the next step.
Score
0
September 9, 2010 12:12:55 AM

schan said:
Which service or driver did it start doing that or did you mean it even did that on diagnostic startup? If so, then yes I would say flashing the BIOS would be the next thing. If it still does that, then you are already aware of the next step.


Yup: It froze while booting on diagnostic startup; no other service or driver loading.
Score
0
September 9, 2010 4:21:22 PM

Ah, wells that sucks. I guess the remaining things are to flash the BIOS, try running a registry software cleaner (CCleaner...I've seen people used it but I haven't tried it), and yes...formatting which you don't have the time for.

If it persists even through diagnostic start-up, I'm afraid that are the options you have. Feel free to keep us posted when you have time to format. If it still does that even after formatting, it's clear enough that it's a hardware issue...although the tests says everything is fine it's not always accurate. I've had to replace the memory or the hard drive several times although tests said they were working.

But yeah good luck with the rest!
Score
0
September 9, 2010 6:32:15 PM

Thanks Schan,

My only worry, if it's hardware related, is I may not be able test it thoroughly before a few months. Hopefully, I'll get to know before the warranty expires...

...
One question :

How is it possible that it boots fine sometimes, but jams other times ?
Shouldn't whatever causes the problem act more consistently ?

(These days, the pattern is as follows : the system will boot w/o problem 3-4 times in a row; then it will freeze 2-3 boot attempts in a row; then fine again, and so on.)
Score
0
September 9, 2010 8:40:28 PM

Although it's a simple question the answer is quite complicated and it's all speculation.

For example, if your issue concerns with a corrupted entry in the registry. Windows may or may not sometimes try to load that entry. My technical knowledge is not strong enough to understand what exactly it loads and how it searches for what to load. If it tries to load it then it will get corrupted.

If the issue is ram, then the problem will definitely not be consistent. It may be the case that Windows is trying to load up something onto ram during load up and it screws up there. Of course, Windows is not trying to always load it in the same address so hence the inconsistencies.

I guess another good effort is to check the Event Viewer (eventvwr) after it jams under (application and system) to see if it logs anything.

Also, the BIOS controls a lot of things especially how hardware on the motherboard communicates with each other/etc. With an outdated BIOS, it may not perform optimally hence these inconsistencies. This is why you should update the BIOS.

Writing this up caused me to think of two other things you can try. First, load up your Windows 7 cd once the system boots into Windows. Run the sfc /scannow command in a dos prompt or through the run command. This will check the integrity of the system file and replace them if they're corrupted. You can find what it finds through the Event Viewer. The task will be called "Windows File Protection"

You can also do a repair installation. This will re-install Windows while leaving EVERYTHING intact so you won't have to format and re-install. You can do a bit more research on repair installations, but yeah it should not lose anything...again though...use at your own risk. If something screws up in the process then you may be forced to format/reinstall if it can't recover. If you are thinking about this, then at least back up beforehand.

If they're still under warranty, I would at least try to get new RAM and see if it resolves the issue. Try not to overuse memtest either. It puts a lot of stress on the RAM and they usually will get a lot hotter than normal.

I'll post more if I think of more.
Score
0
a b $ Windows 7
September 10, 2010 2:42:18 AM

Could be bad RAM. Have you tried diag. that?

I don't know what the program is called, sorry.

MemCheck?
Score
0
a b $ Windows 7
September 10, 2010 11:48:08 PM

foscooter said:
Could be bad RAM. Have you tried diag. that?

I don't know what the program is called, sorry.

MemCheck?

Memtest86
Score
0
September 11, 2010 2:58:25 AM

angkor said:
Hi,

I'd really appreciate suggestions on how to diagnose boot problems.

I recently bought a new system (specs below) and installed Windows 7.
Everything runs fine, except for occasional hang ups at startup. Occasional but very regular.

More precisely, when I boot the pc, as the 4 color spheres appear and start whirling toward making the MS logo, everything freezes.
I then have to manually shut down and reboot. I am then offered to start Windows normally or let Windows attempt a startup repair.
I have tried the latter a couple of times, but Windows failed to come up with anything.

The hang ups will happen roughly 1/5 times that I boot the pc. The other times it boots just fine and very fast.
Sometimes it will hang for several attempts in a row; sometimes not at all for a while. That's why I say it appears to be pretty random.

I have tried to consult the Event Viewer after the problem occurred, but nothing dramatic shows up.
[At the moment, I have 2 warnings: A 1014 (DNS client event) and a 3036 (Application, SystemIndex Catalog).]

As far as I can tell, it could be related to software or hardware, but I don't really know where to start looking and how to troubleshoot.

If anybody would be generous enough to offer advice, I'd greatly appreciate.
Thanks.

............
System specs :
cpu : Phenom 2 555 x2 3.2Ghz 7MB Black
Motherboard : GIGABYTE GA-890GPA-UD3H
ram : Kingston KHX1600C9D3K2/4GX Hyper X
Graphics : SAPPHIRE HD5770 1GIG

Running Windows 7 x32.

Windows and drivers all up to date.

............

PS - I've registered an account with this forum, but haven't received the confirmation email yet.
I've asked for it to be resent, checked my email address and everything, but still nothing...



Hi, I just built my 1st computer and did a lot of reading in preparation to do it. All is well so far. One of the most mentioned reasons I've seen for a computer not booting is a problem with hardware. The mother board, memory or to much heat. Since its a new computer, and I assume you don't have that many important files and stuff did you consider resetting the mother board to default values (pretty easy) and reloading windows ?
Score
0
September 12, 2010 8:51:17 PM

Thanks again everybody for all the advice. Thanks especially to Schan : your detailed explanations on possible causes do help me tackle this problem with a more strategic approach. Greatly appreciated!

I also believe that, even if I end up not finding the solution for my own problem, this thread will certainly prove useful for other people researching similar problems. This is the great thing with these forums : I can’t count the number of times I’ve found the solution to problems like bugs or virii this way.

...
I'll keep trying things out this coming week.

-I'll keep doing overnight memtests, but from now on, I'll do them with only 1 stick at the time. This should help find any eventual problem more efficiently. (I can't believe I haven't thought about this before.)

-I will also try to run the "sfc /scannow" prompt.

-And maybe a complete repair routine from the installation cd, if the above doesn't work.

-As for flashing the BIOS, I looked into the documentation and it appears trickier with this board than with my previous machine.
For one thing, apparently I can't do it from Windows : I have to do it from a floppy. Problem is, I don't have a floppy drive installed at the moment. So I'll first have to connect one and buy floppies…

I will report as I progress.

Thanks again Schan, Foscooter, Mhelm1 and Gerry410 !
Score
0
September 13, 2010 6:55:18 PM

Thanks for your appreciation, Angkor! It means a lot. I am trying to take my knowledge and training to the next level so things like this will prove useful.

I hope you'll be able to resolve it soon.


P.S. For flashing the BIOS, you should be able to burn the ISO (I'm assuming) image onto a CD and flash it from there. It doesn't have to be from a floppy.
Score
0
September 13, 2010 8:35:38 PM

schan said:
P.S. For flashing the BIOS, you should be able to burn the ISO (I'm assuming) image onto a CD and flash it from there. It doesn't have to be from a floppy.


Good to know. I wonder why they don't mention this in the documentation : I'm assuming less and less systems come with floppy drives these days.

-I tried the sfc /scannow routine yesterday, and it reported that it couldn't find anything wrong.

Going over the event viewer afterward, I found a good number of errors and warnings.
Especially, there are VOLSNAP errors (ID 36), which goes : "The shadow copies of volume C: were aborted because of an IO failure on volume C:."

Then VSS errors (ID 8194) : "Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface. hr = 0x80070005, Access is denied.
. This is often caused by incorrect security settings in either the writer or requestor process. "

There are also JRAID errors (ID 117) : "The driver for device \Device\Scsi\JRAID1 detected a port timeout due to prolonged inactivity. All associated busses were reset in an effort to clear the condition."

(I'm only reporting the ones that appear most meaningful here.)

I'm starting to wonder if my problem couldn't possibly be related to a defective HD (even though the Seagate test came out clean).
The reason is, my HD is the only part of this system that I didn't buy new.

I'll try a CHKDSK /R routine later on.
I'm also considering buying a new HD anyway, if only to get a bigger drive.
Score
0
September 13, 2010 9:13:21 PM

...Also a Disk error warning (ID 51) : "An error was detected on device \Device\Harddisk1\DR1 during a paging operation."
Score
0
September 13, 2010 10:24:02 PM

Knocking on wood here, but I've just flashed the BIOS and I seem to be out of the woods.

-I hadn't realized Gigabyte has a little app called @BIOS, which downloads and installs BIOS updates.
After using it, I've rebooted some 11 times so far and... NO FREEZE !

Now, it may just be an incredible string of luck (or bad luck, depending), but it's definitely the highest number of times I've booted w/o problems in a row.

...
Even though it was suggested from the beginning, I'd put off flashing because that operation always makes me a little nervous. Though I guess I shouldn't be, now that I have a dual BIOS motherboard. But I guess I was trying to avoid any operation that could possibly have me spend any more time into further rescue operations.

Now, I'll keep testing by rebooting as often as I can whenever I leave the PC.
I'll report whether all keeps going well or not.

If all's well, I guess I'll move on to figuring out all those Event Viewer errors and warnings.

You know, I'm tempted to paraphrase Homer Simpson here :
-Computers : The solution to AND the cause of all our modern problems.
Score
0
a b $ Windows 7
September 13, 2010 10:30:20 PM

GR8 to hear! Anything else?
Score
0
September 13, 2010 11:12:11 PM

Great to hear, Angkor! Quite honestly, those Event Viewer errors could be a direct result from a flaky BIOS. Now that you flashed the BIOS and it appears to have resolved the issue, I am assuming that those errors you see in Eventvwr will self-resolve. I wouldn't worry too much about it. However, if you continue seeing it, I would look into updating your SCSI/RAID driver.

Ironically, flashing the BIOS has now been the 1st thing I do as a troubleshooting procedure. There is no point investing time in all these tests/trials and errors if the BIOS is outdated. If I were to compare it to medical health, it's pointless for the doctor to prescribe medicine, physical therapy and all that stuff, if they skip the x-ray portion. All that investment is unnecessary if it turns out the patient had a broken/fractured bone.

Flashing the BIOS, to me, is like getting an X-ray - extremely important and necessary before anything else.
Score
0
September 14, 2010 1:10:32 AM

schan said:
Flashing the BIOS, to me, is like getting an X-ray - extremely important and necessary before anything else.


Advice well noted. I'll keep it in mind for future reference.

Now I've cleared the event viewer. I'll see what new messages pop up in the next few days.

Thanks again !
Score
0
September 14, 2010 9:31:20 AM

Maybe I do still need some help after all.

Below is the result of a chkdsk /r routine, which found some problems.
Apparently something funny in step 3, and then something quite worrisome in step 5 :
"Write failure..." "The second NTFS boot sector is unwriteable"

I found a forum thread on Google where the problem was fixed using something called "Acronis"
http://forum.acronis.com/forum/6228

Should I consider doing that ?
Should I take this as a signal that I should buy a new HD ?...

Thanks for any advice.

*****************************************************

Log Name: Application
Source: Microsoft-Windows-Wininit
Date: 2010-09-14 05:09:33
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: XXXXXX
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.

CHKDSK is verifying files (stage 1 of 5)...
141824 file records processed.

File verification completed.
711 large file records processed.

0 bad file records processed.

2 EA records processed.

44 reparse records processed.

CHKDSK is verifying indexes (stage 2 of 5)...
185028 index entries processed.

Index verification completed.
0 unindexed files scanned.

0 unindexed files recovered.

CHKDSK is verifying security descriptors (stage 3 of 5)...
141824 file SDs/SIDs processed.

Cleaning up 788 unused index entries from index $SII of file 0x9.
Cleaning up 788 unused index entries from index $SDH of file 0x9.
Cleaning up 788 unused security descriptors.
Security descriptor verification completed.
21603 data files processed.

CHKDSK is verifying Usn Journal...
35234800 USN bytes processed.

Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
141808 files processed.

File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
9646131 free clusters processed.

Free space verification is complete.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
Correcting errors in the Volume Bitmap.
Write failure with status 0xc0000015 at offset 0x3a32225e00 for 0x200 bytes.
The second NTFS boot sector is unwriteable.

Internal Info:
00 2a 02 00 cf 18 02 00 e0 e5 03 00 00 00 00 00 .*..............
0f 85 00 00 2c 00 00 00 00 00 00 00 00 00 00 00 ....,...........
40 8f 04 00 50 01 03 00 f0 19 03 00 00 00 03 00 @...P...........

Windows has finished checking your disk.
Please wait while your computer restarts.

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Wininit" Guid="{206f6dea-d3c5-4d10-bc72-989f03c8b84b}" EventSourceName="Wininit" />
<EventID Qualifiers="16384">1001</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2010-09-14T09:09:33.000000000Z" />
<EventRecordID>8062</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>XXXXXX</Computer>
<Security />
</System>
<EventData>
<Data>

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.

CHKDSK is verifying files (stage 1 of 5)...
141824 file records processed.

File verification completed.
711 large file records processed.

0 bad file records processed.

2 EA records processed.

44 reparse records processed.


CHKDSK is verifying indexes (stage 2 of 5)...
185028 index entries processed.

Index verification completed.
0 unindexed files scanned.

0 unindexed files recovered.


CHKDSK is verifying security descriptors (stage 3 of 5)...
141824 file SDs/SIDs processed.

Cleaning up 788 unused index entries from index $SII of file 0x9.
Cleaning up 788 unused index entries from index $SDH of file 0x9.
Cleaning up 788 unused security descriptors.
Security descriptor verification completed.
21603 data files processed.

CHKDSK is verifying Usn Journal...
35234800 USN bytes processed.

Usn Journal verification completed.

CHKDSK is verifying file data (stage 4 of 5)...
141808 files processed.

File data verification completed.

CHKDSK is verifying free space (stage 5 of 5)...
9646131 free clusters processed.

Free space verification is complete.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
Correcting errors in the Volume Bitmap.
Write failure with status 0xc0000015 at offset 0x3a32225e00 for 0x200 bytes.
The second NTFS boot sector is unwriteable.

Internal Info:
00 2a 02 00 cf 18 02 00 e0 e5 03 00 00 00 00 00 .*..............
0f 85 00 00 2c 00 00 00 00 00 00 00 00 00 00 00 ....,...........
40 8f 04 00 50 01 03 00 f0 19 03 00 00 00 03 00 @...P...........

Windows has finished checking your disk.
Please wait while your computer restarts.
</Data>
</EventData>
</Event>
Score
0
September 14, 2010 3:34:12 PM

This is the first time I've encountered such an issue, but the second NTFS boot sector is actually a backup of your boot sector. It apparently got corrupted. I do have a couple of questions though.

You said this is a newer system and the hard drive was transferred from the old computer to the new one. Can you give us a bit more details about that? I am assuming it had Windows 7 on there. Nevertheless, I would follow the instructions on the link that you posted. Basically, you need to make a backup image copy, shrink the size of the partition (the 2nd NTFS boot sector lives at the end of the partition - therefore, shrinking the size will automatically get rid of it), restore the image copy, and then expand the partition back to its original size. Then, Windows will backup your primary boot sector, which will create a clean second NTFS boot sector. My experience with this issue is pretty much none, so I highly advise that you follow everything step by step in that forum. If you would like to double check before performing something you're uncomfortable with just let us know.

As far as the physical hard drive itself, it does not seem like it needs to get replaced. Everything seems fine except for the NTFS secondary boot sector. The issues at step 3/5 could simply be from all those crashes in the beginning where you had to shut the computer down and turn it back on. Hard drive failures are pretty apparent. Some symptoms of them are EXTREMELY slow start-up/navigation...loads of disk errors in the event viewer trying to access different sectors, SeaTools are pretty good at detecting them, and chkdsk should've given an error message saying something like this sector is unreadable...bad...etc. It doesn't seem like the case here.

FYI - the freeze at startup COULD sometimes be caused by this second ntfs boot sector corruption.
Score
0
September 14, 2010 5:38:58 PM

Actually, when I bought the new system, this HD was given to me by a friend. Whatever was on it originally, I formatted the drive and installed a fresh copy of Windows 7.

I also wrote to this friend for his advice on the matter. He happens to be a programmer and has a partial formation in computer engineering.

I'll see what he has to say on the matter.
Score
0
September 18, 2010 12:23:23 AM

Best answer selected by Angkor.
Score
0
a b $ Windows 7
September 18, 2010 11:19:18 AM

This topic has been closed by Mousemonkey
Score
0
!