BSOD trying to install service pack 1

Okay, I'm fairly stumped. I'm trying to finish my latest system, an APU build, and I've been getting some BSODs, halfway between random and patterned. At first, I had a faulty PSU, which prompted me to both replace it and test the hardware. The memory passed memtest, the hard drive is new and works well, and as I said, I know the PSU is good. I don't have anything else FM1, so I can't try swapping out the mobo/APU.

Anyway.

I had installed Win7x64 Ult and started in with the long chain of updates. The system started blue screening pretty sporatically.

Long story short, after a wipe and second install, I got it just to the point where I had service pack 1 installed, and the BSOD had thinned out. After upgrading the BIOS, well, that was the end of that Windows installation.

So, now I've started over. Windows is up to the point where SP1 is the next insall.

And that's where I am now. I've tried installing SP1, and it has failed a couple times. I followed a MS help article to a Hotfix (KB947821) and that went through. Still, though, SP1 fails. I've even tried the standalone installer (rather than the Automatic Updates.)

The standalone fails (it says Windows is missing a component, following the troubleshooters/links gets me to the hotfix which installed correctly) and the AU version does one of three things: it either stalls out at 75% complete; it installs correctly, reboots to configures, fails midway through and reverts; or throws a BSOD.

Most commonly it's simply a "Memory Management" BSOD or something about a write call made to read-only memory. These seem to only crop up for the update installer, even though there are some other oddities - Catalyst Control Center crashing 30% of the time on bootup, for example.

Anyway, here's my system specs:
OS Name Microsoft Windows 7 Ultimate
Version 6.1.7600 Build 7600
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name DREN
System Manufacturer Gigabyte Technology Co., Ltd.
System Model GA-A75-UD4H
System Type x64-based PC
Processor AMD A8-3850 APU with Radeon(tm) HD Graphics, 2900 Mhz, 4 Core(s), 4 Logical Processor(s)
BIOS Version/Date Award Software International, Inc. F6, 9/16/2011
SMBIOS Version 2.4
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume1
Locale United States
Hardware Abstraction Layer Version = "6.1.7600.16385"

My BIOS (and EasyTune6) are up to date, and I'm on a wireless network (with the adaptor up to date, as well.)

Thanks in advance for any help or advice!
This is my 8th build or so, but I haven't had this issue before.

DarthDoctor said:

Okay, I'm fairly stumped. I'm trying to finish my latest system, an APU build, and I've been getting some BSODs, halfway between random and patterned. At first, I had a faulty PSU, which prompted me to both replace it and test the hardware. The memory passed memtest, the hard drive is new and works well, and as I said, I know the PSU is good. I don't have anything else FM1, so I can't try swapping out the mobo/APU.

Anyway.

I had installed Win7x64 Ult and started in with the long chain of updates. The system started blue screening pretty sporatically.

Long story short, after a wipe and second install, I got it just to the point where I had service pack 1 installed, and the BSOD had thinned out. After upgrading the BIOS, well, that was the end of that Windows installation.

So, now I've started over. Windows is up to the point where SP1 is the next insall.

And that's where I am now. I've tried installing SP1, and it has failed a couple times. I followed a MS help article to a Hotfix (KB947821) and that went through. Still, though, SP1 fails. I've even tried the standalone installer (rather than the Automatic Updates.)

The standalone fails (it says Windows is missing a component, following the troubleshooters/links gets me to the hotfix which installed correctly) and the AU version does one of three things: it either stalls out at 75% complete; it installs correctly, reboots to configures, fails midway through and reverts; or throws a BSOD.

Most commonly it's simply a "Memory Management" BSOD or something about a write call made to read-only memory. These seem to only crop up for the update installer, even though there are some other oddities - Catalyst Control Center crashing 30% of the time on bootup, for example.

Anyway, here's my system specs:
OS Name Microsoft Windows 7 Ultimate
Version 6.1.7600 Build 7600
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name DREN
System Manufacturer Gigabyte Technology Co., Ltd.
System Model GA-A75-UD4H
System Type x64-based PC
Processor AMD A8-3850 APU with Radeon(tm) HD Graphics, 2900 Mhz, 4 Core(s), 4 Logical Processor(s)
BIOS Version/Date Award Software International, Inc. F6, 9/16/2011
SMBIOS Version 2.4
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume1
Locale United States
Hardware Abstraction Layer Version = "6.1.7600.16385"

My BIOS (and EasyTune6) are up to date, and I'm on a wireless network (with the adaptor up to date, as well.)

Thanks in advance for any help or advice!
This is my 8th build or so, but I haven't had this issue before.

They are memory management and that is usually caused by a driver.


Please run these two tests to verify your memory and find which driver is causing the problem.


1-Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

RAM - Test with Memtest86+



2-Driver verifier

I'd suggest that you first backup your data 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).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

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 "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 (an estimate on my part).

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.

Driver Verifier - Enable and Disable

Okay, I ran Memtest86+ and indeed, one of my sticks is bad. one seems fine, as does the mobo. Going to try and install service pack 1, see if that works now.

DarthDoctor said:

Okay, I ran Memtest86+ and indeed, one of my sticks is bad. one seems fine, as does the mobo. Going to try and install service pack 1, see if that works now.

Without the ram and mobo slot in use it might.

It's working fine now. I had to "upgrade" it to windows 7 again, the bad memory must have cuased it to not install correctly. Thanks for the quick help!