4 days ago,MagicAndre1981 wrote
yes, but afair the power plan is set to use full power by default.
btw, the hotfix which caused to display the bootmgr in English was updated and now the language is ok. But I removed the fix, because I don't need it on my PC.
I currently have some sporadic bug checks and I see this in WinDbg:
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
DEFAULT_BUCKET_ID: CODE_CORRUPTION
PROCESS_NAME: System
ERROR_CODE:(NTSTATUS)0xc0000005
nt!KeBugCheckEx
nt!PspUnhandledExceptionInSystemThread+0x24
nt!??::NNGAKEGL::`string'+0x227d
nt!_C_specific_handler+0x8c
nt!RtlpExecuteHandlerForException+0xd
nt!RtlDispatchException+0x415
nt!KiDispatchException+0x135
nt!KiExceptionDispatch+0xc2
nt!KiGeneralProtectionFault+0x10a
ndis!NdisMCreateLog+0x286b
ndis!NdisMPauseCo}plete+0x4364
ndis!NdisMQueueDpc+0x7f5
ndis!NdisAllocateNetBufferAndNetBufferList+0x2233
ndis!riteLock+0x925f
ndis!NdisFOidRequestComplete+0x5a8
ndis!NdisFOidRequest+0xc9
nm3!NetmonOidRequest+0x109
ndis!NdisMSynchronizeWithInterruptEx+0x842
ndis!NdisAllocateNetBuffer+0x177c
nt!ExpWorkerThread+0x111
nt!PspSystemThreadStartup+0x5a
nt!KiStartSystemThread+0x16
CHKIMG_EXTENSION: !chkimg -lo 50 -db !ndis 3393 errors : !ndis (fffff88001649048-fffff88001717fe0)
FOLLOWUP_NAME: memory_corruption
MEMORY_CORRUPTOR: STRIDE
so the ndis.sys is corrupted in RAM and differs from the file on the symbol server, but I used the Windows Memory tester and memtest86+ and both didn't detect any errors. chkdsk and sfc also didn't detect anything.
Currently I have no idea other than removing Network monitor 3.4 driver from the network adapter and watch if it happens again the next days.