• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Just swapped out my motherboard, but having some problems...

J

janitor53

Member
Hi all, I just installed a new motherboard, cpu, and ram. I went to a gigabyte x38 MB, an e8400, and 2x2 sticks of gskill ram. Tried to load up windows the first time and I got the BSOD, put the windows dvd in to try and repair and I got this message:

startup repair cannot repair this computer automatically

problem signature:
problem event name: startuprepairV2
problem signature 01: externalmedua
problem signature 02: 6.0.6000.16386.6.0.6000.16386
problem signature 03: 6
problem signature 04: 131074
problem signature 05: norootcause
problem signature 06: norootcause
problem signature 07: 0
problem signature 08: 1
problem signature 09: systemrestore
problem signature 10: 0


anyone have any ideas? I'm kind of stuck here. The PC posts, I can get in to the BIOS, etc. but I can't get in to windows.
thanks.
 
Changing motherboards almost always messes up the windows install, it may be possible to fix it, but I usually end up reformatting whenever I get a new motherboard for a system.
 
I'm trying to reuse the vista install. My exact materials:
gigabyte ex38-dq6
gskill f2-8500cl5d-4gbpk
e8400 (not sure which version, it was an OEM though).

Is there no memtest on the gigabyte bios? I can't seem to find it, I want to exhaust my options before reloading vista because there are a couple things on the harddrive I want to get (the reason I am upgrading was because my mobo stopped posting).

Any other info anyone can give would be great.
 
okay, I assume you're using the latest BIOS for the motherboard, because that's one potential issue there.
another thing I see is the board requires the ram operate at 1.8V, the ram you have operates at 2.0V.
also, check to see if your cpu is a "C0" revision.
make and model of the PSU?
what caused you to change motherboards?
 
How do I check the cpu revision? I am using the corsair modular 620 watt power supply. My mobo just crashed, not really sure why but it stopped posting so I took it as a sign to get a new one! ha!
The RAM issue is a little weird, I ran memtest for a couple of hours and there were no errors, do you think the voltage could be a huge issue?
 
Originally posted by: Strebor
Changing motherboards almost always messes up the windows install, it may be possible to fix it, but I usually end up reformatting whenever I get a new motherboard for a system.
Click to expand...

Yes. I would not bother trying to get Windows to adjust to the new motherboard, though it can be done. Best bet is to do a clean reload of Windows.
 
Re-installing Windows is your best bet.

The mb does not require ram to operate at 1.8v. set it in the bios for what the ram is rated for.
 
to check the CPU revision, you can either manually remove the HSF and check it or get the Intel CPU id utility. what happened when the old motherboard crashed, and errors or did the system shut off? I got the info on the voltages for the motherboard and ram from their respective manufacturers, janitor.
 
The mb bios has provisions for increasing the ram voltage according to the manual by the manufacturer. If it needed to be 1.8v, I can't imagine why you could increase it. 1.8v is simply the default setting.
 
I'm not really sure what happened, it was working one day and then the next day it wouldn't post.
I did reinstall windows and it seems to be working okay so far. Could the SATA connections have caused any problems? I installed the including chipset drivers once I got in to Windows and so far things seemed to have settled down. I am definately concerned about stability though.
 
Usually what should be done is changing the drive controllers to standard controllers before swapping the board. You can then install the driver after you swap out the board. That could be probably what happened. Or possibly a loose USB cable or something...Well, best is to check it out for a few days to see how things goes with the new install. If it works, leave it:B
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top