Various BSODs all hinting towards drivers?

Page 13 of 13 FirstFirst ... 3111213

  1. Posts : 58
    Windows 10 Pro
    Thread Starter
       #121

    Hey guys, I did the clean boot and received a BSOD after ~24 hours.

    Memory_dmp210502.zip - Google Drive

    V2 log attached.
    Various BSODs all hinting towards drivers? Attached Files
      My Computer


  2. Posts : 38,626
    windows 10 professional version 1607 build 14393.969 64 bit
       #122

    Please swap test hardware.

    Latest bugcheck: 35

    Prior bugchecks:

    1
    139
    192
    3B
    50
    7F
    A
    A0
    C4
    D1
    FC
      My Computer

  3. philc43's Avatar
    Posts : 5,069
    64bit Win 10 Pro ver 20H2 Build 19042.985 and W10 Insider Preview Build 21376
       #123

    Hello ferchi

    That new bugcheck is an interesting one:

    Code:
    NO_MORE_IRP_STACK_LOCATIONS (35)
    A higher level driver has attempted to call a lower level driver through
    the IoCallDriver() interface, but there are no more stack locations in the
    packet, hence, the lower level driver would not be able to access its
    parameters, as there are no parameters for it.  This is a disastrous
    situation, since the higher level driver "thinks" it has filled in the
    parameters for the lower level driver (something it MUST do before it calls
    it), but since there is no stack location for the latter driver, the former
    has written off of the end of the packet.  This means that some other memory
    has probably been trashed at this point.
    Arguments:
    Arg1: ffff8d8dfcc212e0, Address of the IRP
    Arg2: 0000000000000000
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    The usual cause is a driver but it can also point to a problem with the RAM. In your case I would be more inclined to a driver since you have had 100+ hours in safe mode with no problem.

    The only 3rd party drivers active at the time of the crash were:
    amdgpio2.sys Wed Mar 11 11:15:48 2020 (5E68C864)
    AMDPCIDev.sys Wed Jan 13 09:54:28 2021 (5FFEC354)
    amdpsp.sys Fri Mar 6 21:04:04 2020 (5E62BAC4)
    ibtusb.sys Tue Feb 16 10:08:50 2021 (602B99B2)
    inpoutx64.sys Sat Oct 18 00:01:16 2008 (48F9193C)
    MsIo64.sys Mon Jan 20 03:35:15 2020 (5E251FF3)
    Netwtw10.sys Tue Dec 1 21:58:14 2020 (5FC6BC76)
    nvhda64v.sys Fri Oct 16 12:03:41 2020 (5F897E0D)
    nvlddmkm.sys Tue Feb 23 21:51:02 2021 (603578C6)
    rt640x64.sys Mon Jan 4 10:14:19 2021 (5FF2EA7B)
    RTKVHD64.sys Tue Jan 12 10:18:34 2021 (5FFD777A)
    ssgdio64.sys Fri Sep 9 19:40:54 2005 (4321D736)

    I've highlighted two of the oldest drivers that might be worth removing or updating.

    They are a driver for direct access to hardware ports and one from ATI diagnostics. I have no idea where these have come from!

    Hope it gives you a pointer in the right direction.
      My Computers


  4. Posts : 38,626
    windows 10 professional version 1607 build 14393.969 64 bit
       #124

    philc43 said:
    In your case I would be more inclined to a driver since you have had 100+ hours in safe mode with no problem.

    The only 3rd party drivers active at the time of the crash were:
    amdgpio2.sys Wed Mar 11 11:15:48 2020 (5E68C864)
    AMDPCIDev.sys Wed Jan 13 09:54:28 2021 (5FFEC354)
    amdpsp.sys Fri Mar 6 21:04:04 2020 (5E62BAC4)
    ibtusb.sys Tue Feb 16 10:08:50 2021 (602B99B2)
    inpoutx64.sys Sat Oct 18 00:01:16 2008 (48F9193C)
    MsIo64.sys Mon Jan 20 03:35:15 2020 (5E251FF3)
    Netwtw10.sys Tue Dec 1 21:58:14 2020 (5FC6BC76)
    nvhda64v.sys Fri Oct 16 12:03:41 2020 (5F897E0D)
    nvlddmkm.sys Tue Feb 23 21:51:02 2021 (603578C6)
    rt640x64.sys Mon Jan 4 10:14:19 2021 (5FF2EA7B)
    RTKVHD64.sys Tue Jan 12 10:18:34 2021 (5FFD777A)
    ssgdio64.sys Fri Sep 9 19:40:54 2005 (4321D736)

    I've highlighted two of the oldest drivers that might be worth removing or updating.

    They are a driver for direct access to hardware ports and one from ATI diagnostics. I have no idea where these have come from!

    Hope it gives you a pointer in the right direction.

    See post #107.
    The computer ran 1 week in normal boot without any BSOD.
    The 100 hours of safe mode was < 1 week or 168 hours
    So safe mode testing to be useful may need 2 weeks.


    If you plan to uninstall and reinstall the two drivers then check WDV first:
    Select only these two drivers for testing.
    Select all customized tests including Randomized low resources simulation.
    Run for 4 - 6 hours.

    The WDV test will either be a true pos / neg or a false pos / neg.

    There were multiple types of bugchecks.
    Drivers were tested with WDV.
    There were 6 memory dumps debugged.
    When available please swap test CPU / Motherboard.
      My Computer


 
Page 13 of 13 FirstFirst ... 3111213

  Related Discussions
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 01:12.
Find Us




Windows 10 Forums