BSOD Always When Live Streaming?

Kenny4AG · Nov 17, 2023

My PC keeps crashing during Live Streams, very frustrating as I can't seem to replicate it, Even during live streaming 1 time it occurred an hour into stream, another 15 min into stream, both times after a reboot it didn't occur again until the next day.

PC SPECS:
Windows 11
I7 9700K
Z390 Aorus Elite MB
32 GB Ram

I'm not certain that its crashing because of the live stream specifically but Its only occurring during live streams and seems to happen at random. The software I'm using to stream is OBS.

I've run a memory test and it showed no issues.

I should mention I installed a new Power Supply between the two BSOD because I suspected that was an issue but it clearly wasn't.

Here is the DUMP Files

MY-PC-(2023-11-17_01-50-06).zip

drive.google.com

ubuysa · Nov 17, 2023

Unfortunately there are indications that your Windows license may not be valid. You are licenced via the VOLUME_MAK channel which is only available to corporations and businesses.

Kenny4AG · Nov 17, 2023

ubuysa said:
Unfortunately there are indications that your Windows license may not be valid. You are licenced via the VOLUME_MAK channel which is only available to corporations and businesses.

Hi

Sorry You're mistaken my license is valid

It also says my license is active in settings, not to mention this is my personal business computer (of multiple) in our office.

i'm not sure i understand, it was a win10 pro i upgraded to 11, but also how does that relate to a crash that has only emerged in the last 2 weeks when i've been on win11 for a year.

I also took a look at your other posts and saw you commenting this on other people's questions without elaborating how that is related to a BSOD.

For give me if im clueless but how is this impactful

I really do need help and there is nothing wrong with the license

ubuysa · Nov 17, 2023

Does this PC belong to a corporation that licenses it's PCs via a volume licensing agreement with Microsoft? Or is it a personal computer (regardless of whether you use it for business purposes)?

Kenny4AG · Nov 17, 2023

ubuysa said:
Does this PC belong to a corporation that licenses it's PCs via a volume licensing agreement with Microsoft? Or is it a personal computer (regardless of whether you use it for business purposes)?

Correct this PC is owned by a corporation and specifically sits in the studio portion of our building. Do I need to provide you the exact persons phone number who deals with Microsoft...

If you can't help that is totally ok but please just state that so I understand you are unwilling to help.

Much appreciated

ubuysa · Nov 19, 2023

It's not that I'm unwilling to help, it's that the forum rules here do not allow any discussion of pirated software. I'm not trying to police Windows licenses but I have to obey the forum rules. Thank you for clarifying that you're working on a corporate volume licensed PC, we don't see too many of those.

The two dumps both fail in the same way, and both are 0xA IRQL_NOT_LESS_OR_EQUAL bugchecks. This bugcheck happens because a driver took a page fault, ie. referenced memory that was invalid (not allocated, paged-out, or bad RAM), whilst running at an elevated IRQL (when page faults are not allowed). Most of the time this is caused by a flaky third-party driver that either screws up it's memory allocations or fouls up a memory pointer. It looks from your dumps as thought that might well be the problem here.

Both dumps fail during a networking operation, as you said in the OP. We see only Windows functions being called in the call stack (which shows the function calls leading up to the bugcheck) but one of the Windows drivers called is afd.sys. This is the Auxiliary Function Driver for Winsock and because it's a Windows driver it's not at fault. Although we don't see it in the call stack a networking operation will ultimately call you network adapter driver, and this is where your problem may well lay.

You're using the Intel I219-V Ethernet adapter, the driver for this is e1i68x64.sys and the version you have installed looks to be quite old, dating from May 2021...

Code:

4: kd> lmDvm e1i68x64
Browse full module list
start             end                 module name
fffff801`875e0000 fffff801`87673000   e1i68x64   (deferred)           
    Mapped memory image file: c:\mysymbols\e1i68x64.sys\60AA46B893000\e1i68x64.sys
    Image path: e1i68x64.sys
    Image name: e1i68x64.sys
    Browse all global symbols  functions  data
    Timestamp:        Sun May 23 15:12:40 2021 (60AA46B8)
    CheckSum:         000986DB
    ImageSize:        00093000
    File version:     12.19.1.32
    Product version:  10.0.10011.16384
    File flags:       8 (Mask 3F) Private
    File OS:          40004 NT Win32
    File type:        3.6 Driver
    File date:        00000000.00000000
    Translations:     0000.04b0
    Information from resource tables:
        CompanyName:      Intel Corporation
        ProductName:      Intel(R) Gigabit Adapter
        InternalName:     e1i68x64.sys
        OriginalFilename: e1i68x64.sys
        ProductVersion:   12.19.1.32
        FileVersion:      12.19.1.32
        FileDescription:  Intel(R) Gigabit Adapter NDIS 6.x driver
        LegalCopyright:   Copyright(C) 2013, Intel Corporation.  All rights reserved.

The easiest way to check for driver updates for Intel products is to download the Intel Driver and Support Assistant and run that you scan the PC for driver updates for Intel devices. I would install any updates it finds.

See how that goes. If it still BSODs please run the V2 log collector again and upload the zip file.

Kenny4AG · Nov 30, 2023

ubuysa said:
It's not that I'm unwilling to help, it's that the forum rules here do not allow any discussion of pirated software. I'm not trying to police Windows licenses but I have to obey the forum rules. Thank you for clarifying that you're working on a corporate volume licensed PC, we don't see too many of those.

The two dumps both fail in the same way, and both are 0xA IRQL_NOT_LESS_OR_EQUAL bugchecks. This bugcheck happens because a driver took a page fault, ie. referenced memory that was invalid (not allocated, paged-out, or bad RAM), whilst running at an elevated IRQL (when page faults are not allowed). Most of the time this is caused by a flaky third-party driver that either screws up it's memory allocations or fouls up a memory pointer. It looks from your dumps as thought that might well be the problem here.

Both dumps fail during a networking operation, as you said in the OP. We see only Windows functions being called in the call stack (which shows the function calls leading up to the bugcheck) but one of the Windows drivers called is afd.sys. This is the Auxiliary Function Driver for Winsock and because it's a Windows driver it's not at fault. Although we don't see it in the call stack a networking operation will ultimately call you network adapter driver, and this is where your problem may well lay.

You're using the Intel I219-V Ethernet adapter, the driver for this is e1i68x64.sys and the version you have installed looks to be quite old, dating from May 2021...

Code:

4: kd> lmDvm e1i68x64 Browse full module list start end module name fffff801`875e0000 fffff801`87673000 e1i68x64 (deferred) Mapped memory image file: c:\mysymbols\e1i68x64.sys\60AA46B893000\e1i68x64.sys Image path: e1i68x64.sys Image name: e1i68x64.sys Browse all global symbols functions data Timestamp: Sun May 23 15:12:40 2021 (60AA46B8) CheckSum: 000986DB ImageSize: 00093000 File version: 12.19.1.32 Product version: 10.0.10011.16384 File flags: 8 (Mask 3F) Private File OS: 40004 NT Win32 File type: 3.6 Driver File date: 00000000.00000000 Translations: 0000.04b0 Information from resource tables: CompanyName: Intel Corporation ProductName: Intel(R) Gigabit Adapter InternalName: e1i68x64.sys OriginalFilename: e1i68x64.sys ProductVersion: 12.19.1.32 FileVersion: 12.19.1.32 FileDescription: Intel(R) Gigabit Adapter NDIS 6.x driver LegalCopyright: Copyright(C) 2013, Intel Corporation. All rights reserved.

The easiest way to check for driver updates for Intel products is to download the Intel Driver and Support Assistant and run that you scan the PC for driver updates for Intel devices. I would install any updates it finds.

See how that goes. If it still BSODs please run the V2 log collector again and upload the zip file.

DUDE omg I reformatted the PC, updated my drivers and is BSOD again after running fine for 1.5 weeks

AND during a stream again

/cry

ubuysa · Dec 1, 2023

How did you update the drivers? Did you allow Windows Update to install all drivers or did you get them from somewhere else? If from somewhere else then where did you get them from?

It may be a hardware issue with the LAN adapter, so can you try connecting via WiFi for a while to check?

Kenny4AG · Dec 1, 2023

ubuysa said:
How did you update the drivers? Did you allow Windows Update to install all drivers or did you get them from somewhere else? If from somewhere else then where did you get them from?

It may be a hardware issue with the LAN adapter, so can you try connecting via WiFi for a while to check?

After the new BSOD I went and got Intel Driver and Support Assistant, when I ran a search it said no updates but I still had the old driver for the LAN connection from 2021

I just updated it manually by going to the driver page directly and will now run some more test

I'm sorry if this is annoying

ubuysa · Dec 2, 2023

It's not annoying at all, I apologise if I'm giving that impression. I love helping with sticky problems like this, they're more interesting and rewarding than the simple ones!

Its essential that we know exactly how you got to this point and since 99% of all software problems are caused by bad drivers that's always a question we ask. Troubleshooting is like peeling an onion, you start at the outside and peel back layer by layer, always ensuring that each layer has been confirmed as good before moving on.

One test that it will be VERY useful for you to do, but which you won't like at all, is to start Windows in Safe Mode (with networking). In Safe Mode a stripped-down core version of Windows with only essential services is loaded and with (almost) no third-party drivers loaded. Because you then have the most stable Windows system you can get, if it BSODs in Safe Mode you almost certainly have a hardware problem. If it doesn't BSOD in Safe Mode you can be pretty sure that you have a software/driver problem.

However.....in Safe Mode you won't be able to do any useful work, because most of your devices won't work properly (or at all), because their drivers are not loaded. Your display will be low resolution for example, because only the Windows basic display driver is loaded. Safe Mode is such a useful tool though, that a couple of days of pain in order to determine whether the problem has a hardware or software cause can save many, many days of random troubleshooting. I really urge you to take the time to give Safe Mode a good long testing - including leaving it running in Safe Mode overnight. You won't like it (or me for suggesting it!) but it's a really useful test.

Rollback_Jockey · Dec 2, 2023

Kenny4AG said:
My PC keeps crashing during Live Streams, very frustrating as I can't seem to replicate it, Even during live streaming 1 time it occurred an hour into stream, another 15 min into stream, both times after a reboot it didn't occur again until the next day.

PC SPECS:
Windows 11
I7 9700K
Z390 Aorus Elite MB
32 GB Ram

I'm not certain that its crashing because of the live stream specifically but Its only occurring during live streams and seems to happen at random. The software I'm using to stream is OBS.

I've run a memory test and it showed no issues.

I should mention I installed a new Power Supply between the two BSOD because I suspected that was an issue but it clearly wasn't.

Here is the DUMP Files

MY-PC-(2023-11-17_01-50-06).zip

drive.google.com

Do you have any settings for "Use Hardware Acceleration where available" try toggling it, check if you have updated video drivers available.