Windows 10: BSOD

Discus and support BSOD in Windows 10 BSOD Crashes and Debugging to solve the problem; I have been getting blue screen very frequently since last 2 days. This started only since I installed the windows latest updates. The error on blue... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by AmitPillai, Oct 21, 2020.

  1. BSOD


    I have been getting blue screen very frequently since last 2 days. This started only since I installed the windows latest updates.

    The error on blue screen is: PFN_LIST_CORRUPT


    I have opened the mini dump file but I am not able to follow much , I think it mentions some issue with rtsuvc.sys driver. Also my webcam has been not working properly since.


    Below is the analysis of the dump file:


    Mini Kernel Dump File: Only registers and stack trace are available


    Symbol search path is: srv*

    Executable search path is:

    Windows 10 Kernel Version 19041 MP 8 procs Free x64

    Product: WinNt, suite: TerminalServer SingleUserTS

    Machine Name:

    Kernel base = 0xfffff800`82600000 PsLoadedModuleList = 0xfffff800`8322a310

    Debug session time: Wed Oct 21 15:07:44.854 2020 UTC - 4:00

    System Uptime: 0 days 0:06:34.627

    Loading Kernel Symbols

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

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

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

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

    Loading User Symbols

    Loading unloaded module list

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

    For analysis of this file, run !analyze -v

    0: kd> !analyze -v

    *******************************************************************************

    * *

    * Bugcheck Analysis *

    * *

    *******************************************************************************



    PFN_LIST_CORRUPT 4e

    Typically caused by drivers passing bad memory descriptor lists ie: calling

    MmUnlockPages twice with the same list, etc. If a kernel debugger is

    available get the stack trace.

    Arguments:

    Arg1: 000000000000009a,

    Arg2: 000000000045a9ff

    Arg3: 0000000000000006

    Arg4: 0000000000000002



    Debugging Details:

    ------------------



    *** WARNING: Unable to verify timestamp for rtsuvc.sys



    KEY_VALUES_STRING: 1



    Key : Analysis.CPU.Sec

    Value: 3



    Key : Analysis.DebugAnalysisProvider.CPP

    Value: Create: 8007007e on AMIT-PC



    Key : Analysis.DebugData

    Value: CreateObject



    Key : Analysis.DebugModel

    Value: CreateObject



    Key : Analysis.Elapsed.Sec

    Value: 4



    Key : Analysis.Memory.CommitPeak.Mb

    Value: 80



    Key : Analysis.System

    Value: CreateObject





    DUMP_FILE_ATTRIBUTES: 0x8

    Kernel Generated Triage Dump



    BUGCHECK_CODE: 4e



    BUGCHECK_P1: 9a



    BUGCHECK_P2: 45a9ff



    BUGCHECK_P3: 6



    BUGCHECK_P4: 2



    BLACKBOXBSD: 1 !blackboxbsd





    BLACKBOXNTFS: 1 !blackboxntfs





    BLACKBOXPNP: 1 !blackboxpnp





    BLACKBOXWINLOGON: 1



    CUSTOMER_CRASH_COUNT: 1



    PROCESS_NAME: System



    LOCK_ADDRESS: fffff80083244ae0 -- !locks fffff80083244ae0

    Cannot get _ERESOURCE type



    Resource @ nt!PiEngineLock 0xfffff80083244ae0 Available

    1 total locks



    PNP_TRIAGE_DATA:

    Lock address : 0xfffff80083244ae0

    Thread Count : 0

    Thread address: 0x0000000000000000

    Thread wait : 0x0



    STACK_TEXT:

    ffffac80`40701e68 fffff800`82a3e475 : 00000000`0000004e 00000000`0000009a 00000000`0045a9ff 00000000`00000006 : nt!KeBugCheckEx

    ffffac80`40701e70 fffff800`8287c31e : ffffc7e4`c5ff0a80 ffffac80`40701fe0 00000000`00000002 ffffc7e3`00000000 : nt!MiDeleteNonPagedPoolPte+0x1c2025

    ffffac80`40701ee0 fffff800`82820c16 : ffffc98b`fa7b7000 00000000`00004000 00000000`00000000 00000000`00000000 : nt!MiClearNonPagedPtes+0x162

    ffffac80`40702110 fffff800`82820a3a : 00000000`00000000 ffffac80`40702281 ffffffff`ffffff3f 00000000`00004000 : nt!MmFreePoolMemory+0x1aa

    ffffac80`40702190 fffff800`8281ff86 : 00000000`00000001 00000000`fffffffc fffff800`fffffffc fffff800`00004000 : nt!RtlpHpEnvFreeVA+0x12

    ffffac80`407021c0 fffff800`828256f3 : fffff800`9face7e2 ffffc98b`fa7016c0 00000000`fffffffc ffffc98b`fa7b6000 : nt!RtlpHpFreeVA+0x3a

    ffffac80`40702200 fffff800`8282539e : 00000001`00000000 00000000`ffffff3f 00000000`00000000 00000000`fffff090 : nt!RtlpHpSegMgrCommit+0x1e3

    ffffac80`407022d0 fffff800`828277c1 : ffffc98b`00000010 ffffc98b`fe000120 ffffc98b`00000000 fffff800`000000c1 : nt!RtlpHpSegPageRangeCommit+0x1ee

    ffffac80`40702370 fffff800`8282725b : ffffffff`ffffffff 00000000`0000000d ffffffff`ffffffff ffffc98b`fa7639c0 : nt!RtlpHpSegPageRangeCoalesce+0x1b1

    ffffac80`407023f0 fffff800`828c76f2 : 00000000`00000000 ffffc98b`fa8001c0 00000000`fe000000 00000000`00000000 : nt!RtlpHpSegPageRangeShrink+0xeb

    ffffac80`40702460 fffff800`82fb1019 : ffffb30e`00000000 ffffc98c`094e2980 fffff800`9c8ef0e0 01000000`00100000 : nt!ExFreeHeapPool+0x6b2

    ffffac80`40702540 fffff800`9fa16b73 : ffffc98b`fe0909c0 ffffc98b`fe0909c0 ffffc98c`094e2980 00000000`00000001 : nt!ExFreePool+0x9

    ffffac80`40702570 ffffc98b`fe0909c0 : ffffc98b`fe0909c0 ffffc98c`094e2980 00000000`00000001 00000000`00000001 : rtsuvc+0x226b73

    ffffac80`40702578 ffffc98b`fe0909c0 : ffffc98c`094e2980 00000000`00000001 00000000`00000001 fffff800`9c9023bd : 0xffffc98b`fe0909c0

    ffffac80`40702580 ffffc98c`094e2980 : 00000000`00000001 00000000`00000001 fffff800`9c9023bd ffffb30e`2b181050 : 0xffffc98b`fe0909c0

    ffffac80`40702588 00000000`00000001 : 00000000`00000001 fffff800`9c9023bd ffffb30e`2b181050 fffff800`00000000 : 0xffffc98c`094e2980

    ffffac80`40702590 00000000`00000001 : fffff800`9c9023bd ffffb30e`2b181050 fffff800`00000000 ffffc98b`00000000 : 0x1

    ffffac80`40702598 fffff800`9c9023bd : ffffb30e`2b181050 fffff800`00000000 ffffc98b`00000000 fffff800`7f8ba100 : 0x1

    ffffac80`407025a0 fffff800`9c9022d1 : ffffb30e`2be7fbb0 ffffb30e`2b181050 ffffb30e`2be95950 00000000`00000017 : ks!KspReleaseDeviceBagEntry+0x9d

    ffffac80`407025e0 fffff800`9c916fb9 : ffffc98c`09824e10 fffff800`9c8ef0e0 00000000`00000000 00000000`00000000 : ks!KspTerminateObjectBag+0xe1

    ffffac80`40702620 fffff800`9c9170e4 : 00000000`00000001 ffffc98c`0998bde0 ffffc98c`09a30060 00000000`00000000 : ks!CKsDevice::~CKsDevice+0xa9

    ffffac80`40702650 fffff800`9c90926c : ffffc98c`094e2900 fffff800`82fb1019 00000000`00000000 ffffc98c`084da380 : ks!CKsDevice::`vector deleting destructor'+0x14

    ffffac80`40702680 fffff800`9c919904 : ffffc98c`094e2938 ffffc98c`00000000 ffffc98c`0998bde0 ffffc98c`094e2938 : ks!CBaseUnknown::NonDelegatedRelease+0x3c

    ffffac80`407026c0 fffff800`9c91a133 : fffff800`9fa6a400 00000000`00003700 00000000`00000000 ffffc98c`094e2938 : ks!CKsDevice::Release+0x14

    ffffac80`407026f0 fffff800`9c906db7 : ffffc98c`085a07e0 ffffc98c`0998bde0 ffffc98c`085a0d30 ffffc98c`0998bde0 : ks!KsTerminateDevice+0x73

    ffffac80`40702720 fffff800`828cd805 : ffffac80`40702820 ffffc98c`084da380 ffffc98c`09a30060 fffff800`82fb1094 : ks!CKsDevice:BSOD :DispatchPnp+0x4f7

    ffffac80`40702790 fffff800`9e1715de : fffff800`00000000 fffff800`82d53d25 00000000`00000000 00000000`00000500 : nt!IofCallDriver+0x55

    ffffac80`407027d0 fffff800`9e171023 : ffffc98c`09815920 ffffac80`40702950 ffffc98c`00000000 ffffc98c`085a07e0 : ksthunk!CKernelFilterDevice:BSOD :DispatchIrp+0x15a

    ffffac80`40702830 fffff800`828cd805 : 00000000`00000000 fffff800`82803773 00000000`00000012 00000000`69706e00 : ksthunk!CKernelFilterDevice:BSOD :DispatchIrpBridge+0x13

    ffffac80`40702860 fffff800`82bd4b48 : 00000000`00000000 ffffc98c`09815920 ffffac80`40702950 fffff800`82d39e28 : nt!IofCallDriver+0x55

    ffffac80`407028a0 fffff800`82d39b31 : ffffc98c`09a30060 ffffc98c`09a30060 ffffc98c`02eab9a0 00000000`00000002 : nt!IopSynchronousCall+0xf8

    ffffac80`40702910 fffff800`8296e174 : ffffb30e`2a96f9f0 ffffc98c`02eab9a0 00000000`00000001 00000000`0000000a : nt!IopRemoveDevice+0x105

    ffffac80`407029c0 fffff800`82d396fa : ffffc98c`02eab9a0 ffffdd01`00000000 00000000`00000000 fffff800`83244bc0 : nt!PnpRemoveLockedDeviceNode+0x1ac

    ffffac80`40702a20 fffff800`82d3942f : ffffc98c`02eab9a0 ffffac80`40702aa0 00000000`00000000 00000000`00000000 : nt!PnpDeleteLockedDeviceNode+0x4e

    ffffac80`40702a60 fffff800`82d3bc95 : ffffc98c`02f092c0 00000000`00000002 ffffc98c`07f19490 00000000`00000000 : nt!PnpDeleteLockedDeviceNodes+0xf7

    ffffac80`40702ae0 fffff800`82d358b4 : 00000000`00000000 ffffac80`40702b60 ffffc98b`facb7b10 00000000`00000000 : nt!PipRemoveDevicesInRelationList+0x8d

    ffffac80`40702b30 fffff800`829035f5 : ffffc98c`087a9080 fffff800`83245280 ffffc98b`facb7b10 ffffc98c`00000000 : nt!PnpDelayedRemoveWorker+0x114

    ffffac80`40702b70 fffff800`828a2ae5 : ffffc98c`087a9080 00000000`00000080 ffffc98b`faca3040 000fa425`b19bbdff : nt!ExpWorkerThread+0x105

    ffffac80`40702c10 fffff800`829fbbf8 : ffffdd01`8a5df180 ffffc98c`087a9080 fffff800`828a2a90 00000000`00000000 : nt!PspSystemThreadStartup+0x55

    ffffac80`40702c60 00000000`00000000 : ffffac80`40703000 ffffac80`406fd000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28




    SYMBOL_NAME: rtsuvc+226b73



    MODULE_NAME: rtsuvc



    IMAGE_NAME: rtsuvc.sys



    STACK_COMMAND: .thread ; .cxr ; kb



    BUCKET_ID_FUNC_OFFSET: 226b73



    FAILURE_BUCKET_ID: 0x4E_9a_rtsuvc!unknown_function



    OSPLATFORM_TYPE: x64



    OSNAME: Windows 10



    FAILURE_ID_HASH: {6d83ce9d-2fd9-f756-e19f-c20fb7e9a1cc}



    Followup: MachineOwner

    ---------

    :)
     
    AmitPillai, Oct 21, 2020
    #1
  2. ARC
    Arc Win User

    Random BSOD while browsing internet


    BitDefender is nothing special. mwac.sys causes BSODs anywhere.
    A tiny documentation can be found here: Solved Random BSODs - Windows 10 Forums
    In that very thread, the suggested action apparently worked.

    The storage and network filters of any third party antivirus can cause BSODs. Neither MBAM nor BitDefender is any special. For a regular antivirus, it may be shifted to an alternative; but MBAM has no alternative. So a clean install of the said program is the most feasible first step.
    As far as the first step is not failing, it is better to not think for the second step. Because the BSODs are not universal, failure at the first step is not universal; and success at the second step is also not universal.
    That is why I posted that my suggestion may work, or may not. Let us see where it goes.
     
  3. cplpro Win User
    7 different BSoD

    Hey guys,

    I have a serious problem. I make it as short as possible:

    • system runs 100 % fine with the 10.12
    • updatet to Catalyst 11.1 -> BSoD
    • updatet to 11.1 Hotfix -> BSoD
    • rollback to 10.12 -> BSoD
    • removed ALL AMD files manually, installed 10.12 -> BSoD
    • Temps are fine
    • no sfc /scannow errors
    • no chkdsk errors
    • Prime, Furmark all fine
    • regardless what driver I install -> BSoD
    • I did no hw changes, no OC
    Here are my BSoDs I receive:
    • 0x0000010e
    • 0x1000007e
    • 0x0000007e
    • 0x0000004e
    • 0x0000003b
    • dxgmms1.sys
    • PFN_LIST_CORRUPT
    They all refer to the GPU of course ...

    From now on I receive a BSoD every time I try to play a game (especially BC2 and SC II) even if I completely remove the old driver and make a clean install.
    Apparently the 11.1 damaged my system irreparable.

    Any advice or info would be very much appreciated *Smile BSOD :)
     
    cplpro, Oct 21, 2020
    #3
  4. axe0 Win User

    BSOD

    BAD_POOL_HEADER BSOD, Dump File attached


    Hi Groggubus,

    Welcome to the 10forums BSOD :)

    Please remove / disable items from the startup in taskmanager
    These programs could interfere with the boot process giving you trouble and increase the boot time.

    Daemon tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known cause for BSOD's.
    Please remove Daemon Tools and run the SPTD pass through remover.

    1. Uninstall Daemon Tools
    2. Download the SPTD standalone installer and follow these steps:
      • Double click the executable to open it
      • Click on the button shown below

    BSOD [​IMG]

    If the button is grayed out, like in the image, there is no more SPTD installation on your system, and you can close the window

    Please follow this suggestion for the BSOD
    1. Please open BitDefender and go to the modules,
    2. Go to the firewall settings,
    3. Uncheck 'Block port scans in the network',
    4. Reboot your system <-- IMPORTANT
     
Thema:

BSOD

Loading...
  1. BSOD - Similar Threads - BSOD

  2. BSOD Crash when using Bluetooth PAN to connect to phone. Get invalid mdl range error

    in Windows 10 Gaming
    BSOD Crash when using Bluetooth PAN to connect to phone. Get invalid mdl range error: On a Surface Pro 7+ running the latest version available of Windows 11. EVERY TIME I connect to a phone via BT PAN I get the BSOD error 'Invalid MDL Range'. I've reset all network adapters, updated all drivers via windows update and intel. Seems like the exact same issue...
  3. BSOD Crash when using Bluetooth PAN to connect to phone. Get invalid mdl range error

    in Windows 10 Software and Apps
    BSOD Crash when using Bluetooth PAN to connect to phone. Get invalid mdl range error: On a Surface Pro 7+ running the latest version available of Windows 11. EVERY TIME I connect to a phone via BT PAN I get the BSOD error 'Invalid MDL Range'. I've reset all network adapters, updated all drivers via windows update and intel. Seems like the exact same issue...
  4. BSOD problem dont give option to reset this pc.

    in Windows 10 Gaming
    BSOD problem dont give option to reset this pc.: The bsod is very laggy after automatic repair when bootup. then it bring to the bsod. after that, it didnt give the option to reset this pc and straightway go to advanced option for troubleshooting. in this case i cannot reset my pc. command prompt also didnt work as scannow...
  5. BSOD problem dont give option to reset this pc.

    in Windows 10 Software and Apps
    BSOD problem dont give option to reset this pc.: The bsod is very laggy after automatic repair when bootup. then it bring to the bsod. after that, it didnt give the option to reset this pc and straightway go to advanced option for troubleshooting. in this case i cannot reset my pc. command prompt also didnt work as scannow...
  6. BSOD problem dont give option to reset this pc.

    in Windows 10 BSOD Crashes and Debugging
    BSOD problem dont give option to reset this pc.: The bsod is very laggy after automatic repair when bootup. then it bring to the bsod. after that, it didnt give the option to reset this pc and straightway go to advanced option for troubleshooting. in this case i cannot reset my pc. command prompt also didnt work as scannow...
  7. After fresh install of Windows 11 I still get BSOD

    in Windows 10 Gaming
    After fresh install of Windows 11 I still get BSOD: This is my bug check code 0x1010x8, 0x0, 0xFFFFAA81A9D40180, 0x4 https://answers.microsoft.com/en-us/windows/forum/all/after-fresh-install-of-windows-11-i-still-get-bsod/6fb22eec-31a6-465a-a8a7-244fdb872962
  8. Enabling driver verifier causes BSOD boot loop

    in Windows 10 Gaming
    Enabling driver verifier causes BSOD boot loop: I have a sneaking suspicion that one or some of my drivers are acting up. I tried turning on driver verifier on all non-microsoft drivers, which caused a BSOD loop irql-not-less-or-equal. I have tried:- checking device manager for erroring drivers- DISM- Turned off all...
  9. After fresh install of Windows 11 I still get BSOD

    in Windows 10 Software and Apps
    After fresh install of Windows 11 I still get BSOD: This is my bug check code 0x1010x8, 0x0, 0xFFFFAA81A9D40180, 0x4 https://answers.microsoft.com/en-us/windows/forum/all/after-fresh-install-of-windows-11-i-still-get-bsod/6fb22eec-31a6-465a-a8a7-244fdb872962
  10. Enabling driver verifier causes BSOD boot loop

    in Windows 10 Software and Apps
    Enabling driver verifier causes BSOD boot loop: I have a sneaking suspicion that one or some of my drivers are acting up. I tried turning on driver verifier on all non-microsoft drivers, which caused a BSOD loop irql-not-less-or-equal. I have tried:- checking device manager for erroring drivers- DISM- Turned off all...