BSOD's After Hardware Upgrade

anthonyjr2

Distinguished
Nov 11, 2011
31
0
18,530
I recently upgraded my PC's motherboard and processor. Before this the computer had almost no problems, and certainly nothing along the lines of BSOD's. I realize it may be a driver issue or a hardware issue, but I don't know what to do at this point.

When I first finished installing the new hardware, the first thing I noticed was a BSOD right after POST. I changed my BIOS setting from AHCI mode to IDE mode and that seemed to resolve the issue. Secondly, I noticed a very long delay between POST and the Windows startup screen which was not happening before the upgrade. After logging in, drivers began installing, mostly from the internet, for most of my PC components. After a few reboots, I then installed the driver disk that came with my motherboard just in case. Once everything seemed to be set up, I started getting BSOD's at seemingly random intervals with no identifiable cause. Some of the messages were:

PAGE_FAULT_IN_NONPAGED_AREA
IRQL_NOT_LESS_OR_EQUAL
SYSTEM_SERVICE_EXCEPTION
MEMORY_MANAGEMENT
PROCESS_HAS_LOCKED_PAGES

Most of these had ntoskrnl.exe listed as the driver at fault which is obviously unhelpful. I tried running Driver Verifier to see if it would identify the problem, and it faulted with the driver "mcdbus.sys" which corresponded to a MagicISO driver, which I then uninstalled. However the random BSOD's did not go away. Driver Verifier did not pick up anything else.

Here are my specs, including the new motherboard and CPU:

Gigabyte Z87-D3HP
Intel Core i5-4570 @ 3.20 GHz
Gigabyte nVidia GTX 560Ti
12GB RAM (8GB Corsair & 4GB ADATA)

If anyone would like, I can zip up a few of the minidumps and post them here if it would help out my issue.

At this point I don't know what to do or what is causing the problems, hardware or software. I could really use some help on this. Thanks in advance!
 
Solution
Yes you have to re-install Windows after changing the motherboard, ask any Windows tech.

Your hardware has changed, Windows Setup knows nothing about it.
Hence, you have to run Windows Setup again so it can familiarise itself with the new motherboard.
Setup also has to create a new Product ID in the Registry as the existing one is invalid.
This can only be created during the Windows Setup phase.

If you have important data on the system drive, I'm surprised you haven't already got it backed up (what if the hard drive fails?).

anthonyjr2

Distinguished
Nov 11, 2011
31
0
18,530


I did not. Why is that a definite must? I don't exactly have a way to backup my 2TB hard drive at the moment.
 
Yes you have to re-install Windows after changing the motherboard, ask any Windows tech.

Your hardware has changed, Windows Setup knows nothing about it.
Hence, you have to run Windows Setup again so it can familiarise itself with the new motherboard.
Setup also has to create a new Product ID in the Registry as the existing one is invalid.
This can only be created during the Windows Setup phase.

If you have important data on the system drive, I'm surprised you haven't already got it backed up (what if the hard drive fails?).
 
Solution

anthonyjr2

Distinguished
Nov 11, 2011
31
0
18,530
I have my documents backed up for the most part, however there is around 600gb of other information that I have no place to put at the moment. Is there any other way to go about this without a reinstallation? Even a temporary solution.
 
As I previously said, re-installation of Windows is essential after fitting a new motherboard, so you'll have to buy a backup device (eg external hard drive). I'm surprised you left yourself so vulnerable to data-loss anyway. All important data should be backed up as a matter of common sense all the time, not just when you are faced with a problem.

You never considered what would happen to that data when the hard drive fails? (as it surely will one day).
 

anthonyjr2

Distinguished
Nov 11, 2011
31
0
18,530


Not really. I've never had much of a problem with storage. But alright I guess I'll have to reinstall, thanks for the help.
 

anthonyjr2

Distinguished
Nov 11, 2011
31
0
18,530
UPDATE: I found my actual problem. My BIOS was two updates behind because the "auto-update" utility didn't actually grab the latest update. I was on F4 when the latest was F6. Apparently F6 supports Intel 4th-gen processors which is what I have, so that's probably why I had issues.