Windows 10: Random BSOD - Kernel Power - ID41 / Cat 63

Hey ho!

So my computer has been bugging me since I bought it in October. Random BSOD has occured, sometimes several times a day and sometime it goes a couple weeks between the restarts.

Well, it never goes to BSOD, the computer just reboot.

On the picture I highlighted the time Driver Verifier was on.
Attachment 70301

What I've tried so far:
Reinstall Windows 10
Tried each one memory stick for a couple days.
Memtest during nights, Intel Burn Test, Prime95 - No faults
Driver Verifier - Cause a restart shortly after logged in, used DDU to uninstall GPU drivers - This acctually got the computer to leave me a BSOD showing the HIDClass.sys / LGVirHid as a bad guy. Removed Logitech Gaming Software and it worked again, for a couple hours. Now it's something new.

Code: Microsoft (R) Windows Debugger Version 10.0.10586.567 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\031916-5703-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 10586 MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 10586.162.amd64fre.th2_release_sec.160223-1728 Machine Name: Kernel base = 0xfffff803`3e086000 PsLoadedModuleList = 0xfffff803`3e364cd0 Debug session time: Sat Mar 19 15:15:16.063 2016 (UTC + 1:00) System Uptime: 0 days 4:41:13.711 Loading Kernel Symbols . Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long. Run !sym noisy before .reload to track down problems loading symbols. .............................................................. ................................................................ ............................... Loading User Symbols Loading unloaded module list ............ ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {ffffe002ca41a5e0, 2, 0, fffff8033e0c2ea2} Probably caused by : memory_corruption ( nt!MiIdentifyPfn+1e2 ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: ffffe002ca41a5e0, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff8033e0c2ea2, address which referenced memory Debugging Details: ------------------ DUMP_CLASS: 1 DUMP_QUALIFIER: 400 BUILD_VERSION_STRING: 10586.162.amd64fre.th2_release_sec.160223-1728 SYSTEM_PRODUCT_NAME: To Be Filled By O.E.M. SYSTEM_SKU: To Be Filled By O.E.M. SYSTEM_VERSION: To Be Filled By O.E.M. BIOS_VENDOR: American Megatrends Inc. BIOS_VERSION: P1.80 BIOS_DATE: 12/01/2015 BASEBOARD_MANUFACTURER: ASRock BASEBOARD_PRODUCT: Z170 Extreme6 BASEBOARD_VERSION: DUMP_TYPE: 2 BUGCHECK_P1: ffffe002ca41a5e0 BUGCHECK_P2: 2 BUGCHECK_P3: 0 BUGCHECK_P4: fffff8033e0c2ea2 READ_ADDRESS: fffff8033e404520: Unable to get MiVisibleState ffffe002ca41a5e0 CURRENT_IRQL: 2 FAULTING_IP: nt!MiIdentifyPfn+1e2 fffff803`3e0c2ea2 4c8b3e mov r15,qword ptr [rsi] CPU_COUNT: 8 CPU_MHZ: fa8 CPU_VENDOR: GenuineIntel CPU_FAMILY: 6 CPU_MODEL: 5e CPU_STEPPING: 3 CPU_MICROCODE: 6,5e,3,0 (F,M,S,R) SIG: 49'00000000 (cache) 49'00000000 (init) CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT BUGCHECK_STR: AV PROCESS_NAME: svchost.exe ANALYSIS_SESSION_HOST: MASTER ANALYSIS_SESSION_TIME: 03-19-2016 15:22:02.0047 ANALYSIS_VERSION: 10.0.10586.567 amd64fre TRAP_FRAME: ffffd0002141fe00 -- (.trap 0xffffd0002141fe00) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0a00000000000020 rbx=0000000000000000 rcx=0200000000000000 rdx=022000000056222c rsi=0000000000000000 rdi=0000000000000000 rip=fffff8033e0c2ea2 rsp=ffffd0002141ff90 rbp=ffffd00021420009 r8=0000000000574ec0 r9=0000000000000000 r10=00000000d83f0542 r11=fffff8033e086000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc nt!MiIdentifyPfn+0x1e2: fffff803`3e0c2ea2 4c8b3e mov r15,qword ptr [rsi] ds:00000000`00000000=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff8033e1d32e9 to fffff8033e1c8760 STACK_TEXT: ffffd000`2141fcb8 fffff803`3e1d32e9 : 00000000`0000000a ffffe002`ca41a5e0 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx ffffd000`2141fcc0 fffff803`3e1d1ac7 : 00000000`00528f0f ffffe000`d0b42288 fffffa80`104f1690 00000002`20000000 : nt!KiBugCheckDispatch+0x69 ffffd000`2141fe00 fffff803`3e0c2ea2 : 00000000`00000001 fffff803`3e39ab40 ffffe000`d0b42000 00000000`00000000 : nt!KiPageFault+0x247 ffffd000`2141ff90 fffff803`3e0c2c5e : 00000000`00000100 ffffe000`d0b438c0 00000000`00000000 ffffd000`21420168 : nt!MiIdentifyPfn+0x1e2 ffffd000`21420070 fffff803`3e465597 : 00000000`00000000 00000000`00000000 ffffe000`d0b43140 ffffe000`d0b42000 : nt!MiIdentifyPfnWrapper+0x3e ffffd000`214200a0 fffff803`3e48f53c : 00000000`00000001 ffffc001`aec0b440 ffffd000`21420284 ffffe000`d0b42000 : nt!PfpPfnPrioRequest+0xc7 ffffd000`21420120 fffff803`3e48dc01 : 00000000`0000004f 00000000`00001000 000000d9`fadfb248 00000000`00000000 : nt!PfQuerySuperfetchInformation+0x2dc ffffd000`21420250 fffff803`3e48d8fb : 00000229`89305268 ffffd000`21420a80 ffffffff`ffffffd1 fffff803`3e1d2e26 : nt!ExpQuerySystemInformation+0x211 ffffd000`214209c0 fffff803`3e1d2fa3 : ffffe000`c4c74080 00000000`00000000 ffffe000`c4c74080 ffffd000`21420a80 : nt!NtQuerySystemInformation+0x2b ffffd000`21420a00 00007fff`5bda5794 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 000000d9`fadfb148 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`5bda5794 STACK_COMMAND: kb THREAD_SHA1_HASH_MOD_FUNC: adf7db7e95aa6dee42d5c13ecf7b19cbca76e51f THREAD_SHA1_HASH_MOD_FUNC_OFFSET: e8d5f59e98743fe65ecf1c9304510a07ea24fbf4 THREAD_SHA1_HASH_MOD: bc100a5647b828107ac4e18055e00abcbe1ec406 FOLLOWUP_IP: nt!MiIdentifyPfn+1e2 fffff803`3e0c2ea2 4c8b3e mov r15,qword ptr [rsi] FAULT_INSTR_CODE: f3e8b4c SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nt!MiIdentifyPfn+1e2 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 56cd4410 IMAGE_VERSION: 10.0.10586.162 IMAGE_NAME: memory_corruption BUCKET_ID_FUNC_OFFSET: 1e2 FAILURE_BUCKET_ID: AV_nt!MiIdentifyPfn BUCKET_ID: AV_nt!MiIdentifyPfn PRIMARY_PROBLEM_CLASS: AV_nt!MiIdentifyPfn TARGET_TIME: 2016-03-19T14:15:16.000Z OSBUILD: 10586 OSSERVICEPACK: 0 SERVICEPACK_NUMBER: 0 OS_REVISION: 0 SUITE_MASK: 272 PRODUCT_TYPE: 1 OSPLATFORM_TYPE: x64 OSNAME: Windows 10 OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS OS_LOCALE: USER_LCID: 0 OSBUILD_TIMESTAMP: 2016-02-24 06:48:00 BUILDDATESTAMP_STR: 160223-1728 BUILDLAB_STR: th2_release_sec BUILDOSVER_STR: 10.0.10586.162.amd64fre.th2_release_sec.160223-1728 ANALYSIS_SESSION_ELAPSED_TIME: 887 ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:av_nt!miidentifypfn FAILURE_ID_HASH: {4f0b8d4b-7219-bc8c-33a3-7bfc14bc92e1} Followup: MachineOwner ---------[/quote]


:)

 

Kernel Power 41 (63) error after updating to win10 from win7

Bump for solution

 

Kernel Power 41 (63) error after updating to win10 from win7

Okay, I did a repair install. Videogame freezes disappeared.

But I still have the random reboots with Kernel Power 41(63) error.

 

Tjena Vildling and welcome to 10forums! *Smile

It would be jolly to support you in Swedish but as this is an English speaking forum I'll have to do it in English ::/

The most recent BSOD was caused by the Logitech Gamepanel Virtual HID Device Driver
I suggest you update the drivers, you can use the link below for more info and an update link.
Driver Reference Table - LGVirHid.sys

Code: *** WARNING: Unable to verify timestamp for LGVirHid.sys *** ERROR: Module load completed but symbols could not be loaded for LGVirHid.sys Probably caused by : LGVirHid.sys 4: kd> lmvm LGVirHid Browse full module list start end module name fffff801`a7f10000 fffff801`a7f12500 LGVirHid T (no symbols) Loaded symbol image file: LGVirHid.sys Image path: \SystemRoot\system32\drivers\LGVirHid.sys Image name: LGVirHid.sys Browse all global symbols functions data Timestamp: Sat Apr 25 00:20:53 2015 (553AB3B5) CheckSum: 00015F71 ImageSize: 00002500 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/quote] Cheers, Boris *Smile