kernel power BSOD windows 10 64bit

[nrjohnson15]

I have been getting a Kernel power error for a while now and have no idea how to fix it.

Here is what it says.

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" ></Provider>
<EventID>41</EventID>
<Version>3</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000400000000002</Keywords>
<TimeCreated SystemTime="2016-09-08T22:34:32.606138000Z" ></TimeCreated>
<EventRecordID>3153</EventRecordID>
<Correlation ></Correlation>
<Execution ProcessID="4" ThreadID="8" ></Execution>
<Channel>System</Channel>
<Computer>DESKTOP-7123ESR</Computer>
<Security UserID="S-1-5-18" ></Security>
</System>
- <EventData>
<Data Name="BugcheckCode">209</Data>
<Data Name="BugcheckParameter1">0xb8</Data>
<Data Name="BugcheckParameter2">0x2</Data>
<Data Name="BugcheckParameter3">0x0</Data>
<Data Name="BugcheckParameter4">0xfffff801bcfb7def</Data>
<Data Name="SleepInProgress">0</Data>
<Data Name="PowerButtonTimestamp">0</Data>
<Data Name="BootAppStatus">0</Data>
</EventData>
</Event>

 

[Colif]

event 41 doesn't cause a bsod, it just reports that PC restarted and windows isn't sure why. Is your PC restarting randomly? Are you getting BSOD?

event viewer,as far as I know, doesn't record bsod.

Download and run who crashed: http://www.resplendence.com/whocrashed
it will look at the error dumps and show a summary

copy/paste results here.

if you get no dumps, the crashes aren't caused by windows and need to look at hardware then or heat

 

[nrjohnson15]

My PC is restarting randomly and getting the BSOD here is the crash report analysis.



System Information (local)
--------------------------------------------------------------------------------

Computer name: DESKTOP-7123ESR
Windows version: Windows 10 , 10.0, build: 10586
Windows dir: C:\Windows
Hardware: Z170X-UD3, Gigabyte Technology Co., Ltd., Z170X-UD3-CF
CPU: GenuineIntel Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8537006080 bytes total




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Fri 9/9/2016 1:14:11 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090916-4296-01.dmp
This was probably caused by the following module: wdf01000.sys (0xFFFFF800CA457DEF)
Bugcheck code: 0xD1 (0xB8, 0x2, 0x0, 0xFFFFF800CA457DEF)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Mode Driver Framework Runtime
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Fri 9/9/2016 1:14:11 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0x7DEF)
Bugcheck code: 0xD1 (0xB8, 0x2, 0x0, 0xFFFFF800CA457DEF)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Mode Driver Framework Runtime
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Fri 9/9/2016 5:01:03 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090916-4453-01.dmp
This was probably caused by the following module: wdf01000.sys (0xFFFFF801D8857DEF)
Bugcheck code: 0xD1 (0xB8, 0x2, 0x0, 0xFFFFF801D8857DEF)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Mode Driver Framework Runtime
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Fri 9/9/2016 12:09:17 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090816-4078-01.dmp
This was probably caused by the following module: wdf01000.sys (0xFFFFF8002E2A7DEF)
Bugcheck code: 0xD1 (0xB8, 0x2, 0x0, 0xFFFFF8002E2A7DEF)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Mode Driver Framework Runtime
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Thu 9/8/2016 10:34:06 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090816-4109-01.dmp
This was probably caused by the following module: wdf01000.sys (0xFFFFF801BCFB7DEF)
Bugcheck code: 0xD1 (0xB8, 0x2, 0x0, 0xFFFFF801BCFB7DEF)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Mode Driver Framework Runtime
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Thu 9/8/2016 10:18:15 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090816-4234-01.dmp
This was probably caused by the following module: wdf01000.sys (0xFFFFF800815B7DEF)
Bugcheck code: 0xD1 (0xB8, 0x2, 0x0, 0xFFFFF800815B7DEF)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Mode Driver Framework Runtime
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Wed 9/7/2016 3:42:41 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090716-4109-01.dmp
This was probably caused by the following module: wdf01000.sys (0xFFFFF8004B257DEF)
Bugcheck code: 0xD1 (0xB8, 0x2, 0x0, 0xFFFFF8004B257DEF)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Mode Driver Framework Runtime
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Fri 9/2/2016 12:18:03 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090116-4171-01.dmp
This was probably caused by the following module: wdf01000.sys (0xFFFFF8002D5E7DEF)
Bugcheck code: 0xD1 (0xB8, 0x2, 0x0, 0xFFFFF8002D5E7DEF)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Mode Driver Framework Runtime
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Thu 9/1/2016 11:42:01 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090116-4218-01.dmp
This was probably caused by the following module: wdf01000.sys (0xFFFFF80124A57DEF)
Bugcheck code: 0xD1 (0xB8, 0x2, 0x0, 0xFFFFF80124A57DEF)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Mode Driver Framework Runtime
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Thu 9/1/2016 4:30:33 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090116-5000-01.dmp
This was probably caused by the following module: wdf01000.sys (0xFFFFF800E7657DEF)
Bugcheck code: 0xD1 (0xB8, 0x2, 0x0, 0xFFFFF800E7657DEF)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Mode Driver Framework Runtime
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

 

[Colif]

sometimes who crashed is handy, other times it isn't. It told us name of windows service being pushed to do the error but not what is causing it.

Can you follow option one here: http://www.tenforums.com/tutorials/5560-bsod-minidump-configure-create-windows-10-a.html
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c/windows/minidump
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone will help you fix it

 

[nrjohnson15]

So I used windbg and went through the bugcheck analysis and this is what it said.....


DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000000000000b8, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff80182a57def, address which referenced memory

Debugging Details:
------------------


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10.0.10586.103 (th2_release.160126-1819)

SYSTEM_MANUFACTURER: Gigabyte Technology Co., Ltd.

SYSTEM_PRODUCT_NAME: Z170X-UD3

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: F2

BIOS_DATE: 07/27/2015

BASEBOARD_MANUFACTURER: Gigabyte Technology Co., Ltd.

BASEBOARD_PRODUCT: Z170X-UD3-CF

BASEBOARD_VERSION: x.x

DUMP_TYPE: 2

BUGCHECK_P1: b8

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff80182a57def

READ_ADDRESS: 00000000000000b8

CURRENT_IRQL: 2

FAULTING_IP:
Wdf01000!FxRequest::CompleteInternal+4f [d:\th\minkernel\wdf\framework\shared\core\fxrequest.cpp @ 599]
fffff801`82a57def 488b8ab8000000 mov rcx,qword ptr [rdx+0B8h]

CPU_COUNT: 4

CPU_MHZ: db0

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 5e

CPU_STEPPING: 3

CPU_MICROCODE: 6,5e,3,0 (F,M,S,R) SIG: 23'00000000 (cache) 23'00000000 (init)

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: AV

PROCESS_NAME: System

ANALYSIS_SESSION_HOST: DESKTOP-SHEJBP1

ANALYSIS_SESSION_TIME: 09-10-2016 13:59:44.0630

ANALYSIS_VERSION: 10.0.14321.1024 x86fre

TRAP_FRAME: fffff8003324d330 -- (.trap 0xfffff8003324d330)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=ffffe001442b5190
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80182a57def rsp=fffff8003324d4c0 rbp=0000000000000000
r8=0000000000000000 r9=0000000000000000 r10=0000000000000038
r11=fffff8003324d550 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
Wdf01000!FxIrp::GetMajorFunction+0x11 [inlined in Wdf01000!FxRequest::CompleteInternal+0x4f]:
fffff801`82a57def 488b8ab8000000 mov rcx,qword ptr [rdx+0B8h] ds:00000000`000000b8=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff800317cbfe9 to fffff800317c1480

STACK_COMMAND: kb

THREAD_SHA1_HASH_MOD_FUNC: d5d7485f3a31c125ad3b21697eaceb6933fad5da

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: d0f6f1916fa7e6e8c40988b007a2c56c319db0f5

THREAD_SHA1_HASH_MOD: 5d7868a5406af4268d8581c09eaaf49ed78da356

FOLLOWUP_IP:
USBXHCI!Bulk_Transfer_CompleteCancelable+177
fffff801`8918287f 488d4d58 lea rcx,[rbp+58h]

FAULT_INSTR_CODE: 584d8d48

SYMBOL_STACK_INDEX: 5

SYMBOL_NAME: USBXHCI!Bulk_Transfer_CompleteCancelable+177

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: USBXHCI

IMAGE_NAME: USBXHCI.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 5632d6a0

IMAGE_VERSION: 10.0.10586.0

BUCKET_ID_FUNC_OFFSET: 177

FAILURE_BUCKET_ID: AV_USBXHCI!Bulk_Transfer_CompleteCancelable

BUCKET_ID: AV_USBXHCI!Bulk_Transfer_CompleteCancelable

PRIMARY_PROBLEM_CLASS: AV_USBXHCI!Bulk_Transfer_CompleteCancelable

TARGET_TIME: 2016-09-10T01:50:17.000Z

OSBUILD: 10586

OSSERVICEPACK: 103

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-01-26 21:38:01

BUILDDATESTAMP_STR: 160126-1819

BUILDLAB_STR: th2_release

BUILDOSVER_STR: 10.0.10586.103

ANALYSIS_SESSION_ELAPSED_TIME: 20a9

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:av_usbxhci!bulk_transfer_completecancelable

FAILURE_ID_HASH: {4993a1b5-1810-3a7e-3a43-18068d25fc19}

Followup: MachineOwner
---------

 

[Colif]

You are still running the old version of win 10

That error is caused by a windows driver. Normally I would suggest running SFC & DISM to fix it but updating to latest version of win 10 is likely to fix it a lot easier and save time.

Go Here and click update now and it will download the upgrade assistant. Run it and it will install latest version of win 10, and probably fix this error.