Server 2008 R2 wont boot past classpnp.sys after hardware change
I am not able to boot into Windows after changing hardware of my server.
- Gigabyte GA-G41MT-S2PT motherboard (socket LGA 775)
- Intel Quad Core 2.5Ghz CPU
- 2x Transcend 4Gb DDR 1333 Dimms
- Intel Round Lake LGA 1150 Motherboard
- Intel Core I5 4670 3.40Ghz 6MB Cache SKT 1150
- 2x CORSAIR 16GB DDR3, 1866MHZ
I am running Windows Server 2008 R2. I changed the motherboard, CPU and RAM, but then it goes into a reboot loop. If I try to run in safe mode, it stops at classpnp.sys and then restarts and suggests I run repair mode.
If I change to the old motherboard/CPU/RAM, then it boots into windows just fine. Change back to new hardware and again, won't boot into windows.
- I have tried to rename classpnp.sys to classpnp.old with no luck.
- Tried copying classpnp.sys from another computer to this one, but did not work
- Tried to use the x:\sources\recovery\StartRep.exe tool at command line, but "Startup repair could not detect a problem"
- I have tried all options for SATA settings in BIOS (there was no "compatibility" mode but I did try IDE) - none of the options work
- Tried "sfc /SCANNOW /OFFBOOTDIR=d:\ /OFFWINDIR=d:\windows" - no luck ("did not find any integrity violations")
- With old hardware, I did a full backup (bare metal). With new hardware installed I then did a complete restore. Same problem after restore.
- Ran "chkdsk c: /r" and no problems found
- Booted with F8 and selected the option "Disable automatic restart on system failure" and then I get the BSOD with stop error 0x0000007B
- Tried to boot in debug mode but it just restarts without going into the debug mode.
- Tried to remove one memory module at a time, as well as try completely different memory modules, still with no luck
- Booted with F8 and selected the option "Enable boot logging" but the ntbtlog.txt file is not created.
- In BIOS I disabled all on-board devices such as audio and USB (kept graphics enabled since I don't have a graphics card) - still same problem
From what I have read, this seems to be an issue with the hard drive or HDD controller. Only other thing I can think of is to return the motherboard and try a new one.
Anything else I can try?
Any help and guidance would be greatly appreciated!