BSOD after login, error 0x00000051 REGISTRY_ERROR

[pupfuzz]

Hi,

My machine was running smoothly until recently it became infected with adware. I tried to remove the uninvited software through Uninstall Programs in control panel, and also by using Malwarebytes to quarantine anything it found objectionable. It then seemed to work fine after all of this and booted up OK.

I recently also tried to upgrade the nVidia driver, and there was an error about not being able to update a file in use, so the install failed. I rebooted the computer, re-ran the nVidia installer, and that also completed without any further errors. The computer also rebooted OK after that.

However days later, now I get a BSOD after login. Windows boots fine up to the point where I log in with my password. Once I log in, BSOD occurs. If I wait for awhile before logging in (all drivers have loaded), then the BSOD is immediate after entering my login password. On the other hand, if I log in immediately as soon as the login screen appears, I can see my desktop and use the menus etc for 10-20 seconds before BSOD occurs (I'm assuming that's when all drivers have completed loading).

If I boot in safe mode, it is stable and no crash occurs. I also ran msconfig and disabled all programs in startup. No difference.

At first, the BSOD error was "BAD_POOL_HEADER". I tried uninstalling and reinstalling the nvidia driver, and now the BSOD error has changed to "REGISTRY_ERROR".

If anyone has any suggestions on how to resolve my problem, I would greatly appreciate it.

Thanks!

 

[Hexagon12]

Your computer had 0x51, 0x3B, 0x19, 0x24 and 0x50 BSOD's.

Can your computer boot into safe mode?
If it can, go to start menu, and search cmd. Then right-click and select Run as Administrator. This will open elevated command prompt. From there, type sfc /scannow. This will open Windows Resource Protector. (in cmd mode). It will scan for corrupted system files. If it says that the files were fixed, then restart without safe mode. If it shows a BSOD again, then you might reinstall Windows.

 

[Arc]

Hi pupfuzz.

For a stop 0x51, there laways remains a chance of a security issue, as well as registry corruption. Plus, hardware failure is also a frequent cause of this bugcheck.

Run SFC /SCANNOW Command - System File Checker

Scan the system for possible virus infection with the following programs only.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Stress test the CPU.
Hardware - Stress Test With Prime95

Let us know the results.