New motherboard, no drivers, bluescreen.

bobthedestroyer

Reputable
Mar 11, 2014
9
0
4,510
Alright so I bought a used motherboard today, and well I'm not exacty a wiz with a computer. For some reason I didn't get any driver disc along with it and when the pc boots up I get bluescreen. Futhermore I don't have any keyboard access in the bios making it impossible for me to attempt to install windows...

Any help is appriciated...
 
Solution
You can't swap major components such as motherboards on a Windows installation without expecting hiccups. While there are certainly exceptions to this, as a rule of thumb, expect to reinstall Windows when you swap motherboards. The times you get away without, is usually when you are using the same CPU family and type, such as AMD to AMD, Intel to Intel, sticking with the same architecture such as x86 or x64, and when the supporting chips on the motherboard are in the same family. Once you change anything major without Windows having it's supporting software updated to match, you get what you're experiencing now.
to get into the bios look for the cmos battery near it should be the clear cmos jumper. make sure the mb power off and clear the cmos with the jumper. if the bios gets cleared you should be able to get into the bios.
if you google the motherboard make and model you find the drivers on the mb vendor web page.
if it an intel mb the intel chipset drivers are on intel web page. amd drivers are on amd web page.
if your using an old hard drive with old copy of windows sometime the sata ports need to be set to ide. to get xp to post without blue screening.
 
Drivers for motherboards and other circuit boards that are included on the driver CD in a retail package are usually out of date by the time they are written to the disc. If you need or want drivers for something, go to the manufacturers website and download the most current drivers. :)

You wouldn't be receiving a blue screen if you were not attempting to boot into Windows, or boot from a Windows installation disc. If you are attempting to boot a previously installed copy of Windows, I suspect that is out of the question. If attempting to boot a Windows XP disc, you may have to instruct the BIOS to treat the SATA controllers as IDE, not AHCI, otherwise you will likely need the controller drivers during the initial stages of the installation process.\

It might be helpful, if you can, to post a picture of the blue screen (if it remains long enough,) or to attempt to identify the particular stop error message that the blue screen is reporting.

Can you give any more details to the computer's equipment, the version of Windows you're attempting to install, and how you're going about installing it?
 

bobthedestroyer

Reputable
Mar 11, 2014
9
0
4,510


I've done exactly that, multiple times infact during the 8 hours I've been working on it. But the main problem with it is that I have no keyboard access. Once I actually got into the bios setup but I couldn't do anything since the keyboard didn't work. And this time when I did it I didn't even get access to the bios setup and can't since I can't well use the keyboard :S I'm really at a loss of ideas. I've tried making a bootable USB stick with the drivers on it.. figured it was worth a shot, didn't work. And I can't boot up from my windows cd because it requires me to hit a key on the keyboard to actually launch the setup..
 

bobthedestroyer

Reputable
Mar 11, 2014
9
0
4,510
The motherboard is called: DP55WB Intel Desktop Board. And the version of windows is; Windows 7 home premium from a dvd disc.
I'm unable to post a screenshot since I'm writing this from an entirely different computer.
 
Home Premium should have no problems loading up and installing, regardless of how the SATA ports are configured, so I think we can take that off the table as being the source of your difficulties.

I think you might want to consider reducing everything to the least number of components possible, for troubleshooting purposes. Remove all but a single stick of memory. If you have both an add-in graphics card and on-board graphics, remove the graphics card and use only the on-board for now. Remove all drives except for the optical drive you are using to boot the Windows installation disc.

At this point, you may try booting to your Windows 7 DVD again, or you may want to download and create a bootable memory diagnostic disc, if you have a blank CD and access to a drive to burn with. This will at least help you to determine whether your RAM is acting up, without the need for anything more fancy. If the first RAM module tests through several passes without error, you can power down, swap in the other RAM module, and test again. Once you are certain your memory is functioning correctly, that is the best time to attempt booting to your Windows DVD again. Since there shouldn't be any add-in boards or extra equipment to speak of, other than the motherboard's built-in components, you should be able to boot into your Windows DVD. Of course, it also should inform you that there is nowhere available to install Windows, but that's okay. At least that's progress. Once you can get the Windows installation disc to boot, you can add back hardware, one piece at a time, until you are able to install Windows. Add back the remaining RAM modules, and make sure it boots. Then add a single hard disk, and make sure it boots, etc. Once you have all of the RAM modules and hard disks attached again, I would stop with adding hardware until you can complete the Windows installation. Any graphics cards can be added after Windows has been installed.

You can download free memory testing utilities from the following sites:

Memtest86+: http://www.memtest.org/

Memtest86: http://www.memtest86.com/
 

bobthedestroyer

Reputable
Mar 11, 2014
9
0
4,510
Thanks for the answers I'll go through this process when I get up in the morning. I just put my old motherboard back in along with my old CPU and it booted up just fine. But as you mentioned that's likely due to the OS installation being on that motherboard.
 
You can't swap major components such as motherboards on a Windows installation without expecting hiccups. While there are certainly exceptions to this, as a rule of thumb, expect to reinstall Windows when you swap motherboards. The times you get away without, is usually when you are using the same CPU family and type, such as AMD to AMD, Intel to Intel, sticking with the same architecture such as x86 or x64, and when the supporting chips on the motherboard are in the same family. Once you change anything major without Windows having it's supporting software updated to match, you get what you're experiencing now.
 
Solution