Displaying 2 results from an estimated 2 matches for "efvlf2m".
Did you mean:
efvlf2ms
2015 Jul 25
0
Re: Migrate Win2k3 to KVM
...JGjKvmKnGWz1ZgCvo75uzGoiuGmKDkIF6FJb3/+
+8nnFdYjd5b2NhryhIawxeZphAyMfIgt6Le1mFGgg2EBOD6xhFWv3WOLGSV775uu
29Q0+tPTE1+o8Ed1mtgaS1mRB/huPCMOMJtJS4sZ70wRdCz6i1pcYhQgXr44O1lz
JzZxhnl79Zz0v/rlRIX2EF7t41rvIf//wgoA6jIhI7B15eGPlfGUaU2tMGGf8yGu
yTcmuPKzfR1g8GJzYpNT8wFawEFOe3x2dRjA2kUdvUR1FziNdrUNxwpVOOBuOlX5
efVLf2ms+OOyIOnbSyzMOXL55K7a4HnHacCEjEvzvt60m4ZM7hcRGEE5L8Hi9LGP
z2eDwRtefK6bL4Pg3hjkpBtsG42Pr6y5904MRGtLqwvmtWlTF+txafwahXQALpSi
5QEdWTWMQdI/LBZ/1LWz
=tFUM
-----END PGP SIGNATURE-----
2015 Jul 11
8
Re: Migrate Win2k3 to KVM
Hi,
The error line is:
*** STOP: 0x0000007B (0xF789AA94, 0xC0000034, 0x00000000, 0x00000000)
Nothing more! (Of course there are some inrelevant text line about chkdsk,
etc.)
> Basically, what's required is the "STOP:" line + the image where it
> fails (so, the line below). Image being likely to be NTOSKRNL.EXE
>
Nothing about NTOSKRNL.EXE on the blue screen!
> >