Searching for the highlighted term in the forums should give you some hits on other posts that detail how to fix it.
-Andy.
My crystal ball is currently broken. If you want assistance you are going to have to give me all of the necessary information.
Please don't ask me to do your homework for you, I have more than enough of my own things to do.
That's right, a hardening problem in the NVidia drivers.
Read really carefully the following FAQ: Diagnosing VirtualBox Hardening Issues to understand the reason why the NVidia drivers are being rejected. And when they're rejected, that means no 3D acceleration, that means "software rendering mode"...
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
socratis wrote:That's right, a hardening problem in the NVidia drivers.
Read really carefully the following FAQ: Diagnosing VirtualBox Hardening Issues to understand the reason why the NVidia drivers are being rejected. And when they're rejected, that means no 3D acceleration, that means "software rendering mode"...
@socratis I followed the above recommendations but my VM continues to open only with a single monitor. And I still can not use 3D acceleration, which causes 'black screen'. I am attaching the VBoxHardening.zip file. The 3D acceleration problem is old for me, but failing to open more on two monitors is a new problem. Ever seen that happen?
@leonardopereira,
One of the reasons that we make the FAQs is so that the users will read and learn from them. So, for example the FAQ talks about the first thing to check being the "ExitCode", and in your case:
which is a GoodThing™, because it seems that you don't have a hardening error. Other keywords that we search for are "rejected", "adversaries" and "error". You seem to be doing fine on all of these. So, it seems that the hardening error in your Nvidia drivers is no more.
Which means that we need to see a complete VBox.log, from a complete VM run, where the problem occurs. Try with a single monitor first:
Start the VM from cold-boot (not from a paused or saved state) / Observe problem / Shutdown the VM (force close it if you have to).
With the VM completely shut down (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".
Save only the first "VBox.log", ZIP it and attach it to your response.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
And just to anticipate another potential misunderstanding: 2D acceleration is not enabled either, but that's fine since it only applies to Windows guests.
Parts of the host Nvidia drivers are being rejected because of a hardening error. Without them the 3D acceleration isn't going to work and you probably end up in software rendering mode. You should try updating the drivers to see if the latest ones are signed properly and to make sure that the Windows certificate database gets updated correctly.
-Andy.
My crystal ball is currently broken. If you want assistance you are going to have to give me all of the necessary information.
Please don't ask me to do your homework for you, I have more than enough of my own things to do.
leonardopereira wrote:Sorry... I'll send the log again
@leonardopereira
As I've already explained, you don't have to waste your time sending the logs and then waiting for an answer. You had this exact same error, and Andy was kind enough to provide you with pointers, "what to look for".
So, you should start looking at the VBox.log yourself for these "strings". If you find them, that's not a good sign. And if specific advice is given (install fresh GPU drivers), I think it would be wise if you followed such advice. I didn't see any attempt to install fresh drivers, or downgrade to an older version, until the "supR3Hardened" errors go away. Did you try that?
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
I'm now assuming that the only reason we got a hardening log with no hardening errors in it, was that it too was captured from a session in which 3D acceleration was disabled. All very misleading.
So to reiterate the likely solution:
Update your host's graphics drivers.
Enable 3D acceleration in the guest and launch the VM.
If you continue to have problems then look at the logs: if you continue to see the aforementioned hardening errors then drivers still include unsigned modules, so look for yet another version. Happily NVidia, while being the most persistent offender in the "forgetting to sign their DLLs" stakes, also IMHO have the easiest online database of downloadable driver versions.
My English is not very good so I have some difficulty understanding what you say. I sent the LOG because I understood that you were requesting it, because you certainly know how to interpret it much better than I do.
So this is a problem with NVidia drivers. I'll try to update them and then I'll give you a return, okay?
leonardopereira wrote:I sent the LOG because I understood that you were requesting it, because you certainly know how to interpret it much better than I do.
Sure... sure... I just offered you a way to "speed" things up
leonardopereira wrote:I'll try to update them and then I'll give you a return, okay?
Yes. But remember one thing; you may have to downgrade sometimes. The latest does not mean the best...
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
@socratis Should this procedure also solve the problem of the two monitors or are they different problems? Is that in VBox 5.x I used two monitors without problems.
Why you should worry with getting it working first, and then we can deal with the 2nd monitor. Shall we?
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.