Solved Clean install windows 7 after updates start installing crash

March 15, 2015 at 22:00:18
Specs: windows 7, 2gb
New hard drive.

Crashes to blue screen with "Windows 7 0x00000074 startup Blue Screen BAD_SYSTEM_CONFIG_INFO"

Stuck boot looping with same blue screen.

I have tried burning different DVDs reinstalling and same happens. The install goes fine, computer boots, no problem and then I start installing the updates for windows 7 and same thing happens every time.

I have run chkdsk and it finds mass amounts of problems but the computer doesn't boot.

I have run chkdsk after initial install before doing any updates and chkdsk finds no problems.

I don't no what else to do.

message edited by ToolPunk


See More: Clean install windows 7 after updates start installing crash

Report •

✔ Best Answer
March 18, 2015 at 00:06:45
For solution jump to ***** otherwise read on for a great story!

First I want to thank you guys for being my backboard to bounce all my issues, ideas, theories and in return to stir up more thoughts with ideals and knowledge of your own. This is why despite my knowledge I come here because even the most wise can overlook even the simplest of things.

You can mark this comment down as SOLVED.

I kept hitting a wall as to why this Source: nvstor32 kept resulting in Reset to device, \Device\RaidPort0, was issued. There are only 2 SATA ports, labeled 1 and 2. I struggled with the fact that I knew that this small recurring error was the root of all errors, corruption, failures. I searched and researched only to come up with dead ends. I tried every suggestion many that just seemed down right obvious. Why oh why was this error referencing a port 0?

At the end of my ropes and frustrated with the fact that I cant install this persons new 1TB HDD, I get ahold of a 500GB to test the too large theory. After installing the 500GB drive I boot into the bios to switch the boot to CDROM. Exhausted at this point I am staring at the first bios screen to make sure the new HDD was detected and.....

I see the drive was detected but I happen to glance up at the DVD drive. This drive is on IDE Channel.... 0! Now comes the slam head in wall and self questioning. Self "These days drives don't use jumpers much anymore and usually are set by default to cable select" yes I know this "well self, if the IDE channel is channel 0 it would also represent port 0 wouldn't it?" yea that is correct" well if you are looking at the bios and the DVD drive is set to IDE Channel 0 Master... maybe the old trick of making it the slave would solve this issue?"...sigh.. its definitely worth a try even though if you wanted to plug a HDD into the IDE ribbon (since there is only one IDE channel) it couldn't be plugged into the ribbon with the DVD drive being above the HDD. I guess if you used jumpers with the IDE devices and set the HDD to Master and DVD to Slave...

*****Plugged the middle of the IDE ribbon into the DVD drive. It showed up in the bios as IDE Channel 0 Slave. Reinstalled Windows 7 on the 1TB. Issue solved. No Source: nvstor32, Installed all windows updates back to back no issue. Ten hours lost to a 3min fix, I love computers!



#1
March 16, 2015 at 00:38:03
Your registry is getting corrupted by something.

Are you deleting all the partitions?

W7 - Click on > Drive options (advanced) Then highlight each partition & hit > Delete.
http://www.blackviper.com/os-instal...
http://www.blackviper.com/os-instal...



Report •

#2
March 16, 2015 at 04:09:29
Yes deleting all partitions.

Seatools says HD is fine, memtest says Memory is fine. Computer runs with no issues until I start updating windows. It successfully installs most updates and wants a restart but upon restart I get the blue screen with "Windows 7 0x00000074 startup Blue Screen BAD_SYSTEM_CONFIG_INFO".

I have also run sfc /scannow before updates and no problems.

message edited by ToolPunk


Report •

#3
March 16, 2015 at 04:39:45
"BAD_SYSTEM_CONFIG_INFO"
That error is telling us your registry is corrupted.

Do you have any inkling why?

Try this & see if it can throw any light on the problem.

Lazesoft Recovery Suite Home Edition
http://www.softpedia.com/get/System...
http://www.lazesoft.com/lazesoft-re...
Tutorials
http://www.lazesoft.com/guide.html
Screenshot ( SS )
http://i.imgur.com/4HXqQKS.jpg
How to Boot a Computer from a Lazesoft Recovery USB Device
http://www.lazesoft.com/create-a-bo...


Report •

Related Solutions

#4
March 16, 2015 at 10:28:19
What's the new hard drive model number? Are you configuring it as a single partition?

Report •

#5
March 16, 2015 at 12:10:00
I have no idea why other then the fact that it happens after I install the first round of Windows 7 Updates.

I reinstalled windows and refrained from installing updates. Computer has been running with no issues for 2 days now.

I do see only one error in the event log pre-updates that I can not find any fix for.

Source: nvstor
Event ID: 129
Reset to device, \Device\RaidPort0, was issued.

I am going to install updates but this time I am going to leave out any driver updats and just do the OS updates to make sure it is not a driver/hardware conflict.


Report •

#6
March 16, 2015 at 13:21:53
Manually download and install all motherboard drivers from the motherboard (or system) mfg's site before doing updates. I recommend never letting Windows Update install any drivers for you but to get the latest ones yourself from the source only. If necessary do your updates in groups or 10 to 20 at a time and see how things run before you select the next group to install. Let Windows update rescan for updates before selecting the next group, this should reduce the chance for conflicts.

You have to be a little bit crazy to keep you from going insane.


Report •

#7
March 16, 2015 at 14:43:00
This is a normal setup single hard drive single partition other then the system required partition. I dont understand why everything runs fine other then the nvstor
that I cant seem to figure out. I have never had such an issue with such a basic install. I started the updates again and soon after the computer keeps locking up while its installing the updates. Everytime it locks up I get:

Source: nvstor
Event ID: 129
Reset to device, \Device\RaidPort0, was issued.

I also have a mass amount of other errors now to:

Source: Service Control Manager
Event ID: 7011
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the eventlog service.

Source: WindowsUpdateClient
Event ID: 20
Installation Failure: Windows failed to install the following update with error 0x8024200d: Update for Windows 7 (KB2834140).

Source: Ntfs
Event ID: 138
The transaction resource manager at C:\ encountered a fatal error and was shut down. The data contains the error code.

Source: Ntfs
Event ID: 136
The default transaction resource manager on volume C: encountered an error while starting and its metadata was reset. The data contains the error code.

Source: Ntfs
Event ID: 55
The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume \Device\HarddiskVolume2.

Source: Service Control Manager
Event ID: 7031
The Windows Modules Installer service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service.

Source: WindowsUpdateClient
Event ID: 20
Installation Failure: Windows failed to install the following update with error 0x80071a91: Security Update for Windows 7 (KB2676562).


Report •

#8
March 16, 2015 at 14:46:40
Oh and I intend on getting the drivers from the mfg website. I always use the mfg Graphics/Audio driver. One question on that though, the mfg drivers for the rest of the stuff are older then windows versions, should I still stick with the mfg drivers?

Device manager says the HDD is ST1000DM 003-1er162 SCSI

message edited by ToolPunk


Report •

#9
March 16, 2015 at 15:29:30
Play around with your bios settings.

Changing BIOS mode from UEFI to Legacy
http://acer--uk.custhelp.com/app/an...

Boot to UEFI Mode or Legacy BIOS mode
http://technet.microsoft.com/en-au/...
Applies To: Windows 8, Windows 8.1, Windows Server 2012, Windows Server 2012 R2

BIOS Mode - See if Windows Boot in UEFI or Legacy Mode
http://www.eightforums.com/tutorial...

Secure Boot - Enable or Disable in UEFI
http://www.eightforums.com/tutorial...

Protecting the pre-OS environment with UEFI
http://blogs.msdn.com/b/b8/archive/...


Report •

#10
March 16, 2015 at 15:52:54
I am using Windows 7 x86

Report •

#11
March 16, 2015 at 15:57:34
Yes I know, bios settings are what you look at.

Report •

#12
March 16, 2015 at 18:06:30
I am not seeing any of that. This computer is an emachine w3644. The mobo is mcp61sm2ma-rs2h.

I got the mfg drivers installed and I am still getting same error at boot.
Source: nvstor32
Event ID: 129
Reset to device, \Device\RaidPort0, was issued.

I also get a random freeze and the same error each time it happens. Otherwise I'd I don't run the updates the computer runs great.

message edited by ToolPunk


Report •

#13
March 16, 2015 at 18:14:27
With just a clean install of Windows 7 and the mfg drivers I get the following errors at boot:

Source: nvstor32
Event ID: 129
Reset to device, \Device\RaidPort0, was issued.

Source: Service Control Manager
Event ID: 7016
The NVIDIA Display Driver Service service has reported an invalid current state 32.

Source: Service Control Manager
Event ID: 7009
A timeout was reached (30000 milliseconds) while waiting for the NVIDIA Stereoscopic 3D Driver Service service to connect.

Source: Service Control Manager
Event ID: 7000
The NVIDIA Stereoscopic 3D Driver Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.


Report •

#14
March 16, 2015 at 18:30:07
"Source: nvstor32
Event ID: 129
Reset to device, \Device\RaidPort0, was issued"

Go into Device manager & roll back the driver, even if it goes back 10 years.

Here is where to try.
standard dual channel PCI IDE Controller


Report •

#15
March 16, 2015 at 20:38:31
First your errors indicate that you have a Raid error and with one hard drive you should not have RAID activated in your BIOS. GO to BIOS set up and review all settings. RAID should be disabled. SATA should be set to AHCI or possible Legacy mode if it is still a problem. Load drivers from mfg's site only. Only graphics drivers if from a distinct video card can and should be from video chipset mfg's site (AMD or NVidia) but onboard video still needs to be from system mfg's site only. Manually run Windows Update and manually select only the important updates that relate to system, security, and malware removal. Do not allow Drivers to be updated this way. Install only 10 to 20 updates at a time and let the updater rescan for updates after and review those as well. Put anything driver related on a 'don't show me this update again' list. Repeat as needed. Do not install any of the optional updates at this time, it will be time to review them after the system is running right and stable for a while.

You have to be a little bit crazy to keep you from going insane.


Report •

#16
March 16, 2015 at 20:43:57
I just thought of another thing, before installing Windows, unplug any other SATA devices other than the one hard drive and your DVD drive and unplug any USB device other than your keyboard and mouse. This would also lessen any confusion during the install (for the installer, not necessarily for you). Keep the system at this minimal level until after your updates are completed and stable.

You have to be a little bit crazy to keep you from going insane.


Report •

#17
March 16, 2015 at 20:46:59
Raid is disabled in bios. I don't see any ahci or legacy settings in the boot section of the bios. I installed the mfg drivers and I am running a few updates at a time. So far so good but I am still getting with random freezes:

Source: nvstor32
Event ID: 129
Reset to device, \Device\RaidPort0, was issued


Report •

#18
March 16, 2015 at 21:37:43
You've got an older computer and replaced its 160 gb SATA II drive with a 1 Tb SATA III. That's probably not a problem but some of those drives comes with a jumper to slow them down to SATA II. You may want to check if yours has that.

These are the only drivers I could find supplied by emachine:

http://panam.gateway.com/us/en/emac...

and they're rated for XP. If you went to the individual chip manufacturers instead of the computer manufacturer (you weren't clear which 'manufacturer' you meant) they may be for windows 7 but are you sure everything in device manager looks OK?


Report •

#19
March 16, 2015 at 23:23:13
The board is an nforce4 chip set so I went there. Before I installed the nforce drivers, window's driver had the nvidia nforce serial ATA controler under its own "storage controllers" section in device manager. After the nforce driver install it is listed under IDE ATA/ATAPI controllers.

Other then this there are no flags or anything abnormal that I can see.

Why this is so frustrating? I actually put a used 350GB HDD in here and the computer ran great for 3 years until the HDD slowly died. It had windows 7 on it all those years too.


Report •

#20
March 17, 2015 at 00:00:03
Apparently the only hardware change you made was the new drive. Maybe it's just having a problem with a 1 Tb SATA III drive. Another thing you might try, if you have to start over again, would be to split it into two partitions--maybe 500 gig each--just to see if that makes a difference.

Report •

#21
March 17, 2015 at 00:13:12
Oh that is a good idea. So far though installing the updates ten by ten is working but not to sound like a broken record but I still get hangs and that same nvstor32 error.

I am wondering if the hangs caused by nvstor32 the while time windows was trying to update was causing the corruption?

That though leaves me with, how do I fix this nvstor32 error?

I have looked all over and none of the fixes have pertained to me. They have all been disable this raid setting, uninstall that raid driver. I don't have anything raid installed or turned on.. That I can see or am aware of.


Report •

#22
March 17, 2015 at 00:37:51
Not every error message is going to point to a specific cause. If it is a drive problem the raid error may just be another symptom and not the cause.

Another thing to try, I'm thinking the 'port0' part of the message is referring to the SATA port it's connected to on the motherboard. Can you connect the drive to the other motherboard SATA connector and see what happens. (You may need to change the boot order in bios setup too.)


Report •

#23
March 17, 2015 at 02:28:21
The mobo has only sata 1 and 2 and a single full 80/40 master ide. The DVD drive is on the IDE and the HDD was in sata 1. I moved the HDD over to sata 2 and no change, same:

Source: nvstor32
Event ID: 129
Reset to device, \Device\RaidPort0, was issued


Report •

#24
March 17, 2015 at 02:51:58
Unhooked dvd drive from ide no change

Report •

#25
March 17, 2015 at 02:55:16
Source: nvstor32
Event ID: 129
Reset to device, \Device\RaidPort0, was issued

Only error still, still freezing but updates still trucking


Report •

#26
March 17, 2015 at 13:47:39
I guess keep installing the updates and see if they help. I still think it must be something to do with that type of drive on the motherboard since that was the only change you made. Let us know how it goes.

Report •

#27
March 17, 2015 at 16:00:04
Source: nvstor32
Event ID: 129
Reset to device, \Device\RaidPort0, was issued

http://bit.ly/1EoAZQa


Report •

#28
March 18, 2015 at 00:06:45
✔ Best Answer
For solution jump to ***** otherwise read on for a great story!

First I want to thank you guys for being my backboard to bounce all my issues, ideas, theories and in return to stir up more thoughts with ideals and knowledge of your own. This is why despite my knowledge I come here because even the most wise can overlook even the simplest of things.

You can mark this comment down as SOLVED.

I kept hitting a wall as to why this Source: nvstor32 kept resulting in Reset to device, \Device\RaidPort0, was issued. There are only 2 SATA ports, labeled 1 and 2. I struggled with the fact that I knew that this small recurring error was the root of all errors, corruption, failures. I searched and researched only to come up with dead ends. I tried every suggestion many that just seemed down right obvious. Why oh why was this error referencing a port 0?

At the end of my ropes and frustrated with the fact that I cant install this persons new 1TB HDD, I get ahold of a 500GB to test the too large theory. After installing the 500GB drive I boot into the bios to switch the boot to CDROM. Exhausted at this point I am staring at the first bios screen to make sure the new HDD was detected and.....

I see the drive was detected but I happen to glance up at the DVD drive. This drive is on IDE Channel.... 0! Now comes the slam head in wall and self questioning. Self "These days drives don't use jumpers much anymore and usually are set by default to cable select" yes I know this "well self, if the IDE channel is channel 0 it would also represent port 0 wouldn't it?" yea that is correct" well if you are looking at the bios and the DVD drive is set to IDE Channel 0 Master... maybe the old trick of making it the slave would solve this issue?"...sigh.. its definitely worth a try even though if you wanted to plug a HDD into the IDE ribbon (since there is only one IDE channel) it couldn't be plugged into the ribbon with the DVD drive being above the HDD. I guess if you used jumpers with the IDE devices and set the HDD to Master and DVD to Slave...

*****Plugged the middle of the IDE ribbon into the DVD drive. It showed up in the bios as IDE Channel 0 Slave. Reinstalled Windows 7 on the 1TB. Issue solved. No Source: nvstor32, Installed all windows updates back to back no issue. Ten hours lost to a 3min fix, I love computers!


Report •

#29
March 18, 2015 at 00:19:08
"Ten hours lost to a 3min fix, I love computers!"
Amazing how often it turns out to be something simple & basic.

Report •

#30
March 18, 2015 at 01:37:45
Good job! I know it's a very satisfying feeling.

In a couple days the 'best answer' mark will open up to anyone and we can mark your #28. (No one can choose their own response as best answer so wait for someone else to mark yours.)


Report •

#31
March 18, 2015 at 20:40:41
Great to hear you solved it.

You have to be a little bit crazy to keep you from going insane.


Report •

Ask Question