BSOD on start, Startup Repair: Unknown Bugcheck: Bugcheck 3d

Clonkex, first let me sy that even if you wer able to get it to boot into Windows, if the CPU is not supporeted by yjr motherboard, it will never run correcyly. In ome cases it is the internal arcitecture of the way the CPU works that the board has to support. That being said, if your CPU is not supported by your board, it is surprising it will boot under any circumstances. Also, If you have virus problems on your other drive, cloning it would slso transfer the virus. That plus the fact that you can get rid of a virus, but I know of almost no way to repair the filed thr virus damaged.

To try to resolve some of those problems, I would first update your bios from MSI's website. However we need to get you more stable before flashing the bios. If you BSOD during a bios update, it could brick the whole board. So, while you can still boot into windows, please run sfc/ scannow from an elevated comand prompt (click start, type cmd in the search box, right click the entry that appears and select 'run as administrator). In the window that appears after giving it admin permission you can copy/paste this sfc /scannow and press enter. (if you decide to type in the command, please notice the space between sfc and the /) If it runs and finds errors, it will attempt to correct them. When it completes reboot. Now run it again and if errors are found reboot. You may have to do this several times for it to work completely (no more than 4, I would think). What we want is for it to run and report no integrity violations were found. What you are running is the system file checker. It will check only system files and attempt to repair any damaged or corrupted files.

I would also like you to post a sreenshot of Disk management. (Disk Management - Post a Screen Capture Image) In case you don't know, here is how to post a screenshot on Seven Forums Screenshots and Files - Upload and Post in Seven Forums

I would also like you to run the utility Golden requested inthe second post and upload the files wit your next post.

This next one you are not going to like. As with most hardware tests, it will take a considerable time to run. Please run memtest86 for a minimum of 8 Passes. 8 passes is important.. Each pass is a slightly different set of 9 or 10 tests. Each pass tests a different part of the ram, so it takes 8 complete passes to run a complete test. Having said that, if you get an error anytime during the tests, stop the tests by pushing the escape key. Any error is a failure, no reason to keep running it.

If you have any questions, feel free to ask away. We do not mind answering questions or giving further instructions on what we have asked.

If at any time your computer fails to boot, disconnect at least 1 cable from every hard drive except the one with windows on it and run startup repair again up to 3 times with reboot attempts between each time you run it.

EDIT: while you are at the MSI web site, see if you can update any of the other drivers they have listed. Particularly the chipset driver and sata drivers.

Clonkex, I detect some resentment in your response to some of my suggestions. I came here to try to help. If you would prefer, I will be more than happy to find someone else to help you. I suggested certain tests in order to get a direction on which hardware may be the issue. The simple act of having a BSOD can cause corrupted system files. A good percentage of the hardware issues we see here are caused by ram problems or ram incompatibilities with certain motherboards. If you don't already have it, a good suggestion may be to install CPUz and post screenshots of the SPD tab for each slot that has ram installed and the Memory tab.Also, the next time you go to bios check the values of the +12V, +5V and the +3.3V. ATX standards are +/- 5%. That will show what your PSU is putting out at idle although it won't show what it puts out under stress. Cupid Hardware Monitor will show those values, but it is software and not 100% reliable. Also, I was hoping that the tests Golden requested would show from the dump files what crashed and give us an indication of where the problem may lie.

Clonkex, don't worry about the other stuff. I'm not that easily offended. It is easy to be taken wrong on these computers. Gestures and facial expressions are underrated.

Again, it is software and I don't really trust all readings, but it is what we have. I really see nothing that stand out. The +12V and the +3.3V are on the very high edge of being within ATX standards but they are within standards. I see no temp problems either. The ram seems to be fine although personally I would make sure and set the dimm voltage in bios by hand to 1.8V. CPUZ is the one piece of software I do trust.

I do notice you installed without the 100MB partition, which I do also. The 'D' drive is almost completely full and has 9GB of space to the left of it unallocated. You can regain that space if you want to, but Disk Management can't do it. We'll tell you how if you want to. You can stop, start or make delayed startup on any service by holding the windows key down and pushing the R key to get a run box. Type services.msc in the run box and hit enter. Right click the service and select properties. In the properties of any service you can set it how you want to. Just be sure you know which ones to set and which to leave alone. I would run windows update and install updates. IN Windows Update in the left hand column, click change settings and set the drop down box to check for updates but let me decide what to install. It will cause you some grief, but you will know what you are installing. I install all updates for the OS but not for the hardware until I have checked it myself, by going to the motherboard manufacturer's site or the hardware manufacturer's site to see what the most recent WHQL driver is. You mentioned the Chipset driver. To me, that is the most important driver and make sure you have the latest version installed.

Just to be certain, I would check the hard drive for errors by running Seatools for DOS and chkdsk. That will check the disk for any errors. Another possibility when the bios hands off to the disk during bootup, is hard drive errors. Besides, any time I buy a new disk, I always run those first thing to make sure. you may be surprised at how many come new with errors. But, your repair shop guy was right also. When the drive starts, that's when Windows starts loading drivers.