Share via

BSoD New Machine

Anonymous
2023-07-05T02:45:18+00:00

I have an HP ENVY Laptop 17 with 64GB of RAM and an Intel 12th Gen i7-1206p with a 2TB SSD, and since I received the machine, I have been having issues with it freezing and then restarting. I have had a few BSoD, but usually, this happens by the screen just freezing, and then it restarts. I checked the event log and saw the Kernal-Power Event ID 41. I reinstalled Windows 11 Enterprise Version 22H2 OS Build 22621.1928, and the problem keeps happening. I am not sure where to include the event log file but this is what it says:

  • System
    • Provider
    [ Name] Microsoft-Windows-Kernel-Power [ Guid] {331c3b3a-2005-44c2-ac5e-77220c37d6b4} EventID 41 Version 9 Level 1 Task 63 Opcode 0 Keywords 0x8000400000000002
    • TimeCreated
    [ SystemTime] 2023-07-05T02:27:02.2295876Z EventRecordID 5959 Correlation
    • Execution
    [ ProcessID] 4 [ ThreadID] 8 Channel System Computer LAL-RESEARCH-03
    • Security
    [ UserID] S-1-5-18
  • EventData BugcheckCode 10 BugcheckParameter1 0xffffb88006b042f8 BugcheckParameter2 0x2 BugcheckParameter3 0x0 BugcheckParameter4 0xfffff8071947fcf6 SleepInProgress 0 PowerButtonTimestamp 0 BootAppStatus 0 Checkpoint 0 ConnectedStandbyInProgress false SystemSleepTransitionsToOn 0 CsEntryScenarioInstanceId 0 BugcheckInfoFromEFI false CheckpointStatus 0 CsEntryScenarioInstanceIdV2 0 LongPowerButtonPressDetected false LidReliability false InputSuppressionState 0 PowerButtonSuppressionState 0 LidState 1

So I did a memory dump and opened it with Windbg and here are the results:

Microsoft (R) Windows Debugger Version 10.0.22621.1778 AMD64

Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\TwitchedOut\Desktop\Terri Minidump\070423-14000-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 22621 MP (16 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Edition build lab: 22621.1928.amd64fre.ni_release_svc_prod3.230622-0951

Machine Name:

Kernel base = 0xfffff80719200000 PsLoadedModuleList = 0xfffff80719e13480

Debug session time: Tue Jul 4 19:26:40.320 2023 (UTC - 7:00)

System Uptime: 0 days 0:29:07.311

Loading Kernel Symbols

...............................................................

................................................................

................................................................

..........................................

Loading User Symbols

Loading unloaded module list

..................

For analysis of this file, run !analyze -v

4: 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: ffffb88006b042f8, 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: fffff8071947fcf6, address which referenced memory

Debugging Details:


KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec 

Value: 2061 

Key  : Analysis.DebugAnalysisManager 

Value: Create 

Key  : Analysis.Elapsed.mSec 

Value: 4303 

Key  : Analysis.Init.CPU.mSec 

Value: 5218 

Key  : Analysis.Init.Elapsed.mSec 

Value: 25973 

Key  : Analysis.Memory.CommitPeak.Mb 

Value: 101 

Key  : WER.OS.Branch 

Value: ni\_release\_svc\_prod3 

Key  : WER.OS.Timestamp 

Value: 2023-06-22T09:51:00Z 

Key  : WER.OS.Version 

Value: 10.0.22621.1928 

FILE_IN_CAB: 070423-14000-01.dmp

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b

BUGCHECK_CODE: a

BUGCHECK_P1: ffffb88006b042f8

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff8071947fcf6

READ_ADDRESS: fffff80719f1c468: Unable to get MiVisibleState

Unable to get NonPagedPoolStart

Unable to get NonPagedPoolEnd

Unable to get PagedPoolStart

Unable to get PagedPoolEnd

unable to get nt!MmSpecialPagesInUse

ffffb88006b042f8

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: agent_ui.exe

TRAP_FRAME: ffff980f519867f0 -- (.trap 0xffff980f519867f0)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=ffffac8000000000 rbx=0000000000000000 rcx=0000018000d6085a

rdx=ffff95cae572b7f8 rsi=0000000000000000 rdi=0000000000000000

rip=fffff8071947fcf6 rsp=ffff980f51986980 rbp=ffff980f51986a80

r8=ffff9580000f9108 r9=ffff958000000000 r10=0000007ffffffff8

r11=ffff95cae572b7f8 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up ei pl zr na po nc

nt!MiDecommitPages+0x396:

fffff8071947fcf6 4c397cc828 cmp qword ptr [rax+rcx*8+28h],r15 ds:ffffb88006b042f8=????????????????

Resetting default scope

STACK_TEXT:

ffff980f519866a8 fffff807196442a9 : 000000000000000a ffffb88006b042f8 0000000000000002 0000000000000000 : nt!KeBugCheckEx

ffff980f519866b0 fffff8071963f934 : ffffac8006a3aeb0 00000000002368f9 00000000002368f9 0000000000000000 : nt!KiBugCheckDispatch+0x69

ffff980f519867f0 fffff8071947fcf6 : ffffe78b57f2a700 ffff980f00000000 0000000000000002 ffff95cac00007c8 : nt!KiPageFault+0x474

ffff980f51986980 fffff8071988bd10 : ffffe78b57d31ba0 ffffe78b57f2a548 0000000000000000 fffff8071942c76c : nt!MiDecommitPages+0x396

ffff980f519873e0 fffff8071988b92b : 0000000000000000 0000000000000000 ffff980f519874d0 0000000000000000 : nt!MiDecommitRegion+0x80

ffff980f51987490 fffff8071988b5f5 : 0000000000000000 fffff80719494309 ffffc00498a00380 00000000000000ff : nt!MmFreeVirtualMemory+0x2fb

ffff980f519875d0 fffff807196439e5 : ffffe78b5684a040 0000000000000000 0000000000000004 ffffc00498a00000 : nt!NtFreeVirtualMemory+0x95

ffff980f51987630 fffff80719634500 : fffff8074ee35c66 0000000000000000 fffff8074ee3824f ffffe78b57c0d6e0 : nt!KiSystemServiceCopyEnd+0x25

ffff980f519877c8 fffff8074ee35c66 : 0000000000000000 fffff8074ee3824f ffffe78b57c0d6e0 fffff8074ee452aa : nt!KiServiceLinkage

ffff980f519877d0 fffff8074ee34fc3 : 0000000000032000 ffffe78b57c0dcf8 ffffe78b57c0d6e0 fffff80719f49ac0 : dxgmms2!VIDMM_RECYCLE_RANGE::DebouncedDecommit+0x156

ffff980f51987820 fffff8074ee34cf8 : ffffe78b57c0d6e0 ffffe78b57c0d6e0 ffff980f51987a40 ffffc00400000000 : dxgmms2!VIDMM_RECYCLE_HEAP_MGR::ProcessDebounceList+0x213

ffff980f51987890 fffff807194b15a5 : ffffe78b3c91fbb0 ffff980f51987a00 ffffe78b00000000 fffff80700000000 : dxgmms2!VidMmRangeCurationThread+0x88

ffff980f51987940 fffff807194d9907 : ffffe78b5684a040 0000000000000f52 ffffe78b5684a040 fffff807194b1450 : nt!ExpWorkerThread+0x155

ffff980f51987b30 fffff80719633bd4 : ffff9901ab351180 ffffe78b5684a040 fffff807194d98b0 ffff980f5193b0c8 : nt!PspSystemThreadStartup+0x57

ffff980f51987b80 0000000000000000 : ffff980f51988000 ffff980f51981000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x34

SYMBOL_NAME: dxgmms2!VIDMM_RECYCLE_RANGE::DebouncedDecommit+156

MODULE_NAME: dxgmms2

IMAGE_NAME: dxgmms2.sys

IMAGE_VERSION: 10.0.22621.1972

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 156

FAILURE_BUCKET_ID: AV_dxgmms2!VIDMM_RECYCLE_RANGE::DebouncedDecommit

OS_VERSION: 10.0.22621.1928

BUILDLAB_STR: ni_release_svc_prod3

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {3c68acb7-3cf8-33af-4e4c-1d1e78a8cbf2}

Followup: MachineOwner


4: kd> !blackboxbsd

Version: 0xc0

Product type: 1

Auto advanced boot: FALSE

Advanced boot menu timeout: 30

Last boot succeeded: TRUE

Last boot shutdown: FALSE

Sleep in progress: FALSE

Power button timestamp: 0x0

System running: TRUE

Connected standby in progress: FALSE

User shutdown in progress: FALSE

System shutdown in progress: FALSE

Sleep in progress: 0

Connected standby scenario instance id: 0

Connected standby entry reason: 0

Connected standby exit reason: 0

System sleep transitions to on: 0

Last reference time: 0x1d9aee4140ad593

2023-07-05T01:57:39.617Z 

Last reference time checksum: 0xa42bba78

Last update boot id: 18

Boot attempt count: 1

Last boot checkpoint: TRUE

Checksum: 0x7f

Last boot id: 18

Last successful shutdown boot id: 14

Last reported abnormal shutdown boot id: 17

Error info boot id: 0

Error info repeat count: 0

Error info other error count: 0

Error info code: 0

Error info status: 0x0

Power button last press time: 0x0

Power button cumulative press count: 0

Power button last press boot id: 0

Power button last power watchdog stage: 0

Power button watchdog armed: FALSE

Power button shutdown in progress: FALSE

Power button last release time: 0x0

Power button cumulative release count: 0

Power button last release boot id: 0

Power button error count: 0

Power button current connected standby phase: 0

Power button transition latest checkpoint id: 0

Power button transition latest checkpoint type: 0

Power button transition latest checkpoint sequence number: 0

Power transition Shutdown Device Type: 0

Power transition Setup In Progress: FALSE

Power transition OOBE In Progress: FALSE

Power transition Sleep Checkpoint Source: 0

Power transition Sleep Checkpoint: 0

Power transition Connected Standby Entry Reason Category: 0

Power transition Connected Standby Exit Reason Category: 0

Power transition Connected Standby Entry Scenario Instance Id: 0x0

Feature Configuration State : Committed

4: kd> lmvm dxgmms2

Browse full module list

start end module name

fffff8074eda0000 fffff8074eeb7000 dxgmms2 # (pdb symbols) C:\ProgramData\dbg\sym\dxgmms2.pdb\128DEAC384CAFD6046C78983F66ECD771\dxgmms2.pdb

Loaded symbol image file: dxgmms2.sys 

Mapped memory image file: C:\ProgramData\dbg\sym\dxgmms2.sys\31CA8FFA117000\dxgmms2.sys 

Image path: \SystemRoot\System32\drivers\dxgmms2.sys 

Image name: dxgmms2.sys 

Browse all global symbols  functions  data 

Image was built with /Brepro flag. 

Timestamp:        31CA8FFA (This is a reproducible build file hash, not a timestamp) 

CheckSum:         00123B00 

ImageSize:        00117000 

File version:     10.0.22621.1972 

Product version:  10.0.22621.1972 

File flags:       0 (Mask 3F) 

File OS:          40004 NT Win32 

File type:        3.7 Driver 

File date:        00000000.00000000 

Translations:     0409.04b0 

Information from resource tables: 

    CompanyName:      Microsoft Corporation 

    ProductName:      Microsoft® Windows® Operating System 

    InternalName:     dxgmms2.sys 

    OriginalFilename: dxgmms2.sys 

    ProductVersion:   10.0.22621.1972 

    FileVersion:      10.0.22621.1972 (WinBuild.160101.0800) 

    FileDescription:  DirectX Graphics MMS 

    LegalCopyright:   © Microsoft Corporation. All rights reserved. 

4: kd> .trap 0xffff980f519867f0

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=ffffac8000000000 rbx=0000000000000000 rcx=0000018000d6085a

rdx=ffff95cae572b7f8 rsi=0000000000000000 rdi=0000000000000000

rip=fffff8071947fcf6 rsp=ffff980f51986980 rbp=ffff980f51986a80

r8=ffff9580000f9108 r9=ffff958000000000 r10=0000007ffffffff8

r11=ffff95cae572b7f8 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up ei pl zr na po nc

nt!MiDecommitPages+0x396:

fffff8071947fcf6 4c397cc828 cmp qword ptr [rax+rcx*8+28h],r15 ds:ffffb88006b042f8=????????????????

4: kd> !blackboxntfs

NTFS Blackbox Data

0 Slow I/O Timeout Records Found

0 Oplock Break Timeout Records Found

Windows for home | Windows 11 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

7 answers

Sort by: Most helpful
  1. Anonymous
    2023-07-05T18:33:37+00:00

    This should be impossible on this computer. I would like to know what O.S came with the computer please. I haven't seen Windows 11 enterprise in my local stores. I am located in Canada though. It may be possible you have Windows 11 enterprise in your stores? Thanks for all the information some times people just don't leave enough info but you did how lovely. 🐈🐾

    This code can mean p.c shutdown incorrectly. Can mean it lost power and shutdown.

    This code can come up as well with a old/bad display driver+ monitor driver.

    One solution is to try to update the display driver and the monitor driver(PNP device). It may be possible HP has a newer driver on there website for your model.

    To check your drivers hit window button and then type device manager.

    I hope this helps.

    The Windows version is Windows 11 Enterprise just so that you know. I updated the the video drivers and didn't have any issue until this morning. Now the same thing just happend the computer froze and this is the event log:

    • System
      • Provider
      [ Name] Microsoft-Windows-Kernel-Power [ Guid] {331c3b3a-2005-44c2-ac5e-77220c37d6b4} EventID 41 Version 9 Level 1 Task 63 Opcode 0 Keywords 0x8000400000000002
      • TimeCreated
      [ SystemTime] 2023-07-05T17:17:38.1832507Z EventRecordID 8416 Correlation
      • Execution
      [ ProcessID] 4 [ ThreadID] 8 Channel System Computer LAL-RESEARCH-03
      • Security
      [ UserID] S-1-5-18
    • EventData BugcheckCode 122 BugcheckParameter1 0x1 BugcheckParameter2 0xffffffffc0000005 BugcheckParameter3 0xffffd30fae3020c0 BugcheckParameter4 0xffffe3719f7e9000 SleepInProgress 0 PowerButtonTimestamp 0 BootAppStatus 0 Checkpoint 0 ConnectedStandbyInProgress false SystemSleepTransitionsToOn 0 CsEntryScenarioInstanceId 0 BugcheckInfoFromEFI false CheckpointStatus 0 CsEntryScenarioInstanceIdV2 0 LongPowerButtonPressDetected false LidReliability false InputSuppressionState 0 PowerButtonSuppressionState 0 LidState 1

    Was this answer helpful?

    0 comments No comments
  2. MR_MEOW 3,541 Reputation points
    2023-07-05T10:56:21+00:00

    This should be impossible on this computer. I would like to know what O.S came with the computer please. I haven't seen Windows 11 enterprise in my local stores. I am located in Canada though. It may be possible you have Windows 11 enterprise in your stores? Thanks for all the information some times people just don't leave enough info but you did how lovely. 🐈🐾

    This code can mean p.c shutdown incorrectly. Can mean it lost power and shutdown.

    This code can come up as well with a old/bad display driver+ monitor driver.

    One solution is to try to update the display driver and the monitor driver(PNP device). It may be possible HP has a newer driver on there website for your model.

    To check your drivers hit window button and then type device manager.

    I hope this helps.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2023-07-05T06:51:00+00:00

    Sure, let me know the result. Thank you.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2023-07-05T05:08:54+00:00

    I’m sorry that you are experiencing this issue. The minidumps indicate BSOD caused by the Nvidia driver.

    Please clean uninstall the Nvidia driver with the DDU tool.
    https://www.wagnardsoft.com/display-driver-unin...

    Download and install the latest driver by visiting the below link. Ensure to download the notebook version.
    https://www.nvidia.com/Download/index.aspx?lang...

    If the issue persists, disable GPU Acceleration.
    https://appuals.com/disable-accelerated-gpu-sch...

    Also, kernel Power Error 41 results from the insufficient or faulty adapter. Ensure that your system has sufficient wattage to handle the installed devices appropriately, and test your adapter charger.

    Please let me know the result. Thank you.
    __________________________________________________
    Disclaimer - There is a non-Microsoft website. The page appears to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the site before downloading and installing it.
    The above link is in English; you need to use Translator to see it in your language.

    Thank you for such a quick response, however, the GPU is an Intel Iris Xe but I am going to do what you suggested and remove and update the drivers. I will check to ensure that the power supply is the correct one that came with the laptop and let you know.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2023-07-05T03:20:15+00:00

    I’m sorry that you are experiencing this issue. The minidumps indicate BSOD caused by the Nvidia driver.

    Please clean uninstall the Nvidia driver with the DDU tool.

    https://www.wagnardsoft.com/display-driver-unin...

    Download and install the latest driver by visiting the below link. Ensure to download the notebook version.

    https://www.nvidia.com/Download/index.aspx?lang...

    If the issue persists, disable GPU Acceleration.

    https://appuals.com/disable-accelerated-gpu-sch...

    Also, kernel Power Error 41 results from the insufficient or faulty adapter. Ensure that your system has sufficient wattage to handle the installed devices appropriately, and test your adapter charger.

    Please let me know the result. Thank you.

    __________________________________________________

    Disclaimer - There is a non-Microsoft website. The page appears to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the site before downloading and installing it.

    The above link is in English; you need to use Translator to see it in your language.

    Was this answer helpful?

    0 comments No comments