Failed Startup on win7

dynomonkey · dynomonkey's Computer Specs

if I reinstall it will remove my data correct? Or will in just rewrite the os system? In the past when I reinstalled os it made a mess of my computer. Think 98/me/vista.

**TrainableMan** · TrainableMan's Computer Specs

A reinstall is not necessarily best at all. If your problem is bad or mismatched RAM it won't help at all. If your problem is out-dated drivers then simply installing the correct drivers is all that is needed. If it is a corrupt OS file then a start-up repair can usually correct it. If the corruption is widespread then the hard drive may be dying and a reinstall won't help for long, if at all because you need a new HD. If the problem is caused by a virus then the best solution is to remove the virus.

The best idea is to scan for viruses in safe mode and remove any viruses before anything else. Then, if it is not a virus, zip up your DMP files and post them for a BSOD expert to look over.

Unfortunately our only active BSOD expert on the forums lately, Shintaro, has started a new project in his personal life and has been unavailable for over a week. He was hoping to get back here this weekend but if he doesn't then it may be necessary for you to try posting your DMP files on another forum.

Shintaro · Shintaro's Computer Specs

My apologies for the slow responce.

Could you please run: Memtest86+ Memory Testing

Please let us know how you go.

Shintaro · Shintaro's Computer Specs

You may end up reinstalling due to windows reporting a Registry problem:

Quote:

REGISTRY_ERROR (51)
Something has gone badly wrong with the registry. If a kernel debugger
is available, get a stack trace. It can also indicate that the registry got
an I/O error while trying to read one of its files, so it can be caused by
hardware problems or filesystem corruption.
It may occur due to a failure in a refresh operation, which is used only
in by the security system, and then only when resource limits are encountered.
Arguments:
Arg1: 00000001, (reserved)
Arg2: 8c81b808, (reserved)
Arg3: 016be000, depends on where Windows bugchecked, may be pointer to hive
Arg4: 00000374, depends on where Windows bugchecked, may be return code of
HvCheckHive if the hive is corrupt.

I strongly suggest that you back your data somewhere.

But please also do the RAM test in post #33.

dynomonkey · dynomonkey's Computer Specs

Did the mem test for many hours with no shown errors. I attached a pic of the results.

Having some success with running my system in seletive startup and slowly adding items under the services. But have been unable to find the issue. Wonder if my issue is intermittent.

dynomonkey · dynomonkey's Computer Specs

My last dump was posted in #28. Running stress test now.

Shintaro · Shintaro's Computer Specs

Could you please run Driver Verifier:

(Borrowed from Zigzag3143 posts)

Quote:

Driver verifier

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise.
Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:

Go to Start and type in "verifier" (without the quotes) and press Enter
Select "Create custom settings (for code developers)" and click "Next"
Select "Select individual settings from a full list" and click "Next"
Select everything EXCEPT FOR "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.

If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

dynomonkey · dynomonkey's Computer Specs

Yea....As of now its fixed. Looks like I had a virus that had done some damage to my sys files. After running different virus programs and a few repair programs. I
THINK im fixed. Just now waiting for the next BSOD, but its been a few days now and it appears to be running good. thanks for the help.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Bsod at startup - driver or Bios or Win7 reinstall?	gerrard	Crashes, BSODs and Debugging	29	10-09-2012 03:06 PM
System startup and system congfiguration with user accounts in Win7?	Tim	alt.windows7.general	2	03-06-2012 06:47 PM
Win7(64)"Startup Repair"..Unable to start!	Bozobytes	Windows 7 Support	4	01-27-2012 03:02 AM
1628: failed to complete installation	david	Installation, Setup and Updates	4	04-12-2011 07:47 PM
Win7 startup sound - alternate solution	Dave \Crash\ Dummy	alt.windows7.general	4	03-06-2010 04:32 AM