MB Biostar BT 250 BTC
CPU Intel G4560
RAM 4 gb ADATA
6 x Radeon RX 580 8 gb XFX
HDD KINGSTON SA400S37120G
2 x Chiftec ELP-700S
Crash Dump Analysis
Crash dumps are enabled on your computer.
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Wed 2/24/2021 8:02:32 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\022421-17890-01.dmp
This was probably caused by the following module:
bsmem.sys (0xFFFFF80445E73882)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF80445E73882)
Error:
DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\bsmem.sys
product:
BIOSTAR I/O driver fle
company:
BIOSTAR Group
description: I/O Interface driver file
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: bsmem.sys (I/O Interface driver file, BIOSTAR Group).
Google query:
bsmem.sys BIOSTAR Group DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Wed 2/24/2021 8:02:32 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module:
bsmem.sys (0xFFFFF80445E73882)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF80445E73882)
Error:
DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\bsmem.sys
product:
BIOSTAR I/O driver fle
company:
BIOSTAR Group
description: I/O Interface driver file
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: bsmem.sys (I/O Interface driver file, BIOSTAR Group).
Google query:
bsmem.sys BIOSTAR Group DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Wed 2/24/2021 7:58:48 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\022421-17640-01.dmp
This was probably caused by the following module:
bsmem.sys (0xFFFFF80228FD3882)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF80228FD3882)
Error:
DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\bsmem.sys
product:
BIOSTAR I/O driver fle
company:
BIOSTAR Group
description: I/O Interface driver file
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: bsmem.sys (I/O Interface driver file, BIOSTAR Group).
Google query:
bsmem.sys BIOSTAR Group DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Mon 2/8/2021 11:34:11 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\020821-19609-01.dmp
This was probably caused by the following module:
ntoskrnl.exe (nt+0x3F5780)
Bugcheck code: 0x9F (0x3, 0xFFFFA28DF553B060, 0xFFFFF8052AED2850, 0xFFFFA28DF98F7520)
Error:
DRIVER_POWER_STATE_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product:
Microsoft® Windows® Operating System
company:
Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state. A device object has been blocking an IRP for too long a time.
This is 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 Thu 2/4/2021 2:40:02 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\020421-20140-01.dmp
This was probably caused by the following module:
ntoskrnl.exe (nt+0x3F5780)
Bugcheck code: 0x9F (0x3, 0xFFFFCA076A6BE290, 0xFFFF890FFC837850, 0xFFFFCA076EAF5A30)
Error:
DRIVER_POWER_STATE_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product:
Microsoft® Windows® Operating System
company:
Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state. A device object has been blocking an IRP for too long a time.
This is 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 Wed 2/3/2021 6:19:58 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\020321-18968-01.dmp
This was probably caused by the following module:
ntoskrnl.exe (nt+0x3F5780)
Bugcheck code: 0x9F (0x3, 0xFFFFD68BB13AC060, 0xFFFFF806542D2850, 0xFFFFD68BBD373A30)
Error:
DRIVER_POWER_STATE_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product:
Microsoft® Windows® Operating System
company:
Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state. A device object has been blocking an IRP for too long a time.
This is 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.
Conclusion
6 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
bsmem.sys (I/O Interface driver file, BIOSTAR Group)
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.
Read the topic
general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
