S
Shiran Shushan
Hello guys,
Reinstalling windows doesn't help me fix that problem, my pc bluescreens right before windows should come up with this error message.
Tried analyzing the file with WinDbg Preview, this is what comes up when I analyze the file "MEMORY.DMP" in windows folder.
It's important for me to say that I tried scanning my memory through that windows thing and it said that no problems have been found.
In WinDbg it says in the threads window "nt!KiSwapContext+0x76 (fffff802`805fc9d6)" (tried googling it and it said "DRIVER_POWER_STATE_FAILURE")
Is there any chance it might be cause cause of BIOS version? (when I updated it the last time I installed a beta version)
This thing is driving me crazy as every time I install a Windows update and it has to restart I get like 3-4 BSODs in a row ( I just got 9 in a row lol)
Here are the files from my minidump folder + the MEMORY.DMP one uploaded to google drive
Any help will be so much appreciated ❤
MEMORY.DMP analyzed through windbg preview down below
[COLOR=rgba(30, 30, 30, 1)]Microsoft (R) Windows Debugger Version 10.0.21306.1007 AMD64
Copyright (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.
************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff802`80200000 PsLoadedModuleList = 0xfffff802`80e2a490
Debug session time: Sun Mar 28 00:53:14.604 2021 (UTC + 3:00)
System Uptime: 0 days 0:00:09.212
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
.......
For analysis of this file, run [/COLOR][COLOR=rgba(0, 0, 255, 1)]!analyze -v
[/COLOR][COLOR=rgba(30, 30, 30, 1)]nt!KeBugCheckEx:
fffff802`805f5c50 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffb083`cc73eb10=000000000000000a
2: 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: ffffb5871028b010, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 0000000000000073, 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: fffff80280608bd3, address which referenced memory
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 3828
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 3848
Key : Analysis.Init.CPU.mSec
Value: 218
Key : Analysis.Init.Elapsed.mSec
Value: 5639
Key : Analysis.Memory.CommitPeak.Mb
Value: 73
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
BUGCHECK_CODE: a
BUGCHECK_P1: ffffb5871028b010
BUGCHECK_P2: ff
BUGCHECK_P3: 73
BUGCHECK_P4: fffff80280608bd3
WRITE_ADDRESS: ffffb5871028b010 Paged pool
PROCESS_NAME: System
TRAP_FRAME: ffffb083cc73ec50 -- [/COLOR][COLOR=rgba(0, 0, 255, 1)](.trap 0xffffb083cc73ec50)
[/COLOR][COLOR=rgba(30, 30, 30, 1)]NOTE: The trap frame does not contain all registers.
[/COLOR][COLOR=rgba(0, 0, 255, 1)]Some register values may be zeroed or incorrect.
[/COLOR][COLOR=rgba(30, 30, 30, 1)]rax=ffffb5871028b010 rbx=0000000000000000 rcx=ffffb5871028b020
rdx=ffffffffffde4e90 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80280608bd3 rsp=ffffb083cc73ede8 rbp=ffffb083cc73f279
r8=000000000000001c r9=0000000000000001 r10=ffffb5871006fea0
r11=ffffb5871006ff0c r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up di pl nz na pe nc
nt!memcpy+0x113:
fffff802`80608bd3 0f2941f0 movaps xmmword ptr [rcx-10h],xmm0 ds:ffffb587`1028b010=????????????????????????????????
Resetting default scope
LOCK_ADDRESS: fffff80280e44c00 -- (!locks fffff80280e44c00)
Resource @ nt!PiEngineLock (0xfffff80280e44c00) Exclusively owned
Contention Count = 5
Threads: ffff8a817a40d240-01<*>
1 total locks
PNP_TRIAGE_DATA:
Lock address : 0xfffff80280e44c00
Thread Count : 1
Thread address: 0xffff8a817a40d240
Thread wait : 0x24d
STACK_TEXT:
ffffb083`cc73eb08 fffff802`80607b69 : 00000000`0000000a ffffb587`1028b010 00000000`000000ff 00000000`00000073 : nt!KeBugCheckEx
ffffb083`cc73eb10 fffff802`80603e69 : 00000000`0000007c fffff802`80bb1094 00000000`00000003 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffb083`cc73ec50 fffff802`80608bd3 : fffff802`8045c08b ffffb587`101e0e50 ffffb587`1006fe90 00000000`00000000 : nt!KiPageFault+0x469
ffffb083`cc73ede8 fffff802`8045c08b : ffffb587`101e0e50 ffffb587`1006fe90 00000000`00000000 00000000`00001000 : nt!memcpy+0x113
ffffb083`cc73edf0 fffff802`8081b053 : 00000000`00000001 ffffb587`10201160 ffffb083`cc73efe0 00000000`00000000 : nt!CmpDoQueryKeyName+0x23b
ffffb083`cc73ef30 fffff802`807d9ae3 : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000001 : nt!CmpQueryKeyName+0x13
ffffb083`cc73ef80 fffff802`807d96da : ffffb587`101e0e50 ffffb587`1028b000 00000000`00001000 ffffb083`cc73f0f4 : nt!ObQueryNameStringMode+0xd3
ffffb083`cc73f0a0 fffff802`809267ea : ffffffff`800019c4 ffffffff`800019c4 ffff8a81`7a40d240 fffff802`00001000 : nt!NtQueryObject+0x18a
ffffb083`cc73f1f0 fffff802`80925af9 : fffff802`7e020000 ffff8a81`7a40d240 ffffffff`00000000 00000000`00000000 : nt!IopQueryRegistryKeySystemPath+0xda
ffffb083`cc73f2e0 fffff802`809232c0 : fffff802`7e020000 fffff802`7e020000 00000000`00000000 00000000`00000000 : nt!IopBuildFullDriverPath+0xc1
ffffb083`cc73f3a0 fffff802`80923228 : fffff802`7e020000 00000000`00000000 ffffffff`800019c4 ffffb587`0dff8b10 : nt!PpCheckInDriverDatabase+0x40
ffffb083`cc73f400 fffff802`80926215 : ffffb083`cc73f580 fffff802`7e0200d8 fffff802`80e45a80 00000000`00000000 : nt!PnpPrepareDriverLoading+0x6c
ffffb083`cc73f480 fffff802`80927e06 : 00000000`00000000 00000000`00000000 00000000`00000004 ffffb083`00000004 : nt!IopLoadDriver+0x27d
ffffb083`cc73f650 fffff802`80927b16 : fffff802`8020af01 00000000`00000000 ffff8a81`7ace8410 ffffffff`800019a4 : nt!PipCallDriverAddDeviceQueryRoutine+0x1be
ffffb083`cc73f6e0 fffff802`809274d4 : 00000000`00000000 ffffb083`cc73f7f0 00000000`6e657050 fffff802`0000000e : nt!PnpCallDriverQueryServiceHelper+0xda
ffffb083`cc73f790 fffff802`80926c67 : ffff8a81`7ba18c70 ffffb083`cc73f9d1 ffff8a81`7ba18c70 00000000`00000000 : nt!PipCallDriverAddDevice+0x41c
ffffb083`cc73f950 fffff802`8091fd96 : ffff8a81`7ba18c00 ffff8a81`7ce89701 ffffb083`cc73fa70 fffff802`00000000 : nt!PipProcessDevNodeTree+0x333
ffffb083`cc73fa20 fffff802`8056c31a : 00000001`00000003 ffff8a81`7ba18c70 00000000`00000000 ffff8a81`7ce89780 : nt!PiRestartDevice+0xba
ffffb083`cc73fa70 fffff802`80425975 : ffff8a81`7a40d240 ffff8a81`74287a20 fffff802`80e435a0 ffff8a81`00000000 : nt!PnpDeviceActionWorker+0x46a
ffffb083`cc73fb30 fffff802`80517e85 : ffff8a81`7a40d240 00000000`00000080 ffff8a81`742ce040 000fe067`b4bbbdff : nt!ExpWorkerThread+0x105
ffffb083`cc73fbd0 fffff802`805fd2a8 : ffffe500`d0b47180 ffff8a81`7a40d240 fffff802`80517e30 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffffb083`cc73fc20 00000000`00000000 : ffffb083`cc740000 ffffb083`cc739000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
SYMBOL_NAME: nt!KiPageFault+469
MODULE_NAME: [/COLOR][COLOR=rgba(0, 0, 255, 1)]nt
[/COLOR][COLOR=rgba(30, 30, 30, 1)]IMAGE_NAME: ntkrnlmp.exe
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 469
FAILURE_BUCKET_ID: AV_CODE_AV_nt!KiPageFault
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {22c06795-f62b-154a-eb13-05cdd373e37e}
Followup: MachineOwner
---------
[/COLOR]
Continue reading...
Reinstalling windows doesn't help me fix that problem, my pc bluescreens right before windows should come up with this error message.
Tried analyzing the file with WinDbg Preview, this is what comes up when I analyze the file "MEMORY.DMP" in windows folder.
It's important for me to say that I tried scanning my memory through that windows thing and it said that no problems have been found.
In WinDbg it says in the threads window "nt!KiSwapContext+0x76 (fffff802`805fc9d6)" (tried googling it and it said "DRIVER_POWER_STATE_FAILURE")
Is there any chance it might be cause cause of BIOS version? (when I updated it the last time I installed a beta version)
This thing is driving me crazy as every time I install a Windows update and it has to restart I get like 3-4 BSODs in a row ( I just got 9 in a row lol)
Here are the files from my minidump folder + the MEMORY.DMP one uploaded to google drive
minidump + memory dmp file.zip
drive.google.com
Any help will be so much appreciated ❤
MEMORY.DMP analyzed through windbg preview down below
[COLOR=rgba(30, 30, 30, 1)]Microsoft (R) Windows Debugger Version 10.0.21306.1007 AMD64
Copyright (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.
************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff802`80200000 PsLoadedModuleList = 0xfffff802`80e2a490
Debug session time: Sun Mar 28 00:53:14.604 2021 (UTC + 3:00)
System Uptime: 0 days 0:00:09.212
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
.......
For analysis of this file, run [/COLOR][COLOR=rgba(0, 0, 255, 1)]!analyze -v
[/COLOR][COLOR=rgba(30, 30, 30, 1)]nt!KeBugCheckEx:
fffff802`805f5c50 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffb083`cc73eb10=000000000000000a
2: 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: ffffb5871028b010, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 0000000000000073, 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: fffff80280608bd3, address which referenced memory
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 3828
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 3848
Key : Analysis.Init.CPU.mSec
Value: 218
Key : Analysis.Init.Elapsed.mSec
Value: 5639
Key : Analysis.Memory.CommitPeak.Mb
Value: 73
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
BUGCHECK_CODE: a
BUGCHECK_P1: ffffb5871028b010
BUGCHECK_P2: ff
BUGCHECK_P3: 73
BUGCHECK_P4: fffff80280608bd3
WRITE_ADDRESS: ffffb5871028b010 Paged pool
PROCESS_NAME: System
TRAP_FRAME: ffffb083cc73ec50 -- [/COLOR][COLOR=rgba(0, 0, 255, 1)](.trap 0xffffb083cc73ec50)
[/COLOR][COLOR=rgba(30, 30, 30, 1)]NOTE: The trap frame does not contain all registers.
[/COLOR][COLOR=rgba(0, 0, 255, 1)]Some register values may be zeroed or incorrect.
[/COLOR][COLOR=rgba(30, 30, 30, 1)]rax=ffffb5871028b010 rbx=0000000000000000 rcx=ffffb5871028b020
rdx=ffffffffffde4e90 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80280608bd3 rsp=ffffb083cc73ede8 rbp=ffffb083cc73f279
r8=000000000000001c r9=0000000000000001 r10=ffffb5871006fea0
r11=ffffb5871006ff0c r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up di pl nz na pe nc
nt!memcpy+0x113:
fffff802`80608bd3 0f2941f0 movaps xmmword ptr [rcx-10h],xmm0 ds:ffffb587`1028b010=????????????????????????????????
Resetting default scope
LOCK_ADDRESS: fffff80280e44c00 -- (!locks fffff80280e44c00)
Resource @ nt!PiEngineLock (0xfffff80280e44c00) Exclusively owned
Contention Count = 5
Threads: ffff8a817a40d240-01<*>
1 total locks
PNP_TRIAGE_DATA:
Lock address : 0xfffff80280e44c00
Thread Count : 1
Thread address: 0xffff8a817a40d240
Thread wait : 0x24d
STACK_TEXT:
ffffb083`cc73eb08 fffff802`80607b69 : 00000000`0000000a ffffb587`1028b010 00000000`000000ff 00000000`00000073 : nt!KeBugCheckEx
ffffb083`cc73eb10 fffff802`80603e69 : 00000000`0000007c fffff802`80bb1094 00000000`00000003 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffb083`cc73ec50 fffff802`80608bd3 : fffff802`8045c08b ffffb587`101e0e50 ffffb587`1006fe90 00000000`00000000 : nt!KiPageFault+0x469
ffffb083`cc73ede8 fffff802`8045c08b : ffffb587`101e0e50 ffffb587`1006fe90 00000000`00000000 00000000`00001000 : nt!memcpy+0x113
ffffb083`cc73edf0 fffff802`8081b053 : 00000000`00000001 ffffb587`10201160 ffffb083`cc73efe0 00000000`00000000 : nt!CmpDoQueryKeyName+0x23b
ffffb083`cc73ef30 fffff802`807d9ae3 : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000001 : nt!CmpQueryKeyName+0x13
ffffb083`cc73ef80 fffff802`807d96da : ffffb587`101e0e50 ffffb587`1028b000 00000000`00001000 ffffb083`cc73f0f4 : nt!ObQueryNameStringMode+0xd3
ffffb083`cc73f0a0 fffff802`809267ea : ffffffff`800019c4 ffffffff`800019c4 ffff8a81`7a40d240 fffff802`00001000 : nt!NtQueryObject+0x18a
ffffb083`cc73f1f0 fffff802`80925af9 : fffff802`7e020000 ffff8a81`7a40d240 ffffffff`00000000 00000000`00000000 : nt!IopQueryRegistryKeySystemPath+0xda
ffffb083`cc73f2e0 fffff802`809232c0 : fffff802`7e020000 fffff802`7e020000 00000000`00000000 00000000`00000000 : nt!IopBuildFullDriverPath+0xc1
ffffb083`cc73f3a0 fffff802`80923228 : fffff802`7e020000 00000000`00000000 ffffffff`800019c4 ffffb587`0dff8b10 : nt!PpCheckInDriverDatabase+0x40
ffffb083`cc73f400 fffff802`80926215 : ffffb083`cc73f580 fffff802`7e0200d8 fffff802`80e45a80 00000000`00000000 : nt!PnpPrepareDriverLoading+0x6c
ffffb083`cc73f480 fffff802`80927e06 : 00000000`00000000 00000000`00000000 00000000`00000004 ffffb083`00000004 : nt!IopLoadDriver+0x27d
ffffb083`cc73f650 fffff802`80927b16 : fffff802`8020af01 00000000`00000000 ffff8a81`7ace8410 ffffffff`800019a4 : nt!PipCallDriverAddDeviceQueryRoutine+0x1be
ffffb083`cc73f6e0 fffff802`809274d4 : 00000000`00000000 ffffb083`cc73f7f0 00000000`6e657050 fffff802`0000000e : nt!PnpCallDriverQueryServiceHelper+0xda
ffffb083`cc73f790 fffff802`80926c67 : ffff8a81`7ba18c70 ffffb083`cc73f9d1 ffff8a81`7ba18c70 00000000`00000000 : nt!PipCallDriverAddDevice+0x41c
ffffb083`cc73f950 fffff802`8091fd96 : ffff8a81`7ba18c00 ffff8a81`7ce89701 ffffb083`cc73fa70 fffff802`00000000 : nt!PipProcessDevNodeTree+0x333
ffffb083`cc73fa20 fffff802`8056c31a : 00000001`00000003 ffff8a81`7ba18c70 00000000`00000000 ffff8a81`7ce89780 : nt!PiRestartDevice+0xba
ffffb083`cc73fa70 fffff802`80425975 : ffff8a81`7a40d240 ffff8a81`74287a20 fffff802`80e435a0 ffff8a81`00000000 : nt!PnpDeviceActionWorker+0x46a
ffffb083`cc73fb30 fffff802`80517e85 : ffff8a81`7a40d240 00000000`00000080 ffff8a81`742ce040 000fe067`b4bbbdff : nt!ExpWorkerThread+0x105
ffffb083`cc73fbd0 fffff802`805fd2a8 : ffffe500`d0b47180 ffff8a81`7a40d240 fffff802`80517e30 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffffb083`cc73fc20 00000000`00000000 : ffffb083`cc740000 ffffb083`cc739000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
SYMBOL_NAME: nt!KiPageFault+469
MODULE_NAME: [/COLOR][COLOR=rgba(0, 0, 255, 1)]nt
[/COLOR][COLOR=rgba(30, 30, 30, 1)]IMAGE_NAME: ntkrnlmp.exe
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 469
FAILURE_BUCKET_ID: AV_CODE_AV_nt!KiPageFault
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {22c06795-f62b-154a-eb13-05cdd373e37e}
Followup: MachineOwner
---------
[/COLOR]
Continue reading...