Blue Screen of Death STOP 0x00000051

24/9/2013

Appreciate there are a lot of errors and possible causes associated with BSOD, however I thought I would share our latest error incase anyone else comes across it.

Symptoms: Occured on a Hyper-V Server 2008 R2 Virtual Machine with Server 2008 R2 OS.

When logging into the server via RDP or at the console, the above 'Blue Screen of Death' appears with error *** STOP: 0x00000051 (click to enlarge)

WinDbg on the dump file gave the following information: probably caused by ntkrnlmp.exe (nt !RtlStringFromGUID+4fb5 )
This was logged with Microsoft.

Cause:
From the Memory dump, it was apparent that System was in the process of syncing the current control set (control set 1) to last known good (control set 2). While doing so it detected inconsistency in \registry\machine\system\ControlSet002. This initiated the crash. (Basically a corruption in the registry)

Resolution:
Create a new LastKnownGood Configuration in the registry, which
can sync with Current Control set correctly. We should change ControlSet002 (currently LastKnownGood) to failed, and create a new ControlSet003(new LastKnownGood)

Steps to do this:
Boot failed server in Safe Mode. Open the registry HKEY_LOCAL_MACHINE\SYSTEM\Select
Change LastKnownGood to 3
Change Failed to 2

Reboot the server into normal mode and hopefully log in succesfully!

47 Comments

Ian

2/10/2013 11:51:45 am

Thank you! One of our virtual machines just crashed with this problem, and you're the first place I found with a simple solution!

Wx-yz Earl Rotch C. Gacus

12/5/2015 05:19:35 pm

Btw... how boot ur pc plsss help asap.... hehehe Newbie

Shoaib

14/1/2016 11:20:27 am

Thanks a lot for the nice tip :)

Jose

22/1/2016 09:16:58 pm

Excellent!!! Thanks for this! This saved us big time!

Chris Pallan

12/9/2016 03:46:24 pm

Thanks for this info...just happened to me for the first time on a VM running on esxi 6

Rameh

6/7/2017 07:25:59 pm

thank you v much that worked after exhausting everything ... that was on User End machine running win 7x64...

Alex Heer

2/10/2013 01:19:34 pm

Great, glad it helped! Alex

Andy L

5/11/2015 07:12:00 pm

Just adding my thanks to you (and Google for getting me here). Had an important VM just up and start continually crash for no reason, nothing changed in months, no clue where to start but your fix got it back up in minutes.

jaa

12/11/2013 04:57:16 am

I like to run what is in the supplement because they do not know how to ... please help

jaa

12/11/2013 04:59:11 am

how to to run what is in the supplement because they do not know how to ... please help poprawiam sie (jestem z polski nie umiem pisac po angielsku)

Dean

1/5/2014 08:06:46 am

I have a windows server 2008 R2 sitting inside a Hyper-V environment running on a Windows server 2008 R2 server and when i log in i get the 0x0000051 error and all my parameters basically match yours...you might have just saved me a load of work tonight. If you have, me love you long time!

Alex Heer

1/5/2014 02:16:15 pm

Dean, hope it works for you. Let me know how you get on.

Dean

8/5/2014 04:42:55 pm

Perfect, absolutely perfect. I used remote registry to edit the registry of the server in question, changed the relevant registry entries to what you had above. I rebooted (as i wanted to back up the VM just in case it was dead after the above change) then restarted the HyperV, logged into the VM......and all i know about the problem is a message from windows helpfully telling me "it recovered from a blue screen!" IT RECOVERED?!?! er no, alex heer's advice implemented by Dean is what recovered it! ;)

I am very appreciative of this page, and you have saved me a lot of work. :D

I am off to click an advert of two...if you have any!

Dean

Dean Bailey

11/6/2014 01:32:33 am

Thank you so much. This saved me a load of time.

Mirko

16/6/2014 11:23:07 am

I had the same issue since the recent Windows Update got installed on our server this weekend. Your solution worked just great. Thank you! That saved my day today.

OverDrive

17/6/2014 10:57:59 am

I had the same issue - with the windows update recently - this fixed my problem too. Hyper-V VM, Server 2008 R2.

Mike Russo

19/6/2014 03:08:48 pm

Absolutely stellar post. Thanks so much. We all owe you a pint!

Tobi

26/6/2014 04:18:48 am

Thanks for saved my ass !!!!!!

Dean

26/6/2014 04:19:59 am

Looks like microsoft have a bug they need to fix.

Sunil

22/7/2014 03:15:12 pm

Neat info.. Thanks a lot.. Saved my ass to.

abdulrahman

25/7/2014 11:21:42 pm

wow...wow...wow I been trying to solve this problem for 1 month then I see your solution, first thought like any other solution will not work with me but it did and I really appreciate your work

thank you very much you are the best man

y
in

james

10/9/2014 09:42:05 am

Same issue with Server 2008 R2 VM. Your fix worked perfectly. If I could hug you I would. Thanks.

Sly link

11/9/2014 06:16:03 am

Thank YOU!!!!!!

SAPi

27/12/2014 05:47:23 am

Thanks Dude ! To fix this i had to keep restoring my old VM which was **** annoying but NoW i dont have to anymore Thanks to you For the FiX :) Thumbs Up Dude!

martyn

23/1/2015 08:54:08 am

This worked and got everything up and running but everything seems to be running alot slower for me now.

Luis link

23/2/2015 07:08:34 pm

It worked like a charm. Thank you very much.

cyrill

26/2/2015 09:06:15 am

thank you! after hours of finding the reason, I have finally restored exchange)) )

greatskott

27/5/2015 06:24:37 pm

This worked great for a physical server with the same symptoms! Thanks!

Brandon Jackson

22/10/2015 09:25:44 pm

Wanted to chime in and say thank you. This resolved the issue for me on a windows 7 pro VM running in parallels on mac osx (my client).

Wes

3/11/2015 05:34:11 pm

Thanks very much for this, resolved the issue for me on a 2008 R2 VM on a 2012 R2 Hyper-V host.

20/1/2016 05:15:08 am

This solution was simple and an absolute life saver. After working on a very very similiar problem, where the moment I logged in, it would crash and give me that stupid 0x00000051 error, for 40+ hours straight, 7 hours with a senior Microsoft Technician and another 5 hours with a Dell technician, to have this problem solved by the change of two numbers in the registry blew my mind! Thank you so much for taking the time to post the solution to this horrible, time wasting error that the people who wrote the code don't know how to fix! Keep up the good work! I hope abundance and happiness visits you often.

Dean link

20/6/2016 08:10:26 am

Have microsoft not fixed this bug yet?

Brian Smithson

4/2/2016 08:43:27 pm

Ran across this blog post after running some updates on a 2k8R2 VM and getting the BSOD. Very odd, but yours was the fix!

Very grateful

Michel

20/6/2016 06:44:37 am

Thanks mate. You did it! It is working again...

Chris link

7/7/2016 05:10:29 pm

Thanks so much for this post! Your solution worked for me on a physical 2008 r2 install. Any idea what the underlying cause of this problem is, or how to prevent it from happening again in the future?

yunus

24/12/2016 06:50:48 am

Thank you so much

THX

22/1/2017 10:26:09 pm

Thank you very much from France :-)

paul

30/3/2017 09:18:23 pm

you are the man!

Frits

6/4/2017 01:44:01 pm

Many thanks! Your instructions also worked on Win7(64) Home.

Jaxon

8/8/2017 02:25:15 pm

Thanx. God bless you, worked perfectly

Obelix

19/11/2017 07:54:18 pm

Thanks a lot!!

Jan

23/1/2018 07:11:04 am

Thanks! This fixed it

Kinks

1/3/2018 09:53:40 pm

Can't believe, it works!
I had an horrible day of work because of this BSoD and thanks to you it's solved!
I deeply thank you very very very very very much!!!

Jack

11/4/2018 03:45:04 pm

Great! It's worked for me on a Physical computer in Windows 7. I can't believe it...

Thank you very much!

Mathew

13/4/2018 12:08:24 pm

It worked well ! Thank you.

devnullius

15/5/2018 04:48:55 pm

2018 - still relevant on Windows 2016 Hyper-V with Windows 7 client. My problems started after moving it to a new disk & folder. I had to reset permissions with

icacls "C:\Virtual HDD\Windows 7 x64*.*" /grant "NT VIRTUAL MACHINE\SSID":(F)

Safe mode worked, normal mode would BSOD. So thank you here ♥

Makulet

16/7/2018 03:40:19 am

Such a genius!!!! Thank you so much! ❤️

Blue Screen of Death STOP 0x00000051

Leave a Reply.

Author

Archives

Categories