BSOD at random times

Page 1 of 2 12 LastLast

  1. thpapak
    Posts : 9
    Windows 10 64bit
       New #1

    BSOD at random times


    Hello!

    My PC is getting a lot of BSOD, about 2-3 every day. The BSOD happen at random, etc. I might be browsing, playing a game or even doing nothing at all.
    Things I have tried before:
    WIndows and Driver updates (no exclamation mark at Device manager) -Still BSOD
    SFC and DSIM commands, check HDD for errors - Still BSOD
    Scan with MawareBytes- Still BSOD
    Resocket RAM Dimm and run Windows MemoryTest (Extended) for every dimm - No memory error - Still BSOD

    After every solution I could find in Google searches, I did a Windows reset. PC run for 1 day and got 2 BSOD. I must add that I don't have the older crash dumb files because of the reset, but as far as I remember there were 4-5 different categories of BSOD.

    Running Windows 10 64bit 22H2 ver.19045.2311

    Thank you!

    [Report from WhoCrashed programm:
    On Sun 20/11/2022 12:45:57 μμ your computer crashed or a problem was reported
    crash dump file: C:\WINDOWS\Minidump\112022-16734-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x3F9290)
    Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFD0, 0x2, 0xFFFFF80780A0EBC6, 0x2)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    file path: C:\WINDOWS\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that invalid system memory has been referenced.
    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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Sun 20/11/2022 12:45:57 μμ your computer crashed or a problem was reported
    crash dump file: C:\WINDOWS\MEMORY.DMP
    This was probably caused by the following module: wdfilter.sys (WdFilter+0x4A4AA)
    Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFD0, 0x2, 0xFFFFF80780A0EBC6, 0x2)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    file path: C:\WINDOWS\system32\drivers\wdfilter.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Microsoft antimalware file system filter driver
    Bug check description: This indicates that invalid system memory has been referenced.
    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 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.]
    BSOD at random times Attached Files
      My Computer
    Quote Quote

  3. thpapak
    Posts : 9
    Windows 10 64bit
    Thread Starter
       New #2

    I am attaching the tuneup log
    BSOD at random times Attached Files
      My Computer
    Quote Quote

  4. thpapak
    Posts : 9
    Windows 10 64bit
    Thread Starter
       New #3

    MAIN-(2022-11-25_22-09-36).zip
    Another log collector, getting a lot of BSOD
      My Computer
    Quote Quote

  6. tomdsr
    Posts : 890
    10 Pro/11 Pro Dual Boot
       New #4

    thpapak said:
    MAIN-(2022-11-25_22-09-36).zip
    Another log collector, getting a lot of BSOD
    test memory please
    MemTest86+ - Test RAM
      My Computers
    Quote Quote

  7. thpapak
    Posts : 9
    Windows 10 64bit
    Thread Starter
       New #5

    Hello,
    Did a memory test, PASS on all 8 memory tests with Memtest86+.
      My Computer
    Quote Quote

  8. tomdsr
    Posts : 890
    10 Pro/11 Pro Dual Boot
       New #6

    thpapak said:
    Hello,
    Did a memory test, PASS on all 8 memory tests with Memtest86+.
    well....

    For analysis of this file, run !analyze -v
    2: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 0000000000061941, The subtype of the bugcheck.
    Arg2: 0000023ec293a954
    Arg3: 000000000000000d
    Arg4: ffffd283a4c53b00

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


    KEY_VALUES_STRING: 1

    Key : Analysis.CPU.mSec
    Value: 2702

    Key : Analysis.DebugAnalysisManager
    Value: Create

    Key : Analysis.Elapsed.mSec
    Value: 3229

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

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

    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: 1a

    BUGCHECK_P1: 61941

    BUGCHECK_P2: 23ec293a954

    BUGCHECK_P3: d

    BUGCHECK_P4: ffffd283a4c53b00

    BLACKBOXBSD: 1 (!blackboxbsd)


    BLACKBOXNTFS: 1 (!blackboxntfs)


    BLACKBOXPNP: 1 (!blackboxpnp)


    BLACKBOXWINLOGON: 1

    CUSTOMER_CRASH_COUNT: 1

    PROCESS_NAME: firefox.exe

    STACK_TEXT:
    ffffd283`a4c53958 fffff802`4242e296 : 00000000`0000001a 00000000`00061941 0000023e`c293a954 00000000`0000000d : nt!KeBugCheckEx
    ffffd283`a4c53960 fffff802`42408dd8 : 80000000`00000000 00000000`00000000 00000000`00000000 ffffe70f`00000000 : nt!MmAccessFault+0x1f4c56
    ffffd283`a4c53b00 00007ffc`192cfdb3 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x358
    00000094`c01fd4a0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`192cfdb3


    MODULE_NAME: hardware

    IMAGE_NAME: hardware_ram

    STACK_COMMAND: .thread ; .cxr ; kb

    FAILURE_BUCKET_ID: 0x1a_61941_PAGE_TABLE_RESERVED_BITS_SET_IMAGE_hardware_ram

    OS_VERSION: 10.0.19041.1

    BUILDLAB_STR: vb_release

    OSPLATFORM_TYPE: x64

    OSNAME: Windows 10

    FAILURE_ID_HASH: {c6e5c6cf-692e-7852-5dc5-b74944540fc0}

    Followup: MachineOwner
    ---------
      My Computers
    Quote Quote

  9. thpapak
    Posts : 9
    Windows 10 64bit
    Thread Starter
       New #7

    So, I am between a DIMM RAM fault and a motherboard fault?
      My Computer
    Quote Quote

  10. axe0
    Posts : 14,903
    Windows 10 Pro
       New #8

    Please run driver verifier using the following settings for 48 hours.
    • Special Pool
    • Force IRQL checking
    • Pool Tracking
    • Deadlock Detection
    • Security Checks
    • Miscellaneous Checks
    • Power framework delay fuzzing
    • DDI compliance checking


    On top of selecting third-party drivers as described in the tutorial linked above, also select the following drivers
    • Wdf01000.sys
    • ndis.sys
    • fltMgr.sys
    • Storport.sys



    Warning: driver verifier could cause boot issues and/or performance issues.



    Resetting driver verifier options (recommended in this order)
    1. In normal mode open an administrator command prompt and enter the below command
    2. In safe mode open an administrator command prompt and enter the below command
    3. On 3 boot failures, you'll boot automatically to the recovery options,
      • click Troubleshoot
      • go to the advanced options
      • choose command prompt
      • enter the below command
    4. Boot with the recovery media, see above 4 steps in option 3.
    5. Via the recovery options or recovery media, select a restore point prior enabling driver verifier

    Code:
    verifier /reset


    Crashed when running driver verifier
    1. Reset driver verifier
    2. Boot in normal mode if necessary
    3. Follow Blue Screen of Death (BSOD) Posting Instructions to provide the requested logs




    Extra information about driver verifier
    When you run driver verifier, there are two things you're looking out for
    1. Driver verifier won't find any driver violating something and thus in the time you need to run it there won't be a crash
    2. Driver verifier will find a driver violating something and thus the system will crash.

    The end result of driver verifier is either of the two, but when driver verifier finds something your system will BSOD.


    Driver verifier essentially validates selected drivers on selected actions, this validation adds some delay to actions performed in the background which results in a performance decrease that many people notice. This is called stress testing drivers and depending on quite a few factors this performance decrease is worse for some than for others, and some won't even notice a difference.

    Depending on the drivers selected, it is possible that some of the selected drivers are so-called 'boot' drivers, meaning they load when your system is booting. If these drivers don't pass a validation check, your system will crash, but since the drivers are loading at boot, your system will basically be in a boot loop. That is one of the risks involved and the most important one. Of course, there are various methods to recover from it.

    If you want visual confirmation that driver verifier is actually running, copy/paste the following command in powershell or command prompt

    Code:
    verifier /query
    If the command gives a result similar to this, it means driver verifier is running.


      My Computers
    Quote Quote

  12. thpapak
    Posts : 9
    Windows 10 64bit
    Thread Starter
       New #9

    Did the driver verifier, posting results.

    Thank you !
    BSOD at random times Attached Files
      My Computer
    Quote Quote

  13. tomdsr
    Posts : 890
    10 Pro/11 Pro Dual Boot
       New #10

    thpapak said:
    Did the driver verifier, posting results.

    Thank you !
    Logitech driver.

    0: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
    A device driver attempting to corrupt the system has been caught. This is
    because the driver was specified in the registry as being suspect (by the
    administrator) and the kernel has enabled substantial checking of this driver.
    If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
    be among the most commonly seen crashes.
    Arguments:
    Arg1: 0000000000000140, Non-locked MDL constructed from either pageable or tradable memory.
    Arg2: 0000000000000000, Current IRQL level.
    Arg3: ffff9908550fefc0, MDL address
    Arg4: ffffd28f575c4000, Associated virtual address with this MDL

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

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

    KEY_VALUES_STRING: 1

    Key : Analysis.CPU.mSec
    Value: 2499

    Key : Analysis.DebugAnalysisManager
    Value: Create

    Key : Analysis.Elapsed.mSec
    Value: 11054

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

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

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

    BUGCHECK_P1: 140

    BUGCHECK_P2: 0

    BUGCHECK_P3: ffff9908550fefc0

    BUGCHECK_P4: ffffd28f575c4000

    BLACKBOXBSD: 1 (!blackboxbsd)


    BLACKBOXNTFS: 1 (!blackboxntfs)


    BLACKBOXPNP: 1 (!blackboxpnp)


    BLACKBOXWINLOGON: 1

    CUSTOMER_CRASH_COUNT: 1

    PROCESS_NAME: LWEMon.exe

    STACK_TEXT:
    ffffd28f`575c4508 fffff805`5bbd5e34 : 00000000`000000c4 00000000`00000140 00000000`00000000 ffff9908`550fefc0 : nt!KeBugCheckEx
    ffffd28f`575c4510 fffff805`5bbeb6cb : ffff9908`550fefc0 00000000`00000008 ffff9908`38004dc0 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0xe0
    ffffd28f`575c4550 fffff803`1beb0a9a : ffffd28f`575c4638 ffffd28f`575c4638 00000000`0000049e 00000000`00000000 : nt!VerifierMmBuildMdlForNonPagedPool+0xab
    ffffd28f`575c4590 ffffd28f`575c4638 : ffffd28f`575c4638 00000000`0000049e 00000000`00000000 ffff9908`536dd010 : WmFilter+0xa9a
    ffffd28f`575c4598 ffffd28f`575c4638 : 00000000`0000049e 00000000`00000000 ffff9908`536dd010 fffff805`5b4394cb : 0xffffd28f`575c4638
    ffffd28f`575c45a0 00000000`0000049e : 00000000`00000000 ffff9908`536dd010 fffff805`5b4394cb 00000000`00000000 : 0xffffd28f`575c4638
    ffffd28f`575c45a8 00000000`00000000 : ffff9908`536dd010 fffff805`5b4394cb 00000000`00000000 00000000`00000000 : 0x49e


    SYMBOL_NAME: WmFilter+a9a

    MODULE_NAME: WmFilter

    IMAGE_NAME: WmFilter.sys

    STACK_COMMAND: .thread ; .cxr ; kb

    BUCKET_ID_FUNC_OFFSET: a9a

    FAILURE_BUCKET_ID: 0xc4_140_VRF_WmFilter!unknown_function

    OS_VERSION: 10.0.19041.1

    BUILDLAB_STR: vb_release

    OSPLATFORM_TYPE: x64

    OSNAME: Windows 10

    FAILURE_ID_HASH: {3891eb0a-9a99-02e4-b473-6553d641961f}

    Followup: MachineOwner
    ---------
    Your logitech software is old.

    yours: version 5.10.127
    current: version 9.04.49
    link: https://download01.logi.com/web/ftp/...4_Logitech.exe
      My Computers
    Quote Quote

 

  Related Discussions
BSOD at random times
in BSOD Crashes and Debugging

I have started experiencing random BSOD while doing simple things like internet use or when my son is playing ROBLOX. I have not experienced them during any heavy load such as gaming. MS version 1909 build 18363.1082
BSOD at very random times, no specific times.
in BSOD Crashes and Debugging

Hi guys, I keep on getting BSOD screens when using my laptop. It is very random, sometimes it happens whilst I am working in Adobe Photoshop or Illustrator or even just when I am browsing the web. At first I thought it might be the display...
Random BSOD in random times
in BSOD Crashes and Debugging

Hi, I'm really hoping to solve the problem since it's starting to distract seriously. I think since early summer BSODs been flashing now and then and now more and more often. Naturally I've tried memory solutions found online for memory related...
BSOD at random times doing random things.
in BSOD Crashes and Debugging

Hi, I am getting BSODs at random times, while doing different things each time. Been getting them for 5 days trying to narrow down what could be causing it. Searching lead me here. I did the posting instructions. Also did sfc/scannow 2 times that...
BSOD at random times
in BSOD Crashes and Debugging

I am still getting BSOD. I uploaded the latest file. I would appreciate any help you can provide. This is becoming very frustrating. Thanks
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

 © Designer Media Ltd
All times are GMT -5. The time now is 04:58.
Find Us




Windows 10 Forums