BSOD on syscall trace enabled
17 views
Skip to first unread message
pat
Apr 29, 2012, 1:19:14 PM4/29/12
to ether-devel
Greetings,
I am running Windows XP SP2 domain with nopae and noexecute=alwaysoff
options set in the boot.ini. Windows domain crashes with BSOD as soon
as syscall trace is invoked displaying DRIVER_IRQL_NOT_LESS_OR_EQUAL
with the stop information of 0xD1 followed by the guest virtual
address Ether was trying to set the new SYSTENTER EIP to
(0xddddd0ae). As recommended in previous posts with similar issues, I
tried enabling NX on the host but still getting BSOD.
Does anyone have any suggestions on how to fix this?
Thank you for your help,
Pat
I am running Windows XP SP2 domain with nopae and noexecute=alwaysoff
options set in the boot.ini. Windows domain crashes with BSOD as soon
as syscall trace is invoked displaying DRIVER_IRQL_NOT_LESS_OR_EQUAL
with the stop information of 0xD1 followed by the guest virtual
address Ether was trying to set the new SYSTENTER EIP to
(0xddddd0ae). As recommended in previous posts with similar issues, I
tried enabling NX on the host but still getting BSOD.
Does anyone have any suggestions on how to fix this?
Thank you for your help,
Pat
Artem Dinaburg
Apr 30, 2012, 10:11:14 PM4/30/12
to ether...@googlegroups.com
Do you also have /nopae in your boot.ini ?
Artem
pat
May 2, 2012, 11:56:31 AM5/2/12
to ether-devel
Yes, I have /nopae option set in the boot.ini.
Reply all
Reply to author
Forward
0 new messages