BSDO

Anonymous
2022-02-05T12:48:37+00:00

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.

  • I made a CHKDSK to see if there was any error.

-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!

Windows for home | Windows 10 | Performance and system failures

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.

0 comments No comments

48 answers

Sort by: Oldest
  1. DaveM121 934.5K Reputation points Independent Advisor
    2022-02-05T13:23:28+00:00

    Hi baptistesatcher

    I am Dave, I will help you with this.

    Please upload any minidump files you have, I will check those to see if they provide any insight into a potential cause of the system crashes.

    Open Windows File Explorer.

    Navigate to C:\Windows\Minidump

    Copy any minidump files onto your Desktop, then zip those up.

    Upload the zip file to the Cloud (OneDrive, DropBox... etc.), then choose to share those and get a share link.

    Then post the link here to the zip file, so we can take a look for you.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2022-02-05T14:07:30+00:00

    Hello Dave.

    here is the wetransfer link with the 5 MiniDump.

    https://we.tl/t-g3BAQPMxoH

    Thanks !

    Was this answer helpful?

    0 comments No comments
  3. DaveM121 934.5K Reputation points Independent Advisor
    2022-02-05T14:28:04+00:00

    Hi baptistesatcher

    Your minidump files just indicate memory (RAM) corruption no specific driver is listed

    To try to force Windows 10 show any faulting drivers, the best option would be to turn on Driver Verifier, let your PC crash 3 times, then you must turn off Driver Verifier, and finally, upload any newly created minidump files

    https://answers.microsoft.com/en-us/windows/for...

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2022-02-05T14:55:13+00:00

    Hey Dave.
    Thanks for the quick answers.

    Here is a new minidump i just got. https://1drv.ms/u/s!AmtA0Sjek2N8gSNat2XOJjRX3El6

    I will now use that Driver verifier to stress the drivers.

    I come back soon to tell you what happened.

    Thanks again.

    Was this answer helpful?

    0 comments No comments
  5. DaveM121 934.5K Reputation points Independent Advisor
    2022-02-05T15:12:16+00:00

    Hi baptistesatcher

    There is also nothing specific listed in that new minidump file.

    Was this answer helpful?

    0 comments No comments