Hello; I just completed a mobo swap from an Intel 975X platform to an nVIDIA 780i SLI platform. I'm re-using the same Q9550, 8GB of RAM, and my dual SSD's. The only change is the mobo itself so that I can take advantage of PCIe v 2.0. When Win 7 boots up, I get the 0x7B error that typically indicates there is a "driver problem" of some sort. I have a feeling that it might be related to missing NVIDIA chipset drivers (I used Driver Sweeper and posted a message on their forum) but am not sure how you'd figure this out as to what is causing it. The self-fix-it feature doesn't seem to work and it's not the typical booting problem I've seen elsewhere. It does boot fine after my usual BIOS tweaks, and then crashes before the login screen appears. (Safe mode loads a bunch of drivers and then crashes too.) The full error message is: 0x7B (0xFFFFF880009A9928, 0xFFFFFFFFC0000034; two more 0x0's). I found the DriverStore in the System32 folder, but am not sure if this means Windows knows to look there after swapping out the new hardware. I don't have a 32-bit OS anyway, and there appears to be NVIDIA RAID drivers and a few others in there. The usual response on the net is to "reinstall windows", but figuring it out here should take much less time, and maybe I can fix BSOD errors in the future then. :) I checked the usual nt boot log .txt file; it's dated from August of last year and didn't have anything useful in it. Thanks!!!

Unfortunately, changing the motherboard normally requires a reinstall, and is just about guaranteed when you have changed the chipset.

I'm going to give myself until Saturday morning before I "give up' :) and reinstall Windows, but in the mean time I figured out a few things last night. - When I boot in safe mode, a bunch of drivers do load and it pauses on CLASSPNP.SYS for a moment before it crashes. Is this the last driver to display that it's loading (and therefore the cause) or does this mean the next driver is crashing? Can I look at or edit the list of drivers that are loading? I can run regedit fine but msconfig will not load. - CLASSPNP.SYS seems to be "OK", when I ran 'dir classpnp.sys /s' it showed up in two places and the file sizes were the same. I could copy them to a USB stick and run MD5SUM on them, but I doubt that's it. - In the mean time I am going to run MEMTEST86+ on that PC for awhile, I also doubt it's memory errors but this will at least insure that the system is stable.

On a 64-bit system the System32 folder is where all the 64-bit .DLL's and other software are located. The 32-bit support is in the SySWOW64 folder. Did you have your hard driver controller set in the MB BIOS to IDE/SATA on the old board? Or, was it set to AHCI? Or, did you have a RAID configuration? If you 0x0000007B fault is related to lack of nVidia system drivers, it will be virtually impossible to fix it in your current installation. The same applies even if it's strictly a hard drive controller driver.Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

I found the 'FileRepository' in the System32\DriverStore folder. That seems almost backwards, but there's quite a bit of nv_ and nvda video and raid stuff in there. The old Intel board had the controller set to AHCI. The new board doesn't have AHCI as an option but has either IDE or RAID. (This is a much newer board too; it's odd that ACHI isn't an option.) I've tried both IDE/RAID and get the same result. Windows does seem to partially boot up fine (my estimate is it gets half-way through the colored dots where they start coming together and then the BSOD flash, reboot). I'm going to pop in the install DVD next to see if there's anything on there that makes sense. I'm copying my internal SSD's to a spare HD right now "just in case". That may take another hour or so. EDIT: Sorry, I forgot to mention that Memtest86+ ran for almost 2 hours. No problems.

I just updated the BIOS to the latest on the manufacturer's web site. No changes like AHCI suddenly appearing as a new option, but Windows should be happier once it works again right? :)

The admin over at Driver Sweeper believes that the program would only have removed drivers that I had installed and not the existing system drivers, which I tend to agree with because I am finding stuff in DriverStore. If you're curious, I have my thread here: http://forum.phyxion.net/viewtopic.php?id=13 I found another article at my SSD manufacturer's web site (OCZ) which states that AHCI is enabled in the registry at: HKLM\SYSTEM\CurrentControlSet\services\msahci when the key "Start" is set to 0 (AHCI enabled) or 3 (default/disabled). I thought about disabling AHCI in the registry to see what it does, but when I 'regedit' under the system recovery mode, I get the registry of the temporary OS (X:) and not my C: drive. So, I think I'm left with two ideas here. - Disable AHCI in the registry, although I can't seem to edit my C: registry. - Hope that someone else without an NVIDIA chipset can run Driver Sweeper for me and try removing the NVIDIA chipset drivers. If the admin is right, then Driver Sweeper will do nothing. Thanks for reading this, even if I do end up spending my weekend on another Windows install! :D

I ended up "jumping the gun" and started the reinstall last night because I needed to get my main PC back up by Monday. I mentioned on the Driver Sweeper forum, even if I could find the right driver, there's no guarantee that it would be a stable system in the future with different memory, audio, and network drivers. I must have been just lucky with a similar chipset swap before under XP. My best guess is that it is AHCI driver related. CrystalDiskInfo shows that under my current "RAID" reinstall, my SSDs still have TRIM and Windows still reports that TRIM is enabled, but AHCI is an Intel standard. So it makes sense that it's not available in the BIOS under the NVIDIA chipset. As a strange bonus, it seems that more things are working properly for this Win 7 reinstall. No need to reply on this thread unless someone does find info on replacing storage drivers during a BSOD 0x7B event; I will keep that info for future use.