user12 Posted May 21, 2017 ID:1128711 Share Posted May 21, 2017 GMER is giving BSOD when testing for Trace I/O. If I uncheck Trace I/O box it works fine. Malwarebytes doesn't detect any maleware though. Moreover, this didn't use to happen ... it is only happening now since I updated to Windows 10 version 1703 (creator update). Should I be worried? I attached Sysnative BSOD Dump. SysnativeFileCollectionApp.zip Link to post Share on other sites More sharing options...
user12 Posted May 21, 2017 Author ID:1128746 Share Posted May 21, 2017 The error I am getting is "IRQL_NOT_LESS_OR_EQUAL" when accessing uwndapog.sys Link to post Share on other sites More sharing options...
kevinf80 Posted May 21, 2017 ID:1128755 Share Posted May 21, 2017 Hello user12, The BSOD is being caused by GMER driver "uwndapog.sys" That is shown in the seven 7 minidump files in Sysnative log.. A common cause of BSOD with GMER is active security, All security should be off when a scan is run, that is regardless of settings... Can you turn off all security and try again...? Thank you, Kevin... Link to post Share on other sites More sharing options...
exile360 Posted May 24, 2017 ID:1129849 Share Posted May 24, 2017 Due to the lack of feedback this topic is closed to prevent others from posting here. If you need this topic reopened, please send a Private Message to any one of the moderating team members. Please include a link to this thread with your request. This applies only to the originator of this thread.Other members who need assistance please start your own topic in a new thread. Thanks! Link to post Share on other sites More sharing options...
Recommended Posts