Windows XP BSOD after getting new PC specs

M

Ma-dazz

Member
My Windows XP machine has got a problem after me getting new specs.
I got a new motherboard, CPU and RAM memory.
Motherboard: GIGABYTE H81M-DS2
CPU: Intel Pentium G3260
RAM: CORSAIR CMV4GX3M1A1600C11

When I boot Windows XP, AFTER the logo loading screen, a BSOD appears and reboots. I got dual boot, so I tried it with Ubuntu and it booted, but what's wrong with Windows XP not booting? Is there something I can do?
 
johnb35

johnb35

Administrator
Staff member
Most likely because that motherboard doesn't support xp. The newer technology won't support such an old operating system. Install windows 7 or above.
 
beers

beers

Moderator
Staff member
Changing chipsets on XP would typically do that as well.

Do a fresh installation of a newer version of Windows.
 
M

Ma-dazz

Member
johnb35 said:
Most likely because that motherboard doesn't support xp. The newer technology won't support such an old operating system. Install windows 7 or above.
Click to expand...

beers said:
Changing chipsets on XP would typically do that as well.

Do a fresh installation of a newer version of Windows.
Click to expand...

So, no XP for me?
If so, how do I proceed with Windows 7? Do I need to make a partition beforehand, and will the new installation erase anything? Will the new partition be treated as the only actual part of the HDD?
 
johnb35

johnb35

Administrator
Staff member
Backup any personal data, Boot to the new OS install cd and wipe the partition for xp and install the new OS to it. Not sure what will happen with your ubuntu boot loader.
 
M

Ma-dazz

Member
johnb35 said:
Backup any personal data, Boot to the new OS install cd and wipe the partition for xp and install the new OS to it. Not sure what will happen with your ubuntu boot loader.
Click to expand...

I've decided to do a Windows XP repair install, because I'm not ready at all to give up XP. What would be the most painless way to do this, with losing minimal registry data and drivers as well as taking the considerations above in my first post?
 
Intel_man

Intel_man

VIP Member
Ma-dazz said:
because I'm not ready at all to give up XP.
Click to expand...
913.gif
 
M

Ma-dazz

Member
beers said:
Not using XP.
Click to expand...
That doesn't make sense. Freshly installing a new OS (any OS) would be a lot more work than just making a repair install.

@Intel_man :
I've done a metric ton of customization to it that I don't want to be lost just yet. Maybe I'll make a full backup and change OS later, but since I don't have the capability to do such a backup yet, I won't be changing OS until the current one will be accessible and backup-able.
 
beers

beers

Moderator
Staff member
Ma-dazz said:
Freshly installing a new OS (any OS) would be a lot more work than just making a repair install.
Click to expand...
As someone who reinstalls every 6 months or so, I beg to differ.

Using a no longer supported OS presents you with a variety of other issues moving forward.
 
M

Ma-dazz

Member
beers said:
As someone who reinstalls every 6 months or so, I beg to differ.

Using a no longer supported OS presents you with a variety of other issues moving forward.
Click to expand...
I understand, but I want to preserve my data and program settings. Is there any way to do so while at the same time having an OS reinstalled with a repair install?
 
johnb35

johnb35

Administrator
Staff member
A repair install usually doesn't fix things. And like I said before, new motherboard doesn't support XP. And the main reason why its probably blue screening is that its an old install from a previous machine and its looking for hardware from the old machine and not finding it hence the bluescreen. Your only chance is to backup your data and do a fresh install of XP or if you still have your old system, put the drive back in it and boot to it. Then uninstall all hardware driver software and don't let windows reinstall it. Then put the drive back in and see what happens. What was your previous motherboard and cpu?
 
Intel_man

Intel_man

VIP Member
If you access the internet with your computer that is on XP, you do realize you are at risk of any security vulnerabilities that exist since April 2014.
 
M

Ma-dazz

Member
johnb35 said:
A repair install usually doesn't fix things. And like I said before, new motherboard doesn't support XP. And the main reason why its probably blue screening is that its an old install from a previous machine and its looking for hardware from the old machine and not finding it hence the bluescreen. Your only chance is to backup your data and do a fresh install of XP or if you still have your old system, put the drive back in it and boot to it. Then uninstall all hardware driver software and don't let windows reinstall it. Then put the drive back in and see what happens. What was your previous motherboard and cpu?
Click to expand...
I'll try anything I can, that's for sure. It just seems to me that I still have a semblance of hope when the BSOD happens after the Windows logo shows and loads. Might just be hardware change that causes it IMO.

My old motherboard were a GIGABYTE EP43-S3L, and my old CPU was an Intel Core 2 Duo E8500@3.16 GHz

@Intel_man
That's why I dual boot with Ubuntu.
 
You must log in or register to reply here.
Top