Asus vivobook sudden hangs during light inet surfing or reading win 11

Question

Win 11 suddenly hangs during light activities. I found this error message in event viewer at this time:

svchost (5036,T,0) SRUJet: A request to write to the file "C:\Windows\system32\SRU\SRU.log" at offset 45056 (0x000000000000b000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (43 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.

I tried check disk and it shows that ssd is fine,

Any ideas what it could be? I tried to post a minidump but whenever I attach it to the post it hangs the site and I have to redo the entire post...

When I run analyze -v on minidump in windbg I get following (I am using my other pc to analyze the dump)

WIN32K_POWER_WATCHDOG_TIMEOUT (19c)
Win32k did not turn the monitor on in a timely manner.
Arguments:
Arg1: 0000000000000050, Calling monitor driver to power on.
Arg2: ffffd08ded171080, Pointer to the power request worker thread.
Arg3: 0000000000000000
Arg4: 0000000000000000

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

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 12359

    Key  : Analysis.Elapsed.mSec
    Value: 13050

    Key  : Analysis.IO.Other.Mb
    Value: 0

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 0

    Key  : Analysis.Init.CPU.mSec
    Value: 625

    Key  : Analysis.Init.Elapsed.mSec
    Value: 8066

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 93

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27704.1001

    Key  : Analysis.Version.Description
    Value: 10.2408.27.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2408.27.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x19c

    Key  : Bugcheck.Code.TargetModel
    Value: 0x19c

    Key  : Dump.Attributes.AsUlong
    Value: 1808

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0

    Key  : Failure.Bucket
    Value: 0x19C_DRVSETMONITORPOWERSTATE_HANG_rtp2!unknown_function

    Key  : Failure.Hash
    Value: {516d6d7e-0fb8-68b9-572c-241c7cc1ecba}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 1417df84

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 0

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 1

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 1

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 1

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 1

    Key  : Hypervisor.Flags.HardwareMbecAvailable
    Value: 1

    Key  : Hypervisor.Flags.MaxBankNumber
    Value: 0

    Key  : Hypervisor.Flags.MemoryZeroingControl
    Value: 0

    Key  : Hypervisor.Flags.NoExtendedRangeFlush
    Value: 0

    Key  : Hypervisor.Flags.NoNonArchCoreSharing
    Value: 1

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 1

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 1

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 21631230

    Key  : Hypervisor.Flags.ValueHex
    Value: 14a10fe

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 1

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 1

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 1

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 1

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 1

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 1

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.Value
    Value: 1015

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 3f7

BUGCHECK_CODE:  19c

BUGCHECK_P1: 50

BUGCHECK_P2: ffffd08ded171080

BUGCHECK_P3: 0

BUGCHECK_P4: 0

FILE_IN_CAB:  061224-15531-01.dmp

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

DUMP_FILE_ATTRIBUTES: 0x1808
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffd08ded171080

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  csrss.exe

STACK_TEXT:  
fffff50f`d49531c0 fffff807`6083aa05     : ffffe080`e7351180 00000000`00000000 ffffd08d`7d6b4040 00000000`00000000 : nt!KiSwapContext+0x76
fffff50f`d4953300 fffff807`6083cbe7     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSwapThread+0xab5
fffff50f`d4953450 fffff807`6083eb06     : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x137
fffff50f`d4953500 fffff807`60819a00     : 00000000`0002d410 00000000`00002800 00000000`0000090d ffffd08d`00000080 : nt!KeWaitForSingleObject+0x256
fffff50f`d49538a0 fffff807`6082bc72     : 00000000`00000000 ffffd08d`ed171780 00000000`00000000 00000000`00000000 : nt!ExfAcquirePushLockExclusiveEx+0x1a0
fffff50f`d4953950 fffff807`60968eb3     : fffff50f`d4953a88 00000000`00000001 00000000`00000066 ffff9386`ebe002c0 : nt!ExAcquirePushLockExclusiveEx+0x112
fffff50f`d4953990 fffff807`60844d7e     : 00000000`0000090d 00000000`0000001d 00000000`00000002 fffff50f`d4954430 : nt!RtlpHpAcquireQueuedLockExclusive+0xa3
fffff50f`d49539c0 fffff807`6092fa0e     : fffff50f`00000045 fffff50f`00000440 00000000`00000046 00000000`00000000 : nt!RtlpHpVsContextAllocateInternal+0x7e
fffff50f`d4953a30 fffff807`6092f2cf     : fffff50f`00000002 00000000`000000e4 00000000`52435641 fffff807`608285e8 : nt!ExAllocateHeapPool+0x70e
fffff50f`d4953b50 fffff807`610ac03e     : fffff807`66962400 fffff50f`d4953fb0 ffff9387`7a50ae10 ffff9386`00000000 : nt!ExpAllocatePoolWithTagFromNode+0x5f
fffff50f`d4953ba0 fffff807`6086645d     : fffff50f`d4953c31 fffff50f`d4953be0 ffff9387`7a50ae10 00000000`00000000 : nt!ExAllocatePoolWithTag+0x2e
fffff50f`d4953be0 fffff807`6693d1c0     : 00000000`00000000 fffff50f`d4954040 00000000`00000000 00000000`00000000 : nt!ExAllocatePoolEx+0xd
fffff50f`d4953c10 00000000`00000000     : fffff50f`d4954040 00000000`00000000 00000000`00000000 fffff50f`d49542c0 : rtp2+0x2d1c0

SYMBOL_NAME:  rtp2+2d1c0

MODULE_NAME: rtp2

IMAGE_NAME:  rtp2.sys

STACK_COMMAND:  .process /r /p 0xffffd08df58301c0; .thread 0xffffd08ded171080 ; kb

BUCKET_ID_FUNC_OFFSET:  2d1c0

FAILURE_BUCKET_ID:  0x19C_DRVSETMONITORPOWERSTATE_HANG_rtp2!unknown_function

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {516d6d7e-0fb8-68b9-572c-241c7cc1ecba}

Followup:     MachineOwner

Any ideas what is going on?
Also where can I learn more about minidumps and windbg?

Answer 1

Hi Peckly,

I have checked the minidump files and it's indicating the 'rtp2.sys' driver causing your PC to crash. It may be part of a graphics driver suite, The driver could be involved in managing power states for display devices or sometimes these drivers come bundled with third-party applications that enhance graphics performance or manage display settings.

* In minidump file usually we check the Debugging Details like Process, Module name etc. , for more understanding you can check the below Microsoft Post : https://learn.microsoft.com/en-us/windows-hardw... *

To troubleshoot the issue, Kindly follow the below steps:

1. Ensure that your monitor and cables are properly connected and functioning
2. update the driver associated with rtp2.sys. Visit the hardware manufacturer's website for the latest drivers.
3. Temporarily disable any aggressive power-saving settings in the system BIOS/UEFI and Windows settings
4. Boot into Safe Mode to see if the issue occurs there.
5. In the Device Manager, double-click on the relevant entry ( Display driver or Power Management driver) , right-click on the problematic device and then select Properties. > Now, navigate to the Driver tab, and then click on the Roll Back Driver button. > Choose a reason for it, and then click on Yes at the bottom.
6. Press Windows + R to open the Run command, type mdsched in the text field, and then click OK or hit Enter. > Select the Restart now and check for problems (recommended) option.
7. Open Command Prompt as an administrator and run the command sfc /scannow to check for and repair corrupted system files
8. Press Windows + R to open Run, type msinfo32, and then press Enter > Find BIOS Version/Date and then verify your firmware version and check in manufacturer’s website for current version.

Let me know if this solution works for you. If not, please feel free to reply, and I'll be happy to provide further assistance. Whenever you feel the issue is resolved kindly mark the thread as answered.

Regards,

Kishen :)

Answer 2

Hello Kishen,

thanks for a quick reply.

You can find minidump here:

https://1drv.ms/u/s!AiDGw7PsLJ8ClQ8mq8Mf8iwX-UnJ?e=116U7b

I do not have access to this pc most of the time so this is all I have right now to go off.

Also can you expand on what you are looking for in the event viewer and minidump? Where can I read up on that?

Answer 3

Hi Peckly,

Thank you for reaching out to the Microsoft Community , I'm kishen an Independent Advisor and a Microsoft user like you. I'll be glad to assist you today.

Could you please share these files with me? You can find them in the following location:

1. C:\Windows\Minidump

Copy the minidump files to your Desktop, then compress them into a ZIP file.

Upload the ZIP file to a cloud service (such as OneDrive, Dropbox, etc.), and create a shareable link.

Share the link here so I can review the files for you.

2. Also, check C:\Windows and share the MEMORY.DMP file.

If the folder is empty or the MEMORY.DMP is not available, kindly share the Event viewer logs:https://www.yourwindowsguide.com/2017/12/how-to...

Standard Disclaimer: There are links to non-Microsoft websites. The pages appear to be providing accurate, safe information. Watch out for ads on the sites that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the sites before you decide to download and install it.

Regards,

Kishen :)