- Jul 10, 2013
- 4
- 0
- 10,510
Update: SOLVED
I was getting BSOD is 0x74 with parameters 0x3, 0x2, 0xFFFFF880009A9710, 0xFFFFFFFFC000014C when trying to boot, even with command line only safe mode. I'm using an old nForce 680i mobo with a RAID 5 and a single drive that had Mint Linux on it. I had just pulled the Mint Linux drive and installed a second RAID 5 and was booting for the first time when the problem occurred and suspected GRUB had caused a big problem in my MBR somehow.
I found out that the NT Status code from the BSoD suspected the registry
0xC000014C
STATUS_REGISTRY_CORRUPT
{The Registry Is Corrupt} The structure of one of the files that contains registry data is corrupt; the image of the file in memory is corrupt; or the file could not be recovered because the alternate copy or log was absent or corrupt.
Registries don't get corrupted, they just don't. Teenagers screw them up and blame it on a virus on occasion, but registry problems in Windows are like Lupus on House. It's never Lupus. I pulled half my memory and presto, it boots fine.
All that is left is to determine if it is a bad memory module, just a bad connection, or if my mobo is dying. If it's the mobo, that is kind of sad; DDR2 ram is practically free, but the old performance mobos are price like they're collectors items.
I was getting BSOD is 0x74 with parameters 0x3, 0x2, 0xFFFFF880009A9710, 0xFFFFFFFFC000014C when trying to boot, even with command line only safe mode. I'm using an old nForce 680i mobo with a RAID 5 and a single drive that had Mint Linux on it. I had just pulled the Mint Linux drive and installed a second RAID 5 and was booting for the first time when the problem occurred and suspected GRUB had caused a big problem in my MBR somehow.
I found out that the NT Status code from the BSoD suspected the registry
0xC000014C
STATUS_REGISTRY_CORRUPT
{The Registry Is Corrupt} The structure of one of the files that contains registry data is corrupt; the image of the file in memory is corrupt; or the file could not be recovered because the alternate copy or log was absent or corrupt.
Registries don't get corrupted, they just don't. Teenagers screw them up and blame it on a virus on occasion, but registry problems in Windows are like Lupus on House. It's never Lupus. I pulled half my memory and presto, it boots fine.
All that is left is to determine if it is a bad memory module, just a bad connection, or if my mobo is dying. If it's the mobo, that is kind of sad; DDR2 ram is practically free, but the old performance mobos are price like they're collectors items.
Facebook
Twitter
Instagram