BSOD Network Bridge

Status
Not open for further replies.

iFailGamer

Member
Joined
Aug 6, 2023
Posts
9
Hello everybody. As soon as I run Network Bridge from the phone to the network cable on my computer, after a few minutes it throws me an IRQL BSOD, I made a memory dump, but I don't understand where the error is.

Code:
************* Preparing the environment for Debugger Extensions Gallery repositories **************
   ExtensionRepository : Implicit
   UseExperimentalFeatureForNugetShare : false
   AllowNugetExeUpdate : false
   AllowNugetMSCredentialProviderInstall : false
   AllowParallelInitializationOfLocalRepositories : true

   -- Configuring repositories
      ----> Repository : LocalInstalled, Enabled: true
      ----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.016 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 36

Microsoft (R) Windows Debugger Version 10.0.25877.1004 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Full address space is 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
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Kernel base = 0xfffff807`32400000 PsLoadedModuleList = 0xfffff807`3302a2d0
Debug session time: Sun Aug  6 06:33:00.963 2023 (UTC + 3:00)
System Uptime: 0 days 0:10:38.634
Loading Kernel Symbols
...............................................................
................................................................
.........................................................
Loading User Symbols

Loading unloaded module list
............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff807`327fc0c0 48894c2408      mov     qword ptr [rsp+8],rcx ss:ffffbc0b`fdd0e8f0=000000000000000a
7: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000014, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80732602d44, address which referenced memory

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2889

    Key  : Analysis.Elapsed.mSec
    Value: 2902

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

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

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

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

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

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

    Key  : Bugcheck.Code.KiBugCheckData
    Value: 0xa

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0xa

    Key  : Failure.Bucket
    Value: AV_bridge!unknown_function

    Key  : Failure.Hash
    Value: {fc408975-df9e-bb6d-cca0-5d9f6ee3388a}

    Key  : Hypervisor.Enlightenments.Value
    Value: 0

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 0

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 0

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 0

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 0

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 0

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 0

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 0

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 0

    Key  : Hypervisor.Flags.HardwareMbecAvailable
    Value: 0

    Key  : Hypervisor.Flags.MaxBankNumber
    Value: 0

    Key  : Hypervisor.Flags.MemoryZeroingControl
    Value: 0

    Key  : Hypervisor.Flags.NoExtendedRangeFlush
    Value: 0

    Key  : Hypervisor.Flags.NoNonArchCoreSharing
    Value: 0

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 0

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 0

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 0

    Key  : Hypervisor.Flags.ValueHex
    Value: 0

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 0

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 0

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 0

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 0

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 0

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 0

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 0

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 0

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 0

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 0

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 0

    Key  : Hypervisor.RootFlags.Value
    Value: 0

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 0

    Key  : SecureKernel.HalpHvciEnabled
    Value: 0

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  a

BUGCHECK_P1: 14

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff80732602d44

FILE_IN_CAB:  MEMORY.DMP

READ_ADDRESS:  0000000000000014

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME:  System

TRAP_FRAME:  ffffbc0bfdd0ea30 -- (.trap 0xffffbc0bfdd0ea30)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000007 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80732602d44 rsp=ffffbc0bfdd0ebc0 rbp=ffffbc0bfdd0ed00
 r8=fffffffffffffffe  r9=0000000000000002 r10=0000000000000000
r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!ExReleaseRundownProtectionCacheAwareEx+0x14:
fffff807`32602d44 f77114          div     eax,dword ptr [rcx+14h] ds:00000000`00000014=????????
Resetting default scope

STACK_TEXT: 
ffffbc0b`fdd0e8e8 fffff807`32810129     : 00000000`0000000a 00000000`00000014 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffbc0b`fdd0e8f0 fffff807`3280bce3     : 00000000`00000001 ffffd684`03532de8 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffbc0b`fdd0ea30 fffff807`32602d44     : ffffd684`035cc440 ffffd684`06c864d0 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x463
ffffbc0b`fdd0ebc0 fffff807`3fb780d8     : 00000000`00000000 ffffd684`06c864d0 ffffd684`025c22c0 fffff807`326dac9e : nt!ExReleaseRundownProtectionCacheAwareEx+0x14
ffffbc0b`fdd0ebf0 fffff807`3fb78786     : 00000000`00000000 00000000`00000004 ffffbc0b`fdd0ed80 00000000`00000007 : bridge+0x80d8
ffffbc0b`fdd0ec80 fffff807`32726915     : ffffd684`025c22c0 ffffd684`025c22c0 fffff807`3fb78550 00000000`00000007 : bridge+0x8786
ffffbc0b`fdd0fb10 fffff807`32804cf8     : ffff8200`efad7180 ffffd684`025c22c0 fffff807`327268c0 ffffffff`00000000 : nt!PspSystemThreadStartup+0x55
ffffbc0b`fdd0fb60 00000000`00000000     : ffffbc0b`fdd10000 ffffbc0b`fdd09000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  bridge+80d8

MODULE_NAME: bridge

IMAGE_NAME:  bridge.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  80d8

FAILURE_BUCKET_ID:  AV_bridge!unknown_function

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {fc408975-df9e-bb6d-cca0-5d9f6ee3388a}

Followup:     MachineOwner
---------
 
Hello, and welcome to the forum!

We do have a set of BSOD posting instructions, it would help if you could follow those and upload the output we request. It contains no personally identifying data at all.
 
Hello, and welcome to the forum!

We do have a set of BSOD posting instructions, it would help if you could follow those and upload the output we request. It contains no personally identifying data at all.

======================================================================================================================================================================
  • A brief description of your problem: I work with mobile usb network and connect my ethernet cable in PC and Play Station, and then make a network bridge, his working but after 5-10 min a have a BSOD IRQL
  • System Manufacturer? - None
  • Laptop or Desktop?: Desktop
  • OS ? (Windows 11, 10, 8.1, 8, 7, Vista): Windows 10
  • x86 (32bit) or x64 (64bit)?: x64
  • What was original installed OS on system?: Windows 10, Original but have many tweaks from flibusher and i0ship.
  • Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)?: full retail version.
  • Age of system? (hardware): 7 years.
  • Age of OS installation?: 5 days
  • Have you re-installed the OS?: Yes
  • CPU: i7-6700k
  • RAM: Kingston FURY Beast 32GB (2x16GB) DDR4 3200MHz KF432C16BBK2/32 | i put it in 2 and 4 slots, and make XMP profile 2 what give me CL15
  • Video Card: RTX 4060
  • MotherBoard - ASUS B150M-C
  • Power Supply - ASUS ROG STRIX 850W GOLD (90YE00A3-B0NA00)
  • Is driver verifier enabled or disabled?: disabled
  • What security software are you using?: Nothing, windows defender off
  • Are you using proxy, vpn, ipfilters or similar software?: No
  • Are you using Disk Image tools?: No
  • Are you currently under/overclocking?: I don't use it.
 

Attachments

Last edited:
Network bridging isn't something I'm very familiar with. If I understand you correctly, you're using a mobile phone's Internet connection, which is USB attached to the PC. You also have an Ethernet cable connection between the PC and the Play Station. In the PC (ie. in Windows) you're bridging the two networks to extend Internet access to the Play Station. Do I have that more or less right?

In the two dumps (which are identical) the problem driver would appear to be bridge.sys...
Rich (BB code):
7: kd> knL
 # Child-SP          RetAddr               Call Site
00 ffffbc0b`fdd0e8e8 fffff807`32810129     nt!KeBugCheckEx
01 ffffbc0b`fdd0e8f0 fffff807`3280bce3     nt!KiBugCheckDispatch+0x69
02 ffffbc0b`fdd0ea30 fffff807`32602d44     nt!KiPageFault+0x463
03 ffffbc0b`fdd0ebc0 fffff807`3fb780d8     nt!ExReleaseRundownProtectionCacheAwareEx+0x14
04 ffffbc0b`fdd0ebf0 00000000`00000000     bridge+0x80d8

I was under the impression that bridge.sys was a Microsoft driver (ie. part of WIndows), yet your copy of bridge.sys does not appear to be a Microsoft driver...
Rich (BB code):
7: kd> lmDvm bridge
Browse full module list
start             end                 module name
fffff807`3fb70000 fffff807`3fb97000   bridge   T (no symbols)         
    Loaded symbol image file: bridge.sys
    Image path: \SystemRoot\System32\drivers\bridge.sys
    Image name: bridge.sys
    Browse all global symbols  functions  data
    Timestamp:        Fri Mar  2 16:46:04 2001 (3A9FB22C)
    CheckSum:         00021958
    ImageSize:        00027000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

Which begs the question; where did your copy of bridge.sys come from? It's clearly old, dating from March 2001 - which is positively archaic (though that might indoicate that it's a Microsoft driver after all).

Investigating further, I also came across the driver ew_usbccgpfilter.sys, which appears to be a Huawei USB C filter driver? The version of this you have is also old...
Rich (BB code):
7: kd> lmDvm ew_usbccgpfilter
Browse full module list
start             end                 module name
fffff807`5c1a0000 fffff807`5c1a4980   ew_usbccgpfilter   (deferred)           
    Image path: \SystemRoot\System32\drivers\ew_usbccgpfilter.sys
    Image name: ew_usbccgpfilter.sys
    Browse all global symbols  functions  data
    Timestamp:        Wed Nov 25 12:05:07 2015 (565587D3)
    CheckSum:         0000821F
    ImageSize:        00004980
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

Although this driver is not indicated in the dumps, if your phone is a Huawei then this driver will be involved. I would look for an update to the driver if possible.

Other members might be more familiar with what you're trying to achieve, but I'd like a bit more details on what products and drivers are involved in your network bridge. Is this just vanilla Windows bridging for example, or are you using some additional products/drivers? Note to other forum members, if you understand more about what the OP is doing here please jump in!

One other thing, it's not easy reading your logs etc. in Russian. It would help if, before you do another data colection upload, you change your system language to English.
 
The only reason I think of for using such an old driver if the user was trying to bridge their Playstation 2 (assuming PS2 since 2001 was the release date) with the PC in order to play online games which have had their servers shut down.
 
Network bridging isn't something I'm very familiar with. If I understand you correctly, you're using a mobile phone's Internet connection, which is USB attached to the PC. You also have an Ethernet cable connection between the PC and the Play Station. In the PC (ie. in Windows) you're bridging the two networks to extend Internet access to the Play Station. Do I have that more or less right?

In the two dumps (which are identical) the problem driver would appear to be bridge.sys...
Rich (BB code):
7: kd> knL
 # Child-SP          RetAddr               Call Site
00 ffffbc0b`fdd0e8e8 fffff807`32810129     nt!KeBugCheckEx
01 ffffbc0b`fdd0e8f0 fffff807`3280bce3     nt!KiBugCheckDispatch+0x69
02 ffffbc0b`fdd0ea30 fffff807`32602d44     nt!KiPageFault+0x463
03 ffffbc0b`fdd0ebc0 fffff807`3fb780d8     nt!ExReleaseRundownProtectionCacheAwareEx+0x14
04 ffffbc0b`fdd0ebf0 00000000`00000000     bridge+0x80d8

I was under the impression that bridge.sys was a Microsoft driver (ie. part of WIndows), yet your copy of bridge.sys does not appear to be a Microsoft driver...
Rich (BB code):
7: kd> lmDvm bridge
Browse full module list
start             end                 module name
fffff807`3fb70000 fffff807`3fb97000   bridge   T (no symbols)       
    Loaded symbol image file: bridge.sys
    Image path: \SystemRoot\System32\drivers\bridge.sys
    Image name: bridge.sys
    Browse all global symbols  functions  data
    Timestamp:        Fri Mar  2 16:46:04 2001 (3A9FB22C)
    CheckSum:         00021958
    ImageSize:        00027000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

Which begs the question; where did your copy of bridge.sys come from? It's clearly old, dating from March 2001 - which is positively archaic (though that might indoicate that it's a Microsoft driver after all).

Investigating further, I also came across the driver ew_usbccgpfilter.sys, which appears to be a Huawei USB C filter driver? The version of this you have is also old...
Rich (BB code):
7: kd> lmDvm ew_usbccgpfilter
Browse full module list
start             end                 module name
fffff807`5c1a0000 fffff807`5c1a4980   ew_usbccgpfilter   (deferred)         
    Image path: \SystemRoot\System32\drivers\ew_usbccgpfilter.sys
    Image name: ew_usbccgpfilter.sys
    Browse all global symbols  functions  data
    Timestamp:        Wed Nov 25 12:05:07 2015 (565587D3)
    CheckSum:         0000821F
    ImageSize:        00004980
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

Although this driver is not indicated in the dumps, if your phone is a Huawei then this driver will be involved. I would look for an update to the driver if possible.

Other members might be more familiar with what you're trying to achieve, but I'd like a bit more details on what products and drivers are involved in your network bridge. Is this just vanilla Windows bridging for example, or are you using some additional products/drivers? Note to other forum members, if you understand more about what the OP is doing here please jump in!

One other thing, it's not easy reading your logs etc. in Russian. It would help if, before you do another data colection upload, you change your system language to English.
My system language - Ukrainian. Not Russian. But okay, i change it how u say.

I use Huawei Honor 8x Max and connect him with my PC (Windows) via micro USB to USB 2.0. When i turn ON USB-modem i see new Network Adapter - "Android For Remote NDIS based Internet Sharing Device". Thats and "Realtek PCIe GbE Family Controller" (when i put Ethernet Cable) i make Network Bridge. Another cable side i put in Play Station 5.

For Update Driver i use Windows Update, CCleaner and IObit Driver Booster.
If u help me find new drivers for this device, thats be great) But ofcourse i will try something myself
 

Attachments

Please forgive me for calling you Russian. I do appreciate how insulting that was and I'm sorry.

Using driver search tools like Driver Booster is not wise. You can never be sure they're finding the best driver for your build, nor do you know where the driver they install has come from.

Regarding Ccleaner, have you ever used the registry cleaner in there?

It's getting late here (I'm in Crete Greece) so I'll come back to you tomorrow. I wanted to quickly apologise for my mistake in your location. I can't imagine what life is like for Ukranians right now.
 
Please forgive me for calling you Russian. I do appreciate how insulting that was and I'm sorry.

Using driver search tools like Driver Booster is not wise. You can never be sure they're finding the best driver for your build, nor do you know where the driver they install has come from.

Regarding Ccleaner, have you ever used the registry cleaner in there?

It's getting late here (I'm in Crete Greece) so I'll come back to you tomorrow. I wanted to quickly apologise for my mistake in your location. I can't imagine what life is like for Ukranians right now.
I don't blame you for anything and I'm not offended by anything. Moreover, there is currently a sufficiently large number of people from Ukraine who use the Russian language in the system. However, our national consciousness has awakened, and gradually, perhaps in 5-10 years, we will get rid of all this. This is strictly our national issue, which we are actively addressing by promoting content in our Ukrainian language. This issue has no relevance to the topic at hand, so if you're interested in having a conversation, here's my Discord: "d4_nya_". I apologize for this extensive off-topic discussion. I just wanted to say that you have nothing to apologize for; no one is asking you to be a linguist in a computer troubleshooting forum.
And I wanted to say thank you for helping me.

Now to the topic: I know everyone has a bad opinion about Driver Booster, but it hasn't let me down in recent years, I had good computer performance, so I used it (actually, I'm just too lazy to search everything manually, but don't tell anyone thats)
I used CCleaner both to update drivers and to clean the registry
Manually set only the video card driver and the sound driver because I have 2 audio cards.

Now i instalil Realtek LAN driver from ASUS website where my motherloard webpage, and i have new one error in memory.dmp

Unable to load image \SystemRoot\System32\drivers\bridge.sys, Win32 error 0n2
Code:
************* Preparing the environment for Debugger Extensions Gallery repositories **************
   ExtensionRepository : Implicit
   UseExperimentalFeatureForNugetShare : false
   AllowNugetExeUpdate : false
   AllowNugetMSCredentialProviderInstall : false
   AllowParallelInitializationOfLocalRepositories : true

   -- Configuring repositories
      ----> Repository : LocalInstalled, Enabled: true
      ----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.015 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 36

Microsoft (R) Windows Debugger Version 10.0.25877.1004 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Full address space is available


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Kernel base = 0xfffff804`1f000000 PsLoadedModuleList = 0xfffff804`1fc2a2d0
Debug session time: Sun Aug  6 23:13:14.987 2023 (UTC + 3:00)
System Uptime: 0 days 0:19:40.658
Loading Kernel Symbols
...............................................................
................................................................
...........................................................
Loading User Symbols

Loading unloaded module list
....................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff804`1f3fc0c0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffdf8a`fc9468f0=000000000000000a
1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000014, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8041f202d44, address which referenced memory

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

Unable to load image \SystemRoot\System32\drivers\bridge.sys, Win32 error 0n2

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2702

    Key  : Analysis.Elapsed.mSec
    Value: 4342

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

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

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

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

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

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

    Key  : Bugcheck.Code.KiBugCheckData
    Value: 0xa

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0xa

    Key  : Failure.Bucket
    Value: AV_bridge!unknown_function

    Key  : Failure.Hash
    Value: {fc408975-df9e-bb6d-cca0-5d9f6ee3388a}

    Key  : Hypervisor.Enlightenments.Value
    Value: 0

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 0

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 0

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 0

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 0

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 0

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 0

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 0

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 0

    Key  : Hypervisor.Flags.HardwareMbecAvailable
    Value: 0

    Key  : Hypervisor.Flags.MaxBankNumber
    Value: 0

    Key  : Hypervisor.Flags.MemoryZeroingControl
    Value: 0

    Key  : Hypervisor.Flags.NoExtendedRangeFlush
    Value: 0

    Key  : Hypervisor.Flags.NoNonArchCoreSharing
    Value: 0

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 0

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 0

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 0

    Key  : Hypervisor.Flags.ValueHex
    Value: 0

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 0

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 0

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 0

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 0

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 0

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 0

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 0

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 0

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 0

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 0

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 0

    Key  : Hypervisor.RootFlags.Value
    Value: 0

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 0

    Key  : SecureKernel.HalpHvciEnabled
    Value: 0

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  a

BUGCHECK_P1: 14

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff8041f202d44

FILE_IN_CAB:  MEMORY.DMP

READ_ADDRESS:  0000000000000014

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME:  System

TRAP_FRAME:  ffffdf8afc946a30 -- (.trap 0xffffdf8afc946a30)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8041f202d44 rsp=ffffdf8afc946bc0 rbp=ffffdf8afc946d00
 r8=ffffb8847accab00  r9=0000000000000002 r10=0000000000000000
r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!ExReleaseRundownProtectionCacheAwareEx+0x14:
fffff804`1f202d44 f77114          div     eax,dword ptr [rcx+14h] ds:00000000`00000014=????????
Resetting default scope

STACK_TEXT:
ffffdf8a`fc9468e8 fffff804`1f410129     : 00000000`0000000a 00000000`00000014 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffdf8a`fc9468f0 fffff804`1f40bce3     : 00000000`00000000 ffffb884`7b7f5158 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffdf8a`fc946a30 fffff804`1f202d44     : ffffb884`7ce766f0 ffffb884`7ab0ab40 ffffb884`00000000 00000000`00000000 : nt!KiPageFault+0x463
ffffdf8a`fc946bc0 fffff804`934b80d8     : 00000000`00000000 ffffb884`7ab0ab40 ffffb884`7b93be48 00000000`00000000 : nt!ExReleaseRundownProtectionCacheAwareEx+0x14
ffffdf8a`fc946bf0 fffff804`934b8786     : 00000000`00000000 00000000`00000004 ffffdf8a`fc946d80 00000000`00000001 : bridge+0x80d8
ffffdf8a`fc946c80 fffff804`1f326915     : ffffb884`7b958040 ffffb884`7b958040 fffff804`934b8550 00000000`00000001 : bridge+0x8786
ffffdf8a`fc947b10 fffff804`1f404cf8     : ffffcc01`42f00180 ffffb884`7b958040 fffff804`1f3268c0 fffff804`1f2231e8 : nt!PspSystemThreadStartup+0x55
ffffdf8a`fc947b60 00000000`00000000     : ffffdf8a`fc948000 ffffdf8a`fc941000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  bridge+80d8

MODULE_NAME: bridge

IMAGE_NAME:  bridge.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  80d8

FAILURE_BUCKET_ID:  AV_bridge!unknown_function

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {fc408975-df9e-bb6d-cca0-5d9f6ee3388a}

Followup:     MachineOwner
---------

So, i think all trouble with bridge.sys, but i don't find update for him.
 
Many thanks for the English language download.

It's your PC of course and you're free to use whatever tools you like. However, the use of tools like Driver Booster is most unwise. Drivers run in kernel mode, which gives them access to the heart of your OS and where they can do almost anything. It's most important that you source drivers only from known reliable sources, not just for security reasons but to avoid BSODs when the wrong driver is selected (which we do see). Drivers should only ever be sourced from the following locations...
  • Windows Update - and be sure to check in optional updates for driver updates.
  • The PC/laptop vendor's website - particularly important for laptops, where some drivers are often customised
  • The software product vendor's website, for products that introduce drivers (like anti-virus tools for example)
  • The PC motherboard vendor's website, for drivers for motherboard devices and for BIOS updates
  • The specific hardware device vendor's website and/or official driver support tool - where none of the above found a suitable driver
You don't have to take my advice, but I strongly advise against using Driver Booster or any similar tools. It's not impossible that your current problems are caused by a bad driver installed by Driver Booster.

Using a registry cleaner is also unwise, there is always a danger of the cleaner removing a registry entry that is being used. The registry is the Windows database and its absolutely critical to the proper operation of Windows. To put it bluntly, the registry does not need cleaning, if it did then Microsoft would provide a tool in Windows. In my (quite long) career in Windows support I have never ever seen a problem that could be convincingly laid at the door of an unused/redundant registry entry, but I have seen countless problems caused by registry cleaners. Microsoft actively discourage the use of registry cleaners...
Microsoft is not responsible for issues caused by using a registry cleaning utility. We strongly recommend that you only change values in the registry that you understand or have been instructed to change by a source you trust, and that you back up the registry before making any changes.
Source: Microsoft support policy for the use of registry cleaning utilities - Microsoft Support

Again, it's not impossible that your current problems have been caused by overly aggressive registry cleaning. By using Driver Booster and a registry cleaner you have a system that is in a state which we can't fully trust, that makes systematic troubleshooting that much more difficult.

I have a couple of questions if that's ok?
  1. Has this network bridge ever worked successfully, or is this the first time of using it? If it has worked in the past, what changed recently?
  2. Are you using only the built-in Windows bridging features, or are you using additional bridging software. If so, what are you using?
  3. You have Proton VPN installed, is the VPN active and connected during your bridging attempt?
Also, you seem to be having Windows activation problems...
Code:
Event[0]:
  Log Name: Application
  Source: Microsoft-Windows-Security-SPP
  Date: 2023-08-06T18:57:51.5140000Z
  Event ID: 8198
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: HOME-PC
  Description:
License Activation (slui.exe) failed with the following error code:
hr=0xC004F074
Command-line arguments:
RuleId=502ff3ba-669a-4674-bbb1-601f34a3b968;Action=AutoActivateSilent;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=2de67392-b7a7-462a-b1ca-108dd189f588;NotificationInterval=1440;Trigger=UserLogon;SessionId=2

Could you please open a command prompt window and enter the command slmgr /dlv. A small window will open, please post a screenshot of that window.

As for bridge.sys, it may not be the root cause, it might just be tripping over an issue created by another driver that we don't see in the dumps. That's why I asked about the VPN and why I asked about the Huawei USB-C driver. It might be wise to download the Huawei PC Manager and see whether that finds a driver update for the Huawei USB-C driver. If the VPN is active during the bridging connection can you try it without the VPN connected?

I think the next most sensible troubleshooting step will be to enable Driver Verifier and see whether we can catch the potentially flaky driver that may be causing bridge.sys to fail. Please see here; Driver Verifier - BSOD related - Windows 11, 10, 8.1 and 8 for full details on how to enable Driver Verifier and what options to select. We expect BSODs when running Driver Verifier, indeed we want BSODs to try and identify the failing driver. Please try your bridging connection whilst Driver Verifier is running, but please also leave it running for at least 24 hours whilst you use the PC, to give it the best opportunity of catching a flaky driver.

Note: Your PC may be sluggish with Driver Verifier running, this is to be expected and is normal.
 
Many thanks for the English language download.

It's your PC of course and you're free to use whatever tools you like. However, the use of tools like Driver Booster is most unwise. Drivers run in kernel mode, which gives them access to the heart of your OS and where they can do almost anything. It's most important that you source drivers only from known reliable sources, not just for security reasons but to avoid BSODs when the wrong driver is selected (which we do see). Drivers should only ever be sourced from the following locations...
  • Windows Update - and be sure to check in optional updates for driver updates.
  • The PC/laptop vendor's website - particularly important for laptops, where some drivers are often customised
  • The software product vendor's website, for products that introduce drivers (like anti-virus tools for example)
  • The PC motherboard vendor's website, for drivers for motherboard devices and for BIOS updates
  • The specific hardware device vendor's website and/or official driver support tool - where none of the above found a suitable driver
You don't have to take my advice, but I strongly advise against using Driver Booster or any similar tools. It's not impossible that your current problems are caused by a bad driver installed by Driver Booster.

Using a registry cleaner is also unwise, there is always a danger of the cleaner removing a registry entry that is being used. The registry is the Windows database and its absolutely critical to the proper operation of Windows. To put it bluntly, the registry does not need cleaning, if it did then Microsoft would provide a tool in Windows. In my (quite long) career in Windows support I have never ever seen a problem that could be convincingly laid at the door of an unused/redundant registry entry, but I have seen countless problems caused by registry cleaners. Microsoft actively discourage the use of registry cleaners...

Source: Microsoft support policy for the use of registry cleaning utilities - Microsoft Support

Again, it's not impossible that your current problems have been caused by overly aggressive registry cleaning. By using Driver Booster and a registry cleaner you have a system that is in a state which we can't fully trust, that makes systematic troubleshooting that much more difficult.

I have a couple of questions if that's ok?
  1. Has this network bridge ever worked successfully, or is this the first time of using it? If it has worked in the past, what changed recently?
  2. Are you using only the built-in Windows bridging features, or are you using additional bridging software. If so, what are you using?
  3. You have Proton VPN installed, is the VPN active and connected during your bridging attempt?
Also, you seem to be having Windows activation problems...
Code:
Event[0]:
  Log Name: Application
  Source: Microsoft-Windows-Security-SPP
  Date: 2023-08-06T18:57:51.5140000Z
  Event ID: 8198
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: HOME-PC
  Description:
License Activation (slui.exe) failed with the following error code:
hr=0xC004F074
Command-line arguments:
RuleId=502ff3ba-669a-4674-bbb1-601f34a3b968;Action=AutoActivateSilent;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=2de67392-b7a7-462a-b1ca-108dd189f588;NotificationInterval=1440;Trigger=UserLogon;SessionId=2

Could you please open a command prompt window and enter the command slmgr /dlv. A small window will open, please post a screenshot of that window.

As for bridge.sys, it may not be the root cause, it might just be tripping over an issue created by another driver that we don't see in the dumps. That's why I asked about the VPN and why I asked about the Huawei USB-C driver. It might be wise to download the Huawei PC Manager and see whether that finds a driver update for the Huawei USB-C driver. If the VPN is active during the bridging connection can you try it without the VPN connected?

I think the next most sensible troubleshooting step will be to enable Driver Verifier and see whether we can catch the potentially flaky driver that may be causing bridge.sys to fail. Please see here; Driver Verifier - BSOD related - Windows 11, 10, 8.1 and 8 for full details on how to enable Driver Verifier and what options to select. We expect BSODs when running Driver Verifier, indeed we want BSODs to try and identify the failing driver. Please try your bridging connection whilst Driver Verifier is running, but please also leave it running for at least 24 hours whilst you use the PC, to give it the best opportunity of catching a flaky driver.

Note: Your PC may be sluggish with Driver Verifier running, this is to be expected and is normal.
Ok, I will follow your advice the next time I reinstall Windows, I will try the option of updating the drivers through official sources and not cleaning the registry.

Regarding your questions:
1. I'm using a bridge for the first time, I didn't use it at all in the past, I only needed it because I don't have a router and to play PlayStation from a local network I need this bridge right now.
2. All I use is TCP Optimizer and Network Parameter Settings in the AutoSettingsPS 0.5.9 tweaker (I will attach a photo of the settings), everything else is unchanged.
3. Yes, Proton VPN is installed, but I don't use it, I don't see its activity in Task Manger, so I assume that it doesn't work in the background either.

Yes, there were problems with activation, but I fixed them, I am sending a new Sysnative File, I am adding a photo of your slmgr dlv command to the ZIP archive. After my fixes, nothing has changed, the bridge still does not work.

Regarding Huawei PC Manager, I got an error, I can't install it, I think it's because I don't have a Huawei laptop. (I am attaching a photo of the error).
 

Attachments

  • Sysnative-Actual.zip
    Sysnative-Actual.zip
    1.1 MB · Views: 5
  • Huawei.png
    Huawei.png
    5.6 KB · Views: 5
  • Local Network.png
    Local Network.png
    65.9 KB · Views: 8
  • Network.png
    Network.png
    56.4 KB · Views: 5
  • TCP.png
    TCP.png
    608.7 KB · Views: 5
I think you're right about the Huawei tool being only for Huawei devices. Sadly I'm not able to find an official Huawei site to download an updated version of that driver. I have discovered that there are two versions in existence; 1.0.9.0, which appears to date from 2015, and version 1.0.10.0, which appears to date from 2016. There are a few unofficial sites that claim to have a copy of this driver. I cannot recommend or suggest that you use any of them however.

My opinion of tweaking tools is the same as my opinion on Driver Booster and registry cleaners. The difference that most TCP/IP tweaks make is marginal at best in my experience, compared with the defaults. If it were me, I'd want all those TCP settings restored to default until you have your bridging working.

Do you know whether this tweaking tool makes any changes in real-time?

I notice in the local network output that you have file & printer sharing disabled on the Private (local) network. I would suggest that you enable this. The name is misleading, because it's involved in more than just file and printer sharing, it's required for a lot of network sharing features.

I'm not sure what the 'Restore' entry means on the Network Discovery+Services entry (number [5])? I would suggest that you want this feature turned on, although I'm not sure if it's involved, Microsoft's network and sharing feature is a minefield. In my (albeit limited) experience with it, you want to open everything up in terms of network sharing in order to get things working, and then gradually close things down to the level you want.

In the same vein, and on the network output, the tweaker has disabled NetBIOS and DCOM - are you certain that these are not required when network bridging? I don't know for sure but it might be wiser to enable them. The same with administrative shares, although this relates to disk sharing they are network related shares and this might be needed?

If this were mine, I would use the tweaker to restore all setting to their default values and disable or uninstall the tweaker tool - at least until this problem is resolved. My worry now is that we're fighting a system that may have unknown drivers installed (courtesy of Driver Booster), that may have had important registry entries removed (courtesy of Ccleaner) and now may have incorrect or invalid network settings (courtesy of the tweaker tool).

I think that if none of my above suggestions regarding the tweaker help, and if you still get these BSODs, then enabling Driver Verifier is the best way forward.
 
I think you're right about the Huawei tool being only for Huawei devices. Sadly I'm not able to find an official Huawei site to download an updated version of that driver. I have discovered that there are two versions in existence; 1.0.9.0, which appears to date from 2015, and version 1.0.10.0, which appears to date from 2016. There are a few unofficial sites that claim to have a copy of this driver. I cannot recommend or suggest that you use any of them however.

My opinion of tweaking tools is the same as my opinion on Driver Booster and registry cleaners. The difference that most TCP/IP tweaks make is marginal at best in my experience, compared with the defaults. If it were me, I'd want all those TCP settings restored to default until you have your bridging working.

Do you know whether this tweaking tool makes any changes in real-time?

I notice in the local network output that you have file & printer sharing disabled on the Private (local) network. I would suggest that you enable this. The name is misleading, because it's involved in more than just file and printer sharing, it's required for a lot of network sharing features.

I'm not sure what the 'Restore' entry means on the Network Discovery+Services entry (number [5])? I would suggest that you want this feature turned on, although I'm not sure if it's involved, Microsoft's network and sharing feature is a minefield. In my (albeit limited) experience with it, you want to open everything up in terms of network sharing in order to get things working, and then gradually close things down to the level you want.

In the same vein, and on the network output, the tweaker has disabled NetBIOS and DCOM - are you certain that these are not required when network bridging? I don't know for sure but it might be wiser to enable them. The same with administrative shares, although this relates to disk sharing they are network related shares and this might be needed?

If this were mine, I would use the tweaker to restore all setting to their default values and disable or uninstall the tweaker tool - at least until this problem is resolved. My worry now is that we're fighting a system that may have unknown drivers installed (courtesy of Driver Booster), that may have had important registry entries removed (courtesy of Ccleaner) and now may have incorrect or invalid network settings (courtesy of the tweaker tool).

I think that if none of my above suggestions regarding the tweaker help, and if you still get these BSODs, then enabling Driver Verifier is the best way forward.
Okay, for testing purposes, I restored the TCP and AutoSettingsPS configuratios to their default settings.
Neither of these changes take effect in real-time, and after making all the changes, these two programs can be completely removed from the computer without leaving any tasks behind.

I enabled file and printer sharing.
Network Discovery + Services and NetBIOS + DCOM enabled themselves automatically after resetting all settings.
In addition to all this, I did a network reset in the network & internet settings

Also, I noticed some very large numbers in the Network Bridge Status that do not reflect reality.
It appears that the network speeds simply add up from the two internet adapters.
- I have one adapter named 'Android For Remote NDIS based...' that gives 425.9 Mbps,
- And the second adapter, 'Realtek PCIe GbE Family Controller,' gives 1000 Mbps.
I managed to set a 100 Mbps duplex limit on the second adapter, but the 'Android For Remote NDIS based...' adapter does not have this option.
This difference might cause conflicts or some malfunction, as reducing the speed to 525.9 Mbps on the network bridge resulted in a BSOD.

Additionally, I noticed that when I am not actively using the computer, and the network bridge is just working, it operates significantly longer compared to when I use the computer for activities like watching YouTube or using PlayStation Remote Play. There could be various potential causes for this behavior, such as conflicts with the video card, processor, or RAM. There are many possibilities, but I can perform measurements if needed to investigate further. It seems that the BSOD occurs much faster when I actively use the computer.

Driver Verifier gave me another BSOD, from which I had to restore the system.
 

Attachments

  • Screenshot_12.png
    Screenshot_12.png
    14.3 KB · Views: 6
  • Screenshot_13.png
    Screenshot_13.png
    14.8 KB · Views: 3
  • Screenshot_10.png
    Screenshot_10.png
    13.3 KB · Views: 7
  • BSOD.jpg
    BSOD.jpg
    88.6 KB · Views: 7
Okay, for testing purposes, I restored the TCP and AutoSettingsPS configuratios to their default settings.
Neither of these changes take effect in real-time, and after making all the changes, these two programs can be completely removed from the computer without leaving any tasks behind.

I enabled file and printer sharing.
Network Discovery + Services and NetBIOS + DCOM enabled themselves automatically after resetting all settings.
In addition to all this, I did a network reset in the network & internet settings

Also, I noticed some very large numbers in the Network Bridge Status that do not reflect reality.
It appears that the network speeds simply add up from the two internet adapters.
- I have one adapter named 'Android For Remote NDIS based...' that gives 425.9 Mbps,
- And the second adapter, 'Realtek PCIe GbE Family Controller,' gives 1000 Mbps.
I managed to set a 100 Mbps duplex limit on the second adapter, but the 'Android For Remote NDIS based...' adapter does not have this option.
This difference might cause conflicts or some malfunction, as reducing the speed to 525.9 Mbps on the network bridge resulted in a BSOD.

Additionally, I noticed that when I am not actively using the computer, and the network bridge is just working, it operates significantly longer compared to when I use the computer for activities like watching YouTube or using PlayStation Remote Play. There could be various potential causes for this behavior, such as conflicts with the video card, processor, or RAM. There are many possibilities, but I can perform measurements if needed to investigate further. It seems that the BSOD occurs much faster when I actively use the computer.

Driver Verifier gave me another BSOD, from which I had to restore the system.
I reread what I wrote, I was shocked, I'm sorry... I decided that my knowledge of English was not quite enough and I used ChatGPT.

I would like to clarify what was written:
My phone gives 120 mb\sec internet, the adapter allocates it as 425.9 mb\sec
And the gigabit cable transmits my 120 mb\sec from the phone to the PlayStation, so I wrote that these adapters and, in particular, the network bridge give incorrect information.

And in the sentence "This difference might cause conflicts or some malfunction, as reducing the speed to 525.9 Mbps on the network bridge resulted in a BSOD." - I wanted to write something completely different, namely that I assume that it can cause some errors and I also wanted to write that the result of 525.9 Mbps on the network bridge adapter did not help me avoid BSOD
 
Are you saying that the network bridge now works, at least in some fashion?

Can you please upload another Sysnative file collection output please so I can loomat thd dump for that recent BSOD?
 
Are you saying that the network bridge now works, at least in some fashion?

Can you please upload another Sysnative file collection output please so I can loomat thd dump for that recent BSOD?
The network bridge works as it did, the first 5-10 minutes of active use, and after that = BSOD. All my actions that I did above did not affect BSOD in any way, I'm just sharing my observations.

The last BSOD was caused by a driver verifier, this BSOD appeared right after BIOS boot and prevented user login. I had to use a restore point to get inside.
 

Attachments

Whilst scanning your Application log I noticed that you're still seeing Windows activation errors. One message in particular indicates that your license is a volume license using the Microsoft Generic Volume License Key (GVLK)...
Rich (BB code):
Event[23]:
  Log Name: Application
  Source: Microsoft-Windows-Security-SPP
  Date: 2023-08-08T17:35:09.5230000Z
  Event ID: 8230
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: HOME-PC
  Description: 
The rules engine successfully re-evaluated the schedule.
Kernel policies:
Security-SPP-Action-StateData (REG_SZ) =AppId=55c92734-d682-4d71-983e-d6ec3f16059f;GraceEndDate=2038/01/19:03:12:09;LastConsumptionReason=0x00000000;LastNotificationId=VolumeRenewalRequired;LicenseState=SL_LICENSING_STATUS_LICENSED;PartialProductKey=T83GX;ProductKeyType=Volume:GVLK;SkuId=2de67392-b7a7-462a-b1ca-108dd189f588;ruleId=502ff3ba-669a-4674-bbb1-601f34a3b968;uxDifferentiator=ENVIRONMENT;volumeActivationOrder=normal

This does not match the output of slmgr /dlv command that you uploaded earlier when I queried your activation status...
1. slmgr dlv.png

Not only are the licensing channels different but the partial product key is different. I can only form the opinion that this image does not relate to the system you're seeking help with and you have attempted to deceive us. The forum rules require that...
You agree to not use the Service to submit or link to any Content which ... risks copyright infringement

It's my opinion that you're using a volume licensed copy of Windows on a home computer. I'm happy to be proven wrong.
 
Whilst scanning your Application log I noticed that you're still seeing Windows activation errors. One message in particular indicates that your license is a volume license using the Microsoft Generic Volume License Key (GVLK)...
Rich (BB code):
Event[23]:
  Log Name: Application
  Source: Microsoft-Windows-Security-SPP
  Date: 2023-08-08T17:35:09.5230000Z
  Event ID: 8230
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: HOME-PC
  Description:
The rules engine successfully re-evaluated the schedule.
Kernel policies:
Security-SPP-Action-StateData (REG_SZ) =AppId=55c92734-d682-4d71-983e-d6ec3f16059f;GraceEndDate=2038/01/19:03:12:09;LastConsumptionReason=0x00000000;LastNotificationId=VolumeRenewalRequired;LicenseState=SL_LICENSING_STATUS_LICENSED;PartialProductKey=T83GX;ProductKeyType=Volume:GVLK;SkuId=2de67392-b7a7-462a-b1ca-108dd189f588;ruleId=502ff3ba-669a-4674-bbb1-601f34a3b968;uxDifferentiator=ENVIRONMENT;volumeActivationOrder=normal

This does not match the output of slmgr /dlv command that you uploaded earlier when I queried your activation status...
View attachment 90026

Not only are the licensing channels different but the partial product key is different. I can only form the opinion that this image does not relate to the system you're seeking help with and you have attempted to deceive us. The forum rules require that...


It's my opinion that you're using a volume licensed copy of Windows on a home computer. I'm happy to be proven wrong.
Yes, you caught me... 👮‍♀️

Sorry... At the beginning, when I installed Windows, I have a not valid activation.
Hindered by the driver verifier's launch, Windows access eluded me.
Eventually i had to roll back the system to the point when I still had the old activation.
Reassured by the successful rollback of the system, I did not pay attention to the windows activation.
Liberally sharing my expertise, I've recorded a video with the new activation now.
Observing the ongoing challenges, I decided to address another common issue. In this video, I demonstrated everything I do to get BSOD (Blue Screen of Death) errors.
Concluding, you can notice at the end of the video that I created a zip archive of Sysnative (Before BSOD) and showed that there is also this information that you showed me in your screenshot.
Keenly observing i do not know why the old activation is written to this file, it is still a mystery to me.

 

Attachments

I'm sorry, but I'm not comfortable assisting your further. I don't appreciate being deliberately deceived.
 
Status
Not open for further replies.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top