Windows 10: I have a BSOD problem related with module name NT, can you help me?

Debugging info:Arg1: ffffffffc0000005, The exception code that was not handled Arg2: 000000599d3febb0, The address that the exception occurred at Arg3: 0000000000000008, Parameter 0 of the exception Arg4: 000000599d3febb0, Parameter 1 of the exception BUGCHECK_CODE: 1e BUGCHECK_P1: ffffffffc0000005 BUGCHECK_P2: 599d3febb0 BUGCHECK_P3: 8 BUGCHECK_P4: 599d3febb0 FILE_IN_CAB: 062224-17015-01.dmp DUMP_FILE_ATTRIBUTES: 0x1008 Kernel Generated Triage Dump EXCEPTION_PARAMETER1: 0000000000000008 EXCEPTION_PARAMETER2: 000000599d3febb0 WRITE_ADDRESS: fffff8075591c4a8: Unable to get MiVisi

:)

 

Daily BSOD - Windows 10 PRO 22H2

Two of your BSODs occurred whilst a mouse or keyboard operation was underway, the HIDCLASS driver appears often on the two call stacks. One BSOD occurred during storage access, the NTFS driver appears often on the call stack. One BSOD is inconclusive, I'm not sure what's causing that one. The one that's of real interest in the DRIVER_VERIFIER_DETECTED_VIOLATION. Although you have Driver Verifier enabled it doesn't have the recommended options enabled, but it's still managed to catch a third-party driver that is misbehaving. That driver is GUBootStartup.sys as you can see from the call stack... Code:

The GUBootStartup.sys driver appears to be a component of Glary Utilities and from the name it would seem that this one is loaded at Windows startup and thus is always present. The version you have is about 18 months old... Code:

I would suggest either looking for any update to Glary Utilities or, better still, uninstalling it completely. Interestingly I note that Glary Utilities doesn't appear in your list of installed software? I can't be certain that the other BSODs are related to this driver but we need to proceed one step at a time. We know now that GUBootStartup.sys is faulty and needs removing or updating before we look at anything else.

 

BSOD - Bad_Pool_Caller

Please do not mark the thread as answered until you feel the issue is resolved.

As far the the dump is concerned, I looked at it and found the module list was corrupt:

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

Unable to get size of nt!_MMPTE - probably bad symbols

Unable to get size of nt!_MMPTE - probably bad symbols

Before I suggest a memory test, can you post one or two more dump files?

 

GTA IV and the dreaded BSOD

One (or more) of the cores in the CPU could be failing. Games can't ever cause a BSOD unless they are dabbling in affairs that they shouldn't be (namely hardware configuration without interfacing via the drivers).


Does the BSOD list a faulting module (e.g. mom.exe, nv4_disp.dll, ccc.exe, etc.)?