Best way to test cpu/motherboard

[stikkk]

I recently got my hands on a 3930k and a sabertooth motherboard with it. The problem is when i get it to launch on all the same components as my working pc, it launches all the way up to the windows loading and BSODs with different errors every time. ex0xc000021a , 0xc000007b , CRITICAL PROCESS HAD DIED. and a few others i didn't get to list.

Eventually though it corrupts the hard drive, so that on boot it then starts to do a windows repair instead, and still continues to bsod.

Basically i just want to know if theres any decent way to test either component, without having another cpu/motherboard in hand. And if there is no other way, will it pose a threat to other peoples components if i do try running them with my faulty ones? Thank you for reading!

 

[Darkbreeze]

Have you bothered to try doing a clean install of the OS? It is rare that two different motherboards, especially if they are not of the same generation and chipset, will boot using the same OS without any issues. CPU chipset drivers, storage controller drivers, other misc supporting files are generally different between chipsets and controllers so although it might work fine with one, it's a bigtime crapshoot with one that is different.

I'd try the clean install first and then go from there.

Windows 10 Clean install tutorial


Probably also a good idea to make sure you have the latest bios version installed. Do not update to versions newer than the end of December, but whatever version is the latest prior to December should likely be updated to if one is available.

If it is on a relatively new version, then pulling the cmos battery to reset the bios is a good idea prior to attempting to boot a new configuration or perform a clean install. You may have to go into the bios and reconfigure the default settings before moving forward after resetting though. That is normal.

 

[stikkk]

Have you bothered to try doing a clean install of the OS? It is rare that two different motherboards, especially if they are not of the same generation and chipset, will boot using the same OS without any issues. CPU chipset drivers, storage controller drivers, other misc supporting files are generally different between chipsets and controllers so although it might work fine with one, it's a bigtime crapshoot with one that is different.

I'd try the clean install first and then go from there.

Windows 10 Clean install tutorial



Probably also a good idea to make sure you have the latest bios version installed. Do not update to versions newer than the end of December, but whatever version is the latest prior to December should likely be updated to if one is available.

If it is on a relatively new version, then pulling the cmos battery to reset the bios is a good idea prior to attempting to boot a new configuration or perform a clean install. You may have to go into the bios and reconfigure the default settings before moving forward after resetting though. That is normal.

yeah i did reinstall the os. even when trying to install using the motherboard with a usb does the similar bsod errors

 

[stikkk]

sorry i also wanted to say that i have reinstalled to a newer version of bios but i have not tryed the cmos reset, but i do not believe that is the issue i can still try it sometime soon.

 

[Darkbreeze]

Re-install is NOT the same as CLEAN install. Neither is Reset, Repair, Restore, Update to new version or Install but leave files intact. Clean install means you will delete ALL of the existing partitions, including any existing boot partitions. This is where the main difference is. ALL other drives should be disconnected from the system, especially if THEY have ever had Windows installed on them too.

If you HAVE done a clean install, deleting all the existing partitions from the OS drive, with all other drives disconnected during the installation, AND with an accompanying CMOS clear, then I'd agree that is not likely the issue. If you have not, then you should attempt to do so if possible.

If you have, then I'd suggest the next step might be running a memory test test using Memtest86 or Memtest86+. Run at least two and preferably five passes. This will take a long while to complete.

http://www.techfleece.com/2013/07/01/how-to-test-your-ram-sticks-using-memtest86/

 

[stikkk]

Every other component of this system works fine in my other motherboard/cpu.

I tried running it last night and i get the error CRYPTO LIBRARY INTERNAL ERROR. another is SYSTEM THREAD EXCEPTION NOT HANDLED. as well as the other bsods previously stated.

So the issue is definitely the motherboard or the ram. I can't even launch into windows at all, it just gets the the 2d windows logo and loading symbol and eventually gives me one of the bsods previously stated. I can launch into bios and temps and everything else seems normal through that.

 

[Darkbreeze]

Memtest doesn't need the Windows environment. It is it's own environment neither needing Windows, nor DOS, nor Linux in order to run. If you cannot run Memtest86 or Memtest86+, then I'd agree that there is clearly a hardware problem.

If you have multiple memory modules, perhaps try using only one or the other, or different RAM altogether if you have some other memory you can test with. Maybe borrow for testing. Otherwise I suspect that you are down to simply guessing which is the problem HOWEVER it is far more common for a motherboard that has been in use to start showing signs of failure over time or suddenly than it is for memory. Most memory will last a long time unless something else damages it or something was wrong from the start but simply went unnoticed or was attributed to other things. Memory issues typically occur immediately or soon after they are put into use, but obviously other factors like a problem with the motherboard, PSU or CPU could cause failures of the memory in addition to the primary, root issue with the other hardware device.

Perhaps you have another motherboard or know somebody with one, that uses the same type memory.

What are your full system specs including model numbers?