A random BSOD shows up sometimes on my VM when windows is running. please fix this issue.
ntoskrnl.exe causes this BSOD
guest is Windows 10 1803 x64
host is MacOS 10.13.5
Virtualbox version is 5.2.12
when a new update for Virtualbox is released, it does not fix this issue.
ntoskrnl.exe causes BSOD windows 10
-
- Posts: 31
- Joined: 25. Sep 2017, 23:07
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Windows
- Location: Kissimmee FL
- Contact:
-
- Volunteer
- Posts: 1631
- Joined: 25. May 2010, 23:48
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Assorted Linux, Windows Server 2012, DOS, Windows 10, BIOS/UEFI emulation
Re: ntoskrnl.exe causes BSOD windows 10
This is a user to user forum so isn't the right place to start demanding that people fix issues.Neptune BSC wrote:A random BSOD shows up sometimes on my VM when windows is running. please fix this issue.
You could create a new bug ticket but as you have a random (and therefore not reproducible) issue that probably isn't a VirtualBox issue and doesn't affect other users with the same combination then I doubt you will get very far. If you can find some way of provoking the failure on demand then you might get further. Reading Minimum information needed for assistance and posting a log file might be a good start.
-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.
Please don't ask me to do your homework for you, I have more than enough of my own things to do.
-
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: ntoskrnl.exe causes BSOD windows 10
Unless we see a VBox.log (ZIPPED) and the VM recipe (the .vbox file), you won't get too far, that's for sure. Especially with a problem that's 100% happening in the guest, and not in VirtualBox.
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.
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.
-
- Posts: 31
- Joined: 25. Sep 2017, 23:07
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Windows
- Location: Kissimmee FL
- Contact:
Re: ntoskrnl.exe causes BSOD windows 10
this is the log and the vbox file
- Attachments
-
- vbox.log.zip
- (33.87 KiB) Downloaded 125 times
-
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: ntoskrnl.exe causes BSOD windows 10
That was only the log file, but it's OK (for the moment). Your log look amazingly good, I don't see any problems with the configuration.
What's the BSOD that you're getting? It may not be related to VirtualBox at all. What were you doing at the moment that your VM BSODed?
What's the BSOD that you're getting? It may not be related to VirtualBox at all. What were you doing at the moment that your VM BSODed?
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.
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.
-
- Posts: 31
- Joined: 25. Sep 2017, 23:07
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Windows
- Location: Kissimmee FL
- Contact:
Re: ntoskrnl.exe causes BSOD windows 10
I am getting 0x00000109 in the blue screen randomly on my VM.
-
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: ntoskrnl.exe causes BSOD windows 10
I had more questions that that...
Again, this is *not* necessarily a VirtualBox issue. Treat it as such...
Again, this is *not* necessarily a VirtualBox issue. Treat it as such...
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.
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.
-
- Posts: 31
- Joined: 25. Sep 2017, 23:07
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Windows
- Location: Kissimmee FL
- Contact:
Re: ntoskrnl.exe causes BSOD windows 10
how can I attach the vbox file.
-
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: ntoskrnl.exe causes BSOD windows 10
I should have checked your post history, mea culpa...
This is a duplicate of your other thread "Freezing every time a BSOD appears on Windows 10 guest (#17590)".
This is a duplicate of your other thread "Freezing every time a BSOD appears on Windows 10 guest (#17590)".
- You were repeatedly asked to provide information.
- You were repeatedly told to look at it as a native error, not a VirtualBox error.
- You opened ticket #17590
- You opened another, duplicate ticket #17736
Continue the discussion in viewtopic.php?f=2&t=87676Opening new threads and new tickets without providing any information when asked, is not going to have a happy ending. In the best case scenario, you will be completely ignored, because there's nothing else that can be done about your issue...
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.
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.