Windows 10: BugCheck Evento ID 1001 PAGE_FAULT_IN_NONPAGED_AREA win32kfull.sys

Como posso reparar esse win32kfull.sys?

Microsoft R Windows Debugger Version 10.0.19528.1000 AMD64Copyright c Microsoft Corporation. All rights reserved.Loading Dump File [C:\Windows\MEMORY.DMP]Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.Symbol search path is: srv*Executable search path is: Windows 10 Kernel Version 18362 MP 6 procs Free x64Product: WinNt, suite: TerminalServer SingleUserTS18362.1.amd64fre.19h1_release.190318-1202Machine Name:Kernel base = 0xfffff806`32000000 PsLoadedModuleList = 0xfffff806`32448150Debug session time: Sat Feb 1 17:39:46.822 2020 UTC - 3:00System Uptime: 0 days 1:43:00.489Loading Kernel Symbols...............................................................................................................................................................................Loading User SymbolsPEB is paged out Peb.Ldr = 00000023`fefe7018. Type ".hh dbgerr001" for detailsLoading unloaded module list..........For analysis of this file, run !analyze -vnt!KeBugCheckEx:fffff806`321c14e0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff930d`999e72d0=0000000000000050Loading Dump File [C:\WINDOWS\MEMORY.DMP]Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.Can't set dump file contextsMachineInfo::SetContext failed - Thread: 00000159DE2CAAC0 Handle: 6 Id: 6 - Error == 0x8000FFFF************* Path validation summary **************Response Time ms LocationDeferred srv*Symbol search path is: srv*Executable search path is: Windows 10 Kernel Version 18362 MP 6 procs Free x64Product: WinNt, suite: TerminalServer SingleUserTS18362.1.amd64fre.19h1_release.190318-1202Machine Name:Kernel base = 0xfffff806`32000000 PsLoadedModuleList = 0xfffff806`32448150Debug session time: Sat Feb 1 17:39:46.822 2020 UTC - 3:00System Uptime: 0 days 1:43:00.489Loading Kernel Symbols...............................................................................................................................................................................Loading User SymbolsPEB is paged out Peb.Ldr = 00000023`fefe7018. Type ".hh dbgerr001" for detailsLoading unloaded module list..........nt!KeBugCheckEx:fffff806`321c14e0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff930d`999e72d0=00000000000000501:5: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************PAGE_FAULT_IN_NONPAGED_AREA 50Invalid system memory was referenced. This cannot be protected by try-except.Typically the address is just plain bad or it is pointing at freed memory.Arguments:Arg1: ffffd1be21418a0c, memory referenced.Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.Arg3: ffffc1be21fa97dd, If non-zero, the instruction address which referenced the bad memory address.Arg4: 0000000000000002, reservedDebugging Details:------------------Page 452cc2 not present in the dump file. Type ".hh dbgerr004" for detailsKEY_VALUES_STRING: 1 Key : Analysis.CPU.Sec Value: 2 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on GABI Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.Sec Value: 7 Key : Analysis.Memory.CommitPeak.Mb Value: 79 Key : Analysis.System Value: CreateObjectADDITIONAL_XML: 1BUGCHECK_CODE: 50BUGCHECK_P1: ffffd1be21418a0cBUGCHECK_P2: 0BUGCHECK_P3: ffffc1be21fa97ddBUGCHECK_P4: 2READ_ADDRESS: ffffd1be21418a0c Nonpaged poolMM_INTERNAL_CODE: 2IMAGE_NAME: win32kfull.sysMODULE_NAME: win32kfullFAULTING_MODULE: ffffc1be21f50000 win32kfullPROCESS_NAME: nvsphelper64.exeTRAP_FRAME: ffff930d999e7570 -- .trap 0xffff930d999e7570NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=ffffd1be21418a0c rbx=0000000000000000 rcx=ffffc1dc841ed8a0rdx=0000004000000000 rsi=0000000000000000 rdi=0000000000000000rip=ffffc1be21fa97dd rsp=ffff930d999e7700 rbp=ffff930d999e7a80 r8=0000000000000001 r9=0000000000000001 r10=0000000000000000r11=0000000000000001 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0 nv up ei pl zr na po ncwin32kfull!xxxRealInternalGetMessage+0x26d:ffffc1be`21fa97dd 8b10 mov edx,dword ptr [rax] ds:ffffd1be`21418a0c=????????Resetting default scopeSTACK_TEXT: ffff930d`999e72c8 fffff806`321e35d6 : 00000000`00000050 ffffd1be`21418a0c 00000000`00000000 ffff930d`999e7570 : nt!KeBugCheckExffff930d`999e72d0 fffff806`32072eef : 00000000`00000000 00000000`00000000 00000000`00000000 ffffd1be`21418a0c : nt!MiSystemFault+0x1d6866ffff930d`999e73d0 fffff806`321cf520 : 00000000`00000000 00000000`00000000 00000000`00000001 0000000e`64282299 : nt!MmAccessFault+0x34fffff930d`999e7570 ffffc1be`21fa97dd : ffffc1dc`841e28a0 ffff930d`999e7a80 ffffc1dc`84408540 00000000`00000064 : nt!KiPageFault+0x360ffff930d`999e7700 ffffc1be`21fa94f7 : ffff930d`999e7920 00000000`00000000 00000023`00000000 00000023`ff3ff3e8 : win32kfull!xxxRealInternalGetMessage+0x26dffff930d`999e78e0 fffff806`321d2d15 : 00000023`ff3ff3e8 ffffc588`fdf66080 ffff930d`999e79a8 00000000`00010394 : win32kfull!NtUserPeekMessage+0x157ffff930d`999e7990 00007ffe`040810c4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x2500000023`ff3ff2b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`040810c4SYMBOL_NAME: win32kfull!xxxRealInternalGetMessage+26dSTACK_COMMAND: .thread ; .cxr ; kbBUCKET_ID_FUNC_OFFSET: 26dFAILURE_BUCKET_ID: AV_R_INVALID_win32kfull!xxxRealInternalGetMessageOS_VERSION: 10.0.18362.1BUILDLAB_STR: 19h1_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {f5ba39cd-cb80-55c4-f34a-64a00c1917a4}Followup: MachineOwner

:)

 

Error id 1001 BugCheck

Hi,

I'm having troubles with random reboots on my pc as of late. I'm not sure what causes it since i have not made any changes to my pc recently.

I decided to check out the logs to see if there are any errors related to these reboots. among a few others i found; "Error id 1001"

"The Computer rebooted after a bugcheck, the bugcheck is 0x00000124 (0x0000000000000000, 0xffff9b8d54c078f8, 0x0000000000000000, 0x0000000000000000). "

There is also a mini dumpfile, but i have no idea how to open or indeed read it.

Any help would be appreciated!

Cheers,

Maik

 

Windows 10 bugcheck every few hours with event id 1001

Unfortunately, I have now had a further two bugcheck reboots with event id 1001.

The event text is:

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009c (0x0000000000000000, 0xffffd0006a879760, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 092615-4281-01.

I have saved the MEMORY.DMP file on onedrive here: http://1drv.ms/1KBbXmO

On both occasions I was running VMWare Workstation 12.

Please can someone with the necessary tools inspect the MEMORY.DMP to find out what is going on?

Thanks,

Paul

 

Bugcheck 1001

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050 (0xffff828039ef0d28, 0x0000000000000000, 0xfffff80123d000e1, 0x0000000000000002). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 8333fe62-2287-4661-910d-133bab9d5396.

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000109 (0xa39fce67b0d2b4fe, 0xb3b6daee0350fdaf, 0xfffff8016ab000d4, 0x0000000000000001). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 0c59e2f7-9475-4763-90e0-565501ebb34b.

and this is new Dump file

MEMORYNEW.DMP