Je suis le gestionnaire du parc informatique des Bibliothèques de l’Université Coté d’Azur, et nous rencontrons exactement le même problème (avec exactement le même rapport WinDbg où Firefox est en cause) sur les 3/4 de nos Dell Latitude 5410 et Dell Latitude 5420. (et même maintenant sur des Latitude 5490)
Malgré toutes les mises à jour des pilotes, du bios et de Windows 10, (je suis même reparti avec un Windows 10 pro 21H2 neutre pour refaire l’image) ces satanées pages bleues (avec reboot) apparaissent toujours au bout d’une semaine d’utilisation environ...
Est-ce que vous avez trouvé une solution ?
Nous sommes à 2 doigts de supprimer Firefox de ces ordinateurs...
I'm the IT manager of the University Coté d'Azur Libraries (Nice, France), and we have exactly the same problem (with exactly the same WinDbg report where Firefox is involved) on 3/4 of our Dell Latitude 5410 and Dell Latitude 5420 (and even now on Latitude 5490)
Despite all the updates of drivers, bios and Windows 10, (I even left with a neutral Windows 10 pro 21H2 to do the image) these blue pages (with reboot) still appear after about a week of use...
Have you found a solution?
We are close to removing Firefox from these computers...
Unfortunately I still have the problem. But I can assure you that Firefox has nothing to do with it. I tried uninstalling it, but the problem still occurs. I also have PCs that don't have Firefox and the blue screens still occur. The "positive" thing is that it's less frequent... Sometimes it happens even with the PC turned on, with no programs open and no one using it.
SMarzorati
9 Posts
0
August 29th, 2022 08:00
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) 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 kernel debugger is available get stack backtrace. Arguments: Arg1: 0000000000000008, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, value 0 = read operation, 1 = write operation Arg4: fffff8065235d460, address which referenced memory Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 3765 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 3939 Key : Analysis.Init.CPU.mSec Value: 1858 Key : Analysis.Init.Elapsed.mSec Value: 3061 Key : Analysis.Memory.CommitPeak.Mb Value: 107 Key : Bugcheck.Code.DumpHeader Value: 0xd1 Key : Bugcheck.Code.KiBugCheckData Value: 0xd1 Key : Bugcheck.Code.Register Value: 0xa 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 FILE_IN_CAB: MEMORY.DMP BUGCHECK_CODE: d1 BUGCHECK_P1: 8 BUGCHECK_P2: 2 BUGCHECK_P3: 0 BUGCHECK_P4: fffff8065235d460 READ_ADDRESS: 0000000000000008 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 PROCESS_NAME: firefox.exe TRAP_FRAME: ffffa28323d04fb0 -- (.trap 0xffffa28323d04fb0)NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=0000000000000000 rbx=0000000000000000 rcx=ffffa28323d052b8 rdx=ffffa60ef206e010 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8065235d460 rsp=ffffa28323d05140 rbp=ffffa28323d051b9 r8=ffffa60ef206e0e0 r9=0000000000000027 r10=ffffa60f01f49310 r11=0000000000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc NETIO!StreamInvokeCalloutAndNormalizeAction+0x5c: fffff806`5235d460 488b4808 mov rcx,qword ptr [rax+8] ds:00000000`00000008=???????????????? Resetting default scope STACK_TEXT: ffffa283`23d04e68 fffff806`4bc0a869 : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx ffffa283`23d04e70 fffff806`4bc06b69 : ffffa283`23d05020 ffffa60e`e2f16ad0 ffffa60e`e550be80 fffff806`763f7bca : nt!KiBugCheckDispatch+0x69 ffffa283`23d04fb0 fffff806`5235d460 : ffffa60e`f206e0e0 ffffa283`23d051b9 ffffa283`23d05280 ffffa60e`f206e0e0 : nt!KiPageFault+0x469 ffffa283`23d05140 fffff806`5235d174 : ffffa283`23d055a0 ffffa60e`f206e010 00000000`00000000 ffffa60e`f206e0e0 : NETIO!StreamInvokeCalloutAndNormalizeAction+0x5c ffffa283`23d05210 fffff806`5235c77b : 00000000`00000014 fffff806`ac234cd0 ffffa60e`00000000 ffffa283`23d05c10 : NETIO!StreamProcessCallout+0x3fc ffffa283`23d05340 fffff806`523595eb : 00000000`00000014 ffffa283`23d05c10 ffffa283`23d05c40 ffffa283`23d05ac0 : NETIO!ProcessCallout+0x75b ffffa283`23d054c0 fffff806`5235818a : ffffa60f`0b1c73e0 ffffa283`23d05720 ffffa60e`981d0960 fffff806`52239fbb : NETIO!ArbitrateAndEnforce+0x71b ffffa283`23d05620 fffff806`5235789b : ffffa60e`00000003 00000000`00000000 ffffa60e`9560f820 fffff806`4baabc04 : NETIO!KfdClassify+0x37a ffffa283`23d05a10 fffff806`523574ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : NETIO!StreamClassify+0x28b ffffa283`23d05bb0 fffff806`52357158 : 00000000`00000000 ffffa283`23d06310 00000000`00000014 00000000`00000001 : NETIO!StreamCommonInspect+0x282 ffffa283`23d05f90 fffff806`5243f679 : ffffa283`23d06200 ffffa283`23d06310 ffffa283`23d06091 ffffa283`23d060b8 : NETIO!WfpStreamInspectSend+0x2a8 ffffa283`23d06020 fffff806`5243ef7e : 00000000`00000000 00000000`00000000 ffffa283`23d06280 fffff806`5243ef50 : tcpip!TcpEnqueueTcbSend+0x6d9 ffffa283`23d06160 fffff806`4badae28 : ffffa60e`e93c7b01 00000000`00000000 ffffe200`00000000 00000000`00000001 : tcpip!TcpTlConnectionSendCalloutRoutine+0x2e ffffa283`23d061a0 fffff806`4badad9d : fffff806`5243ef50 ffffa283`23d06280 ffffa60e`faed2af8 00000000`067a93ff : nt!KeExpandKernelStackAndCalloutInternal+0x78 ffffa283`23d06210 fffff806`524a61a0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0x1d ffffa283`23d06250 fffff806`761be0d0 : ffffa60e`faed2af8 ffffa60e`e93c7b80 00000000`00000018 ffffa60e`faed2af8 : tcpip!TcpTlConnectionSend+0x80 ffffa283`23d062c0 fffff806`761bdefa : ffffa60e`e93c7b80 ffffa283`23d06a80 ffffa60f`0a803370 ffffa60e`faed2bc0 : afd!AfdTLStartBufferedVcSend+0xa0 ffffa283`23d06370 fffff806`761a4010 : ffffa60e`faed2af8 ffffa283`23d06858 000000a1`00000018 ffffa283`23d06858 : afd!AfdFastConnectionSend+0x2a2 ffffa283`23d06440 fffff806`4be1bfd8 : 00000000`00000000 00000000`00000000 ffffa283`23d06a80 ffffa60f`067a9310 : afd!AfdFastIoDeviceControl+0xf90 ffffa283`23d067e0 fffff806`4be1b896 : 00000000`00000001 00000000`00000568 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x728 ffffa283`23d06920 fffff806`4bc0a2b5 : 00000000`80004005 00000271`2f4ef7d0 00000271`3ea3d520 00000271`2f44fd70 : nt!NtDeviceIoControlFile+0x56 ffffa283`23d06990 00007ffd`cb9cd024 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25 000000a1`8ffce9e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`cb9cd024 SYMBOL_NAME: NETIO!StreamInvokeCalloutAndNormalizeAction+5c MODULE_NAME: NETIO IMAGE_NAME: NETIO.SYS STACK_COMMAND: .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET: 5c FAILURE_BUCKET_ID: AV_NETIO!StreamInvokeCalloutAndNormalizeAction OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {c2ca2d1f-cfdc-88d5-c7bc-7693b8f0de04} Followup: MachineOwnerSMarzorati
9 Posts
0
October 6th, 2022 00:00
Hi Oli, the laptops are not connected to a docking station.
I have all firmware update, all Windows Update applied and all driver update.
The only thing that I could say is that in the last month, the issue show most rarely.
o-haine
2 Posts
0
October 6th, 2022 00:00
Hello! Is the laptop connected to a Dell docking station? Did you update the firmware of the docking? Are all Windows updates applied?
We are seeing the exact same issue...
Cheers,
OLi
Jo-One06
3 Posts
0
November 29th, 2022 01:00
Je suis le gestionnaire du parc informatique des Bibliothèques de l’Université Coté d’Azur, et nous rencontrons exactement le même problème (avec exactement le même rapport WinDbg où Firefox est en cause) sur les 3/4 de nos Dell Latitude 5410 et Dell Latitude 5420. (et même maintenant sur des Latitude 5490)
Malgré toutes les mises à jour des pilotes, du bios et de Windows 10, (je suis même reparti avec un Windows 10 pro 21H2 neutre pour refaire l’image) ces satanées pages bleues (avec reboot) apparaissent toujours au bout d’une semaine d’utilisation environ...
Est-ce que vous avez trouvé une solution ?
Nous sommes à 2 doigts de supprimer Firefox de ces ordinateurs...
Merci
Jo-One06
3 Posts
0
November 29th, 2022 01:00
I'm the IT manager of the University Coté d'Azur Libraries (Nice, France), and we have exactly the same problem (with exactly the same WinDbg report where Firefox is involved) on 3/4 of our Dell Latitude 5410 and Dell Latitude 5420 (and even now on Latitude 5490)
Despite all the updates of drivers, bios and Windows 10, (I even left with a neutral Windows 10 pro 21H2 to do the image) these blue pages (with reboot) still appear after about a week of use...
Have you found a solution?
We are close to removing Firefox from these computers...
Thanks
SMarzorati
9 Posts
0
November 29th, 2022 02:00
Unfortunately I still have the problem.
But I can assure you that Firefox has nothing to do with it.
I tried uninstalling it, but the problem still occurs.
I also have PCs that don't have Firefox and the blue screens still occur.
The "positive" thing is that it's less frequent... Sometimes it happens even with the PC turned on, with no programs open and no one using it.
SMarzorati
9 Posts
0
January 17th, 2023 05:00
I have upgraded these PCs to Windows 11.
The problem is still there!