Hi baptistesatcher
You only need to install the latest version (top) Realtek WiFi driver from that list.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hello !
First of all, sorry for my English.
I am trying to fix BSDO that i get (a lot, like 5 to 10 each day...) on my ASUS A15.
I tried different think to fix this :
-I updates the drivers with the latest version, but also i tried with the recommend version from Asus Support.
-I tested my RAM with Memetest.
-And finally, i reinstalled Windows 10
But sadly i still get this damn BSDO...
Just for information i mostly get them when i am on Internet and/or when i am downloading something. But for example i never get issue when i am playing games ( thanks god !). It's weird no ?
Here is the WhoCrash report :
System Information (local)
Computer name: LAPTOP-1R0V7FTB
Windows version: Windows 10, 10.0, version 2009, build: 19044
Windows dir: C:\WINDOWS
Hardware: ASUS TUF Gaming A15 FA506IV_TUF566IV, ASUSTeK COMPUTER INC., FA506IV
CPU: AuthenticAMD AMD Ryzen 7 4800H with Radeon Graphics 8664, level: 23
16 logical processors, active mask: 65535
RAM: 33736310784 bytes (31,4GB)
Crash Dump Analysis
Crash dumps are enabled on your computer.
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Sat 05/02/2022 13:36:43 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\020522-18437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F72E0)
Bugcheck code: 0xFC (0xFFFF8A0078D25F10, 0x81000007F21ED963, 0xFFFFFE8F94E844F0, 0x2)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
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 an attempt was made to execute non-executable memory.
This may be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. Memory corruption can also occur because of overheating (thermal issue). There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 05/02/2022 13:36:43 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!memset+0x79BA8)
Bugcheck code: 0xFC (0xFFFF8A0078D25F10, 0x81000007F21ED963, 0xFFFFFE8F94E844F0, 0x2)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
Bug check description: This indicates that an attempt was made to execute non-executable memory.
This may be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. Memory corruption can also occur because of overheating (thermal issue). There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 05/02/2022 12:07:44 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\020522-11640-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F72E0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8037B20928F, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 05/02/2022 11:43:28 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\020522-9609-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F72E0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8027D2BE5D3, 0xFFFFEE8F962DE120, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Sat 05/02/2022 09:57:21 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\020522-17265-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F72E0)
Bugcheck code: 0xD1 (0x0, 0x2, 0x8, 0x0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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 a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 05/02/2022 06:04:48 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\020522-18578-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F72E0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80526805701, 0x0, 0x48)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
I hope you can help me with this issues..
Thanks in advance!
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Hi baptistesatcher
You only need to install the latest version (top) Realtek WiFi driver from that list.
Hi.
https://1drv.ms/u/s!AmtA0Sjek2N8gSsEloMi7OXlqMPe?e=q5Tg4l Sorry but can you tell me what drivers that should be ?
And the network card are the 2 i put on the screenshot right ?
Thanks
Hi baptistesatcher
Driver Verifier indicates it is the device driver on your network card that is causing the crashes.
Please disable verifier, then go to the support page for your PC on the manufactures website, then from there, download and install the version of network card device drivers they recommend.
Hey dave.
So i ran the verifier on Microsoft Drivers. The Pc couldn't even start and i got a few time that error :
Driver Verified Detected Violation.
Here is the DMP file. https://1drv.ms/u/s!AmtA0Sjek2N8gShgCQ1qYSojLM9N
I saw on WhoCrash that the cause was the module verifierext.sys, that means the Verifier right ?
So i guess it doesn't give any infos right ?
Tanks again.
Hi baptistesatcher
That new minidump file also just indicates a generic memory corruption, it is unlikely to be a windows driver causing the crashes, but certainly you can try running verifier again to see if that flags a system driver.