BSOD Issue
BSOD Issue
Resolved the persistent crash issue after the fix, though it continues to fail at that stage.
So seeing as how it crashes in VR without the headset, this is what it threw. Looks like it's just software issues... Spoiler ******************************************************************************* * * * 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: ffffffffc0000005, The exception code that was not handled Arg2: fffff8042f7f7108, The address that the exception occurred at Arg3: 0000000000000001, Parameter 0 of the exception Arg4: 00000000001f0002, Parameter 1 of the exception Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 2093 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 3309 Key : Analysis.Init.CPU.mSec Value: 796 Key : Analysis.Init.Elapsed.mSec Value: 6547 Key : Analysis.Memory.CommitPeak.Mb Value: 74 DUMP_FILE_ATTRIBUTES: 0x8 Kernel Generated Triage Dump BUGCHECK_CODE: 1e BUGCHECK_P1: ffffffffc0000005 BUGCHECK_P2: fffff8042f7f7108 BUGCHECK_P3: 1 BUGCHECK_P4: 1f0002 WRITE_ADDRESS: fffff8042fefb390: Unable to get MiVisibleState Unable to get NonPagedPoolStart Unable to get NonPagedPoolEnd Unable to get PagedPoolStart Unable to get PagedPoolEnd unable to get nt!MmSpecialPagesInUse 00000000001f0002 EXCEPTION_PARAMETER1: 0000000000000001 EXCEPTION_PARAMETER2: 00000000001f0002 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: VRChat.exe TRAP_FRAME: ffff800000000000 -- (.trap 0xffff800000000000) Unable to read trap frame at ffff8000`00000000 STACK_TEXT: fffffd87`1d778f48 fffff804`2f65a5cb : 00000000`0000001e ffffffff`c0000005 fffff804`2f7f7108 00000000`00000001 : nt!KeBugCheckEx fffffd87`1d778f50 fffff804`2f6099ac : 00000000`00001000 fffffd87`1d7797f0 ffff8000`00000000 00000000`00000000 : nt!KiDispatchException+0x174bbb fffffd87`1d779610 fffff804`2f605b43 : ffffe309`3f28b080 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0x12c fffffd87`1d7797f0 fffff804`2f7f7108 : 00000000`00000000 ffffe309`3f28b1c0 fffffd87`1d7799e0 00000000`00000000 : nt!KiPageFault+0x443 fffffd87`1d779980 00000000`00000000 : ffffe309`3f28b1c0 fffffd87`1d7799e0 00000000`00000000 00000000`00040000 : nt!ExpLookupHandleTableEntry+0x48 SYMBOL_NAME: nt!ExpLookupHandleTableEntry+48 MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe IMAGE_VERSION: 10.0.19041.1645 STACK_COMMAND: .thread ; .cxr ; kb BUCKET_ID_FUNC_OFFSET: 48 FAILURE_BUCKET_ID: 0x1E_c0000005_W_nt!ExpLookupHandleTableEntry OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {d53fa430-2ad8-0df0-1b21-db9495ba137b} Followup: MachineOwner ---------
This approach is effective because it simplifies identifying the issue. By swapping everything at once, you can pinpoint whether the problem lies in the safe mode settings or the drivers. If safe mode causes issues, you replace just the windows; if not, you tackle the drivers. The typical fix for corrupted software involves replacing it with a clean version.
They’re talking about Bloatwares and similar tools that claim to update drivers and add extra features. I’m not sure if they actually help or if they’re just misleading software with unnecessary content.
Check the original source. For NVIDIA drivers, visit nvidia etc.