BSOD when opening settings.

Question

Hello! I am using a Asus x555uj laptop in UEFI firmware BIOS mode. When tryng to open settings i got BSOD

Here is the analysys from ors online. The driver in "What failed" is"ipt.sys

Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 8 Kernel Version 17686 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff803`06414000 PsLoadedModuleList = 0xfffff803`067d55f0
Debug session time: Fri Jun 15 10:35:44.713 2018 (UTC - 4:00)
System Uptime: 0 days 0:41:48.468
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000096, The exception code that was not handled
Arg2: fffff8031f3f7d28, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

Debugging Details:
------------------

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

EXCEPTION_CODE: (NTSTATUS) 0xc0000096 - {EXCEPTION}  Privileged instruction.

FAULTING_IP: 
ipt!StartTrace+98
fffff803`1f3f7d28 0f30            wrmsr

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

ERROR_CODE: (NTSTATUS) 0xc0000096 - {EXCEPTION}  Privileged instruction.

BUGCHECK_STR:  0x1e_c0000096

CUSTOMER_CRASH_COUNT:  2

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  SystemSettings

CURRENT_IRQL:  0

BAD_PAGES_DETECTED: 2031a

EXCEPTION_RECORD:  ffffc98bc0c44000 -- (.exr 0xffffc98bc0c44000)
Cannot read Exception record @ ffffc98bc0c44000

TRAP_FRAME:  0000000000000100 -- (.trap 0x100)
Unable to read trap frame at 00000000`00000100

LAST_CONTROL_TRANSFER:  from fffff803065f9b89 to fffff803065d02b0

CONTEXT:  00000408938b4830 -- (.cxr 0x408938b4830)
Unable to read context, Win32 error 0n30

STACK_TEXT:  
fffffe8c`23731268 fffff803`065f9b89 : 00000000`0000001e ffffffff`c0000096 fffff803`1f3f7d28 00000000`00000000 : nt!KeBugCheckEx
fffffe8c`23731270 fffff803`065e1102 : ffffc98b`c0c44000 00000000`00000001 00000000`00000100 00000000`00000000 : nt!KiDispatchException+0x190fe9
fffffe8c`23731920 fffff803`065dd84d : 00000000`00000010 00000000`00000010 00000000`00000000 fffff370`4017e138 : nt!KiExceptionDispatch+0xc2
fffffe8c`23731b00 fffff803`1f3f7d28 : 00000000`0000280c fffffe8c`23731cc0 00000000`00000001 00000000`00000000 : nt!KiGeneralProtectionFault+0x2cd
fffffe8c`23731c90 fffff803`1f3f849a : ffffe080`2fc27000 00000000`0000280c ffffc98b`a2594230 ffffc98b`a2594230 : ipt!StartTrace+0x98
fffffe8c`23731cc0 fffff803`06ac9f86 : 00000000`00000001 fffff803`0680d238 00000000`00000200 fffff803`064fd8d0 : ipt!OnThreadCreate+0x4a
fffffe8c`23731cf0 fffff803`069043d2 : 00000000`000004d0 ffffc98b`c09a7700 ffffc98b`c0b50700 fffffe8c`23732770 : nt!PspCallThreadNotifyRoutines+0x148b56
fffffe8c`23731d30 fffff803`069042bd : ffffe080`2bf41180 ffffe080`2bf41180 ffffc98b`c09a7700 00000000`00000000 : nt!PspInitializeThunkContext+0x76
fffffe8c`237327d0 fffff803`065d7cf6 : ffffe080`2bf41180 ffffc98b`c09a7700 ffffc98b`c0b50700 00000000`00000000 : nt!PspUserThreadStartup+0x1ed
fffffe8c`237328c0 fffff803`065d7c70 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartUserThread+0x16
fffffe8c`23732a00 00007ff9`be502b00 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartUserThreadReturn
0000008a`b83ffc78 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7ff9`be502b00

STACK_COMMAND:  .cxr 0x408938b4830 ; kb

SYMBOL_NAME:  PAGE_NOT_ZERO

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

BUCKET_ID:  PAGE_NOT_ZERO

Followup: MachineOwner
---------

 *** Memory manager detected 131866 instance(s) of page corruption, target is likely to have memory corruption.I am having the folowuing insider priview buld: 17686.1003

Answer 1

Your welcome. Please let us know if we can be of any help

Answer 2

Yes, Reinstalling 1803 seems to be the best resort. Fast ring Builds would always have problems.

Answer 3

>I am having the folowuing insider priview buld: xxx xx xxxx

In Insider builds, these issues are common.

Can you reach Windows update page and attempt an upgrade to 17692?

Answer 4

You can tell me advanced seting i have tehician documatation.

Answer 5

I am a fellow community member who likes to help my peers when able.
Blue Screen errors can have many different causes.
Microsoft has put together an awesome troubleshooting tool to help diagnose and repair these types of errors. It can be found here
https://support.microsoft.com/en-us/help/14238/...