Error System Trace 150 (0x96): How to Fix it

This issue can affect your VM in VirtualBox

2 min. read

Updated onNovember 1, 2024

updated onNovember 1, 2024

Share this article

Improve this guide

Read our disclosure page to find out how can you help Windows Report sustain the editorial teamRead more

Fix all BSoD events and keep computer safe and clean:

Fortect will find the cause of BSoD and fix it. Here is how to do it with 3 easy steps:

Error_System_Trace comes with the following message150 (0x96) System trace information was not specified in your CONFIG.SYS file, or tracing is disallowed, and this is a developer error. However, if you encounter it as a user, we have a few solutions that can help you fix it.

How can I fix Error_System_Trace?

1. Use hibernation in VM

This message appears when the guest system is put to sleep, but using the hibernate option as an alternative usually works.

2. Change resource allocation

Remember that you need to leave CPU cores and RAM available to the host PC to prevent issues such as these from occurring.

Error_System_Trace is a vague error, and it rarely appears, but if you ever encounter it in your VirtualBox logs, you might be able to fix it with these steps.

This isn’t the only issue you can encounter, we recently wrote aboutRefs_File_Systemerror as well asMailslot_File_System, so don’t miss them for more information.

In ourError_Is_Subst_Targetarticle we covered a similar issue, so don’t miss it for more information.

Error System Trace 150 (0x96): How to Fix it#

How can I fix Error_System_Trace?#

1. Use hibernation in VM#

2. Change resource allocation#

Error System Trace 150 (0x96): How to Fix it

How can I fix Error_System_Trace?

1. Use hibernation in VM

2. Change resource allocation