axe0 Administrator, BSOD Academy Instructor, Security Analyst Staff member Joined May 21, 2015 Posts 3,307 Location Holland Dec 29, 2021 #21 Just for info, the latest memory dump file is corrupt, 7zip and Windows Explorer cannot access it. That is what zbook means.
Just for info, the latest memory dump file is corrupt, 7zip and Windows Explorer cannot access it. That is what zbook means.
P pacofernandez58 Member Joined Dec 23, 2021 Posts 12 Dec 29, 2021 #22 I updated the zip file in Google Drive, now the link in post #19 should point to a non-corrupted file. Let me know if you still aren't able to open it.
I updated the zip file in Google Drive, now the link in post #19 should point to a non-corrupted file. Let me know if you still aren't able to open it.
x BlueRobot Administrator Staff member Joined May 7, 2013 Posts 10,188 Location %systemroot% Dec 30, 2021 #23 I have an idea which might possibly work, could you please boot into your BIOS and then disable Hardware Virtualisation? How to enable or disable Hardware Virtualization in Windows 11/10
I have an idea which might possibly work, could you please boot into your BIOS and then disable Hardware Virtualisation? How to enable or disable Hardware Virtualization in Windows 11/10
P pacofernandez58 Member Joined Dec 23, 2021 Posts 12 Dec 30, 2021 #24 x BlueRobot said: I have an idea which might possibly work, could you please boot into your BIOS and then disable Hardware Virtualisation? How to enable or disable Hardware Virtualization in Windows 11/10 Click to expand... Done, it is now disabled. However, I would like this to be a temporary solution, because as I said in the previous posts, WSL and virtual machines are two of the tools I use almost every day, and they don't work if the hardware virtualization is disabled. So, in case this is the cause of the problems, what should I do? Fill another RMA? Thanks!
x BlueRobot said: I have an idea which might possibly work, could you please boot into your BIOS and then disable Hardware Virtualisation? How to enable or disable Hardware Virtualization in Windows 11/10 Click to expand... Done, it is now disabled. However, I would like this to be a temporary solution, because as I said in the previous posts, WSL and virtual machines are two of the tools I use almost every day, and they don't work if the hardware virtualization is disabled. So, in case this is the cause of the problems, what should I do? Fill another RMA? Thanks!
x BlueRobot Administrator Staff member Joined May 7, 2013 Posts 10,188 Location %systemroot% Dec 30, 2021 #25 I would send it back if the system doesn't crash with it disabled. If we can confirm that it is the issue then it will give you more leverage if you file an RMA with them.
I would send it back if the system doesn't crash with it disabled. If we can confirm that it is the issue then it will give you more leverage if you file an RMA with them.
P pacofernandez58 Member Joined Dec 23, 2021 Posts 12 Jan 11, 2022 #26 Hey guys! So it's been almost two weeks since I disabled hardware virtualization as @x BlueRobot suggested, and since then I haven't got anymore BSODs. I researched a bit and it seems there are some problems between WSL and Ryzen processors (Can't boot after WSL 2 Install · Issue #4784 · microsoft/WSL). Some people said that disabling Memory Integrity protection would resolve the issue, and some other that changing the UMA buffer size would also work. I tried the second one, re-enabling Hardware Virtualization and decreasing UMA buffer size from 2G to 1G, and still no BSODs, so I think this issue can be definitely marked as solved. I wanna thank you all for all your help :) I wish I had the same knowledges as you about BSODs since I find it a very interesting topic. At the moment I don't have enough time, but maybe in the future I'll take a chance and try to enroll in your BSOD Academy. Thanks again!
Hey guys! So it's been almost two weeks since I disabled hardware virtualization as @x BlueRobot suggested, and since then I haven't got anymore BSODs. I researched a bit and it seems there are some problems between WSL and Ryzen processors (Can't boot after WSL 2 Install · Issue #4784 · microsoft/WSL). Some people said that disabling Memory Integrity protection would resolve the issue, and some other that changing the UMA buffer size would also work. I tried the second one, re-enabling Hardware Virtualization and decreasing UMA buffer size from 2G to 1G, and still no BSODs, so I think this issue can be definitely marked as solved. I wanna thank you all for all your help :) I wish I had the same knowledges as you about BSODs since I find it a very interesting topic. At the moment I don't have enough time, but maybe in the future I'll take a chance and try to enroll in your BSOD Academy. Thanks again!
x BlueRobot Administrator Staff member Joined May 7, 2013 Posts 10,188 Location %systemroot% Jan 11, 2022 #27 Awesome! Thank you for telling us the outcome, hopefully you won't have any more issues.